@aearil I have very important needs regarding bad faith
@wxcafe Interestingly, n-gate doesn't seem to support https.
@tyil doesn't matter?
@wxcafe Maybe if security doesn't matter to you. Especially given how easy and cost-free it is to set up these days.
@tyil ain’t no point in setting up https for a static site with no exchange of information. Literally who cares.
@wxcafe HTML is information, and the purpose of HTTP is to exchange it.
Anyone intercepting the connection at any point can still inject stuff (like scripts), even if the original host only provides static content. And anyone can still read out the entire message and use it for personal/meta data harvesting.
Anyone understanding what the words "information", "exchange" and "security" mean would care.
@tyil oh piss off
After all it is the authors decision not to do it. Can not really blame someone for that. If he doesn't know better: educate him.
If you really cared for "security" in that context you should try to get a cert fingerprint in-person from the author/admin. The certificate authority system is broken anyway...
@andi @tyil look, I know. I have TLS everywhere. I used to have self-signed certs everywhere before LE came along. I have a yubikey to store my gpg key. I do totp 2fa on ssh logins. I get crypto. But I also get that some things are not worth tls-ing, and that who the fuck gives a shit. It’s literally not a problem for anyone. It’lol be flagged as insecure by browsers soon and they’ll probably upgrade then. It’s fine, calm down, stop telling strangers on the internet.
@wxcafe this is why I ultimately don't like n-gate
they're contrarian to *everything*, virtually no exceptions, and it gets old and depressing after a while. I don't want to see that much shit consistently week after week, even if some of it is funny.
But it would prevent certain attacks for next to no cost. This faulty concept that some people have that plain-text sites are somehow secure by default is harmful to propagate, and I'd rather people not do that. Which is why I tried to explain that part.
Just as there's no magic bullet for security, nor should anything be assumed as default secure, one can't be dogmatic in telling a total strangers what their threat model or cost/benefit is.
I've seen lots of people introduce new security holes trying to make TLS work in their environment. LE made it soooo much easier, but in shared environments (i.e. most hosting), TLS is still non-trivial.
@nickfarr I agree with you, don't get me wrong.
I just wanted to clear up to that person that static pages aren't "secure" any more than other pages. In reality, all content transmitted over HTTP are static pages.