z3bra wrote about [the gophirst approach][z] a while ago. I usually go
by "Lynx first" these days, but I feel like that's not enough.

[z]: gopher://phlog.z3bra.org/0/the-gophirst-approach.txt


Gopher first and then some tool to make the content accessible via
HTTPS, too, sounds really nice. I like the idea of being able to access
my stuff without having to rely on ginormous pieces of software. It's a
bit extremist, sure, because I could also just do this:

-   Turn off the HTTP to HTTPS redirect.

That would allow you to access the web page from very old machines or
manually via telnet(1). The HTML content can actually be read in a text
editor, it's not that terrible. And it shows reasonably well in ancient
browsers.

It's not ideal, though. Nothing beats a plain text file, because that
thing *just works*. And it would be *so* cool to have the web page look
like this:

<https://codevoid.de/>

:)

I would just need to make sure to not break all hyperlinks (again). I
mean, to my surprise at least two blog posts have been cited in
academical work (a bachelor's thesis and master's thesis), which is
pretty nifty, and I don't want to break that.


I'll probably be lazy and just turn off the redirect, once browsers
start to query HTTPS first and then fall back to HTTP. Because, you
know, that's what's going to happen. Firefox already has an HTTPS-only
mode that you can turn on:

<https://bugzilla.mozilla.org/show_bug.cgi?id=1620242>