Daniel Micay on Twitter: "@RichFelker The Chromium developers and Google are countering the claim that they're dropping ad-blocking support by pointing out that they aren't doing that. It was completely counterproductive to have this fake news cycle distracting from the actual issues with their proposed changes." / Twitter

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

1

8

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.

2

1

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.

1

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.

2

Replying to

His thread is highly critical of Google's move. You're quoting it in a context of claiming folks are over-reacting in a way that implies it backs up that claim. Or at least that's how I read it...

1

Replying to

My words speak for themselves: twitter.com/DanielMicay/st That's not what I said. I told people to read his thread criticizing what they're changing, rather than reading the fake news completely misrepresenting what is happening. The people spreading misinformation aren't helping.

Quote Tweet

Daniel Micay

@DanielMicay

May 30, 2019

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.

Show this thread

1

Replying to

and

The Chromium developers and Google are countering the claim that they're dropping ad-blocking support by pointing out that they aren't doing that. It was completely counterproductive to have this fake news cycle distracting from the actual issues with their proposed changes.

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

Replying to

and

There's now going to be an official response pointing out that they aren't dropping ad-blocking support. The actual issues are going to be completely missed, and I doubt they will be included in the official response. I find these cycles extremely counter-productive / harmful.

1

Replying to

and

There are also 2 separate things here. Adding the declarativeNetRequest API is a very positive thing, and isn't the problem. As

@gorhill

mentions, the reasoning behind that is legitimate. They do not need to deprecate webRequest as part of adding a declarative alternative though.

Replying to

It's likely that they *are* effectively dropping ad blocking support, especially if blocking anti-adblock depends on non-declarative filtering capabilities which it likely does.

1

Replying to

We'll see what ultimately ends up happening and the impact of it. The claim that it's motivated by business reasons is implying that their privacy and security engineers are explicitly lying about the motivations and design process behind the changes based on their responses.

2

Show replies

Conversation