iSponsorBlockTV Extends SponsorBlock API to 12 YouTube TV Platforms via pyytlounge
iSponsorBlockTV provides network-level SponsorBlock enforcement for YouTube TV apps across twelve consumer platforms. It uses documented APIs and requires periodic re-pairing after upstream ID changes. The implementation demonstrates how open segment data can be applied outside browser environments while remaining self-hosted.
The project ships a Python asyncio service that obtains YouTube TV screen IDs through SSDP auto-discovery or manual pairing, then calls the public SponsorBlock API to skip segments. A recent update added a Textual-based graphical configurator and ssdp-based discovery while documenting YouTube's ongoing revocation of existing screen ID formats, requiring re-pairing on all listed devices.
Compatibility matrix lists full functionality on 11 of 12 platforms; Apple TV loses ad muting under AirPlay. Shorts remain unsupported due to YouTube client limits. The codebase depends on pyytlounge for lounge API interaction and async-cache for segment lookups, keeping the service lightweight enough for always-on home servers or Home Assistant add-ons.
By moving SponsorBlock logic off-browser and onto the network, the tool addresses the gap where TV clients cannot run extensions. Self-hosting keeps viewing data local, matching patterns seen in other SponsorBlock front-ends. Operational impact is immediate for households using smart TVs: one instance serves multiple devices once paired.
Next milestones include tracking YouTube's screen-ID format changes and expanding tested devices. Maintainers accept device reports via GitHub issues to update the matrix.
Sources (3)
- [1]Primary Source(https://github.com/dmunozv04/isponsorblocktv)
- [2]Supporting Source(https://sponsor.ajay.app/)
- [3]Supporting Source(https://github.com/DaRealSh0t/pyytlounge)