Threads lets you limit who can reply to your posts: everyone, profiles you follow, profiles you mention, or only the original poster. The Fediverse, which includes Mastodon and other ActivityPub-compatible services, expects replies to be open by default so they can flow freely across servers. When you restrict replies on a public Threads post and that post is shared to the Fediverse, the two systems clash. This article explains exactly how reply audience controls work on each platform, why the conflict occurs, and what happens to restricted replies when they leave Threads.
Key Takeaways: Threads Reply Restrictions vs Fediverse Open Replies
- Threads reply audience options: Everyone, Profiles you follow, Profiles you mention, and Only the original poster.
- Fediverse default reply behavior: All public posts accept replies from any user on any connected server.
- Conflict point: Restricted replies on Threads break the Fediverse expectation of open conversation, leading to missing or blocked replies on other servers.
How Threads Reply Audience Control Works
Threads gives you four reply audience options when composing a new post. These controls determine who can reply to that specific post directly inside the Threads app. The options are:
- Everyone: Any Threads user can reply to your post.
- Profiles you follow: Only accounts you follow can reply.
- Profiles you mention: Only accounts you tag in the post can reply.
- Only the original poster: Only your own account can reply. This effectively disables replies.
These settings apply only to replies posted within the Threads app. They do not affect the visibility of the post itself. A post with restricted replies is still public and can be seen by anyone on Threads or the Fediverse.
How the Fediverse Handles Replies
The Fediverse is a network of independent servers running ActivityPub software, such as Mastodon, Pleroma, and Misskey. On these platforms, replies to a public post are open by default. Any user on any participating server can reply to a public post. There is no built-in concept of reply audience controls at the protocol level. Each server enforces its own moderation rules, but the ActivityPub specification does not define a way to restrict who can reply to a specific post.
When a Threads post is shared to the Fediverse, it becomes a standard ActivityPub object. The reply audience metadata from Threads is not part of the ActivityPub standard. Therefore, Fediverse servers ignore it.
Where the Conflict Occurs
The conflict appears in two main scenarios:
Restricted Replies Are Visible but Unreplyable on Fediverse
When a Threads post with restricted replies reaches a Mastodon server, the post appears normally. Mastodon users can see the post text and any media. However, if a Mastodon user tries to reply, the reply may be sent back to Threads but then be rejected or silently dropped by the Threads server. The Mastodon user sees no error message, but their reply never appears in the Threads conversation. This creates a broken conversation flow.
Replies from Fediverse Users Are Silently Dropped
If your Threads post is set to “Profiles you follow” or “Profiles you mention,” only specific Threads users can reply. A Fediverse user who is not on your follow list or mentioned in the post can still attempt to reply. Their reply is sent to Threads via ActivityPub, but Threads checks the reply audience rule and discards the incoming reply. The Fediverse user never sees their reply appear on Threads. This is the most common source of user confusion.
What Happens to Restricted Replies on the Fediverse
The table below summarizes the outcome for each Threads reply audience setting when the post is shared to the Fediverse.
| Threads Reply Audience Setting | Post Visible on Fediverse | Reply from Fediverse User |
|---|---|---|
| Everyone | Yes | Accepted and shown on Threads |
| Profiles you follow | Yes | Dropped by Threads unless replier is followed |
| Profiles you mention | Yes | Dropped by Threads unless replier is mentioned |
| Only the original poster | Yes | Always dropped by Threads |
Why This Design Choice Exists
Threads is built on top of Instagram’s infrastructure. Reply audience controls are a feature inherited from Instagram’s commenting system. Instagram uses these controls to reduce harassment and spam. Threads extended the same feature to its own posts. The Fediverse, on the other hand, was designed with open communication as a core principle. ActivityPub does not include reply audience restrictions because the protocol prioritizes interoperability over granular control.
Meta, the owner of Threads, chose to implement Fediverse sharing as a one-way bridge for replies. Your Threads posts are sent to the Fediverse, but replies from the Fediverse are subject to Threads rules. This asymmetry is the root of the conflict.
Common Misunderstandings and Edge Cases
“My Fediverse Followers Cannot Reply to My Threads Posts”
If you set reply audience to “Profiles you follow,” only Threads accounts you follow can reply. Fediverse users are not on Threads, so they are never in your follow list. Their replies are always dropped. To allow Fediverse users to reply, set reply audience to “Everyone” on posts you intend to share to the Fediverse.
“A Fediverse User’s Reply Appears on Mastodon but Not on Threads”
This is expected behavior. The reply exists on the Fediverse server where it was created. It is not synced back to Threads because Threads rejected it. The Fediverse user sees their reply on their own server, but it is invisible to Threads users.
“I Changed the Reply Audience After Posting”
Threads does not allow changing the reply audience after a post is published. The setting is locked at the time of posting. If you need to adjust who can reply, you must delete the post and create a new one with the desired audience setting.
Threads Reply Audience vs Fediverse Open Replies: Comparison
| Feature | Threads | Fediverse (Mastodon) |
|---|---|---|
| Reply audience control | 4 levels: Everyone, Followed, Mentioned, Only OP | None at post level |
| Default reply behavior | Everyone can reply | Everyone on any server can reply |
| Protocol support | Proprietary, not in ActivityPub | ActivityPub does not define reply restrictions |
| Reply from Fediverse user | Dropped if audience is not Everyone | Accepted and visible on local server |
| User confusion risk | High when audience is not Everyone | Low because no restrictions exist |
Best Practices for Threads Users Who Share to Fediverse
If you want your Threads posts to receive replies from the Fediverse, set reply audience to “Everyone” before posting. This is the only setting that allows Fediverse replies to appear on Threads. For posts where you need strict reply control, be aware that Fediverse users will be unable to participate in the conversation. Consider posting sensitive or personal topics only within the Threads app and disabling Fediverse sharing for those posts.
Threads reply audience control and Fediverse open replies are fundamentally incompatible at the protocol level. Threads enforces restrictions that the Fediverse ignores, leading to dropped replies and broken conversations. By understanding this conflict, you can choose the right audience setting for each post and avoid confusing your followers on both platforms. For cross-platform conversations, always use the “Everyone” reply audience.