I also think that it is problematic that TLS is mandatory in Gemini. (I think it would be good to make it optional.) There are some other problems with Gemini a

I also think that it is problematic that TLS is mandatory in Gemini. (I think it would be good to make it optional.) There are some other problems with Gemini as well, such as the lack of any equivalent of a (optional) "Content-Length" header like HTTP has, and that it uses Unicode, and a few other things. I suggested using "insecure-gemini" as the URI scheme name for the non-TLS variant of Gemini. You could have TLS and non-TLS service on the same port number, since I think that it can be distinguished from the first byte received from the client. However, TLS service programs that I have checked do not seem to have this capability.