Date: Tue, 2 Apr 1996 23:49:28 -0500 (EST)
From: James Milne <jmilne@electrontrap.org>
To: gopher@complete.org
Subject: [gopher] Mozilla gopher bug
Message-ID: <Pine.LNX.4.44.9604022341050.6068-100000@localhost.localdomain>
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

I just got pygopherd installed for the first time, and was playing 
around with it. Noticed that I was running into several problems, and 
discovered through some searching that my problem was that I was using 
Mozilla to try and browse Gopher sites. Turns out, Gopher is broken 
pretty bad in Mozilla right now. I could fall back to Netscape 4 or 
Lynx, but I'd rather see a more modern implementation (and once with a 
growing userbase) actually succeed, and it could use some help.

Bug 194220 (http://bugzilla.mozilla.org/show_bug.cgi?id=194220) has 
been filed as a meta bug for all the current Gopher issues with 
Mozilla. This includes issues with the current 1.4 alpha release. The 
more people that can test out Gopher issues, or who just go and vote 
for this bug, the more exposure it can get and hopefully Mozilla can 
be a viable Gopher client again.

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
             James Milne
       jmilne@electrontrap.org
 http://www.electrontrap.org/jmilne/
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=