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 -0400
Chris 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 Gemini
spec where on one hand it says that the scheme may be omitted but on
the other hand that in that case "gemini://" is implied, which in its
whole is more than just the scheme.
Strictly speaking, ":" is not part of the scheme, (and "//" is not part
of the authority), so what we'd really end up with when omitting the
scheme from the absolute URI is "://gemini.circumlunar.space".
"//gemini.circumlunar.space" is only defined in RFC 3986 as a "relative
reference" as opposed to an "absolute URI".
The Gemini spec could really use some clarification here, guided by a
careful reading of RFC 3986 in order to get the terminology right and
define the allowed syntax in those terms.
--
Philip
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: not available
URL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20201028/76f79d98/attachment.sig>
More information about the Gemini
mailing list