How to Verify Federated Reach of a Threads Post
🔍 WiseChecker

How to Verify Federated Reach of a Threads Post

When you enable fediverse sharing on Threads, your public posts can reach people on Mastodon and other ActivityPub servers. But how do you know if your post actually made it outside the Threads app? Without a way to check, you might wonder whether your content is being seen by a wider audience. This article explains how to verify whether a Threads post has been shared to the fediverse and how to confirm its reach on other platforms. You will learn the exact steps to inspect post metadata, use fediverse search tools, and interpret the signals that indicate successful distribution.

Key Takeaways: How to Verify Federated Reach of a Threads Post

  • Post URL + ?format=activity+json: Append this parameter to any Threads post URL to view its ActivityPub representation and confirm federation.
  • Mastodon search for Threads post ID: Use the last segment of the Threads post URL as a search term on Mastodon to find the post on a remote server.
  • Fediverse search tools like FediDB: Enter your Threads profile URL to see which servers are receiving your posts.

ADVERTISEMENT

What Federated Reach Means for Your Threads Posts

Threads uses the ActivityPub protocol to send public posts to other fediverse platforms. When a post is federated, it becomes available on Mastodon, Pleroma, and other ActivityPub-compatible servers. The post appears as a regular status on those platforms, including replies, likes, and boosts from users who are not on Threads. However, federation is not automatic for every post. Only public posts from accounts that have enabled fediverse sharing are distributed. You can check this setting in your Threads profile under Privacy > Fediverse sharing.

To verify that a specific post has been federated, you need to inspect its ActivityPub metadata. Every federated post has a unique ActivityPub ID that other servers can resolve. If the ID is accessible, the post is being shared. If you cannot retrieve the ActivityPub representation, the post may not have been federated, or your account may not have the feature enabled. Understanding these signs helps you confirm that your content is reaching the broader fediverse.

Steps to Verify Federated Reach of a Threads Post

Use the following methods to check whether a Threads post has been sent to the fediverse. Each method gives you a different level of confirmation.

Method 1: Check the ActivityPub Representation of the Post

  1. Open the Threads post in your browser
    Go to the Threads post you want to verify. Copy the post URL from the address bar. The URL looks like https://www.threads.net/@username/post/123456789.
  2. Append the ActivityPub query parameter
    Add ?format=activity+json to the end of the URL. For example: https://www.threads.net/@username/post/123456789?format=activity+json.
  3. Load the modified URL
    Press Enter to load the URL. If the post is federated, you will see a JSON object containing ActivityPub data. The JSON includes fields such as @context, id, type, object, and published. If you see a Threads webpage or an error page, the post is not federated.
  4. Look for the id field
    In the JSON, find the id field. Its value is the ActivityPub ID of the post. This ID confirms that the post has been published to the fediverse. Copy this ID for use in the next method.

Method 2: Search for the Post on Mastodon

  1. Extract the post ID from the Threads URL
    In the Threads post URL, the last segment after the last slash is the post ID. For example, in https://www.threads.net/@username/post/123456789, the ID is 123456789.
  2. Log in to your Mastodon account
    Open your Mastodon instance and log in. You need an account on any Mastodon server to perform the search.
  3. Use the Mastodon search box
    Paste the post ID into the search box. Press Enter. If the post has been federated to that instance, you will see it appear in the search results. You can also search for the full ActivityPub ID from Method 1.
  4. Check for the post on other instances
    If your Mastodon instance has not received the post, try searching on a different instance. You can use a public instance like mastodon.social. If the post appears on any instance, it has been federated.

Method 3: Use a Fediverse Search Tool

  1. Open FediDB or a similar tool
    Go to FediDB (fedidb.org) or another ActivityPub search tool. These tools index public fediverse activity.
  2. Enter your Threads profile URL
    Paste your full Threads profile URL into the search field. For example: https://www.threads.net/@username.
  3. Review the search results
    The tool will show a list of recent posts from your account that have been federated. You can click on a post to see its ActivityPub details. If your post appears in the results, it has been successfully shared.

ADVERTISEMENT

If the Post Does Not Appear Federated

A post may not show up in the fediverse for several reasons. First, verify that your account has fediverse sharing enabled. Go to Profile > Privacy > Fediverse sharing and ensure the toggle is on. Second, check that the post is set to public. Only public posts are federated. If the post is set to followers only or mentioned accounts only, it will not be distributed. Third, federation can take a few minutes. Wait at least 10 minutes after posting before checking again. If the post still does not appear, the Threads server may be experiencing delays. Try checking again later.

Threads Profile Does Not Show the Federated Sharing Option

If you do not see the fediverse sharing option in your Threads settings, your account may not be eligible. Fediverse sharing is currently available only in certain regions and for accounts that have not been restricted. You can check the official Threads help center for the latest availability. If your account is eligible but the option is missing, update the Threads app to the latest version.

The ActivityPub JSON Returns a 404 Error

A 404 error when you load the ?format=activity+json URL means the post is not federated. This can happen if the post was deleted or if your account lost fediverse access. Double-check your account settings and try a different post. If the issue persists, contact Threads support.

Threads Post Federation Status: Indicators Compared

Indicator Federated Not Federated
ActivityPub JSON at ?format=activity+json Returns valid JSON with id field Returns HTML page or error
Mastodon search for post ID Post appears in search results No results found
FediDB profile search Post listed in recent activity Post not listed
Fediverse sharing toggle in settings Enabled Disabled or missing

You can now verify whether your Threads posts are reaching the fediverse by using the ActivityPub query parameter, Mastodon search, or fediverse tools. Start by checking one post using the ?format=activity+json method. If you confirm federation, try searching for the post on Mastodon to see how it appears to remote users. For ongoing monitoring, bookmark the FediDB tool and check your profile periodically. Remember that only public posts from accounts with fediverse sharing enabled will be distributed.

ADVERTISEMENT