smashblock VS cname-cloaking-blocklist

However, you should not generally being seeing popups like these. You might want to try the SMASHBLOCK Blocklist as well as some of the built in annoyance filters. StevenBlack/hosts is another great one. Both of those are amalgamations of multiple blocklists, so they will filter way more stuff than you're used to. You might find yourself temporarily or permanently allowing some hosts to go through, more than you're used to.

uBlock Origin - with most relevant adblocker filters installed, including custom ones like NoCoin, SMASHBLOCK, and others.

Awesome work!

For anyone interested in using The Quantum ad-list in their adguard setups, I've added this to my self-updating ad gaurd block list generator (smashblock - which is also based on hblock).

https://github.com/smashah/smashblock

So nextdns’s third party disguised trackers is actually really tiny of a list, like 30 domains. (Im trying to add more so it has the same amount of cname’s blocked as adguard). Anyways, the reason why the list is so tiny is because it uses wildcard logic so all subdomains get blocked. It already uses some of the cname companies that adguards cname-tracker list uses but not all. Hopefully my pull request can get merge eventually because then the setting will be a little bit more effective

We've been discussing this new list source on another forum. As stated by some other users, a lot of the entries are already included in other lists, even that isn't very efficient. A long time ago, NextDNS published something similar on GitHub, after looking into that, I created and published a script that turned these entries into regex blacklist entries, which provide adequate protection against CNAME cloaking. Now the Adguard Team has published their version, however, using a similar technique to create regex blacklist entries also provides adequate protection, without adding thousands of new (some duplicate) entries to gravity. The file of interest in the entire repository is the json file, it contains the domains that would require regexes to efficiently block everything in the lists. When adding the regex entries, using a script, it turned out most of them are already covered by the NextDNS entries, only 9 additional regexes are added. For those who are interested in using the regex blacklist method, as opposed to adding big lists, you can find the entire explanation (and how to) in my pihole manual, section 15 (Deep CNAME inspection). the domain users.telenet.be may require whitelisting!