Bonum Certa Men Certa

Freedom From Censorship on Mailing Lists

Reprinted with permission from the Free Software Fellowship

A recent blog examined the phenomena of fake communities, especially in the free software space.



One prominent tool used to construct the fake community is the email discussion list.



When people join a discussion list, they assume and believe that they are being exposed to a wide range of opinions. Therefore, when some opinions or critical information is hidden, ordinary members of the list are deceived. People have not consented to this deception.



In 2018, FSFE used these tactics to make it appear that nobody supported elections any more. In 2019, rogue elements of the Free Software Foundation (FSF) staff used the same tactics to undermine their own founder, Richard Stallman. FSF is the organization that explains their use of the word Free using the phrase Free as in speech, not free as in beer. When they don't even allow Free Speech on their own LibrePlanet-discuss mailing list, the organization loses all credibility.



Can you work around mailing list censorship?



By default, it is safe to assume that other members of the mailing list have not consented to being deceived by censorship.



If your messages are being censored and if you didn't consent to censorship, politely working around it, using techniques like BCC, is morally justified.



The monoculture's last gasp



Defenders of the monoculture will make up all kinds of defamation and threats to justify their behaviour.



They regularly try to make claims about netiquette or consent to use the email addresses of other list participants.



Ultimately, by joining a list, the participants have consented to communicate with you about the topic of the list. The technical means you use to communicate with them, whether it involves private emails or list emails, are secondary to that. To put that in reverse: if you used the list to send off-topic spam that was unrelated to the list, the simple fact that you had used the official list infrastructure rather than a side-channel doesn't make your off-topic spam more legitimate. Therefore, they can't credibly argue that sending on-topic mails through a side-channel is less legitimate.



If you believe in freedom, the F in FSF, like the Libre in LibrePlanet, then protecting communication channels is fundamental.



Side channels in practice



Implementing a side-channel is a great way to make the free software community stronger and more resilient against totalitarian behaviour. Here are some of the design criteria:





All of these things can be achieved using a combination of message headers, including BCC, Reply-To, List-Id, List-Unsubscribe and In-Reply-To.



In the Mozilla Thunderbird email client, you can add any arbitrary header to a message. To do so, go to the Preferences window, click Advanced and then Config Editor....



In the Config Editor window, look for the key mail.compose.other.header and set the String value In-Reply-To,List-Id,List-Unsubscribe:



fsfellowship image

Now you can start composing a message. Here is how to populate each header:





Here is an example:



fsfellowship image

Questions and feedback?



Please come and share your experiences of mailing list censorship on the Fellowship mailing list.



Recent Techrights' Posts

Sounds Like IBM is Preparing for Mass Layoffs/Redundancies in Red Hat, Albeit in "PIP" (Performance Improvement Plan) or "Relocation" Clothing
This isn't the "old" IBM; they're applying pressure by confusion and humiliation
Gemini Links 17/04/2025: Role of Language and Back to Mutt for E-mail
Links for the day
Microsoft's Attack Dogs Have Failed. Now What?
It would be utterly foolish to assume that Microsoft has any intention of changing
All Your "Github Projects" Will be Gone One Day (Just Like Skype)
If you have code you wish to share and keep, then start learning how to do so on your own
Fedora Already Lost Its Soul Under IBM
Fedora used to be very strict compared to many other distros and it had attracted very bright volunteers
 
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Friday, April 18, 2025
IRC logs for Friday, April 18, 2025
Links 18/04/2025: "Fentanylware (TikTok) Exodus Continues", Chinese Weapons Allegedly in Russia Already
Links for the day
Gemini Links 18/04/2025: Price of Games and State of Tinylog
Links for the day
"Sayonara" (さよなら), Microsoft
Windows had fallen below iOS in some countries
Links 18/04/2025: Layoffs at Microsoft Infosys and Qt Becoming Increasingly Proprietary (Plus Slop)
Links for the day
Google News is Dying
treating MElon's algorithmic/biased site as a source of verified news
To Understand Who's Truly Controlling You Follow the Trail of Censorship (or Self-Censorship)
Do not let media steal and steer the narrative; CoCs are not about "social justice", they're about corporate domination
Microsoft is Still Attacking GNU/Linux and the Net
Microsoft bribed the government using money that did not even exist
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Thursday, April 17, 2025
IRC logs for Thursday, April 17, 2025
Gemini Links 18/04/2025: Pinephone Pro and Linux is too Easy
Links for the day
Links 17/04/2025: Calling Whistleblowers at Microsoft, Slop Doing More Harm Everywhere
Links for the day
Links 17/04/2025: Russian Bot Farms Infect TikTok (Which US Government and SCOTUS Decided to Block January 19), US Hardware Stocks Crash Due to Tariffs
Links for the day
Gemini Links 17/04/2025: Sticking to Free Software, Smolnet, and Counting the Reals
Links for the day
Open Source Initiative (OSI) Privacy Fiasco in Detail: In Conclusion and Enforcement Action Proceeds Against OSI at the California Privacy Protection Agency (CPPA)
There's too much to cover in one single part
When You Fail to Filter Your Clients You End Up SLAPPing Reporters on Behalf of Bad People From Microsoft in Another Continent
“American Psycho”
Links 17/04/2025: LayoffBot and Tesla Cheats Buyers
Links for the day
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Wednesday, April 16, 2025
IRC logs for Wednesday, April 16, 2025