💾 Archived View for mozz.us › journal › 2021-05-27.gmi captured on 2021-12-03 at 14:04:38. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2021-11-30)
-=-=-=-=-=-=-
Published 2021-05-27
The "i" type is probably most pivotal contribution to the gopher protocol made from outside of the original UMN gopher team. The "i" type allows plain text to mingle alongside links to files in gopher directories. It transforms a gopher directory from what was originally a "bag-of-links" style listing ala FTP into a true hypertext document. The "i" type is now ubiquitous in modern gopherspace and is an absolute minimum requirement for any new gopher client.
However, there's a school of thought among gopher purists that the "i" type is an abuse of gopher's original design philosophy. The feeling is that gopher was designed to have menus and documents, and the two should remain separate. So instead of tacking an ASCII banner and a short blurb at the top of your root gopher menu, stick it in a text file named "ABOUT". Instead of tacking a text description above a link in your gopher menu, put that description properly in the link's metadata using the gopher+ abstract field.
The cool thing about the above is that it allows for a whole class of client interaction that's just not possible with hypertext. Like directly mounting a gopher hole as a filesystem using FUSE. Or allowing clients to sort a gopher menu in alphabetical order or hide certain file types. This was no doubt the direction that the UMN gopher team was oriented, and they doubled down on this with the creation of gopher+ and gopherVR. In fact, "i" selectors break the whole concept of gopherVR terribly which is a shame.
Regardless, the "i" type became hugely popular with the gopher revival in the 2000's, and that's we're at today. However, I was curious about where this selector came from. Who invented it? It's not mentioned anywhere in RFC 1436. It's listed as an "unofficial" type on the wikipedia page with no further clarification. So I did some digging on my own...
The best resource that I have found for gopher history is old usenet archives:
These were both fairly active from around '92 to '95. After that, there was a dead period in gopher history until the gopher-project mailing list was started up in 2000.
For reference, the gopher protocol was invented in (late?) '91 and RFC 1436 was published in March '93.
RFC 1436 - The Internet Gopher Protocol
Here's the alt.gopher FAQ from June '92, which lists all of the known gopher link types. The "i" selector is nowhere to be found yet.
(An interesting aside, the only one of these "experimental" IDs to make it into RFC 1436 is "I")
Q9: What are the type characters for the different Gopher Objects? A9: Normal IDs. 0 Item is a file 1 Item is a directory 2 Item is a CSO (qi) phone-book server 3 Error 4 Item is a BinHexed Macintosh file. 5 Item is DOS binary archive of some sort. 6 Item is a UNIX uuencoded file. 7 Item is an Index-Search server. 8 Item points to a text-based telnet session. 9 Item is a binary file! Client must read until the connection closes. Beware. T TN3270 connection. Experimental IDs. s Sound type. Data stream is a mulaw sound. M MIME type. Item contains MIME data. h html type. I Image type.
Here's the FAQ from September '92, just 3 months later.
There's the "i" type"! But what the heck is panda???
<snip> Experimental IDs. s Sound type. Data stream is a mulaw sound. g GIF type. M MIME type. Item contains MIME data. h html type. I Image type. i "inline" text type (used by panda).
So it turns out that Panda was a fork of gopher created by the University of Iowa to provide student internet services. It integrated gopher, usenet, FTP, WWW, and more. I found an announcement email (definitely worth a read!), and in it they describe several changes to their "souped up" gopher client. One of which is...
Ability to add informational text to the tops of menus. This makes menus look a *lot* nicer and are much more readable than plain menus. See the sample screen later in this note.
The "i" type isn't called out by name, but it's clear that this is what's being referred to here. Later on in the email, there's a screenshot. This is probably the first recorded screenshot showing custom "info" at the top of a gopher menu!
An interesting side-note, they're wrapping at 80 characters instead of the 70 which was later mandated in RFC 1436. The client in this screenshot appears very well designed and intuitive, IMO.
----------------------------------------------------------------------------- > Page: 1 of 1 University of Iowa Panda (v. 0.8) > > Passport: News & Information for Foreign Students and Scholars > > This is the May edition of Passport, the newsletter for the Office of > International Education and Services (OIES). You can go directly to this > menu by typing "go passport" at any Command=> prompt. > > --> 1. About Passport > 2. Current News > 3. Information About Immigration... > 4. Calendar of Upcoming Events > 5. Employment Opportunities for Graduates > 6. Financial Aid > 7. Off-Campus Educational Opportunities > 8. Nationality Organization Officers > 9. Health Information... > 10. Feature Stories with an International Theme > > > Command==> > ?-Help Up-Prev. Menu > -----------------------------------------------------------------------------
[alt.gopher] Panda Announcement
So it looks like Lee Brintle gets credit for the Panda project and thus inventing the "i" selector.
Panda was also presented by University of Iowa at the very first GopherCon. This was only a couple weeks before the gopher FAQ was updated to include the line about the "i" item type, so the timeline matches up.
Lee Brintle from the University of Iowa's "panda" project talked about some of their extensive modifications to Gopher: printer selection, remote updating of files by data maintainers, scripting (a forth-based interpreter in the client to allow massaging of input to and output from complex servers such as the geography server), grep-like searching of non-WAISified data, and search by title on the current level (a la rn and elm). Panda has evolved into an entirely different animal from Gopher (for starters, it is written in C++) and it is not clear which of these enhancements may make it back to the mainstream. The one Panda feature which seemed to gain everyone's approval was the ability to put explanatory text at the top and/or bottom of the screen rather than in an "About" file.
Emphasis on...
The one Panda feature which seemed to gain everyone's approval was the ability to put explanatory text at the top and/or bottom of the screen rather than in an "About" file.
Dope.
From what I can tell, not much happened after that. There was no immediate widespread adoption of the "i" type. I suspect this is because the UMN gopher client and server resisted adding the "i" item type to their software, which was the dominant server/client among the community. The gopher team went their separate direction with gopher+ and gopherVR which didn't fit with the "i" type methodology.
I hope to eventually find more information from this time period. How widely was the info type used in '92 and '93? Why was it ignored by the UMN gopher team and later omitted from RFC 1436?
Later on, I found a question posed to the gopher newsgroup in '94 about the fate of gopher's experimental i type.
comp.infosystems.gopher - Clients that support type "i"?
Early on, the University of Iowa devised an extension to the Gopher0 protocol whereby type "i" denotes a piece of inline annotation. I've heard tell that U Mn intends to embrace this extension. Has anyone compiled a list of clients that already support type "i"? Hgopher seems to. Is anything else up to speed?
There was a response from Lee Brintle, the creator of Panda himself.
After the last FAQ, I mailed the Gopher folks about the still-experimental status of the "i" type, and they indicated that it would be moved into the "official" section.
And then a confirmation from Neophytos Iacovou at the UMN Distributed Computing Services.
Yup, that's true.
It looks like this corresponds with the UMN gopher client finally accepting the "i" type in their software.
Since no one else has mentioned it yet, i'll throw in that the last few versions of UMinn's Unix gopher+ client support the "i" type.
Annoyingly, shortly after the last email in April '94 the gopher team stopped posting updates of the gopher FAQ directly to the newsgroup. Instead, they linked to a copy of the gopher FAQ on a long dead FTP server. This is around the time that the UMN gopher team dissolved and the group traffic started to die down.
Fortunately I found one last version of the gopher FAQ posted by Paul Linden on Dec '94. In this version they dropped the "Official" and "Experimental" labels and posted everything in one big list of "known/used" gopher types.
I have no choice but to interpret this as one last jab by the UMN team to refuse making "i" an official gopher type.
Q9: What are the type characters for the different Gopher Objects? A9: The following is a list of known/used Gopher types 0 Item is a file 1 Item is a directory 2 Item is a CSO (qi) phone-book server 3 Error 4 Item is a BinHexed Macintosh file. 5 Item is DOS binary archive of some sort. 6 Item is a UNIX uuencoded file. 7 Item is an Index-Search server. 8 Item points to a text-based telnet session. 9 Item is a binary file T TN3270 connection. s Sound type. Data stream is a mulaw sound. g GIF type. M MIME type. Item contains MIME data. h html type. I Image type. i "inline" text type
The end.