NextDNS-Config VS metadata

As far as lists go, its extremely subjective. Definitely look into the Hagezi lists and yokoffing's configuration guide, I'd recommend Multi Pro++ for most people. Most other blocklists are redundant with that one.

I followed this https://github.com/yokoffing/NextDNS-Config and my Apple private relay works. It shows a red dot next to the profile when I check but the logs still show what I browse

You download the app, create an account at the official website NextDNS.io, the the first page that will open will be the setup page. From there you will choose your device and follow the steps until your NextDNS account is connected to your device. For the blocklists I recommend this website for guidance. After that you’re all set.

Nope. Can’t confirm. Abel to reach the site while running the same (and only) list. I also don’t see these exact trackers blocked while accessing the domain. I’d set up my profile with this guide. Hope that helps. BR

There is this guy on GitHub and he also did an in depth analysis and wrote a guide. He recommends HaGeZi - Multi NORMAL. I'll stick with that.

Which list is blocking archive.org? If "NextDNS Ads & Trackers Blocklist", probably some kind of mistake, write about it - https://github.com/nextdns/metadata/issues

You can find the NextDNS lists here: https://github.com/nextdns/metadata

You can always look at github. This is just the activity for their metadata repo: https://github.com/nextdns/metadata/commits/masterFeel free to check their other repos.

NextDNS gives you a whole bunch of 3rd party filters, maintained by random dudes in Github repos as a hobby. We support some of them too in the "3rd party filters" tab, however we don't encourage anyone to actually use them, as we have our own Native filters, that we've built up over the course of 5 years based on feedback for millions of Windscribe (our sister company) users. Our native filters are highly effective, and prone to much fewer false positives. We recommend you try them, you will be pleasantly surprised with how they perform. I guarantee you that you will spend 90% less time making whitelist rules for false blocks... or your money back :) "Native tracking protection" filters are all part of the IoT Filter. NextDNS has the individual toggles, which enforce this small set of rules. Out IoT filter enforces all of them, as well as 10x more things.

Here is the list: https://github.com/nextdns/metadata/blob/master/parentalcontrol/categories/video-streaming.json

Here's those native blocking lists from NextDNS: https://github.com/nextdns/metadata/tree/master/privacy/native

From https://github.com/nextdns/metadata/blob/master/privacy/blocklists/energized-ultimate.json the link used is https://block.energized.pro/ultimate/formats/domains.txt which currently contains nothing but comments.