Mime-Version: 1.0
Message-Id: <p05010406b8c7a71a4776@[205.189.158.32]>
In-Reply-To: <143EE215-419B-11D6-863F-0003930BF072@complete.org>
References: <143EE215-419B-11D6-863F-0003930BF072@complete.org>
Date: Wed, 27 Mar 2002 11:51:27 -0500
To: gopher@complete.org
From: Robert Hahn <rhahn@tenletters.com>
Subject: [gopher] Re: The road ahead
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


John:

>I don't think we should even have that.  I think of Gopher as a global
>filesystem -- you're "mounting world" when you browser gopherspace. 
>People can look at it with all sorts of different interfaces just like
>you can with, eg, NFS.

If this is what Gopher is truly about, then maybe we're going about 
designing clients the wrong way.

Maybe we should figure out how to mount a gopherhole as a networked 
drive (mounted readonly) and just let people use their OS of choice 
to browse, search, index, and open files - whatever they do with the 
files on their own drive - other than writing - can be done on a 
gopherdrive.

If that's what Gopher is *really* about.

...and I'm really cool with that notion - it makes a far better 
distinction from the web than many popular conceptions of what gopher 
is...

-rh