[gopher] Draft RFC

[Nick Matavka]

On 21 June 2012 13:23, Alistair <alistair at alistairsserver.no-ip.org> wrote:
> On 21/06/2012 18:18, Nick Matavka wrote:
>>>
>>> * The redirect is for clients which don't support URL: links but which
>>> do support HTML. They will be sent to the correct location so that
>>> they're not left wondering what went wrong.
>>
>>
>> Yes, that's what "non-compliant" means (do not support URL:).
>>
>
> Non-compliant suggests either not doing something correctly or omitting
> support for something mandatory.
>
> There is no way it should be mandatory for a gopher client to support things
> that aren't gopher...
>
>
> _______________________________________________
> Gopher-Project mailing list
> Gopher-Project at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project

It should be mandatory for a Gopher client to support LINKING TO
things that aren't gopher.  HTTP clients (aka web browsers) do the
same thing.

For instance, if you see a link like <mailto:asdf at example.co.uk> you
can click it and it will launch your eMail client.  If you see a link
like <gopher://gopher.example.co.uk> it will launch your Gopher
client.

Why shouldn't Gopher clients do the same?

-- 
       /^\/^\
       \----|
   _---'---~~~~-_
    ~~~|~~L~|~~~~
       (/_  /~~--
     \~ \  /  /~
   __~\  ~ /   ~~----,
   \    | |       /  \
   /|   |/       |    |
   | | | o  o     /~   |
 _-~_  |        ||  \  /
(// )) | o  o    \\---'
//_- |  |          \
//   |____|\______\__\
~      |   / |    |
       |_ /   \ _|
     /~___|  /____\