[gopher] Regarding "title" (and other special) informational items [Was: Re: RFC submission?]
On Fri, Jan 2, 2015 at 9:59 AM, Mateusz Viste <mateusz@...> wrote:
> document on piratepad.net looks more like a bag of wishes. Also, it
> describes the usage of some xml-like tags in gopher (title), which by
> itself, is a heresy to me. [...]
Although I tend to agree with Mateusz regarding the simplicity appeal
of the Gopher protocol (at times perhaps too simple), and the fact
that "bolting" new features on-top of the existing protocol (like the
title information items) detracts from this simplicity towards
convoluted specifications and incompatible implementations.
However the title information items, which replace the empty selector
with the "TITLE" selector, made me think a little about how structured
Gopher menus actually are right now...
First of all, is there any Gopher client which actually implements
this title information item feature? Because I've seen it documented
it that RFC proposal I thought so, but Overbite doesn't seem to
so). (BTW `lynx` doesn't even implement `URL:...` selectors...)
Back to the topic of how structured the Gopher menus are, currently
the Gopher menus are technically just a flat list of items with no
differentiation between the various items (except their type).
However if we look at a few Gopher sites, like the ones below
(randomly picked from a list I've once seen), we can easily observe
that the editors do impose a certain structure inside the menus
(especially the "root" menu).