| People keep bringing up Manifest v3 like it's some evil plot to show people ads. Nevermind that Chrome already ships with its own adblocker which blocks bad ads. The fact is that with the Spectre mitigations added to Chrome, the performance of networking with manifest v2 was bad. Having to keep sending every network request through 3 different processes just in case there is a plugin (uses by the minority of users) that wants to filter the requests before they are made. Of course, blocking resource fetches like that could have easily been detected by any server that cares about it, and the interaction with service workers was...weird. With manifest v3 you can still block ads. You can remove them from the DOM, you can make them invisible, you can replace them. You just can't programmatically decide which resources to filter - only a declarative model for resource filtering is supported. |
No it doesn't, because I define all ads as bad, so Chrome's ad "blocker" is does not even remotely meet my needs.
> You just can't programmatically decide which resources to filter
That "just" is doing a ton of work there. Declarative ad blockers aren't terrible, but they're not great either. And I don't want my browser fetching ads (which could also be malware) at all. Downloading them and then hiding them is insufficient.