I have very few memories of Gopher when it was current. It was already on its way out when I started college. The course catalogs and a few other things were available, but not much else, and if they ever offered student gopher space, I don’t remember it. I don’t even remember for sure if the student web space was available my first year or if they added that the second year.

So I missed Gopher’s heyday (such as it was). And I was fully enmeshed in the blogosphere when the gopher revival started. I hadn’t even heard of a “phlog” until I discovered the Gemini Protocol in 2021, and read about how in a way it was a reaction to that Gopher revival, trying to build something that was almost as simple, but with a few key features backported from the web. (Hyperlinks, some very minimal formatting, TLS to prevent eavesdropping, and general user input.)

I got out of Gemini for a while as I focused on my website again, then came back to it (but not as thoroughly). A blog post by Brennan Kenneth Brown, Gemini, Gophers and Fingers, Oh My! got me thinking about Gopher again.

And then I got stopped by the most trivial stumbling block ever: Naming. I felt like I needed to set up a Gopher presence before really diving in. And I wanted to just use my domain name like I do with my website and Gemini capsule…but Gopher listens on a protected port. That means I can’t run a server in the userspace on my webhost. I have to run it on something I have root access to (or else let someone else manage the software, which I probably should’ve started with). And the idea of typing this:

	gopher gopher://gopher.kvibber.com

just seemed absurd.

(Then again, maybe it’s not that trivial. There’s a reason for the classic phrase about the only really hard problems in computing being naming things and cache invalidation. And off-by-one errors.)

Eventually I got around to asking on the Fediverse, a place with a large population of Old Internet People like myself (and older): What naming conventions did people use for Gopher sites back then?

The consensus was that most sites just used a gopher prefix.

Though I did contemplate some sort of pun like pocket or botta (as in Botta’s Pocket Gopher, the most common one I see here in the Los Angeles area according to the rare photo I catch and post to iNaturalist).

Anyway, a follow-up to Brown’s post the other day prompted me to just build something.

I pointed gopher.kvibber.com to one of my VPSes, picked a reasonably current (by Gopher standards) piece of server software (Gophernicus, latest release 2020), and promptly discovered that not only is Gophernicus not available directly in Alpine Linux, but it relies on a system network listener (inetd, xinetd, systemd), and Alpine doesn’t install any of those by default. So
I figured out how to get inetd running on Alpine, built Gophernicus and started it up.

I’ve pulled in a few pages from my Gemini capsule to start with. And now that I have that place to start, I feel like going exploring.

Originally posted on gopher.kvibber.com.