You boost a post from another Mastodon instance, but the boosted post never shows up in your home timeline or your profile. This can happen even though the original post is still visible and the boost action appeared to succeed. The problem is almost always caused by a server-side mute or block rule applied by your home instance against the remote server or the remote user. This article explains the technical reason for the missing boost and provides the exact steps to identify and remove the filter so your boost appears normally.
Key Takeaways: Fixing a Missing Boost from a Remote Instance
- Preferences > Moderation > Server blocks: Check whether the remote instance is muted or suspended by your home server.
- Preferences > Moderation > Domain blocks: Review if a domain-level block is silently hiding boosts from that instance.
- Preferences > Filters: Verify that no active text or hashtag filter is suppressing the boosted post.
Why Your Mastodon Boost From a Remote Instance Disappears
When you boost a post, your Mastodon client sends a request to your home instance. The instance then creates an Announce activity that references the original post. If the remote instance or the remote user is muted, blocked, or suspended by your home server, the server drops the Announce activity before it reaches your timeline or profile. The boost action itself succeeds at the API level, so you see no error message. But the boosted post never renders. The same thing happens if a text filter on your account matches the content of the boosted post. Mastodon does not show a warning or notification for this silent drop. You must check the server-side moderation rules and your personal filters to find the cause.
Instance-Level Domain Blocks
Your home instance administrator can apply domain blocks that mute, suspend, or limit visibility of posts from a specific remote instance. If the remote instance is muted at the domain level, boosts from that instance are invisible to everyone on your home server. You can still see the original post if you visit the remote instance directly, but the boost will not appear on your profile or in your followers’ timelines.
User-Level Mutes and Blocks
If your home instance has a rule that mutes the remote user who created the original post, any boost of that user’s content is also hidden. This can happen if the remote user is on a blocklist maintained by your server’s moderation team. Unlike a personal mute, this server-enforced mute is not visible in your own account settings. You must check the moderation interface to see it.
Personal Text Filters
Mastodon allows you to create filters that hide posts containing specific words, phrases, or hashtags. If a filter is set to hide or warn, a boosted post that matches the filter condition will not appear in your timeline. The filter applies to the content of the boosted post, not to the boost action itself. Check your filters list in Preferences > Filters to rule this out.
Steps to Find and Remove the Block Causing the Missing Boost
- Open the Moderation interface
You need admin or moderator privileges on your home instance. If you are not an admin, contact your instance moderator and ask them to check domain blocks and user blocks for the remote instance or user involved. If you are an admin, navigate to Preferences > Moderation > Server blocks. - Check domain blocks for the remote instance
In the Server blocks section, look for the domain of the remote instance where the original post lives. If the domain appears with a status of “Muted” or “Suspended”, the boost is being dropped because of this block. Click the domain name and select “Remove block” to lift the restriction. After removal, ask the remote user to repost the original content, then try boosting again. - Inspect user-level blocks
In the Moderation interface, go to the Users section and search for the remote user who created the original post. If that user is silenced or suspended, the boost will not appear. Remove the silence or suspension by editing the user record and setting the account status to “Active”. - Review personal filters
Go to Preferences > Filters. Look for any filter that might match the text, hashtags, or content of the boosted post. If you find a matching filter, either delete it or change its action to “Show” instead of “Hide”. Save the changes and reload your timeline. - Test the boost again
After removing any block or filter, find the original post again and perform the boost. The boosted post should now appear in your home timeline and on your profile. If it still does not appear, repeat steps 2 through 4 to confirm no other block exists.
If the Boost Still Does Not Appear After Checking Blocks
Boost from a private or followers-only post
If the original post is set to “Followers only” or “Private”, boosting it will not make it visible to your followers. Mastodon does not propagate boosts of locked posts. The boost action succeeds on your end, but the boosted post is only visible to you. Ask the original poster to change the visibility to “Public” before you boost.
Remote instance is defederated or suspended
If the remote instance is fully suspended by your home server, all traffic from that instance is blocked. Boosts from a suspended instance are never delivered. The only fix is to have your admin remove the suspension. If you cannot get the suspension lifted, you cannot boost posts from that instance.
Browser cache or client issue
Sometimes the boost appears on the server side but your client does not refresh properly. Open your profile in a private or incognito browser window and check if the boosted post shows up there. If it does, clear your browser cache and reload the normal window. On the Mastodon web interface, press Ctrl+F5 to force a full refresh.
| Item | Domain Block (Mute) | User-Level Silence | Personal Filter |
|---|---|---|---|
| Who can remove it | Instance admin only | Instance admin only | Any account owner |
| Effect on boosts | All boosts from that domain are hidden | Boosts of that specific user are hidden | Boosts matching filter text are hidden |
| How to check | Preferences > Moderation > Domain blocks | Preferences > Moderation > Users | Preferences > Filters |
| Typical fix | Remove the domain block | Unsilence or unsuspend the user | Delete or modify the filter |
You now know the three main reasons a boost from a remote instance can disappear: a domain block, a user-level silence, or a personal text filter. Use the Moderation interface and your Filters settings to identify and remove the cause. As an advanced tip, ask your instance admin to add the remote instance to the “Allow list” if your server uses allow-list mode, which ensures all content from that instance is visible by default.