SponsorBlock (and DeArrow): "YouTube is currently experimenting with server-si…" - Fosstodon
SponsorBlock (and DeArrow): "YouTube is currently experimenting with server-si…" - Fosstodon
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 wit...
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're viewing a single thread.
Also, if the ads where in different parts of the video every time, it would not be possible to use SponsorBlock for them :(
How does a client know when to block the user from fast forwarding to prevent them from skipping over the ad? Could something like sponsorblock detect that to know where the ads are placed?
SB would need to adapt to detecting the ads being shown instead of relying on timestamps. This should be possible in theory, since when ads are displayed there will be some ways that the client is informed that SB could pick up on.