News for hackers. Stuff that matters.

A comment on Web Request and Declarative Net Request: Explaining the impact on Extensions. Parent comment

Re:Web Request and Declarative Net Request: Explaining the i... by dfabulich on Wednesday June 12, 2019 @02:59PM (#20168087)
The rule limits Google's proposing are more generous than the limits Apple puts on content blockers. Apple allows only 50K rules. And it turns out 50K rules is actually fine!

Declarative rules engines are better and preserve privacy better. This is Google following Apple's lead and doing the right thing.

[ Parent | on HN ]
Re:Web Request and Declarative Net Request: Explaining the i... by mixedCase on Wednesday June 12, 2019 @03:18PM (#20168271)
> The rule limits Google's proposing are more generous than the limits Apple puts on content blockers

And Firefox and most Chromium forks have no limit. Does that mean they have infinite generosity?

Seriously, how is Apple being bad at something an argument for lowering other options to the same level? Right now I have ~200K filters enabled on this machine. EasyList alone is sitting at 90K according to uBlock Origin.

[ Parent | on HN ]
Re:Web Request and Declarative Net Request: Explaining the i... by buckminster on Wednesday June 12, 2019 @03:18PM (#20168270)
Please don't spam the same comment multiple times.

https://news.ycombinator.com/item?id=20168111

[ Parent | on HN ]
Re:Web Request and Declarative Net Request: Explaining the i... by hungryfoolish on Wednesday June 12, 2019 @04:04PM (#20168706)
>And it turns out 50K rules is actually fine!

No its not. Plus, if you combine Easylist with a bunch of additional filter lists, then it very easily crosses 50k.

[ Parent | on HN ]