💾 Archived View for rawtext.club › ~sloum › geminilist › 002958.gmi captured on 2020-10-31 at 14:53:37. Gemini links have been rewritten to link to archived content

View Raw

More Information

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

<-- back to the mailing list

Using netcat with gemini (was Re: A question regarding the spec)

Philip Linde linde.philip at gmail.com

Wed Oct 28 18:22:13 GMT 2020

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

On Wed, 28 Oct 2020 13:51:50 -0400Chris Vittal <chris at vittal.dev> wrote:

The issue here is that the URL text of 'gemini.circumlunar.space' is not
an absolute URL. It has no scheme, no authority, and a path of
'gemini.circumlunar.space'. The spec does state that the scheme is
unnecessary, but the authority is.

I think the confusion around this stems from the phrasing in the Geminispec where on one hand it says that the scheme may be omitted but onthe other hand that in that case "gemini://" is implied, which in itswhole is more than just the scheme.

Strictly speaking, ":" is not part of the scheme, (and "//" is not partof the authority), so what we'd really end up with when omitting thescheme from the absolute URI is "://gemini.circumlunar.space".

"//gemini.circumlunar.space" is only defined in RFC 3986 as a "relativereference" as opposed to an "absolute URI".

The Gemini spec could really use some clarification here, guided by acareful reading of RFC 3986 in order to get the terminology right anddefine the allowed syntax in those terms.

-- Philip-------------- next part --------------A non-text attachment was scrubbed...Name: not availableType: application/pgp-signatureSize: 488 bytesDesc: not availableURL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20201028/76f79d98/attachment.sig>