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

Today The Register MS Showed Loyalty to the Pyramid Scheme With Homage of Paid Spam About "AI"
The Register MS is disavowed by its founder, who died a few years ago (The Register MS didn't even mention this)
Intercontinental Brigading - Part XXXXXV - Acts of Hypocrisy (Doing What You Accuse Others of Doing)
connected to my criticism of "Restricted Boot"
 
Links 19/11/2026: "Ignorance Has Taken Over" and "Apocalypse Now, Again"
Links for the day
Richard Stallman Still Insists "They" is Plural, Suggests "Perse" Instead
this week
New Video Explains Why Software Patents Are Evil ("Why Software Patents Spark So Much Frustration")
Maybe some patent examiners (who don't mind a Facebook URL) can take a look
Intercontinental Brigading - Part XXXXXVI - Never Showing Up for Their Own Hearings, Just Paying Hired Guns in London to Act as Fall Guys and Proxies With No Comprehension of the Technical Issues (and Sometimes by Bullying Our Lawyers)
Without any qualifications in the subject at hand
Compatible With Software of 30 Years Ago
Old is not bad, sometimes old is better
NVIDIA Corporation Does Not Look Healthy
The bubble will be hard to re-inflate
Gemini Links 19/11/2026: Thinking About Thinking and Discord
Links for the day
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Wednesday, November 18, 2026
IRC logs for Wednesday, November 18, 2026
Lots of IBM Layoffs in Slovakia This Year
Slovakia and Europe at large
There May be Little or No Future for IBM Consulting
IBM is believed to be run by parasites
At Least Three RMS Talks Next Month in Mexico (Richard Stallman Has 8+ Talks in a Month)
And also - possibly with slop - in social control media
Mass Layoffs at Salesforce Foretold by Techrights
Salesforce is dead meat and it's not alone
Gemini Links 18/11/2026: Creativity, MFA Hype, and Presto Music
Links for the day
Links 18/11/2026: More GAFAM/Apple 'Clown Computing' Outages and Deutsche Bank Leak, Banks' Downtimes
Links for the day
Staff Union of the European Patent Office (SUEPO) Plans General Assembly Next Week, Vote Planned to Approve 7+ More Months of Strikes
The "Agenda" is the same as what we showed yesterday, but the pattern of the actions varies somewhat
IBM's Red Hat a Microsoft Reseller (Second Day in a Row)
If you want a replacement for Microsoft, look somewhere other than Red Hat
After the Bubble Pops the "AI Experts" (Formerly "Data Scientists" or Whatever) Will Rebrand Themselves Again
Remember blockchains and metaverse?
Links 18/11/2026: "Fossil Fuel Companies Are Undermining Democracy" and "Lawyer Up, Elon"
Links for the day
Mainstream and Establishment Media Trying to Connect "Open Source" to White-Collar Crimes and Scandals at Fraudulent NVIDIA
An associate us said that "MIT lies to smear OSS"
Lawfare Will Continue in 2027
We're dealing with defiant Microsofters who wrongly assume that accurate reporting that causes them distress somehow makes them entitled to money
On the Concept of Moral Obligations to Make the World a Better Place for Everybody
The world generally becomes better when more people challenge the status quo rather than bow down to masters
Nadella Talks About 60,000 Microsoft Workers Having to Decide Whether to Leave (in the Next 2-3 Weeks), They've Been Put on Notice
Some parts of Microsoft are poised for severe cuts
IBM Moved From Selling Technology to Selling Its Buildings
IBM is trying very hard to silence/crush critics
Staff Union of the European Patent Office (SUEPO) Looking to Extend Industrial Actions and Strikes to Almost 1.5 Years
It says a lot about the media that for 1.5 years staff is on strike in the second-largest organisation in Europe and the media pretends it's not happening
Richard Stallman's Talk in Quito This Week (At Least 5 Talks After That)
He's having a busy end of year
Gemini Links 18/11/2026: "Love For Old Devices" and New Software/Slop-ware Releases
Links for the day
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Tuesday, November 17, 2026
IRC logs for Tuesday, November 17, 2026
Gemini Links 17/11/2026: The RAM Question and Lagrange Sync
Links for the day
EPO Strikes to Continue Until Summer of 2027 (If Not Further) Based on Existing Plan
It'll never end until the dictatorship ends
Intercontinental Brigading - Part XXXXXIV - Hostility Towards Media, Coming From People Who Promote Microsoft Back Doors and Engage in Mass Plagiarism, Attack Women Etc.
The core issue or the seminal issue is Microsoft as the "master" of all computers
Trading 212 UK Limited Acting Like a Scam, FCA Says It's Legitimate
If this was some coy prank or a scam, it is certainly not funny
Richard Stallman's Talk Earlier Today and Next Month's Appearance in Mexico
He seems to have managed to dodge the 'cancel mob' for quite some time now
The Cost of Losing Integrity at The Register MS
Recently we learned that they make a "ton of money" out of their Huawei spam
Links 17/11/2026: Jensen Huang's Price-Fixing Story, "Russian Attacks Aimed At 'Breaking The Spirit' Of Ukrainians"
Links for the day
NVIDIA Continues Diving and Press Reports Speak of Business Crimes of Jensen Huang (Not China or Sex)
The deeper they go...
Gemini Links 17/11/2026: Super Power, Knowember, Writing in Shorthand, Cooking over a Woodstove, Decoupling Code and Content
Links for the day
Links 17/11/2026: California Sues Slop Peddlers and Nvidia Was Already in Trouble Before the Jensen Huang Mess
Links for the day
An American and South Korean Cartel Artificially Inflating the Prices You Pay for Computers (or Any Service That Relies on Computers, I.e. Almost Everything)
As long as the principal tenant of the White House is a white-collar criminal we can expect only cover-up and participation, not a crackdown
NVIDIA Corp Was Grossly Overvalued, Lost 36.06% of Alleged "Market Value" in 5-6 Weeks
NVIDIA has many of "obligations" (to pay), not money
Over at Tux Machines...
GNU/Linux news for the past day
IRC Proceedings: Monday, November 16, 2026
IRC logs for Monday, November 16, 2026
The EPO Still on Strike. 141 Tickets Opened Regarding Lack of Toilet Paper (or Similar).
Yesterday staff representatives at the EPO in The Hague (LSCTH] spoke of a meeting which took place a month ago
Intercontinental Brigading - Part XXXXXIII - An Attack on the Dignity of Reporters and Their Family Members (by Proxy/Attack Dogs)
The Microsofters seem to be super-upset that I uncovered Microsoft fraud
IBM and OSI Said opensource.net Would Replace opensource.com, But It Has Been Dead for 1.5 Years and the Person Who Had Made Promises Left OSI
Over a year ago he left
Red Hat and IBM Meet Targets (of Pushing People Out)
now there are claims of security breach inside IBM, but no press reports related to that
Gemini Links 17/11/2026: Reading Clocks and StreetComplete
Links for the day