Conversation

This Tweet was deleted by the Tweet author. Learn more

That's not what's happening. The programmatic webRequest API is being partially phased out in favor of a of declarativeNetRequest. developer.chrome.com/extensions/dec It's not true that they're disabling ad-blockers. In fact, they added a built-in ad-blocking engine for extensions to use.

Replying to

and

I don't think it's helpful to spread misinformation about it. The main issue with the proposed draft of the declarative API is the limit of 30000 static rules which is still provisional and they should be pressured to raise it before it ships. It's also genuinely a good approach.

9:11 PM · May 30, 2019Twitter Web Client

Replying to

and

It's very similar to Safari content blockers. A declarative API is more efficient and enables extensions to offer content filtering without needing to see the content of the requests / responses. There are still more complex valid uses for programmatic webRequest blocking though.

Replying to

and

such as JS blocking, which I refuse to browse the web without (e.g. NoScript on Firefox)

Show replies