Conversation

This Tweet was deleted by the Tweet author. Learn more

This is true, but have you seen the thread at twitter.com/gorhill/status? The approach being taken by Chromium is able to provide EasyList-style functionality, but it's missing the enhanced capabilities provided by uBlock Origin. It's fine as a replacement for *most* ad-blockers.

Quote Tweet

R. Hill

@gorhill

May 30, 2019

It is not possible for uBlock Origin ("uBO") to retrofit its matching algorithm into the set-in-stone matching algorithm of the declarativeNetRequest API.

Show this thread

Replying to

and

It's not a replacement for uBlock Origin though, and it would currently be a regression from it. It definitely makes sense to have this as a more robust and efficient declarative API, but it should actually be a competitive alternative to the leading content filtering engine.

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

Replying to

and

I don't think it's appropriate to deprecate webRequest before at least providing the capabilities needed for matching how uBlock Origin currently works. This would have been seen as a positive thing if it was approached differently and if the benchmark wasn't Adblock Plus parity.