4 ms·
This is nice and all for now while YouTube allows dismissal of the warning. However, YouTube could go nuclear and just not allow any video to play at all if an
by dylan604 3y ago
This is nice and all for now while YouTube allows dismissal of the warning. However, YouTube could go nuclear and just not allow any video to play at all if an ad blocker is detected. No DOM element removal will solve that. I'm not sure if that qualifies as scorched earth on YT's part, but it is an option.
- wedernoch 3y agoYouTube already does exatly this for me. If uBlock origin is active it loads the base site, but all video tiles are just grey squares and the video titles below are just grey bars.
- nabakin 3y agoScreenshot?
- wedernoch 3y agoNot at home. If I remember I post one tomorrow. It's only on my Desktop. I have zero adds on mobile. Looks like they are trying a few different versions
- remotefonts 3y agoEnable remote fonts loading in uBlock for YouTube and your problem will be solved, I suspect...
- Phelinofist 3y agoI had that a few weeks ago, but that was fixed by a uBlock update (I think)
- kaelinl 3y agoThis, in turn, will spawn user scripts which work around the detection. Any client-side solution will be an arms race between Google and user script/adblock devs. The only real way to prevent it is to withhold the video stream from the CDN until the client has streamed the full ad and/or bake it into the video stream. My impression is that Twitch does this for its live streams (although not VODs).
- serf 3y agoyeah. given that in-stream ads still have blocking/ignoring methods I think that if this arms race keeps going that ultimately the data (video, whatever) is going to be stuffed behind some hard authentication barrier of some sort -- and then traditional piracy methods will take over like single-user-rebroadcast/etc.
- losteric 3y agoI look forward to my browser-based TiVo, buffering videos to ship over ads just like in the 00s... TV started as advertising channels, it's not surprising YouTube converges towards the cesspool of cable TV.
- Aurornis 3y agoThe number of people who will do all the things necessary to play in that arms race gets smaller and smaller with each extra difficulty. In the end, if the only way to block the ads is to have a setup so complicated that only 1 in 10,000 people would be able and willing to maintain it, that’s basically perfect. The people who will spend hours and hours perfecting and maintaining their ad blocking setup were never going to buy premium anyway and they’re negligible drains on resources.
- brucethemoose2 3y agoAnother option is to require Chrome for playback outside of authenticated apps, and lock Chrome down. TBH baking it into the video stream is probably the easiest path. The whole video doesn't have to be re-encoded if the ad is spliced in. This is a "soft lockdown" since the ad can theoretically be manually skipped by the user, but its probably good enough.
- dylan604 3y agobaking into the video stream loses their ability to auction off ads in realtime to customize ads per viewer based on all of the analytics they've hoovered up on that viewer. they aren't doing the hoovering to go back to old school pre-determined ad placement
- hsbauauvhabzb 3y agoBanning google accounts or blocking ips from all google services is the nuclear option.
- zarzavat 3y agoReminder to everyone to back up your Google account, and perhaps have separate accounts for email and regular usage (better yet transition away from gmail).
- LispSporks22 3y ago> and just not allow any video to play at all if an ad blocker is detected They intend to "go nuclear" and do that via their "Web Integrity API" https://arstechnica.com/gadgets/2023/07/googles-web-integrity-api-sounds-like-drm-for-the-web/ https://arstechnica.com/gadgets/2023/07/googles-web-integrit... Also previously discussed a few times here on HN.
- madeofpalk 3y agoThey don't even need that. They can just to server-side ad insertion into the HLS feed.
- OJFord 3y agoThey don't even need that. They can just not play video without a cookie. Fakeable of course, but it's not DOM element removal, it's not how current blockers (have had to) work.