💾 Archived View for rawtext.club › ~sloum › geminilist › 006177.gmi captured on 2023-09-08 at 17:04:35. Gemini links have been rewritten to link to archived content

View Raw

More Information

⬅️ Previous capture (2021-11-30)

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

<-- back to the mailing list

Will Gemini ever become a standardized protocol?

Genro gemini-lists.orbitalfox.eu at box559.com

Thu Mar 25 08:25:53 GMT 2021

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

almaember wrote on 2021-03-25 12:26 a.m.:

On Thu, 25 Mar 2021 02:13:02 +0000
Jordan <jordan at crowesnest.io> wrote:
Eh, I couldnt care less if it does or not. What would the big
benefits be if it does?
-------- Original Message --------
On Mar 24, 2021, 6:16 PM, almaember wrote:
Hello,
I was wondering. Right now, Gemini uses a non-registered protocol
schema (gemini://) and a non-registered MIME-type (text/gemini).
The specification is a self-identified "pseudo-specification", and
is often not specific enough, leading to a number of de facto
standards, and the main website took a descriptive approach, and
simply collected[1] these "standards".
I understand that this is a very young protocol, but I wanted to
post this question anyway. Do you think Gemini will ever become a
standard? Even if not a standard published by a big organization
like the ISO, ECMA, IETF or IEEE, will text/gemini and the gemini
url scheme ever be registered with the IANA?
Cheers,
almaember
[1]: https://gemini.circumlunar.space/docs/best-practices.gm
One benefit would be a more definitive standard. We could also register
the port so no other software will use it.
And Gemini might also get into projects like cURL.

The port is already registered - to someone else.

Port 1965 has been assigned for years to "qsm-gui."

See https://www.iana.org/assignments/service-names-port-numbers/service-names-port-numbers.xhtml?&page=19