Complete.Org: Mailing Lists: Archives: gopher: January 2002:
[gopher] Re: Heads up
Home

[gopher] Re: Heads up

[Top] [All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index] [Thread Index]
To: gopher@xxxxxxxxxxxx
Subject: [gopher] Re: Heads up
From: Timm Murray <hardburn@xxxxxxxxxx>
Date: Tue, 8 Jan 2002 23:14:27 -0600
Reply-to: gopher@xxxxxxxxxxxx

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tuesday 08 January 2002 20:53, you wrote:
> On Tue, Jan 08, 2002 at 06:36:00PM -0500, John Goerzen wrote:
> > Hi,
> >
> > In conjunction with UMN Gopher's 10th birthday, I will be releasing
> > version 3.0 of UMN gopher/gopherd sometime within the next 48 hours.
>
> (In my best Mr. Burns voice.... "Excellent")
>
> > Long live Gopher!
>
> Indeed.  Thanks for version 3.0, I will check it out within the next
> few days.   I guess the question is now, "where is gopher going?"
>
> As an open question, I'd like to ask people:
>
> - What does gopher *not* do that you wish it did?  (Keeping in mind
>   that gopher is gopher, and HTTP is HTTP, so please don't say, "some
>   cookie type of ability would be nice...")

To me, Gopher seems to be a much less flexible protocol than HTTP.  However, 
this may be a hidden advantage; it stops Gopher from becoming that gigantic, 
festering pile of commercialism that the web has become.  I think the only 
thing I really don't like is that it's hard to find good content.  OK, 
quux.org has a lot of stuff, but I'd like to see more academic resources on 
Gohper.  I'd like to see more Free Software projects use Gopher.  Just more 
content is what is really needed.

- -- 
I have also been a huge Unix fan every since I realized that SCO was not Unix.
                --Dennis Baker
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iEYEARECAAYFAjw70bcACgkQqpueKcacfLT90QCglNfLsXOyVFbldcpByYPr0uUK
5CEAoKjOKv+1AyHJJ2A2H328pXu74kw7
=OpG6
-----END PGP SIGNATURE-----


[Prev in Thread] Current Thread [Next in Thread]