From: "Gopher-Project" <gopher-project-bounces+rachael=telefisk.org@lists.alioth.debian.org> Date: Tue Dec 30 18:26:18 2014 Subject: Re: [gopher] Hello, world! --===============2319149643779428645== Content-Type: multipart/alternative; boundary=001a113e9642d39ca7050b72467a --001a113e9642d39ca7050b72467a Content-Type: text/plain; charset=UTF-8 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. On 30 December 2014 at 12:15, Wolfgang Faust <wolfgangmcq@gmail.com> wrote: > On Mon, Dec 29, 2014 at 6:36 PM, James Mills > <prologic@shortcircuit.net.au> wrote: > > > > On Tue, Dec 30, 2014 at 6:15 AM, Nick Matavka > > <n.theodore.matavka.files@gmail.com> wrote: > >> > >> Hello, world! > > > > > > Hello Nick! > > > > > >> > >> Many years ago, I collaborated with several people (I have forgotten all > >> their names, but one of the contributors writes under the name Barana) > on > >> this mailing list about the future of Gopher. I eventually took the > >> initiative in creating a rough draft for a new Gopher RFC, and invited > >> comment, but no consensus was reached. I believe that all the new > features > >> Gopher has *mandate* an RFC; Gopher+, caps files, etc etc etc. > >> > >> I now believe that consensus *can* be established and therefore I > >> re-submit the same link. Please edit it and comment to the best of your > >> ability. I hope to actually submit this in the near future. > >> > >> http://piratepad.net/gopher > > > > > > I haven't quite read through this thoroughly yet. (Also I'm brand > spanking > > new go Gopher!) > > > > Couple of questions: > > > > Is this a combination of the old Gopher protocol with > > inclusion of some of the GOpher+ ideas? > See the "Goals" section of the document for details, but it's > primarily intended to codify current practices and ad-hoc standards. > If it's not currently in common use, it doesn't belong in the > standard. For example, it covers: > * Several gophertypes not in the original RFC, including the > ubiquitous 'i' type. > * caps.txt and robots.txt files > * What clients and servers should do with the trailing fullstop on > menus and other text types (this still has some holes, I think--edits > welcome!) > * URL: selectors > * And more! > > It is *not* intended to add even more features, unless they are > already in common use. > > -- > The views expressed above are exclusively mine, if anyone's. > > _______________________________________________ > Gopher-Project mailing list > Gopher-Project@lists.alioth.debian.org > http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project > -- /^\/^\ \----| _---'---~~~~-_ ~~~|~~L~|~~~~ (/_ /~~-- \~ \ / /~ __~\ ~ / ~~----, \ | | / \ /| |/ | | | | | o o /~ | _-~_ | || \ / (// )) | o o \\---' //_- | | \ // |____|\______\__\ ~ | / | | |_ / \ _| /~___| /____\ --001a113e9642d39ca7050b72467a Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">I think a new goal should be added---standardising Gopher+= .=C2=A0 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 enhan= cing its usage.=C2=A0 I'm happy that Gopher development moves at a glac= ial 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 bloo= dy ready.<br></div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote= ">On 30 December 2014 at 12:15, Wolfgang Faust <span dir=3D"ltr"><<a hre= f=3D"mailto:wolfgangmcq@gmail.com" target=3D"_blank">wolfgangmcq@gmail.com<= /a>></span> wrote:<br><blockquote class=3D"gmail_quote" style=3D"margin:= 0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class=3D"HOEnZ= b"><div class=3D"h5">On Mon, Dec 29, 2014 at 6:36 PM, James Mills<br> <<a href=3D"mailto:prologic@shortcircuit.net.au">prologic@shortcircuit.n= et.au</a>> wrote:<br> ><br> > On Tue, Dec 30, 2014 at 6:15 AM, Nick Matavka<br> > <<a href=3D"mailto:n.theodore.matavka.files@gmail.com">n.theodore.m= atavka.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 forgott= en all<br> >> their names, but one of the contributors writes under the name Bar= ana) on<br> >> this mailing list about the future of Gopher.=C2=A0 I eventually t= ook the<br> >> initiative in creating a rough draft for a new Gopher RFC, and inv= ited<br> >> comment, but no consensus was reached.=C2=A0 I believe that all th= e 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.=C2=A0 Please edit it and comment to the b= est of your<br> >> ability.=C2=A0 I hope to actually submit this in the near future.<= br> >><br> >> <a href=3D"http://piratepad.net/gopher" target=3D"_blank">http://p= iratepad.net/gopher</a><br> ><br> ><br> > I haven't quite read through this thoroughly yet. (Also I'm br= and 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=3D"HOEnZb"><font color=3D"#888888"><br> --<br> The views expressed above are exclusively mine, if anyone's.<br> <br> _______________________________________________<br> Gopher-Project mailing list<br> <a href=3D"mailto:Gopher-Project@lists.alioth.debian.org">Gopher-Project@li= sts.alioth.debian.org</a><br> <a href=3D"http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-p= roject" target=3D"_blank">http://lists.alioth.debian.org/cgi-bin/mailman/li= stinfo/gopher-project</a><br> </font></span></blockquote></div><br><br clear=3D"all"><br>-- <br><div clas= s=3D"gmail_signature"> =C2=A0 =C2=A0 =C2=A0 =C2=A0/^\/^\<br> =C2=A0 =C2=A0 = =C2=A0 =C2=A0\----|<br> =C2=A0 =C2=A0_---'---~~~~-_ =C2=A0<br> =C2=A0 = =C2=A0 ~~~|~~L~|~~~~<br> =C2=A0 =C2=A0 =C2=A0 =C2=A0(/_ =C2=A0/~~--<br> =C2= =A0 =C2=A0 =C2=A0\~ \ =C2=A0/ =C2=A0/~<br> =C2=A0 =C2=A0__~\ =C2=A0~ / =C2= =A0 ~~----,<br> =C2=A0 =C2=A0\ =C2=A0 =C2=A0| | =C2=A0 =C2=A0 =C2=A0 / =C2= =A0\ =C2=A0<br> =C2=A0 =C2=A0/| =C2=A0 |/ =C2=A0 =C2=A0 =C2=A0 | =C2=A0 =C2= =A0|<br> =C2=A0 =C2=A0| | | o =C2=A0o =C2=A0 =C2=A0 /~ =C2=A0 | =C2=A0<br> = =C2=A0_-~_ =C2=A0| =C2=A0 =C2=A0 =C2=A0 =C2=A0|| =C2=A0\ =C2=A0/<br> (// ))= | o =C2=A0o =C2=A0 =C2=A0\\---'<br> //_- | =C2=A0| =C2=A0 =C2=A0 =C2= =A0 =C2=A0 =C2=A0\ <br>// =C2=A0 |____|\______\__\<br>~ =C2=A0 =C2=A0 =C2= =A0| =C2=A0 / | =C2=A0 =C2=A0|<br> =C2=A0 =C2=A0 =C2=A0 =C2=A0|_ / =C2=A0 \= _|<br> =C2=A0 =C2=A0 =C2=A0/~___| =C2=A0/____\ =C2=A0 =C2=A0 =C2=A0 =C2=A0= <br></div> </div> --001a113e9642d39ca7050b72467a-- --===============2319149643779428645== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Gopher-Project mailing list Gopher-Project@lists.alioth.debian.org http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project --===============2319149643779428645==-- Thread start (DIR) [gopher] Hello, world! (DIR) Followup: Re: [gopher] Hello, world! (DIR) Followup: Re: [gopher] Hello, world!