this post was submitted on 14 Jun 2024
263 points (97.8% liked)
Privacy
31957 readers
320 users here now
A place to discuss privacy and freedom in the digital world.
Privacy has become a very important issue in modern society, with companies and governments constantly abusing their power, more and more people are waking up to the importance of digital privacy.
In this community everyone is welcome to post links and discuss topics related to privacy.
Some Rules
- Posting a link to a website containing tracking isn't great, if contents of the website are behind a paywall maybe copy them into the post
- Don't promote proprietary software
- Try to keep things on topic
- If you have a question, please try searching for previous discussions, maybe it has already been answered
- Reposts are fine, but should have at least a couple of weeks in between so that the post can reach a new audience
- Be nice :)
Related communities
Chat rooms
-
[Matrix/Element]Dead
much thanks to @gary_host_laptop for the logo design :)
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Would sponsorblock be a solution for this?
From what I read, this also breaks sponsorblock - as the ads are part of the video, it moves the time stamps of the video so it makes it not correct. The ads will also change I imagine so idk if sponsorblock will be a solution.
So videos that reference timestamps in their own video won't work? And comments that reference a timestamp won't work?
They could on the fly change them.
Wouldn't that need to be done via some kind of API for cross-platform compatibility? An API which could be exploited to detect ad segments?
No, they would just do that internally in their own code, why would they need an API for that?
So that the timestamp adjustment can be propagated via uploader or user comments across YouTube clients on all platforms... i.e. to avoid having to hardcode each adjustment for each ad on each video on every client
Why couldn't they just serve the comments to each client with the ad-adjusted timestamps already? The only thing the client has to request then is the comment page it wants to load, and some unique ID for which the backend remembers which ad version it's associated with.