Links that show something else: one Wrong game press clears the lookalikes, and the app stops trading to them #170
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#170
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 owner, 2026-11-14: "it is fairly common for the streams to just be wrong".
That afternoon the app's channel for Indiana vs. USC ran from 15:37 to 19:04 EST. Its log (
GET /api/events):edgestream.pro/omljkhqsdag79edgestream.pro/omljkhqsdag79, through app.my1click.topFrames taken at 16:14 and 16:18 showed Middle Tennessee vs. Liberty on
edgestream.pro/omljkhqsdag79, and USC against Indiana on thetvapp.plus. So the channel played another game for over two hours, reached the right one only because the wrong one lost frames, and thirteen minutes later traded back to the wrong one because it graded better.The research's comparison told the two apart at once: four readings out of four between 16:12 and 16:24 scored 0.02 (a match scores 0.35 to 0.98), while the wrong stream's two sites matched each other at 0.85.
What the app does about a wrong game today, read in the code and not seen live:
Channel.reject,resolution.reject) excludes the link for the game's life, but remembers its stream for the cooldown only (CHANNEL_COOLDOWN_SECONDS, 600 s). The same stream on another site can be kept again ten minutes later.resolution.take_standby), even when it is the stream just rejected on another site. A failed stream's recovery does look (resolution.recovery_pick); the press does not.stream_identity). Two different re-broadcasts of one wrong channel are two streams to the app.After #167 the app knows, for each kept link, whether it shows what the stream playing shows. This ticket acts on that. It needs #167, and does not wait for #168 or #169.
What the app can and cannot know
So the app never rejects a stream, or calls one wrong, because other links outnumber it. Only a Wrong game press says which is wrong.
The idea
recovery_pick).Decided
The owner, 2026-11-14. Asked "Hold a choppy stream when its only standby shows something else?", he chose "Swap as today". So a degrading swap onto a link that reads "No match" is made and marked, and only trades are refused. Holding the stream was the other way, and is not built. What it would have cost: when the unmatched standby was another broadcast of the same game, a useful swap would not have been made by the app.
Data it needs
offset_stateagainst the stream playing._spentholds them for the cooldown.Done when
In the unit lane, with the generated streams of #167: a wrong programme W, a second encode of it W2 (another stream by identity), and the right programme R.
recovery_pickfor copies and slow hosts still pass unchanged.Live: on the next link showing another game, one press of Wrong game lands on the right game, and no trade moves a channel onto a link that reads "No match".
Not in this ticket
Specs:
stream-resolution,stream-supervision,admin-page,event-log.Decided by the owner, 2026-11-14. Asked "Hold a choppy stream when its only standby shows something else?", he answered: "Swap as today".
The ticket's text is changed to match: a degrading swap onto a link that reads "No match" is made as today and marked; only trades to such a link are refused. Holding the stream is not built.
From the live tests of 2026-11-16 (build
ff90c98): "No match" is not "wrong game".So the rule here, "no trade to a link that reads No match", would also refuse right-game links in another language. Suggested change for when this is built: