In 1980, at the MIT Artificial Intelligence Lab, a printer jammed.

This was not unusual. Printers jam. What was unusual was the man it annoyed, and what he decided to do about it.

Richard Stallman was a programmer in the lab, and the lab had recently been given a new laser printer by Xerox. A good machine. Fast. It also had a habit the old one shared: it jammed quietly, on a different floor, and left people waiting on pages that would never arrive. The old printer had the same flaw, but Stallman had fixed the social half of the problem. He had the source code, so he rewrote it. He made the machine send a message when it jammed, and tell you when your job was done. A small thing. A neighbourly thing.

The new printer came with no source code. So he set out to get it the way he always had, by asking. He learned that a researcher at Carnegie Mellon had a copy. He went to ask. And the researcher said no. He had signed a non-disclosure agreement with Xerox. He was not allowed to share.

That was the moment. Not the jam. The no.

Because the no was new. Stallman had grown up inside a culture where code was something you shared the way you share directions with a stranger, automatically, without mistaking it for generosity. Now a colleague, a fellow researcher, was telling him he had promised not to help. The promise was the product. Xerox had not just sold a printer. It had bought a man’s willingness to cooperate with the people around him.

He was not trying to start a movement. He was trying to fix a printer.

But he had seen the fence going up. And once you see a fence, you cannot unsee where it runs.

the commons before the fence#

Before software was a product, it was a practice.

Code came bundled with the machine, or printed in journals, or passed hand to hand between people who assumed the next person would read it. The first programmers were academics and engineers, and they wrote the way scientists publish. You showed your work. Someone built on it. That was not generosity. It was the method. A field where nobody could read anyone else’s code would not have been a field at all.

Unix is the cleanest example. Ken Thompson and Dennis Ritchie built it at Bell Labs around 1970, and because AT&T was barred at the time from selling computer products, it could not turn Unix into a business. So it licensed the system to universities, cheaply, with the source included. An entire generation of computer scientists learned how an operating system actually works by reading the one in front of them. Berkeley took that source, improved it, and gave the improvements back. The system got better because everyone could see inside it.

There was a name for the people who lived this way, though they did not choose it as a brand. Hackers. Not in the sense the news later ruined. In the original sense: someone who wants to know how the thing works, who believes access should be open, who judges a person by what they can build rather than the credentials they carry, and who treats a useful piece of code as something you pass on. Sharing was the default. Hoarding was the aberration.

Then the fence went up.

Software stopped being something you read and became something you bought. The binary shipped. The source stayed home. When the legal constraints on AT&T lifted, the Unix that had been almost free became expensive and guarded, and the licensing that once invited you in started keeping you out. The commons did not vanish in a single act. It was enclosed the way commons always are. Quietly, parcel by parcel, one non-disclosure agreement at a time.

Stallman had not seen one fence post. He had seen the line it belonged to.

free as in freedom#

Stallman’s response was not a protest. It was a replacement.

In September 1983 he posted a message to a Usenet group announcing that he would build a complete operating system, free, compatible with Unix, that anyone could use, read, change, and share. He called it GNU, a recursive joke that unfolds forever: GNU’s Not Unix. A few months later he left his job at MIT, partly so the university could never turn around, claim what he built, and lock it away. In 1985 he founded the Free Software Foundation and wrote the manifesto that named the thing he was defending.

The word free was the problem from the start, and it still is. English collapses two different ideas into one syllable. Stallman drew the line that has held ever since. Free as in freedom, not free as in beer. The point was never the price. You can sell free software. The point was control, and he spelled out exactly what control meant in four freedoms, numbered from zero the way a programmer counts.

The freedom to run the program however you want. The freedom to study how it works, which is impossible without the source. The freedom to share copies with the people around you. And the freedom to change it and pass on what you changed. Strip those away and you do not own the software. You are renting permission, on terms someone else writes and can revoke.

Then came the part that is genuinely clever, the part you have to admire even if you do not care about software at all.

Copyright exists to restrict copying. Stallman took that exact instrument and inverted it. The GNU General Public License uses the full force of copyright law, not to lock the code down, but to keep it open permanently. If you distribute software covered by it, you must pass on the same freedoms you received, source included. You cannot take the commons, improve it, and quietly fence the result. The licence forces it back open. He called it copyleft. It does not fight the legal system that enables enclosure. It turns that system against its own intent and makes freedom self-perpetuating.

This is the same move that runs through everything I write here. You do not win by destroying the machine. You win by using its own mechanisms to build something it cannot reach. Cryptography did it with mathematics. Bitcoin did it with proof. Stallman did it first, with a licence.

The idealist had drawn the map. What the map needed now was a kernel.

just a hobby#

In August 1991, a twenty-one-year-old student in Helsinki posted a message to a Usenet group about a project he was building in his spare time. He wanted to be modest about it. He undersold it so completely that the line became legend.

He described it as just a hobby, won’t be big and professional like gnu.

He was wrong in the most spectacular way a person has ever been wrong about their own work. The hobby became the most widely deployed software in human history. It runs the servers behind almost every site you visit. It runs every Android phone on earth. It runs the supercomputers, the stock exchanges, the spacecraft, the routers, the machines the internet itself is made of. Linus Torvalds set out to write a toy to understand his own processor. He wrote the kernel the modern world runs on.

Why he wrote it at all is the part that matters here. He had been using MINIX, a small Unix-like system built for teaching, and he was hemmed in by its licensing. He could look but he could not truly build. The constraint annoyed him the same way the printer annoyed Stallman a decade earlier. So he started writing his own.

The first versions of Linux carried a licence of Torvalds’ own making, and it was restrictive. You could not sell it. Then in 1992 he made the decision the whole story turns on. He relicensed Linux under Stallman’s GPL. He later called it the best thing he ever did, and he was right, because that single choice is what let two halves of a machine find each other.

GNU had everything except a kernel. Years of work. The compiler, the shell, the utilities, the entire body of a free operating system, waiting for a heart that had not arrived. The GNU kernel was perpetually almost finished. And here was Linux, a working kernel with no body to move. Put under the same licence, they fit together like they had been designed apart on purpose. The idealist’s tools and the pragmatist’s kernel became one system. This is why some people still insist on calling it GNU/Linux, and they are not wrong to.

The two men were nothing alike. Stallman is a philosopher who happens to write code. Torvalds is an engineer who finds philosophy tiresome and says so. One built a movement to defend a principle. The other built a kernel because the existing one annoyed him. In 1998 a group reframed the whole thing in business-friendly language and called it open source, dropping the word freedom precisely because it unsettled companies. Stallman objected, and his objection was correct. They objected back, and they were also correct.

Because the thing needed both of them. Idealism without pragmatism is a manifesto nobody runs. Pragmatism without idealism is a free tool with no reason not to be fenced again. The principle keeps the soul. The pragmatism wins the world. You do not get to keep only the half you find more comfortable.

the cyberpunk thread#

None of this was happening in a vacuum.

While Stallman was writing licences and Torvalds was writing kernels, a culture was forming around the same nerve. It showed up in fiction first. In 1984 William Gibson published Neuromancer and gave a name to a feeling people already had. A world of high technology and low autonomy, vast corporations running systems no individual could see inside, and a particular kind of person who refused to accept that as the end of the story. The console cowboy. The operator who jacks into the machine not to obey it but to move through it on his own terms.

The aesthetic came later, and it swallowed the meaning the way aesthetics do. Neon. Trench coats. Rain on glass. People remember the look and forget the look was downstream of a politics. Cyberpunk was never about how it looked. It was a stance toward power. High technology in the hands of the people the system was built to manage. The lone figure against the opaque structure, carving out a space to act, to think, to be unseen.

The same year Gibson published his novel, Stewart Brand stood at the first Hackers Conference and said the line everyone half-remembers. Information wants to be free. What gets forgotten is that he said it as a tension, not a slogan. Information wants to be expensive because it is valuable, and information wants to be free because the cost of moving it keeps falling, and those two forces are at war. The half that survived in the culture was the half that felt like a demand. Free. Because the people who heard it were already living the other half in their bones.

The cypherpunks were the most disciplined expression of it. I have written about them already, the mailing list, the manifesto, the belief that privacy is asserted through mathematics and not granted by law. That is the cyberpunk stance with the romance stripped out and the engineering left in. Do not ask the system for permission. Build the thing that makes permission irrelevant.

I lived a small version of all of it without knowing the names. The internet cafes in the mid-nineties, the dial-up handshakes, the feeling of slipping through a wall the state had built and out into something borderless. I called none of it cyberpunk at the time. I just knew it felt like the only honest room in the building.

Here is what connects every thread. FOSS, the cypherpunks, the console cowboy, the hacker ethic. They are not a style you adopt to stay current. They are what happens when the reality you are handed stops fitting, and you decide to do something about it instead of adjusting yourself to the discomfort. You do not move to free software to be on the right side of a trend. The trend is irrelevant. You move because you have looked closely at what the alternative actually is, and you can no longer unsee it.

That is the part that matters. Not the tool. The reason for the tool.

no black boxes#

Here is the sentence the whole blog rests on, and I have been circling it since the first post.

You cannot be sovereign on a black box.

Everything I write about depends on software. Encrypted messages run on software. Your keys live on software. Sovereign money, sovereign identity, the entire parallel architecture I keep describing, all of it sits on top of code you can either inspect or you cannot. And if you cannot inspect it, then every guarantee underneath it is a promise made by someone you have never met, with interests you cannot see, that you have no way to check. Privacy on a black box is a rumour. Privacy you can verify is a property.

This is the same idea at the heart of the cryptography piece, moved down one floor. There I wrote that Bitcoin replaces trust with proof. The math does not care who you are or what a court says. Free software is that principle applied to the tools themselves. Proprietary software asks you to trust it. Run this, accept the terms, believe it does what we say and nothing more. You cannot read it. You cannot check. A closed binary can watch you, report on you, betray you in a hundred quiet ways, and you would never find the evidence, because the evidence is the part they kept.

Open source removes the asking. The source is right there. And here is the part people miss: it does not matter whether you personally read it. I have compiled hundreds of kernels in my life and I still do not read every line of the ones I run. The guarantee was never that you audit it yourself. The guarantee is that anyone can, that thousands do, that the door is open and the light is on and a liar has nowhere to hide. The freedom to look is what keeps the thing honest, even for the people who never look.

I learned this with my hands, on Slackware, the distribution that refuses to hide anything from you and makes you assemble your own understanding piece by piece. I compiled kernel after kernel, choosing what went in and what stayed out, not because I had to but because I could, and because the difference between using a machine and owning one turns out to be exactly that. Later, running infrastructure for an ISP, the same system stopped being a preference and became load-bearing. A whole city’s connection ran on software you could read all the way down. That is not a hobby. That is a foundation.

And this is where it stops being technical and becomes something closer to the bone.

An open system has no observer built into it. A black box does, by design. It phones home. It reports. It moderates. It optimises you toward whatever serves the people who built it. The open machine does not, and more than that, you can prove it does not. It is the digital version of a room with no judge in it. A place where you get to be right or wrong and the polarity does not matter, because nothing is recording the verdict and no one is keeping score. That is what was taken. Not convenience. Not capability. The unwatched room. The only honest space where a person actually becomes themselves.

True sovereignty is not a setting you enable. It is the condition of standing on ground you can see all the way down to the bottom. Open source is the only ground that lets you look.

the daily driver#

I have run Linux near me for almost thirty years.

Not as a project. Not as a position I defend at dinner. Just as a fact about how I work, the way some people always keep a particular knife in the kitchen. Through the internet cafe, through the ISP, through the company I built and the consultancy after it and the security work that followed, the constant underneath all of it was the same. Whatever the job asked of me, there was a Linux machine within reach doing the real work. I did not keep choosing it. By a certain point it had simply become true about me.

This is what I mean when I say Linux is a practice and not an alternative. An alternative is something you switch to, and could switch back from, when a better deal comes along. A practice is something you do, repeatedly, because it expresses what you actually believe. You do not run free software to dodge a licence fee. You run it because the relationship it offers you, open, inspectable, yours, is the only relationship with a machine that matches how you want to stand in the world. The operating system stops being a product you consume and becomes a discipline you keep.

I am deliberately not going to tell you which distribution to run, because the question is a trap and the answer does not matter. There are hundreds of them. That abundance is not chaos to be tidied up. It is the four freedoms made visible. Anyone can take the work, reshape it, rename it, and hand it on, which is why no single company owns the ground and no single decision can fence it. The right distribution is the one that fits your hands and your values, and the only way to find it is to use a few and notice which one disappears into the work. For the record, and not as advice, I run Fedora on the laptop and Pop!_OS on the desktop, and I am watching where the Cosmic desktop goes with real interest. That is my answer, not yours.

It will ask something of you. That part is honest, so I will be honest about it. There are afternoons where something does not work and the path back is not obvious. But that friction is not a defect to apologise for. Convenience was the entire mechanism of the trade I wrote about at the start of this blog, the comfort that quietly takes the thing it is charging you for. A little honest friction is the texture of actually owning something. It is the difference between living in a house and renting a room you are not allowed to see the wiring of.

the fences you stopped seeing#

You are probably never going to compile a kernel. That is fine. This was never really a piece about software.

Stallman did not set out to change the world. He set out to fix a printer, and in being told no, he saw a fence going up around something that used to be open. The whole movement, GNU, the GPL, Linux, the parallel world I keep mapping on this blog, all of it grew from one man recognising a single fence post and understanding the line it belonged to.

So here is the question the printer leaves you with. How much of your own life runs on machines you have never opened and could not open if you tried?

Your money sits inside institutions whose ledgers you are not allowed to read, governed by rules you did not write and cannot see. Your sense of what is happening in the world arrives through a feed whose logic is hidden from you, a system that decides what you look at and therefore, slowly, what you think about. Your sense of who you are is increasingly shaped by something optimising for your attention rather than your growth, handing you a mirror every time you reached for a window. These are black boxes too. You trust them for the same reasons you trust closed software. Checking feels impossible. The convenience is real. Everyone else already has.

That is the trade I described in the very first essay here. The comfort that quietly takes the thing it is charging you for. It does not feel like a fence while it is being built. It feels like a feature.

Free software is small next to all of that. One operating system. A way of running a laptop. But it is a rehearsal. It is the discipline of insisting on seeing the floor, practised on the one surface where seeing the floor is still possible. And the thing that happens, the thing I did not expect back when I was compiling kernels for no reason but that I could, is that the eye does not stay on the laptop. Once you know what it feels like to stand on ground you can inspect all the way down, you start to notice every place you cannot. You start to feel the fences. The unease you carry about the digital world you live in now is not a sign that you have failed to adapt. It is the opposite. It is the last working part of an immune system that has recognised something foreign and is trying to tell you.

I am not going to tell you what to do about it. That has never been how this works, and anyone selling you a single answer is selling you another box to trust. There is no clean exit and no product that grants you sovereignty. There is only the eye, once you have it, and the slow refusal to mistake the walls for the horizon.

So look at the things you depend on and ask the only question that matters. Can I see inside this, or am I simply trusting that I should?

Stallman asked it about a printer.

You can ask it about your whole life.