Repository navigation
v3.10.1
A housekeeping release: now that rooms outlive the command that created them, this bounds what one can cost the server.
🧹 Rooms can't grow without limit. A room's history was capped by message count, but a message is a batch of up to ~70KB, so a chatty session could hold ~14MB — and the terminal-size message, stored for the room's whole life, wasn't counted at all (one oversized size frame measured at 8.5MB of memory per room). History now has a byte budget, control messages are capped, and so is a single frame. Nothing changes for you: the budget is sized so a late joiner still gets the full-screen redraw that lets them reconstruct a running TUI.
⏱️ A finished broadcast always expires. A room with a broadcaster attached was exempt from cleanup, so if a connection ever ended without being accounted for, that room stayed forever — and viewers kept seeing it as live. An attached broadcast now gets a minimum lifetime rather than an exemption, and a quiet-but-live one is still never dropped early.
Self-hosting? These are server-side limits, so upgrade the server to get them; shellshare CLI binaries are unaffected and need no update.
What's Changed
- Bound what a room can cost now that rooms outlive their broadcaster by @vitorbaptista in #172
Full Changelog: v3.10.0...v3.10.1