Complete.Org: Mailing Lists: Archives: gopher: July 2008:
[gopher] Re: Serving up gopher content via a wiki

[gopher] Re: Serving up gopher content via a wiki

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: gopher@xxxxxxxxxxxx
Subject: [gopher] Re: Serving up gopher content via a wiki
From: "Jay Nemrow" <jnemrow@xxxxxxx>
Date: Mon, 7 Jul 2008 16:29:16 -0600
Reply-to: gopher@xxxxxxxxxxxx

I had something like this going already with a combination of Docuwiki and
pygopherd.  The important part ended up being that Docuwiki stores its
documents as flat text files which pygopherd (actually most gopher servers)
is accustomed to using.  Sounds like what you are doing is much more
sophisticated.  WikiWords (embedded hyperlinks) have no analogue in gopher
so I ended up altering my wiki behavior to make things work better in
gopher.  Messy.
Keep us up-to-date on the wiki/gopher hybrid.  I would be interested in the
results!  Anthing to make managing a gopher even easier would be exciting...

Jay Nemrow

On 7/4/08, brian@xxxxxxxxxxxxx <brian@xxxxxxxxxxxxx> wrote:
> As time permits I've been working on a proof-of-concept for serving up
> gopher content via a wiki.  I'm one of the devs that works on
> WikkaWiki (, so naturally that is the
> framework on which I'm developing.
> My rationale for going in this direction, as well as some supporting
> notes, can be found at  I
> believe the resurgence of gopher will depend upon a number of
> different approaches; this represents my contribution.
> I have a test page that can be accessed at
>  Please keep in mind the key
> phrase "proof of concept."  Not all selectors have been implememted
> (rudimentary navigation should work, as well as text files downloads).
> Comments can comment here, or right on the
> GopherTest page (you'll need to register a username first).
>   --Brian

[Prev in Thread] Current Thread [Next in Thread]