I set this up earlier this month after seeing someone recommend it here on HN in a comment, and after a very good start I decided to stop using it.<p>The performance was very good, and switching default DNS from Google to OpenNIC was easy enough, but the default blocklists included too many domains I needed to use (e.g. mailchimp.com) which were not explicitly ad domains. Whitelisting domains is possible but you have to drop what you are doing and SSH into the Pi, whitelist it and reload the config, then resume what you were doing.<p>But the real dealbreaker for me was that this is largely incompatible with NoScript and its &#x27;Application Boundaries Enforcer&#x27; which gave me constant warnings due to some content being served from my LAN. The way pi-hole works is to intercept your DNS query for &#x27;bad&#x27; domains, re-route it to its own server, and return an empty page. It is the return of an empty page over the LAN that was problematic.<p>Maybe someone more savvy could have made it all work together but at some point you have to evaluate the usability of this versus just toggling an ad-blocker with your browser. The browser ad blocker is just faster and easier when you need to override anything.