Just as the title says, I’ve had to re-enable mandatory HTTPS on this website. I didn’t want to, I’d rather have let the site be reasonably accessible from older computers lacking modern encryption, but at this stage, given how things are with the internet on a whole this just wasn’t feasible.
The problem I was experiencing was one of ambiguous log-in status. That is to say, I could log in, click a few links and, because HTTPS would randomly be active or inactive on a given page my login would be, basically, nullified. That is to say, it would look like I was logged in, and technically I was, but the second I loaded up one of these other pages that was it – everything that being logged in provided me as far as actually publishing or editing content would break. It’s made publishing the past few months actually a special kind of hell.
Believe me, when you can’t even load up a new page without being scared you’ll break everything you’re working on, it’s pretty bad, and while it had recently gotten better, today I reached a point where I literally couldn’t edit anything if I even tried to load a page to edit.
What’s the point then?
Look, I’d really like for text only browsers on computers from the early 90’s to be able to view my writings on this site. Really, I would. I’d love for someone to fire up Classilla on a PowerMac G3 and see if the site will load. It just ain’t happening, though, not without too much hassle on my end.
Then again there was so much content linked here like Twitter threads and YouTube comments that it really doesn’t matter – that’s the stuff that caused many of the problems to begin with, I think, so… what can ya do?
Ah well, it isn’t all bad. I still have a gopherspace and my BBS. You can access those on pretty much anything, if you’re tech savvy enough. 😉
