Threads, ActivityPub, and Fediverse Media Federation

Executive Summary

Threads implements the open W3C ActivityPub protocol, allowing public posts to federate to external platforms like Mastodon. When a post federates, media attachments are referenced as ActivityStreams objects pointing to Meta CDN nodes or cached by recipient servers.

In March 2024, Meta began enabling Fediverse sharing for Threads users. This rollout connected Threads to the open, decentralized social web powered by the ActivityPub protocol.

What is the Fediverse?

The Fediverse is a decentralized network of independent servers that communicate using standard protocols. Instead of one corporation owning all servers, independent communities run software such as Mastodon, Pixelfed, and PeerTube.

By supporting ActivityPub, a user on Mastodon can follow a Threads creator, view their updates, and reply without ever registering a Threads account.

The ActivityPub Object Model

Under the hood, ActivityPub messages are serialized as JSON-LD documents called ActivityStreams. When a creator publishes a post with a video on Threads:

{
  "@context": "https://www.w3.org/ns/activitystreams",
  "id": "https://threads.net/users/123/posts/DdcPsEkH3NZ",
  "type": "Note",
  "attributedTo": "https://threads.net/users/123",
  "content": "Check out this project update!",
  "attachment": [
    {
      "type": "Document",
      "mediaType": "video/mp4",
      "url": "https://scontent.cdninstagram.com/v/t50.2886-16/...",
      "name": "Project Video"
    }
  ]
}

Notice the attachment array:

  • It defines the media type (video/mp4).
  • It links to the Meta CDN stream URL.
  • Receiving Fediverse servers fetch this stream and cache it for their local users.

Implications for Media Access

  1. Protocol Interoperability: Because ActivityPub uses standard web URLs and MIME types, public posts are designed to be read by independent software clients.
  2. Actor Identity: User identities are tethered to the @username@threads.net namespace, maintaining stable author attribution across servers.
  3. Open Standards Alignment: Media follows open standards (MP4 containers, AVC video, JPEG images), ensuring that videos play seamlessly regardless of which client views them.

Read more about domain routing in our explainer on Threads.net vs Threads.com or learn how Threaa Resolves Public Media.

References & Technical Sources