💾 Archived View for rawtext.club › ~sloum › geminilist › 005797.gmi captured on 2024-02-05 at 11:06:55. Gemini links have been rewritten to link to archived content

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

[spec] List of proposed clarifications

Stephane Bortzmeyer stephane at sources.org

Mon Mar 1 10:37:03 GMT 2021

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

On Sun, Feb 28, 2021 at 10:23:12AM -0500, Adnan Maolood <me at adnano.co> wrote a message of 10 lines which said:

I'd like to keep track of proposed clarifications to the Gemini

specification, since they seem to get buried in the mailing list. So

I've made a list and published them on my capsule:

=

gemini://adnano.co/gemini-spec-proposals/

Now that we have an issue tracker to follow the work on the finalspecification <https://gitlab.com/gemini-specification>, you may wantto turn this page into tickets at this issue tracker and/or to addticket numbers and links in your page.

From your list:

https://gitlab.com/gemini-specification/protocol/-/issues/3 Clarify that META cannot be empty=

https://gitlab.com/gemini-specification/protocol/-/issues/3 Clarify that META cannot contain LF before the final CRLF=

TODO Clarify that Gemini URL queries MUST (not SHOULD) use %20 instead of +=

https://gitlab.com/gemini-specification/protocol/-/issues/2 Clarify that servers MUST send TLS close notify before closing the connection=

TODO Clarify that clients MUST NOT send fragments to the server [IMHO, RFC 3986, section 3.5 is clear enough]=

TODO Clarify the purpose of alt text