Threads adds new dedicated feed for fediverse content

Meta’s Threads is deepening its integration with the fediverse, a collection of decentralized social media platforms that includes Mastodon. Starting today, users who have enabled sharing to the fediverse in Threads will be able to see posts from federated accounts that they follow. These posts will now appear in a dedicated feed.

From this feed, users can now search for federated users from within Threads. These posts will populate in reverse chronological order, ensuring the newest posts from accounts you follow appear first.

Decentralized platforms currently compatible with Threads include Mastodon, Bookwyrm, WriteFreely and more, with Meta hoping more services will sign on in the future. When searching for fediverse accounts, simply input their username and corresponding service into the search bar, such as “@flipboard@flipboard.social,” and if an exact match exists, their profile will appear alongside the fediverse icon.

Meta has spent the last year working on building the fediverse into the Threads experience, and the company says that Threads “has interacted with over 75 percent of all fediverse servers” since sharing to the fediverse was launched a year ago.

The social media conglomerate states that its goal “remains to grow the fediverse responsibly, prioritizing the success of a safe community from multiple platforms and with multiple points of view.” Integrations like the features being launched today, however, make it much easier for the company’s users to see federated posts without ever navigating away from Threads to do so. Furthermore, fediverse engagement on Threads remains an “opt-in” feature, and replies you receive to posts shared in the fediverse are still not integrated into Threads.

This article originally appeared on Engadget at https://www.engadget.com/big-tech/threads-adds-new-dedicated-feed-for-fediverse-content-174105370.html?src=rss https://www.engadget.com/big-tech/threads-adds-new-dedicated-feed-for-fediverse-content-174105370.html?src=rss