Mastodon uses a standardized, open protocol to implement federation. It is called ActivityPub. Any software that likewise implements federation via ActivityPub can seamlessly communicate with Mastodon, just like Mastodon servers communicate with one another.
The fediverse (“federated universe”) is the name for all servers that can communicate with each other. That includes all Mastodon servers, but also other implementations:
- and many more
The fediverse does not have its own brand, so you will more often hear “follow me on Mastodon” than “follow me on the fediverse”, but technically the latter is more correct.
Mastodon usernames actually consist of two parts:
- The local username, e.g.
- And the domain of the server, e.g.
Just like an e-mail address. For convenience sake, Mastodon allows you to skip the second part when addressing people on the same server as you, but you have to keep in mind when sharing your username with other people, you need to include the domain or they won’t be able to find you as easily.
|I’m @alice on Streamz!||I’m @firstname.lastname@example.org on Streamz!|
The search form in Mastodon will find people either with the above address form, or the link to the person’s profile, so you can share that instead if you prefer.
As long as you encounter a person within your app’s user interface, e.g. the web interface on your home server, or your mobile app, you can just click “follow” and you won’t notice a difference if that person is on your server or not.
However if you come across someone’s public profile hosted on a different server, there’s an obstacle: That server sees you as just another anonymous visitor.
So when you click “follow”, a dialog will pop up asking you to enter your own full username (with the domain part, most importantly). This way, the dialog actually sends you back to your home server, where you are logged in and can really do stuff.
You will also notice that dialog when clicking on “reply”, “boost” or “favourite” on public pages of other servers.
To allow you to discover potentially interesting content, Mastodon provides a way to browse all public posts. Well, there is no global shared state between all servers, so there is no way to browse all public posts. When you browse the federated timeline, you see all public posts that the server you are on knows about. There are various ways your server may discover posts, but the bulk of them will be from people that other users on your server follow.
There is a way to filter the federated timeline to view only public posts created on your server: The local timeline. Mind that “local” here refers to the server, not to a geographical location.