What Is the Fediverse? A Plain Guide

The fediverse is a set of independent social media servers that can all talk to each other. Someone with an account on one server can follow, reply to and share posts from someone on a completely different server running completely different software. It works the way email does. You do not need a Gmail address to email a Gmail user, and you do not need a Mastodon account to follow someone on Mastodon.

The glue is an open standard called ActivityPub, published by the W3C in 2018. Any app that speaks it can join. That is why a photo posted on Pixelfed can appear in a Mastodon timeline, and why a video hosted on PeerTube can collect replies from people who have never opened PeerTube. There is no company in the middle. There are thousands of separate servers, each run by a person, a group or a business, that have agreed to pass messages along.

How the fediverse actually works

Every fediverse account lives on a server, often called an instance. That server stores your posts, your follower list and your settings. When you post, your server sends a copy of that post to every other server that has at least one of your followers on it. Those servers keep their copy and show it to their own users.

ActivityPub defines the envelope for those messages. Each account is an actor with an inbox and an outbox, and actions such as Follow, Create, Like, Announce (a boost) and Delete travel between them as small documents. Servers sign each message cryptographically, so a receiving server can tell a genuine post from a forged one.

The practical effect is that following someone is a standing request from your server to theirs, not a row in one enormous corporate database. Nothing routes through a head office. If one server goes down, only its own users go quiet and the rest of the network keeps running.

The apps, and what each one is closest to

The fediverse is not a single app. It is a family of them, built by different teams for different jobs.

Interoperation is real but partial. A Mastodon user can follow a Pixelfed account and see the photos in their timeline, but features that exist in only one app do not magically appear in another. Polls, quote posts and content warnings all render differently depending on who receives them. Expect a rough edge now and then rather than one seamless product.

If you are already working through leaving Google behind, these are the social layer of that same move. You can adopt one and ignore the rest.

Your address is @you@server, and the server matters

A fediverse handle looks like @[email protected]. The first part is your username, the second is the server that hosts you. That is the whole addressing system, and it is deliberately the same shape as an email address.

Picking a server is a real decision, in the same way that picking an email provider is. The admin sets the rules, decides how much storage you get, chooses when to upgrade and pays the bill. Small servers built around a town, a workplace or a hobby tend to have attentive moderation and a local timeline worth reading. Very large general servers are easier to join and harder to feel at home on.

You are not locked in, but the escape hatch is imperfect. Mastodon and most compatible apps support account migration, which moves your followers and your follow list to a new server and leaves a redirect on the old one. Your old posts usually do not come with you. Export your data before you move, and treat the migration as a fresh start with the same audience.

Three timelines, and why it feels quiet at first

Most fediverse apps show you three views. The home timeline is the accounts you follow, in order, with no ranking algorithm deciding what you deserve to see. The local timeline is every public post from people on your own server. The federated timeline is every public post your server has received from anywhere, which is a firehose on a big server and a trickle on a small one.

This is the part that surprises new arrivals. Your server only knows about posts that reach it, and posts reach it because someone on your server already follows the author. On a brand new personal server, almost nothing arrives on day one. It is not broken. It has no relationships yet.

Two things fix that. Follow forty or fifty accounts by hand, using hashtags and other people's boosts as a directory. Or subscribe your server to a relay, a shared firehose that forwards public posts between participating servers so a small instance has something to show. Relays do not backfill history, so they only help going forward.

Moderation is local, and that cuts both ways

There is no central trust and safety department. Each admin writes their own rules and enforces them on their own users. Admins can also act against whole servers: limiting one so its posts stay out of public timelines, or suspending it outright so no messages pass in either direction. That second one is usually called defederation.

The upside is speed and fit. A server run by and for a specific community can ban a spam farm in minutes and can set norms a global platform would never adopt. The downside is inconsistency. Two people on two servers can have completely different experiences of the same network, and a block you never voted on can quietly remove a chunk of it from your view.

Before joining anywhere, read the server rules and the about page, and check whether the admin publishes a list of the servers they have limited or suspended. Communities that run a server together also need a fair way to make those calls, which is the problem Folkmoot was built for.

Running your own server, honestly

Self-hosting is the strongest version of this. You own the account, the data and the rules, which is the practical meaning of data sovereignty. It is also real work, and nobody is well served by pretending otherwise.

A Mastodon-class server needs a PostgreSQL database, a cache, background job workers and a web process, plus somewhere to keep uploaded media. It also caches media from every remote post it receives, so disk use grows with the size of your social graph rather than the size of your own posting. Most admins run a scheduled job to prune that cache. Lighter software such as GoToSocial or Akkoma exists precisely because full Mastodon is heavy for one or two people.

Then there is the unglamorous half. Outbound email has to actually arrive so password resets work. Backups have to be tested, not just configured. Upgrades land on someone's evening. And you become the moderator, including for reports about your users filed by strangers. We run our own Mastodon and Akkoma servers, and that ongoing maintenance is the honest price of the independence.

Where the fediverse falls short

Search is the biggest gap. Because no server holds the whole network, there is no complete index of it. Mastodon added opt-in full-text search, which means posts are findable only if their author agreed to it. Digging up a specific old conversation is genuinely hard, and that is a choice made for consent rather than an oversight.

Direct messages are not private in the way the name suggests. In most ActivityPub software a DM is an ordinary post with a restricted audience, stored in plain text on your server and on the recipient's server, readable by either admin. Use Signal or Matrix for anything sensitive.

Other honest limits, in short:

• Servers close. When an admin runs out of money, time or patience, the users scatter and the links rot.
• A large share of accounts sit on a handful of big servers, so the network is less decentralised in practice than on paper.
• Corporate federation, such as Meta connecting Threads, splits opinion sharply, and many servers block it on principle.
• It still needs the internet. ActivityPub is not an offline or local-first protocol, so if you want communication that survives an outage you are looking at mesh networking and radio hardware like the LoRa kit from Blackout Labs, not a social protocol.

Fediverse, Bluesky and Nostr are not the same thing

All three try to escape a single owner, and they make different bets about identity.

In the fediverse your identity is tied to a server name, and moving means asking two servers to cooperate. Bluesky, built on the AT Protocol, gives each account a portable identifier and lets you point your own domain at it, so changing hosts is smoother, but the discovery and moderation infrastructure most people rely on there is still centrally operated. Nostr goes furthest: your identity is a cryptographic keypair and posts are copied to many relays, which is very hard to censor but leaves you personally responsible for a key that cannot be reset if you lose it.

None of this says one wins. The fediverse has the most mature software, the longest track record and the widest range of app types. It also carries the most operational baggage. Bridges between these networks exist and mostly work, and plenty of people simply keep an account on more than one. Our other guides cover the surrounding pieces if you want to go deeper.

Frequently asked questions

Is the fediverse the same thing as Mastodon?

No. Mastodon is one application in the fediverse, and it is the best known, which is why the names get swapped. The fediverse is the whole network of servers speaking ActivityPub, including Pixelfed for photos, PeerTube for video, Lemmy for discussion boards and many others. You can follow accounts on any of them from a Mastodon account.

How do I pick a fediverse server, and can I move later?

Pick one whose rules and subject matter suit you, and prefer a smaller server with an active admin over the biggest one you can find. You can move later. Account migration carries your followers and your follow list to the new server and leaves a redirect behind, but your old posts normally stay put, so export your data first.

Are direct messages on the fediverse private?

Not really. In most fediverse software a direct message is an ordinary post limited to the people you mention. It is stored unencrypted on your server and on each recipient server, so both administrators can read it if they choose. Treat it like a postcard, and use Signal or Matrix for anything you would not want an admin reading.

Why is my fediverse timeline empty when I join?

Your server only receives posts that someone on it already follows, so a new or small server starts with almost nothing. There is no algorithm filling the gap. Follow several dozen accounts through hashtags and boosts, and if you run the server yourself, subscribe it to a relay. Relays only forward new posts, never past ones.

Does it cost anything to use the fediverse?

Joining an existing server is normally free, though servers cost their admins real money for hosting, storage and bandwidth, and many run on donations. Running your own means paying for a server and storage yourself. There are no ads and no data sales in the standard software, which is exactly why the bills land on operators instead.

Can big platforms like Threads really connect to the fediverse?

Yes. ActivityPub is an open standard, so any company can implement it, and Meta has connected parts of Threads to it. Federation is not automatic, though. Individual server admins decide whether to accept messages from a given platform, and many have suspended large commercial servers over privacy and moderation concerns.