[gopher] Gopher+ support in the community

[Kevin Veroneau]

Of course TLS would be optional.  It would just add some privacy and better protect password protected sections on a gopher hole to work more securely.

Passwords can be entered via "query requests", but I'm sure everyone knew that.

For a gopher client, I was going to make a console-based one, along with a Qt4 WebKit-based one.  Qt4 is nicely cross platform, so nobody will be left out.

I do like the UMN client, but I find it rather limited, and lynx works really well, but it's scrolling system is horrible on gopher menus and text...  My console client will address both the limitations and provide a more user friendlier experience overall.  Perhaps I'll work on my initial release this evening.

On April 22, 2015 4:35:27 PM MDT, James Mills <prologic at shortcircuit.net.au> wrote:
>On Thu, Apr 23, 2015 at 8:29 AM, Cameron Kaiser <spectre at floodgap.com>
>wrote:
>
>> I'm not opposed to Gopher over TLS, but I definitely would not want
>it to
>> be
>> mandatory, and it would increase client burden as well particularly
>with
>> respect to certificate management.
>>
>
>+1 on Gopher over TLS being optional.
>
>gophers:// and port 7433?
>(It doesn't seem to be taken according to the register[1])
>
>cheers
>James
>
>[1]:
>https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.txt
>
>James Mills / prologic
>
>E: prologic at shortcircuit.net.au
>W: prologic.shortcircuit.net.au
>
>
>------------------------------------------------------------------------
>
>_______________________________________________
>Gopher-Project mailing list
>Gopher-Project at lists.alioth.debian.org
>http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project

-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/gopher-project/attachments/20150422/3844987e/attachment-0001.html>