I don't really care anyway. Chrome is not the internet. Just use Firefox.
I don't really care anyway. Chrome is not the internet. Just use Firefox.
If some mechanism or capability is no longer possible or is made infeasible for adblockers to control, then ads will simply switch to using that mechanism. It's a pretty obvious outcome. You cannot simply give just an inch with adtech.
https://github.com/w3c/webextensions/issues/151#issuecomment...
Google is an advertising company. Chrome extensions already experienced a lost decade, where nothing much happened until the Manifest V3 "proposal". It's not a good idea to let Google hold the keys to anti-tracking tech.
[1] I stand corrected, DNS lookups are not part of webRequest in MV2 Chrome either. This doesn't change my larger point.
But Chrome never had CNAME filtering before either
- Now any block filter list will have be updated with a plugin update. So no fetching lists from links directly.
- strict blocking ability [1]
- No dynamic filtering [2]
- No Custom lists (own or third party by the user)
- Element Picker [3]
[1] https://github.com/gorhill/uBlock/wiki/Strict-blocking [2] https://github.com/gorhill/uBlock/wiki/Blocking-mode [3] https://github.com/gorhill/uBlock/wiki/Element-picker
That approach doesn't work well given Firefox's established track record of just imitating Chrome, and then getting rid of the prior (and better) way of doing things.
XUL extension developers are well aware of this problem, for example.
We've seen it happen repeatedly with Firefox's UI, too.
And they aren't afraid to diverge from Chrome in important ways. For example, letting you disable 3p cookies already.
Established track record? What?
> and then getting rid of the prior (and better) way of doing things.
Do you mean how they did the complete opposite by keeping Manifest v2 around for much longer than Google wanted to? Then by making their own Manifest v3 that didn't gimp ad blockers like google has been trying to for years?
> XUL extension developers are well aware of this problem, for example.
XUL was super useful... for it's time.
But it became a drag on performance as Firefox became more optimised for multi-core CPUs. And it became a drag for developers trying to support an older standard. Sure the new extension standard became more difficult to get started, but it did push the workers standards forwards which is ultimately what the web needed.
> We've seen it happen repeatedly with Firefox's UI, too.
Firefox's UI goes up and down in quality all the time. Thinking nothing is improving at all is an observational bias.
That said, it's not like there's a large amount of choice in the browser space. Today's Firefox can be worse (in ways that are important to you & I) than yesterday's but still be the best of the options available to us today.
My opinion, and the reason I switched back to FF, is that FF is the "least bad" option we have.