Mastodon relays are servers that broadcast public posts from multiple instances to your instance. They help populate your federated timeline with content from many communities. However, some relays may carry spam, low-quality posts, or content that does not align with your instance’s rules. This article explains how to configure Mastodon to reject posts from specific … Read more
When you run a Mastodon server, you decide how posts from other instances reach your users. You can either subscribe to a relay or ask users to follow accounts directly. Each method affects your server bandwidth and the quality of content your users see. This article explains the technical differences between relays and direct follows. … Read more
If your Mastodon instance uses a public relay, your local timeline can become cluttered with posts from servers that have no connection to your community. A public relay indiscriminately distributes all messages from all connected servers, which can overwhelm small instances with irrelevant content. Switching to a private relay gives you control over which remote … Read more
As a Mastodon instance admin, you manage the relay that your server uses to exchange public posts with other instances. A relay distributes your local public posts to all subscribed instances and brings their public posts into your federated timeline. Without a clear view of who subscribes to your relay, you cannot audit federation partners … Read more
Mastodon relays let instances share public posts with each other without following every user individually. Without a tag filter, a relay forwards all public posts from every connected instance, which can flood your local timeline with irrelevant content. Building a topic-specific relay with a tag filter solves this by forwarding only posts that contain specific … Read more
When a Mastodon relay connection breaks, your instance stops receiving public posts from federated servers that depend on that relay. This usually happens because the relay server went offline, changed its endpoint, or the subscription token expired. Without a working relay, your local timeline becomes quieter and users may miss trending content from outside instances. … Read more
If you run a Mastodon instance for a niche community such as vintage computer collectors, bird watchers, or indie game developers, your users may feel isolated. The local timeline shows only posts from your instance, and the federated timeline can be overwhelming or irrelevant. A Mastodon relay solves this by automatically pulling in public posts … Read more
Mastodon relays aggregate public posts from multiple instances into a single federated timeline. As an admin, you need to know how many inbound posts your relay processes to gauge its health and performance. The inbound posts counter is a built-in metric in the Mastodon admin interface that shows the total number of statuses received from … Read more
When you join a new Mastodon instance, the local timeline shows only posts from users on that same server. This can feel isolating if the instance is small or specialized. A Mastodon relay connects multiple instances so they share public posts with each other, effectively expanding the local timeline. This article explains what a relay … Read more
After upgrading your Mastodon server, relay subscriptions may stop working without any visible error. The relay connection can silently break, causing your instance to miss federated content from subscribed relays. This typically happens because the upgrade process resets internal database connections or changes the relay handshake protocol. This article explains how to verify that your … Read more