Zerush@lemmy.ml to Privacy@lemmy.ml · 20 days agoYouTube is testing server-side ad injection to counteract ad blockersalternativeto.netexternal-linkmessage-square92fedilinkarrow-up11arrow-down10
arrow-up11arrow-down1external-linkYouTube is testing server-side ad injection to counteract ad blockersalternativeto.netZerush@lemmy.ml to Privacy@lemmy.ml · 20 days agomessage-square92fedilink
minus-squarejayknight@lemmy.mllinkfedilinkEnglisharrow-up0·20 days agoSo videos that reference timestamps in their own video won’t work? And comments that reference a timestamp won’t work?
minus-squareJeena@piefed.jeena.netlinkfedilinkEnglisharrow-up0·20 days agoThey could on the fly change them.
minus-squaregila@lemm.eelinkfedilinkEnglisharrow-up0·20 days agoWouldn’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?
minus-squareJeena@piefed.jeena.netlinkfedilinkEnglisharrow-up0·19 days agoNo, they would just do that internally in their own code, why would they need an API for that?
minus-squaregila@lemm.eelinkfedilinkEnglisharrow-up0·19 days agoSo 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
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