wow HTTPS sure makes swapping servers around less fun. combined with the DNS lag I also have to make sure the certs get moved properly or people will get invalid certs. fun.
part of my problem with modern web development is that OBVIOUSLY everything should be HTTPS and the latest TLS and everything to avoid security issues, but I'm a retrocomputerist and I'm still like "but then my site won't work on Netscape 4.0! ;_;"
@foone@digipres.club I mean I don't necessarily agree that everything should be HTTPS. If you don't handle privacy-related info or user logins... why should it?
@LuigiDev@foone hardly anyone has one site per ip. DNS is aggressivly encrypted in the largest browser. Moves also afoot to scramble sub domains at resolver level
@falken@LuigiDev@foone The hostname is typically exposed by TLS Server Name Indication, which in turn is required to support per-vhost (as opposed to per-IP-address) certs.
@falken@LuigiDev@foone If by “all” you mean “the one latest version, and then only if you don’t advertise any compatibility with any older version”, then yes. :-)
@vjon@LuigiDev@foone death of IE and rise of evergreen browsers with own DNS (including over HTTPS) and networking stacks helps massively with adoption.
CleverLibre Social is an inclusive social instance for open discussion, learning, and community.
All cultures welcome.
Hate speech and harassment strictly forbidden.
@falken@qoto.org @foone@digipres.club hostname is not really hidden anyway. Since DNS is not always protected and even then IP is always visible