Closed SpencerIsGiddy closed 1 year ago
There’s also a disclaimer in the blocklist saying “for this blocklist to work, the blocking logic must wildcard match”. That’s not all the disclaimer says but that’s the important part of it
serverless-dns already uncloaks CNAME
s (NextDNS does too). What's the use of this list, would you know?
Nextdns says this
“Automatically detect and block third-party trackers disguising themselves as first-party to circumvent recent browser's privacy protections like ITP”
This list is too small. Besides, almost all entries I checked from this list is present in CPBL, 1Hosts, StevenBlack or others. Given that all 3 of those are rethinkdns recommended blockists, a separate entry for just cname blocking isn't really required. What do you think?
Not sure. If those lists contain most of these entries. I guess it isn’t much needed. There is a adguard cname tracker list with about 50k entries. Would that be more suitable do you think?
There is a adguard cname tracker list with about 50k entries. Would that be more suitable do you think?
Can add it to the existing AdGuard list, as an additional entry, yeah.
Thanks! (:
Thanks! (:
No thank you!
A small list that is included with nextdns and it should be included here in my opinion