0

NextDNS uses the wrong syntax filter lists

An ABP-style syntax list will have...

|| legitdomain.com^specifics
legitdomain##cosmetics

And the domain will be allowed, with some modifications.

However, if an application that only wants to see Domains or Hosts syntax, gets an ABP Syntax list, it either loads zero or it loads all and disregards the specifics, and interprets the text input as simply a Domain or Host to be wholly blocked! I have seen both in application behavior.

How can such a thing be tested? A useful site, and the latest one I found...

https://canyoublockit.com

Blocked by NextDNS with EasyList. OK. Let's see what the current EasyList says...

||canyoublockit.com^$popup,third-party
canyoublockit.com##.elementor-widget-container > center > p

No sign of it being blocked outright! Uh oh. You've been using a list for a Content Filter, not a list for a Network Filter. You're fired.

I noticed this last year, kinda expected it to smooth-out by now, but it hasnt. Nobody noticed.

Reply

null

Content aside

  • 6 days agoLast active
  • 17Views
  • 1 Following