The [Gemini protocol][0] came up on [nixers.net][1].

[0]: https://gemini.circumlunar.space/
[1]: https://nixers.net/showthread.php?tid=2339

Already popped up on my radar a while ago. Back then, I thought, "nah,
too complicated". Gopher is dead simple and that's nice. On the other
hand, the Gemini FAQ makes a good point:

> Gopher is simpler at a protocol level, but as a consequence the client
> is eternally uncertain: what character encoding is this text in? Is
> this text the intended content or an error message from the server?
> What kind of file is this binary data? Because of this, a robust
> Gopher client is made less simple by needing to infer or guess missing
> information.

Yep, that's not wrong.

In practice, I only ever had a problem with character encoding. I mean,
the Gopher RFC says it's supposed to be ASCII. End of discussion.
Sometimes, you do encounter something else, though, and yeah ... it's
2020, UTF-8 is everywhere. People expect that they can just use it.

Whatever.

Maybe I'll play with Gemini a bit. I'll probably be too lazy to run
HTTP, Gopher, and Gemini at the same time, so if Gemini takes off, one
of the other two has to die. (I even thought about running only Gopher
for a while.)

You are viewing proxied material from uninformativ.de. The copyright of proxied material belongs to its original authors. Any comments or complaints in relation to proxied material should be directed to the original authors of the content concerned. Please see the disclaimer for more details.