Cases the market caused

The market collects far more blame than it earns. This section is the part it earns.

Six cases. Each one is something the operator decided, configured or failed to communicate, and in each one the fault is theirs regardless of how reasonable their reasons were.

The six

• The address set changed and nobody told you a deliberate rotation
• A rule changed under an order already running an operator setting
• The chain finished and the market had not looked yet their polling, their schedule
• The listing vanished and the vendor got the blame a moderation decision
• The wall in front of the door is theirs installed on purpose
• Everything stopped at once and nobody is saying anything the one that matters

What an operator actually controls

It is a short and specific list, and knowing it saves a great deal of misdirected argument.

• Which onion addresses exist and which ones stop being used.
• Every rule in the place, including whether a change applies to orders already running.
• How deposits are watched for and when a balance moves.
• Which listings and accounts stay visible.
• Whatever gate sits between an incoming visitor and the market itself.
• Whether anything is announced, and where.

Notice what is absent. Nothing about routing, nothing about how long a page takes to arrive, nothing about whether your particular connection works. Those belong to the network section and they are the source of most of the blame that lands here by mistake.

The communication problem

Four of the six cases here are not really failures of infrastructure at all. They are failures to say anything. An address rotates and nobody is told. A rule changes without notice. A listing goes and no reason is given. A balance sits uncredited with no indication of when the check runs.

In each of those the underlying action is defensible and the silence is what causes the damage. That is a real fault and it belongs here, even though it will never be acknowledged and cannot be appealed.

The one that is different

Five of these are annoyances with a route through them. The sixth is not, and it is the reason people keep as little as possible on any market for as long as possible. It is covered on its own page, carefully, because it is also the case where confident public claims arrive fastest and are worth least.

This site will never tell you that case is happening or that it is not. It monitors nothing and it would not be able to tell.

Being fair to an operator you cannot see

Nothing here is written to be generous. It is written to be accurate, and accuracy happens to clear the operator of a lot of things.

Running an onion service under constant flooding, with no upstream to lean on and no way to recover a key that goes wrong, is difficult in ways that are invisible from a browser. A rotation is usually competence rather than trouble. A gate at the door is protection rather than obstruction. A batch job that credits deposits is a normal way to build software.

The complaints that survive that reading are the ones on this page, and they mostly come down to not telling anybody anything. That is a fair criticism and it stands.

• The published address list
• Every case in one table
• How cases get assigned