[gopher] Gopher-Project Digest, Vol 45, Issue 4

Thu Sep 19 21:20:54 UTC 2013

This is really impressive good job!
This makes a lot of sense, too.
This is much more clear than Wikipedia.
Next step is to try it with Lynx and see how it looks.
Great addition to the community, I wonder if something like this could be
implemented for most popular sites.

On Thu, Sep 19, 2013 at 4:48 PM, <
gopher-project-request at lists.alioth.debian.org> wrote:

> Send Gopher-Project mailing list submissions to
>         gopher-project at lists.alioth.debian.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
>
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project
>
> or, via email, send a message with subject or body 'help' to
>         gopher-project-request at lists.alioth.debian.org
>
> You can reach the person managing the list at
>         gopher-project-owner at lists.alioth.debian.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of Gopher-Project digest..."
>
> Today's Topics:
>
>    1.  Announcing gopherpedia.com (Colin Mitchell)
>    2. Re:  Joining in: I'm the maintainer/host of Gopher Proxy
>       (Kyle Hooks)
>    3. Re:  Joining in: I'm the maintainer/host of Gopher Proxy
>       (Bradley D. Thornton)
>    4. Re:  Announcing gopherpedia.com (chals)
>    5. Re:  Announcing gopherpedia.com (Jacob Dahl Pind)
>
>
> ---------- Forwarded message ----------
> From: Colin Mitchell <muffinista+gopher at gmail.com>
> To: gopher-project at lists.alioth.debian.org
> Cc:
> Date: Sat, 31 Aug 2013 21:49:22 -0400
> Subject: [gopher] Announcing gopherpedia.com
> Hello All, I thought some of you would be interested in a project I
> launched a few months ago - gopherpedia, a mirror of wikipedia in
> gopherspace. It's accessible on port 70 at gopherpedia.com, or via
> proxy server at http://gopherpedia.com/
>
> The data is searchable, and there's a list of recent searches on the
> front page, along with a mirror of Wikipedia's featured daily content.
>
> This is definitely a work in progress with some kinks and rough edges.
> To implement the site, I wrote a custom gopher server in ruby as well
> as a PHP proxy server, both of which are available on github:
>
> https://github.com/muffinista/gopher2000
> https://github.com/muffinista/gophper-proxy
>
> The data is a little stale because dealing with wikipedia dumps is a
> challenging and time-consuming process, but I will probably try and
> keep it reasonably up to date. There's also the occasional place where
> my parsing of wikitext isn't quite working.
>
> I have fond memories of using gopher in the early days of my life on
> the internet, so this was both a fun learning exercise, and a chance
> to revisit those early adventures.
>
> Thanks!
>
>
> --
> Colin Mitchell
> http://muffinlabs.com/
> This is my signature
>
>
>
>
> ---------- Forwarded message ----------
> From: "Kyle Hooks" <kthprog at gmail.com>
> To: "'Gopher Project Discussion'" <gopher-project at lists.alioth.debian.org>
> Cc:
> Date: Fri, 13 Sep 2013 08:41:53 -0400
> Subject: Re: [gopher] Joining in: I'm the maintainer/host of Gopher Proxy
> I think we might be better off seeing if we can contribute GOPHER
> protocol compatibility code to the Firefox codebase, or try to
> convince them to ship it with a plug-in preinstalled.
>
> -----Original Message-----
> From: Bradley D. Thornton [mailto:Bradley at NorthTech.US]
> Sent: Friday, September 13, 2013 8:02 AM
> To: Gopher Project Discussion
> Subject: Re: [gopher] Joining in: I'm the maintainer/host of
> Gopher Proxy
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
>
>
>
> On 09/13/2013 01:33 AM, Kim Holviala wrote:
> > On Sep 12, 2013, at 16:18, Evert Meulie <evert at meulie.net>
> wrote:
> >
> >> Hi all,
> >>
> >> http://gopherproxy.org/ & http://gopherproxy.meulie.net/
> allows Gopher content to be viewed in any web browser, by
> converting Gopher content into web pages as you request it.
> >>
> >> And yes, currently there is little/no means in place to keep
> bots & search engines out.
> >> I've been reading a bit what has been written here in other
> threads on this subject, and will chime in with my 2¢ soon.
> >
> > Personally I don't mind that Google and others crawl through my
> gopher resources, but I think quite a lot of people here object
> to that. I think the easiest way would be to just have a
> robots.txt to completely block all spidering.
>
> I'm one of those who object - not to gopher spiders indexing
> resources, but any access to my resources via http. If I wanted
> web browsers using hypertext transfer protocol browsing through
> my resources then I would put them on webservers - which I
> already do for other resources.
>
> This has come up before, and I was shot down by the community for
> considering the blocking of all proxy servers. Many people here
> felt that any form of indexing or access to gopher resources by
> any foreign protocol was better than not being indexed or
> accessed at all, and I disagree, at least where my resources are
> concerned, especially since I maintain unique content only
> available via gopher:// protocol.
>
> It's not for me to decide what others opinions are, but I for one
> am of the mind that if someone can surf gopher resources via
> http:// then there is no point in gopher:// at all.
>
> As far as robots.txt is concerned, my feeling is that this is a
> http standard, and not a gopher standard, so there should be some
> other way to limit indexing of gopher resources for those who
> choose to do so. I do not choose to block such indexing, and
> welcome it, just not via a means that is only going to lead to an
> URL in google that starts with an http:// instead of a gopher://
>
> If those come up as dead links because the protocol is not
> supported by some particular client then so be it. Perhaps Google
> could put a note saying that the browser needs to be capable of
> accessing gopher sites or that the user needs a plugin - I dunno,
> and don't much care.
>
> I can say this. There are several protocols as URIs which don't
> get indexed or returned as search strings because some, or many
> browsers do not yet, or no longer, support those protocols.
> Here's a list of some URIs where the protocols may or may not be
> supported depending upon whether certain software is installed on
> the client machine, or plugins have been installed, or support is
> inherent in some or most browsers:
>
> gopher://
> ftp://
> skype://
> http://
> https://
>
> Again, I'm not interested in ANYONE accessing any of my gopher
> resources via an http to gopher proxy. They can access those
> resources with a client that is gopher capable or not access them
> at all - this is the only way that gopher will have any
> relevance.
>
> I see no relevance in gopher protocol if it's just going to be
> accessed via hypertext transfer protocol anyway - therefore, I am
> now more inclined to consider blocking http to gopher proxy
> servers at this time than I ever have been.
>
> Going back to that thread now, here is the segue, in this
> particular posting, that I promised to be forthcoming a few
> moments ago...
>
>
> >
> > Anyway - great work - I really like the way gopherproxy.org
> works.
>
> Hey I think these are great services too, and applaud the effort
> and level of functionality - I just think it's wrong to let
> gopher fall further into obscurity because it can be relegated
> into insignificance by browswers (supposed to be multi-protocol
> clients) that do not have gopher support, and search engines that
> will not provide search results as gopher:// URIs.
>
>
> >
> >
> >
> > - Kim
> >
> >
> > _______________________________________________
> > Gopher-Project mailing list
> > Gopher-Project at lists.alioth.debian.org
> >
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-pr
> oject
>
> - --
> Bradley D. Thornton
> Manager Network Services
> NorthTech Computer
> TEL: +1.310.388.9469  (US)
> TEL: +44.203.318.2755 (UK)
> TEL: +41.43.508.05.10 (CH)
> http://NorthTech.US
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Find this cert at x-hkp://pool.sks-keyservers.net
>
> iQEcBAEBAwAGBQJSMv7KAAoJEE1wgkIhr9j3FmAH/0Xlvu6uaL9xjaiTg4d0C6Fg
> ICk4P8T6MI89hAdaNOxesGuIiQaCyMG4K/v20PNGpOH1V4okIe/dH4Cwm2T8i8tF
> Fhfs7QVFfCsRgcwzpwAK3rA68TYwAFSKaGoMGz28V9TkLjFBaqWB2SKlQdtxkspI
> 1PGadt9EdeCumGH09T1hbjd/629YJSzP81wckdeTQ828ddhkzjRBkbYNwLeldg12
> UFJtzkE6Uoyez63SlwHJjyjDAkM3PkL71qCNGLSBu9qkFw/pJ6BN2N0upeIhtSpJ
> im6CT3Fv4vfNSdBOxh2JSy0DGkXXpGs5R3tvyWAE209947B0S5llcBbE5YTcBDQ=
> =yYRZ
> -----END PGP SIGNATURE-----
>
>
>
>
>
>
>
> ---------- Forwarded message ----------
> From: "Bradley D. Thornton" <Bradley at NorthTech.US>
> To: Gopher Project Discussion <gopher-project at lists.alioth.debian.org>
> Cc:
> Date: Thu, 19 Sep 2013 10:41:24 -0700
> Subject: Re: [gopher] Joining in: I'm the maintainer/host of Gopher Proxy
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: RIPEMD160
>
>
>
> On 09/13/2013 05:41 AM, Kyle Hooks wrote:
> > I think we might be better off seeing if we can contribute GOPHER
> > protocol compatibility code to the Firefox codebase, or try to
> > convince them to ship it with a plug-in preinstalled.
>
> Thanks for the top-post there! :(
>
> Anyway, on the surface that sounds like the sane thing to do, doesn't
> it? Perhaps Cameron could weigh in on his thought related to this
> matter, considering he was shot down in flames on this subject while
> Firefox still had support for gopher:// protocol in its core.
>
> Particularly, there was talk of a concerted agenda to divest Firefox of
> gopher regardless of any commitments offered to maintain the code, etc.,
> and I'm interested in hearing just what the hearsay or supposition on
> that touchy subject was.
>
> I mean, if the deciding factor was related strictly to critical mass vs
> kruft, okay I can understand that - but the impression I got was that
> insiders over there did this w/prejudice for some reason.
>
> >
> > -----Original Message-----
> > From: Bradley D. Thornton [mailto:Bradley at NorthTech.US]
> > Sent: Friday, September 13, 2013 8:02 AM
> > To: Gopher Project Discussion
> > Subject: Re: [gopher] Joining in: I'm the maintainer/host of
> > Gopher Proxy
> >
> >
> >
> > On 09/13/2013 01:33 AM, Kim Holviala wrote:
> >> On Sep 12, 2013, at 16:18, Evert Meulie <evert at meulie.net>
> > wrote:
> >
> >>> Hi all,
> >>>
> >>> http://gopherproxy.org/ & http://gopherproxy.meulie.net/
> > allows Gopher content to be viewed in any web browser, by
> > converting Gopher content into web pages as you request it.
> >>>
> >>> And yes, currently there is little/no means in place to keep
> > bots & search engines out.
> >>> I've been reading a bit what has been written here in other
> > threads on this subject, and will chime in with my 2¢ soon.
> >
> >> Personally I don't mind that Google and others crawl through my
> > gopher resources, but I think quite a lot of people here object
> > to that. I think the easiest way would be to just have a
> > robots.txt to completely block all spidering.
> >
> > I'm one of those who object - not to gopher spiders indexing
> > resources, but any access to my resources via http. If I wanted
> > web browsers using hypertext transfer protocol browsing through
> > my resources then I would put them on webservers - which I
> > already do for other resources.
> >
> > This has come up before, and I was shot down by the community for
> > considering the blocking of all proxy servers. Many people here
> > felt that any form of indexing or access to gopher resources by
> > any foreign protocol was better than not being indexed or
> > accessed at all, and I disagree, at least where my resources are
> > concerned, especially since I maintain unique content only
> > available via gopher:// protocol.
> >
> > It's not for me to decide what others opinions are, but I for one
> > am of the mind that if someone can surf gopher resources via
> > http:// then there is no point in gopher:// at all.
> >
> > As far as robots.txt is concerned, my feeling is that this is a
> > http standard, and not a gopher standard, so there should be some
> > other way to limit indexing of gopher resources for those who
> > choose to do so. I do not choose to block such indexing, and
> > welcome it, just not via a means that is only going to lead to an
> > URL in google that starts with an http:// instead of a gopher://
> >
> > If those come up as dead links because the protocol is not
> > supported by some particular client then so be it. Perhaps Google
> > could put a note saying that the browser needs to be capable of
> > accessing gopher sites or that the user needs a plugin - I dunno,
> > and don't much care.
> >
> > I can say this. There are several protocols as URIs which don't
> > get indexed or returned as search strings because some, or many
> > browsers do not yet, or no longer, support those protocols.
> > Here's a list of some URIs where the protocols may or may not be
> > supported depending upon whether certain software is installed on
> > the client machine, or plugins have been installed, or support is
> > inherent in some or most browsers:
> >
> > gopher://
> > ftp://
> > skype://
> > http://
> > https://
> >
> > Again, I'm not interested in ANYONE accessing any of my gopher
> > resources via an http to gopher proxy. They can access those
> > resources with a client that is gopher capable or not access them
> > at all - this is the only way that gopher will have any
> > relevance.
> >
> > I see no relevance in gopher protocol if it's just going to be
> > accessed via hypertext transfer protocol anyway - therefore, I am
> > now more inclined to consider blocking http to gopher proxy
> > servers at this time than I ever have been.
> >
> > Going back to that thread now, here is the segue, in this
> > particular posting, that I promised to be forthcoming a few
> > moments ago...
> >
> >
> >
> >> Anyway - great work - I really like the way gopherproxy.org
> > works.
> >
> > Hey I think these are great services too, and applaud the effort
> > and level of functionality - I just think it's wrong to let
> > gopher fall further into obscurity because it can be relegated
> > into insignificance by browswers (supposed to be multi-protocol
> > clients) that do not have gopher support, and search engines that
> > will not provide search results as gopher:// URIs.
> >
> >
> >
> >
> >
> >> - Kim
> >
> >
> >> _______________________________________________
> >> Gopher-Project mailing list
> >> Gopher-Project at lists.alioth.debian.org
> >
> > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-pr
> > oject
> >
>
> _______________________________________________
> Gopher-Project mailing list
> Gopher-Project at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project
>
> - --
> Bradley D. Thornton
> Manager Network Services
> NorthTech Computer
> TEL: +1.310.388.9469  (US)
> TEL: +44.203.318.2755 (UK)
> TEL: +41.43.508.05.10 (CH)
> http://NorthTech.US
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.10 (GNU/Linux)
> Comment: Find this cert at x-hkp://pool.sks-keyservers.net
>
> iQEcBAEBAwAGBQJSOzdEAAoJEE1wgkIhr9j3x5wIAJ0GZt7BcI2NVS7IwJ1pgZD0
> d79o7ueiR3ncq0BYRsR/872/L3ok+YPr8z786wlRhxTfIIHQv+phuqYOsGmNnUDa
> dWGZ8hpEf5otXOKF9a9Vfw7qbhl1QDzCI/K7asqv/5ZyCfkzU3xESIWfZYDA/pI7
> 8x2n/2/fXuktmoEcTNEbtwpjUfh5uzxb7f7On371Ly+ZQ/nigIuVMP8NZ8BPSlG8
> kRkn9YYMHRRx3FVgs3IuxKk5/1Sab9Vesd5yCmX4X2wFsRsVnqMSg+BoOTvEaWwZ
> qkD6OxpEgV5kLF4b1MqlSx+OpG6P74hloQOOYpLCOlXmae/au+hMgRFCaRd+FC8=
> =z7PG
> -----END PGP SIGNATURE-----
>
>
>
>
> ---------- Forwarded message ----------
> From: chals <chals at altorricon.com>
> To: Gopher Project Discussion <gopher-project at lists.alioth.debian.org>
> Cc:
> Date: Thu, 19 Sep 2013 22:14:51 +0200
> Subject: Re: [gopher] Announcing gopherpedia.com
> On Sun, Sep 1, 2013 at 3:49 AM, Colin Mitchell
> <muffinista+gopher at gmail.com> wrote:
> > Hello All, I thought some of you would be interested in a project I
> > launched a few months ago - gopherpedia, a mirror of wikipedia in
> > gopherspace. It's accessible on port 70 at gopherpedia.com, or via
> > proxy server at http://gopherpedia.com/
> >
>
> I must say that I liked the idea straight away so I accessed the
> content both ways (with and without proxy). Congrats, I think this is
> a good contribution to gopherspace.
>
> > The data is searchable, and there's a list of recent searches on the
> > front page, along with a mirror of Wikipedia's featured daily content.
> >
>
> And the search engine seems to work pretty well.
>
> Thanks
>
> --
> chals
> www.chalsattack.com
>
>
>
>
> ---------- Forwarded message ----------
> From: Jacob Dahl Pind <rachael at telefisk.org>
> To: Gopher Project Discussion <gopher-project at lists.alioth.debian.org>
> Cc:
> Date: Thu, 19 Sep 2013 22:48:29 +0200 (CEST)
> Subject: Re: [gopher] Announcing gopherpedia.com
> On Sat, 31 Aug 2013, Colin Mitchell wrote:
>
>  Hello All, I thought some of you would be interested in a project I
>> launched a few months ago - gopherpedia, a mirror of wikipedia in
>> gopherspace. It's accessible on port 70 at gopherpedia.com, or via
>> proxy server at http://gopherpedia.com/
>>
>> The data is searchable, and there's a list of recent searches on the
>> front page, along with a mirror of Wikipedia's featured daily content.
>>
>>  Nice work, wikipedia is such a killer feature when one needs to waste
> some
> time, its amazing how one can get from one topic to a whole different one
> in a few clicks.
>
> Had toyed with the idear myself, had the wiki dumps here and made some
> code, but as you says its a time consuming process to keep it uptodate, big
> files and all that .
>
> seems the i lines your server sendes includes an extra field
> i=============================**==============================**===========
> null    (FALSE) 0
>
> should only be itext\thost\tport
>
> tables gets a bit confusing when they gets linewrapped, but not much you
> can do, sans detecting tables and send lines as long as needed, and let the
> clients handle any issues that may arise, else it works perfect.
>
> Regards
>
> --
> Jacob Dahl Pind | telefisk.org | fidonet 2:230/38.8
>
>
>
>
> _______________________________________________
> Gopher-Project mailing list
> Gopher-Project at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/gopher-project/attachments/20130919/33f4088c/attachment-0001.html>