You have enabled Fediverse sharing in Threads, but replies from Mastodon or other ActivityPub servers do not appear in your Threads timeline or post view. This is not a bug in most cases. It is a deliberate design choice by Meta regarding how federated content is displayed. This article explains the technical reason why remote replies are hidden and what you can do about it.
Key Takeaways: Why Federated Replies Are Hidden in Threads
- Threads shows only local replies by default: Replies from Mastodon and other ActivityPub servers are not displayed in the Threads UI to keep the experience simple.
- Remote replies exist on the originating server: Federated replies are stored on the remote server and can be viewed there, not inside Threads.
- No setting to show remote replies in Threads: Meta has not added a toggle to display federated replies in the Threads interface as of early 2025.
Why Threads Hides Federated Replies from Other Servers
Threads uses the ActivityPub protocol to share your public posts with Mastodon, Pleroma, and other Fediverse servers. When someone on Mastodon replies to your Threads post, that reply is created on their home server. The reply is then sent to Threads via ActivityPub. However, Threads does not display that reply in your post’s reply thread inside the Threads app or website.
The root cause is that Meta designed Threads as a single-server social network with limited federation. Unlike Mastodon, where replies from any server appear in the same timeline, Threads treats remote replies as separate objects. They are stored in Threads’ database but are not rendered in the UI for most users. Meta has stated this is intentional to avoid confusion with content that may violate their policies or that cannot be moderated under their terms.
Another technical factor is that Threads does not fetch the full context of a federated thread. When a Mastodon user replies to your post, Threads receives the reply object but does not request the parent conversation from the remote server. This means Threads cannot build a complete threaded view that includes both local and remote replies. The result is that remote replies are silently dropped from the interface.
What Happens to the Remote Reply Data
The remote reply is still received and stored by Threads. You can verify this by checking your post’s ActivityPub representation directly. But the reply is never shown in the Threads timeline, notifications, or post detail page. The only way to see it is to visit the remote server where the reply was originally posted.
How to Verify That Federated Replies Are Being Sent
Before assuming something is broken, confirm that Fediverse sharing is actually working. Follow these steps to check the connection between your Threads account and a Mastodon server.
- Open your Threads profile
Tap your profile picture in the bottom-right corner of the Threads app. - Go to Settings
Tap the two horizontal lines icon in the top-right corner, then select Settings. - Navigate to Account
Tap Account in the Settings menu. - Tap Fediverse sharing
This option appears under Account. If you do not see it, your account is not eligible or the feature is not available in your region. - Confirm the toggle is on
If the toggle for Share your public posts to the fediverse is green, sharing is active. If it is off, turn it on. - Post a public Threads post
Create a new post with the globe icon selected for public visibility. Wait a few minutes. - Search for your post on a Mastodon instance
Use a Mastodon search tool or visit a Mastodon server’s federated timeline. Search for your Threads handle in the format @username@threads.net. If the post appears, federation is working.
If the post appears on Mastodon but replies from Mastodon users do not show up in Threads, the behavior is by design. There is no fix to make them appear because Meta has not implemented that feature.
Related Issues: Other Federated Content That Does Not Display
Federated Likes and Boosts Not Showing in Threads
When a Mastodon user likes or boosts your Threads post, that interaction is sent to Threads but is not displayed in your notifications or on the post. Only likes and boosts from Threads users appear in the UI. This is another deliberate limitation of Threads’ federation implementation.
Federated Followers Not Visible in Threads Follower List
If someone follows you from Mastodon, you cannot see them in your Threads follower list. Threads only shows followers who have a Threads account. The remote follower exists in the Fediverse but is not surfaced in the Threads UI. You can verify the follow by checking your post’s ActivityPub audience data via a tool like FediFetcher.
Remote Posts Not Appearing in Threads Search
Threads search only indexes posts created on Threads. Posts from Mastodon or other servers that mention your Threads handle will not appear in Threads search results. To find those posts, you must search on the remote server directly.
Threads vs Mastodon: Where Federated Replies Appear
| Item | Threads | Mastodon |
|---|---|---|
| Local replies displayed in UI | Yes | Yes |
| Remote replies displayed in UI | No | Yes |
| Remote likes shown in notifications | No | Yes |
| Remote followers visible in follower list | No | Yes |
| Posts searchable across servers | No | Yes |
Threads federation is one-way for most interactions. Your posts go out to the Fediverse, but remote interactions do not come back into the Threads interface. Mastodon displays all federated content equally because it was built for the Fediverse from the start.
Federated replies not appearing in Threads is not a malfunction. It is a limitation of how Meta implemented ActivityPub. Your posts are shared across the Fediverse, and replies from other servers exist on those servers. To see them, you must visit the remote server. If you want full two-way federation, consider using a Mastodon account directly. For now, Threads remains a one-way publishing tool for the Fediverse.