Who owns the machine?

The cloud is someone else’s computer

Your email, photos, and group chats live in data centers owned by a few large companies. “The cloud” makes this sound weightless, but it’s a building full of computers, and whoever owns them sets the terms. This essay asks who owns the machine, and why it matters.

Langdon Winner’s answer to “Do Artifacts Have Politics?” was yes. Some technologies require a certain social order to run them: a nuclear plant needs centralized, hierarchical control, and a rooftop solar panel doesn’t. Computing is the same. Routing everyone’s data through one company’s servers produces one kind of power; a network of small servers run by households and neighborhoods produces another.

Free software won, and lost

In “Freedom in the Cloud” (2010), Eben Moglen pointed out that free software had largely won, but users’ data had moved onto servers they didn’t control, where every click and message was logged. Free code on your laptop didn’t help when the important part happened on someone else’s machine. His answer was small, cheap servers in people’s homes, running free software and federating with each other. That became the FreedomBox project, and it is the starting point for this blog’s guides.

Tools you can understand

Ursula Franklin distinguished holistic from prescriptive technologies. In holistic work, like a potter’s, the person doing it controls the whole process. In prescriptive work, someone else sets the steps. Most platforms are prescriptive: you use the features they offer, the way they allow. Ivan Illich called for convivial tools that people can understand, use, and adapt. A small server running well-documented software is convivial: you can open it up, change it, and fix it.

People stay on platforms anyway because of switching costs, as Cory Doctorow argues in The Internet Con. Leaving means leaving your contacts, history, and community behind. Open protocols and federation lower those costs and let a community server talk to the rest of the world instead of becoming an island.

Owning it isn’t enough

A server where one person holds every password is still a small platform, just with a friendly owner. Once other people depend on it, the question changes from who owns the machine to who decides how it’s run. One pattern follows here, about the system itself. The rule it leads to, Two Keyholders, is about who holds which role, so it’s introduced in the governance piece, Who holds root?.

Patterns introduced

Small Enough to Understand

Illich and Franklin point the same way: people can only control what they can understand. A server only one expert can follow is prescriptive technology with a friendlier face, and members can’t fix it or take part in decisions about it.

Therefore: keep the system small enough that a second member could learn to run it in a weekend, by adding complexity only when a real need appears.

How the patterns fit together

Small Enough to Understand is the larger pattern: a second keyholder is only realistic if the system is small enough to learn. Two Keyholders, introduced in Who holds root?, completes it. Talk Before You Enforce, from the institutions thread, completes Two Keyholders: people who share power need a way to settle problems together.

From theory to practice

• The guide builds a small, understandable server: one machine, plain Debian, a few standard tools.
• The governance piece introduces Two Keyholders and applies Talk Before You Enforce, turning both into rules and a charter a group can adopt.