Federated Server Capacity: A Key-Numbers Breakdown
Community administrators exploring federated microblogging often face structural choices regarding how to manage inbound member capacity, supervise new registrations, and handle distributed identity. In federated ecosystems like Mastodon, a website functions as an independent service provider that hosts member accounts, profiles, and personal home feeds, much like choosing an email host or selecting a realm for a new character in World of Warcraft. Assessing capacity and operational rules requires examining foundational architectural thresholds.
3 Signup Modes for Moderation and Intake Control
A primary capacity threshold for any server operator is controlling the rate of incoming registrations. According to the Mastodon documentation on signing up for an account, platform administrators can configure their websites using one of three distinct signup modes:
- Open signup: This configuration permits visitors to register immediately by filling out a form with a username, an email address, and a password. Once submitted, the user can start using the account straight away, maximizing growth velocity at the expense of automated screening.
- Server invites: Administrators can choose to disable the public registration form completely. Under this mode, new accounts can only be created when existing members or operators generate and distribute explicit invite links.
- Approval-based registration: This intake format requires prospective members to submit a standard registration form alongside an additional text entry explaining why they want to join the instance. The account cannot be used until a human moderator reviews and approves the submission.
Choosing between these three mechanisms directly affects administrative workload. Open signups demand active background monitoring, whereas invite-only setups limit inbound volume to trusted networks. For communities requiring close curation, approval mode ensures moderators evaluate every applicant before granting access, aligning directly with strategies detailed in our Mastodon moderation tools profile.
2 Essential Segments in Federated Identity Architecture
Unlike centralized message boards where a single database stores all user records, federated networks partition account identification across distinct servers. As outlined in the official signup documentation from Mastodon, account usernames consist of exactly two constituent parts:
- The local username: The specific handle assigned to the individual on their home server, such as alice.
- The website domain: The host domain where the profile and data reside, such as example.com.
While members can omit the domain when communicating with someone on the exact same server, cross-server communication requires the complete two-part address. For addressing and searching across the fediverse, valid formats include the full handle structure (@alice@example.com) or the direct profile link (https://example.com/@alice). Attempting to use only the local portion across federated boundaries is incorrect and will prevent remote instances from finding the user.
This two-part framework also establishes a critical namespace principle: the exact same username can be registered across multiple servers. Just as an email user cannot expect alice@outlook.com to belong to the same person who owns alice@gmail.com or alice@yahoo.com, federated microblogging treats identical usernames on different domains as separate individuals. Administrators must recognize that they cannot claim a local handle globally across every independent instance.
Evaluating Server Rules via the /about/more Pathway
Before launching an instance or inviting users to create accounts, administrators must define their operational terms. The documentation explains that a server will usually list its policies, terms of use, and local community rules on the specific /about/more path. Logged-out visitors access this repository by selecting the “learn more” link available directly on the landing page.
Publishing clear rules on the /about/more page establishes expectations regarding unacceptable behavior, expected discussion etiquette, and local administrative boundaries. Community owners can refine these standards by consulting our comprehensive forum moderation guide to maintain transparent governance across their user base.
Directory Categorization and Multi-Server Topologies
Operating or selecting a federated instance requires understanding where a website fits within the broader network topology. Prospective users can discover and browse independent servers organized by languages and thematic categories on joinmastodon.org. Because each individual website acts as a sovereign host for profiles and feeds, administrators can tailor their communities around specific shared interests or linguistic boundaries while maintaining connectivity to external instances across the network.
Platform Operational Standards Dated November 22, 2024
Maintaining a secure and predictable federated environment requires relying on documented operational standards. The baseline specifications governing these signup modes, user addressing structures, and policy locations reflect updates finalized on November 22, 2024. Adhering to these documented protocols ensures that newly deployed instances maintain stability and interoperability as members communicate across distributed domains.
Sources
Signing up for an account - Mastodon documentation
Published October 31, 2026. No affiliate links on this page. Facts come from the sources linked above; check them for updates.