It is why software needs support to (optionally, if configured by the user) do such things as non-tunneling proxies for HTTPS. (There are other problems too, wh

It is why software needs support to (optionally, if configured by the user) do such things as non-tunneling proxies for HTTPS. (There are other problems too, which can be solved by other changes to the software. Not all of them have to do with HTTPS, though.) Neither HTTPS or other protocols prevent whatever service you are using from using it badly, or from malware in the client or server side. Just because it is HTTPS does not necessarily mean that it is desirable. I currently do not have any TLS server in my computer, although I intend that I may later add it as an option (but without redirecting; if it is implemented, both the TLS and non-TLS will remain available). However, some of my projects are mirrored on the Chisel fossil hosting which allows both TLS and non-TLS to connect. (And, in the case of obscured data, even if the protocol isn't encrypted the program might make its own encryption, and disabling TLS (even if you have the opportunity to do so) won't help.)