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