Server Contact Information

I strongly urge that EVERYONE who operates a Gopher Server
include a "CONTACT.TXT" informational file as
described in this document.  
   
  There is no reason why any Server (even established Gopher
Servers) should not include such basic informational
documents such as "contact.txt",
"changes.txt", or "about.txt".
   
       
---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo!
Mobile.  Try it now.

Document =
gopher://home.jumpjet.info/00Begin_HereReferencesStandard
_Informational_Files.txt
   
  Example = gopher://home.jumpjet.info/00Contact.txt
  
JumpJet Mailbox <jumpjetinfoyahoo.com> wrote:
  I strongly urge that EVERYONE who operates a Gopher Server
include a "CONTACT.TXT" informational file as
described in this document. 

There is no reason why any Server (even established Gopher
Servers) should not include such basic informational
documents such as "contact.txt",
"changes.txt", or "about.txt".


---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo!
Mobile. Try it now.




       
---------------------------------
Be a better friend, newshound, and know-it-all with Yahoo!
Mobile.  Try it now.

Is this part of the Gopher standard or did you invent it
just now?

Avery M. wrote:
> Is this part of the Gopher standard or did you invent
it just now?
>   

Invented.  The document referenced is a proposal.  A few
comments about 
the referenced document...

The inability to embed links into a document is not the
fault of the 
protocol, but a fact of that document's format.  One can
easily serve a 
Hypertext document on a Gopher site and links will work just
fine.

Also, Gopher *can* "associate a freeform label directly
with a file"; 
this is done in the menu.

There's also a standard mechanism to identify attributes of
Gopher items 
using Gopher+, e.g., +INFO, +ADMIN, +ABSTRACT blocks,
effectively making 
the proposal unnecessary.