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 how to identify a federated reply, report it correctly within Threads, and escalate the issue to the remote server’s administrators when needed.
Key Takeaways: Reporting Federated Replies on Threads
- Three-dot menu on the reply: Tap the three dots icon at the top right of the federated reply to access moderation options.
- Report to Meta: Use the built-in report flow to send a report to Threads moderators for any reply that violates Meta’s policies.
- Report to the remote server: Copy the reply’s permalink and submit a separate report to the remote server’s administrator using their own reporting system.
Understanding Federated Replies in Threads
Threads is connected to the fediverse through the ActivityPub protocol. This means that users on other servers, such as Mastodon or Flipboard, can reply to public Threads posts. Those replies appear in your Threads timeline just like native replies. However, the content is stored on the remote server, not on Meta’s servers.
When you report a federated reply, you are sending a signal to Meta, but Meta can only act on content it controls. If the reply violates Meta’s Community Guidelines, Meta can hide the reply from Threads users or block the remote user from interacting with Threads. But Meta cannot delete the reply from the remote server. To get the reply fully removed, you must also report it to the remote server’s administrators.
How to Identify a Federated Reply
Look for a small icon next to the reply author’s display name. This icon may be a server logo or a generic globe symbol. On the reply’s timestamp, you may see a link that leads to the remote instance. Tapping the timestamp opens the original post on the remote server. If the URL contains a domain other than threads.net, the reply is federated.
Steps to Report a Federated Reply in Threads
Follow these steps to report a federated reply through Threads and to the remote server. You will need the reply visible in your timeline.
- Open the reply in your timeline
Tap the reply you want to report to expand it fully. Ensure you can see the full text and any media attached. - Tap the three-dot menu
Look at the top right corner of the reply card. Tap the three horizontal dots to open the context menu. - Select Report
From the menu, choose the Report option. A new screen appears with a list of violation categories. - Choose a reason
Select the category that best describes the violation: Spam, Hate speech, Harassment, Violence, or Something else. Tap Next. - Confirm the report
Review the details and tap Submit. Meta receives your report and will review it. You will see a confirmation message. - Copy the permalink for remote reporting
Go back to the reply and tap the timestamp. This opens the original post on the remote server. Copy the full URL from your browser’s address bar. - Report to the remote server
Visit the remote server’s website. Look for a Report link in the footer or under the user’s profile. Paste the permalink and describe the violation. Submit the report.
If the remote server does not have a public reporting form, you can send an email to the server’s abuse contact. The contact address is usually abuse@domain.tld. Use the permalink and explain why the content violates the server’s rules.
If Threads Still Has Issues After Reporting
Report Option Is Grayed Out or Missing
Some federated replies may not show the Report option in the three-dot menu. This happens when the remote server has restricted the visibility of the reply. In this case, you cannot report the reply through Threads. You must report it directly to the remote server using the permalink method described above.
Reply Is Still Visible After Meta Removes It
Meta can hide the reply from Threads users, but the reply remains on the remote server. Other users on the fediverse who access the remote server directly can still see it. To remove the content entirely, you need the remote server administrator to delete it. Follow the remote reporting steps and check the remote server’s moderation policy for response times.
Remote Server Does Not Respond
If the remote server is unresponsive or has no active administrators, the reply may remain indefinitely. In this case, you can block the remote user in Threads. Open the user’s profile, tap the three-dot menu, and select Block. This prevents that user from seeing your posts or replying to them in the future. Blocking does not remove existing replies, but it stops new interactions.
Threads Native Report vs Federated Report Compared
| Item | Native Threads Reply | Federated Reply |
|---|---|---|
| Content location | Stored on Meta’s servers | Stored on remote ActivityPub server |
| Meta can remove | Yes, completely | No, can only hide from Threads |
| Reporting within Threads | Full report flow available | Report flow available but limited |
| Need remote report | No | Yes, for full removal |
| Blocking effectiveness | Stops all interactions | Stops future interactions only |
Reporting a federated reply requires a two-step process. Use the Threads report to alert Meta and block the user. Use the remote server’s reporting system to request content removal. This dual approach ensures the violation is addressed on both platforms.