Conversation

An accurate/informative thread about the proposed changes in Chrome by the uBlock Origin developer, summarized in this conclusion: twitter.com/gorhill/status I recommend reading that thread and skipping all the fake news falsely claiming Chrome is removing support for ad-blocking.

Quote Tweet

R. Hill

@gorhill

May 30, 2019

I am not against the declarativeNetRequest API, and I am not arguing against the stated advantages -- they are legitimate. I am against the conversion of the webRequest API into a passive one and other changes crippling uBO's ability to seamlessly function as it does now.

Show this thread

10:13 PM · May 30, 2019Twitter Web Client

Replying to

The declarative filtering API is documented at developer.chrome.com/extensions/dec. They've stated that the limits are placeholders are subject to change. Increasing the static limit by 10x is probably enough. Introducing this API for the built-in content filtering is a very positive thing.

Daniel Micay

@DanielMicay

May 30, 2019

The current draft of Manifest V3 deprecates the webRequest blocking capabilities, with declarativeNetRequest as a replacement for most cases. There's still a use for programmatic rather than declarative filters, and arguing against removing it can be done without misinformation.

This Tweet was deleted by the Tweet author. Learn more

Replying to

I don't quite know what you mean. Filter lists is how existing extensions work, and they implemented an equivalent to the EasyList / Adblock Plus style filters. uBlock Origin offers more power than that, but there's no reason it couldn't be how the built-in blocking engine works.

Show replies