<div dir="ltr">I think a new goal should be added---standardising Gopher+. I don't want to glut-ise Gopher like HTML has been, but I think that it's a feature that should be made official in the hopes of enhancing its usage. I'm happy that Gopher development moves at a glacial pace---helps me keep up---but the Gopher+ spec is from nineteen-ninety-bloody-three and in my opinion it's time to make it a standard all bloody ready.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On 30 December 2014 at 12:15, Wolfgang Faust <span dir="ltr"><<a href="mailto:wolfgangmcq@gmail.com" target="_blank">wolfgangmcq@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Mon, Dec 29, 2014 at 6:36 PM, James Mills<br>
<<a href="mailto:prologic@shortcircuit.net.au">prologic@shortcircuit.net.au</a>> wrote:<br>
><br>
> On Tue, Dec 30, 2014 at 6:15 AM, Nick Matavka<br>
> <<a href="mailto:n.theodore.matavka.files@gmail.com">n.theodore.matavka.files@gmail.com</a>> wrote:<br>
>><br>
>> Hello, world!<br>
><br>
><br>
> Hello Nick!<br>
><br>
><br>
>><br>
>> Many years ago, I collaborated with several people (I have forgotten all<br>
>> their names, but one of the contributors writes under the name Barana) on<br>
>> this mailing list about the future of Gopher. I eventually took the<br>
>> initiative in creating a rough draft for a new Gopher RFC, and invited<br>
>> comment, but no consensus was reached. I believe that all the new features<br>
>> Gopher has *mandate* an RFC; Gopher+, caps files, etc etc etc.<br>
>><br>
>> I now believe that consensus *can* be established and therefore I<br>
>> re-submit the same link. Please edit it and comment to the best of your<br>
>> ability. I hope to actually submit this in the near future.<br>
>><br>
>> <a href="http://piratepad.net/gopher" target="_blank">http://piratepad.net/gopher</a><br>
><br>
><br>
> I haven't quite read through this thoroughly yet. (Also I'm brand spanking<br>
> new go Gopher!)<br>
><br>
> Couple of questions:<br>
><br>
> Is this a combination of the old Gopher protocol with<br>
> inclusion of some of the GOpher+ ideas?<br>
</div></div>See the "Goals" section of the document for details, but it's<br>
primarily intended to codify current practices and ad-hoc standards.<br>
If it's not currently in common use, it doesn't belong in the<br>
standard. For example, it covers:<br>
* Several gophertypes not in the original RFC, including the<br>
ubiquitous 'i' type.<br>
* caps.txt and robots.txt files<br>
* What clients and servers should do with the trailing fullstop on<br>
menus and other text types (this still has some holes, I think--edits<br>
welcome!)<br>
* URL: selectors<br>
* And more!<br>
<br>
It is *not* intended to add even more features, unless they are<br>
already in common use.<br>
<span class="HOEnZb"><font color="#888888"><br>
--<br>
The views expressed above are exclusively mine, if anyone's.<br>
<br>
_______________________________________________<br>
Gopher-Project mailing list<br>
<a href="mailto:Gopher-Project@lists.alioth.debian.org">Gopher-Project@lists.alioth.debian.org</a><br>
<a href="http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project" target="_blank">http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project</a><br>
</font></span></blockquote></div><br><br clear="all"><br>-- <br><div class="gmail_signature"> /^\/^\<br> \----|<br> _---'---~~~~-_ <br> ~~~|~~L~|~~~~<br> (/_ /~~--<br> \~ \ / /~<br> __~\ ~ / ~~----,<br> \ | | / \ <br> /| |/ | |<br> | | | o o /~ | <br> _-~_ | || \ /<br> (// )) | o o \\---'<br> //_- | | \ <br>// |____|\______\__\<br>~ | / | |<br> |_ / \ _|<br> /~___| /____\ <br></div>
</div>