webextensions

This seems to be a significant problem: https://github.com/w3c/webextensions/issues/493#issuecomment... TL;DR: In order to detect ad blocks sites create "bait" URL's that look like ads, but are purely there to detect if ad blockers block them. The only reason to do that is to punish the user for using a ad blocker, perhaps by nagging them, perhaps by refusing to display or load the content entirely. UBO responded by making bait URL's appear to work by redirecting them to local resources. Sites responded to that by putting required content behind bait URL's. So UBO now uses a number of dynamic heuristics it uses to detect what is bait and what isn't. Those heuristics aren't possible in V3. My guess is UBO ability to change it's behaviour for every site based on what the site did created never ending war between ad blocker detectors an

Exactly as they intended. They can claim all they want that this is for security and that they're "supportive" of adblockers, but if you read the meeting minutes it's clear that they're just phoning it in in terms of the API surface needed to properly support adblocking against a hostile web. https://github.com/w3c/webextensions/blob/56dc974e5d583d6989... https://github.com/w3c/webextensions/blob/01ac3748984f31885c...

It sure is awfully convenient that MV3 by design will prevent referal-stripping extensions https://github.com/w3c/webextensions/issues/302 (By the way, the meeting minutes are all published so you can read exactly how they're conspiring to kill your privacy and security. Take note of how many times they decide not to implement something citing that they don't want to engage in a cat-mouse game. How benevolent of them, to make the hard decisions on our behalf.)

That’s wrong: https://github.com/w3c/webextensions