About Timer
A timer, or a deadline
Timer counts down a length you choose: five minutes, an hour and a half, ninety seconds. Press Start and it works out when that lands, then counts towards it.
Until counts down to a moment: midnight, a release date, the expiry on a token. Type it, pick it from the calendar button, or wire one in from anywhere that produces a timestamp. The box takes a unix timestamp or an ISO string as readily as a date, so anything you can paste out of a log will do.
They are the same calculation underneath, which is why they are one block. Starting a timer is just working out its finish line — and it fills the Until box in with that finish line, so you can switch between the two views of a running timer without losing it: how long is left, and the wall-clock moment it lands on. While it runs the deadline is locked, the way the length boxes are, and Stop is there in both views; a run holds at zero whichever way you are reading it.
Only a length needs starting. A moment is already absolute, so Until counts towards whatever it is given the instant it has it — nothing to press, which is also the only way a deadline arriving down a wire could work.
Setting a length
Three boxes — hours, minutes, seconds — and a row of common lengths underneath: 30s, 1m, 5m, 10m, 30m, 1h. Pressing one fills the boxes, so you can adjust it before pressing Start. While a timer is running its length is fixed; stop it to change it.
The length itself is stored the way you would say it — 5m, 1h 30m — so a bode you edit by hand or open as JSON reads plainly. It will also accept 90, 5:30 or PT1H30M if it finds them, and a bare number means seconds.
What happens at zero
It keeps going, and says how long ago. A countdown that froze on zero could not answer the question people actually ask of an expiry — not "has it passed" but "how long ago". The seconds output goes negative at the same moment, so a block downstream can tell.
Nothing rings. A sound that played while you were reading something else, in a tab you had forgotten, is not a feature.
Common questions
- Does a running timer survive a refresh?
- No, deliberately. A timer you started is something happening here and now, so it is held for the session only — the length you configured is saved, the run is not. The same rule means a bode you share does not arrive holding your stopwatch, already expired.
- Can it count down to a token expiry?
- Yes. The JWT block emits its expiry as a timestamp, so wiring that in gives you a live countdown to it. The same works for the timestamp inside a ULID or anything the Time block produces.
- Why is there no pause?
- Start and Stop only, for now. Pausing means keeping a second piece of state — how much was left when you paused — and the block reads better without it. Wire it to a Display and you have a clock; that is most of what a pause was for.
- Does it run in the background?
- It counts while the page is open. Browsers slow timers in hidden tabs, so the reading catches up rather than drifting: the target is a fixed moment and the block subtracts from it, rather than counting ticks.