Date: Tue, 20 Nov 2007 17:35:00 -0600
From: Chris <chris@hal3000.cx>
To: gopher@complete.org
Subject: [gopher] Re: BRING THE GOPHER BACK
Message-Id: <20071120173500.4c4c3ae3@work1.hal3000.cx>
In-Reply-To: <754829.36093.qm@web35510.mail.mud.yahoo.com>
References: <Pine.NEB.4.64.0711120952001.20840@vinland.freeshell.org>
	<754829.36093.qm@web35510.mail.mud.yahoo.com>
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

On Tue, 20 Nov 2007 11:32:00 -0800 (PST)
JumpJet Mailbox <jumpjetinfo@yahoo.com> wrote:

> You may find most of what you are seeking already on Gopher Jewels 2
>   gopher://home.jumpjet.info/11\Gopher_Jewels_2
>    
>   As far as Gopher dying/rising...
>   Educational/Government sources are dying,
>   Other sources are stable.
>    
>   A quick look over GJ2 will show that the real problem with Gopher is the lack of content originating on Gopher.  Most of the rarely appearing "new" content is really just feeds from an HTTP (Web) source.

I might point out that some are from ftp sources and that really if the info is available only from HTTP then to grab it there and put it onto gopher doesnt make it invalid in gopher. Information is information protocols are ways to diseminate it via the particular server.