How to Choose Your Path in the Mastodon Documentation

Updated

The Mastodon documentation at docs.joinmastodon.org is organized around what you want to do, not around a single linear manual. The site's "Choose your path" section is the entry point: pick the path that matches your goal — using Mastodon as a person, or running and moderating your own server — and the docs route you into the relevant guides from there. If you are unsure, start by reading "What is Mastodon?" and the pages on microblogging, federation, and ActivityPub, because those concepts shape which path actually applies to you.

What the documentation covers before you choose

The opening pages establish vocabulary the rest of the docs assume you already have:

  • Microblogging — publishing small updates to a stream on your profile, optionally with media such as pictures, audio, video, or polls. Mastodon lets you follow friends and discover new ones.
  • Federation — a form of decentralization. Instead of one central service everyone uses, there are multiple services any number of people can use. The docs place centralized services (Twitter, Facebook, Instagram) at one end, federated ones (email, XMPP, phone networks, physical mail) in the middle, and distributed ones (BitTorrent, IPFS, Scuttlebutt) at the other.
  • ActivityPub — the standardized, open protocol Mastodon uses to implement federation. Software that implements federation via ActivityPub can communicate with Mastodon seamlessly.
  • The fediverse — "federated universe," the name for all websites that can communicate over ActivityPub and the web. That includes Mastodon servers plus other implementations: Pleroma, Pixelfed, Misskey, PeerTube, Plume, and personal websites.

A Mastodon website can operate alone like a traditional site — people sign up, post, upload pictures, and talk to each other. Unlike a traditional site, Mastodon sites interoperate, so you can mention or message anyone on any site using their address, the same way you email someone from Gmail to Outlook.

The two main paths

The practical fork in the documentation follows from a simple fact: Mastodon is software that can power any website. That means your path depends on whether you are a user of someone else's server or the operator of your own.

Your goal What the docs point you toward
Join an existing server, post, follow people, use the apps User-facing guides: signing up, posting, following, and messaging across servers
Run your own instance, set policy, moderate, administer Server-facing guides: installation, configuration, administration, and moderation

The docs note one consequence of this split explicitly: because Mastodon is just software powering any website, choice of service provider and policy matters to potential users. Different servers set different rules, and the documentation treats that as a decision you make rather than a default you inherit.

How to decide which path is yours

Work through these questions in order:

  1. Do you already have an account on a Mastodon server? If yes, you are on the user path. If no, you still need to choose a server before most user guides apply — the docs' federation explanation is what makes that choice meaningful.
  2. Do you want to communicate with people on other servers? This is normal on Mastodon, not an exception. If cross-server interaction is your goal, the federation and ActivityPub pages are required reading before anything else, because they explain why your address, not a central username, is how people find you.
  3. Do you want to control policy, moderation, or hosting? That is the server path. It is a different kind of commitment from signing up, and the docs separate it for that reason.
  4. Are you looking for a specific non-Mastodon platform? If you are interested in Pixelfed, PeerTube, Misskey, Pleroma, or Plume, note that these are separate implementations in the same fediverse. The Mastodon docs describe how they interoperate, not how to run them.

Common sticking points

  • "Follow me on Mastodon" vs. "follow me on the fediverse." The docs point out that the fediverse has no brand of its own, so the first phrasing is more common even though the second is technically more correct. Do not let the terminology make you think you are choosing between separate networks — you are not.
  • Assuming one central sign-up. There is no single Mastodon site to join. The federation model is the reason the docs spend time on the centralized/federated/distributed comparison before sending you anywhere.
  • Skipping the concepts. The "Choose your path" orientation sits after the explanatory pages, not before them. Reading the microblog, federation, and ActivityPub sections first will make the path you pick much easier to follow.

If you only remember one thing: the documentation is split by role, and the role you pick determines everything else. Read the four concept pages, decide whether you are a user or an operator, then follow the matching path.