diff options
author | Andrew Yu <andrew@andrewyu.org> | 2022-04-16 21:57:16 +0200 |
---|---|---|
committer | Andrew Yu <andrew@andrewyu.org> | 2022-04-16 21:57:16 +0200 |
commit | bb3870b584f8dc862a66b218be3c24094d02d981 (patch) | |
tree | b5f8ef51bfddd41c3b349735aaaceb77104360b5 /pragmatics | |
parent | 566ce45b9f9a77118f869ec592d388b26ae92ec2 (diff) | |
download | www-bb3870b584f8dc862a66b218be3c24094d02d981.tar.gz |
foldersort
Diffstat (limited to 'pragmatics')
-rw-r--r-- | pragmatics/Makefile | 14 | ||||
-rw-r--r-- | pragmatics/pragmatics.7 | 112 | ||||
-rw-r--r-- | pragmatics/pragmatics.html | 1390 | ||||
-rw-r--r-- | pragmatics/pragmatics.man | 215 | ||||
-rw-r--r-- | pragmatics/pragmatics.md | 142 | ||||
-rw-r--r-- | pragmatics/pragmatics.txt | 280 | ||||
-rw-r--r-- | pragmatics/pragmatics.xml | 113 |
7 files changed, 2266 insertions, 0 deletions
diff --git a/pragmatics/Makefile b/pragmatics/Makefile new file mode 100644 index 0000000..3fdf7c2 --- /dev/null +++ b/pragmatics/Makefile @@ -0,0 +1,14 @@ +update: pragmatics.txt pragmatics.man + git add . + git commit + git push + +pragmatics.man: pragmatics.7 + groff -man -Tascii pragmatics.7 > pragmatics.man +pragmatics.7: pragmatics.md + mmark --man pragmatics.md > pragmatics.7 +pragmatics.txt: pragmatics.xml + xml2rfc --text --html pragmatics.xml +pragmatics.xml: pragmatics.md + mmark pragmatics.md > pragmatics.xml + diff --git a/pragmatics/pragmatics.7 b/pragmatics/pragmatics.7 new file mode 100644 index 0000000..1200ce8 --- /dev/null +++ b/pragmatics/pragmatics.7 @@ -0,0 +1,112 @@ +.\" Generated by Mmark Markdown Processer - mmark.miek.nl +.TH "PRAGMATIC USE OF NONFREE SOFTWARE" 1 "April 2022" "Free Software" "Free Software Community" + +.SH "ABSTRACT" +.PP +Free Software is undoubtably a good thing for society. However, modern computer users are stuck in the proprietary "ecosystem" for historical reasons. This document describes the author's viewpoint of using proprietary platforms to spread the ideas of Free Software. + +.SH "STATUS OF THIS MEMO" +.PP +This document is currently in the DRAFT status. + +.PP +This document describes the author's viewpoint. This does not represent the ideas of the Free Software Foundation or any other entity. Distribution of this memo is unlimited. + +.SH "INTRODUCTION" +.PP +Readers of this memo probably understand the ideals of the Free Software Movement, and avoid proprietary software when possible. However, as most outsiders are unaware and are deeply buried inside the proprietary dystopia created by mostly multibillion-dollar technology coorporations, our methods of communicating with the masses are ineffective. + +.PP +In February 2022, the author decided to adjust his dogma, and permitted limited usage of nonfree chat platforms to hopefully spread our ideas to the general public. This was attempted by registering a Discord account, creating a Guild called "Free Software Introductions", and setting up a basic Discord-to-IRC relay to #fsi on both irc.andrewyu.org and irc.libera.chat. + +.PP +One of the communities that he knows about, the VF-Technic Minetest community, primarily uses Discord as a means of communication by plays not in-game. As the users inside are Minetest players, a Free Software voxel sandbox game, similar to but much more flexible and freedom-respecting than Minecraft, it is believed that the users have some contact with Free Software, although they might not understand the freedom part of the issue, i.e. they might be thinking in terms of "open source" instead. After sharing the invite link in the VF-Technic Guild, some people joined, and we've partially converted two users. + +.SH "JUSTIFICATION" +.PP +Two users is definitely few, but it sets a start and an example for how freedom can be spread. + +.PP +There are numerous free replacements to proprietary services such as Discord, such as Internet Relay Chat, the Extensible Messaging and Presense Protocol, the Matrix protocol, and email. As Free Software activists, we generally prefer these protocols over nonfree services. This section explains the reasons to consider nonfree services and protocols. + +.PP +Generally, users on IRC and XMPP have a fair understanding of the Free Software Movement, and it is quick and easy to inform them what we mean by "free", "the four freedoms", and similar ideas. For users on the Libera Chat IRC network, which by far has the most users of any network, it is exceptionally easy to introduce a user into the #fsf channel for discussions with people supporting Free Software. Introducing ignorant users on these protocols and platforms are a day-to-day simple task. + +.PP +Furthermore, the amount of users we can reach on these protocols are rather limiting. Libera has around forty thousand users according to the \fB\fCUSERS\fR command, and considering the fact that around 90% of these people aren't ignorant, there isn't much we can do. + +.PP +Matrix users, in particular users of the matrix.org homeserver, typically know but don't completely understand Free Software. Rather than using Matrix IDs to identify users, the Matrix specification specifies that third-party platform identities, such as email and GitHub, are how users should be referenced both internally by servers and shown to other users. This is obviously an increadibly foolish idea, especially considering the use of centralized identity servers (similar to X509 certificate authorities) for 3PIDs. These are our first targets, but these should also be easy to get the idea across. + +.PP +It is true that Libera Chat and similar IRC networks, though multi-centered in a technical way (i.e. multiple IRC servers form an IRC network), the network is politically centralized, controlled by one entity, Libera. The Internet Relay Chat server-to-server protocol implies that servers fully trust each other and are expected to not send damaging commands, which in turn implies full trust between server operators, no federation, and political centralization. The privacy policy and network policy of Libera Chat are in the author's opinion non-intrusive, therefore the use of which is acceptable and is promoted by the FSF. (Obviously, most methods of using IRC do not involve nonfree software.) + +.PP +Nevertheless, those that have never touched Free Software are often on giant proprietary platforms, and take these as universal methods of communication. Many people go months before checking their mailbox (physical or electronic), refuse to use XMPP or IRC for its age. + +.PP +An alternative protocol, Internet Delay Chat, is being developed. + +.PP +There is one special case where using some nonfree software, and even urging others to use it, can be a positive thing. That's when the use of the nonfree software aims directly at putting an end to the use of that very same nonfree software.[RMSGP] The author believes that the following fall within this scope: + +.IP \(bu 4 +Developing a free program that requires nonfree environments to bootstrap; +.IP \(bu 4 +To spread awareness of software freedom issues to users in nonfree environments. + + +.PP +As almost all types of programming can be done on most types of BSD and GNU operating systems, the author hasn't found any software that fit this category. Extending the interpretation allos for using nonfree software's behavior as a reference in Free Software development, though an arguable programming practice, may help the community to progress by understanding common features that users of nonfree services use. + +.PP +The latter is more interesting, as explained above our methods of spreading awareness is limited. + +.SH "ACTION PROCEDURE" +.PP +Activists \fBMUST NOT\fP list such nonfree services in "Contact Information" pages on their website or similar sources, unless followed by a explanation that the purpose of the nonfree platform is to introduce users thereof onto free protocols and to eventually exterminate the nonfree platform. Whenever these references to nonfree platforms appear, the author \fBMUST\fP present free methods of communication. Activists \fBSHOULD\fP pragmatically use as many of the popular free protocols as possible, to ensure that oppurtunities of introductions are not lost. In cases involving competition between free and nonfree protocols and platforms, ethical concerns (i.e. enabling talking to a new user on any ethical platform) \fBMUST\fP take precedence over technical concerns (such as disliking the XMPP protocol for its inefficent use of XML) whenever possible. + +.PP +Communities for introducing users to Free Software on nonfree platforms \fBMUST\fP be bridged to a free protocol in some obvious way, in order to minimize the usage of nonfree platforms even for the purpose of communicating ideology to new users and allow members of the Free Software community refusing to use nonfree platforms in any way to participate. Usages of nonfree platforms, besides part of the user-introduction process that must happen on the nonfree platform, \fBSHOULD\fP be avoided. + +.PP +For example, the author created a Discord Guild called Free Software Introductions, which is one-way-puppeted to #fsi on irc.andrewyu.org, which is then one-way-puppeted to Libera. The relay system is sort-of messed up, but it's working. Inviting new users to it via https://discord.gg/7CYp7ntww7 +\[la]https://discord.gg/7CYp7ntww7\[ra] is good, but as the author has made his own sacrifice already, there exists no need for other existing Free Software activists to join and use it instead of IRC. + +.SH "TECHNICAL LIMITATIONS" +.PP +The old and centralized nature of IRC, the insane 3PID recommendation of Matrix, the bad routing and efficency of XMPP, and the lack of documentation on PSYC, has led us to develop a new protocol, Internet Delay Chat[IDC], which aims to be free, modern (i.e. support for channel groups and shared permission sets, non-text data with MIME types), sane (i.e. TCP, UDP and SCTP-based, instead of HTTP POST APIs) and simple. + +.SH "CONCLUSION" +.PP +Hi + +.SH "FSF CONSIDERATIONS" +.PP +Hi + +.SH "BIBLIOGRAPHY" +.TP +[IDC] +Andrew Yu +The Second School Affiliated to Fudan University +Internet Delay Chat +\[la]https://git.andrewyu.org/internet-delay-chat\[ra]2022 + +.TP +[RMSGP] +Richard Stallman +The GNU Project +Is It Ever a Good Thing to Use a Nonfree Program? +\[la]http://www.gnu.org/philosophy/is-ever-good-use-nonfree-program.en.html\[ra]2013 + + +.SH "ACKNOWLEDGEMENTS"<!--77uuMany thanks to iShareFreedom, qrpnxz, DiffieHellman, Leah Rowe and many others for the ideas (and rebutted arguments) in this article.--> +.SH "CONTRIBUTORS" +.PP +Many thanks to everyone in the Free Software community for the freedom we have today. + +.SH "AUTHORS" +.PP +Written by Andrew Yu. + diff --git a/pragmatics/pragmatics.html b/pragmatics/pragmatics.html new file mode 100644 index 0000000..e1fadff --- /dev/null +++ b/pragmatics/pragmatics.html @@ -0,0 +1,1390 @@ +<!DOCTYPE html> +<html lang="en" class="Internet-Draft"> +<head> +<meta charset="utf-8"> +<meta content="Common,Latin" name="scripts"> +<meta content="initial-scale=1.0" name="viewport"> +<title>Pragmatic Use of Nonfree Software</title> +<meta content="Andrew Yu" name="author"> +<meta content=" + Free Software is undoubtably a good thing for society. However, modern computer users are stuck in the proprietary "ecosystem" for historical reasons. This document describes the author's viewpoint of using proprietary platforms to spread the ideas of Free Software. + " name="description"> +<meta content="xml2rfc 3.12.4" name="generator"> +<meta content="Nonfree" name="keyword"> +<meta content="Pragmatics" name="keyword"> +<meta content="Request for Discussions 1" name="ietf.draft"> +<!-- Generator version information: + xml2rfc 3.12.4 + Python 3.9.2 + appdirs 1.4.4 + ConfigArgParse 1.2.3 + google-i18n-address 2.5.0 + html5lib 1.1 + intervaltree 3.1.0 + Jinja2 2.11.3 + kitchen 1.2.6 + lxml 4.8.0 + MarkupSafe 2.0.1 + pycountry 22.3.5 + pyflakes 2.4.0 + PyYAML 6.0 + requests 2.25.1 + setuptools 52.0.0 + six 1.16.0 +--> +<link href="pragmatics.xml" rel="alternate" type="application/rfc+xml"> +<link href="#copyright" rel="license"> +<style type="text/css">/* + + NOTE: Changes at the bottom of this file overrides some earlier settings. + + Once the style has stabilized and has been adopted as an official RFC style, + this can be consolidated so that style settings occur only in one place, but + for now the contents of this file consists first of the initial CSS work as + provided to the RFC Formatter (xml2rfc) work, followed by itemized and + commented changes found necssary during the development of the v3 + formatters. + +*/ + +/* fonts */ +@import url('https://fonts.googleapis.com/css?family=Noto+Sans'); /* Sans-serif */ +@import url('https://fonts.googleapis.com/css?family=Noto+Serif'); /* Serif (print) */ +@import url('https://fonts.googleapis.com/css?family=Roboto+Mono'); /* Monospace */ + +@viewport { + zoom: 1.0; + width: extend-to-zoom; +} +@-ms-viewport { + width: extend-to-zoom; + zoom: 1.0; +} +/* general and mobile first */ +html { +} +body { + max-width: 90%; + margin: 1.5em auto; + color: #222; + background-color: #fff; + font-size: 14px; + font-family: 'Noto Sans', Arial, Helvetica, sans-serif; + line-height: 1.6; + scroll-behavior: smooth; +} +.ears { + display: none; +} + +/* headings */ +#title, h1, h2, h3, h4, h5, h6 { + margin: 1em 0 0.5em; + font-weight: bold; + line-height: 1.3; +} +#title { + clear: both; + border-bottom: 1px solid #ddd; + margin: 0 0 0.5em 0; + padding: 1em 0 0.5em; +} +.author { + padding-bottom: 4px; +} +h1 { + font-size: 26px; + margin: 1em 0; +} +h2 { + font-size: 22px; + margin-top: -20px; /* provide offset for in-page anchors */ + padding-top: 33px; +} +h3 { + font-size: 18px; + margin-top: -36px; /* provide offset for in-page anchors */ + padding-top: 42px; +} +h4 { + font-size: 16px; + margin-top: -36px; /* provide offset for in-page anchors */ + padding-top: 42px; +} +h5, h6 { + font-size: 14px; +} +#n-copyright-notice { + border-bottom: 1px solid #ddd; + padding-bottom: 1em; + margin-bottom: 1em; +} +/* general structure */ +p { + padding: 0; + margin: 0 0 1em 0; + text-align: left; +} +div, span { + position: relative; +} +div { + margin: 0; +} +.alignRight.art-text { + background-color: #f9f9f9; + border: 1px solid #eee; + border-radius: 3px; + padding: 1em 1em 0; + margin-bottom: 1.5em; +} +.alignRight.art-text pre { + padding: 0; +} +.alignRight { + margin: 1em 0; +} +.alignRight > *:first-child { + border: none; + margin: 0; + float: right; + clear: both; +} +.alignRight > *:nth-child(2) { + clear: both; + display: block; + border: none; +} +svg { + display: block; +} +.alignCenter.art-text { + background-color: #f9f9f9; + border: 1px solid #eee; + border-radius: 3px; + padding: 1em 1em 0; + margin-bottom: 1.5em; +} +.alignCenter.art-text pre { + padding: 0; +} +.alignCenter { + margin: 1em 0; +} +.alignCenter > *:first-child { + border: none; + /* this isn't optimal, but it's an existence proof. PrinceXML doesn't + support flexbox yet. + */ + display: table; + margin: 0 auto; +} + +/* lists */ +ol, ul { + padding: 0; + margin: 0 0 1em 2em; +} +ol ol, ul ul, ol ul, ul ol { + margin-left: 1em; +} +li { + margin: 0 0 0.25em 0; +} +.ulCompact li { + margin: 0; +} +ul.empty, .ulEmpty { + list-style-type: none; +} +ul.empty li, .ulEmpty li { + margin-top: 0.5em; +} +ul.ulBare, li.ulBare { + margin-left: 0em !important; +} +ul.compact, .ulCompact, +ol.compact, .olCompact { + line-height: 100%; + margin: 0 0 0 2em; +} + +/* definition lists */ +dl { +} +dl > dt { + float: left; + margin-right: 1em; +} +/* +dl.nohang > dt { + float: none; +} +*/ +dl > dd { + margin-bottom: .8em; + min-height: 1.3em; +} +dl.compact > dd, .dlCompact > dd { + margin-bottom: 0em; +} +dl > dd > dl { + margin-top: 0.5em; + margin-bottom: 0em; +} + +/* links */ +a { + text-decoration: none; +} +a[href] { + color: #22e; /* Arlen: WCAG 2019 */ +} +a[href]:hover { + background-color: #f2f2f2; +} +figcaption a[href], +a[href].selfRef { + color: #222; +} +/* XXX probably not this: +a.selfRef:hover { + background-color: transparent; + cursor: default; +} */ + +/* Figures */ +tt, code, pre, code { + background-color: #f9f9f9; + font-family: 'Roboto Mono', monospace; +} +pre { + border: 1px solid #eee; + margin: 0; + padding: 1em; +} +img { + max-width: 100%; +} +figure { + margin: 0; +} +figure blockquote { + margin: 0.8em 0.4em 0.4em; +} +figcaption { + font-style: italic; + margin: 0 0 1em 0; +} +@media screen { + pre { + overflow-x: auto; + max-width: 100%; + max-width: calc(100% - 22px); + } +} + +/* aside, blockquote */ +aside, blockquote { + margin-left: 0; + padding: 1.2em 2em; +} +blockquote { + background-color: #f9f9f9; + color: #111; /* Arlen: WCAG 2019 */ + border: 1px solid #ddd; + border-radius: 3px; + margin: 1em 0; +} +cite { + display: block; + text-align: right; + font-style: italic; +} + +/* tables */ +table { + width: 100%; + margin: 0 0 1em; + border-collapse: collapse; + border: 1px solid #eee; +} +th, td { + text-align: left; + vertical-align: top; + padding: 0.5em 0.75em; +} +th { + text-align: left; + background-color: #e9e9e9; +} +tr:nth-child(2n+1) > td { + background-color: #f5f5f5; +} +table caption { + font-style: italic; + margin: 0; + padding: 0; + text-align: left; +} +table p { + /* XXX to avoid bottom margin on table row signifiers. If paragraphs should + be allowed within tables more generally, it would be far better to select on a class. */ + margin: 0; +} + +/* pilcrow */ +a.pilcrow { + color: #666; /* Arlen: AHDJ 2019 */ + text-decoration: none; + visibility: hidden; + user-select: none; + -ms-user-select: none; + -o-user-select:none; + -moz-user-select: none; + -khtml-user-select: none; + -webkit-user-select: none; + -webkit-touch-callout: none; +} +@media screen { + aside:hover > a.pilcrow, + p:hover > a.pilcrow, + blockquote:hover > a.pilcrow, + div:hover > a.pilcrow, + li:hover > a.pilcrow, + pre:hover > a.pilcrow { + visibility: visible; + } + a.pilcrow:hover { + background-color: transparent; + } +} + +/* misc */ +hr { + border: 0; + border-top: 1px solid #eee; +} +.bcp14 { + font-variant: small-caps; +} + +.role { + font-variant: all-small-caps; +} + +/* info block */ +#identifiers { + margin: 0; + font-size: 0.9em; +} +#identifiers dt { + width: 3em; + clear: left; +} +#identifiers dd { + float: left; + margin-bottom: 0; +} +/* Fix PDF info block run off issue */ +@media print { + #identifiers dd { + float: none; + } +} +#identifiers .authors .author { + display: inline-block; + margin-right: 1.5em; +} +#identifiers .authors .org { + font-style: italic; +} + +/* The prepared/rendered info at the very bottom of the page */ +.docInfo { + color: #666; /* Arlen: WCAG 2019 */ + font-size: 0.9em; + font-style: italic; + margin-top: 2em; +} +.docInfo .prepared { + float: left; +} +.docInfo .prepared { + float: right; +} + +/* table of contents */ +#toc { + padding: 0.75em 0 2em 0; + margin-bottom: 1em; +} +nav.toc ul { + margin: 0 0.5em 0 0; + padding: 0; + list-style: none; +} +nav.toc li { + line-height: 1.3em; + margin: 0.75em 0; + padding-left: 1.2em; + text-indent: -1.2em; +} +/* references */ +.references dt { + text-align: right; + font-weight: bold; + min-width: 7em; +} +.references dd { + margin-left: 8em; + overflow: auto; +} + +.refInstance { + margin-bottom: 1.25em; +} + +.references .ascii { + margin-bottom: 0.25em; +} + +/* index */ +.index ul { + margin: 0 0 0 1em; + padding: 0; + list-style: none; +} +.index ul ul { + margin: 0; +} +.index li { + margin: 0; + text-indent: -2em; + padding-left: 2em; + padding-bottom: 5px; +} +.indexIndex { + margin: 0.5em 0 1em; +} +.index a { + font-weight: 700; +} +/* make the index two-column on all but the smallest screens */ +@media (min-width: 600px) { + .index ul { + -moz-column-count: 2; + -moz-column-gap: 20px; + } + .index ul ul { + -moz-column-count: 1; + -moz-column-gap: 0; + } +} + +/* authors */ +address.vcard { + font-style: normal; + margin: 1em 0; +} + +address.vcard .nameRole { + font-weight: 700; + margin-left: 0; +} +address.vcard .label { + font-family: "Noto Sans",Arial,Helvetica,sans-serif; + margin: 0.5em 0; +} +address.vcard .type { + display: none; +} +.alternative-contact { + margin: 1.5em 0 1em; +} +hr.addr { + border-top: 1px dashed; + margin: 0; + color: #ddd; + max-width: calc(100% - 16px); +} + +/* temporary notes */ +.rfcEditorRemove::before { + position: absolute; + top: 0.2em; + right: 0.2em; + padding: 0.2em; + content: "The RFC Editor will remove this note"; + color: #9e2a00; /* Arlen: WCAG 2019 */ + background-color: #ffd; /* Arlen: WCAG 2019 */ +} +.rfcEditorRemove { + position: relative; + padding-top: 1.8em; + background-color: #ffd; /* Arlen: WCAG 2019 */ + border-radius: 3px; +} +.cref { + background-color: #ffd; /* Arlen: WCAG 2019 */ + padding: 2px 4px; +} +.crefSource { + font-style: italic; +} +/* alternative layout for smaller screens */ +@media screen and (max-width: 1023px) { + body { + padding-top: 2em; + } + #title { + padding: 1em 0; + } + h1 { + font-size: 24px; + } + h2 { + font-size: 20px; + margin-top: -18px; /* provide offset for in-page anchors */ + padding-top: 38px; + } + #identifiers dd { + max-width: 60%; + } + #toc { + position: fixed; + z-index: 2; + top: 0; + right: 0; + padding: 0; + margin: 0; + background-color: inherit; + border-bottom: 1px solid #ccc; + } + #toc h2 { + margin: -1px 0 0 0; + padding: 4px 0 4px 6px; + padding-right: 1em; + min-width: 190px; + font-size: 1.1em; + text-align: right; + background-color: #444; + color: white; + cursor: pointer; + } + #toc h2::before { /* css hamburger */ + float: right; + position: relative; + width: 1em; + height: 1px; + left: -164px; + margin: 6px 0 0 0; + background: white none repeat scroll 0 0; + box-shadow: 0 4px 0 0 white, 0 8px 0 0 white; + content: ""; + } + #toc nav { + display: none; + padding: 0.5em 1em 1em; + overflow: auto; + height: calc(100vh - 48px); + border-left: 1px solid #ddd; + } +} + +/* alternative layout for wide screens */ +@media screen and (min-width: 1024px) { + body { + max-width: 724px; + margin: 42px auto; + padding-left: 1.5em; + padding-right: 29em; + } + #toc { + position: fixed; + top: 42px; + right: 42px; + width: 25%; + margin: 0; + padding: 0 1em; + z-index: 1; + } + #toc h2 { + border-top: none; + border-bottom: 1px solid #ddd; + font-size: 1em; + font-weight: normal; + margin: 0; + padding: 0.25em 1em 1em 0; + } + #toc nav { + display: block; + height: calc(90vh - 84px); + bottom: 0; + padding: 0.5em 0 0; + overflow: auto; + } + img { /* future proofing */ + max-width: 100%; + height: auto; + } +} + +/* pagination */ +@media print { + body { + + width: 100%; + } + p { + orphans: 3; + widows: 3; + } + #n-copyright-notice { + border-bottom: none; + } + #toc, #n-introduction { + page-break-before: always; + } + #toc { + border-top: none; + padding-top: 0; + } + figure, pre { + page-break-inside: avoid; + } + figure { + overflow: scroll; + } + h1, h2, h3, h4, h5, h6 { + page-break-after: avoid; + } + h2+*, h3+*, h4+*, h5+*, h6+* { + page-break-before: avoid; + } + pre { + white-space: pre-wrap; + word-wrap: break-word; + font-size: 10pt; + } + table { + border: 1px solid #ddd; + } + td { + border-top: 1px solid #ddd; + } +} + +/* This is commented out here, as the string-set: doesn't + pass W3C validation currently */ +/* +.ears thead .left { + string-set: ears-top-left content(); +} + +.ears thead .center { + string-set: ears-top-center content(); +} + +.ears thead .right { + string-set: ears-top-right content(); +} + +.ears tfoot .left { + string-set: ears-bottom-left content(); +} + +.ears tfoot .center { + string-set: ears-bottom-center content(); +} + +.ears tfoot .right { + string-set: ears-bottom-right content(); +} +*/ + +@page :first { + padding-top: 0; + @top-left { + content: normal; + border: none; + } + @top-center { + content: normal; + border: none; + } + @top-right { + content: normal; + border: none; + } +} + +@page { + size: A4; + margin-bottom: 45mm; + padding-top: 20px; + /* The follwing is commented out here, but set appropriately by in code, as + the content depends on the document */ + /* + @top-left { + content: 'Internet-Draft'; + vertical-align: bottom; + border-bottom: solid 1px #ccc; + } + @top-left { + content: string(ears-top-left); + vertical-align: bottom; + border-bottom: solid 1px #ccc; + } + @top-center { + content: string(ears-top-center); + vertical-align: bottom; + border-bottom: solid 1px #ccc; + } + @top-right { + content: string(ears-top-right); + vertical-align: bottom; + border-bottom: solid 1px #ccc; + } + @bottom-left { + content: string(ears-bottom-left); + vertical-align: top; + border-top: solid 1px #ccc; + } + @bottom-center { + content: string(ears-bottom-center); + vertical-align: top; + border-top: solid 1px #ccc; + } + @bottom-right { + content: '[Page ' counter(page) ']'; + vertical-align: top; + border-top: solid 1px #ccc; + } + */ + +} + +/* Changes introduced to fix issues found during implementation */ +/* Make sure links are clickable even if overlapped by following H* */ +a { + z-index: 2; +} +/* Separate body from document info even without intervening H1 */ +section { + clear: both; +} + + +/* Top align author divs, to avoid names without organization dropping level with org names */ +.author { + vertical-align: top; +} + +/* Leave room in document info to show Internet-Draft on one line */ +#identifiers dt { + width: 8em; +} + +/* Don't waste quite as much whitespace between label and value in doc info */ +#identifiers dd { + margin-left: 1em; +} + +/* Give floating toc a background color (needed when it's a div inside section */ +#toc { + background-color: white; +} + +/* Make the collapsed ToC header render white on gray also when it's a link */ +@media screen and (max-width: 1023px) { + #toc h2 a, + #toc h2 a:link, + #toc h2 a:focus, + #toc h2 a:hover, + #toc a.toplink, + #toc a.toplink:hover { + color: white; + background-color: #444; + text-decoration: none; + } +} + +/* Give the bottom of the ToC some whitespace */ +@media screen and (min-width: 1024px) { + #toc { + padding: 0 0 1em 1em; + } +} + +/* Style section numbers with more space between number and title */ +.section-number { + padding-right: 0.5em; +} + +/* prevent monospace from becoming overly large */ +tt, code, pre, code { + font-size: 95%; +} + +/* Fix the height/width aspect for ascii art*/ +pre.sourcecode, +.art-text pre { + line-height: 1.12; +} + + +/* Add styling for a link in the ToC that points to the top of the document */ +a.toplink { + float: right; + margin-right: 0.5em; +} + +/* Fix the dl styling to match the RFC 7992 attributes */ +dl > dt, +dl.dlParallel > dt { + float: left; + margin-right: 1em; +} +dl.dlNewline > dt { + float: none; +} + +/* Provide styling for table cell text alignment */ +table td.text-left, +table th.text-left { + text-align: left; +} +table td.text-center, +table th.text-center { + text-align: center; +} +table td.text-right, +table th.text-right { + text-align: right; +} + +/* Make the alternative author contact informatio look less like just another + author, and group it closer with the primary author contact information */ +.alternative-contact { + margin: 0.5em 0 0.25em 0; +} +address .non-ascii { + margin: 0 0 0 2em; +} + +/* With it being possible to set tables with alignment + left, center, and right, { width: 100%; } does not make sense */ +table { + width: auto; +} + +/* Avoid reference text that sits in a block with very wide left margin, + because of a long floating dt label.*/ +.references dd { + overflow: visible; +} + +/* Control caption placement */ +caption { + caption-side: bottom; +} + +/* Limit the width of the author address vcard, so names in right-to-left + script don't end up on the other side of the page. */ + +address.vcard { + max-width: 30em; + margin-right: auto; +} + +/* For address alignment dependent on LTR or RTL scripts */ +address div.left { + text-align: left; +} +address div.right { + text-align: right; +} + +/* Provide table alignment support. We can't use the alignX classes above + since they do unwanted things with caption and other styling. */ +table.right { + margin-left: auto; + margin-right: 0; +} +table.center { + margin-left: auto; + margin-right: auto; +} +table.left { + margin-left: 0; + margin-right: auto; +} + +/* Give the table caption label the same styling as the figcaption */ +caption a[href] { + color: #222; +} + +@media print { + .toplink { + display: none; + } + + /* avoid overwriting the top border line with the ToC header */ + #toc { + padding-top: 1px; + } + + /* Avoid page breaks inside dl and author address entries */ + .vcard { + page-break-inside: avoid; + } + +} +/* Tweak the bcp14 keyword presentation */ +.bcp14 { + font-variant: small-caps; + font-weight: bold; + font-size: 0.9em; +} +/* Tweak the invisible space above H* in order not to overlay links in text above */ + h2 { + margin-top: -18px; /* provide offset for in-page anchors */ + padding-top: 31px; + } + h3 { + margin-top: -18px; /* provide offset for in-page anchors */ + padding-top: 24px; + } + h4 { + margin-top: -18px; /* provide offset for in-page anchors */ + padding-top: 24px; + } +/* Float artwork pilcrow to the right */ +@media screen { + .artwork a.pilcrow { + display: block; + line-height: 0.7; + margin-top: 0.15em; + } +} +/* Make pilcrows on dd visible */ +@media screen { + dd:hover > a.pilcrow { + visibility: visible; + } +} +/* Make the placement of figcaption match that of a table's caption + by removing the figure's added bottom margin */ +.alignLeft.art-text, +.alignCenter.art-text, +.alignRight.art-text { + margin-bottom: 0; +} +.alignLeft, +.alignCenter, +.alignRight { + margin: 1em 0 0 0; +} +/* In print, the pilcrow won't show on hover, so prevent it from taking up space, + possibly even requiring a new line */ +@media print { + a.pilcrow { + display: none; + } +} +/* Styling for the external metadata */ +div#external-metadata { + background-color: #eee; + padding: 0.5em; + margin-bottom: 0.5em; + display: none; +} +div#internal-metadata { + padding: 0.5em; /* to match the external-metadata padding */ +} +/* Styling for title RFC Number */ +h1#rfcnum { + clear: both; + margin: 0 0 -1em; + padding: 1em 0 0 0; +} +/* Make .olPercent look the same as <ol><li> */ +dl.olPercent > dd { + margin-bottom: 0.25em; + min-height: initial; +} +/* Give aside some styling to set it apart */ +aside { + border-left: 1px solid #ddd; + margin: 1em 0 1em 2em; + padding: 0.2em 2em; +} +aside > dl, +aside > ol, +aside > ul, +aside > table, +aside > p { + margin-bottom: 0.5em; +} +/* Additional page break settings */ +@media print { + figcaption, table caption { + page-break-before: avoid; + } +} +/* Font size adjustments for print */ +@media print { + body { font-size: 10pt; line-height: normal; max-width: 96%; } + h1 { font-size: 1.72em; padding-top: 1.5em; } /* 1*1.2*1.2*1.2 */ + h2 { font-size: 1.44em; padding-top: 1.5em; } /* 1*1.2*1.2 */ + h3 { font-size: 1.2em; padding-top: 1.5em; } /* 1*1.2 */ + h4 { font-size: 1em; padding-top: 1.5em; } + h5, h6 { font-size: 1em; margin: initial; padding: 0.5em 0 0.3em; } +} +/* Sourcecode margin in print, when there's no pilcrow */ +@media print { + .artwork, + .sourcecode { + margin-bottom: 1em; + } +} +/* Avoid narrow tables forcing too narrow table captions, which may render badly */ +table { + min-width: 20em; +} +/* ol type a */ +ol.type-a { list-style-type: lower-alpha; } +ol.type-A { list-style-type: upper-alpha; } +ol.type-i { list-style-type: lower-roman; } +ol.type-I { list-style-type: lower-roman; } +/* Apply the print table and row borders in general, on request from the RPC, +and increase the contrast between border and odd row background sligthtly */ +table { + border: 1px solid #ddd; +} +td { + border-top: 1px solid #ddd; +} +tr:nth-child(2n+1) > td { + background-color: #f8f8f8; +} +/* Use style rules to govern display of the TOC. */ +@media screen and (max-width: 1023px) { + #toc nav { display: none; } + #toc.active nav { display: block; } +} +/* Add support for keepWithNext */ +.keepWithNext { + break-after: avoid-page; + break-after: avoid-page; +} +/* Add support for keepWithPrevious */ +.keepWithPrevious { + break-before: avoid-page; +} +/* Change the approach to avoiding breaks inside artwork etc. */ +figure, pre, table, .artwork, .sourcecode { + break-before: auto; + break-after: auto; +} +/* Avoid breaks between <dt> and <dd> */ +dl { + break-before: auto; + break-inside: auto; +} +dt { + break-before: auto; + break-after: avoid-page; +} +dd { + break-before: avoid-page; + break-after: auto; + orphans: 3; + widows: 3 +} +span.break, dd.break { + margin-bottom: 0; + min-height: 0; + break-before: auto; + break-inside: auto; + break-after: auto; +} +/* Undo break-before ToC */ +@media print { + #toc { + break-before: auto; + } +} +/* Text in compact lists should not get extra bottim margin space, + since that would makes the list not compact */ +ul.compact p, .ulCompact p, +ol.compact p, .olCompact p { + margin: 0; +} +/* But the list as a whole needs the extra space at the end */ +section ul.compact, +section .ulCompact, +section ol.compact, +section .olCompact { + margin-bottom: 1em; /* same as p not within ul.compact etc. */ +} +/* The tt and code background above interferes with for instance table cell + backgrounds. Changed to something a bit more selective. */ +tt, code { + background-color: transparent; +} +p tt, p code, li tt, li code { + background-color: #f8f8f8; +} +/* Tweak the pre margin -- 0px doesn't come out well */ +pre { + margin-top: 0.5px; +} +/* Tweak the comact list text */ +ul.compact, .ulCompact, +ol.compact, .olCompact, +dl.compact, .dlCompact { + line-height: normal; +} +/* Don't add top margin for nested lists */ +li > ul, li > ol, li > dl, +dd > ul, dd > ol, dd > dl, +dl > dd > dl { + margin-top: initial; +} +/* Elements that should not be rendered on the same line as a <dt> */ +/* This should match the element list in writer.text.TextWriter.render_dl() */ +dd > div.artwork:first-child, +dd > aside:first-child, +dd > figure:first-child, +dd > ol:first-child, +dd > div:first-child > pre.sourcecode, +dd > table:first-child, +dd > ul:first-child { + clear: left; +} +/* fix for weird browser behaviour when <dd/> is empty */ +dt+dd:empty::before{ + content: "\00a0"; +} +/* Make paragraph spacing inside <li> smaller than in body text, to fit better within the list */ +li > p { + margin-bottom: 0.5em +} +/* Don't let p margin spill out from inside list items */ +li > p:last-of-type { + margin-bottom: 0; +} +</style> +<link href="rfc-local.css" rel="stylesheet" type="text/css"> +<script type="application/javascript">async function addMetadata(){try{const e=document.styleSheets[0].cssRules;for(let t=0;t<e.length;t++)if(/#identifiers/.exec(e[t].selectorText)){const a=e[t].cssText.replace("#identifiers","#external-updates");document.styleSheets[0].insertRule(a,document.styleSheets[0].cssRules.length)}}catch(e){console.log(e)}const e=document.getElementById("external-metadata");if(e)try{var t,a="",o=function(e){const t=document.getElementsByTagName("meta");for(let a=0;a<t.length;a++)if(t[a].getAttribute("name")===e)return t[a].getAttribute("content");return""}("rfc.number");if(o){t="https://www.rfc-editor.org/rfc/rfc"+o+".json";try{const e=await fetch(t);a=await e.json()}catch(e){t=document.URL.indexOf("html")>=0?document.URL.replace(/html$/,"json"):document.URL+".json";const o=await fetch(t);a=await o.json()}}if(!a)return;e.style.display="block";const s="",d="https://datatracker.ietf.org/doc",n="https://datatracker.ietf.org/ipr/search",c="https://www.rfc-editor.org/info",l=a.doc_id.toLowerCase(),i=a.doc_id.slice(0,3).toLowerCase(),f=a.doc_id.slice(3).replace(/^0+/,""),u={status:"Status",obsoletes:"Obsoletes",obsoleted_by:"Obsoleted By",updates:"Updates",updated_by:"Updated By",see_also:"See Also",errata_url:"Errata"};let h="<dl style='overflow:hidden' id='external-updates'>";["status","obsoletes","obsoleted_by","updates","updated_by","see_also","errata_url"].forEach(e=>{if("status"==e){a[e]=a[e].toLowerCase();var t=a[e].split(" "),o=t.length,w="",p=1;for(let e=0;e<o;e++)p<o?w=w+r(t[e])+" ":w+=r(t[e]),p++;a[e]=w}else if("obsoletes"==e||"obsoleted_by"==e||"updates"==e||"updated_by"==e){var g,m="",b=1;g=a[e].length;for(let t=0;t<g;t++)a[e][t]&&(a[e][t]=String(a[e][t]).toLowerCase(),m=b<g?m+"<a href='"+s+"/rfc/".concat(a[e][t])+"'>"+a[e][t].slice(3)+"</a>, ":m+"<a href='"+s+"/rfc/".concat(a[e][t])+"'>"+a[e][t].slice(3)+"</a>",b++);a[e]=m}else if("see_also"==e){var y,L="",C=1;y=a[e].length;for(let t=0;t<y;t++)if(a[e][t]){a[e][t]=String(a[e][t]);var _=a[e][t].slice(0,3),v=a[e][t].slice(3).replace(/^0+/,"");L=C<y?"RFC"!=_?L+"<a href='"+s+"/info/"+_.toLowerCase().concat(v.toLowerCase())+"'>"+_+" "+v+"</a>, ":L+"<a href='"+s+"/info/"+_.toLowerCase().concat(v.toLowerCase())+"'>"+v+"</a>, ":"RFC"!=_?L+"<a href='"+s+"/info/"+_.toLowerCase().concat(v.toLowerCase())+"'>"+_+" "+v+"</a>":L+"<a href='"+s+"/info/"+_.toLowerCase().concat(v.toLowerCase())+"'>"+v+"</a>",C++}a[e]=L}else if("errata_url"==e){var R="";R=a[e]?R+"<a href='"+a[e]+"'>Errata exist</a> | <a href='"+d+"/"+l+"'>Datatracker</a>| <a href='"+n+"/?"+i+"="+f+"&submit="+i+"'>IPR</a> | <a href='"+c+"/"+l+"'>Info page</a>":"<a href='"+d+"/"+l+"'>Datatracker</a> | <a href='"+n+"/?"+i+"="+f+"&submit="+i+"'>IPR</a> | <a href='"+c+"/"+l+"'>Info page</a>",a[e]=R}""!=a[e]?"Errata"==u[e]?h+=`<dt>More info:</dt><dd>${a[e]}</dd>`:h+=`<dt>${u[e]}:</dt><dd>${a[e]}</dd>`:"Errata"==u[e]&&(h+=`<dt>More info:</dt><dd>${a[e]}</dd>`)}),h+="</dl>",e.innerHTML=h}catch(e){console.log(e)}else console.log("Could not locate metadata <div> element");function r(e){return e.charAt(0).toUpperCase()+e.slice(1)}}window.removeEventListener("load",addMetadata),window.addEventListener("load",addMetadata);</script> +</head> +<body> +<script src="metadata.min.js"></script> +<table class="ears"> +<thead><tr> +<td class="left"></td> +<td class="center">Pragmatic Use of Nonfree Software</td> +<td class="right">April 2022</td> +</tr></thead> +<tfoot><tr> +<td class="left">Yu</td> +<td class="center">Informational</td> +<td class="right">[Page]</td> +</tr></tfoot> +</table> +<div id="external-metadata" class="document-information"></div> +<div id="internal-metadata" class="document-information"> +<dl id="identifiers"> +<dt class="label-workgroup">Workgroup:</dt> +<dd class="workgroup">Free Software Community</dd> +<dt class="label-authors">Author:</dt> +<dd class="authors"> +<div class="author"> + <div class="author-name">A. Yu</div> +<div class="org">The 2nd School Aff. to FDU</div> +</div> +</dd> +</dl> +</div> +<h1 id="title">Pragmatic Use of Nonfree Software</h1> +<section id="section-abstract"> + <h2 id="abstract"><a href="#abstract" class="selfRef">Abstract</a></h2> +<p id="section-abstract-1">Free Software is undoubtably a good thing for society. However, modern computer users are stuck in the proprietary "ecosystem" for historical reasons. This document describes the author's viewpoint of using proprietary platforms to spread the ideas of Free Software.<a href="#section-abstract-1" class="pilcrow">¶</a></p> +</section> +<section class="note" id="section-note.1"> + <h2 id="name-status-of-this-memo-2"> +<a href="#name-status-of-this-memo-2" class="section-name selfRef">Status of This Memo</a> + </h2> +<p id="section-note.1-1">This document is currently in the DRAFT status.<a href="#section-note.1-1" class="pilcrow">¶</a></p> +<p id="section-note.1-2">This document describes the author's viewpoint. This does not represent the ideas of the Free Software Foundation or any other entity. Distribution of this memo is unlimited.<a href="#section-note.1-2" class="pilcrow">¶</a></p> +</section> +<div id="toc"> +<section id="section-toc.1"> + <a href="#" onclick="scroll(0,0)" class="toplink">▲</a><h2 id="name-table-of-contents-2"> +<a href="#name-table-of-contents-2" class="section-name selfRef">Table of Contents</a> + </h2> +<nav class="toc"><ul class="compact toc ulBare ulEmpty"> +<li class="compact toc ulBare ulEmpty" id="section-toc.1-1.1"> + <p id="section-toc.1-1.1.1" class="keepWithNext"><a href="#section-1" class="xref">1</a>.  <a href="#name-introduction-2" class="xref">Introduction</a></p> +</li> + <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.2"> + <p id="section-toc.1-1.2.1" class="keepWithNext"><a href="#section-2" class="xref">2</a>.  <a href="#name-justification-2" class="xref">Justification</a></p> +</li> + <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.3"> + <p id="section-toc.1-1.3.1" class="keepWithNext"><a href="#section-3" class="xref">3</a>.  <a href="#name-action-procedure-2" class="xref">Action Procedure</a></p> +</li> + <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.4"> + <p id="section-toc.1-1.4.1"><a href="#section-4" class="xref">4</a>.  <a href="#name-technical-limitations-2" class="xref">Technical Limitations</a></p> +</li> + <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.5"> + <p id="section-toc.1-1.5.1"><a href="#section-5" class="xref">5</a>.  <a href="#name-conclusion-2" class="xref">Conclusion</a></p> +</li> + <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.6"> + <p id="section-toc.1-1.6.1"><a href="#section-6" class="xref">6</a>.  <a href="#name-fsf-considerations-2" class="xref">FSF Considerations</a></p> +</li> + <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.7"> + <p id="section-toc.1-1.7.1"><a href="#section-7" class="xref">7</a>.  <a href="#name-normative-references-2" class="xref">Normative References</a></p> +</li> + <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.8"> + <p id="section-toc.1-1.8.1"><a href="#appendix-A" class="xref"></a><a href="#name-acknowledgements-2" class="xref">Acknowledgements</a></p> +</li> + <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.9"> + <p id="section-toc.1-1.9.1"><a href="#appendix-B" class="xref"></a><a href="#name-contributors-2" class="xref">Contributors</a></p> +</li> + <li class="compact toc ulBare ulEmpty" id="section-toc.1-1.10"> + <p id="section-toc.1-1.10.1"><a href="#appendix-C" class="xref"></a><a href="#name-authors-address-2" class="xref">Author's Address</a></p> +</li> + </ul> +</nav> +</section> +</div> +<div id="introduction"> +<section id="section-1"> + <h2 id="name-introduction-2"> +<a href="#section-1" class="section-number selfRef">1. </a><a href="#name-introduction-2" class="section-name selfRef">Introduction</a> + </h2> +<p id="section-1-1">Readers of this memo probably understand the ideals of the Free Software Movement, and avoid proprietary software when possible. However, as most outsiders are unaware and are deeply buried inside the proprietary dystopia created by mostly multibillion-dollar technology coorporations, our methods of communicating with the masses are ineffective.<a href="#section-1-1" class="pilcrow">¶</a></p> +<p id="section-1-2">In February 2022, the author decided to adjust his dogma, and permitted limited usage of nonfree chat platforms to hopefully spread our ideas to the general public. This was attempted by registering a Discord account, creating a Guild called "Free Software Introductions", and setting up a basic Discord-to-IRC relay to #fsi on both irc.andrewyu.org and irc.libera.chat.<a href="#section-1-2" class="pilcrow">¶</a></p> +<p id="section-1-3">One of the communities that he knows about, the VF-Technic Minetest community, primarily uses Discord as a means of communication by plays not in-game. As the users inside are Minetest players, a Free Software voxel sandbox game, similar to but much more flexible and freedom-respecting than Minecraft, it is believed that the users have some contact with Free Software, although they might not understand the freedom part of the issue, i.e. they might be thinking in terms of "open source" instead. After sharing the invite link in the VF-Technic Guild, some people joined, and we've partially converted two users.<a href="#section-1-3" class="pilcrow">¶</a></p> +</section> +</div> +<div id="justification"> +<section id="section-2"> + <h2 id="name-justification-2"> +<a href="#section-2" class="section-number selfRef">2. </a><a href="#name-justification-2" class="section-name selfRef">Justification</a> + </h2> +<p id="section-2-1">Two users is definitely few, but it sets a start and an example for how freedom can be spread.<a href="#section-2-1" class="pilcrow">¶</a></p> +<p id="section-2-2">There are numerous free replacements to proprietary services such as Discord, such as Internet Relay Chat, the Extensible Messaging and Presense Protocol, the Matrix protocol, and email. As Free Software activists, we generally prefer these protocols over nonfree services. This section explains the reasons to consider nonfree services and protocols.<a href="#section-2-2" class="pilcrow">¶</a></p> +<p id="section-2-3">Generally, users on IRC and XMPP have a fair understanding of the Free Software Movement, and it is quick and easy to inform them what we mean by "free", "the four freedoms", and similar ideas. For users on the Libera Chat IRC network, which by far has the most users of any network, it is exceptionally easy to introduce a user into the #fsf channel for discussions with people supporting Free Software. Introducing ignorant users on these protocols and platforms are a day-to-day simple task.<a href="#section-2-3" class="pilcrow">¶</a></p> +<p id="section-2-4">Furthermore, the amount of users we can reach on these protocols are rather limiting. Libera has around forty thousand users according to the <code>USERS</code> command, and considering the fact that around 90% of these people aren't ignorant, there isn't much we can do.<a href="#section-2-4" class="pilcrow">¶</a></p> +<p id="section-2-5">Matrix users, in particular users of the matrix.org homeserver, typically know but don't completely understand Free Software. Rather than using Matrix IDs to identify users, the Matrix specification specifies that third-party platform identities, such as email and GitHub, are how users should be referenced both internally by servers and shown to other users. This is obviously an increadibly foolish idea, especially considering the use of centralized identity servers (similar to X509 certificate authorities) for 3PIDs. These are our first targets, but these should also be easy to get the idea across.<a href="#section-2-5" class="pilcrow">¶</a></p> +<p id="section-2-6">It is true that Libera Chat and similar IRC networks, though multi-centered in a technical way (i.e. multiple IRC servers form an IRC network), the network is politically centralized, controlled by one entity, Libera. The Internet Relay Chat server-to-server protocol implies that servers fully trust each other and are expected to not send damaging commands, which in turn implies full trust between server operators, no federation, and political centralization. The privacy policy and network policy of Libera Chat are in the author's opinion non-intrusive, therefore the use of which is acceptable and is promoted by the FSF. (Obviously, most methods of using IRC do not involve nonfree software.)<a href="#section-2-6" class="pilcrow">¶</a></p> +<p id="section-2-7">Nevertheless, those that have never touched Free Software are often on giant proprietary platforms, and take these as universal methods of communication. Many people go months before checking their mailbox (physical or electronic), refuse to use XMPP or IRC for its age.<a href="#section-2-7" class="pilcrow">¶</a></p> +<p id="section-2-8">An alternative protocol, Internet Delay Chat, is being developed.<a href="#section-2-8" class="pilcrow">¶</a></p> +<p id="section-2-9">There is one special case where using some nonfree software, and even urging others to use it, can be a positive thing. That's when the use of the nonfree software aims directly at putting an end to the use of that very same nonfree software.<span>[<a href="#RMSGP" class="xref">RMSGP</a>]</span> The author believes that the following fall within this scope:<a href="#section-2-9" class="pilcrow">¶</a></p> +<ul class="compact"> +<li class="compact" id="section-2-10.1">Developing a free program that requires nonfree environments to bootstrap;<a href="#section-2-10.1" class="pilcrow">¶</a> +</li> + <li class="compact" id="section-2-10.2">To spread awareness of software freedom issues to users in nonfree environments.<a href="#section-2-10.2" class="pilcrow">¶</a> +</li> + </ul> +<p id="section-2-11">As almost all types of programming can be done on most types of BSD and GNU operating systems, the author hasn't found any software that fit this category. Extending the interpretation allos for using nonfree software's behavior as a reference in Free Software development, though an arguable programming practice, may help the community to progress by understanding common features that users of nonfree services use.<a href="#section-2-11" class="pilcrow">¶</a></p> +<p id="section-2-12">The latter is more interesting, as explained above our methods of spreading awareness is limited.<a href="#section-2-12" class="pilcrow">¶</a></p> +</section> +</div> +<div id="action-procedure"> +<section id="section-3"> + <h2 id="name-action-procedure-2"> +<a href="#section-3" class="section-number selfRef">3. </a><a href="#name-action-procedure-2" class="section-name selfRef">Action Procedure</a> + </h2> +<p id="section-3-1">Activists <span class="bcp14">MUST NOT</span> list such nonfree services in "Contact Information" pages on their website or similar sources, unless followed by a explanation that the purpose of the nonfree platform is to introduce users thereof onto free protocols and to eventually exterminate the nonfree platform. Whenever these references to nonfree platforms appear, the author <span class="bcp14">MUST</span> present free methods of communication. Activists <span class="bcp14">SHOULD</span> pragmatically use as many of the popular free protocols as possible, to ensure that oppurtunities of introductions are not lost. In cases involving competition between free and nonfree protocols and platforms, ethical concerns (i.e. enabling talking to a new user on any ethical platform) <span class="bcp14">MUST</span> take precedence over technical concerns (such as disliking the XMPP protocol for its inefficent use of XML) whenever possible.<a href="#section-3-1" class="pilcrow">¶</a></p> +<p id="section-3-2">Communities for introducing users to Free Software on nonfree platforms <span class="bcp14">MUST</span> be bridged to a free protocol in some obvious way, in order to minimize the usage of nonfree platforms even for the purpose of communicating ideology to new users and allow members of the Free Software community refusing to use nonfree platforms in any way to participate. Usages of nonfree platforms, besides part of the user-introduction process that must happen on the nonfree platform, <span class="bcp14">SHOULD</span> be avoided.<a href="#section-3-2" class="pilcrow">¶</a></p> +<p id="section-3-3">For example, the author created a Discord Guild called Free Software Introductions, which is one-way-puppeted to #fsi on irc.andrewyu.org, which is then one-way-puppeted to Libera. The relay system is sort-of messed up, but it's working. Inviting new users to it via <a href="https://discord.gg/7CYp7ntww7">https://discord.gg/7CYp7ntww7</a> is good, but as the author has made his own sacrifice already, there exists no need for other existing Free Software activists to join and use it instead of IRC.<a href="#section-3-3" class="pilcrow">¶</a></p> +</section> +</div> +<div id="technical-limitations"> +<section id="section-4"> + <h2 id="name-technical-limitations-2"> +<a href="#section-4" class="section-number selfRef">4. </a><a href="#name-technical-limitations-2" class="section-name selfRef">Technical Limitations</a> + </h2> +<p id="section-4-1">The old and centralized nature of IRC, the insane 3PID recommendation of Matrix, the bad routing and efficency of XMPP, and the lack of documentation on PSYC, has led us to develop a new protocol, Internet Delay Chat<span>[<a href="#IDC" class="xref">IDC</a>]</span>, which aims to be free, modern (i.e. support for channel groups and shared permission sets, non-text data with MIME types), sane (i.e. TCP, UDP and SCTP-based, instead of HTTP POST APIs) and simple.<a href="#section-4-1" class="pilcrow">¶</a></p> +</section> +</div> +<div id="conclusion"> +<section id="section-5"> + <h2 id="name-conclusion-2"> +<a href="#section-5" class="section-number selfRef">5. </a><a href="#name-conclusion-2" class="section-name selfRef">Conclusion</a> + </h2> +<p id="section-5-1">Hi<a href="#section-5-1" class="pilcrow">¶</a></p> +</section> +</div> +<div id="fsf-considerations"> +<section id="section-6"> + <h2 id="name-fsf-considerations-2"> +<a href="#section-6" class="section-number selfRef">6. </a><a href="#name-fsf-considerations-2" class="section-name selfRef">FSF Considerations</a> + </h2> +<p id="section-6-1">Hi<a href="#section-6-1" class="pilcrow">¶</a></p> +</section> +</div> +<section id="section-7"> + <h2 id="name-normative-references-2"> +<a href="#section-7" class="section-number selfRef">7. </a><a href="#name-normative-references-2" class="section-name selfRef">Normative References</a> + </h2> +<dl class="references"> +<dt id="IDC">[IDC]</dt> + <dd> +<span class="refAuthor">Yu, A.</span>, <span class="refTitle">"Internet Delay Chat"</span>, <time datetime="2022-04" class="refDate">April 2022</time>, <span><<a href="https://git.andrewyu.org/internet-delay-chat">https://git.andrewyu.org/internet-delay-chat</a>></span>. </dd> +<dd class="break"></dd> +<dt id="RMSGP">[RMSGP]</dt> + <dd> +<span class="refAuthor">Stallman, R.</span>, <span class="refTitle">"Is It Ever a Good Thing to Use a Nonfree Program?"</span>, <time datetime="2013-09" class="refDate">September 2013</time>, <span><<a href="http://www.gnu.org/philosophy/is-ever-good-use-nonfree-program.en.html">http://www.gnu.org/philosophy/is-ever-good-use-nonfree-program.en.html</a>></span>. </dd> +<dd class="break"></dd> +</dl> +</section> +<div id="acknowledgements"> +<section id="appendix-A"> + <h2 id="name-acknowledgements-2"> +<a href="#name-acknowledgements-2" class="section-name selfRef">Acknowledgements</a> + </h2> +</section> +</div> +<div id="contributors"> +<section id="appendix-B"> + <h2 id="name-contributors-2"> +<a href="#name-contributors-2" class="section-name selfRef">Contributors</a> + </h2> +<p id="appendix-B-1">Many thanks to everyone in the Free Software community for the freedom we have today.<a href="#appendix-B-1" class="pilcrow">¶</a></p> +</section> +</div> +<div id="authors-addresses"> +<section id="appendix-C"> + <h2 id="name-authors-address-2"> +<a href="#name-authors-address-2" class="section-name selfRef">Author's Address</a> + </h2> +<address class="vcard"> + <div dir="auto" class="left"><span class="fn nameRole">Andrew Yu</span></div> +<div dir="auto" class="left"><span class="org">The 2nd School Aff. to FDU</span></div> +<div class="email"> +<span>Email:</span> +<a href="mailto:andrew@andrewyu.org" class="email">andrew@andrewyu.org</a> +</div> +<div class="url"> +<span>URI:</span> +<a href="https://www.andrewyu.org/" class="url">https://www.andrewyu.org/</a> +</div> +</address> +</section> +</div> +<script>const toc = document.getElementById("toc"); +toc.querySelector("h2").addEventListener("click", e => { + toc.classList.toggle("active"); +}); +toc.querySelector("nav").addEventListener("click", e => { + toc.classList.remove("active"); +}); +</script> +</body> +</html> diff --git a/pragmatics/pragmatics.man b/pragmatics/pragmatics.man new file mode 100644 index 0000000..c3dba40 --- /dev/null +++ b/pragmatics/pragmatics.man @@ -0,0 +1,215 @@ +PRAGMATIC USE OF NONFREE SOFTFWrAeReE(S1o)ftware CPoRmAmGuMnAiTtIyC USE OF NONFREE SOFTWARE(1) + + + +AABBSSTTRRAACCTT + Free Software is undoubtably a good thing for society. However, modern + computer users are stuck in the proprietary "ecosystem" for historical + reasons. This document describes the author's viewpoint of using pro- + prietary platforms to spread the ideas of Free Software. + + +SSTTAATTUUSS OOFF TTHHIISS MMEEMMOO + This document is currently in the DRAFT status. + + + This document describes the author's viewpoint. This does not repre- + sent the ideas of the Free Software Foundation or any other entity. + Distribution of this memo is unlimited. + + +IINNTTRROODDUUCCTTIIOONN + Readers of this memo probably understand the ideals of the Free Soft- + ware Movement, and avoid proprietary software when possible. However, + as most outsiders are unaware and are deeply buried inside the propri- + etary dystopia created by mostly multibillion-dollar technology coorpo- + rations, our methods of communicating with the masses are ineffective. + + + In February 2022, the author decided to adjust his dogma, and permitted + limited usage of nonfree chat platforms to hopefully spread our ideas + to the general public. This was attempted by registering a Discord ac- + count, creating a Guild called "Free Software Introductions", and set- + ting up a basic Discord-to-IRC relay to #fsi on both irc.andrewyu.org + and irc.libera.chat. + + + One of the communities that he knows about, the VF-Technic Minetest + community, primarily uses Discord as a means of communication by plays + not in-game. As the users inside are Minetest players, a Free Software + voxel sandbox game, similar to but much more flexible and freedom-re- + specting than Minecraft, it is believed that the users have some con- + tact with Free Software, although they might not understand the freedom + part of the issue, i.e. they might be thinking in terms of "open + source" instead. After sharing the invite link in the VF-Technic + Guild, some people joined, and we've partially converted two users. + + +JJUUSSTTIIFFIICCAATTIIOONN + Two users is definitely few, but it sets a start and an example for how + freedom can be spread. + + + There are numerous free replacements to proprietary services such as + Discord, such as Internet Relay Chat, the Extensible Messaging and Pre- + sense Protocol, the Matrix protocol, and email. As Free Software ac- + tivists, we generally prefer these protocols over nonfree services. + This section explains the reasons to consider nonfree services and pro- + tocols. + + + Generally, users on IRC and XMPP have a fair understanding of the Free + Software Movement, and it is quick and easy to inform them what we mean + by "free", "the four freedoms", and similar ideas. For users on the + Libera Chat IRC network, which by far has the most users of any net- + work, it is exceptionally easy to introduce a user into the #fsf chan- + nel for discussions with people supporting Free Software. Introducing + ignorant users on these protocols and platforms are a day-to-day simple + task. + + + Furthermore, the amount of users we can reach on these protocols are + rather limiting. Libera has around forty thousand users according to + the UUSSEERRSS command, and considering the fact that around 90% of these + people aren't ignorant, there isn't much we can do. + + + Matrix users, in particular users of the matrix.org homeserver, typi- + cally know but don't completely understand Free Software. Rather than + using Matrix IDs to identify users, the Matrix specification specifies + that third-party platform identities, such as email and GitHub, are how + users should be referenced both internally by servers and shown to + other users. This is obviously an increadibly foolish idea, especially + considering the use of centralized identity servers (similar to X509 + certificate authorities) for 3PIDs. These are our first targets, but + these should also be easy to get the idea across. + + + It is true that Libera Chat and similar IRC networks, though multi-cen- + tered in a technical way (i.e. multiple IRC servers form an IRC net- + work), the network is politically centralized, controlled by one en- + tity, Libera. The Internet Relay Chat server-to-server protocol im- + plies that servers fully trust each other and are expected to not send + damaging commands, which in turn implies full trust between server op- + erators, no federation, and political centralization. The privacy pol- + icy and network policy of Libera Chat are in the author's opinion non- + intrusive, therefore the use of which is acceptable and is promoted by + the FSF. (Obviously, most methods of using IRC do not involve nonfree + software.) + + + Nevertheless, those that have never touched Free Software are often on + giant proprietary platforms, and take these as universal methods of + communication. Many people go months before checking their mailbox + (physical or electronic), refuse to use XMPP or IRC for its age. + + + An alternative protocol, Internet Delay Chat, is being developed. + + + There is one special case where using some nonfree software, and even + urging others to use it, can be a positive thing. That's when the use + of the nonfree software aims directly at putting an end to the use of + that very same nonfree software.[RMSGP] The author believes that the + following fall within this scope: + + + +o Developing a free program that requires nonfree environments to + bootstrap; + + +o To spread awareness of software freedom issues to users in nonfree + environments. + + + + As almost all types of programming can be done on most types of BSD and + GNU operating systems, the author hasn't found any software that fit + this category. Extending the interpretation allos for using nonfree + software's behavior as a reference in Free Software development, though + an arguable programming practice, may help the community to progress by + understanding common features that users of nonfree services use. + + + The latter is more interesting, as explained above our methods of + spreading awareness is limited. + + +AACCTTIIOONN PPRROOCCEEDDUURREE + Activists MMUUSSTT NNOOTT list such nonfree services in "Contact Information" + pages on their website or similar sources, unless followed by a expla- + nation that the purpose of the nonfree platform is to introduce users + thereof onto free protocols and to eventually exterminate the nonfree + platform. Whenever these references to nonfree platforms appear, the + author MMUUSSTT present free methods of communication. Activists SSHHOOUULLDD + pragmatically use as many of the popular free protocols as possible, to + ensure that oppurtunities of introductions are not lost. In cases in- + volving competition between free and nonfree protocols and platforms, + ethical concerns (i.e. enabling talking to a new user on any ethical + platform) MMUUSSTT take precedence over technical concerns (such as dislik- + ing the XMPP protocol for its inefficent use of XML) whenever possible. + + + Communities for introducing users to Free Software on nonfree platforms + MMUUSSTT be bridged to a free protocol in some obvious way, in order to + minimize the usage of nonfree platforms even for the purpose of commu- + nicating ideology to new users and allow members of the Free Software + community refusing to use nonfree platforms in any way to participate. + Usages of nonfree platforms, besides part of the user-introduction + process that must happen on the nonfree platform, SSHHOOUULLDD be avoided. + + + For example, the author created a Discord Guild called Free Software + Introductions, which is one-way-puppeted to #fsi on irc.andrewyu.org, + which is then one-way-puppeted to Libera. The relay system is sort-of + messed up, but it's working. Inviting new users to it via https://dis- + cord.gg/7CYp7ntww7 <https://discord.gg/7CYp7ntww7> is good, but as the + author has made his own sacrifice already, there exists no need for + other existing Free Software activists to join and use it instead of + IRC. + + +TTEECCHHNNIICCAALL LLIIMMIITTAATTIIOONNSS + The old and centralized nature of IRC, the insane 3PID recommendation + of Matrix, the bad routing and efficency of XMPP, and the lack of docu- + mentation on PSYC, has led us to develop a new protocol, Internet Delay + Chat[IDC], which aims to be free, modern (i.e. support for channel + groups and shared permission sets, non-text data with MIME types), sane + (i.e. TCP, UDP and SCTP-based, instead of HTTP POST APIs) and simple. + + +CCOONNCCLLUUSSIIOONN + Hi + + +FFSSFF CCOONNSSIIDDEERRAATTIIOONNSS + Hi + + +BBIIBBLLIIOOGGRRAAPPHHYY + [IDC] Andrew Yu The Second School Affiliated to Fudan University In- + ternet Delay Chat <https://git.andrewyu.org/internet-delay- + chat>2022 + + + [RMSGP] + Richard Stallman The GNU Project Is It Ever a Good Thing to Use + a Nonfree Program? <http://www.gnu.org/philosophy/is-ever-good- + use-nonfree-program.en.html>2013 + + + +AACCKKNNOOWWLLEEDDGGEEMMEENNTTSS <<!!----7777uuuuMMaannyy tthhaannkkss ttoo iiSShhaarreeFFrreeeeddoomm,, qqrrppnnxxzz,, DDiiffffiieeHHeellllmmaann,, + LLeeaahh RRoowwee aanndd mmaannyy ootthheerrss ffoorr tthhee iiddeeaass ((aanndd rreebbuutttteedd aarrgguummeennttss)) iinn + tthhiiss aarrttiiccllee..---->> +CCOONNTTRRIIBBUUTTOORRSS + Many thanks to everyone in the Free Software community for the freedom + we have today. + + +AAUUTTHHOORRSS + Written by Andrew Yu. + + + + +Free Software April 202P2RAGMATIC USE OF NONFREE SOFTWARE(1) diff --git a/pragmatics/pragmatics.md b/pragmatics/pragmatics.md new file mode 100644 index 0000000..e4884dd --- /dev/null +++ b/pragmatics/pragmatics.md @@ -0,0 +1,142 @@ +%%% +title = "Pragmatic Use of Nonfree Software" +abbrev = "Pragmatic Use of Nonfree Software" +area = "Free Software" +workgroup = "Free Software Community" +submissiontype = "independent" +ipr = "none" +keyword = ["Nonfree", "Pragmatics"] +#updates = [ 2555, 5540 ] +#date = 2003-04-01T00:00:00Z + +[seriesInfo] +name = "Internet-Draft" +value = "Request for Discussions 1" +stream = "independent" +status = "informational" + +[[author]] +initials = "A." +surname = "Yu" +fullname = "Andrew Yu" +#role = "author" +organization = "The 2nd School Aff. to FDU" + [author.address] + email = "andrew@andrewyu.org" + uri = "https://www.andrewyu.org/" +%%% + +.# Abstract + +Free Software is undoubtably a good thing for society. However, modern computer users are stuck in the proprietary "ecosystem" for historical reasons. This document describes the author's viewpoint of using proprietary platforms to spread the ideas of Free Software. + +.# Status of This Memo + +This document is currently in the DRAFT status. + +This document describes the author's viewpoint. This does not represent the ideas of the Free Software Foundation or any other entity. Distribution of this memo is unlimited. + +{mainmatter} + +# Introduction + +Readers of this memo probably understand the ideals of the Free Software Movement, and avoid proprietary software when possible. However, as most outsiders are unaware and are deeply buried inside the proprietary dystopia created by mostly multibillion-dollar technology coorporations, our methods of communicating with the masses are ineffective. + +In February 2022, the author decided to adjust his dogma, and permitted limited usage of nonfree chat platforms to hopefully spread our ideas to the general public. This was attempted by registering a Discord account, creating a Guild called "Free Software Introductions", and setting up a basic Discord-to-IRC relay to #fsi on both irc.andrewyu.org and irc.libera.chat. + +One of the communities that he knows about, the VF-Technic Minetest community, primarily uses Discord as a means of communication by plays not in-game. As the users inside are Minetest players, a Free Software voxel sandbox game, similar to but much more flexible and freedom-respecting than Minecraft, it is believed that the users have some contact with Free Software, although they might not understand the freedom part of the issue, i.e. they might be thinking in terms of "open source" instead. After sharing the invite link in the VF-Technic Guild, some people joined, and we've partially converted two users. + +# Justification + +Two users is definitely few, but it sets a start and an example for how freedom can be spread. + +There are numerous free replacements to proprietary services such as Discord, such as Internet Relay Chat, the Extensible Messaging and Presense Protocol, the Matrix protocol, and email. As Free Software activists, we generally prefer these protocols over nonfree services. This section explains the reasons to consider nonfree services and protocols. + +Generally, users on IRC and XMPP have a fair understanding of the Free Software Movement, and it is quick and easy to inform them what we mean by "free", "the four freedoms", and similar ideas. For users on the Libera Chat IRC network, which by far has the most users of any network, it is exceptionally easy to introduce a user into the #fsf channel for discussions with people supporting Free Software. Introducing ignorant users on these protocols and platforms are a day-to-day simple task. + +Furthermore, the amount of users we can reach on these protocols are rather limiting. Libera has around forty thousand users according to the `USERS` command, and considering the fact that around 90% of these people aren't ignorant, there isn't much we can do. + +Matrix users, in particular users of the matrix.org homeserver, typically know but don't completely understand Free Software. Rather than using Matrix IDs to identify users, the Matrix specification specifies that third-party platform identities, such as email and GitHub, are how users should be referenced both internally by servers and shown to other users. This is obviously an increadibly foolish idea, especially considering the use of centralized identity servers (similar to X509 certificate authorities) for 3PIDs. These are our first targets, but these should also be easy to get the idea across. + +It is true that Libera Chat and similar IRC networks, though multi-centered in a technical way (i.e. multiple IRC servers form an IRC network), the network is politically centralized, controlled by one entity, Libera. The Internet Relay Chat server-to-server protocol implies that servers fully trust each other and are expected to not send damaging commands, which in turn implies full trust between server operators, no federation, and political centralization. The privacy policy and network policy of Libera Chat are in the author's opinion non-intrusive, therefore the use of which is acceptable and is promoted by the FSF. (Obviously, most methods of using IRC do not involve nonfree software.) + +Nevertheless, those that have never touched Free Software are often on giant proprietary platforms, and take these as universal methods of communication. Many people go months before checking their mailbox (physical or electronic), refuse to use XMPP or IRC for its age. + +An alternative protocol, Internet Delay Chat, is being developed. + +There is one special case where using some nonfree software, and even urging others to use it, can be a positive thing. That's when the use of the nonfree software aims directly at putting an end to the use of that very same nonfree software.[@!RMSGP] The author believes that the following fall within this scope: + +- Developing a free program that requires nonfree environments to bootstrap; +- To spread awareness of software freedom issues to users in nonfree environments. + +As almost all types of programming can be done on most types of BSD and GNU operating systems, the author hasn't found any software that fit this category. Extending the interpretation allos for using nonfree software's behavior as a reference in Free Software development, though an arguable programming practice, may help the community to progress by understanding common features that users of nonfree services use. + +The latter is more interesting, as explained above our methods of spreading awareness is limited. + +# Action Procedure + +Activists **MUST NOT** list such nonfree services in "Contact Information" pages on their website or similar sources, unless followed by a explanation that the purpose of the nonfree platform is to introduce users thereof onto free protocols and to eventually exterminate the nonfree platform. Whenever these references to nonfree platforms appear, the author **MUST** present free methods of communication. Activists **SHOULD** pragmatically use as many of the popular free protocols as possible, to ensure that oppurtunities of introductions are not lost. In cases involving competition between free and nonfree protocols and platforms, ethical concerns (i.e. enabling talking to a new user on any ethical platform) **MUST** take precedence over technical concerns (such as disliking the XMPP protocol for its inefficent use of XML) whenever possible. + +Communities for introducing users to Free Software on nonfree platforms **MUST** be bridged to a free protocol in some obvious way, in order to minimize the usage of nonfree platforms even for the purpose of communicating ideology to new users and allow members of the Free Software community refusing to use nonfree platforms in any way to participate. Usages of nonfree platforms, besides part of the user-introduction process that must happen on the nonfree platform, **SHOULD** be avoided. + +For example, the author created a Discord Guild called Free Software Introductions, which is one-way-puppeted to #fsi on irc.andrewyu.org, which is then one-way-puppeted to Libera. The relay system is sort-of messed up, but it's working. Inviting new users to it via https://discord.gg/7CYp7ntww7 is good, but as the author has made his own sacrifice already, there exists no need for other existing Free Software activists to join and use it instead of IRC. + +# Technical Limitations +The old and centralized nature of IRC, the insane 3PID recommendation of Matrix, the bad routing and efficency of XMPP, and the lack of documentation on PSYC, has led us to develop a new protocol, Internet Delay Chat[@!IDC], which aims to be free, modern (i.e. support for channel groups and shared permission sets, non-text data with MIME types), sane (i.e. TCP, UDP and SCTP-based, instead of HTTP POST APIs) and simple. + + +# Conclusion + +Hi + +# FSF Considerations + +Hi + +{backmatter} + +{numbered="false"} +# Acknowledgements + +<!--77uuMany thanks to iShareFreedom, qrpnxz, DiffieHellman, Leah Rowe and many others for the ideas (and rebutted arguments) in this article.--> + +{numbered="false"} +# Contributors + +Many thanks to everyone in the Free Software community for the freedom we have today. + +<reference anchor="RFC2813" target="https://www.rfc-editor.org/rfc/rfc2813.txt"> + <front> + <title>Internet Relay Chat: Server Protocol</title> + <author> + <organization>Internet Engineering Task Force</organization> + </author> + <date year="2013" month="September"></date> + </front> +</reference> +<reference anchor="RMSGP" target="http://www.gnu.org/philosophy/is-ever-good-use-nonfree-program.en.html"> + <front> + <title>Is It Ever a Good Thing to Use a Nonfree Program?</title> + <author initials='R.' surname='Stallman' fullname='Richard Stallman'> + <organization>The GNU Project</organization> + <address> + <email>rms@gnu.org</email> + <uri>https://stallman.org/</uri> + </address> + </author> + <date year="2013" month="September"></date> + </front> +</reference> +<reference anchor='IDC' target='https://git.andrewyu.org/internet-delay-chat'> + <front> + <title>Internet Delay Chat</title> + <author initials='A.' surname='Yu' fullname='Andrew Yu'> + <organization>The Second School Affiliated to Fudan University</organization> + <address> + <email>andrew@andrewyu.org</email> + <uri>https://www.andrewyu.org/</uri> + </address> + </author> + <date year='2022' month="April" /> + </front> +</reference> diff --git a/pragmatics/pragmatics.txt b/pragmatics/pragmatics.txt new file mode 100644 index 0000000..4d92124 --- /dev/null +++ b/pragmatics/pragmatics.txt @@ -0,0 +1,280 @@ + + + + +Free Software Community A. Yu + The 2nd School Aff. to FDU + 16 April 2022 + + + Pragmatic Use of Nonfree Software + Request for Discussions 1 + +Abstract + + Free Software is undoubtably a good thing for society. However, + modern computer users are stuck in the proprietary "ecosystem" for + historical reasons. This document describes the author's viewpoint + of using proprietary platforms to spread the ideas of Free Software. + +Status of This Memo + + This document is currently in the DRAFT status. + + This document describes the author's viewpoint. This does not + represent the ideas of the Free Software Foundation or any other + entity. Distribution of this memo is unlimited. + +Table of Contents + + 1. Introduction . . . . . . . . . . . . . . . . . . . . . . . . 1 + 2. Justification . . . . . . . . . . . . . . . . . . . . . . . . 2 + 3. Action Procedure . . . . . . . . . . . . . . . . . . . . . . 4 + 4. Technical Limitations . . . . . . . . . . . . . . . . . . . . 4 + 5. Conclusion . . . . . . . . . . . . . . . . . . . . . . . . . 5 + 6. FSF Considerations . . . . . . . . . . . . . . . . . . . . . 5 + 7. Normative References . . . . . . . . . . . . . . . . . . . . 5 + Acknowledgements . . . . . . . . . . . . . . . . . . . . . . . . 5 + Contributors . . . . . . . . . . . . . . . . . . . . . . . . . . 5 + Author's Address . . . . . . . . . . . . . . . . . . . . . . . . 5 + +1. Introduction + + Readers of this memo probably understand the ideals of the Free + Software Movement, and avoid proprietary software when possible. + However, as most outsiders are unaware and are deeply buried inside + the proprietary dystopia created by mostly multibillion-dollar + technology coorporations, our methods of communicating with the + masses are ineffective. + + In February 2022, the author decided to adjust his dogma, and + permitted limited usage of nonfree chat platforms to hopefully spread + our ideas to the general public. This was attempted by registering a + + + +Yu Informational [Page 1] + + Pragmatic Use of Nonfree Software April 2022 + + + Discord account, creating a Guild called "Free Software + Introductions", and setting up a basic Discord-to-IRC relay to #fsi + on both irc.andrewyu.org and irc.libera.chat. + + One of the communities that he knows about, the VF-Technic Minetest + community, primarily uses Discord as a means of communication by + plays not in-game. As the users inside are Minetest players, a Free + Software voxel sandbox game, similar to but much more flexible and + freedom-respecting than Minecraft, it is believed that the users have + some contact with Free Software, although they might not understand + the freedom part of the issue, i.e. they might be thinking in terms + of "open source" instead. After sharing the invite link in the VF- + Technic Guild, some people joined, and we've partially converted two + users. + +2. Justification + + Two users is definitely few, but it sets a start and an example for + how freedom can be spread. + + There are numerous free replacements to proprietary services such as + Discord, such as Internet Relay Chat, the Extensible Messaging and + Presense Protocol, the Matrix protocol, and email. As Free Software + activists, we generally prefer these protocols over nonfree services. + This section explains the reasons to consider nonfree services and + protocols. + + Generally, users on IRC and XMPP have a fair understanding of the + Free Software Movement, and it is quick and easy to inform them what + we mean by "free", "the four freedoms", and similar ideas. For users + on the Libera Chat IRC network, which by far has the most users of + any network, it is exceptionally easy to introduce a user into the + #fsf channel for discussions with people supporting Free Software. + Introducing ignorant users on these protocols and platforms are a + day-to-day simple task. + + Furthermore, the amount of users we can reach on these protocols are + rather limiting. Libera has around forty thousand users according to + the USERS command, and considering the fact that around 90% of these + people aren't ignorant, there isn't much we can do. + + + + + + + + + + + +Yu Informational [Page 2] + + Pragmatic Use of Nonfree Software April 2022 + + + Matrix users, in particular users of the matrix.org homeserver, + typically know but don't completely understand Free Software. Rather + than using Matrix IDs to identify users, the Matrix specification + specifies that third-party platform identities, such as email and + GitHub, are how users should be referenced both internally by servers + and shown to other users. This is obviously an increadibly foolish + idea, especially considering the use of centralized identity servers + (similar to X509 certificate authorities) for 3PIDs. These are our + first targets, but these should also be easy to get the idea across. + + It is true that Libera Chat and similar IRC networks, though multi- + centered in a technical way (i.e. multiple IRC servers form an IRC + network), the network is politically centralized, controlled by one + entity, Libera. The Internet Relay Chat server-to-server protocol + implies that servers fully trust each other and are expected to not + send damaging commands, which in turn implies full trust between + server operators, no federation, and political centralization. The + privacy policy and network policy of Libera Chat are in the author's + opinion non-intrusive, therefore the use of which is acceptable and + is promoted by the FSF. (Obviously, most methods of using IRC do not + involve nonfree software.) + + Nevertheless, those that have never touched Free Software are often + on giant proprietary platforms, and take these as universal methods + of communication. Many people go months before checking their + mailbox (physical or electronic), refuse to use XMPP or IRC for its + age. + + An alternative protocol, Internet Delay Chat, is being developed. + + There is one special case where using some nonfree software, and even + urging others to use it, can be a positive thing. That's when the + use of the nonfree software aims directly at putting an end to the + use of that very same nonfree software.[RMSGP] The author believes + that the following fall within this scope: + + * Developing a free program that requires nonfree environments to + bootstrap; + * To spread awareness of software freedom issues to users in nonfree + environments. + + As almost all types of programming can be done on most types of BSD + and GNU operating systems, the author hasn't found any software that + fit this category. Extending the interpretation allos for using + nonfree software's behavior as a reference in Free Software + development, though an arguable programming practice, may help the + community to progress by understanding common features that users of + nonfree services use. + + + +Yu Informational [Page 3] + + Pragmatic Use of Nonfree Software April 2022 + + + The latter is more interesting, as explained above our methods of + spreading awareness is limited. + +3. Action Procedure + + Activists MUST NOT list such nonfree services in "Contact + Information" pages on their website or similar sources, unless + followed by a explanation that the purpose of the nonfree platform is + to introduce users thereof onto free protocols and to eventually + exterminate the nonfree platform. Whenever these references to + nonfree platforms appear, the author MUST present free methods of + communication. Activists SHOULD pragmatically use as many of the + popular free protocols as possible, to ensure that oppurtunities of + introductions are not lost. In cases involving competition between + free and nonfree protocols and platforms, ethical concerns (i.e. + enabling talking to a new user on any ethical platform) MUST take + precedence over technical concerns (such as disliking the XMPP + protocol for its inefficent use of XML) whenever possible. + + Communities for introducing users to Free Software on nonfree + platforms MUST be bridged to a free protocol in some obvious way, in + order to minimize the usage of nonfree platforms even for the purpose + of communicating ideology to new users and allow members of the Free + Software community refusing to use nonfree platforms in any way to + participate. Usages of nonfree platforms, besides part of the user- + introduction process that must happen on the nonfree platform, SHOULD + be avoided. + + For example, the author created a Discord Guild called Free Software + Introductions, which is one-way-puppeted to #fsi on irc.andrewyu.org, + which is then one-way-puppeted to Libera. The relay system is sort- + of messed up, but it's working. Inviting new users to it via + https://discord.gg/7CYp7ntww7 (https://discord.gg/7CYp7ntww7) is + good, but as the author has made his own sacrifice already, there + exists no need for other existing Free Software activists to join and + use it instead of IRC. + +4. Technical Limitations + + The old and centralized nature of IRC, the insane 3PID recommendation + of Matrix, the bad routing and efficency of XMPP, and the lack of + documentation on PSYC, has led us to develop a new protocol, Internet + Delay Chat[IDC], which aims to be free, modern (i.e. support for + channel groups and shared permission sets, non-text data with MIME + types), sane (i.e. TCP, UDP and SCTP-based, instead of HTTP POST + APIs) and simple. + + + + + +Yu Informational [Page 4] + + Pragmatic Use of Nonfree Software April 2022 + + +5. Conclusion + + Hi + +6. FSF Considerations + + Hi + +7. Normative References + + [IDC] Yu, A., "Internet Delay Chat", April 2022, + <https://git.andrewyu.org/internet-delay-chat>. + + [RMSGP] Stallman, R., "Is It Ever a Good Thing to Use a Nonfree + Program?", September 2013, <http://www.gnu.org/philosophy/ + is-ever-good-use-nonfree-program.en.html>. + +Acknowledgements + +Contributors + + Many thanks to everyone in the Free Software community for the + freedom we have today. + +Author's Address + + Andrew Yu + The 2nd School Aff. to FDU + Email: andrew@andrewyu.org + URI: https://www.andrewyu.org/ + + + + + + + + + + + + + + + + + + + + + +Yu Informational [Page 5] diff --git a/pragmatics/pragmatics.xml b/pragmatics/pragmatics.xml new file mode 100644 index 0000000..9254784 --- /dev/null +++ b/pragmatics/pragmatics.xml @@ -0,0 +1,113 @@ +<?xml version="1.0" encoding="utf-8"?> +<!-- name="GENERATOR" content="github.com/mmarkdown/mmark Mmark Markdown Processor - mmark.miek.nl" --> +<rfc version="3" ipr="none" docName="Request for Discussions 1" submissionType="independent" category="info" xml:lang="en" xmlns:xi="http://www.w3.org/2001/XInclude" indexInclude="true"> + +<front> +<title abbrev="Pragmatic Use of Nonfree Software">Pragmatic Use of Nonfree Software</title><seriesInfo value="Request for Discussions 1" stream="independent" status="informational" name="Internet-Draft"></seriesInfo> +<author initials="A." surname="Yu" fullname="Andrew Yu"><organization>The 2nd School Aff. to FDU</organization><address><postal><street></street> +</postal><email>andrew@andrewyu.org</email> +<uri>https://www.andrewyu.org/</uri> +</address></author><date/> +<area>Free Software</area> +<workgroup>Free Software Community</workgroup> +<keyword>Nonfree</keyword> +<keyword>Pragmatics</keyword> + +<abstract> +<t>Free Software is undoubtably a good thing for society. However, modern computer users are stuck in the proprietary "ecosystem" for historical reasons. This document describes the author's viewpoint of using proprietary platforms to spread the ideas of Free Software.</t> +</abstract> + +<note><name>Status of This Memo</name> +<t>This document is currently in the DRAFT status.</t> +<t>This document describes the author's viewpoint. This does not represent the ideas of the Free Software Foundation or any other entity. Distribution of this memo is unlimited.</t> +</note> + +</front> + +<middle> + +<section anchor="introduction"><name>Introduction</name> +<t>Readers of this memo probably understand the ideals of the Free Software Movement, and avoid proprietary software when possible. However, as most outsiders are unaware and are deeply buried inside the proprietary dystopia created by mostly multibillion-dollar technology coorporations, our methods of communicating with the masses are ineffective.</t> +<t>In February 2022, the author decided to adjust his dogma, and permitted limited usage of nonfree chat platforms to hopefully spread our ideas to the general public. This was attempted by registering a Discord account, creating a Guild called "Free Software Introductions", and setting up a basic Discord-to-IRC relay to #fsi on both irc.andrewyu.org and irc.libera.chat.</t> +<t>One of the communities that he knows about, the VF-Technic Minetest community, primarily uses Discord as a means of communication by plays not in-game. As the users inside are Minetest players, a Free Software voxel sandbox game, similar to but much more flexible and freedom-respecting than Minecraft, it is believed that the users have some contact with Free Software, although they might not understand the freedom part of the issue, i.e. they might be thinking in terms of "open source" instead. After sharing the invite link in the VF-Technic Guild, some people joined, and we've partially converted two users.</t> +</section> + +<section anchor="justification"><name>Justification</name> +<t>Two users is definitely few, but it sets a start and an example for how freedom can be spread.</t> +<t>There are numerous free replacements to proprietary services such as Discord, such as Internet Relay Chat, the Extensible Messaging and Presense Protocol, the Matrix protocol, and email. As Free Software activists, we generally prefer these protocols over nonfree services. This section explains the reasons to consider nonfree services and protocols.</t> +<t>Generally, users on IRC and XMPP have a fair understanding of the Free Software Movement, and it is quick and easy to inform them what we mean by "free", "the four freedoms", and similar ideas. For users on the Libera Chat IRC network, which by far has the most users of any network, it is exceptionally easy to introduce a user into the #fsf channel for discussions with people supporting Free Software. Introducing ignorant users on these protocols and platforms are a day-to-day simple task.</t> +<t>Furthermore, the amount of users we can reach on these protocols are rather limiting. Libera has around forty thousand users according to the <tt>USERS</tt> command, and considering the fact that around 90% of these people aren't ignorant, there isn't much we can do.</t> +<t>Matrix users, in particular users of the matrix.org homeserver, typically know but don't completely understand Free Software. Rather than using Matrix IDs to identify users, the Matrix specification specifies that third-party platform identities, such as email and GitHub, are how users should be referenced both internally by servers and shown to other users. This is obviously an increadibly foolish idea, especially considering the use of centralized identity servers (similar to X509 certificate authorities) for 3PIDs. These are our first targets, but these should also be easy to get the idea across.</t> +<t>It is true that Libera Chat and similar IRC networks, though multi-centered in a technical way (i.e. multiple IRC servers form an IRC network), the network is politically centralized, controlled by one entity, Libera. The Internet Relay Chat server-to-server protocol implies that servers fully trust each other and are expected to not send damaging commands, which in turn implies full trust between server operators, no federation, and political centralization. The privacy policy and network policy of Libera Chat are in the author's opinion non-intrusive, therefore the use of which is acceptable and is promoted by the FSF. (Obviously, most methods of using IRC do not involve nonfree software.)</t> +<t>Nevertheless, those that have never touched Free Software are often on giant proprietary platforms, and take these as universal methods of communication. Many people go months before checking their mailbox (physical or electronic), refuse to use XMPP or IRC for its age.</t> +<t>An alternative protocol, Internet Delay Chat, is being developed.</t> +<t>There is one special case where using some nonfree software, and even urging others to use it, can be a positive thing. That's when the use of the nonfree software aims directly at putting an end to the use of that very same nonfree software.<xref target="RMSGP"></xref> The author believes that the following fall within this scope:</t> + +<ul spacing="compact"> +<li>Developing a free program that requires nonfree environments to bootstrap;</li> +<li>To spread awareness of software freedom issues to users in nonfree environments.</li> +</ul> +<t>As almost all types of programming can be done on most types of BSD and GNU operating systems, the author hasn't found any software that fit this category. Extending the interpretation allos for using nonfree software's behavior as a reference in Free Software development, though an arguable programming practice, may help the community to progress by understanding common features that users of nonfree services use.</t> +<t>The latter is more interesting, as explained above our methods of spreading awareness is limited.</t> +</section> + +<section anchor="action-procedure"><name>Action Procedure</name> +<t>Activists <bcp14>MUST NOT</bcp14> list such nonfree services in "Contact Information" pages on their website or similar sources, unless followed by a explanation that the purpose of the nonfree platform is to introduce users thereof onto free protocols and to eventually exterminate the nonfree platform. Whenever these references to nonfree platforms appear, the author <bcp14>MUST</bcp14> present free methods of communication. Activists <bcp14>SHOULD</bcp14> pragmatically use as many of the popular free protocols as possible, to ensure that oppurtunities of introductions are not lost. In cases involving competition between free and nonfree protocols and platforms, ethical concerns (i.e. enabling talking to a new user on any ethical platform) <bcp14>MUST</bcp14> take precedence over technical concerns (such as disliking the XMPP protocol for its inefficent use of XML) whenever possible.</t> +<t>Communities for introducing users to Free Software on nonfree platforms <bcp14>MUST</bcp14> be bridged to a free protocol in some obvious way, in order to minimize the usage of nonfree platforms even for the purpose of communicating ideology to new users and allow members of the Free Software community refusing to use nonfree platforms in any way to participate. Usages of nonfree platforms, besides part of the user-introduction process that must happen on the nonfree platform, <bcp14>SHOULD</bcp14> be avoided.</t> +<t>For example, the author created a Discord Guild called Free Software Introductions, which is one-way-puppeted to #fsi on irc.andrewyu.org, which is then one-way-puppeted to Libera. The relay system is sort-of messed up, but it's working. Inviting new users to it via <eref target="https://discord.gg/7CYp7ntww7">https://discord.gg/7CYp7ntww7</eref> is good, but as the author has made his own sacrifice already, there exists no need for other existing Free Software activists to join and use it instead of IRC.</t> +</section> + +<section anchor="technical-limitations"><name>Technical Limitations</name> +<t>The old and centralized nature of IRC, the insane 3PID recommendation of Matrix, the bad routing and efficency of XMPP, and the lack of documentation on PSYC, has led us to develop a new protocol, Internet Delay Chat<xref target="IDC"></xref>, which aims to be free, modern (i.e. support for channel groups and shared permission sets, non-text data with MIME types), sane (i.e. TCP, UDP and SCTP-based, instead of HTTP POST APIs) and simple.</t> +</section> + +<section anchor="conclusion"><name>Conclusion</name> +<t>Hi</t> +</section> + +<section anchor="fsf-considerations"><name>FSF Considerations</name> +<t>Hi</t> +</section> + +</middle> + +<back> +<references><name>Normative References</name> +<reference anchor="IDC" target="https://git.andrewyu.org/internet-delay-chat"> + <front> + <title>Internet Delay Chat</title> + <author fullname="Andrew Yu" initials="A." surname="Yu"> + <organization>The Second School Affiliated to Fudan University</organization> + <address> + <email>andrew@andrewyu.org</email> + <uri>https://www.andrewyu.org/</uri> + </address> + </author> + <date year="2022" month="April"></date> + </front> +</reference> +<reference anchor="RMSGP" target="http://www.gnu.org/philosophy/is-ever-good-use-nonfree-program.en.html"> + <front> + <title>Is It Ever a Good Thing to Use a Nonfree Program?</title> + <author fullname="Richard Stallman" initials="R." surname="Stallman"> + <organization>The GNU Project</organization> + <address> + <email>rms@gnu.org</email> + <uri>https://stallman.org/</uri> + </address> + </author> + <date year="2013" month="September"></date> + </front> +</reference> +</references> + +<section anchor="acknowledgements" numbered="false"><name>Acknowledgements</name> +</section> + +<section anchor="contributors" numbered="false"><name>Contributors</name> +<t>Many thanks to everyone in the Free Software community for the freedom we have today.</t> +</section> + +</back> + +</rfc> |