Notarised and stapled. Also on apt for arm64 and amd64 — apt.vibesdr.net.
A shared VFO told every listener there was no time limit
On a receiver with a shared dial, the countdown never appeared — while the landing banner told the same person "yours for 30 minutes". Two answers to one question, from one server, in the same breath.
A shared VFO has one dial and one pipeline, so there is no per-listener DSP object to read a start time from — and the missing value was being reported as no limit rather than as don't know. Single-user receivers were never affected, which is what made it look like a client problem.
The listener's own socket start time is used instead. It is stamped at the websocket handshake for every socket, so it exists precisely where the per-client object does not.
Also
- The connect explanation is no longer overwritten. Connecting crosses into a band, so the band announcement fired a second later and replaced the notice explaining what the receiver was doing — for the one person it was written for.
- Disconnects say why — closed by peer, send failed, or closed by server — so "is it us or the connection?" can be answered from the log rather than argued about.