- Shipped
- September 6, 2026 at 6:25 AM UTC
- Author
- Kamo
- Commit
- da28f2c
Feeds the two meters the Linux Desktop menu now draws — how much of a member's A sweep rather than a push, because the numbers are born on the machine and statusLine command, so a status line records them and the agent reads the recording; the agent has no NATS client and no credential for this service, and giving it one would open an inbound trust direction the design deliberately does not have. So this asks — once per tick for the WHOLE machine, which keeps the request count off the size of the fleet. It publishes only when a number actually moves. A window moves when a session spends it: a handful of times a minute while somebody is working, and never while nobody is. That is what makes a ten-second sweep feel live — the sweep is how fast we notice, not how fast the browser is told — and it is why the subject is silent by construction rather than by throttling. Per member because a colleague's remaining allowance says what hours they have been working and how hard. MediaService relays it to against the subscriber's own id. its first frame — core NATS keeps no history, so a console that only subscribed would show nothing until the member next spent something. It takes no member id: the Linux account comes from the caller's own session, which is the only reason a per-member number is safe to serve at all. The sweep never throws. An unreachable dev machine is an expected state, not a fault — it means the meters hold their last value, which is what they should do — and an exception escaping a @Scheduled method would log a stack trace per tick for as long as the machine stayed off.