Comments on 2019-06-21 Solderpunk's Gemini Protocol

I am not sure I understand the problem you’re trying to solve. What you’re doing here is basically reinventing HTTP/1.0. There is nothing wrong with HTTP, it is a very simple, text based protocol. Easily extendable. Has a lot of clients available.

I don’t think what drew you to gopher in the first place was the transfer protocol. It was the limitation to text. You can transfer text via HTTP. HTTP isn’t the bloated mess you like to avoid, text/html is.

Andreas Gohr 2019-06-21 23:23 UTC


Yeah, perhaps you are right. HTPP/1.0 didn’t include virtual hosts, chunked encoding, and many other things. But there are already small complications:

  1. content coding for compression
  2. multipart types are left open
  3. referrer heading is suggested
  4. user agent heading is suggested

But with just a few small tweaks I could write a simple http server without any features. 🙂

And I could specific that the request method is optional and defaults to GET and that the protocol version is optional and if not provided, no further request headers are expected... and it should all work. 🤔

– Alex Schroeder 2019-06-22 11:29 UTC


Reply by Solderpunk.

– Alex Schroeder 2019-06-22 19:47 UTC


Please make sure you contribute only your own work, or work licensed under the GNU Free Documentation License. Note: in order to facilitate peer review and fight vandalism, we will store your IP number for a number of days. See Privacy Policy for more information. See Info for text formatting rules. You can edit this page if you need to fix typos. You can subscribe to updates by email without leaving a comment.

To save this page you must answer this question:

Please say HELLO.