Technology

37730 readers

194 users here now

A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.

Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.

Subcommunities on Beehaw:

This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.

founded 2 years ago

MODERATORS

[email protected]

108

SponsorBlock (and DeArrow): "YouTube is currently experimenting with server-si…" - Fosstodon (fosstodon.org)

submitted 5 months ago by [email protected] to c/[email protected]

31 comments fedilink hide all child comments

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.

you are viewing a single comment's thread
view the rest of the comments

[–] [email protected] 10 points 5 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.