Re: [gopher] Gopher+ support in the community

cgod doesn't implement Gopher+

(I don't think Gophernisus does either)

My views on Gopher+ are a bit hazy.

I think it need (if we want to improve the protocol) rethinking...

gophers:// could be very interesting.

However existing clients would not be able to use this.

So this would require completely new clients.

(Gopherspaces could support both gopher:// and gophers:// I suppose for backwards compatbility with older clients)

My Gopher client(s) of choice are basically

curl and Overbite. I was using elinks for a bit

but have found it's implementation to by buggy

at best.

cheers

James

James Mills / prologic

E: prologic@shortcircuit.net.au

W: prologic.shortcircuit.net.au

On Thu, Apr 23, 2015 at 8:18 AM, Kevin Veroneau <kevin@veroneau.net> wrote:

Hello everyone,

I'm curious to know how many widely used Gopher clients properly support Gopher+ and what's the communities general view about supporting it.

I personally haven't used any Gopher+ features, and my current GopherSpace doesn't use it either. How many of your gopherspaces have Gopher+ support?

I'm also a tad curious on working with "gophers://", Gopher over TLS. it'd be easy to enable on a gopher server, but no clients currently support it.

On that note about Gopher clients, I did mention awhile back that I was planning on developing a more modern stand alone gopher client for PCs. So if I made a new client, I'd add Gopher over TLS support for kicks, and depending on overall support, maybe Gopher+ support. OverbiteFF doesn't do Gopher+ it seems(from reading it's source) and neither does the android client...

One last question... what is your Gopher client of choice, and why?

Kevin.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
_______________________________________________
Gopher-Project mailing list
Gopher-Project@lists.alioth.debian.org
http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/gopher-project