Who Can Reply Settings on X: What They Mean for What You See

A thread with only a handful of replies isn't always a thread nobody cared about. Sometimes the poster limited who could reply in the first place, and everyone outside that group got a "you can't reply to this" message instead of a chance to weigh in. Knowing the setting exists changes how you read a quiet reply count.

The four levels

X gives posters one control with four settings, choosable before posting or changed anytime after:

• Everyone — the default. Any account can reply.
• Accounts you follow — only people the poster follows can reply.
• Only accounts you mentioned — replies are limited to the specific handles named in the post itself.
• Verified accounts — only accounts with a verification badge can reply.

Whichever level is active, it only gates new replies. It does not touch who can view the post or read the replies that already exist.

How to tell a thread is restricted

X shows a short label near the post's timestamp when a restriction is on, something like "Only accounts [poster] follows can reply." If that label is missing, replies are open to everyone and the reply count reflects genuine turnout. If it's there, the count reflects turnout from a narrower pool, and treating it as a proxy for "how much people cared" is misleading.

What you can and can't see as a reader

This is the part that trips people up: a reply restriction has nothing to do with what you can read. If you're not in the allowed group, you can still open the thread and see every reply that made it through — you just can't add one of your own. The greyed-out reply box, sometimes with an explanation, is the only visible difference. Everything downstream of that — sorting by best or newest, seeing past the ranked order, searching the thread — works exactly the same as on an unrestricted post.

Where it does matter for reading is completeness. A "mentioned only" thread has, by definition, excluded every reply from someone the poster didn't tag. If you're trying to gauge broad reaction to something, a restricted thread gives you a curated slice, not a representative sample. That's a different problem from replies being hidden or collapsed after the fact — here, the missing voices never had the chance to post at all.

Why the setting exists

Posters reach for reply restrictions for a few honest reasons: cutting down pile-ons on a sensitive announcement, keeping a mentions-only thread on topic when it's really a conversation between a small group, or avoiding a flood of low-effort replies on something that's likely to go wide. It's a moderation tool aimed at the reply box, not at readers, and most people who open a restricted thread never notice it's on unless they try to reply themselves.

It's also worth knowing the setting is a blunt instrument, not a quality filter. Restricting replies to "accounts you follow" doesn't screen for good replies, it screens for a specific relationship to the poster. A poster's follows can be just as prone to a low-effort one-liner as a stranger would be — the restriction changes who gets to try, not how good what they say turns out to be. That's a different lever from the quality filtering that runs on every reply regardless of who posted it, which does score for spam and low effort but has nothing to do with the poster's relationship settings.

The timing catch

Because the setting can change after the post goes live, a thread's reply population can shift hours or days later. A poster who started with "mentioned only" to keep an early conversation contained can switch to "everyone" once the initial back-and-forth settles, and a new batch of replies from previously-excluded accounts shows up all at once. If you read a thread early and come back later expecting the same shape, a widened restriction is one reason it can look different.

The SkimFast way

None of this changes how SkimFast reads a thread — restrictions are decided on X's side before a reply ever exists, and SkimFast just shows you what's there. What it changes is how easy it is to notice the label and read the resulting replies without extra taps. SkimFast opens the full reply thread in a popover right in your timeline, so checking whether a quiet thread is restricted or just genuinely quiet doesn't cost you a reload.

A quick way to read a quiet thread

1. Check for the restriction label near the timestamp before assuming a short reply list means low interest.
2. If it's restricted to "mentioned only," treat the replies as a curated slice, not the full reaction.
3. If you're revisiting a thread, check whether the restriction loosened since your last visit — that's the usual explanation for a sudden jump in replies.
4. Restriction and ranking are separate steps; once a reply gets through, it's sorted the same as anything else.

A restricted thread isn't hiding anything from you as a reader — it's just working from a smaller pool of people who were ever allowed to answer. Spotting the label takes the guesswork out of a quiet reply count, and SkimFast makes checking it as easy as opening the thread itself.