4 ms·
It's OK to inject ads, but not OK to remove them, under Google's current policies.
by Animats 7mo ago
It's OK to inject ads, but not OK to remove them, under Google's current policies.
- Legend2440 7mo agoWell no, actually. Both halves of that statement are false. Injecting ads will get you removed from the extension store if caught, while adblockers are advertised on the front page of the store.
- Animats 7mo agoGoogle's "Manifest 3" rules, vs. ad blocking, in Ars Technica.[1] Did the JSON formatter with ads get kicked out of the extension store yet? [1] https://arstechnica.com/gadgets/2024/08/chromes-manifest-v3-and-its-changes-for-ad-blocking-are-coming-real-soon/ https://arstechnica.com/gadgets/2024/08/chromes-manifest-v3-...
- SquareWheel 7mo agoManifest 3 explicitly enables ad blocking through the declarativeNetRequest API. It's trivial to do so, and many blockers exist in the Chrome Web Store.
- Legend2440 7mo agoEverybody freaked out about Manifest v3, but I'm running Chrome + uBlock and still not seeing any ads. Seems like a nothingburger to me.
- Ygg2 7mo agoWater is merely 49C, said the frog. It's not even 100C. I'll stay. Google really is slow boiling Internet until everyone forgets you can have stuff without ads.
- FergusArgyll 7mo agoublock origin light is featured in the chrome web store.
- eviks 7mo agoBut it isn't as featureful!
- Aurornis 7mo agoSeveral of the top Chrome extensions on their charts are ad blockers: https://chromewebstore.google.com/top-charts/popular?hl=en https://chromewebstore.google.com/top-charts/popular?hl=en They have an API basically dedicated to this: https://developer.chrome.com/docs/extensions/reference/api/declarativeNetRequest https://developer.chrome.com/docs/extensions/reference/api/d... I think you may have been confused about the Manifest V3 API changes, which were controversial because they didn't support every feature of the old API. The mainstream ad blockers all wrote new versions for Manifest V3.
- teruakohatu 7mo agoIt is widely known that Manifest V3 reduces extensions ability to perform SoTA ad blocking. It limits heuristic based filtering, under a guise of privacy.
- armadyl 7mo agoIt was more of a security related change. MV3 overall objectively is far better for browser security than MV2. MV2 was essentially giving extensions a full on free RCE pathway. MV3 is what it should’ve been from the start imo.
- pfg_ 7mo agoMV3 still allows you to run content scripts, which can inject any javascript into any webpage. From there, you can do anything you want. You can steal passwords, tokens, show popups, redirect, ... etc. Preventing extensions from dynamically modifying network requests doesn't change that.