Locking the Web Open
In 2015, Brewster Kahle — founder of the Internet Archive — published "Locking the Web Open: A Call for a Distributed Web." The title named both a problem and a method. The problem: the web had drifted toward centralization, with a handful of platforms controlling the infrastructure billions of people depended on for memory, communication, and identity. The method: distribute the layers — storage, naming, communication — so that no single node could be switched off.
Kahle's framing introduced the term distributed web as a technical and political category. It was not merely a peer-to-peer file system (though IPFS — the InterPlanetary File System — would become its most cited implementation). It was a design philosophy: that the web's openness must be locked in at the architectural level, not maintained by the goodwill of platform owners who can and do change their minds.
Content-addressing is the key mechanism. In a location-addressed web, a URL points to a server at a specific address; if the server goes dark, the content vanishes. In a content-addressed web, a hash points to the content itself; any node that holds a copy can serve it. Link rot becomes structurally impossible. Censorship requires erasing every copy simultaneously.
Web 1.0 Was Already There
The distributed web is not a utopian destination — it is closer to a recovery. The hand-built web of the 1990s already operated as a decentralized system. Personal homepages functioned as federated neighborhoods where anyone with hosting capability could publish. Email remains an open protocol enabling interoperability across thousands of independent servers. The early web was not distributed in the technical sense of content-addressing, but it was structurally plural: no single entity owned it.
The deeper question is not how to build decentralized systems — that knowledge already exists and always did. The necessary inquiry is why decentralized systems lost to centralized platforms, and how to prevent that loss from recurring. The answer is not purely technical. Centralization won because convenience, network effects, and venture capital combined to make the platforms frictionless to adopt and catastrophic to leave. The distributed web lost on user experience, not on architecture.
Why Web3 Got It Wrong
The 2017–2022 "Web3" moment promised to solve exactly this problem. Its rhetoric invoked decentralization, user ownership, and escape from platform control. Its reality produced a new generation of platforms that reproduced the identical dynamics of extraction, concentration of power, and vulnerability to shutdowns — now augmented with speculative financialization.
The structural failure was predictable. Web3 projects built decentralized protocols but then wrapped them in centralized interfaces (exchanges, wallets, marketplaces) that became the actual chokepoints. Users interacted with the interface, not the protocol. The distributed layer became invisible plumbing for a reconstituted platform economy. Meanwhile, IPFS itself illustrated a governance problem the Archaeobytology textbook identified plainly: files disappear if no one pins them. The protocol distributes storage, but the incentive to preserve is not distributed.
The lesson is not that distribution is impossible. It is that distribution requires solving coordination problems — who maintains the nodes, who funds the infrastructure, who pins the files — that technical protocols alone cannot resolve.
The Third Way: Owned Ground
Archaeobytology identifies a third path between Web 2.0's centralized platforms and Web3's hollow decentralization: sovereign systems built on genuinely owned infrastructure. The principle is called Owned Ground — users control the infrastructure that hosts their data, through self-hosting, cooperative infrastructure, or genuinely distributed systems where governance matches the architecture.
This is distinct from both the SaaS model (where the company owns the ground and leases access) and the Web3 model (where tokenization creates the illusion of ownership while the interface layer remains extractive). Owned Ground means the data is on your machine, your server, or a cooperative whose members you are — and that it remains yours when the company goes bankrupt, the subscription lapses, or the platform changes its terms.
In the Sovereignty Stack, the distributed web corresponds to Layers 1 and 2: the physical infrastructure and the network protocols that run on it. These layers cannot be owned by the people who use them if they are rented from a landlord-platform. The distributed web, at its most fundamental, is a claim about who owns the ground.
Field Notes — Legibility Without Centralization: "In a distributed web, legibility often comes not from text, but from recognizable patterns of interaction and structure." — Myceloom Loom Archive. The distributed web does not require a central authority to make itself navigable. It requires conventions, protocols, and communities that maintain them — the same things that made early webrings, blogrolls, and mailing lists navigable before the algorithm was invented to do it for us.