21yo plural autism, trans girl, professional internet weirdo, late blooming theater kid, video editor, occasional musicker, voice actress in progress, still learning about stuff
emily subsystem will probably be main posters
π - goatmily / emily delta
π - catmily / emily tau
πͺ - omicron(?)
π - josie/piece (@pieceofjosie)
π¦ - alex
π - soleil
πͺ - marisa (@marisakirisame)
π₯οΈ - EMI (@exe-cute-able)
and many more...
my website usually redirects you to a secure connection, but...
I've configured it so you can avoid the redirect by going to http.moonbase.lgbt β enabling support for vintage browsers that can't do modern TLS!
If you wanna set something like this up for yourself, obviously I don't know how to set it up in every webserver, but if you're using Caddy like I do, the Caddyfile config looks like this:
moonbase.lgbt,
http://http.moonbase.lgbt {
... site configuration goes in here ...
}
Now that's retro! (And here I am, trying to add TLS to Telnet. Needs moar retro >_<)
should figure out how to do it in nginx since i purposely designed my site with the look and feel of that era
is there a reason why one would expose http on a subdomain rather than just foregoing the redirect to https? the only reason i can come up with is that it makes it harder to accidentally use http without knowing
it's mostly just vibes but i'd rather it be secure-by-default and have using an insecure connection be an explicit opt-in
what's your opinion on redirecting to https iff the client sends an upgrade-insecure-requests header? it's sent by all modern browsers, but admitedly could be stripped away by a MITM. then again, a MITM could just redirect your request somewhere else entirely
honestly I think that's probably the ideal way to do it and I wasn't aware of it when I set this up originally, the only thing stopping me from doing it that way is having to figure out how to override Caddy's default redirection behavior
