Measuring: a source slower than about 0.67x is still taken for a new stream every 90 s (shd247.world) #190
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#190
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
On 2026-11-17, on build
849c2f8with #179's fix, shd247.world's links on the European friendlies listed media far slower than real time, stalling and bursting. Their playlists were on edge1 and edge2.candyshop.st. The watch read these paces:The app kept taking these links for new streams:
offsets: in 300 s, …: N clock restarts) counted 28 clock restarts on four shd247 links. That is about one every 90 s per link.On 2026-11-16 the same site ran at a steady 0.90×, which #179 (PR #184) fixed. Tonight's slower, burstier listing is outside what that fix covers.
Why
offsets._listedcompares each reading with the clock carried forward by the link's drift (_freshest). A jump of more than 30 s (RESTART_SECONDS) is taken for a new stream: the readings are cleared and the pairs dropped.DRIFT_MIN_READINGS,DRIFT_MIN_SECONDS).HEARD_SECONDS). At 0.5× that point comes after about five minutes. So the gain is in the first minutes of such a link, and in far fewer drops, comparisons and log lines.Done when