3 ms·
(Kicking around an idea to build this:) Would anybody be interested in a local DNS server that automatically updated its list of black-holed domains through a
by politician 9y ago
(Kicking around an idea to build this:)
Would anybody be interested in a local DNS server that automatically updated its list of black-holed domains through a mechanism that preserved your privacy? (Assuming, of course, a decentralized representation of the block lists.)
Would anybody be willing to sell their attention by accepting payment (BTC), perhaps through a dutch auction, to re-enable a black-holed domain for a time-limited period? (Hand-waving the mechanism for ensuring that the domain was actually whitelisted.)
I'd personally be interested in the former, and would likely use the latter - even though I find it hilariously unlikely that Ad Networks or Web Sites would participate in bidding for my attention directly.
- victorvation 9y agoLarge ad publishers such as Google and Facebook are already doing the equivalent of auctioning users' attention by proxy of views, clicks, and conversions through their existing ad delivery methods.
- politician 9y agoWouldn't you rather be in control?
- shuntress 9y agoIf you don't already know about it, definitely check out https://pi-hole.net/ https://pi-hole.net/ I'm not totally clear on where their blacklist comes from but their mainpage claims "Known ad-serving domains are pulled from third party sources and compiled into one list" This is pretty much exactly your first suggestion and seems like it would be an excellent platform on which to launch your second suggestion.
- stordoff 9y agoDefault block lists appear to be: https://github.com/pi-hole/pi-hole/wiki/Customising-sources-for-ad-lists https://github.com/pi-hole/pi-hole/wiki/Customising-sources-... The most comprehensive of the lists appears to be https://github.com/StevenBlack/hosts https://github.com/StevenBlack/hosts , which is the same list I use for DNS filtering on my DD-WRT router. Seems to work pretty well.
- atesti 9y agoThe problem with the hosts file is that some sites have onclick-handlers in their download-buttons etc. that first call out to google analytics etc. to register the event before allowing it. Blocking on the host level makes these sites fail and temporarily disabling hosts is cumbersome. Ghostery has a nice little library of stubs for e.g. ga that are injected in each page. I think any good solution will need to have such shims. Doing it on the network level (like redirecting to a stub hosting webserver) has problems with SSL