Eyeo adblock vs declarativeNetRequest implementation

[BugmanSpirit]

I remember that eyeo adblock or bromite's subresource filter based adblock was initially picked up because of light weight resource consumption and good integration with existing chromium codebase. Looking at google's declarativeNetRequest implementation, it already does all that both of these adblockers tried to achieve. It uses the same fundamentals from google's sub resource filter like flatbuffer for storing rules on disk. It will be maintained by chromium upstream so no problem of integration. And it also has better community for maintaining filter lists like uBO lite, which is much better than adblock plus. So why not ditch this eyeo thing and just support extensions like uBO lite?

[uazo]

So why not ditch this eyeo thing and just support extensions like uBO lite?

Simply because extensions do not work on Android, for now (#256)

[BugmanSpirit]

Would declarativeNetRequest be preferred once extensions available? And what about using patches from Kiwi? I aslo see that Edge has added them in android

[uazo]

Would declarativeNetRequest be preferred once extensions available?

I don't know.

And what about using patches from Kiwi?

see #256