💾 Archived View for rawtext.club › ~sloum › geminilist › 007679.gmi captured on 2024-03-21 at 15:40:49. Gemini links have been rewritten to link to archived content

-=-=-=-=-=-=-

Documents with mixed languages

Krixano krixano at protonmail.com

Mon Dec 13 11:21:44 GMT 2021

- - - - - - - - - - - - - - - - - - -

Yeah, some people don't know Gemini History apparently, lol.

People need to stop imposing their views on the standard as if it was part of the original design of the protocol when it wasn't. Solderpunk could change things at any time, of course, but that doesn't change the original designs. So... No, as far as I'm aware, Gemini was never about read-only. It was about balancing the power-to-weight ratio. No, Gemini's text input was never exclusively for search - there's an article written by Solderpunk that details why he included input labels. No, Gemini was never anti-applications (at least since the idea of Client Certificates). Solderpunk wrote an article showing that applications were at least considered as a potential for the protocol. Also, no, having (text, and others) streaming and browsers that interact with streams in Gemini is not against the intended spec. In fact, allowing for Text Streaming was a decision talked about between Solderpunk, Tomasino (iirc), Mozz, and a few other people. Solderpunk references this feature in one of his recent emails here on the mailing list (regarding how close_notify doesn't affect streaming via Gemini).

Now, about what the spec states. If you read the spec too literally and linearly, then I can kinda see how people might think the spec says requests must be handled after close_notify, from:

C: Opens connection

S: Accepts connection

C/S: Complete TLS handshake (see section 4)

C: Validates server certificate (see 4.2)

C: Sends request (one CRLF terminated line) (see section 2)

S: Sends response header (one CRLF terminated line), closes connection under non-success conditions (see 3.1 and 3.2)

S: Sends response body (text or binary data) (see 3.3)

S: Closes connection (including TLS close_notify, see section 4)

C: Handles response (see 3.4)

I firmly believe that this is an undesired overly-linear interpretation, and that perhaps Solderpunk might want to consider changing this if necessary, and if his views on streaming haven't changed. Remember, the spec isn't actually final yet.

As for the links:On Inputs and Client Certificates: gopher://zaibatsu.circumlunar.space:70/0/~solderpunk/gemini/inputs-and-client-certs.txtOn Streaming (Tomasino): gemini://rawtext.club/~sloum/geminilist/001696.gmiOn Applications and Streaming (Solderpunk): gemini://gemini.circumlunar.space/users/solderpunk/gemlog/a-vision-for-gemini-applications.gmiMozz's Response to Solderpunk on Streaming: gemini://mozz.us/journal/2020-06-21.gmi

Links via Gemini:On Inputs and Client Certificates: gemini://zaibatsu.circumlunar.space/~solderpunk/gemini/inputs-and-client-certs.txtOn Streaming (Tomasino): [Only Available Via Gopher, afaik]On Applications and Streaming (Solderpunk): gemini://gemini.circumlunar.space/users/solderpunk/gemlog/a-vision-for-gemini-applications.gmiMozz's Response to Solderpunk on Streaming: [Only Available Via Gopher, afaik]

Christian Seibold