Keep the best of a game's different streams, not the first one that verified #95
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#95
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?
What happens
The walk takes the ladder in order (by tier, then by the host's record) and keeps the first link that verifies. The standbys are simply the next links that verify (#64, #74). Nothing compares how the streams actually play. #62 found the same from the resolution side: the first stream that lands is the most reliable host, not the best picture.
Tonight (Ole Miss vs. Georgia, #91) the ladder held 19 links, and every link that verified carried one stream. Whether a second stream existed among the links never read is unknown. The app had no reason to keep looking once one link verified.
The idea
For each followed live game:
To settle in the design: what "clearly better" means (a pace margin, for example 0.05, or the playing stream being Choppy while the other is Steady), and how the score breaks ties with #62's resolution floor.
Done when
Built in PR #99 (merged as
732ab0a), deployed 2026-11-08 04:19Z (container 52cd495f611a); the OpenSpec change is archived in038f7a9. This stays open until it is seen working on a live followed game: a grade before the tune, a Warm background channel, and a Choppy stream that stays put.Live test, UTEP vs. Hawai'i, 2026-11-07 23:22–23:55 ET (first followed game after the deploy). Not seen yet: no trade, because the game was watched the whole time. The second standby (sportsframe.site, a different stream, found 23:27) was not moved ahead of the copy in the first slot before the failure at 23:30 (#101, gap 2).
Closed at the owner's word (2026-11-08): the fix is merged to develop in PR #99 (merge
732ab0a) and deployed. A new issue will be opened if a problem shows up.