A game's standby is usually the same stream as its main link #74

Closed
opened 2026-11-01 02:18:18 -05:00 by cmoriarty · 2 comments
Owner

What happens

Since #68, most of the links at the top of a game's ladder are front ends of one embedcenter.st channel: givemestreams.cfd, s2watch.cyou, resports.cfd, buff-streams.buzz and more. They're different sites, but the stream URL behind them is the same. The standby read takes the next link that verifies, excluding only the player pages already in use (resolution.verify_standby), so it usually lands on another front end of the same channel.

Production's ready games, 2026-10-31 21:35 UTC:

Game Main link Standby Same stream?
Georgia vs. Florida givemestreams.cfd: edgestream6.pro/hls/hfzljfahzcax29.m3u8 s2watch.cyou: the same Yes; they expire 1 min apart
Oklahoma vs. South Carolina s2watch.cyou: edgestream3.pro/…/poertjnvnev40.json resports.cfd: the same Yes; the same playlist, to the second
Indiana vs. Minnesota givemestreams.cfd: edgestream1.pro/hls/qsdnajbq32.m3u8 s2watch.cyou: edgestream7.pro/hls/qsdnajbq32.m3u8 The same stream from another edge server
Hornets vs. 76ers givemestreams.cfd: edgestream3.pro (JSON) topsurge.st: hls.lshls.st No

They fail together:

  • At 20:11, Oklahoma vs. South Carolina's givemestreams.cfd and buff-streams.buzz were both refused in the same minute: "media sequence did not advance".
  • On Chelsea vs. Man Utd (#66), one channel's switch to the disguised player knocked out givemestreams, buff-streams, resports, s2watch and iframely at once.

What it costs

A failure upstream (the channel freezes, goes off the air, changes player or expires) takes the standby down with the main link. A swap or a relapse (#65) then lands on a stream that's already failing, and the recovery falls to the ladder, whose next links are more front ends of the same channel. A copy still helps when only that one URL fails, such as one edge server, so it's better than no standby.

The idea

  1. Know which stream a link is. After a read, a link's stream is its playlist's file name without the token, such as hfzljfahzcax29. The design settles the exact rule.
  2. The standby and the second standby (#64) prefer a different stream from the main link and from each other. A read that finds the same stream is kept as a fallback, and the walk goes on. If no different stream verifies, the fallback is used.
  3. Skip links already known to be the same stream. Per game, a standby read skips links it has seen resolve to the main link's stream, so it doesn't re-read every front end of the channel.

Defaults:

  • The card marks a same-stream standby with a small muted mark, not text, per the front-end preferences.
  • Not part of this: the recovery's own ladder walk. After an expiry, a fresh read of the same stream is the right answer there.
## What happens Since #68, most of the links at the top of a game's ladder are front ends of one embedcenter.st channel: givemestreams.cfd, s2watch.cyou, resports.cfd, buff-streams.buzz and more. They're different sites, but the stream URL behind them is the same. The standby read takes the next link that verifies, excluding only the player pages already in use (`resolution.verify_standby`), so it usually lands on another front end of the same channel. **Production's ready games, 2026-10-31 21:35 UTC:** | Game | Main link | Standby | Same stream? | |---|---|---|---| | Georgia vs. Florida | givemestreams.cfd: `edgestream6.pro/hls/hfzljfahzcax29.m3u8` | s2watch.cyou: the same | Yes; they expire 1 min apart | | Oklahoma vs. South Carolina | s2watch.cyou: `edgestream3.pro/…/poertjnvnev40.json` | resports.cfd: the same | Yes; the same playlist, to the second | | Indiana vs. Minnesota | givemestreams.cfd: `edgestream1.pro/hls/qsdnajbq32.m3u8` | s2watch.cyou: `edgestream7.pro/hls/qsdnajbq32.m3u8` | The same stream from another edge server | | Hornets vs. 76ers | givemestreams.cfd: `edgestream3.pro` (JSON) | topsurge.st: `hls.lshls.st` | No | **They fail together:** - At 20:11, Oklahoma vs. South Carolina's givemestreams.cfd and buff-streams.buzz were both refused in the same minute: "media sequence did not advance". - On Chelsea vs. Man Utd (#66), one channel's switch to the disguised player knocked out givemestreams, buff-streams, resports, s2watch and iframely at once. ## What it costs A failure upstream (the channel freezes, goes off the air, changes player or expires) takes the standby down with the main link. A swap or a relapse (#65) then lands on a stream that's already failing, and the recovery falls to the ladder, whose next links are more front ends of the same channel. A copy still helps when only that one URL fails, such as one edge server, so it's better than no standby. ## The idea 1. **Know which stream a link is.** After a read, a link's stream is its playlist's file name without the token, such as `hfzljfahzcax29`. The design settles the exact rule. 2. **The standby and the second standby (#64) prefer a different stream** from the main link and from each other. A read that finds the same stream is kept as a fallback, and the walk goes on. If no different stream verifies, the fallback is used. 3. **Skip links already known to be the same stream.** Per game, a standby read skips links it has seen resolve to the main link's stream, so it doesn't re-read every front end of the channel. **Defaults:** - **The card marks a same-stream standby** with a small muted mark, not text, per the front-end preferences. - **Not part of this:** the recovery's own ladder walk. After an expiry, a fresh read of the same stream is the right answer there.
Author
Owner

Deployed 2026-11-01 07:49 UTC at develop 2eb6d74 (PR #75); archived in c53ad34. Open until production shows a played or followed game whose standby is a different stream from its main link while copies were on the ladder (a check event with a link refused as "the same stream as the one kept"), or a "same stream" chip when only copies verified.

Deployed 2026-11-01 07:49 UTC at develop 2eb6d74 (PR #75); archived in c53ad34. Open until production shows a played or followed game whose standby is a different stream from its main link while copies were on the ladder (a check event with a link refused as "the same stream as the one kept"), or a "same stream" chip when only copies verified.
Author
Owner

Closed on the tests at the operator's word (2026-11-01): reopen, or file a new ticket, if production shows a problem.

Closed on the tests at the operator's word (2026-11-01): reopen, or file a new ticket, if production shows a problem.
Sign in to join this conversation.
No labels
No milestone
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#74
No description provided.