[gopher] Updated Gopher RFC

Tue May 8 16:08:17 UTC 2012

On 08/05/2012 17:01, zack mayson wrote:
> Gopher is generally designed to be a low overhead protocol; plus, it
> would introduce incompatibilities in clients running on old computers
> (i.e. Zilogs, Sinclairs) and specifying what kind of data/files/content
> X is neans a lot less work for client Y.
>

Trouble is there's a gazillion kinds of file and soon you end up with a 
huge mess like mimetypes.

As ling as a client or whatever knows what it /can/ handle it can just 
ignore anything it doesn't recognise.