If it’s so great for Privacy, why does it support DNS over HTTPS?
Taking name resolution control away from the user and the OS is NOT a benefit to your privacy. Especially since bad actors can and do exploit DNS for data exfiltration.
I don’t see any inherent problem with the two things you say are problems: neither DoH, nor the idea that a browser can override default settings.
I’m not a fan of defaulting to Cloudflare, but this seems more like a case of picking your poison. Somebody’s going to get a crack at the domains you’re visiting, are they not? It seems better to encrypt these queries than to allow a middleman to intercept them.
Regarding override default system settings, is this really a problem? I prefer browsers that give people extra options, and I would find it worse if they suddenly took this option away.
If it’s so great for Privacy, why does it support DNS over HTTPS?
Taking name resolution control away from the user and the OS is NOT a benefit to your privacy. Especially since bad actors can and do exploit DNS for data exfiltration.
(And yes, you can disable it… FOR NOW.)
DNS queries can be and are logged by public WiFi access points and ISPs. DoH cannot.
It doesn’t take anything away. It’s just a default. If you don’t want DoH, then just turn it off.
So you’re okay with the current situation and are complaining about some hypothetical future that you are theorizing might materialize?
I don’t see any inherent problem with the two things you say are problems: neither DoH, nor the idea that a browser can override default settings.
I’m not a fan of defaulting to Cloudflare, but this seems more like a case of picking your poison. Somebody’s going to get a crack at the domains you’re visiting, are they not? It seems better to encrypt these queries than to allow a middleman to intercept them.
Regarding override default system settings, is this really a problem? I prefer browsers that give people extra options, and I would find it worse if they suddenly took this option away.