Threads and the Fediverse: ActivityPub Integration Explained (2026)

Meta's Threads is doing something no Big Tech platform has done before: connecting to the open, decentralized web. Through the ActivityPub protocol, Threads users can interact with Mastodon, Pixelfed, and thousands of independent servers. Here's exactly how it works, what's live today, and what it means for creators.

1. What Is the Fediverse?

The fediverse (a portmanteau of "federated" and "universe") is a network of interconnected social media servers that communicate using open protocols. Instead of one company owning the entire network, anyone can run a server and connect it to the wider ecosystem.

Think of it like email. You can send a message from Gmail to Outlook to ProtonMail because they all speak the same protocol (SMTP). The fediverse works the same way, but for social media. A user on Mastodon can follow someone on Pixelfed, comment on a Lemmy post, or — now — interact with a Threads account.

That last number is the reason Threads joining the fediverse is such a big deal. Threads alone has roughly 28 times more users than the entire rest of the fediverse combined. Whether you see that as an opportunity or a threat depends on who you ask — but we'll get to that.

2. ActivityPub: The Protocol Behind It

ActivityPub is a W3C-recommended open standard published in 2018. It defines how servers send and receive social activities — posts, likes, follows, replies, boosts — in a structured JSON format called Activity Streams 2.0.

How it works in practice:

1. You publish a post on Threads (or any ActivityPub server)
2. Your server sends the post to the inboxes of every server that has followers subscribed to you
3. Each receiving server validates the message, stores it, and displays it to the relevant users
4. Replies flow back through the same mechanism in reverse

The key principle is that no single server controls the network. If Mastodon.social goes down, the thousands of other Mastodon instances keep running. If Threads were to shut down federation tomorrow, the rest of the fediverse would continue unaffected — users would just lose access to Threads content.

This stands in sharp contrast to closed platforms. When Twitter became X, users had no choice but to accept the changes or leave. With ActivityPub, your identity and social graph are portable. You can migrate your followers from one server to another without starting from zero.

Platforms that use ActivityPub:

Note that Bluesky uses a different protocol called the AT Protocol (atproto). The two networks are not interoperable — you cannot follow a Bluesky account from Mastodon or Threads via federation.

3. How Threads Federation Works

Threads implements ActivityPub as an opt-in feature. Federation is not on by default — you have to enable it manually in your account settings.

How to turn on fediverse sharing:

1. Open Threads and go to Settings
2. Tap Account
3. Tap Fediverse Sharing
4. Toggle it on and confirm

Once enabled, your public Threads posts become visible on any federated server. Your Threads handle becomes discoverable in the @username@threads.net format. Mastodon users, Pixelfed users, and anyone else on the fediverse can search for that address, follow you, and see your posts in their timeline.

What happens under the hood:

When you publish a post on Threads with federation enabled, Meta's servers format your content as an ActivityPub Create activity and deliver it to the inbox of every remote server that has at least one user following you. Replies from those servers arrive as Note activities in your Threads inbox and appear alongside native Threads replies.

Your Threads profile essentially becomes a node in a global, open network — while still being accessible through the familiar Threads app.

4. Federation Timeline & Current Status

Meta has taken a gradual approach to federation. Here's the timeline:

5. What Works (and What Doesn't)

Federation is functional but not complete. Here's an honest breakdown of where things stand.

What works today:

• Posts — Public Threads posts appear on federated timelines
• Replies — Fediverse users can reply, and those replies show up on Threads
• Follows — Cross-platform following works in both directions
• Likes — Federated likes are counted (though displayed differently per platform)
• Profile discovery — Search @username@threads.net from any ActivityPub platform
• Images and media — Attached images federate with posts

What doesn't work yet:

• Direct messages — DMs stay within Threads; no cross-platform messaging
• Stories and polls — These are Threads-native features with no ActivityPub equivalent
• Full post editing — Edits on Threads may not propagate to all federated servers
• Algorithmic feeds — Fediverse servers show posts chronologically; Threads' recommendation algorithm doesn't apply there
• Granular audience control — You can't federate some posts but not others; it's all-or-nothing for public posts

For a deeper comparison of how Threads compares to Mastodon as a platform, including audience size, moderation approaches, and content discovery differences, see our dedicated breakdown.

6. Privacy and Control

Privacy is the most common concern about Threads federation — and rightfully so. When your posts leave Meta's servers, they're stored on independently operated machines around the world. Here's what you need to know.

What Meta controls:

• Opt-in by default — Federation is off until you enable it
• Public posts only — Followers-only and private posts are never federated
• Deletion requests — When you delete a post or disable federation, Threads sends an ActivityPub Delete activity to all known servers
• Block propagation — Blocking a fediverse user prevents them from seeing your content on their server

What Meta doesn't control:

• Remote server compliance — Federated servers are independently operated. A rogue server could theoretically ignore deletion requests
• Caching and archiving — Third-party servers may cache your content even after you revoke sharing
• Instance-level blocks — Some Mastodon instances preemptively block threads.net, meaning their users can't see your federated content at all

"Federation means your public posts are public in the truest sense. If you're comfortable posting it on the open web, you'll be comfortable with fediverse sharing."

The practical advice: treat federated posts like public blog posts. If you'd publish it on a website, enable federation. If it's something you'd want the ability to fully retract, keep federation off or don't post it publicly in the first place.

7. What This Means for Creators

If you're building an audience on Threads, federation changes the game in several important ways.

The upside:

• Larger addressable audience — Your posts can reach the 16M+ fediverse users without those people ever downloading Threads
• Platform insurance — If anything changes on Threads (algorithm shifts, policy changes, monetization pivots), your federated followers still see your content
• Cross-platform discovery — People find you through Mastodon searches, Pixelfed feeds, or WordPress-powered blogs that show federated content
• SEO benefits — Some fediverse platforms index posts publicly, creating additional surface area for search engines

The considerations:

• Engagement metrics split — Likes and replies from the fediverse may display differently in Threads analytics
• Moderation complexity — You may receive replies from fediverse users who aren't subject to Threads' community guidelines
• No algorithmic boost — Fediverse timelines are chronological. The Threads algorithm that helps new posts get discovered doesn't extend to federated servers

For most creators, the answer is straightforward: turn federation on. The incremental reach is free, the privacy trade-off is minimal for public content, and having a presence on the open web is increasingly valuable. If you want the complete playbook for building your Threads audience, check our guide on how to grow on Threads in 2026.

8. Frequently Asked Questions