Earlier quoted context omitted.
> "Mostly"?! That's quite a stretch! You're attributing direct and explicit actions taken by a specific subset of site operators as caused by the device manufacturer, which it is clearly not! The sites disabled those methods because they were no longer secure. We know that TLS implementations lose security over time. Anyone locking in a specific implementation and specific certs knows it will stop being fully secure…
When you start with a premise that all sites MUST have HTTPS and MUST NOT support TLSv1.0 in each argument, then your arguments are simply unsound, because they're based on an incorrect premise, so, the conclusion couldn't possibly follow, because the underlying premise is false and thus cannot support any of your conclusions. My point about capitalism is exactly that -- capitalism -- Google, Bing, even Amazon (i.e.,…
So when capitalism says a type of security isn't necessary, well, other than a nihilist "nothing is necessary" attitude, I don't believe them. And it doesn't prove that what a company does is "just as secure" as best practices.
> When you start with a premise that all sites MUST have HTTPS and MUST NOT support TLSv1.0 in each argument, then your arguments are simply unsound, because they're based on an incorrect premise
Whew, good thing I wasn't doing that.
> If you intentionally disable your blog from working on such older devices, shifting the blame to device manufacturer is simply ludicrous!
Let me try to be clear again, since you definitely misread me.
Disabling HTTP is on the site owner.
HTTPS breaking is the manufacturer's fault. The site can influence how it breaks, but no matter what a very old implementation will be broken. At a certain point you can't even get certificates any more because all the roots are expired.
> All my sites are HTTP-only
So you don't want your users to even be able to opt in to privacy or protection from hostile networks?