Nothing announces that a route went quiet

The mechanism, or the absence of one

A retired onion address does not forward anywhere. There is no redirect from a service that has stopped answering, because a redirect is something a running service sends and there is nothing running.

So the address simply stops producing answers. That is the entire event, and it looks exactly like a temporary failure.

Why there is no notice either

A notice would have to be published somewhere a reader already trusts and already checks. There is no such place that is not itself an address that could go quiet, and a notice sent through any other channel is indistinguishable from a message somebody made up.

That is not a failure of anyone's diligence. It is a structural gap, and it is why this subject has the shape it does.

The consequence for every list

Every page that publishes a set is downstream of a decision it cannot see, with no channel that would tell it when the decision changed. Lists therefore go stale silently, and a list that has not been touched looks exactly like one that has been confirmed.

That is the whole argument of how a list goes stale, and it applies to this site as much as to any other.

The consequence for a reader

• You will find out by trying, which means you find out at the least convenient moment.
• You will not be able to tell a retired route from a temporarily quiet one, as quiet and then back describes.
• You cannot rely on any page to tell you, including this one.
• Your own copy of the set is as current as the last time you refreshed it, and nothing will remind you.

What this rules out

It rules out the whole class of solutions people reach for: subscribe to something, follow an announcement, get an alert. None of those can work here, because the channel that would carry them is exactly the thing that is missing.

Anything offering that service is offering something it cannot deliver, whatever its intentions.

What is left

Redundancy and refreshing. Hold all three so that one going quiet is absorbed rather than discovered. Refresh your copy occasionally from a source you already use, at a moment when nothing has failed, rather than urgently at a moment when something has.

Neither is clever. Together they are the entire available response, and the second one is the one almost nobody does.

Why plurality is the mitigation, not the cause

The silence problem would exist with one address and would be worse, because there would be nothing to absorb it. What plurality adds is a buffer: the set can lose a member without the reader losing access, which buys enough time for the reader to notice at a calm moment.

That is the honest description of the arrangement. It does not fix the missing channel. It makes the missing channel survivable.

The thing to accept

You are always slightly behind, and so is every page you read. Accepting that is more useful than any attempt to be current, because attempts to be current are what send readers to sources they would otherwise avoid.

The habit that substitutes for the missing channel

Refresh your copy when nothing is wrong. That is the whole substitute, and it is almost never done, because there is no prompt and no reward. Nothing changes when you do it and nothing appears to be at stake.

The reward arrives later, in the form of a bad moment that was ordinary instead. That is a difficult thing to build a habit around, which is why it is worth stating as plainly as possible: the only maintenance available happens at moments when it feels unnecessary.

What this study is not. It is not a claim about any change to the set, which this site would have no way of detecting.