SponsorBlock (and DeArrow) (@sponsorblock@fosstodon.org)
fosstodon.org
YouTube is currently experimenting with server-side ad injection. This means that the ad is being added directly into the video stream. This breaks sponsorblock since now all timestamps are offset by the ad times. For now, I set up the server to detect when someone is submitting from a browser with this happening and rejecting the submission to prevent the database from getting filled with incorrect submissions.

cross-posted from: https://lazysoci.al/post/14579120

YouTube is currently experimenting with server-side ad injection. This means that the ad is being added directly into the video stream.

This breaks sponsorblock since now all timestamps are offset by the ad times.

For now, I set up the server to detect when someone is submitting from a browser with this happening and rejecting the submission to prevent the database from getting filled with incorrect submissions.

  • Kissaki@beehaw.orgEnglish
    10·
    6 months ago

    Right now it’s entirely timestamp-based. That means it can interface and work on simple playback terms. On time, jump, jump to time, etc. Having to get frame data and hash it, and make playback depend on it adds a lot of technical complexity.

    If ad length varies you don’t even know how far to jump ahead. And if you haven’t prebuffered the data until after the ad, you can’t find out from a hashed after-frame-hash-value either.