Threads now gives users 15 minutes to edit posts and lets users who have connected their accounts to the fediverse see who follows them and likes their posts
RE: https://www.threads.net/... Anuj Ahooja / @quillmatiq : I think it's cool that this many people follow me on the Fediverse with no extra effort on my part, but what's cooler is that they follow me across 94 servers...It could include different Mastodon servers, Flipboard, micro[dot]blog, solo servers - w/e they choose to use to tap into the network. But 94 different platforms running their choice of software and user experience, all connected via a protocol. Incredible. @0xjessel : my fediverse replies like to joke that there's only dozens of them out there, but actually seeing this number is insane. wow. congrats to our fediverse team for getting this out the door. one step closer to 2-way interoperability Tim Chambers / @timothyjchambers : So for my own person non-influencer account as an example, just by turning on Fediverse sharing my social reach grew by 7.36%.... not bad for one settings change that took 2 minutes and required zero additional work on my part. Fediverse sharing FTW! — RE: https://www.threads.net/... Casey Newton / @crumbler : Interesting trade-offs here! — RE: https://www.threads.net/...
Context & Ripple Effects
Threads' federation work moved from a test of making Threads posts available to ActivityPub services to a regional beta that supported cross-posting and federated likes. The latest step makes that distributed audience more legible to people who opt in.
It follows August changes that expanded the ability to view and like fediverse replies beyond a user's own posts. A later addition allowing follows of interacting fediverse accounts suggests the product path is gradually turning cross-network visibility into usable social connections.
First-order effects
- Threads users gain a 15-minute correction window, reducing the cost of publishing a post with an error.
- Users who connect to the fediverse can now see follower and like activity from across participating services, rather than treating that engagement as largely invisible.
Second-order effects
- Federated creators have a clearer incentive to connect their accounts because engagement from multiple servers becomes attributable and visible.
- Other ActivityPub-compatible services face more pressure to expose understandable cross-service identity and engagement signals if they want interoperability to feel useful to ordinary users.
Third-order effects
- If Threads continues converting federation from passive syndication into follows and engagement workflows, interoperability may compete on product usability—not simply protocol support.
- The durable challenge will be trust: cross-network counts and identities need to remain intelligible enough that users can assess what engagement means across different services.
The trend: Social platforms are progressively productizing open-protocol connections, moving from content distribution toward cross-network audience management.