PSA re: the wild misreporting about Extensions Manifest v3: declarativeNetRequest *is a list-based blocker*, and that's what's being added. This is the same approach Apple/Safari uses for the same reasons (perf & privacy): https://developer.chrome.com/extensions/declarativeNetRequest …
-
Show this thread
-
This is similar to the way Chrome extensions didn't expose all the power that legacy FF extensions did; we all learn the hard way that providing nice things and hoping they don't get misused eventually get users hurt. So this is a correction whose details are being honed.
6 replies 3 retweets 8 likesShow this thread -
One of those details is that the size of the list provided by each extension to `declarativeNetRequest` is something that is being studied from the performance point of view. Remember that many extensions can provide lists!
1 reply 0 retweets 3 likesShow this thread -
And yes, there is an explicit goal here to remove and reduce use of a much, much slower and more privacy invasive system (blocking `webRequest`). This is a move away from a system that is unsafe in most cases to one that is more like what Apple has shipped.
6 replies 0 retweets 5 likesShow this thread -
There *are* open debates about various limits in the new declarative world. But saying "debates rage about the size of a number as tests to verify continue" isn't a great headline...soooo...
3 replies 1 retweet 1 likeShow this thread -
For sense of scale for those just joining, Apple limits the total number of rules in the Safari implementation to 50K (if I understand it correctly; doesn't seem documented). Chrome's proposal is 30K *per extension* with evaluation ongoing to raise it: https://developer.chrome.com/extensions/declarativeNetRequest#property-MAX_NUMBER_OF_RULES …
3 replies 2 retweets 7 likesShow this thread -
Replying to @slightlylate
Safari allows 50K per extension. Some Safari content blockers have adopted a clever workaround of providing multiple extensions per app, e.g. 1Blocker X.https://backstage.1blocker.com/say-hello-to-1blocker-x-8b55efe1ae36 …
1 reply 0 retweets 1 like
Thanks for the clarification!
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
& Web Standards TL; Blink API OWNER
Named PWAs w/
DMs open. Tweets my own; press@google.com for official comms.