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

Daniel Micay

@DanielMicay

May 30, 2019

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.

Replying to

You're seriously misrepresenting the thread you quoted, where UBO author says the new declarative filtering is not sufficiently powerful to implement UBO, regardless of filter count limit.

Replying to

I wasn't not summarizing what he said but rather adding some information which wasn't mentioned in the thread. You say that I'm misrepresenting what he said, but it's really you misrepresenting what I said right here. It's absolutely not what I said in those tweets.

Replying to

and

I linked to his own summary and people can read that in my first tweet. I told people to go read the thread rather than summarizing or paraphrasing it here. I wanted to add that the developers say the current limits are placeholders. They haven't said how much they'll raise them.

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