YouTube's Adblock detection might break the law in the EU

Original Article ↗ Hacker News Discussion ↗

YouTube’s escalating efforts to detect and block ad blockers are raising questions about their legality under EU privacy rules, particularly around whether such detection constitutes tracking that requires user consent. Commenters dissect how YouTube may be technically identifying ad blockers and describe a fast-moving cat‑and‑mouse game with tools like uBlock Origin, while noting different experiences from “toothless” warnings to full blocking. The exchange broadens into a critique of invasive advertising, consent fatigue from mechanisms like cookie banners, and whether regulators should more aggressively protect users’ ability to control what runs in their browsers.

How YouTube Detects Adblockers (Technical Discussion)

  • Several comments speculate detection is based on missing network requests or JS not executing.
  • Others mention that in the past, ad metadata in JSON responses was modified by blockers (e.g., turning an ads array empty), and YouTube may now validate that via additional requests or fake responses.
  • uBlock Origin is reported to rely on regexes over XHR bodies; YouTube is said to be changing scripts and identifiers multiple times per day to break these filters.
  • Some propose server-side timing checks (skipping ad segments) but others think this is not what YouTube is currently doing, given existing workarounds (uBO, Newpipe, embedding).
  • There’s recognition that Google benefits from a prolonged cat‑and‑mouse game that exhausts volunteer blocker maintainers.

EU Law, Tracking, and Consent

  • One EU memo excerpt says sites may check if a device can receive content including ads, without consent, and then “respond appropriately” (e.g., asking users to disable adblockers).
  • A separate, older EU communication referenced in the video appears more restrictive, leading to claims of internal inconsistency that may require courts or regulators to resolve.
  • Some argue adblock detection alone involves no tracking: user requests JS, runs or doesn’t run it, and the site can refuse service.
  • Others counter that if detection contributes to a profile (e.g., “uses adblocker” tied to IP and other attributes), it becomes personal data processing requiring consent unless strictly necessary.
  • Debate over whether terms of service can legitimately require users not to mute/alter ads.

JavaScript, Cookie Banners, and Browser Controls

  • Some want explicit consent for running JS, similar to camera/mic permissions; others fear this would just reproduce cookie‑banner annoyance.
  • Several see cookie banners as malicious compliance: companies could simply avoid unnecessary tracking but instead dark‑pattern users into accepting.
  • There is disagreement over whether GDPR is a net positive: some praise its protections; others blame the EU for not anticipating how bad actors would game the consent rules.

User Experiences and Workarounds

  • Reports vary: some are fully blocked after a few videos; others see dismissible popups; some never hit the block after updating filters.
  • Clearing cookies/local storage and updating uBlock filters is repeatedly suggested as a temporary fix.
  • Chrome users are said to be at a disadvantage vs. Firefox due to extension restrictions.
  • Users mention alternatives like FreeTube, Invidious, Newpipe, PeerTube, and watching via third‑party embeds.

Economics, Ethics, and Future of Ads

  • Some insist no one has a “right” to free YouTube; others argue YouTube grew precisely by being free and is now tightening monetization.
  • Many distinguish between tolerable, static ads and YouTube’s increasingly invasive, frequent ad breaks.
  • There’s skepticism that paid plans (e.g., premium tiers) will remain ad‑free; several expect all streaming services to converge on heavy ad loads.
  • Broader frustration is expressed with perpetual revenue growth pressure, DRM‑like tactics, and what’s seen as corporate overreach in tracking and coercive UX.