Re:PipePipe: NewPipe hard fork implementing SponsorBlock
by Dylan16807 on Sunday September 27, 2026 @12:29AM
(#49863364)
SDR 1080p AV1 can handle 90% of YouTube views.
Re:PipePipe: NewPipe hard fork implementing SponsorBlock
by nijave on Sunday September 27, 2026 @12:46PM
(#49868372)
I'd be interested in seeing data that supports this.
Netflix reported in 2025 something like 30% of traffic was av1. I think smartphone and PC support are fairly robust but under the impression streaming devices are still quite terrible unless it's a Chromecast.
AVC/h.264 is the only thing I know of that's pretty much universally supported at this point. I found a Facebook/Meta report citing some consultant provided data that VP9 was a close second. Limiting to devices from the last few years, HEVC might work.
Re:PipePipe: NewPipe hard fork implementing SponsorBlock
by Dylan16807 on Sunday September 27, 2026 @07:30PM
(#49871870)
Okay I wasn't considering streaming devices. Those are going to have trouble participating in P2P at all but maybe they need something else.
Re:PipePipe: NewPipe hard fork implementing SponsorBlock
by darkwater on Sunday September 27, 2026 @03:14AM
(#49864157)
You are correct, but in this scenario reducing the number of available qualities to cover the most reasonable use cases would be the right tradeoff.
Re:PipePipe: NewPipe hard fork implementing SponsorBlock
by nijave on Sunday September 27, 2026 @12:49PM
(#49868393)
Why is that the right tradeoff? It seems like the Plex/Jellyfin ecosystem has landed on keeping high quality persisted and hardware accelerated transcoding for everything else. Put another way, transcoding capable caches.
The client can pick the optimal encoding and quality which makes that quite a bit more difficult. A user on a modern device that can hardware decode HDR av1 will have a file cached completely useless to a browser that can only do SDR h264.
I think there is a sort of network effect needed to make it become reasonable.