Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

I'm confused. For me, a major selling point of DoH is it hides DNS queries from your ISP, which has detailed personal information about you. And if you're locked into Comcast, you're operating with completely eroded trust from the get-go.

Clearly, DNS statistics are extremely valuable to Comcast, or they would not have engaged with Mozilla to get back the data, nor would they have raised hell with Congress.

I would not have expected an organization like Mozilla to sign a data deal with Comcast, even if Comcast is now theoretically restricted on how they use the data.

This is a weak move.



Mozilla cannot enable one provider by default. People already complained that Cloudflare was initially the only choice.

Users at the moment are expected to choose their provider anyway.

This deal is about Mozilla picking Comcast by default for Comcast customers. This is essentially as if they'd be using the network's default, because Comcast is the network's default already, being what people get via DHCP.

They can always choose a different provider. And Mozilla apparently struck a privacy deal with them too.


I understand the arrangement. From a Comcast user’s perspective, very little has changed, depending on how much trust you assign to a “we promise” privacy agreement. Are Comcast users better off than default? Yes. But decoupling DNS from ISPs which sit in such a privileged position is, for me, 85% of the threat model.

I’d like to read more about how the choice will be presented to users, beyond about:config. I’d also like to understand more the community’s reaction to Cloudflare default.

What if there was a round robin setup between neutral operators? Pairing Comcast users to Comcast just seems like a wtf move.


Having just done a Firefox install recently, the UX when prompted to enable DoH on first run did not set the expectation of choosing a provider.

Is there something you can point to that speaks to that expectation?




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: