Closed SpencerIsGiddy closed 1 year ago
Does leaving it in affect blocking adversely? If not, it is okay to leave it as-is, I feel.
Does leaving it in affect blocking adversely? If not, it is okay to leave it as-is, I feel.
I have seen people say there are some false positives with the list. https://github.com/AdguardTeam/cname-trackers/issues/62
maybe we can switch it out for this https://github.com/AdguardTeam/cname-trackers/blob/master/combined_original_trackers.txt
maybe we can switch it out for this https://github.com/AdguardTeam/cname-trackers/blob/master/combined_original_trackers.txt
This one contains the cname + AdGuard orig list?
maybe we can switch it out for this https://github.com/AdguardTeam/cname-trackers/blob/master/combined_original_trackers.txt
This one contains the cname + AdGuard orig list?
I think it just uses the cname list but this is probably the list meant for blocklists capable of scanning CNAME records unlike the current one which is very general
Hm, that list has like 10 to 20 entries only
Is the current commit good to be merged?
Is the current commit good to be merged?
Sure!
Thanks (again).
Thanks (again).
😁👍
I was doing some thinking and maybe adguard cname blocklist should not be with adguard sdns since there is a higher chance for false positives and you mentioned in the past that serverless dns already uncloaks cnames anyways. So it seems like a good idea to remove this list from sdns