Links that show something else: one Wrong game press clears the lookalikes, and the app stops trading to them #170

Open
opened 2026-11-14 19:37:10 -05:00 by cmoriarty · 2 comments
Owner

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):

Time (EST) What the app did
15:37:27 Tuned; playing s2watch.cyou, stream edgestream.pro/omljkhqsdag79
17:50:15 That stream lost frames; swapped to the standby on thetvapp.plus
18:03:47 "nobody watching; moved from thetvapp.plus to the better stream": back onto edgestream.pro/omljkhqsdag79, through app.my1click.top
18:10:38 That stream's playlist answered 403; recovered on thetvapp.plus

Frames 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:

  • Nothing by itself. A stream showing another game verifies, plays and reads Healthy. A trade weighs how well a stream plays, not what it shows.
  • A Wrong game press (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.
  • The press takes the first standby without looking (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.
  • Only the very same stream is recognised (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

  • It can know same or different: a kept link matches the stream playing, or never does.
  • It cannot know which one is wrong. A link that never matches shows another game, or another broadcast of this one (another commentary). When two links differ, either may be the wrong one.
  • Counting votes is not safe. When a site's list points a game at the wrong channel, several sites carry that channel, and they agree with each other. On 2026-11-14 two of the three kept links carried the wrong game (one stream, on two sites).

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

  1. A Wrong game press takes the lookalikes with it.
    • Every kept link that showed the same thing as the rejected stream goes with it: the same stream on another site, and any link with a trusted match by sound (#167).
    • The stream stays rejected for the game's life, not for ten minutes.
    • The channel then goes to a link that did not match the rejected stream, when there is one. That link shows something else, which is what the press asked for.
    • The way back (#79) restores everything the press rejected.
  2. The app does not trade to a link that shows something else.
    • No trade to a link that reads "No match". This alone would have stopped the 18:03 move above.
    • A degrading swap is still made, as today, when the only ready standby reads "No match" (the owner's pick, below). Its record and the game page say the link taken was not matched to the one left.
    • A stream that has failed: as today too. With nothing else ready the recovery takes the unmatched link, and its record says so.
  3. Among ready standbys, a matched one goes first. Matched, then not yet compared, then "No match". A matched standby shows what is being watched, and its swap can be aimed (#168). This comes after the rules already there for copies and slow hosts (recovery_pick).
  4. Say when kept links differ. A labelled field on the game page ("Other links: 1 of 2 shows something else") and a tag on the game's row in the Overview. Plain words, not a Problem: the app does not know which is wrong.

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

  • From #167: each kept link's offset_state against the stream playing.
  • The game's rejected streams, by identity, kept for the game's life. Today _spent holds them for the cooldown.
  • On the Wrong game event: the links rejected with it and why each ("same stream", "matched by sound"), and whether the link taken next had read "No match".
  • On a refused trade, and on a swap or recovery onto a link that was not matched: a log line and an Admin line that say so.

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.

  • One press: playing W with standbys "W on another site" and R, Wrong game is pressed once. Both W links are rejected, the channel is on R, and the event names both.
  • By sound: the same with W2 as a standby after a trusted match. W2 is rejected with W.
  • For the game's life: eleven minutes after the press, a new link carrying W is read. It is not kept.
  • The way back restores every link the press rejected.
  • No trade: playing R with a better-graded W as standby reading "No match", nobody watching. No trade is made, and the log says why.
  • Degrading: playing R, degrading, with only W ready. The channel swaps to W as today, and the event and the game page say the link taken was not matched to the one left.
  • Failed: playing R, failed, with only W ready. The recovery takes W, and its record says it was not matched.
  • Order: with a matched and an unmatched standby both ready, a swap and a recovery take the matched one. One not yet compared ranks between them.
  • The field and the tag appear after about five minutes of samples with no match, and go when the link matches or leaves.
  • Nothing is rejected, and no stream is left, on a count of links.
  • The tests of recovery_pick for 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

  • Telling which link is the right game without the owner. One way: read the score and clock off the picture and compare them with the scoreboard feed the app already has. Not researched.
  • Another commentary. Whether crowd sound alone can match two broadcasts of one game. Not researched; until then such a pair reads "No match" and is treated as above.
  • Comparing two standbys with each other. They are compared with the stream playing only.

Specs: stream-resolution, stream-supervision, admin-page, event-log.

## 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`): | Time (EST) | What the app did | | --- | --- | | 15:37:27 | Tuned; playing s2watch.cyou, stream `edgestream.pro/omljkhqsdag79` | | 17:50:15 | That stream lost frames; swapped to the standby on thetvapp.plus | | 18:03:47 | "nobody watching; moved from thetvapp.plus to the better stream": back onto `edgestream.pro/omljkhqsdag79`, through app.my1click.top | | 18:10:38 | That stream's playlist answered 403; recovered on thetvapp.plus | Frames 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: - **Nothing by itself.** A stream showing another game verifies, plays and reads Healthy. A trade weighs how well a stream plays, not what it shows. - **A Wrong game press** (`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. - **The press takes the first standby without looking** (`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. - **Only the very same stream is recognised** (`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 - **It can know same or different:** a kept link matches the stream playing, or never does. - **It cannot know which one is wrong.** A link that never matches shows another game, or another broadcast of this one (another commentary). When two links differ, either may be the wrong one. - **Counting votes is not safe.** When a site's list points a game at the wrong channel, several sites carry that channel, and they agree with each other. On 2026-11-14 two of the three kept links carried the wrong game (one stream, on two sites). 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 1. **A Wrong game press takes the lookalikes with it.** - Every kept link that showed the same thing as the rejected stream goes with it: the same stream on another site, and any link with a trusted match by sound (#167). - The stream stays rejected for the game's life, not for ten minutes. - The channel then goes to a link that did *not* match the rejected stream, when there is one. That link shows something else, which is what the press asked for. - The way back (#79) restores everything the press rejected. 2. **The app does not trade to a link that shows something else.** - No trade to a link that reads "No match". This alone would have stopped the 18:03 move above. - A degrading swap is still made, as today, when the only ready standby reads "No match" (the owner's pick, below). Its record and the game page say the link taken was not matched to the one left. - A stream that has failed: as today too. With nothing else ready the recovery takes the unmatched link, and its record says so. 3. **Among ready standbys, a matched one goes first.** Matched, then not yet compared, then "No match". A matched standby shows what is being watched, and its swap can be aimed (#168). This comes after the rules already there for copies and slow hosts (`recovery_pick`). 4. **Say when kept links differ.** A labelled field on the game page ("Other links: 1 of 2 shows something else") and a tag on the game's row in the Overview. Plain words, not a Problem: the app does not know which is wrong. ## 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 - From #167: each kept link's `offset_state` against the stream playing. - The game's rejected streams, by identity, kept for the game's life. Today `_spent` holds them for the cooldown. - On the Wrong game event: the links rejected with it and why each ("same stream", "matched by sound"), and whether the link taken next had read "No match". - On a refused trade, and on a swap or recovery onto a link that was not matched: a log line and an Admin line that say so. ## 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. - **One press:** playing W with standbys "W on another site" and R, Wrong game is pressed once. Both W links are rejected, the channel is on R, and the event names both. - **By sound:** the same with W2 as a standby after a trusted match. W2 is rejected with W. - **For the game's life:** eleven minutes after the press, a new link carrying W is read. It is not kept. - **The way back** restores every link the press rejected. - **No trade:** playing R with a better-graded W as standby reading "No match", nobody watching. No trade is made, and the log says why. - **Degrading:** playing R, degrading, with only W ready. The channel swaps to W as today, and the event and the game page say the link taken was not matched to the one left. - **Failed:** playing R, failed, with only W ready. The recovery takes W, and its record says it was not matched. - **Order:** with a matched and an unmatched standby both ready, a swap and a recovery take the matched one. One not yet compared ranks between them. - **The field and the tag** appear after about five minutes of samples with no match, and go when the link matches or leaves. - **Nothing is rejected, and no stream is left, on a count of links.** - The tests of `recovery_pick` for 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 - **Telling which link is the right game without the owner.** One way: read the score and clock off the picture and compare them with the scoreboard feed the app already has. Not researched. - **Another commentary.** Whether crowd sound alone can match two broadcasts of one game. Not researched; until then such a pair reads "No match" and is treated as above. - **Comparing two standbys with each other.** They are compared with the stream playing only. Specs: `stream-resolution`, `stream-supervision`, `admin-page`, `event-log`.
Author
Owner

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.

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.
Author
Owner

From the live tests of 2026-11-16 (build ff90c98): "No match" is not "wrong game".

  • Greece vs. Serbia's powerstream.club link carried Greece's Nova Sports, with Greek commentary. Against FS2's English commentary, 0 of 7 comparisons matched, so it read "No match". It showed the right game.
  • The background trade moved onto it while nobody watched, recorded as "not aimed: no match".
  • Germany's ARD and FS1 matched in only 2 comparisons of 7.

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:

  • A trade avoids a "No match" link only when another candidate did match.
  • A link is "another game" only by a Wrong game press, as the ticket already says for rejecting.
From the live tests of 2026-11-16 (build ff90c98): "No match" is not "wrong game". - Greece vs. Serbia's powerstream.club link carried Greece's Nova Sports, with Greek commentary. Against FS2's English commentary, 0 of 7 comparisons matched, so it read "No match". It showed the right game. - The background trade moved onto it while nobody watched, recorded as "not aimed: no match". - Germany's ARD and FS1 matched in only 2 comparisons of 7. 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: - A trade avoids a "No match" link only when another candidate did match. - A link is "another game" only by a Wrong game press, as the ticket already says for rejecting.
Sign in to join this conversation.
No labels
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
cmoriarty/sports-breaker#170
No description provided.