Settings for background channels: on/off, how many, and which teams #100
Labels
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set
Reference
cmoriarty/sports-breaker#100
Loading…
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-up to #96. Background channels went live on 2026-11-08 with UTEP vs. Hawai'i: the channel was warm before the tune, and the tune came up quickly.
Why
Each background channel plays its stream with nobody watching, so it costs the stream's full bitrate (about 3 Mbit/s each, about 15 Mbit/s at the limit of 5). The only control today is
CHANNEL_BACKGROUND_LIMITin stack 131's environment. Changing it means editing the stack and redeploying, which is too slow when bandwidth is needed for something else right now.What
Settings in the app, applied at the next background round (15 s):
CHANNEL_BACKGROUND_LIMIT(the env var stays as the starting value).Possibly also
WATCH_LINKS_LIMIT(the watch's polling), which is much cheaper (about 25–50 KB/s per link).Notes
watchlist.jsonin the data folder so it survives restarts.Deployed 2026-11-08 08:48Z as 1.2.0: PR #113 (merge
654a9a7), released throughrelease/1.2.0(tagv1.2.0), container b0f1f361509d. The OpenSpec changesettings-and-recoveriesis archived ind013eb4.Live now:
settings.jsonbesidewatchlist.json, so they survive restarts.CHANNEL_BACKGROUND_LIMITis only the starting value now.Decisions I took on the open questions (yours to reverse):
WATCH_LINKS_LIMITstays an env var. The watch costs about 25–50 KB/s a link, and a switch for it didn't seem worth the space.Left open until it has been used on a game night.
Closing: the fix is merged to develop in PR #113 (
654a9a7) and deployed as 1.2.0.Seen live on 2026-11-08: the top bar's flame showed 1/5 at 1.3 Mbit/s for the Liverpool game, then 2/5 at 2.8 Mbit/s, and a watched channel left the count as designed.
Not seen yet: switching off, changing the count, or a kept-warm team on a game night. A new issue if any of them misbehaves.
The controls move into the settings gear's pane in #117.