>>No, Chrome isn’t killing ad blockers
They’re just neutering them with a ridiculously low limit of rules.
One of the benefits of doing this declaratively is that they can optimize the shit out of these blocking declarations. There is no need for such a low limit. Or even a limit at all.
However I do agree that there shouldn't be a limit, in accordance with https://en.wikipedia.org/wiki/Zero_one_infinity_rule. I think they were just trying to get people to actually clean up EasyList to prune dead rules.
I just checked and my uBlock Origin -- which doesn't have any social filter lists applied -- has 148,339 rules applied in total.
I read 42K from a source earlier today. That's where I got my figure.
https://www.ghacks.net/2019/01/22/chrome-extension-manifest-...
Might it be different for different extensions?
150,000 is definitely better than 30,000, but it's probably not a future-proof number.
EDIT: Actually, given Apple's 50,000 filter limit, I wonder if your source was looking at a version of Easylist that was trimmed down specifically for Safari.
Declarative rules engines are better and preserve privacy better. This is Google following Apple's lead and doing the right thing.
> Yes, but network requests won't be observable without permission on the relevant hosts. And host permissions are changing significantly in Mv3 (e.g. they can't be granted as blanket install time permissions).
https://twitter.com/justinschuh/status/1138889508512866304
there's also some stuff in the design doc: https://docs.google.com/document/d/1nPu6Wy4LWR66EFLeYInl3Nzz...
Which explains the specific hosts part, but only makes vague mention of how extensions that users do want to run on every site will get permission to do so.
>Since the original announcement of the Declarative Net Request API, we have added significant functionality to the API as a result of these discussions. The Declarative Net Request API now allows for the registration and removal of dynamic rules - specified at runtime rather than statically in the manifest. We’ve also added the capability to remove common tracking headers, such as Referer, Cookie, and Set-Cookie.
>We are actively exploring other ways to expand this API, including adding methods to get feedback about matched rules, and support for richer redirects leveraging URL manipulation and regular expressions. Additionally, we are currently planning to change the rule limit from maximum of 30k rules per extension to a global maximum of 150k rules.
They posted a simpler post to the Security blog also addressing these issues.
https://security.googleblog.com/2019/06/improving-security-a...
They lead with the point that most-seemed to get lost in translation, even on technical sites like HN.
>No, Chrome isn’t killing ad blockers