| What carries on while your machine is off | What that means for you |
|---|---|
| An outside network keeps adding to its own record. | Agreement accumulates whether or not anything of yours is open. See a deposit reaching enough confirmations. |
| A vendor reaches their messages when they reach them. | Nothing done at the keyboard moves your message up somebody else's list. See a vendor reading your message. |
| Maintenance runs through to its own end. | The service is not waiting to be reloaded before it will finish. See maintenance finishing. |
| Your own patience recovers. | The only item on this list that improves specifically because you left. See the pause you add yourself. |
A wait that does not need you present
This band is defined by an absence. In everything filed here, the thing that has to happen is not happening on your machine, has no knowledge that your machine exists, and will proceed at exactly the same rate with the tab open or closed. That is not a description of how long it takes. It is a description of where the work is, and the length follows from it.
Two mechanisms produce that arrangement. The first is repetition by an outside network. A single agreement is a short affair, but a wait that requires many of them in sequence inherits the pace of the slowest, and no part of that sequence is yours to hurry. The second is human attention. A person reads their messages in an order they chose, inside a day that has other things in it, in a timezone nobody told you about.
A third arrangement belongs here too, and it is the one people trip over, because it is the service itself being unavailable on purpose rather than anything to do with you. Work of that kind runs to a plan somebody else wrote, finishes when the plan says, and shows nothing useful in the meantime. It sits in this band for the same reason the other two do: the end of it is set somewhere you have no access to.
What follows from both is the same, and it is the point of the band. The screen is the worst possible place to spend the wait, because the screen has nothing to show. Progress here is not incremental in any way you can watch. It is a state that has not changed, and then it is a state that has, and there is no visible slope between the two.
Staying at the screen for something that will not resolve at the screen
The mistake here is not the retry. It is the vigil. A page left open, reloaded at intervals, watched for a state to flip in front of you, on the theory that being present when it happens is worth something. It is not worth anything, and it costs three things.
It also has a shape that makes it hard to stop. Every reload confirms the thing is still running, which feels like information, and the feeling of gathering information is what keeps somebody in the chair. But the same result would have been produced by not looking, and it would have cost nothing. The only thing the vigil has actually established is that no time has passed, which you could have worked out from the clock.
The first cost is judgement. A long stretch of watching nothing makes small oddities look enormous. People talk themselves into believing an address was wrong, or an account has been touched, or a message was never sent, and none of those were true when the evening started. The second cost is the damage from the band below, which arrives eventually, because somebody who has watched a still screen for long enough will begin pressing things, and the things worth pressing all ran out a while ago. The third cost is the plain one. An evening spent in front of a screen that could not have told you anything is an evening spent badly, and it buys nothing back.
So the instruction that fits this band is an unusual one for a website to give. Close it. Come back later the same day, once, and look. If the state has not moved by then, the card for your particular wait will say whether that is ordinary for its mechanism or whether the thing has quietly turned into a wait that takes days, which is a different situation and wants a different response.
The waits that run without you
Read the card for the one you are in, then go and do something else. Every card on this page names what is proceeding without you, what would delay it further, and what is safe to do in the meantime. The last of those is usually the shortest section on the card, and that is not an accident. In this band the honest list of useful actions is short.
An evening · Wait 17
Acknowledged early, credited late. The gap between those two events is the whole wait.
Waiting for the payment to sit deep enough in the chain for the market to treat it as final
An evening · Wait 18
A message is a queue entry, not a doorbell. Somebody has to sit down before it is answered.
Waiting for a person on the far side to open their inbox and work down to what you sent
An evening · Wait 19
One of the strings stops opening. From your side, every possible cause looks the same.
Waiting for a string that has gone quiet to answer again, without knowing which layer stopped it
An evening · Wait 20
You finished the checkout. Somebody still has to look at the order and agree to it.
Waiting for a vendor to open the order, decide they can fill it, and mark it accepted
An evening · Wait 21
The gate keeps refusing you. Trying harder is the one move that reliably fails.
Waiting for a gate to stop refusing you, which usually means elapsed time rather than a better answer
An evening · Wait 22
Planned work leaves notes. It is also the only wait here with a stated end you still should not trust.
Waiting for planned work to end, on a schedule set by people who are not talking to you
An evening · Wait 23
The one wait here that you choose. It costs nothing and it is worth more than the rest put together.
Waiting for nothing on the far side. This is the only wait where the thing that changes is you
Which side of the evening a wait falls on
This band sits between waits that finish while you sit there and waits you should not look at again until tomorrow. Two questions do most of the separating, and a third case sits inside the band rather than on either edge of it.
- Downward, towards <a href="/minutes">minutes</a>
- Ask whether anything at the keyboard could still change the outcome. If some action of yours is still part of the mechanism, the wait has not left the keyboard yet and the card is a band lower.
- Upward, towards <a href="/days">days</a>
- Ask whether coming back after supper is a sensible test. When the thing you are waiting on runs on working days, or on a queue worked through by people during their own hours, no evening is long enough and the card sits a band higher.
- The one that is yours to set
- The pause you add yourself is the only wait on the site with no external mechanism at all. It is filed here because an evening is the length at which a deliberate pause starts doing what it is for.