Jacob Dahl Pind | 21 Jan 10:10 2015

[gopher] mass crawle

could the owner of , please let the bot crawle a little less 
aggressiv, there is no pause between selector requests.

Jacob Dahl Pind | telefisk.org | fidonet 2:230/38.8
kaltheat | 8 Jan 00:45 2015

[gopher] History and future of "the gopher project"


I recently asked similiar questions in IRC (#gopherproject on freenode), but
without sufficient responds. So here again (with wider audience?):

What was "the gopher project"?
What is "the gopher project"?
How is "the gopher project" related to Debian (the mailing list runs on a
debian domain)?
What should "the gopher project" be?

I can't find informations on the purpose of "the gopher project". If it really
is a project it should have its own gopherhole.

I am kind of new to gopher and maybe these questions were already discussed
somewhere (please give me a hint in that case). But if I'm allowed to give my
two cents to the discussion of the purpose of "the gopher project", it's this:

The project should reflect the history, present and future of gopher as a
protocol and gopherspace as the usage of the protocol. Speaking of the future
this would mean that it could coordinate new developments (protocol, software,
services) and "recruiting" of new users/developers. To be able to do this sort
of things the project (as any project) needs a structure and people creating
and taking part in this structure. Maybe one can think of "the gopher project"
as a W3C for gopher (I must admit that I don't exactly know how the W3C works
and what it does).

What do you think?

(Continue reading)

Mateusz Viste | 7 Jan 00:23 2015

[gopher] Gopher-FAQ update

Hi all,

I received a contribution to the Gopher-FAQ from a user named kaltheat. 
He kindly cleaned up the FAQ from some dead links, and fixed a few things.

I used the occasion to make some changes, too. I removed some questions 
that were really out of date, and added a few new ones, related to 
subjects that were appearring on the gopher-project mailing list.

The latest version of the gopher-faq is available here:


Of course, I will happily accept any contributions - the document would 
still need to be polished (best to send modification as patches, either 
to the gopher-project mailing list or the comp.infosystems.gopher 

Mateusz Viste | 7 Jan 00:11 2015

Re: [gopher] GopherMole - a gopher media crawler

This a mail that is one week old (apparently it was stuck in some 
moderation queue on the mailing list) - the GopherMole spider does 
present the stats menu server list as a clickable menu since then.


On 01/06/2015 11:54 PM, James Mills wrote:
> On Fri, Jan 2, 2015 at 10:46 AM, Zachary Lee Andrews
> <zcrayfish@...
<mailto:zcrayfish@...>> wrote:
>     Would it be possible for your statistics menu to actually link to
>     the found servers instead of displaying them are informational text?
> +1
> James Mills / prologic
> E: prologic@... <mailto:prologic@...>
> W: prologic.shortcircuit.net.au <http://prologic.shortcircuit.net.au>
Zachary Lee Andrews | 2 Jan 01:46 2015

Re: [gopher] GopherMole - a gopher media crawler


Would it be possible for your statistics menu to actually link to the 
found servers instead of displaying them are informational text?


P.S.: I sent this to your email as well as the list because my posts are 
always sent to the moderation queue and never seem to get approved.

 >Hello list,
 >Here's a quick update on GopherMole - I worked on it since my last 
 >post, and made a few improvements:
 > - a 'statistics' page, where one can see some interesting numbers
 > - support for PDF documents (although sadly, not many PDF files in 
the >gopherspace contain proper metadata to identify them)
 > - random searches (as in "give me 10 random mp3 files")
 >  gopher://gopher.viste.fr/1/gophermole/
 >Interesting fact: my spider arrived to the end of the visible 
 >gopherspace, and found out there are 43'575 menus out there, spread 
 >over 134 servers. These are definitely not very high numbers.
 >I'm curious to know whether the spider missed any servers - the full 
 >list is available on gophermole (in the "statistics" menu). If you are 
(Continue reading)

Zachary Andrews | 27 Dec 06:29 2014

Re: [gopher] Local Veronica?

> gopher://zcrayfish.dyndns.org:70/9/users/everyone/local.veronica.tar.gz
That file no longer exists on my server; it hasn't been up there for a
while anyway... Besides it's very likely it came off of boombox or
some other server which had been corrupting files when it was up. :(
Zachary Andrews | 18 Dec 07:22 2014

[gopher] Web frontend for gopher

I have written a shell script www frontend for gopher servers, it
relies on lynx, html tidy, and xinetd (it probably works under regular
inetd too).  Please check it out and see what you guys think.

Source is at:

The script is public domain, I appreciate any useful modifications however. :)

feedback is welcome here or on IRC freenode/#gopherproject
Ciprian Dorin Craciun | 2 Jan 20:43 2015

[gopher] Regarding "title" (and other special) informational items [Was: Re: RFC submission?]

On Fri, Jan 2, 2015 at 9:59 AM, Mateusz Viste <mateusz@...> wrote:
> [...]
> document on piratepad.net looks more like a bag of wishes. Also, it
> describes the usage of some xml-like tags in gopher (title), which by
> itself, is a heresy to me. [...]

Although I tend to agree with Mateusz regarding the simplicity appeal
of the Gopher protocol (at times perhaps too simple), and the fact
that "bolting" new features on-top of the existing protocol (like the
title information items) detracts from this simplicity towards
convoluted specifications and incompatible implementations.

However the title information items, which replace the empty selector
with the "TITLE" selector, made me think a little about how structured
Gopher menus actually are right now...

First of all, is there any Gopher client which actually implements
this title information item feature?  Because I've seen it documented
it that RFC proposal I thought so, but Overbite doesn't seem to
implement it (although it only took one line of JavaScript to make it
so).  (BTW `lynx` doesn't even implement `URL:...` selectors...)

Back to the topic of how structured the Gopher menus are, currently
the Gopher menus are technically just a flat list of items with no
differentiation between the various items (except their type).
However if we look at a few Gopher sites, like the ones below
(randomly picked from a list I've once seen), we can easily observe
that the editors do impose a certain structure inside the menus
(especially the "root" menu).

(Continue reading)

Mateusz Viste | 31 Dec 10:45 2014

[gopher] gopher charset

Hi list,

I am using utf-8 for most of my content since years, and I always have 
this trouble that in gopherspace, utf-8 stuff appears all scrambled, 
until I manually switch my browser to the proper encoding.

Just wondering - maybe would it be a nice extension to add a server-wide 
charset preference to CAPS ? Of course it's not solving the problem of 
"I have some files in unicode, other in KOI, and some in Mazovia", but 
at least it could provide a clear default setting for server owners.

Let's say, something like this:


What do you think?

Mateusz Viste | 30 Dec 23:13 2014

[gopher] GopherMole - a gopher media crawler

Hi all,

Here I present GopherMole.

GopherMole is a project I worked on since some time now, and today is 
the day when it's ready enough to be put public. It is basically a 
gopher crawler, but focused on media files, and indexing the actual 
(meta) content of files, not their menu descriptions.

It's far from being as polished as I'd like it to be, I will improve it 
with time. For now, it indexes MP3, OGG and EPUB files. Other formats 
will come later.

Finally, here is the URL where you can take GopherMole for a test ride:


Nick Matavka | 30 Dec 18:12 2014

[gopher] RFC submission?

Hello, world!

I think it might soon be time for submitting the updated Gopher RFC.  In my belief, it should be within a month at most, as we have a very good document authored and edited by some of this mailing list's best minds (i.e. Kim Holviala, Matjaz Viste, Dr Kaiser, etc). 

But before the RFC is submitted, there are some organisational quirks that need to be fulfilled.  I suppose I *could* submit the draft RFC (available at http://piratepad.net/gopher) as an independent document, but that would only be for informational purposes, rather than putting it on the standards track.

I believe that what we currently have is a standard in a formative stage.  This is not simply information, or quirky RFC engineering humour.  This is the new standard for Next-Generation Gopher (call it GopherNG if you like, or Gopher++, I still haven't figured out a decent name for it).  If I send this as an independent submission and credit everyone, it'll never be anything other than simple "information".

The better way forward, at least in my view, is to submit it through the usual channels.  This involves more work, some of which I concede that I am not familiar with.  For instance, there will need to be a working group; I propose that this mailing list become one. but it needs a charter and it needs to be listed on the IETF's page, which is the part of the job I'm ignorant of (can't find the link to submit a working group for instance).

So I guess you can take this as a request for help.  Has anyone ever been through the IETF's Kafka-esque methods of working yet?  Can you elucidate them for me?  Should this simply be informational maybe?

Cordially yours,
N. Edward Matavka
Gopher-Project mailing list