Stream links expire on a timer, and nothing renews them before they do #73

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

What happens

A stream link is a CDN URL with a built-in expiry. The app keeps a verified link until it fails, so every link a game is using fails at its expiry time.

The stamps on production's ready links, 2026-10-31 21:35 UTC:

  • embedcenter's ordinary streams (edgestream*.pro/hls/<id>.m3u8?st=…&e=…): e is 180 min after the link was read. givemestreams.cfd, buff-streams.buzz, s2watch.cyou, ihdstreams.top and the rest of that network serve these.
  • topsurge.st (hls.lshls.st/secure_hls.php?path=…&e=…&sig=…): e is about 30 min after the read.
  • The disguised JSON playlists (#68, edgestream3.pro/sh/access/<token>/…json): no stamp in the URL. The token is in the path, and the page renews it with &grant=1 (#66). Its lifetime is to be measured. One such link still answered 200 at 87 min.

The re-checks in the event log fail right on those marks (2026-10-30 to 2026-10-31):

  • 410 Gone, 180–182 min after the read: 9 times, on givemestreams.cfd, buff-streams.buzz and ihdstreams.top.
  • 403, 31–33 min after the read: 6 times, on topsurge.st and buff-streams.buzz.

What it costs

  • A ready game: little. The 150 s re-check catches the expiry, and the same round re-reads the game. Duke vs. Boston College was ready again 14 s after its link went 410.
  • A watched channel: a stall. The channel's next playlist fetch fails, so it stalls and recovers by re-reading the link (Channel._recover, step 1). This hasn't been traced on a watched channel yet.
  • How often a watched game hits it:
    • every 30 min on topsurge;
    • at least once in any full football game on embedcenter, since a link can be read up to 30 min before kickoff and a game runs about 3.5 h.
  • The standby doesn't help. It's usually the same stream (#74), so it expires within a minute of the main link. Georgia vs. Florida's main link and its standby had 69 and 70 min left.

The idea

Renew a link before its expiry: re-read the same link in the background, verify the fresh URL, and swap it in for the old one. It's the same stream, so a watched channel's next playlist fetch simply uses the new URL, with no swap, filler or re-encode.

Defaults:

  • When: with 5 minutes left on the e stamp. That covers playing channels, their standbys and ready games.
  • Links with no stamp (the JSON playlists): renewed at a lifetime learned from their own failures, or not at all until one is seen.
  • If a renewal fails, the old link plays on until it expires and the recovery takes over as today.
  • Cost: one site read per link per lifetime, about two an hour for a game on topsurge and one per 3 h on embedcenter. Production made 57 site reads in the hour to 21:33.
## What happens A stream link is a CDN URL with a built-in expiry. The app keeps a verified link until it fails, so every link a game is using fails at its expiry time. **The stamps on production's ready links, 2026-10-31 21:35 UTC:** - **embedcenter's ordinary streams** (`edgestream*.pro/hls/<id>.m3u8?st=…&e=…`): `e` is 180 min after the link was read. givemestreams.cfd, buff-streams.buzz, s2watch.cyou, ihdstreams.top and the rest of that network serve these. - **topsurge.st** (`hls.lshls.st/secure_hls.php?path=…&e=…&sig=…`): `e` is about 30 min after the read. - **The disguised JSON playlists** (#68, `edgestream3.pro/sh/access/<token>/…json`): no stamp in the URL. The token is in the path, and the page renews it with `&grant=1` (#66). Its lifetime is to be measured. One such link still answered 200 at 87 min. **The re-checks in the event log fail right on those marks** (2026-10-30 to 2026-10-31): - **410 Gone, 180–182 min after the read:** 9 times, on givemestreams.cfd, buff-streams.buzz and ihdstreams.top. - **403, 31–33 min after the read:** 6 times, on topsurge.st and buff-streams.buzz. ## What it costs - **A ready game: little.** The 150 s re-check catches the expiry, and the same round re-reads the game. Duke vs. Boston College was ready again 14 s after its link went 410. - **A watched channel: a stall.** The channel's next playlist fetch fails, so it stalls and recovers by re-reading the link (`Channel._recover`, step 1). This hasn't been traced on a watched channel yet. - **How often a watched game hits it:** - every 30 min on topsurge; - at least once in any full football game on embedcenter, since a link can be read up to 30 min before kickoff and a game runs about 3.5 h. - **The standby doesn't help.** It's usually the same stream (#74), so it expires within a minute of the main link. Georgia vs. Florida's main link and its standby had 69 and 70 min left. ## The idea Renew a link before its expiry: re-read the same link in the background, verify the fresh URL, and swap it in for the old one. It's the same stream, so a watched channel's next playlist fetch simply uses the new URL, with no swap, filler or re-encode. **Defaults:** - **When:** with 5 minutes left on the `e` stamp. That covers playing channels, their standbys and ready games. - **Links with no stamp** (the JSON playlists): renewed at a lifetime learned from their own failures, or not at all until one is seen. - **If a renewal fails,** the old link plays on until it expires and the recovery takes over as today. - **Cost:** one site read per link per lifetime, about two an hour for a game on topsurge and one per 3 h on embedcenter. Production made 57 site reads in the hour to 21:33.
Author
Owner

Deployed 2026-11-01 07:49 UTC at develop 2eb6d74 (PR #75); archived in c53ad34. Open until production shows it: a re-check event reading "renewed the link on …, N min before it expired", ideally on a watched channel that plays on with no swap. The JSON playlists have no stamp and aren't renewed yet.

Deployed 2026-11-01 07:49 UTC at develop 2eb6d74 (PR #75); archived in c53ad34. Open until production shows it: a re-check event reading "renewed the link on …, N min before it expired", ideally on a watched channel that plays on with no swap. The JSON playlists have no stamp and aren't renewed yet.
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#73
No description provided.