Platforms and Algorithms

Open and Decentralized Social Networks Explained

What it means for a social network not to be run by one company, how federated and open designs work, and the trade-offs in moderation, ease of use and cost.

On this page
  1. The usual model and its alternative
  2. Key terms
  3. How a federated network works in practice
  4. Possible benefits
  5. Trade-offs and difficulties
  6. Who uses these networks
  7. Questions to ask before joining
  8. An evolving area

The usual model and its alternative

On most large social services, one company owns the servers, writes the rules, designs the feed, controls the data and decides who can join. Users and creators build audiences inside that company’s walls, and if the company changes direction, they have limited say.

Open and decentralized networks try a different arrangement. Instead of one operator, many independent operators run parts of the network, and they communicate using shared, published rules. The goal is to spread control more widely and to make it easier to leave without losing everything.

The terms are used loosely, so it helps to separate a few ideas.

Key terms

  • Open standard (protocol). A publicly documented set of rules for how software exchanges posts and follows. Anyone can build software that uses it, much as anyone can build an email program.
  • Federated. The network is made of many separate servers, sometimes called instances, run by different people or organizations. Accounts on different servers can usually follow and message each other, as email users on different providers can.
  • Decentralized. Control is spread across many parties rather than concentrated in one. This is a matter of degree, not an on-off switch.
  • Portable account or identity. The idea that your identity and followers can move with you if you change provider.
  • Open source. The software’s code is public and can be inspected and modified, which is related to openness but not identical to it. A network can be built on open code and still be controlled by one company.

How a federated network works in practice

Imagine a person who joins a small server run by a hobby group. They post, follow people on that server and can follow people on other servers too. Posts travel between servers using the shared protocol. Each server has its own rules, its own moderators and often its own culture and size. If someone does not like their server’s rules, they may be able to move to another, possibly taking their follower list with them, though how well this works varies by design.

Other designs go further and let users hold their own keys or choose among competing services that organize the same underlying data in different ways. Some let people pick between different feed algorithms instead of accepting one.

Possible benefits

  • Choice of rules and community. Different servers can set different moderation styles, which may suit communities better than one global policy.
  • Less dependence on one company. If one operator closes or changes course, others can continue, and the network does not disappear.
  • Greater transparency. Public code and published protocols let outsiders see how things work, which can matter to anyone concerned about social privacy.
  • Fit for community building. Groups that want their own space, their own norms and no outside advertising may find a server of their own suits community building better than a large shared service.
  • Room for experiments. Developers can try new feed designs or apps without needing permission from a single owner.
  • Independent organizing. Groups doing online organizing sometimes prefer infrastructure that no single company can switch off, though they still depend on their own server operators.
  • Portability. In better designs, moving your account is easier, which reduces the lock-in described in the article on moving between services.

Trade-offs and difficulties

Decentralization is not a cure-all, and it brings its own problems.

Complexity for newcomers. Choosing a server, understanding usernames that include a server name, and finding people can be confusing. Many people prefer an app that simply works. Services that hide this complexity may do so by centralizing again.

Moderation is uneven. Quality depends on each operator. A well-run server may be pleasant, while a neglected one may attract abuse. Servers can also block or cut off others, which can fragment the network. The same challenges described in the piece on content moderation apply, but are spread across many small operators, many of them volunteers with limited time and money.

Cost and sustainability. Someone has to pay for servers, storage and support. Small operators often rely on donations or personal funds, and a server can close with little notice. Moving accounts is helpful then, but only if the design supports it.

Privacy and data. Posts that are shared across servers may be copied to many places, so deleting something completely can be difficult, and your digital footprint may be wider than it appears. Messages that are meant to be private are not necessarily protected by end-to-end encryption, so check what a given service actually offers. Server administrators can often see more than users assume, depending on the setup, so reading privacy settings and understanding who runs your server matters.

Discovery and reach. Without a central ranking system, finding new people and content can be harder. Creators used to the audiences of large services may find that reach is smaller and income options are fewer, a point relevant to the creator economy.

Concentration can return. Even in decentralized networks, a few large servers or a few popular apps can gain disproportionate influence, so the practical outcome is sometimes less distributed than the design suggests.

Abuse and spam. Open systems can be easy to exploit with fake accounts and unwanted messages, so servers need shared tools to cope.

Who uses these networks

People are drawn to them for different reasons: wanting more control over their data, preferring community-run spaces, valuing open code, or being unhappy with changes to a large service. Others try them out of curiosity and return to larger services where more of their contacts are. Neither choice is wrong. Many people use both.

Questions to ask before joining

  • Who runs this server, and how are they funded?
  • What are the rules, and how are they enforced?
  • Can I export my posts and follower list? Can I move to another server?
  • Does it interoperate with the other networks I care about?
  • What happens to my data if the server shuts down?
  • Is the software actively maintained?

An evolving area

Open and decentralized networks have grown and shifted over the years, and their long-term place is uncertain. They offer a real alternative to the single-company model, with different strengths and weaknesses, not a simple replacement. For anyone interested, the sensible approach is to try one at low stakes, keep your important contacts reachable elsewhere, and judge it by how well it serves you.

The complete guide to platforms and algorithms

How Social Feeds Decide What You See
Read the guide

Keep exploring

Guides from other topics

All topics →