Received: with ECARTIS (v1.0.0; list gopher); Sun, 13 Oct 2002 08:42:55 -0500 (EST) Return-Path: <jgoerzen@complete.org> Delivered-To: gopher@complete.org Received: from christoph.complete.org (0-1pool88-127.nas8.indianapolis1.in.us.da.qwest.net [65.128.88.127]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "christoph.complete.org", Issuer "John Goerzen -- Root CA" (verified OK)) by gesundheit.complete.org (Postfix) with ESMTP id 8877B62E43; Sun, 13 Oct 2002 08:42:53 -0500 (EST) Received: by christoph.complete.org (Postfix, from userid 1000) id 0F9B62B07A; Sat, 12 Oct 2002 14:09:06 -0500 (EST) Date: Sat, 12 Oct 2002 14:09:06 -0500 From: John Goerzen <jgoerzen@complete.org> To: gopher@complete.org Subject: [gopher] Re: embarrassing newbie question Message-ID: <20021012190906.GA21867@complete.org> References: <20021011183215.GC5635@excelhustler.com> <Pine.LNX.4.33.0210111439240.22050-100000@cadence.thinkers.org> Mime-Version: 1.0 Content-type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <Pine.LNX.4.33.0210111439240.22050-100000@cadence.thinkers.org> User-Agent: Mutt/1.4i Content-Transfer-Encoding: 8bit X-archive-position: 705 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 Fri, Oct 11, 2002 at 02:46:17PM -0400, Stephanie Smith wrote:

> So when I try to add a link to a gopher site (next on my list of things to > do), I would use that sort of entry instead of the URL: you mention > below.... (correct me if I'm wrong)

Yes, the URL: is only for non-gopher sites. The gopher protocol can link to other gopher sites without this extension.

> Interesting you should mention that. I was just considering switching, > given that there seems to be more explicit PyGopherd reference material > about than for UMN gopherd.

You'll probably be able to find information about UMN gopherd out in groups.google.com -- but not so much on websites. You can read a bit about the history of UMN gopherd, and the 3.x FurryTerror releases, at gopher://quux.org.

As it stands now, I have been devoting most of my gopher-server-writing time to PyGopherd. I feel that the advent of languages like Python can be exploited to write a more secure and featureful server in less time. It's also going to be possible in the future to share some code between it and OfflineIMAP [1], I beliveve. I am more comfortable with the security of PyGopherd right now than I am with that of UMN gopherd, and there is very little that UMN gopherd supports that PyGopherd doesn't.

[1] gopher://quux.org/1/devel/offlineimap

-- John