To: "em@nuel" <em@nuel.ca>
Cc: gopher@complete.org
Subject: [gopher] Re: web->gopher
References: <20010520231206.B10530@siva.heatdeath.org>
From: John Goerzen <jgoerzen@complete.org>
Date: 21 May 2001 10:37:33 -0500
In-Reply-To: <20010520231206.B10530@siva.heatdeath.org>
Message-ID: <87itiud876.fsf@complete.org>
Lines: 16
User-Agent: Gnus/5.090001 (Oort Gnus v0.01) XEmacs/21.1 (Cuyahoga Valley)
MIME-Version: 1.0
Content-type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 8bit
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org


"em@nuel" <em@nuel.ca> writes:

> Some of you may remember the web->gopher gateway I was working on some
> months back.  Well, I just woke it up.  It had been dormant in the
> middle of a bunch of work to improve the code and add proper Gopher+ for
> some time now, and I just tied up a bunch of loose ends today.

It looks way cool!  Glad to see it back alive!

Your Gopher+ question about the bug in gopherd is a sticky one.  I may
have to look into it, but the question as to how to handle that in the
client is a tricky one because many gophers out there are not actively
maintained and won't see the update even if gopherd is fixed.  I'm not
sure what to suggest just yet.

-- John