Threads now lets users see and like fediverse replies on other posts besides their own, and will syndicate posts submitted via the Threads API to the fediverse
Threads is deepening its ties to the fediverse, also known as the open social web, which powers services like X alternative Mastodon …
TechCrunchSarah Perez
Context & Ripple Effects
This extends Threads’ earlier beta federation rollout, which enabled cross-posting and visibility into some activity from federated services. The new steps move interoperability from a limited account-level connection toward interaction on posts users do not own and distribution for API-published content.
The direction is reinforced by the later ability to follow fediverse accounts that interacted with a Threads post, although discovery remains bounded by where Threads chooses to surface outside-network activity. That distinction makes usability—not merely protocol support—the central issue.
First-order effects
Threads users can now view and like fediverse replies attached to other users’ posts, broadening the set of cross-network conversations they can participate in.
Developers publishing through the Threads API gain syndication to the fediverse, giving their submitted posts a distribution path beyond Threads itself.
Second-order effects
Fediverse services such as Mastodon can receive more Threads-originated material, while Threads gains a reason for creators and API developers to treat it as an entry point to open-social distribution.
Cross-network engagement becomes more valuable only if it is legible to users; Threads’ later follower and like visibility for connected accounts shows the product work required to turn federation into a recognizable social graph.
Third-order effects
If Threads continues to expose more replies, follows, and publishing across networks, federation could shift from a portability feature to a competitive distribution layer spanning otherwise separate social services.
The durable constraint is likely to be usable openness: large platforms can support federation while retaining control over feed placement, discovery, and the user interface through which outside activity is experienced.
The trend: This is one step in the shift from isolated social apps toward selectively interoperable networks, where interface and discovery choices determine how open protocols translate into real reach.
This is happening! One more thing: Since June, Threads users who are sharing to the fediverse have been able to see and like replies from the fediverse on their own posts in Threads. This week, we're starting to roll out the ability for Threads users who've turned on sharing to…
🪐🪐 Mini Fediverse Launch Today 🪐🪐 — 1) Now (in most geo regions) you can see replies from the Fediverse on posts you *didnt* make! Try going to the replies on a post from @mkbhd or @reckless1280 and you'll likely see the fediverse reply row... and you can like the replies in t…
In the before times, Twitter was the place to air customer service complaints, esp airlines.. I've seen a lot of people trying this w/ Threads but it doesn't seem like most companies monitor their accounts here in the same way (prob lack of Threads API level tools)...
Thank you all! I'm hoping following Fediverse accounts here is coming. Please continue to support making text based social media a real, sustainable town square @mosseri @zuck
I continue to be surprised and delighted that Threads is following through on its promise to federate. I also appreciate that they're doing it in a slow, deliberate way. They could easily just not do these things. Kudos! — RE: https://www.threads.net/...
It's done! Threads now has two-way federation! If you're comfortable being on an instance that hasn't fediblocked Threads, now is the time to engage constructively with your people over on Threads on the issues they care about, so they can learn the Fediverse exists, see how it…