[gopher] Should we be mirroring Gopher sites via FTP?

Sun Sep 17 12:11:23 UTC 2017

Is electron a library akin to the QT you are currently using? Gtk would be super sweet, just saying... I do not want to have to install a large portion of KDE to run a gopher client. I do applaud the notion of supporting TLS. There a quite a few things that have become standard in the past when someone took the initiative to Just Do It (TM) in the absence of consensus. Thank you Kim and James 

--
Leveck

17. Sep 2017 01:33 by prologic at shortcircuit.net.au:

> Oh nice! I'll make > https://github.com/prologic/go-gopher>  support this! That also means > https://github.com/prologic/gopherproxy>  and > https://github.com/prologic/gopherclient>  (which I want to port to Electron)
>
> James Mills / prologic
>
> E: > prologic at shortcircuit.net.au> W: > prologic.shortcircuit.net.au
>
> On Sun, Sep 17, 2017 at 12:01 AM, Kim Holviala <> kim at holviala.com> > wrote:
>
>> We didn't decide... so I just did straight up gopher-over-TLS (no STARTLS though) running on randomly chosen port 7070. And as far as I know there are no clients which would support the gophers// protocol.
>>
>> - Kim
>>
>>
>>
>>> On 17 Sep 2017, at 03:59, James Mills <>>> prologic at shortcircuit.net.au>>> > wrote:
>>> Wait.... There are gopher TLS holes? Did we decide on how this works already?
>>> cheers>>> James
>>>
>>> James Mills / prologic
>>>
>>> E: >>> prologic at shortcircuit.net.au>>> W: >>> prologic.shortcircuit.net.au
>>>
>>> On Sat, Sep 16, 2017 at 3:01 PM, Mr. Leveck <>>> leveck at leveck.us>>> > wrote:
>>>
>>>>           >>>> Out of curiosity what clients properly handle gophers:// ?
>>>>
>>>> I will have some spare time coming up next week... looks like I will be getting a cert. Maybe >>>> gopher.leveck.us>>>>  (yeah, all my subdomains point to the same DSL router) will be the second TLS gopher site.
>>>> --
>>>> Leveck
>>>>
>>>> 16. Sep 2017 10:15 by >>>> kim at holviala.com>>>> :
>>>>
>>>>
>>>>> Not even going offtopic since Gophernicus - The Most Awesome(tm) gopher server \o/ - actually supports TLS and the only existing TLS-enabled gopher server (gophers://>>>>> gophernicus.org:7070/>>>>> ) runs on a free Let's Encrypt certificate.
>>>>> I was really against the whole thing until start of this year when my existing certs were due to renewal. So being slightly autistic I wrote down the steps to renew a cert between the traditional way vs. up and coming Let's Encrypt that I hated. 
>>>>> That was not even a competition... and yes, it's fully scritable - I've got a simple bash script running form /etc/cron.monthly/ to renew the cert every two months (they're valid for three). As long as Let's Encrypt is operational I never ever have to do anything to renew. Nada.
>>>>>
>>>>> - Kim
>>>>>
>>>>>
>>>>>> On 16 Sep 2017, at 19:08, Mr. Leveck <>>>>>> leveck at leveck.us>>>>>> > wrote:
>>>>>>           >>>>>> I have looked at Let's Encrypt in the past. There is quite a bit of smack talk floating around vis-a-vis this service particularly because it is free. Every single free cert I have seen in the last 20 years eventually shut down due to misuse by idiots. I guess I'll grab one while it is still around...
>>>>>>
>>>>>> Is renewing the LE cert scriptable or is this just something that will need a calendar entry and a reminder?
>>>>>>
>>>>>> --
>>>>>> Leveck
>>>>>>
>>>>>> 16. Sep 2017 02:38 by >>>>>> irl at fsfe.org>>>>>> :
>>>>>>
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> On 16/09/17 05:47, Stephen Kellat wrote:
>>>>>>>> RFC 4217 comes to mind at this point & I wonder if >>>>>>>> letsencrypt.org>>>>>>>>  supports that perchance.
>>>>>>>
>>>>>>> By putting some records into the DNS, yes it is possible to have a cert
>>>>>>> issued for a domain name that will then work for any service, including
>>>>>>> FTPS or even some form of Gopher/TLS if such a thing exists.
>>>>>>>
>>>>>>> Personally I've used the certs for mail servers, FTP servers, XMPP
>>>>>>> servers as well as many many web servers.
>>>>>>>
>>>>>>> Thanks,
>>>>>>> Iain.
>>>>>>>
>>>>>>> _______________________________________________
>>>>>>> Gopher-Project mailing list
>>>>>>> Gopher-Project at lists.alioth.debian.org
>>>>>>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project
>>>>>>   >>>>>> _______________________________________________
>>>>>> Gopher-Project mailing list
>>>>>> Gopher-Project at lists.alioth.debian.org
>>>>>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project
>>>>>
>>>>>
>>>>   
>>>> _______________________________________________
>>>> Gopher-Project mailing list
>>>> Gopher-Project at lists.alioth.debian.org
>>>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project
>>>>
>>>
>>> _______________________________________________
>>> Gopher-Project mailing list
>>> Gopher-Project at lists.alioth.debian.org
>>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project
>>
>>
>> _______________________________________________
>> Gopher-Project mailing list
>> Gopher-Project at lists.alioth.debian.org
>> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project
>>
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/gopher-project/attachments/20170917/321b7b64/attachment.html>