blocklists VS fdroiddata

It lets you run the "on-device" version of RethinkDNS+. It lets you set blocklists to help you block domains based on categories such as trackers & ads, cryptocurrencies, gambling, social media, adult, security etc with precurated list of blocklists (which are defined here). These are DNS-based blocklists, so as such, they're less powerful than anti-ad browsers like Brave, Vivaldi or browser-based plugins like uBlockOrigin, AdGuard.

There's an open issue to include it: github/serverless-dns/blocklists/issues/21 (the reason we haven't already is that it isn't clear if existing blocklists are insufficient compared to it).

Filter list: Rethink actually has had 1:1 filter support with NextDNS for a long time. It doesn't now since NextDNS has moved a lot of its filters away from the erstwhile open metadata repository. So, now we do our own lists: https://github.com/serverless-dns/blocklists

Commit: https://github.com/serverless-dns/blocklists/commit/ffc73385e166e4d74af20471abfda327f7d89bb8

The code that generates the blocklists is also open source.

We _do_ compile to reduce memory and cpu impact. RethinkDNS app can do 5M entries without breaking a sweat. You don't see us ask folks to not use larger lists because the implementation is such. The code which compresses these blocklists into a compact form for use on mobile devices is open source: github.com/serverless-dns/blocklists/

The repository that builds these (and other lists) for RethinkDNS (the resolver) is at https://github.com/serverless-dns/blocklists

[0] https://github.com/serverless-dns/blocklists

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.