Skip to content

Instantly share code, notes, and snippets.

@ajayyy

ajayyy/FAQ.md Secret

Last active June 21, 2024 20:05
Show Gist options
  • Save ajayyy/f7b1807e13731c25cef4c2c057d022bc to your computer and use it in GitHub Desktop.
Save ajayyy/f7b1807e13731c25cef4c2c057d022bc to your computer and use it in GitHub Desktop.
YouTube server-side ad injection faq

Does this mean YouTube is live re-encoding content?

No, this is not needed. Online video streaming nowadays uses a "playlist" of video chunks. These chunks are seperately encoded videos, so can easily be swapped out, or concatted to. This also means that an ad-blocker could ignore specific chunks if they know which ones to ignore.

Is this the end of SponsorBlock?

No, if YouTube displays any UI such as a clickable link, that means it has to know how long the ad is. SponsorBlock could find this data as well. There is also the feature for clicking on a timestamp in a comment that would need to know the duration of the ad, so it should be findable somewhere, it just might be kind of hard.

In the short term, SponsorBlock will not work for people with this experiment.

Will this be the end of general adblockers?

Probably not. But it makes things harder. As always, uBlock Origin work best on Firefox-based browsers, especially now that we reach the end of manifest v2.

Will this affect yt-dlp, NewPipe, etc.

Maybe in the future, but at the moment it seems to only switch to this server-side ad injection via client-side flags.

The more pressing issue for these clients is the new sign in requirement to watch videos for some people.

Will this affect DeArrow

The offsetting issue will affect DeArrow thumbnail submissions, but should be fixable in the same way as SponsorBlock.

@nukeop
Copy link

nukeop commented Jun 21, 2024

Never pay Google a cent!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment