Introduction
Email is one of the clearest examples of how a decentralized system can gradually become centralized over time.
At the protocol level, email was designed to be open and decentralized:
- anyone could run a server,
- anyone could communicate with anyone else,
- and no central authority controlled the network.
Protocols like SMTP and IMAP created a universal communication layer that belonged to the internet itself rather than to a single corporation.
Yet despite this architecture, email eventually became dominated by centralized platforms such as Gmail and Microsoft Outlook.
This shift did not happen because decentralized email stopped working technically.
It happened because decentralized systems struggle when critical social and operational problems are not solved directly at the protocol layer.
Spam was one of those problems.
But beneath the spam problem lies something even deeper:
privacy.
The moment privacy disappears from a communication system, usability changes completely.
And once usability changes, users begin demanding centralized protection layers to compensate.
Email Was Built for a Different Internet
Early email protocols assumed a relatively cooperative environment.
The original internet was small:
- universities,
- research institutions,
- technical communities,
- and trusted operators.
SMTP was intentionally simple.
A mail server could announce itself and send messages to another server with very little verification.
This openness was a feature, not a flaw.
The philosophy of the early internet prioritized:
- interoperability,
- openness,
- permissionless participation,
- and decentralization.
But the system depended heavily on implicit trust.
There was very little:
- identity verification,
- sender authentication,
- rate limiting,
- or reputation enforcement.
As long as the network remained relatively small and socially cohesive, this worked surprisingly well.
However, once email became global, the environment changed dramatically.
Spam Was Not Just Noise — It Was a Privacy Collapse
Spam is often treated as merely an annoyance.
But in reality, spam represents a breakdown of informational boundaries and privacy expectations.
When anyone can:
- contact anyone,
- monitor behavioral responses,
- mass-target users,
- scrape addresses,
- and algorithmically optimize manipulation,
communication itself changes.
The inbox stops being a protected personal space and becomes an adversarial environment.
This radically alters usability.
Without strong privacy protections:
- users receive unwanted attention constantly,
- malicious actors can profile and target individuals,
- communication becomes noisy and cognitively expensive,
- and trust in unsolicited interaction collapses.
The result is that openness becomes difficult to use safely.
This is a critical insight:
privacy is not merely an ethical or political concern.
Privacy directly affects usability.
A system without privacy eventually becomes operationally hostile to ordinary users.
The Usability Shift
As spam exploded, users no longer wanted pure protocol freedom.
They wanted:
- filtering,
- curation,
- reputation systems,
- protection,
- and convenience.
This is where centralized providers gained power.
Companies like Gmail solved problems that the decentralized protocol itself did not solve:
- machine-learning spam filters,
- phishing detection,
- sender reputation,
- automatic categorization,
- account recovery,
- abuse prevention.
These features dramatically improved usability.
And importantly, they improved usability specifically because the underlying environment had become insufficiently private and too adversarial.
In other words:
once privacy deteriorated, users increasingly depended on centralized intelligence layers to navigate the system safely.
This dependency accelerated centralization.
Centralization Emerges Through Trust Aggregation
Gmail did not centralize email by replacing SMTP.
SMTP still exists.
Instead, Gmail centralized:
- trust,
- reputation,
- filtering,
- and usability infrastructure.
This distinction matters.
The protocol remained decentralized in theory, but the practical ability to participate increasingly depended on centralized actors.
Large providers accumulated enormous advantages:
- more behavioral data,
- better spam classification,
- stronger reputation systems,
- and network-wide visibility.
Smaller independent servers could not compete easily.
Eventually, centralized providers became gatekeepers of legitimacy.
They began:
- blacklisting servers,
- rejecting suspicious senders,
- enforcing authentication standards,
- and determining deliverability.
At that point, the decentralized protocol still existed technically, but effective participation increasingly required alignment with centralized trust systems.
Privacy and the Need for Mediation
The deeper lesson is that systems without strong native privacy protections tend to require stronger intermediaries.
Why?
Because users cannot safely process unlimited untrusted interaction on their own.
Without privacy boundaries:
- attack surfaces increase,
- spam scales,
- manipulation scales,
- surveillance scales,
- and cognitive overload scales.
Users then seek protection from entities capable of:
- filtering information,
- evaluating trust,
- suppressing abuse,
- and managing risk.
This naturally favors centralization.
Centralized systems become attractive not because users necessarily desire control, but because users desire relief from adversarial complexity.
In this sense, the erosion of privacy changes usability so fundamentally that centralization begins to feel necessary.
The Pattern Reappears Everywhere
The email story is not unique.
The same dynamic appears repeatedly in digital systems:
- social media moderation,
- app store governance,
- payment fraud prevention,
- identity systems,
- AI platforms,
- and messaging infrastructure.
Whenever privacy and trust are weak at the protocol layer, operational burdens shift upward.
Then centralized intermediaries emerge to manage:
- abuse,
- verification,
- coordination,
- and usability.
This creates a recurring historical pattern:
- Open decentralized infrastructure emerges.
- Abuse scales faster than native protections.
- Usability deteriorates.
- Centralized actors solve the coordination problem.
- Users migrate toward convenience and safety.
- Trust becomes centralized even if the protocol remains open.
Why This Matters for Modern Decentralized Systems
Modern decentralized technologies often focus heavily on openness while underestimating the importance of privacy-preserving usability.
But usability is not neutral.
A radically transparent system creates radically different user behavior.
If every action is globally visible:
- profiling becomes easy,
- spam becomes easier,
- targeting becomes easier,
- manipulation becomes easier,
- and surveillance becomes structural.
Users eventually demand mediation layers to cope with that environment.
And those mediation layers tend to centralize.
The lesson from email is therefore not simply:
“spam caused centralization.”
The deeper lesson is:
when privacy collapses, usability changes so dramatically that centralized coordination layers become increasingly attractive and eventually dominant.
Conclusion
Email began as one of the internet’s most successful decentralized systems.
Yet over time, spam, abuse, and usability challenges pushed users toward centralized providers that could offer filtering, trust, and protection at scale.
This was not merely a technical evolution.
It reflected a deeper structural reality:
privacy and usability are tightly connected.
When privacy disappears, users become exposed to adversarial environments that are difficult to navigate independently.
Centralized intermediaries then emerge to restore usability through filtering, reputation, and trust management.
The protocol may remain decentralized, but the practical experience becomes centralized.
The history of email therefore demonstrates a crucial principle for all modern decentralized systems:
without strong native privacy protections, decentralization alone is often insufficient to preserve meaningful user autonomy.
This thought leadership article was written by Mališa Pušonja, CPO at Curvy.