Google confirms they will disable uBlock Origin in Chrome in 2024

Original Article ↗ Hacker News Discussion ↗

Google’s decision to disable Manifest V2 extensions in Chrome in 2024 is widely seen as a de facto move against powerful ad blockers like uBlock Origin, raising concerns about user control, privacy, and the future of effective content filtering. Commenters debate how much Manifest V3’s new declarative APIs will weaken ad blocking in practice, noting specific lost capabilities and questioning Google’s stated security and privacy rationale. Many expect the change to push technically inclined users toward alternatives such as Firefox, Brave, or Vivaldi, and see it as an opening for rival browsers to differentiate themselves on ad blocking and user autonomy.

Scope of Google’s Change

  • Google is disabling all Manifest v2 extensions in Chrome; uBlock Origin is not named but will be affected along with many others.
  • Several commenters argue the thread title (“disable uBlock Origin”) is misleading because it implies Google targeted uBO by name; others say it’s fair shorthand since the practical effect is obvious to users.

Manifest v3 vs v2: Technical and UX Impact

  • MV3 removes the powerful “blocking webRequest” API and replaces it with declarative rules (declarativeNetRequest), so extensions cannot arbitrarily intercept/modify network traffic.
  • Expected consequences for robust blockers like uBO:
    • Harder or impossible to block certain dynamic/script-driven ads (e.g., YouTube techniques).
    • Loss or reduction of features such as cosmetic filtering, scriptlet injection, URL parameter stripping, CSP manipulation, and flexible redirect rules in uBO’s MV3 variant.
    • Rule and allowlist limits (though Google is raising some limits).
  • Some say MV3 improves security, privacy, efficiency, and reliability; others counter that it mainly removes user control while still allowing inspection of traffic, so claimed privacy benefits are dubious.

Motives and Strategy

  • Many see this as an indirect but intentional move to weaken ad blockers and protect Google’s ad revenue, especially given parallel YouTube anti-adblock measures.
  • A minority view it as a genuine security/privacy hardening that unfortunately affects ad blockers.
  • Some expect Google to “slow-roll” further restrictions over years.

Browser Ecosystem Responses

  • Strong advocacy to switch to Firefox, which is implementing MV3 but keeping the blocking webRequest API so full-strength ad blocking remains possible.
  • Brave’s built-in (non-extension) ad blocker is said to be unaffected. Vivaldi and others have signaled interest in retaining MV2, but maintaining a divergent Chromium fork is seen as costly.
  • Edge, Arc, and other Chromium-based browsers’ plans are unclear; speculation that search-revenue deals with Google discourage them from being too ad-blocker-friendly.

Broader Reactions

  • Many vow to abandon Chrome or further “de-google” (alternative browsers, email, and productivity suites).
  • Some are skeptical Google will really execute after years of delays; others think ad pressure means they will this time.
  • Concern is expressed about Firefox’s dependence on Google funding and what happens if that support is reduced.