From: gopher-project-bounces+rachael=telefisk.org@lists.alioth.debian.org
       Date: Mon Jul  4 20:21:29 2011
       Subject: Re: [gopher] PyGopherd - PYG and executable help
       
       > > If the reason for the http/gopher gateway is the lack of native gopher
       > > support in the browser, I would think such a gateway would have to
       > > recive its input on port 80 and as such is a part of the httpd stack
       > > and not of the gopherd.
       > 
       > shouldn't such a gateway rather redirect the user to the specific
       > Overbit* project or a short text, which describes how to use the
       > Gopherspace? Showing just the content will not generate any learn-
       > ing effect.
       
       I agree wholeheartedly. I think part of continuing to run Gopher servers
       is to educate a population that has forgotten how to use them.
       
       -- 
       ------------------------------------ personal: http://www.cameronkaiser.com/ --
         Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckaiser@floodgap.com
       -- PRIVACY. IT'S EVERYONE'S BUSINESS. -- Evil, Inc. ---------------------------
       
       _______________________________________________
       Gopher-Project mailing list
       Gopher-Project@lists.alioth.debian.org
       http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project
       Thread start
 (DIR) [gopher] PyGopherd - PYG and executable help
 (DIR) Followup: Re: [gopher] PyGopherd - PYG and executable help