"This content isn't available" — which means four different things

“This content isn’t available at the moment.” It could mean the person blocked you. Or deleted the post. Or narrowed who can see it. Or Facebook removed it for a policy violation. Four unrelated situations, one identical screen — and no way to tell from the message which one you’re looking at.

The steelman, and it’s a real one

This is not primarily condescension, and it’s worth saying so clearly, because the obvious reading is wrong. Platforms deliberately refuse to confirm blocks to protect the person who blocked.

Telling someone “X blocked you” hands actionable information to the exact people it’s most dangerous to inform. For a stalker or an abusive ex, confirmation that they’ve been noticed and cut off is a documented escalation trigger — new accounts, other platforms, real-world retaliation. Quiet blocking is a genuine safety feature, and the ambiguity is doing real work for real people in real danger.

So the vagueness isn’t stupid. The problem is that it doesn’t work, and it over-applies.

It fails against exactly the threat it’s for

You can distinguish the four cases in about five seconds by opening a private window. That’s not an exploit — it’s the standard advice in every help article on the subject.

Which inverts the whole design:

• The determined bad actor — the stalker, the person the safety feature exists to stop — absolutely will check, and learns the truth immediately.
• The ordinary confused person — who wasn’t a threat to anyone — doesn’t think to, and is left guessing about a relationship, a deleted post, or their own account.

Protection defeated by a five-second workaround only stops the people who weren’t dangerous. That’s the textbook shape of security theatre: the appearance of protection, borne entirely by the harmless.

And three of the four cases need no protection at all

Only blocked is sensitive. The rest are safe to state plainly:

One message covering all four means a safety mechanism designed for a rare, serious case has been applied to three common, harmless ones — where its only effect is to leave ordinary people confused. Narrow the vagueness to the case that needs it.

The math

3.07B users × 20% × 4 times/yr × 60s = ~60 lifetimes / year

Is treating people like idiots good business?

It’s cheap in the short run — vague errors mean fewer support tickets, fewer arguments about moderation, less to be held to. But it has a compounding cost this site keeps running into: an interface that is routinely unreliable trains people to disregard everything it says. Once you learn that “isn’t available at the moment” means nothing in particular, you stop reading the messages that do matter.

That’s the same failure as case 007, where a local disconnect is blamed on the server, and the same fatigue that makes cookie consent meaningless. Every message that doesn’t mean what it says devalues the whole channel.

Difficulty to fix: moderate

Say what happened when saying it is safe — deleted, restricted, removed. Keep the quiet only for the one case that genuinely needs protecting. Right now the safety design for a rare, serious situation is being paid for by everyone else’s confusion, while the people it guards against just open a private window.