Russell Ballestrini
f45b22054e
The mod-action serializer (runModSerial) was waiting for case 'state' to release the next sign — but no 'state' broadcast follows a successful kick/ban/promote. The server bumps rm.epoch and emits the action-specific event (peer-booted / role-change) carrying the new epoch. The client was already updating roomEpoch in role-change but never released the queue gate, and the peer-booted handler did neither — so kick/ban always burned the 1500ms fallback timeout AND signed the next action with the stale epoch (signal bounces it with "stale epoch"). Fox 2026-06-04: "couldn't kick until leaving as host" — leaving + welcome was the only thing that refreshed roomEpoch. Pair with signal-side fix that moves rm.epoch++ before the peer-booted broadcast and includes "epoch" in the payload. |
||
|---|---|---|
| .. | ||
| blog | ||
| fonts | ||
| chat.html | ||
| host-your-own.html | ||
| how-it-works.html | ||
| index.html | ||
| kernel.html | ||
| stamp.js | ||
| zebra-audio.html | ||
| zebra-spaces.html | ||