You enabled Fediverse sharing in Threads and your posts appear on Mastodon. But the boost counts from those external servers never show up inside the Threads app. This happens because Threads and the Fediverse count interactions differently. This article explains why the numbers differ and what you can do about it.
Key Takeaways: Threads Boost Counts and Fediverse Discrepancy
- Profile > Privacy > Fediverse sharing: Enables cross-platform posting but does not sync all engagement data back to Threads.
- Boost vs Favorite: Mastodon boosts are not the same as Threads reposts; only Threads-native reposts add to your boost count.
- Manual check: Open the post on your connected Mastodon server to see the true boost count from Fediverse users.
Why Fediverse Boost Counts Do Not Sync to Threads
Threads uses the ActivityPub protocol to send posts to other Fediverse servers like Mastodon. When a user on Mastodon boosts your post, that interaction stays on the Mastodon server. Threads does not pull that boost data back into its own app. The Threads app only counts interactions that happen inside Threads itself.
This is not a bug. It is a design limitation of the current Fediverse integration. Threads treats Fediverse servers as destinations for your content, not as sources of engagement data. The same applies to favorites, replies, and follows that originate on other servers. Only a small subset of Fediverse interactions — such as replies from certain servers — appear in the Threads app.
What Interactions Threads Does Reflect
Threads shows replies from Mastodon users if the Mastodon server is configured to send them. This depends on the Mastodon server’s software version and settings. Boost counts, however, are never sent back. The ActivityPub protocol defines a boost as an “Announce” activity. Threads ignores Announce activities for counting purposes inside its own interface.
How Fediverse Servers Count Boosts
On Mastodon, a boost is a public repost that appears in your followers’ timelines. Each server counts its own boosts independently. If your post is boosted by users on three different Mastodon servers, the total boost count is the sum of all those individual boosts. Threads never sees this total.
Steps to Check Your Real Boost Count
You cannot force Threads to show Fediverse boost counts. But you can view the true number by checking your post on the Fediverse server where it was shared. Follow these steps.
- Open your Threads post
Go to your profile and tap the post you want to check. Tap the share icon and select Copy link. - Paste the link into a Fediverse search
Open your Mastodon account or any public Fediverse server’s web interface. Paste the Threads post URL into the search bar. The server will fetch the post and display its Fediverse ID. - View the post on the Fediverse server
Click the post link in the search results. The page will show the number of boosts and favorites that users on that specific server have given the post. This count is accurate for that server only. - Repeat for other servers
If your post was boosted on multiple Fediverse servers, you must repeat steps 2 and 3 on each server. Add the boost counts together to get the total.
If Threads Still Shows Zero Boosts After a Fediverse Boost
“I boosted a Threads post on Mastodon but the count is still zero”
This is expected behavior. The boost you performed on Mastodon will never appear in the Threads app. Only Threads-native reposts add to the boost count. To confirm the boost worked, check the post on the Mastodon server where you performed the boost. You will see the boost count there.
“My Threads post was boosted by someone else but I see no change”
Again, only boosts that originate within the Threads app are counted. Boosts from other Fediverse servers are invisible inside Threads. The only way to verify that the boost occurred is to view the post on the Fediverse server that sent the boost.
“I see replies from Fediverse users but not boosts”
Replies are sent back to Threads as ActivityPub “Create” activities. Boosts are sent as “Announce” activities. Threads processes Create activities for display but ignores Announce activities for counting. This is a known difference in how Threads handles the two activity types.
Threads App vs Mastodon Server: Engagement Metrics Compared
| Item | Threads App | Mastodon Server |
|---|---|---|
| Boost count source | Only Threads-native reposts | All boosts from users on that server |
| Favorite count source | Only Threads-native likes | All favorites from users on that server |
| Reply visibility | Replies from supported Fediverse servers appear | All replies on that server appear |
| Follow count | Only Threads followers shown | Fediverse followers shown separately |
| Data sync direction | One-way: Threads pushes posts out | Two-way with other Mastodon servers |
The table shows that Threads and Mastodon servers treat the same interactions differently. The Threads app is not a full Fediverse client. It is a publishing tool with limited reception of engagement data.
You now understand why Fediverse boost counts do not appear in Threads. The fix is not a setting change but a change in expectation. Use your Mastodon server’s web interface to check true engagement from Fediverse users. For a complete picture of your post’s reach, add the boost counts from each Fediverse server where your post appears. This manual method is the only way to get accurate numbers today.