Scheme Section 2 quibble

[Philip Linde]

On Tue, 17 Nov 2020 16:07:08 -0700
Alex // nytpu <alex at nytpu.com> wrote:

> I'm going to use a real-world example here because people seem to not
> get why this may be a problem.
> 
> Let's say I want to start hosting the git repo for my utility
> gemlog.sh[a] on gemini. I make a directory on my site, so the full url
> would be `gemini://nytpu.com/gemlog.sh/`. Now, say I put a link in my
> root index.gmi (`/`) linking to `gemlog.sh`[b]. This is a perfectly
> valid link to a directory on my server, but this would instead be
> interpreted as the url `gemini://gemlog.sh/` if you use the faulty
> method of parsing. (`.sh` is a valid TLD[c] so it wouldn't work even if
> you have a whitelist of tlds).

I think that we all actually agree that this can't possibly work for
links. What Ali Fardan is suggesting is to allow suffix references only
in requests, where the ambiguity could be avoided for the simple reason
that the request must contain an authority.

I completely disagree that suffix references should be used anywhere,
but the suggestion is not quite so outlandish as to require any of
options 1-3. It should be avoided for the simple reason that it
precludes option 4.

-- 
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/20201118/3a7d4b0d/attachment.sig>