| I personally like the article pages the way they are formatted as Gopher type 0. I find it really weird when Gopherholes use Gopher type 1 for articles, then litter it full of gopher menu items. It's really messy and breaks the simplicity of the Gopher protocol. It can also add some interesting issues for gopher clients that display text items differently than menu items. For example, my XBMC gopher client is written to take advantage of the XBMC interface. So menus are shown as XBMC directory views, and text files are shown as... text files. Which makes gopher look like it was meant to run on XBMC. I'm sure other specialized clients like GopherVR and GopherFS will equally have issues with these. Let alone trying to download a text document locally or even browsing through raw telnet. There is a clear distinction between "menu type" and "text type" in the gopher protocol specification. Can we all at least keep that part of the protocol alive? I would however like it if assets were available too, but in the proper gopher manner. Say each article is a menu type. The first item should link to the pure text representation keeping the current look and feel. Below that menu item could be links to each image in the article, then perhaps links to the "See Also" references. In fact, I'd rather links to "See Also" over images. I browse via Gopher to avoid seeing pages like Pintrest which are overly cluttered in images. We're here because we love text and the Gopher protocol, not because we want to transform gopher into the next HTTP/HTML. Unlike HTTP, gopher is fully KISS compliant... gopher://gopherpedia.com/0/KISS principle On June 15, 2015 4:26:17 PM MDT, "barana ." <barana24@hotmail.com> wrote:
-- Sent from my Android device with K-9 Mail. Please excuse my brevity. |
_______________________________________________ Gopher-Project mailing list Gopher-Project@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project