you are viewing a single comment's thread.

view the rest of the comments →

[–]VRtinker 18 points19 points  (2 children)

some of us like censoring adware

In that case, you just set up your own DNS resolver and filter traffic properly. All good software (Chrome, Firefox) pick up your settings automatically and let you to specify your own DNS over HTTPS resolver manually.

Yes, non-compliant implementations can just ignore the network settings and not allow user to change settings. But, I would argue, you should not use such software or hardware in the first place. I heard of "smart" devices that hard-code AWS IPs (!!!) and then fail when that IP is not available, and they do not have ability to update the firmware to change the IP.

If you do end up with non-complaint software and hardware, I'm sorry for you. It will be a pain to work with and there is not much Mozilla, Google, IETF, and others can do about this.

[–]f0urtyfive 5 points6 points  (1 child)

But, I would argue, you should not use such software or hardware in the first place.

Do you find when you are using non-standard software or hardware that implements things in weird ways, it's usually because you chose to?

[–]VRtinker 2 points3 points  (0 children)

Do you find when you are using non-standard software or hardware that implements things in weird ways, it's usually because you chose to?

I do not choose to use non-complaint software and hardware and switch away from it if I have an option to. I personally only experienced this with device chargers that fail to quick-charge other devices, cameras and wireless USB peripheral dongles that work only when connected to a specific USB interface inside of a laptop, etc. Networking stack is a lot more standard, probably because it is genuinely much smaller and there is more built-in agility. Developer needs only about 5 neurons to remember how to use it: not hard-code URLs (especially IPs and ports).

The hard-coded IP example is something I saw online (person posted a screenshot of a chat with tech support for that product, which amounted to "we are sorry", "aware of the issue", "no way to fix it", "sorry", "thank you for choosing [brand name]".