Bonum Certa Men Certa

Help Make Techrights (and Other Technology-Centric Sites) More Robust to Censorship by Setting Up More IPFS Nodes

IPFS large logo



Summary: We're trying to improve the site's availability (ensuring it can never be offline) and make it more censorship-resistant; people who adopt IPFS can make that happen while tackling the "bloated Web" and "centralised Internet" issues -- all at the same time

JUST over a month ago we hooked up with data-centric security folks who had offered help with Techrights. Having faced legal threats over the years (for exposing corruption), we're always looking for ways to avert or discourage such attempts (ideally, even if we're forced to go offline or remove something, we want that to be outside our control, i.e. inability to comply, even if there's a will to comply). We don't typically just repeat what other sites say, we have many exclusive stories and we publish leaks (unseen beforehand).



Now, less than a month later, we have a pipeline for publishing the site both as text and over distributed protocols. The Techrights IPFS node over here (at home) now exceeds 50GB in traffic, just 3 weeks down the line (after introducing people to it, i.e. 'going public'). Not bad considering how young it is. It's always active, offering full site access. There's no single point of failure, no HTTP, no WWW, no HTML. It's very text-centric and thus compact, portable and so on. No bloat associated with exporting/importing images, fonts, JavaScript and so on.

Earlier today we published many pages of internal EPO material; we need to get those sorts of things backed up, as EPO management can be litigious and threatening (they tried it on us several times). Techrights is home to many other important bits of material; months ago we published old debian-private archives (1990s only); those were accessed nearly 30,000 times in this past week alone. Giving Debian better transparency 2.5 decades later can't be a bad thing. In fact, nobody contacted us regarding removal or redaction. Those mailing lists are pretty harmless and barely even embarrassing. Due to their age, they don't present/pose a threat to anybody's career.

"In other words, the more people participate in this network, the more robust and censorship-resistant it'll become. This, in turn, can attract more high-profile whistleblowers with high-profile leaks."Now, on to the 'beef' of this post...

This past autumn we spent time coding and testing a bunch of stuff (at the back end for the most part). First we made everything in the site accessible in/as text. Plain text. Nice and simple. Then, we explored a number of distribution systems. At the end we went ahead of IPFS, seeing that it is decentralised and Web-agnostic (its protocols aren't connected to the Web, unless a gateway is set up). We already have a number of devices pinning and serving the site's pages (or objects) upon request by CID.

Share large logoHow can readers help? They can become nodes. The material itself isn't sensitive (everything in it is public anyway), but it's precarious in the sense that takedown requests can be attempted against our main servers; we want to make it very clear upfront that it's an exercise in futility because many copies of the articles are already 'out there', being distributed by peer, not from a single point (of potential failure).

In other words, the more people participate in this network, the more robust and censorship-resistant it'll become. This, in turn, can attract more high-profile whistleblowers with high-profile leaks.

An informal manual was typed up by one of us as a sort of primer for those wishing to set up their own node. It ought not be hard to achieve (by just following the series of steps). Those instructions were written for a Raspberry Pi with Debian, but the hardware and the distro ought not matter much because we use the binaries rather than repos.

"I'm going to outline a pragmatic setup that you can use to get going with IPFS on any host," said the manual's author. Here's the recipe:




SUMMARY



Make user + group for IPFS. All further steps are to be performed under IPFS user's "~/" (home directory).

Download and extract latest Go binaries available from official tarball.

Symbolic link Go binary executables, from tarball, into "~/bin".

Download and extract latest IPFS binary available from official tarball.

Symbolic link IPFS binary executable, from tarball, into "~/bin".

BEGIN IPFS BASIC USE GUIDE SUMMARY



What's covered:

IPFS conceptual overview.

Help from the `ipfs` command itself.

Initialise ipfs for your IPFS user.

List pinned IPFS objects.

Add/pin IPFS objects.

Remove pinned IPFS objects.

Run garbage collector for IPFS objects.

Check IPFS stats.

Check a file's CID without adding/pinning to IPFS.

SETUP DETAILS



Make a dedicated user and group for IPFS on your machine. This will keep things manageable, down the line. Everything should be done under the IPFS user's home directory "~/".

Grab the latest Go binary you can find. Set it up in the home directory of your IPFS user. You can find the latest Go binary here. There are builds for a wide array of operating systems and CPU architectures.

Extract the tarball; look in "/bin" in the tarball for the binary executables. Right now there are two binaries, "go" and "gofmt".

Create a symbolic link in "~/bin" for the binary executables you find in the Go tarball. You should be able to run `$ source ~/.profile` to make sure "~/bin" is in PATH, for the IPFS user.

This completes the Go setup.

Next, we tackle the IPFS setup.

Download the latest binary you can get for go-ipfs from here. This binary should be packed in a tarball.

Extract the tarball.

"go-ipfs" is the name of the binary executable. Create a symbolic link for this binary in "~/bin". You don't need to use the setup script provided. It'll just mess with things that don't need messing.

IPFS BASIC USE GUIDE



Think of IPFS as a filesystem that lives on the Internet. Each file is an IPFS object denoted by a hash called the CID (content identifier).

`ipfs --help` includes help for commands and subcommands. Always double-check with this to make sure that anything you read on the Internet about IPFS matches up to the binary you actually are using on your system.

Before you do anything with ipfs, make sure to run `ipfs init`. This will populate "~/.ipfs" for you. That's all you need to do for initial setup.

You can "deploy" ipfs locally with `ipfs daemon`; this process will be running in the foreground and print to the terminal (probably stdout). You can just put it in the background and redirect stdout and stderr to a log file to manually monitor what it's doing. Killing this daemon will mean your IPFS node is no longer online. Feel free to control this daemon in whichever method you choose. This guide is kept as abstract as possible to enable deployment in maximum number of environments.

Files from your host can be added to IPFS as something called IPFS objects. The ipfs command for this is, unsurprisingly, called `ipfs add`. `ipfs add path` will add the specified file or directory to IPFS.

By default, `ipfs add` "pins" objects in your local IPFS datastore. What is a "pinned object"? A pinned object is an IPFS object in your local IPFS datastore that doesn't get garbage-collected.

`ipfs pin ls` is a good way to view your pins. `ipfs pin rm` can be used to remove pins; if you try to remove the wrong type of pin, IPFS will get mad and yell at you because it's probably a recursive pin (you'll see what kind of pin an IPFS object is in the output for `ipfs pin ls`); a top-level pin will probably be of type "recursive" (so you'll need to remove that to get rid of all the pinned objects that are associated).

You can check bandwidth status with `ipfs stats bw`. Good way to keep track of your precious bandwidth. ipfs comes with some default pins. You might want to get rid of those with `ipfs pin rm` to save on bandwidth. Those pins are documentation, however, so it's up to you if you want to keep them around or not.

Just removing a pin is not enough to ensure pin(s) are no longer is eating up your local IPFS datastore space. `ipfs repo gc` will run the garbage collector to get rid of all the unpinned IPFS objects.

The default IPFS configuration is pretty sane. You can find the default config file for IPFS in "~/.ipfs/config"; the config file is formatted in JSON. See `ipfs config --help` for further details.

Remember: always check `ipfs <command> <subcommand> --help` for definitive guidance on your binary's implementation. `ipfs --help` should be skimmed, in full, before you do anything with IPFS; you will likely find commands to help you with what you want to do. Don't forget that `ipfs <command> --help` and `ipfs <command> <subcommand> --help` are always available for you as well.

Consuming IPFS objects is straightforward. Just look at `ipfs get --help` and `ipfs cat --help` for instructions.

To check what a file's CID is, without adding/pinning to ipfs, just run `ipfs add -n /path/to/file`; see `ipfs add --help` for details. This is going to be a very important operation if you want to do any automation. It helps knowing what a file's CID will be before doing any operations live IPFS operations on it.

You should now be able to independently navigate the Internet for further information on IPFS. Official, online, documentation available here. Remember to always cross-check `ipfs version` and `ipfs <command> <subcommand> --help` to ensure what you read on the Internet is applicable to the IPFS binary executable on your system. ⬆

Image attributions: Font Awesome (Creative Commons Attribution 4.0 International) and IPFS project (Creative Commons Attribution-Share Alike 3.0 Unported)

Recent Techrights' Posts

When Short is Way Too Short (Superficiality, Lowering of Entropy)
Demonstrating how truly worthless social control media was all along
 
Links 16/11/2026: Data Centers (White Elephants) as Tax Evasion Scam/Ploy, Social Control Media Harms Boomers, "Microsoft Outage Hindered Ticket Issuance in Greece"
Links for the day
The Register MS Seems to Have Moved to 'The Cloud' (WeWork) After Shutting Down the Office
The Register MS will have a hard time explaining why it so passionately participated in the "hey hi" pyramid scheme
Holiday Plans (We Need More IBM Whistleblowers)
in particular with possession of material in relation to PIPs, NDAs, and silent RAs
After Microsoft Outage GNU/Linux Usage Leaps to 9% in the UK (Where Public Services Were Notoriously Overdependent on Microsoft Disservices)
in the UK we are extremely dependent on Microsoft stuff in the NHS, courts, law firms, police etc.
Richard Stallman Was Right About the Corruption of the Term "Artificial intelligence"
This will do severe damage to the administration which participated in the scam
The Dictatorship Already Working to Distract From NVIDIA Corruption and Slop Bubble Reaching Its Limits
Circular financing is simply a form of financial fraud
IBM Selling Itself, Piecewise, to Raise Money (to Pay Salaries)
IBM is a zombie waiting to inhale one last time (last breath)
"Allies" of Disgraced NVIDIA CEO Aren't About Morality, They're Just Covering Up Their Own Backs (and Loans)
The next stage is examining the false accounting (fraud basically)
No Outage Since 2023
I did host from home between 2020 and 2023
Intercontinental Brigading - Part XXXXXII - Back Doors and Kill Switches From Microsoft Are Objectively Undesirable
"I dual-boot Omarchy and Windows. Be careful updating your BIOS. Mine made Omarchy unbootable."
Gemini Links 16/11/2026: Enjoyable Coding, Social Control Media Considered Harmful, and Recursive Rectangular Subdivision
Links for the day
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Sunday, November 15, 2026
IRC logs for Sunday, November 15, 2026
Cusp of Collapse
NVIDIA Corp (NASDAQ: NVDA) is set to open in the red tomorrow
Getting Fed Up Not Only With Microsoft But Also Windows
This morning we wrote about North America
Layoffs and Silent Layoffs (e.g. PIPs) as a "Break" From IBM
If the press doesn't report it, then it never happened, right?
Microsoft XBox at 25 and All-Time Low
XBox will be "officially" dead (not the brand) when sales fall below some threshold and then production is halted, sort of like Apple's Vision Pro
Links 15/11/2026: Microsoft Already Emitting Chaff to Distract From Its Catastrophe, Jensen Huang Deemed Just 'Fall Guy' Amid Collapse of the Pyramid Scheme
Links for the day
Gemini Links 15/11/2026: CD Players Live on and Self-Hosting from Home Fallacy
Links for the day
Techrights Hates Slop Bots
They benefit nobody
The Economy is Fine! (If Only for China!)
The future is slop! If not, then it's China's fault! It's "sabotaging" the "Western hey hi" in this "hey hi arms race!"
"IT" as "Musical Chairs" (on the Deck of The Titanic)
Each generation will get worse for "IT"
Salesforce in Trouble, Debt Nearly Quadrupled in 9 Months
Salesforce is perishing in a deep pool of debt
"Microsoft is Next IBM"
The words of a Microsoft insider and responses to that
IRC is Decentralised
Bye, Microsoft Teams/Skype
Links 15/11/2026: Murdoch's "WSJ Buries Stephen Miller's Racism" and "America Has Entered a New Age of Propaganda"
Links for the day
In the UK, GNU/Linux Usage Soared During Microsoft Downtime
since the massive outage GNU/Linux usage soared to over 10%
Google Slop About Richard Stallman Shows Stallman Was Right, LLMs are BS Generators
Google slop is the "new Google"
Spouse of Garrett Needs to Get "Several Firearms" to Feel Safe Amid Divorce (Garrett Has a "Girlfriend" Now)
Seems like Isis and my wife have a lot in common when it comes to Garrett
Vista 11 is Small
Can Microsoft survive the fall of Windows?
Six Richard Stallman and FSF Talks This Month (FSF Staff at Ohio State University)
Dr. Stallman's talks in Ecuador are well timed because of the collapse of the LLMs (slop) pyramid scheme
NVIDIA's Crisis Has Only Just began
NVIDIA Corp (NASDAQ: NVDA) is set to open in the red tomorrow
IBM Has Destroyed Red Hat and Hashicorp, Insiders Say It's the Usual From IBM:
Bluewashing is a death wave
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Saturday, November 14, 2026
IRC logs for Saturday, November 14, 2026
Techrights Was Right About Slop Destroying Development Communities and Projects
Slop does not improve your project. It kills the community. Without community, what is left? A 'botfarm'?
Intercontinental Brigading - Part XXXXXI - Harassment Law and "Things Are Unfairly Asymmetric" (Exploring the Boundaries of Death Threats and Various Threats From America)
the sort of "technofascism" that our country must learn to confront rather than facilitate
Gemini Links 15/11/2026: "The Bastards Can Never Win" and "The Last Low-Tech Generation"
Links for the day
Links 14/11/2026: Wuhan Corruption and "Aid Isn’t Reaching Ebola’s Epicenter"
Links for the day
Rahul Kumar Has Turned tecadmin.net Into a Slopfarm That Promotes Slop and Microsoft (as Usual)
Slop promoting slop - a death knell of once-active "Linux" sites
Large-Scale Layoffs - Not Just PIPs - at Red Hat and IBM This Month
Mainstream media has quit covering mass layoffs
Links 14/11/2026: "The Claude Delusion" and "The Microsoft Outage is a Warning for the World"
Links for the day
Ethics in Perspective, Free Software and Morality
top clients of Jeffrey Epstein are one happy family
Richard Stallman (RMS) at Universidad Central del Ecuador (Guayaquil), Cuenca, Campus Sur Universidad Politecnica Salesiana (Quito), and Ohio State University
Long live the message and mission of RMS
They Paid Workers in 'Shares' (That Lost Almost Half Their Value in One Month)
Welcome back 1999 or 2007
The Register MS Made Millions of Pounds by Participating in the Slop Hype Campaign (It's Still Doing It), Now It Admits That It's Just a Bubble
the slop frenzy played a role in the Microsoft meltdown
Intercontinental Brigading - Part XXXXX - Pyramid Schemes (Planned Plunder) and Canceled/Botched Surgeries Aren't "Funny", They Cause Serious Harm and Distress
We were right about Microsoft
Links 14/11/2026: "OpenAI Is Sustaining Enormous Losses" and Slop "Loses the Popular Vote"
Links for the day
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Friday, November 13, 2026
IRC logs for Friday, November 13, 2026
Gemini Links 14/11/2026: Code of Conduct, Back to Gemini, and Gemlog to Inbox
Links for the day