Hacker News Reader

Comment by tombrossman | Hacker News Reader

I really like it too but after extended testing I found it was incompatible with NoScript's Application Boundaries Enforcer because pi-hole replaces ad requests with an empty HTML 'page', rather than simply dropping or blocking ads like a browser ad-blocker would.

I don't know enough about how this works to figure out how to work around it so I reverted to blocking ads at the router with a hosts file. NoScript provides too many other benefits so I had to keep it and stop using pi-hole.

View on HN

Do you actually use the ABE specifically, that part can be turned off (NoScript > Options > Advanced : ABE and then uncheck the enable checkbox) without stopping any of the other aspects from working.

I'm not a dev but looking very quickly at pihole it seems it serves an index.html file (https://pi-hole.net/faq/is-it-possible-to-change-the-blank-p...) in place of ad content, you might make that a link to /dev/null or just make it a blank file, and see if that works? I suspect it won't as the ABE is checking for the correct origin of content and pihole is spoofing the origin.

I use ABE only because it's enabled by default and it seems like a sensible thing to do. At the time I tested pi-hole, reverting to router hosts blocking seemed easier so I left it at that. Maybe I'll look at it again and see if I can selectively disable ABE for the pi-hole's IP address which should solve the issue.

For me the big difference is management - pihole has a nice interface and there are a bunch of browser extensions compatible with it, you can exclude all of their lists and start from scratch.

Hmm, I think ABE works back-to-front of what you want, eg http://stackoverflow.com/questions/20111530/noscript-abe-all.... You let a remote page have access to local data, so you'd need access rules for all the external pages that are adblocked to let them have access to the local content that pihole wants to stuff the ad spaces with.

This might work, using https://noscript.net/abe/abe_rules.pdf, but I'd ask at the NoScript forums. The rules cascade so it would need to go at the top.

    #ABE rules
    # ALL matches any URI
    # accept lets it happen, sandbox and anon probably would be fine too
    # INCLUSION is any sub-page level part, like images and such, can specify further which inclusions
    # LOCAL is any local address including those in noscript.ABE.localExtras (see about:config);
    Site ALL
    Accept INCLUSION from LOCAL
    # Deny # probably only needs that if you're not prepending already made rules??

That might negate much of ABE though as you're letting external sites reference anything that they find on the local domain.

Let me know if it works!

Reply on news.ycombinator.com