LOG-022 ·
Email: The Decentralized Network That Already Won
Federation is not a theory. You have been using it since 1982, and its history contains both the proof and the warning for everything being built now.
- Words
- 721
- Est. read
- 3.1 min
- Confidence
- 0.95
- Topics
- federation, email, history
People discussing decentralized networks talk as if the concept were unproven, a promising architecture awaiting its first success at civilizational scale. The success is in your pocket, delivering receipts and newsletters. Email is a fully federated, vendor-neutral, planetary message network, running continuously since before most of its users were born, and it embodies both the strongest proof and the sharpest warning in the entire decentralization portfolio. Today's entry is the explainer, because federation is the primitive underneath half of what this log discusses.
Federation, defined by the thing you already use
You have an address at one provider. Your accountant has an address at another. Neither of you ever agreed on a company, signed the same terms, or created accounts on the same platform, and yet the message arrives in seconds. That is federation: independent operators, running independent servers, interoperating through a shared protocol that no one owns.
Contrast every messaging app on your phone, where both parties must join the same company's system, and the network's roster of members is a corporate asset. The difference is not cosmetic; it is who holds the exit. My email address is at my own domain, so I have changed the company behind it (twice now) without telling a single correspondent. Try changing messenger apps without herding every contact you have through the move. The group chat is a hub. Email is a mesh. You feel the difference only when you try to leave, which is exactly when it is too late to matter.
The numbers deserve respect: roughly 4.5 billion users, on the order of 350 billion messages daily, across millions of independent servers, with no headquarters, no CEO, and no off switch. It is the largest decentralized system ever built, and its uptime as a network (not any one provider, the network) is effectively unbroken since 1982. When people ask whether federation can scale, the honest answer is that it is the only architecture that demonstrably has.
The warning in the same dataset
Now the part the enthusiasts skip, because this log does not. Email's protocol remained open while its operation quietly centralized. Depending on whose measurement you take, two companies now handle mail for a large fraction of all mailboxes, and the market share of the leader alone is routinely estimated near a third or more. The protocol says anyone can run a server. The spam-reputation regime says: good luck. I run my own mail infrastructure and I keep logs, so here is the lived number: deliverability of mail from my well-configured, correctly authenticated server required weeks of reputation warm-up, and even now a new large-provider policy change can send my messages to spam folders for reasons no error message will ever explain.
This is the pattern I want the current generation of federated networks to study like scripture: an open protocol does not guarantee a decentralized outcome. Centralization re-emerges through operational convenience (running a mail server is work), through economies of scale, and through trust mechanisms (spam filtering) that structurally favor incumbents. The decentralization of a system is a distribution to be measured continuously, not a property to be declared at the protocol's birth. I made this point with grades in the entry on decentralized social; email is the fifty-year longitudinal study backing it.
The scoreboard
| Property | Typical messenger | |
|---|---|---|
| Choose your provider | Yes, any of millions | No |
| Keep identity when switching | Yes (own domain) | No |
| Two networks interoperate | Structurally | Rarely, reluctantly |
| Can be shut down by one company | No | Yes |
| Operationally concentrated anyway | Increasingly (the warning) | Totally |
What I take from the winner
Three instructions, extracted from four decades of data. First: federation works at any scale humanity has yet required, so build on it without apology. Second: your address should live at a domain you control, because the domain is the exit right; this single move (mine cost $54/year, migration measured at 6.5 hours in the original audit) converts your most-used federated identity from captive to portable. Third: openness requires maintenance. The moment participation becomes operationally expensive, the network re-centralizes around whoever can afford the operations, protocol be damned.
Confidence that email, in recognizably federated form, outlives every centralized messenger currently installed on my phone: 0.95. It has already outlived several dozen of their predecessors. The tortoise is 44 years old and delivers 350 billion messages a day.