Threads, Meta’s microblogging platform, is built on the ActivityPub protocol. This means it can connect to other services in the fediverse, such as Mastodon and Pixelfed. Server administrators who run their own federated services may need to manage which other servers their users can interact with. Defederation is the act of blocking an entire server … Read more
When you receive a reply to your Threads post, it can be difficult to know whether the reply came from another Threads user or from someone on a federated server like Mastodon. The reply appears in your notifications and in the post thread, but the visual indicators are subtle. This article explains the specific signs … Read more
When you reply to a post on Threads, a small icon sometimes appears next to your reply. This icon tells you whether your reply will be shared outside of Threads to other Fediverse platforms like Mastodon. Many users are unsure what this icon means or why it appears only on certain replies. This article explains … Read more
You are getting unwanted notifications from a fediverse user who replies to your public Threads posts. This happens when your account has fediverse sharing enabled and an ActivityPub user on Mastodon or another compatible server interacts with your thread. Their replies appear in your Threads notification list just like any other reply. This article explains … Read more
Threads now supports a per-user mute for the Fediverse, giving you more control over which accounts from other servers appear in your timeline. When you mute a user from Mastodon, Pixelfed, or any ActivityPub platform, their posts stop showing up on Threads without blocking or reporting them. This article explains exactly what the mute does, … Read more
When you see a reply on Threads that originated from another server in the fediverse, the standard reporting tools may not work as expected. This happens because federated replies are hosted on a remote server, not on Meta’s infrastructure. Meta’s moderation team cannot directly remove content that lives on another ActivityPub server. This article explains … Read more
When you reply to a Threads post from a user on a different federated server, such as Mastodon or another ActivityPub instance, your reply may be blocked or hidden without a clear error message. This happens because Threads applies cross-server action limits to prevent spam and abuse across the fediverse. These limits restrict how many … Read more
Threads allows you to share your public posts with other platforms that use the ActivityPub protocol, such as Mastodon. This feature is called Fediverse sharing. When enabled, your public Threads posts appear on Mastodon servers, and your profile becomes visible to Mastodon users. This article explains how to set up Fediverse sharing in Threads and … Read more
You want your Threads posts to appear on Mastodon and also allow replies from Mastodon users to flow back into Threads. This two-way connection is called round-trip posting. It relies on the ActivityPub protocol, which Threads supports in a limited way. This walkthrough explains how to set up that connection and what you can realistically … Read more
Fediverse sharing lets your Threads posts appear on platforms like Mastodon and other ActivityPub-compatible services. For verified accounts, the process is identical to standard accounts, but you must ensure your profile meets all requirements. This article explains the prerequisites and the exact steps to turn on fediverse sharing for your verified Threads account. Key Takeaways: … Read more