mux web narrates reconnects only to the browser #14

New issue

Open

opened 2026-08-13 15:27:14 +00:00 by a73x · 1 comment

a73x commented

2026-08-13 15:27:14 +00:00

(Migrated from git.a73x.sh)

From the M17 simplify round + collect.sh. The hub's control messages (connecting/up/reconnecting/gone) are written to the WebSocket and nowhere else — a tile that flapped all night leaves no trace on the hub side, and collect.sh's hub section can only report /tiles, not history. One stderr line per tile state TRANSITION (with the timestamp from the sibling issue) makes the hub's log the wall's flight recorder. Cheap: the write sites are the two controlMessage callers in the pump and dialLoop.

Migrated from git-collab issue 6aba30a0b78c09fe9d35cf75455a54e8a5135511.

Original author: a73x dev@a73x.sh.

a73x commented

2026-08-29 12:29:45 +00:00

(Migrated from git.a73x.sh)

2026-08-29: half done. The hub now prints 'mux web: tile N: SPELLING#NAME' and 'tile N: gone' to stderr (webhub.zig applyList). 'reconnecting' is still WS-only (controlMessage(.reconnecting), webhub.zig ~661).