Conversation

in its current form--if shipped without revision--declarativeNetRequest would be seriously detrimental, but that's most infosec initiatives where the people designing them and the people affected are non-intersecting groups. doesn't have to be ad-related
Quote Tweet
Replying to @whitequark
The problem is sure it blocks google ads, but it doesn't block google's tracking scripts, nor can it block random javascript from other sites. Its a fail-open blacklist scheme, instead of a fail-closed whitelist scheme like noscript (which requires the old API) allows.
1
14
Replying to
Shipping declarativeNetRequest doesn't imply deprecating blocking via webRequest though. It also appears that it's going to ship long before that happens. A better approach would have been implementing declarativeNetRequest and iterating on it before announcing any deprecation.
1
3
Replying to and
Sure, all I'm saying is that they chose the wrong benchmark to use for matching the status quo. A blacklist-based approach is fundamentally not going to block all tracking / advertising and doesn't provide fundamental improvements to privacy and security. It's opportunistic.
1
Show replies