3 ms·

Probably because v2 extensions haven't been switched off yet. It might be different in January 2023; or maybe the limited adblocking of v3 will be enough for m

Probably because v2 extensions haven't been switched off yet. It might be different in January 2023; or maybe the limited adblocking of v3 will be enough for most people. Time will tell.

mmis1000 5y ago
Ad providers are obfuscating domains to bypass blocks. Currently only ublock origin deobfuscate and block based on the original domain.(It is supported on firefox only anyway) But after the change... I guess no one on chrome can do. And ad blocking will be totally useless at that point. See also: https://github.com/gorhill/uBlock/wiki/Dashboard:-Settings#uncloak-canonical-names https://github.com/gorhill/uBlock/wiki/Dashboard:-Settings#u...
- xwdv 5y ago
  What about first party domains
  - XorNot 5y ago
    Behavior-based blocks take care of those largely. I think only Facebook is reliably staying ahead?
    - Stephen304 5y ago
      If you mean ublock origin cosmetic filters, yeah facebook is really putting up a fight. The status quo has been randomized css classes, identical html structure, interspersing hidden junk characters in between the "Sponsored" text, and the latest I've noticed, anchors that link to # until you hover over, preventing blocking href=^/ads. That and turning on or off or changing behavior between users and regions makes collaborating on rules really difficult.
      - vadfa 5y ago
        This has me surprised because most of these changes are not very complicated and I have always wondered why these methods weren't more widespread. To me defeating ad blockers seems easy as long as you're willing to play cat and mouse (and if your income depends on it I guess you are)
      - bashinator 5y ago
        Now I’m imagining monetizing an ad-blocker by selling CAPTCHA services based on users training an AI to recognize Facebook ads.
- sharps1 5y ago
  Brave also does the CNAME uncloaking like uBO. https://brave.com/privacy-updates-6/ https://brave.com/privacy-updates-6/
saurik 5y ago
Around which time Firefox is intending to make the same changes, having deprecated v2 manifests (this post seems to use that term to mean the actual removal) and doing all the API swaps to service workers and the such. Firefox just makes all the same decisions Chrome does, the good and the bad. https://blog.mozilla.org/addons/2021/05/27/manifest-v3-update/ https://blog.mozilla.org/addons/2021/05/27/manifest-v3-updat...
- NoGravitas 5y ago
  Mozilla does plan to support the old request-blocking APIs indefinitely, though, even after the Manifest v3 switch, until an alternative that meets the needs of extension developers is developed.

Probably because v2 extensions haven't been switched off yet. It might be different in January 2023; or maybe the limited adblocking of v3 will be enough for most people. Time will tell.

mmis1000 5y ago

Ad providers are obfuscating domains to bypass blocks. Currently only ublock origin deobfuscate and block based on the original domain.(It is supported on firefox only anyway) But after the change... I guess no one on chrome can do. And ad blocking will be totally useless at that point. See also: https://github.com/gorhill/uBlock/wiki/Dashboard:-Settings#uncloak-canonical-names https://github.com/gorhill/uBlock/wiki/Dashboard:-Settings#u...

xwdv 5y ago
What about first party domains
- XorNot 5y ago
  Behavior-based blocks take care of those largely. I think only Facebook is reliably staying ahead?
  - Stephen304 5y ago
    If you mean ublock origin cosmetic filters, yeah facebook is really putting up a fight. The status quo has been randomized css classes, identical html structure, interspersing hidden junk characters in between the "Sponsored" text, and the latest I've noticed, anchors that link to # until you hover over, preventing blocking href=^/ads. That and turning on or off or changing behavior between users and regions makes collaborating on rules really difficult.
    - vadfa 5y ago
      This has me surprised because most of these changes are not very complicated and I have always wondered why these methods weren't more widespread. To me defeating ad blockers seems easy as long as you're willing to play cat and mouse (and if your income depends on it I guess you are)
    - bashinator 5y ago
      Now I’m imagining monetizing an ad-blocker by selling CAPTCHA services based on users training an AI to recognize Facebook ads.
sharps1 5y ago
Brave also does the CNAME uncloaking like uBO. https://brave.com/privacy-updates-6/ https://brave.com/privacy-updates-6/

saurik 5y ago

Around which time Firefox is intending to make the same changes, having deprecated v2 manifests (this post seems to use that term to mean the actual removal) and doing all the API swaps to service workers and the such. Firefox just makes all the same decisions Chrome does, the good and the bad. https://blog.mozilla.org/addons/2021/05/27/manifest-v3-update/ https://blog.mozilla.org/addons/2021/05/27/manifest-v3-updat...

NoGravitas 5y ago
Mozilla does plan to support the old request-blocking APIs indefinitely, though, even after the Manifest v3 switch, until an alternative that meets the needs of extension developers is developed.