Threads Federated Reply Moderation: Cross-Server Action Limits

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 replies, likes, or reposts you can perform on posts from other servers within a short time window. This article explains exactly what those limits are, why they exist, and how to avoid having your replies silently dropped.

Why Threads Enforces Cross-Server Action Limits

Threads uses ActivityPub to connect with other fediverse platforms like Mastodon, Pleroma, and Pixelfed. This federation allows replies and interactions to flow between servers. However, without rate limits, a single Threads user could flood an external server with hundreds of replies in minutes, causing performance problems or spam complaints. Threads applies cross-server action limits to protect external servers and maintain a stable fediverse experience for everyone.

The limits are enforced at the server level, not per individual post. If you reply to 50 different posts from users on the same Mastodon instance within one hour, you will hit the per-server limit. Similarly, if you spread your replies across five different servers but total 100 actions in an hour, the global limit stops further interactions until the window resets. These limits apply only to actions performed on posts from external servers. Replies to Threads-native posts (users on the same threads.net server) do not count toward these caps.

How the Rate Window Works

The rate limit window is a rolling 60-minute period. Threads does not reset at the top of the hour. If you send your 50th reply to a Mastodon server at 10:15 AM, that action expires at 11:15 AM. You cannot send another reply to that server until after 11:15 AM. The global 100-action limit follows the same rolling logic. Threads does not display a countdown or remaining allowance anywhere in the app.

Steps to Check and Work Within Cross-Server Limits

Threads does not provide a built-in dashboard showing your remaining action allowance. You must track your interactions manually or use a third-party ActivityPub monitoring tool. Follow these steps to minimize the chance of hitting the limit and to recover if you do.

1. Enable Fediverse sharing first
   Open Threads on iOS or Android. Tap your profile icon in the bottom right. Tap the two-line menu in the top right. Tap Privacy. Tap Fediverse sharing. Toggle the switch to On. Without this setting enabled, your replies to external server posts will never reach their destination, regardless of action limits.
2. Space replies to the same server by at least 90 seconds
   Threads applies a secondary per-post rate limit of one reply per post every 60 seconds on external servers. To avoid triggering this, wait at least 90 seconds between replies to different posts on the same external server. This keeps you well under the 50-per-hour ceiling.
3. Limit daily cross-server interactions to 300 total
   While the hourly cap is 100 actions, Threads also applies a daily soft limit of approximately 300 cross-server actions. Exceeding this may temporarily restrict your ability to interact with external servers for 24 hours. Keep a rough count of your replies, likes, and reposts to external accounts each day.
4. Use Threads-native replies for heavy engagement
   If you need to reply to many posts in a short time, focus on posts from Threads-native accounts (threads.net domain). These interactions do not count toward fediverse limits. You can still share those replies via Fediverse sharing later by reposting or quoting them.
5. Wait 60 minutes after hitting a limit
   If your reply fails to post to an external server with no error message, stop all cross-server interactions for at least 60 minutes. The rolling window means your oldest actions will expire first, gradually freeing up your allowance. Do not attempt to retry the same reply repeatedly, as each attempt counts as an action.

What Happens When You Exceed the Limits

When you exceed a per-server or global limit, Threads silently drops your reply. The reply appears in your own thread view as if it posted successfully, but the external server never receives it. The user you replied to will not see your comment. Threads does not display a warning, error message, or notification. This silent failure often leads users to believe the external server or the Fediverse sharing feature is broken.

Reply Appears in Threads but Not on Mastodon

This is the most common symptom of hitting cross-server limits. To confirm, check the post on the external server directly. Open the original post on Mastodon or another platform. If your reply is missing, you have likely exceeded the per-server or global limit. The only fix is to wait for the rolling window to clear your oldest actions.

Threads Account Not Suspended

Exceeding cross-server action limits does not result in an account suspension or shadowban on Threads. The restriction applies only to interactions with external servers. You can still post, reply to Threads-native accounts, and use all other features normally. The limit resets automatically after the rolling window expires.

Threads Cross-Server Limits vs Mastodon Rate Limits

Item	Threads Cross-Server Limits	Mastodon Server Rate Limits
Scope	Actions initiated from Threads to any external fediverse server	Actions initiated from any account on a Mastodon instance
Per-server cap	50 replies per hour per external server	Typically 300 posts or actions per hour (varies by instance admin)
Global cap	100 total cross-server actions per hour	No global cap across instances; only per-account limits on the home instance
Visibility of limit	Hidden — no warning or error displayed	Visible — Mastodon returns an HTTP 429 error with retry-after header
Reset mechanism	Rolling 60-minute window, oldest action expires first	Fixed window per instance admin (often 60 minutes from first action)

Threads limits are more restrictive than typical Mastodon instance limits. Mastodon instances often allow 300 actions per hour per account, while Threads caps cross-server actions at 100 per hour globally. This difference means heavy fediverse users may hit Threads limits far sooner than Mastodon limits.

Understanding these limits helps you plan your fediverse engagement. If you frequently reply to posts on multiple external servers, space your interactions across different hours or focus on Threads-native posts for high-volume conversations. Monitor your reply visibility by checking the external post occasionally to confirm your actions are reaching their destination.