deno-gopher VS gopher-plus

Shameless plug: I recently wrote a gopher client library for Deno, just for fun. https://github.com/matt1/deno-gopher

I also cleaned-up the weird formatting of the Gopher+ protocol and put it on github as a formatted markdown file since it was never and official RFC so trawling through an unstructured txt file when trying to implement the protocol was a pain: https://github.com/gopher-protocol/gopher-plus

Hope it is useful for someone implementing new gopher code like I was! :)

Shameless plug: I recently wrote a gopher client library for Deno, just for fun. https://github.com/matt1/deno-gopher

I also cleaned-up the weird formatting of the Gopher+ protocol and put it on github as a formatted markdown file since it was never and official RFC so trawling through an unstructured txt file when trying to implement the protocol was a pain: https://github.com/gopher-protocol/gopher-plus

Hope it is useful for someone implementing new gopher code like I was! :)

I think it is a bit of a chicken and an egg problem. There are a few Gopher+ servers out there, and the Gopher+ protocol is pretty flexible and designed with the metaverse in mind originally (see GopherVR from the original authors).

It is a shame that a lot of current Gopher users seem to be strongly against anything apart from standard Gopher, when the original authors of the protocol had much grander ideas for interactivity & visual interfaces. Sigh.

For anyone interested, the Gopher+ protocol doc never made it to a proper RFC, but is on github in a hyper-linked format to make it easier to read: https://github.com/gopher-protocol/gopher-plus/blob/main/gop...

https://github.com/gopher-protocol/gopher-plus/blob/main/gop... specifically mentions 3D representations of Gopherspace.