Adblock Warning Removal List

[mikedelic]

Please add the following blocklist.

https://easylist-downloads.adblockplus.org/antiadblockfilters.txt

[quantumpacket]

Those do not work with DNS. They operate at the HTML level, to block specific elements on the page, in this case adblock banners/messages. NextDNS can only block per DNS.

[mikedelic]

What does work with DNS?

…

On Jun 2, 2021, at 3:07 PM, 0ri0n ***@***.***> wrote: Those do not work with DNS. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#683 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APOO4AZVWG7ROTD4SP2WT7TTQZ6P5ANCNFSM457JOE5A>.

[beerisgood]

What does work with DNS?

Domains like github.com.
You should read about DNS

[mikedelic]

Would this work? https://github.com/reek/anti-adblock-killer#anti-adblock-killer--reek

…

On Jun 2, 2021, at 4:40 PM, beerisgood ***@***.***> wrote: What does work with DNS? Domains like github.com. You should read about DNS — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#683 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APOO4A6L3NWPRAQIZDWEESDTQ2JKVANCNFSM457JOE5A>.

[quantumpacket]

No. Just throwing list suggestions without knowing how DNS works is not productive.

[beerisgood]

Please close this issue as it doesn't make sense nor can be solved.

[mikedelic]

You’re right. You’re the experts. What would be productive is to know if there are any potential plans on the table to add anti-adblock to your NextDNS Filters for paid customers, instead of short rude comments. FYI: This is where customers are routed to make these types of suggestions. https://help.nextdns.io/t/q6hmva4/custom-blocklist-support

…

On Jun 2, 2021, at 4:58 PM, 0ri0n ***@***.***> wrote: No. Just throwing list suggestions without knowing how DNS works is not productive. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#683 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/APOO4A5H22L4ZSIC3ONTZXLTQ2LQ3ANCNFSM457JOE5A>.

[crssi]

Did search for some nicely written article explaining difference between DNS and path or content filtering.
I am not good at explaining, but since I haven't found any good article, I will try...

Filtering on DNS level works only for hosts, that is:
you can control to allow or deny DNS requests on host level like for example subdomain.example.net
but you can't go deeper into to allow or deny by URL path for example subdomain.example.net/somepath/etcetera, since DNS does not know nothing about the path
also you cant control on DNS level the behavior on content level

So, for path or content level you need in-browser solution like uBlock Origin or similar.

Think of DNS as of a telephone book.
So you can control the telephone numbers, but not extensions (like URL path), and you cant control by the words spoken over the line.

Cheers

[romaincointepas]

As said in this thread, those lists unfortunately do not work at the DNS level.

Great explanation @crssi by the way.