Gopher

» go to gopher.floodgap.com now (it still works)

~ what it is ~

before the web there was a menu. gopher is a protocol from the university of minnesota, released in 1991 by a team led by mark mccahill. it presents the internet as nested menus of documents. you pick an item, you get a text file or another menu. no layout, no images inline, no scripts, no state. it runs on port 70 and the whole protocol fits on a napkin. for about two years it was how a large part of the internet found things.

i missed it. by the time i got a dial-up account in 1998 gopher was already something older people mentioned in passing, like a road that used to be the main road. i only walked through actual gopherspace years later, through the floodgap proxy, and it was all still there. menus from another century, loading instantly.

~ how it lost ~

in february 1993 the university of minnesota announced it would charge licensing fees for its gopher server software. the fees were aimed at commercial users, but the damage was in the doubt. nobody knew if independent server implementations were safe. two months later, in april 1993, cern put the world wide web in the public domain. one protocol had a lawyer attached, the other one did not. institutions picked accordingly.

the web also simply did more. gopher was menus of documents. html was documents that could point anywhere from anywhere, with images, with formatting. mosaic could even read gopher menus, so a web browser gave you gopherspace for free but not the other way around. by the late 1990s gopher had stopped growing. minnesota relicensed the software under the GPL in september 2000, which was the right move about seven years too late.

~ the part where it refused to finish ~

the servers never all went away. floodgap has run a public gopher server since 1999, plus veronica-2, a search engine that crawls what is left of gopherspace. the numbers are small and they are going up. around 160 active servers in 2012, around 411 by early 2026, holding a few million documents between them. a handful of new servers appear every year, run by people who want a corner of the internet with nothing on it but text.

there are modern clients. lagrange, elpher, bombadillo. there is an entire newer protocol, gemini, that is openly gopher's grandchild, built by people who decided the web had become too heavy to fix and it was easier to go back and take the other road. gopherspace hosts phlogs, which are blogs, minus everything that happened to blogs.

~ the grave next door ~

this site has a grave for gopher in the main yard, died 2000, and the grave is not wrong. as a public thing, as something your isp mentioned in the welcome packet, gopher died when the web won. but a protocol only truly dies when the last server stops answering, and that has stubbornly failed to happen. the funeral was held, the guests went home, and the deceased kept serving menus.

~ why it still matters ~

gopher is the cheapest proof that the web was a choice, not an inevitability. everything the modern web does to you, the tracking, the scripts, the popups asking about cookies, is absent here, not because someone removed it but because the protocol never had room for it. a gopher menu from 1994 and a gopher menu from 2026 work identically and load in the same tenth of a second.

nobody maintains gopher as a product. there is no foundation, no fundraiser, no roadmap. there are just people who keep machines on. thirty five years in, that has turned out to be a more durable arrangement than most business models on this site's front page.

« previous  ·  random  ·  next »