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: JumpJet Mailbox <jumpjetinfo@xxxxxxxxx>
Date: Thu, 10 Jul 2008 13:33:21 -0700 (PDT)
Reply-to: gopher@xxxxxxxxxxxx

Have you considered GN?  
It serves up either HTTP or Gopher data DYNAMICALLY (depending on the client 
request)!  Check out this operating GN server:
--- On Wed, 7/9/08, Jay Nemrow <jnemrow@xxxxxxx> wrote:

From: Jay Nemrow <jnemrow@xxxxxxx>
Subject: [gopher] Re: Serving up gopher content via a wiki
To: gopher@xxxxxxxxxxxx
Date: Wednesday, July 9, 2008, 12:14 AM

When I was struggling with how to "merge" the web and gopherspace, I
myself trying to determine if I wanted to make web content accessible
through a gopher client or to make gopher content accessible through the
web.  It seems a lot of people went for what I finally also decided was the
logical course: webified gopher content, which is to say just building web
access essentially atop a gopher server.
In my wiki/gopher hybrid, I immediately saw that there were monumental
differences, the most glaring was that gopher lends itself to a heirarchy
(the simpliest method mirrors the files/documents in folders[menus] scheme)
and wiki wants to be essentially flat (all pages on an equal footing and
crosslinked).  I found myself constantly wanting to make the wiki more
heirarchial because that is the gopher way (drilling down through menus)
which I find more to my liking.  I finally decided that I was really wanting
to conveniently add lower menus, files, or documents to gopher menus,
shuffle things about like it was in an outliner, and finally desired to
abandon wiki except for the interesting markup that could render nicely in a
web browser from a human-readable text file that gopher could serve up raw.
Again, it ended up being a webified gopher server/CMS system, losing a lot
of the wikiness.  I never got around to actually coding the idea, but I
still ponder some sort of Outliner/CMS/Gopher hierarchial mashup.

How do you plan to meld the wiki and the gopher?  I could never figure out
how to do both without losing the essence of either one or the other.
Perhaps you see a way that I never could figure out...


On Tue, Jul 8, 2008 at 10:17 AM, <brian@xxxxxxxxxxxxx> wrote:

> On Tue, Jul 08, 2008 at 11:11:02AM -0500, brian@xxxxxxxxxxxxx wrote
> In fact, there's really no reason to make a big deal about a proxy
> being a gopher proxy -- many won't care, so long as they can simply
> find the information they need.  And the "clickable link" meme
> certainly carry over into the gopher world without users having to
> change their habits, install add-ons to their browsers, etc.


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