adblock-rust VS fdroiddata

Brave has written their own (open source) adblock engine (in rust) that is directly integrated into the browser (ie. not an extension, so is not affected by Manifest V3).

https://github.com/brave/adblock-rust

Here is a (somewhat dated) article describing it by the authors:

https://brave.com/improved-ad-blocker-performance/

Brave has its own Rust implementation of an adblocker embedded in the browser: https://github.com/brave/adblock-rust; so it does not embed uBlock Origin (but the filters are mostly compatible)

Disclaimer: I work at Brave but not on the browser.

We support :has currently, which impacts many filters in EL and uBO. Some non-supported filters such as upward() can be manually converted over to use :has instead. The other unsupported procedual filters are a WIP will depend how easy/hard they are implement. No ETA, but have opened a ticket https://github.com/brave/adblock-rust/issues/293

ublock on chromium and brave itself can't use all of the filters in that list: https://github.com/brave/adblock-rust/issues/4

It's open source https://github.com/brave/adblock-rust

I've fixed this in the adblock engine as of https://github.com/brave/adblock-rust/commit/8a755bdb190bb55a3a3acee1e6507085051bdeec, and I'll push to get this patched in 1.47 soon. Thanks for the reports!

Fork this repository.

For reference my app: project: https://github.com/balzack/databag merge request: https://gitlab.com/fdroid/fdroiddata/-/merge_requests/12183

You should add a new entry in "Builds". Have a look at how Newpipe does it for each new version here for example.

To me it's not very clear whether those terms practically apply only to their app, since clearly they can't grab logs from Aurora if Aurora doesn't dump those logs for example... but if this is something the F-Droid team should look into, open an issue on https://gitlab.com/fdroid/fdroiddata/-/issues or inquire in one of their official channels on OFTC (#fdroid) or Matrix (#fdroid:f-droid.org).

OsmAnd~ from F-Droid not having Android Auto is a known bug: see the discussions at https://gitlab.com/fdroid/fdroiddata/-/issues/2567 , https://github.com/osmandapp/OsmAnd/issues/13514, https://github.com/osmandapp/OsmAnd/issues/3391 and https://github.com/osmandapp/OsmAnd/issues/15400

You can also get F-Droid Build Status which I believe will let you see apps that are being attempted to be built even if their build isn't succeeding yet, again for the "catching things early experience". Or, just keep an eye on the issues, merge requests and commits at fdroiddata which is where people actually add new metadata for new apps to be built by F-Droid, and it often takes a while between an app being first mentioned, and it being able to be included, for many possible reasons.