Bonum Certa Men Certa

Introduction to Techrights IRC

IRC channels



Summary: A sort of belated primer regarding our IRC channels; these remain our main collaboration tool for real-time interactions (since 2008)

Techrights IRC channels go back more than 12 years (hence the channels with "boycottnovell" still in them; it's a legacy feature or artifact). There are 4 channels and one of them is mostly used to retain local copies of Social Control Media posts; historically this was done for about a dozen regulars of ours, using Identi.ca (and later Twitter) APIs; when Twitter shut down these APIs 2 years ago we resorted to Pleroma/Fediverse (a bot called "viera" was developed for us, for this very purpose), so the number of people echoed was significantly reduced. Many are, sadly enough, not on Fediverse (and not because they're too busy blogging).

"Nowadays the main channel has in it between 60 to 70 people (plus bots) constantly lurking. Some people do not lurk in IRC but instead read the logs to keep abreast (happenings behind the scenes)."In a sense, going back to these Identi.ca roots (Fediverse is only partly compatible with what was once known as StatusNet) is a gain for freedom and for Free software, even if the paradigm itself -- namely Social Control Media -- is deeply flawed.

Nowadays the main channel has in it between 60 to 70 people (plus bots) constantly lurking. Some people do not lurk in IRC but instead read the logs to keep abreast (happenings behind the scenes). Sometimes E-mail provides a sort of 'feedback loop' between log lurkers and IRC lurkers (they can communicate with one another days apart). We facilitate those kinds of discussions.

While we don't need to talk about who's who (some people prefer their pseudonyms and their privacy; they're reasonably technical and privacy-conscious), there's something to be said about the IRC logs.

Logging



It all started in 2008. Keith from Slated.org helped set up the main and first channel. The channels were logged on multiple machines and logs published on a daily basis since the early days (my workstation in Manchester University used to be the fallback machine, sitting there in the shared office with XChat in the background). Some time around 2011 -- or maybe a year later -- the logs were published less regularly because the workflow was labour-intensive and sometimes I was physically away. Mark, who is based in Canada, has a server sitting on the channels logging it for us in case the connection goes offline here in the UK. Logging is nowadays also being done in the US. So three different countries do the logging, which improves robustness (avoiding data loss/textual lapses) by redundancy. Netsplits and Freenode downtime incidents -- however rare these may be -- can be compensated for (by having logs from both sides of the 'split'). We improved these mechanisms over the years. Not even prolonged power outages would lead to data loss.

"Netsplits and Freenode downtime incidents -- however rare these may be -- can be compensated for (by having logs from both sides of the 'split')."Last summer or in early autumn (we published some logs retroactively) we worked to address that lack of automation and resumed publishing logs every day at roughly the same time. The logs are typically generated, manually, some time after midnight and then uploaded. Supervised by a person, the process is less error-prone. Two people check the process.



Redaction



There are two levels of redaction. One pertains to pre-pasting of material onto channels and another is done, albeit very rarely, after something is said publicly (in IRC, but not in logs). This can be due to a privacy issue, a pasting malfunction, or a request (it's rare but it happens). We don't just publish everything irresponsibly. We carefully check that nothing illegal, for example, is being done or promoted. Considering the fact we're censorship-free, the channels are still surprisingly civil and most of the time they're professional enough. Profanities aren't being censored; we detest censorship. Profanity is part of human nature and deletion won't change that nature.

How to Join Us



The channels can be accessed using a Web browser or using an IRC client. The main channel is #techrights at irc.freenode.org (the less important channels are #boycottnovell, #techbytes and #boycottnovell-social; there's also #tuxmachines, but that's a different site).

"It probably shouldn't be too shocking that many of the IRC discussion lead to topics and angles covered here on a daily basis (in wiki and blog form)."We're always attentive and there's always somebody ready to reply, provided one waits long enough because people are "away from keyboard" (afk) a lot of the time. Sometimes people drop by, say a few words, then disappear after about a minute, not giving even an opportunity to respond. 4 of my screens show me 4 IRC channels in tandem, but rather than or instead relying on alerts/notifications I depend on motion (screen changes) to detect activity because it is a lot less distracting.

It probably shouldn't be too shocking that many of the IRC discussion lead to topics and angles covered here on a daily basis (in wiki and blog form). The community generally grew over time and we're proud to say no censorship or "CoC" was needed; it would only harm the general atmosphere. We're an unmoderated forum. We're also transparent enough that the concept of "techrightsGate" or "techrightsLeaks" is ludicrous at best; it would not reveal anything that's not already publicly accessible to all.

Recent Techrights' Posts

Writing and Coding Isn't Always Enough
Last year we had to assume a role we didn't have before: litigants
 
Why We Publish Information About the SLAPPs (But Not About the Legal Process), an Abuse of Process by Americans Trying to Silence Critics of Their Employer, Microsoft
It doesn't take thousands of pages to explain something simple
Internet Relay Chat Didn't Fall Off a Cliff
IRC will turn 40 in less than 3 years from now
The UEFI 9/11 - Part V - This is Not a Drill (Disable "SecureBoot" Now)
A "9/11" Coming
There's No Obligation to Speak to Anybody
The very fact that "bkuhn" is till spending time in social control media says a lot about his poor judgment
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Monday, September 01, 2025
IRC logs for Monday, September 01, 2025
The Register MS Says "AI Web Crawlers Are Destroying Websites", So Why Does The Register MS Help 'AI' Companies? (Spoiler: Money)
People need to call out The Register MS on its hypocrisy
Microsoft Trying to Force People to Resign (Amid Mass Layoffs) a Strategy That Takes Its Toll
Microsoft seems to be circling down the drain and the "final flush" will be the moment the "hey hi" (AI) bubble implodes completely
Google Simply Cannot Be Trusted
Only fools would trust GAFAM
Admission That a Third Party (or Parties) Funds the SLAPPs Against Techrights
This can end up costing them over a million dollars
Modifying and Writing One's Own Computer Programs is Not a Crime (or: Google Proves That Stallman Was Right)
We're generally gratified to see so many positive mentions of him
Why We Stopped Publishing Videos (for Now)
We'll probably get back to videos one day, but it's hard to say when or to what extent
What Animal Rights Activism Teaches Us About Sympathy and Focus
It's possible to believe that the planet is warming, that we must do something about it, and still eat eggs and butter
When You Turn Web Sites About Tech Into Political Sites
A lot of people fall into the trap of catering only for particular groups
Gemini Links 02/09/2025: ROOPHLOCH 2025 and Lagrange 1.19 Released
Links for the day
Gemini Links 01/09/2025: News Corp. WSJ and A Month With NixOS
Links for the day
Slopfarms Already Peaked, They Will Die When Slop Companies Run Out of Money to Borrow
slopfarms will lack an actual "engine"
“Sideloading” Never Killed Anybody
There are many online discussions this week about the misnomer "sideloading"
Slopwatch: Google News as FUD Vector Against Linux and Plagiarism Enhancer, Serial Slopper (SS) Uses LLMs to Googlebomb "Linux"
Slop destroys the Web not just by screwing with search engines and helping plagiarists. It's also responsible for de facto DDoS attacks...
Links 01/09/2025: "Attacks on Science" and China's "Soft Power" Grows
Links for the day
Links 01/09/2025: Fresh Backlash Against Slop and "Norway’s Electricity Crisis is About to Hit Britain"
Links for the day
Links 01/09/2025: Catching Up (Mostly via Deutsche Welle), "Windows TCO" Effect in UK
Links for the day
Gemini Links 01/09/2025: Linguistic Barriers and "Web 1.0 Hosting"
Links for the day
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Sunday, August 31, 2025
IRC logs for Sunday, August 31, 2025
Autumn Has Come
Autumn should be exciting in all sorts of ways; it'll also mark our anniversary
The UEFI 9/11 - Part IV - External Interference
They all seem to be playing a role in crushing Software Freedom and self-determination for users
Links 31/08/2025: Baggage Claim Scams, an Insurrectionist’s War on Culture, and a Sudden Robotics Hype
Links for the day
Gemini Links 31/08/2025: Reviewing Netsurf and Slightly Less Historic Ada Design
Links for the day
IBM Has Taken Control of GNOME
Don't expect a successor to be found any time soon
Links 31/08/2025: Google Gmail Data Breach and LF Puff Pieces for Pay
Links for the day
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Saturday, August 30, 2025
IRC logs for Saturday, August 30, 2025
This is What Google News Has Become
Moments ago