Received: with ECARTIS (v1.0.0; list gopher); Thu, 02 Jun 2005 13:05:47 -0500 (CDT) Received: from gatekeeper.excelhustler.com ([68.99.114.105] helo=excelhustler.com) by glockenspiel.complete.org with esmtps (with TLS-1.0:RSA_AES_256_CBC_SHA:32) (No TLS peer certificate) (Exim 4.50) id 1Ddu4e-0003Lo-30; Thu, 02 Jun 2005 13:05:46 -0500 Received: from wile.internal.excelhustler.com ([192.168.1.34]) by excelhustler.com with esmtp (Exim 4.50) id 1Ddu4U-0006aq-VN; Thu, 02 Jun 2005 13:05:37 -0500 Received: by wile.internal.excelhustler.com (Postfix, from userid 1000) id CF8865EA18; Thu, 2 Jun 2005 13:05:33 -0500 (CDT) Date: Thu, 2 Jun 2005 13:05:33 -0500 From: John Goerzen <jgoerzen@complete.org> To: gopher@complete.org Subject: [gopher] Re: Gopher block! Message-ID: <20050602180533.GI342@excelhustler.com> References: <20050529063117.GA10967@pongonova.net> <20050529193612.GL12306@pongonova.net> Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050529193612.GL12306@pongonova.net> User-Agent: Mutt/1.5.9i X-Spam-Status: No (score -2.7): ALL_TRUSTED=-2.82, AWL=0.101 X-Virus-Scanned: by Exiscan on excelhustler.com at Thu, 02 Jun 2005 13:05:37 -0500 X-Spam-Status: No (score 0.0): AWL=0.023 X-Virus-Scanned: by Exiscan on glockenspiel.complete.org at Thu, 02 Jun 2005 13:05:46 -0500 Content-Transfer-Encoding: 8bit X-archive-position: 1042 X-ecartis-version: Ecartis v1.0.0 Sender: gopher-bounce@complete.org Errors-to: gopher-bounce@complete.org X-original-sender: jgoerzen@complete.org Precedence: bulk Reply-to: gopher@complete.org List-help: <mailto:ecartis@complete.org?Subject=help> List-unsubscribe: <mailto:gopher-request@complete.org?Subject=unsubscribe> List-software: Ecartis version 1.0.0 List-Id: Gopher <gopher.complete.org> X-List-ID: Gopher <gopher.complete.org> List-subscribe: <mailto:gopher-request@complete.org?Subject=subscribe> List-owner: <mailto:jgoerzen@complete.org> List-post: <mailto:gopher@complete.org> List-archive: <http://www.complete.org/mailinglists/archives/> X-list: gopher

On Sun, May 29, 2005 at 02:36:12PM -0500, brian@pongonova.net wrote: > OK, I have a gopher server up and running...problem is, I really don't > know where to start! Sure, I've read the pygopherd documentation, but > I don't have a clear picture of what a typical gopher file looks like > (formatting of selectors, layout, etc.).

Well, like a Web site, "typical" is not necessarily possible :-)

You can take a look at quux.org to get a feel for what it looks like to the user.

So, if you take a look at the top-level page of quux.org, here's an excerpt for the .Links file for that directory:

Path=./Software Name=Software and Downloads

Path=/Software/Gopher/servers Host=+ Port=+ Name=Other Gopher Servers Type=1

Path=/Archives/index Host=+ Port=+ Name=Index to Quux.Org Type=1

The first stanza sets the name for a specific directory. The next two add entries to the directory index that wouldn't already be there. The UMN gopherd manual may provide better detail than PyGopherd currently does on the setup. PyGopherd's UMNDirHandler will parse UMN files.

> Like Alessandro, I too miss the simpler times. I often wonder where > technology went wrong when it turned down the path of what I call > "prerequisite complexity," something I see quite often in my IT life: > The idea that technology requires ever-increasing complexity, whether > or not the problem that is being solved actually warrants it.

Indeed. See XML :-)

> Setting up a gopher server is my insignificant way of protesting the > bloat that permeates all that is Internet-related.

Excellent. Welcome aboard!

-- John