The web we know is highly centralized. A handful of companies host most content, provide most services, and control most infrastructure. Decentralized web technologies aim to change this by distributing data and services across many participants. Let’s explore how these systems work and what they mean for privacy and censorship resistance.
The Centralization Problem
Today’s web concentrates power in surprising ways:
Hosting: AWS, Google Cloud, and Azure host much of the web; outages affect huge portions of the internet
DNS: A small number of authorities control domain name resolution
Identity: A few companies manage logins for countless services
Content distribution: CDNs concentrate traffic through limited paths
Search: One company shapes what most people find online
This centralization creates single points of failure, censorship, and surveillance.
IPFS: The InterPlanetary File System
IPFS is a peer-to-peer protocol for storing and sharing content. Unlike HTTP, which addresses content by location (a specific server), IPFS addresses content by what it contains (a cryptographic hash).
This means:
Content can come from any peer that has it
The same content has the same address everywhere
Content can’t be silently modified – the hash would change
Popular content becomes more available, not less, as it spreads
IPFS doesn’t automatically provide privacy – peers can see who requests what content – but it does provide censorship resistance and resilience.
Blockchain-Based Systems
Some decentralized systems use blockchains for coordination:
Ethereum Name Service (ENS): Decentralized alternative to DNS
Decentralized identity (DID): Self-sovereign identity systems
Decentralized storage: Filecoin, Arweave, and Storj for permanent storage
Decentralized social media: Lens Protocol and Farcaster
Blockchains provide tamper-resistant coordination but raise their own privacy concerns due to public ledgers.
The Fediverse
The fediverse is a network of independently operated servers that interoperate through open protocols. Examples include:
Mastodon: Decentralized alternative to Twitter
PeerTube: Decentralized video sharing
Pixelfed: Decentralized image sharing
Lemmy: Decentralized link aggregation
Each server operates independently but federates with others through ActivityPub protocol. Users can interact across servers while no single entity controls the whole network.
Privacy in Decentralized Systems
Decentralization doesn’t automatically provide privacy:
Public by default: Most decentralized social systems are publicly visible by design
Server admin trust: Federated systems still require trusting your home server’s administrator
Permanent records: Blockchain-based systems make data permanent and visible
Network analysis: P2P systems can leak metadata about peer relationships
Privacy must be designed in deliberately; decentralization alone isn’t enough.
Censorship Resistance
One major benefit of decentralization is resistance to censorship:
No single entity can take down content available across many peers
Domain seizures don’t affect content accessible by hash
Server shutdowns don’t eliminate federated content
Country-level blocks become harder to enforce
This benefits both legitimate speech and content that some find objectionable – decentralization is generally content-neutral.
The Self-Hosting Option
Self-hosting your own services is a form of decentralization. Running your own:
Email server
Cloud storage (Nextcloud)
Password manager (Vaultwarden)
Mastodon instance
Git server (Forgejo, Gitea)
This gives you control but requires technical knowledge and ongoing maintenance.
Tradeoffs of Decentralization
Pros:
Censorship resistance
No single point of failure
User control over data
Reduced dependence on large companies
Innovation through open protocols
Cons:
More complex for users
Performance often worse than centralized alternatives
Moderation and abuse harder to address
Privacy must be carefully designed
Network effects favor existing centralized services
Decentralized Identity
Self-sovereign identity systems let you control your digital identity without depending on companies or governments. You can:
Prove attributes without revealing more than necessary
Carry credentials across services
Revoke access without depending on third parties
Maintain consistent identity across decentralized systems
Standards like W3C Verifiable Credentials enable interoperable identity systems.
The Web3 Question
“Web3” sometimes refers to blockchain-based decentralization, sometimes to broader decentralized web concepts. Critics note that much “Web3” infrastructure remains highly centralized despite decentralization rhetoric. Genuine decentralization requires more than blockchain technology.
Practical Engagement with Decentralization
Ways to participate:
Try Mastodon or other fediverse services: Experience federated social media
Use IPFS for content distribution: Share files in censorship-resistant ways
Self-host services: Take control of your data
Support decentralized projects: Use and contribute to open alternatives
For Students and Researchers
Decentralized systems offer rich research opportunities in distributed systems, cryptography, network protocols, and social systems design. Understanding both the promise and limitations of decentralization helps you evaluate emerging technologies and their implications.
The future of the web likely involves greater decentralization in some areas while centralization persists in others. Critical understanding helps navigate this evolving landscape.