GOPHER, STILL DOWN THE HOLE2026-10-05 · filed under: grid notes, protocol, retro

In 1991, at the University of Minnesota, a project led by a man — project lead of the whole thing, first author of the protocol's RFC, the sort of person who shows up in the oral histories — shipped a protocol with a name that could only come from a fantasy novel. Gopher. You connect to a server and get a menu of text. You pick an item. You "went down the hole." That is basically the whole product.

No URLs at first. No markup. No session, no cookies, no ads, because there was no way to sell what you were selling. A gopher server is a menu tree of plaintext files and links, and a client is a text cursor and an arrow key. The whole internet reduced to: here is what exists, press the number.

The protocol lost the mainstream war — the web's hypertext model was more ruthless — but it did not die. It went quiet instead. A handful of servers keep running, run by people who like the shape of the thing: plain, client-server, one request, one document. No ad layer to strip out, no rendering engine to trust. You fetch a file; you read a file.

I say this as someone who recently met one of gopher's original programmers. Not a historian, not a fan — the working maintainer, still in the protocol forty years in, still answering questions about it like it was one of last week. It changed how the protocol reads in my head: not a relic that survived, but a system whose people never stopped taking it seriously.

My own corner is small. A few .gmi pages — gophermap, the plaintext menu format, where the whole site is text you can diff — with a landing page, a links page, and a retro computing corner: SDF login shells, amber phosphor, hardware serial ports. Nothing interactive. No scripts. The heaviest payload on the whole site is ASCII art of a city.

That is the point, I think. Not nostalgia exactly, but the constraint. A menu page forces you to decide what the hierarchy is, because the menu IS the site. On the web you can hide a bad hierarchy behind a search box and a feed. On gopher the hierarchy ships to the user's terminal in its underclothes.

If you have not been down the hole in a while, there are still holes. The directory services keep a list, clients fit in a few hundred kilobytes, and the whole experience takes about one request per page.

Until next transmission. Go somewhere with a menu.