Which setup are you using where you require HTTP and cannot use HTTPS? The mere existence of HTTP endangers users who do not know about its problems, because many links are posted in HTTP version and they just click them.
I use many such setups. But it's not just about me. It's about anyone who can't or doesn't want to. I don't blindly click links and neither should anyone else. If they do this in HTTP, they're going to fall for the ad scams in HTTPS too. I find it hard to feel sorry for people like that. They do this in other areas of life too, I suspect.
I actually found that the site (namely the forum reputation "Rate" button) doesn't work properly when browsing via plain HTTP. Still, I welcome the ability to browse and post without JS and HTTPS, even though I use both 99% of the time.
11-09-2020, 04:23 PM
(This post was last modified: 11-09-2020, 04:31 PM by BronzeBeard.)
jed and fsflover,
Bullet point arguments in favor of allowing HTTP are included in post #11, if you care to read the entire thread before rehashing the same arguments others have already made. Rebuttles to common cited reasons for removing HTTP from everywhere is in post #13.
In short, it's the user's responsibility to use HTTPS. If the user is too stupid to do that, then it's Firefox and Chrome's fault. Websites shouldn't be redirecting your protocol. Your browser should check if HTTPS exists and default to that. Sadly, the popular browsers require a plugin for that functionality.
Content providers should provide their content in any reasonable format they deem cost effective. In HTTP and HTTPS' case, there isn't any administrative costs. Refer to post #11 for reasons why HTTP is still a valid choice for some users.
Anti-HTTPS rhetoric is irrelevant to the thread, not to mention poor security and OpSec practice.
I hope the OP can reach a resolution, this thread's gone off the deep end.
This thread is now closed.