Nonsense. End users have the power to configure their browsers just like they have the power to configure their DNS settings, their operating system and all the rest. Of course very few people do. Mostly that power requires something most users don't have: which is knowledge to know they need to do this and how to do this. The people actually capable of doing this lose no power whatsoever.
You seem to not trust Google. Nobody is saying you should or must. Other DNS servers are available. Set up your own one if you must. You have that power. If you are smart enough to actually know how to set up DNS now, you should be able to figure out how to configure that to use https. It's not rocket science.
If not, maybe it's a good thing that your browser stops blasting your DNS queries unencrypted over a public network to absolutely anybody that can be bothered to listen in. This would include all the 3 letter acronym security agencies that you can name (domestic and foreign ones), big ad driven companies, your local police, and everybody else with or without the cooperation from your friendly neighborhood operators or arm twisting of the incompetent politicians representing which ever government is governing wherever you live. The best you can hope for to protect you from that is a combination of incompetence and indifference.
> Nonsense. End users have the power to configure their browsers just like they have the power to configure their DNS settings, their operating system and all the rest.
This power is illusory. If Google decides Chrome will no longer allow changing DNS providers, game over for 60% of internet users. Consider how it's no longer possible to block ads the way you want to in Chrome with manifest 3.
True - but I think this is not the fault of DoH or IETF. On a technical level, the power stems from Google's ability to auto-update Chrome with whatever logic they see fit. On a social level, maybe Chrome's market share and the acceptance of users of that power.
Even without DoH, Google could just as easily have decided to hardwire DNS for Chrome to 8.8.8.8 or to switch Chrome to their own home-grown proprietary name resolution protocol. They don't need a public standard for that.
>Nonsense. End users have the power to configure their browsers just like they have the power to configure their DNS settings, their operating system and all the rest.
It is already not possible to avoid DoH to Google servers with chromecast
> Of course very few people do. Mostly that power requires something most users don't have: which is knowledge to know they need to do this and how to do this.
Yes, which means that effectively they don't have the power.
You seem to not trust Google. Nobody is saying you should or must. Other DNS servers are available. Set up your own one if you must. You have that power. If you are smart enough to actually know how to set up DNS now, you should be able to figure out how to configure that to use https. It's not rocket science.
If not, maybe it's a good thing that your browser stops blasting your DNS queries unencrypted over a public network to absolutely anybody that can be bothered to listen in. This would include all the 3 letter acronym security agencies that you can name (domestic and foreign ones), big ad driven companies, your local police, and everybody else with or without the cooperation from your friendly neighborhood operators or arm twisting of the incompetent politicians representing which ever government is governing wherever you live. The best you can hope for to protect you from that is a combination of incompetence and indifference.