Recent and related:
Chrome is looking to permanently drop MV2 extension - https://news.ycombinator.com/item?id=48471970 - June 2026 (450 comments)
Fuck Google
Title: Ad company makes a browser update to disable ad blocking
News at 11.
I'm sorry for the glib comment but "they could just not do this"
Seriously. Imagine a company that solicits advice from the public. Not all of it is going to be good. The customer isn't always right, but basically the reaction to Should We Do This would be Fuck No
But they'll do it anyway. You should get fired from your job if you just plow ahead like this
[dead]
[dead]
tl;dr MV2 is going away (after already being deprecated a while ago). MV3 exists, you're probably already using it in your adblocker.
Stop suggesting this Firefox crap which is not only much slower but it also can't even properly manage RAM usage on mobile, leading to app being killed on my low-RAM device, chrome can deal with it even though that's a "desktop" version with extensions for a much newer high end device.
Restricting webRequestBlocking (but it's not going away, just needs a policy extension) and synchronous executeScript did in practice make adblockers unreliable though.. I partially worked it around by using a custom extension that uses the recent userScripts API..
BTW, it's not possible to inject scripts to workers like a ServiceWorker or to replace it's content (DNR let's you redirect but this redirect breaks SW origin + it's visible when you disallow redirects), but MV2 was no better, chrome extensions never had advanced capabilities for ad blocking, a bug about not being able to access POST data via webRequest was open for 10+ years and will probably never be fixed.
But still, firefox is not the alternative, even WebKit is much better.
This is not true. There are other APIs extensions can use to block ads and browsers like Brave have ad blocking built into the engine itself.