4 ms·
I wouldn't characterize it as "mic-drop snark" it's just that your assumptions were wrong. There's actually a pretty big contingent on HN that wanted this, the
by tialaramex 6y ago
I wouldn't characterize it as "mic-drop snark" it's just that your assumptions were wrong.
There's actually a pretty big contingent on HN that wanted this, they see the alternatives as either my DNS query goes to the ISP I've already chosen and contracted with, or to Google/ Cloudflare/ OpenDNS who I maybe don't like and don't deal with otherwise - and they'd prefer the former.
The "point" of DoH is actually that it sidesteps ossification. One of the big differences from Mozilla's user privacy focused TRR is that Google's programme cuts to the chase immediately. Your DoH service must work for well formed queries you don't understand, in particular HTTPSSRV. Why? Because the "point" is to get to a world where we can actually use technologies like QUIC and ECH and we can't deploy those technologies at scale in a world where your 1990s ad-tech DNS server responds to anything other than an A query with confused silence.
One of the things DoH allowed them to throw in is a way to express "I won't tell you the answer because censorship" as distinct from just giving bogus answers. Again Google's programme is specific that it's fine to censor stuff, but Comcast are obliged to use this mechanism so that Chrome can tell users "No, you aren't allowed to look at Porn Hub" rather than "Huh, Porn Hub doesn't exist". And again, even though I'd guess you're like me and don't want censorship lots of people do so defeating censorship is not "the point" either.
[Edited to fix quote]
- tptacek 6y agoYou continue to make a strong case for not using Comcast's DNS servers. Since I entered this conversation believing nobody should use Comcast's DNS servers, I'm confused why you're making that case to me personally, but whatever, I agree.