It is what I thought too; if it should be reinvented, it should be done properly. (Although, I still think TCP will do; it is not necessary to change it to UDP

It is what I thought too; if it should be reinvented, it should be done properly. (Although, I still think TCP will do; it is not necessary to change it to UDP instead.) Comment 45393083 has some of my comments about this Gurted. There is another discussion at: gemini://bbs.geminispace.org/s/SmallWeb/15126 (connect to port 1965 with TLS and send the full URL followed by CRLF) I think Gemini was designed to be between Gopher and WWW (and it is not so bad, although I would have made the TLS optional instead of mandatory; from my experience, I am not the only one). I designed Scorpion to be between Gemini and "WWW as it should be if it was designed better", which has the result of being neither a subset nor superset of the capabilities of Gemini or of WWW (as well as doing things that I considered to be useful enough to keep, such as range requests (although, for simplicity, I allowed only a single range per request, rather than the multiple ranges per request that HTTP does)). I also think that it is useful to use different protocols (and different file formats) for different uses; e.g. for some types of games (and for live chat services) it would probably be better to use an interactive session such as Telnet or SSH (or IRC, in the case of chat) rather than using HTTP or Gemini (even though both are used).