2 ms·
> IMO, it's just a DNS black hole with a slick interface This is why it gets to the front page. It's a DNS black hole with a slick interface. You run it and
by buro9 8y ago
> IMO, it's just a DNS black hole with a slick interface
This is why it gets to the front page.
It's a DNS black hole with a slick interface.
You run it and it does great by itself, manages the updates, and when it does do something you don't want (or vice versa) there's this really slick interface for figuring it out and correcting it.
We underestimate how much slick interfaces are worth, especially when they make a chore that was almost entirely CLI driven and making it a non-chore for a bigger audience.
- asutekku 8y agoThis is a thing a lot of engineers don’t seem to get. Slick interface is the most important thing for public, no one wants to use terminal or advanced settings to actually do anything related to your product.
- nominated1 8y agoMy comment also states that since adblockers have come along a DNS solution seems a bit archaic. Adblockers are even more slick and user friendly so your reply doesn’t at all answer, why? Why move back to a less than solution? Lack of device control, unknown alternatives, unwillingness to just say no (for whatever reason… not criticizing here) seems to be the answer. Unfortunately, as ignoramous states there are techniques that will render DNS blacklisting useless if they want to.