Alex Schroeder 🐝 is a user on octodon.social. 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.
Alex Schroeder 🐝 @kensanata

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.
gopher://alexschroeder.ch
And with that I think I’m going to take a break from gopher tooting and gopher server development. Time to do other things.
alexschroeder.ch/wiki/2018-01-

@kensanata Oh hey, I wonder if Mastodon can handle Z̢͎̖̲͉̋͗͛̇́̏̎͡a̴̡̛̳͔̖̻̣̭̱͚͎͂̌́̓͘l̸̹̼̩̜͖̝̃̓́̉̈̀̆͗g̷̗͚̦͚͕̲̜̐̽̍͛͊͂̎̓ö̵̠͉̥̺̣͍̫̋̍̃͑̀̒̃͟ text, the demon lord of #ascii destruction.

Also, this toot will be interesting to see if this kind of technological #w̧̡̜͓̮͕͖͇̙̽̈́̊̈͑̾̓̔͠i̴̡̛̺͔̮̙̟̳̖̿̾̓̒͜ţ̵̡̗͓̝̱̰̉͑͆͐̽̌̚c̨̝̯̹̠̲͙̱͔̠̄͆͑̄̃͒h̡̥͚̪̭̭̥̱͖́̆͌̕̚e̡̡̬̞̩̞̞̐͂̉̑̚͟ͅͅř̷̖̪͎̙̠͖̮̦̾̈́̄̿̇͘͘ͅy̳̪̘̩̟͛͌̄̒̂͡ͅ applies to hashtags. Or if it gets applied to the normal #witchery tag.

All hail #zalgo, the #pagan
.
ŏ̵̢̪̲̹̜̽͗͗̆͆̕͡͠ͅv̖̖̭̭͎̺͂̊͂̎͗̕͘̚͡ě̤͈̘̺͕̥̖͋̑̌̃̀͊̕͟͝ͅŗ̸̳̰͉̝̫̩̻̗̹̃͋̇̏̿̑̑͡͠l̷̜̹̟̲̠̜̠̆̾͐͊̈̿̂̈́̈͢o̶̢̡̻͍̻̖̲̟̮͐͛̈́͒̊̄̓̌̚ͅr̷̙̫͕͕̺̊̉͌̽͌͆͞d̸̟͔̱͈͉͈̆̈́͊̆̇̚͟͞ of #utf8 abuse!

(No elephants were harmed in the making of this toot).

@kensanata So, a silver lining is Gopher at least would allow the above to be readable, minus the tons of empty square box replacement characters, and not permit unicode abuse.

Still stinks that all the other non-Latin based languages are out of luck :(

@cj I mean, if your client is Emacs based, recoding the buffer will at least be easy. But any other client will need a button, or a menu.

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

@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 lynx.invisible-island.net/lynx)