From: "Gopher-Project" <gopher-project-bounces+rachael=telefisk.org@lists.alioth.debian.org> Date: Tue Jun 16 01:06:34 2015 Subject: Re: [gopher] Gopherpedia is officially broken --===============2832831674596933767== Content-Type: multipart/alternative; boundary="----WP0MQUARGQWOQBZBMY0POLC1II6RSV" Content-Transfer-Encoding: 8bit ------WP0MQUARGQWOQBZBMY0POLC1II6RSV Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset=UTF-8 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: >I'm glad Its back up and runninng! thx colin. >btw do you take requests for features? > >I was wondering if you'd like to add inline selectors for images? > >From: kevin@veroneau.net >Date: Mon, 15 Jun 2015 14:53:53 -0600 >To: gopher-project@lists.alioth.debian.org >Subject: Re: [gopher] Gopherpedia is officially broken > >Happy days are among us once again. :) I guess it was an API change on >their part? > >On June 15, 2015 2:25:34 PM MDT, Colin Mitchell ><muffinista+gopher@gmail.com> wrote: >Fixed, thanks for pointing it out! >On Mon, Jun 15, 2015 at 4:20 PM, Colin Mitchell ><muffinista+gopher@gmail.com> wrote: >Working on it now :-/ >On Mon, Jun 15, 2015 at 3:48 PM, Kevin Veroneau <kevin@veroneau.net> >wrote: >It is indeed a sad day for Gopher, as one of the most widely used >gopher sites is dead. Hopefully Muffinlabs can spring into action with >a fix, so that us Gopherites can ge > t our >Wikipedia fix in plain text once again. Until that glorious day, I >guess we'll need to get our fix using the legacy HTTP protocol method. > >-- > >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 > > > > > >Gopher-Project mailing list >Gopher-Project@lists.alioth.debian.org >http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project > >-- > >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 > > >------------------------------------------------------------------------ > >_______________________________________________ >Gopher-Project mailing list >Gopher-Project@lists.alioth.debian.org >http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project -- Sent from my Android device with K-9 Mail. Please excuse my brevity. ------WP0MQUARGQWOQBZBMY0POLC1II6RSV Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit <html><head><style><!-- .hmmessage P { margin:0px; padding:0px } body.hmmessage { font-size: 12pt; font-family:Calibri } --></style></head><body class="hmmessage">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.<br> <br> 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?<br> <br> 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.<br> <br> 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...<br> <br> gopher://<a href="http://gopherpedia.com/0/KISS">gopherpedia.com/0/KISS</a> principle<br> <br><br><div class="gmail_quote">On June 15, 2015 4:26:17 PM MDT, "barana ." <barana24@hotmail.com> wrote:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;"> <div dir="ltr">I'm glad Its back up and runninng! thx colin.<br />btw do you take requests for features?<br /><br />I was wondering if you'd like to add inline selectors for images?<br /><br /><div><hr id="stopSpelling" />From: kevin@veroneau.net<br />Date: Mon, 15 Jun 2015 14:53:53 -0600<br />To: gopher-project@lists.alioth.debian.org<br />Subject: Re: [gopher] Gopherpedia is officially broken<br /><br />Happy days are among us once again. :) I guess it was an API change on their part?<br /><br /><div class="ecxgmail_quote">On June 15, 2015 2:25:34 PM MDT, Colin Mitchell <muffinista+gopher@gmail.com> wrote:<blockquote class="ecxgmail_quote" style="border-left:1px solid rgb(204, 204, 204);padding-left:1ex;"> <div dir="ltr">Fixed, thanks for pointing it out!</div><div class="ecxgmail_extra"><br /><div class="ecxgmail_quote">On Mon, Jun 15, 2015 at 4:20 PM, Colin Mitchell <span dir="ltr"><<a href="mailto:muffinista+gopher@gmail.com" target="_blank">muffinista+gopher@gmail.com</a>></span> wrote:<br /><blockquote class="ecxgmail_quote" style="border-left:1px #ccc solid;padding-left:1ex;"><div dir="ltr">Working on it now :-/</div><div class="ecxgmail_extra"><br /><div class="ecxgmail_quote"><div><div class="h5">On Mon, Jun 15, 2015 at 3:48 PM, Kevin Veroneau <span dir="ltr"><<a href="mailto:kevin@veroneau.net" target="_blank">kevin@veroneau.net</a>></span> wrote:<br /></div></div><blockquote class="ecxgmail_quote" style="border-left:1px #ccc solid;padding-left:1ex;"><div><div class="h5">It is indeed a sad day for Gopher, as one of the most widely used gopher sites is dead. Hopefully Muffinlabs can spring into action with a fix, so that us Gopherites can ge t our Wikipedia fix in plain text once again. Until that glorious day, I guess we'll need to get our fix using the legacy HTTP protocol method.<span><font color="#888888"><br /> -- <br /> Sent from my Android device with K-9 Mail. Please excuse my brevity.</font></span><br /></div></div>_______________________________________________<br /> Gopher-Project mailing list<br /> <a href="mailto:Gopher-Project@lists.alioth.debian.org" target="_blank">Gopher-Project@lists.alioth.debian.org</a><br /> <a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project" rel="noreferrer" target="_blank">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project</a><br /></blockquote></div><br /></div> </blockquote></div><br /></div> <p style="border-bottom:1px solid #000;"></p><pre class="ecxk9mail"><hr /><br />Gopher-Project mailing list<br />Gopher-Project@lists.alioth.debian.org<br /><a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project" target="_blank">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project</a></pre></blockquote></div><br /></div></div></blockquote></div><br> -- <br> Sent from my Android device with K-9 Mail. Please excuse my brevity.</body></html> ------WP0MQUARGQWOQBZBMY0POLC1II6RSV-- --===============2832831674596933767== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Gopher-Project mailing list Gopher-Project@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project --===============2832831674596933767==-- Thread start (DIR) [gopher] Gopherpedia is officially broken (DIR) Followup: Re: [gopher] Gopherpedia is officially broken