DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=X-YMail-OSG:Received:Date:From:Subject:To:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding:Message-ID;
  b=zaIPvAdyR22SF/PwhOP+d0Ly2Ns/oOnglIIvhOZwuN9iyRtoYhZiwMVheEEHQRPC959aykylBd6KZyhtzS8abcgqO5WbZf2MGnhUqr/kq+RhUEiJHrgqGiCUt6TaVeq69ZGRayate9AeSzjnzX2qbdZahSbjG00Ac4L++Xl1rbE=;
Date: Sun, 10 Dec 2006 19:34:58 -0800 (PST)
From: JumpJet Mailbox <jumpjetinfo@yahoo.com>
Subject: [gopher] Re: Gopher home pages (was: Web-Based Subscription
                Management)
To: gopher@complete.org
In-Reply-To: <37426.66.222.64.178.1165616880.squirrel@66.222.64.178>
MIME-Version: 1.0
Content-type: text/plain
Content-Transfer-Encoding: 8bit
Message-ID: <797880.55716.qm@web35505.mail.mud.yahoo.com>
Sender: gopher-bounce@complete.org
Errors-to: gopher-bounce@complete.org
Precedence: bulk
Reply-to: gopher@complete.org

Although I.E. handles the "i" (information) "Type" strangely, it is not the only software with this issue.  Regardless of the Gopher client, the Gopher protocol places a burden on Server operators to assist Clients whenever possible.  The need for the Server operator to have to even specify "Type" mappings is just one example.  Without the Server specifically associating the "Type" with a file extension, even dedicated Gopher Clients will, for example, try to open a binary file as if it were a text file!  
  Although, in this example, Internet Explorer would try to open an "i" (information) as if it were a link, the Server operator can take steps to provide the I.E. with useful results if they DO try to open the "i" as a link (rather than just letting them get the undecipherable built-in error message).  The simplest solution is to STOP using "fake" as a path with "i", and instead use a real path to a real file (see: gopher://home.jumpjet.info/00\Begin_Here\Link_File_Basics.txt ).  This file can be to a help file explaining why you shouldn't click on "i", a link to your standard "About.txt" file, a link to one of your directories, or even a link to another server (such as to JumpJets collection of true Gopher clients).  
   
  It IS the Server Operators responsability to make their Gopher Server as generically friendly as possible.  Sure, suggest to users better alternatives, but DON'T try to FORCE users into only doing things certain ways.  This is whats so bad about HTTP, and all those websites that are specifically optimized for this or that flavor of browser.  Always think that your Server may be accessed by DOS, or an Amiga, or an Atari, or an Acorn, or even a VAX; and consider what these Clients would see and what they could do should they visit.   
   
  
newmanbe@sdf.lonestar.org wrote:
  > I've tried it, it doesn't work. I mean the folder works but not the "btdn
> in
> Gopherspace!" page. The "More btdn in Gophersoace",I think you meant
> "Gopherspace".
Probably
>The page that pops up in my browser is
> gopher://gopher.9grid.de/iErr. I'm using Internet Explorer 6.0 with the
> EnableGopher registry key.
You didn't do your homework! Internet Explorer does not properly support i
(information links). Read gopher://gopher.floodgap.com/0/gopher/wbgopher
> Eric


---------------------------------
Check out the all-new Yahoo! Mail beta - Fire up a more powerful email and get things done faster.