Alex Schroeder 🐝 is a user on You can follow them or interact with them if you have an account anywhere in the fediverse. If you don't, you can sign up here.

The inability to show UTF-8 in Gopherspace makes me want to cry. Perhaps a simple heuristic will suffice for most uses? Anyway, I managed to rewrite my server once more and now it knows how to properly daemonize and drop privileges and all that, so now it runs on port 70 instead of 7070.
And with that I think I’m going to take a break from gopher tooting and gopher server development. Time to do other things.

Alex Schroeder 🐝 @kensanata

Hum, using the client seems to work for UTF-8 gopher sites like my gopher wiki. But not for lynx. Hrm.

Β· Web Β· 0 Β· 0

@ckeen Actually my gopher server double encoded the UTF-8 upon printing. Today I just removed some encoding and decoding statements on the server side and suddenly gopher.el started to work correctly, no change required. But for Lynx, I'm not sure. Perhaps Lynx expects URL-encoded selectors? Right now I have no time to investigate, sadly.

@kensanata @ckeen

Not sure if this helps, but the Lynx documentation on Gopher URL handlong says:

"Any reserved characters in the selector should be hex escaped (%hh), including slashes, although hex escaping of slashes is not required by Lynx in gopher URLs." (from