When you boost a post from another Mastodon instance, your followers see it in their Home timeline. But when you reply to a cross-instance post, the reply may not reach all followers. This difference confuses many users because both actions seem similar: you engage with content from a different server. The visibility rules for boosts and replies are not the same because Mastodon processes each action through different federation mechanisms. This article explains why cross-instance boosts are visible to all followers while replies are not, and shows you how to check and control what your followers see.
Key Takeaways: Boost vs Reply Visibility on Other Instances
- Boost (reblog) button: A boost of a cross-instance post is delivered to all your followers, regardless of their home instance.
- Reply text box: A reply to a cross-instance post is only delivered to the original author and to followers who also follow the original author.
- Preferences > Appearance > Show boosts in timeline: Toggle this setting to control whether you see boosts from accounts you follow.
Why Boost Visibility and Reply Visibility Differ Across Instances
Mastodon is a federated network. Each instance is an independent server running Mastodon software. When you boost a post from another instance, your home server sends a notification to all your followers’ servers. The post itself is embedded in the boost. Your followers see the boost in their Home timeline even if they do not follow the original author or are not on the same instance as the original author.
A reply works differently. When you reply to a post from another instance, your home server sends the reply to the original author’s server. The original author’s server then delivers the reply to that author and to any of your followers who also follow that original author. This behavior is by design. Mastodon treats replies as a conversation between the reply author and the original post author. Followers who do not follow the original post author will not see your reply in their Home timeline.
The root cause of this difference is the Mastodon timeline delivery algorithm. The algorithm prioritizes boosts as announcements and replies as threaded conversations. Boosts are broadcast to all followers. Replies are scoped to the conversation participants and their shared followers. This design prevents reply spam from flooding timelines but also means your cross-instance replies may have lower reach than your boosts.
How to Verify What Your Followers See From Cross-Instance Posts
Check Boost Visibility
- Log in to your Mastodon account
Open your Mastodon instance in a web browser and sign in. - Find a post from another instance
Navigate to a post that was written by someone on a different server. For example, a post from @user@example.com. - Click the Boost (reblog) icon
The icon looks like two overlapping arrows. Click it once. The icon turns solid, indicating the boost is active. - Open a browser in incognito or private mode
Use a browser window that is not logged into any Mastodon account. Go to your public profile URL, for example https://yourinstance.social/@yourusername. - Verify the boosted post appears
On your public profile, the boosted post appears in the timeline. This confirms that any follower, regardless of their instance, can see the boost.
Check Reply Visibility
- Log in to your Mastodon account
Use the same account as above. - Find the same cross-instance post
Locate the post you boosted earlier. - Type a reply in the Reply text box
Enter a short message and click Reply. - Switch to a secondary account that does not follow the original author
Use a different Mastodon account or ask a colleague who does not follow the original author. If you have a test account, log in there. - Check the secondary account’s Home timeline
The reply does not appear in the Home timeline of that account. The reply only appears if the secondary account also follows the original author.
Common Misunderstandings About Cross-Instance Engagement
“I Replied But No One Saw It”
This is the most frequent complaint. Users expect replies to behave like boosts. The reply is not broken. It was delivered to the original author and to followers who also follow that author. If your followers do not follow the original author, they never see the reply. The solution is to boost the original post instead of replying, or to create a new post that quotes the original post.
“My Boost Disappeared From Followers’ Timelines”
A boost may disappear if the original post is deleted or if the original author blocks your instance. Mastodon removes the boost from all timelines when the source post is gone. This is not a visibility bug. It is a content removal cascade. If you want to preserve the content, save a screenshot or create a new post with the content and credit the original author.
“I See Replies From People I Don’t Follow”
This happens when someone you follow replies to a post from someone else. Mastodon shows you the reply because your followed account participated in the conversation. You do not need to follow the original author. The reply is delivered to you because Mastodon considers it part of the thread started by the account you follow.
Boost vs Reply: Cross-Instance Visibility Comparison
| Item | Boost | Reply |
|---|---|---|
| Delivery to all followers | Yes, regardless of follower instance | No, only to followers who also follow the original author |
| Appears in Home timeline | Yes | Only for shared followers |
| Appears in public profile | Yes | Yes, on your profile page as a reply thread |
| Requires original author follow | No | Yes, for reply to be visible to non-shared followers |
| Can be removed by original author | Yes, if original post is deleted | Yes, if original post is deleted or reply is deleted |
If You Want Cross-Instance Replies to Reach More Followers
You cannot change how Mastodon delivers replies. The federation protocol is fixed. However, you can adjust your posting strategy. Boost the original post first, then add a reply in a new post that quotes the original. Use the quote post feature if your instance supports it. Alternatively, create a new post that mentions the original author and includes a link to the original post. This new post behaves like a regular post and is delivered to all your followers.
You can also check your instance’s federation settings. Some instances allow you to disable boosts from certain accounts or domains. Go to Preferences > Filters to create a filter that hides replies from specific users if you find the visibility rules confusing. Remember that Mastodon’s design intentionally limits reply reach to reduce noise. Once you understand this, you can choose the right action for your audience.
For a quick test, boost a cross-instance post and then reply to it. Ask a follower who does not follow the original author to confirm they see the boost but not the reply. This real-world test reinforces the difference. Use boosts for announcements and replies for direct conversation with the original author.