-- Leo's gemini proxy
-- Connecting to bbs.geminispace.org:1965...
-- Connected
-- Sending request
-- Meta line: 20 text/gemini; charset=utf-8
Also @skyjake that gitlab link is helpful discussion, and provided another interesting read. thx
May 02 · 4 weeks ago
I like your proposal but also I would like to consider a couple of additions.
First, the initial hash sign in the URL must not denote the level of "heading" we're trying to link, but rather is the standard fragment delimiter in the URL: see https://en.wikipedia.org/wiki/URL.
Second, the actual fragment should be URL-encoded. This would mean that for a triple subheading you would require the hash symbol that separates the fragment plus 3 hash symbols for the header, but these are encoded. This would also allow for spaces or any other text in the header.
Finally, I think clients are already forced to not send fragments in their requests and servers are forced to reject requests that include one, so that part is covered.
Example: to link to "## My second level header" in "capsule.org/home" you would request "gemini://capsule.org/home#%23%23%20My%20second%20level%20header".
Anchors — This is a question about the limitations on the gemini protocool. It isn't a criticism or a complaint, more of ... seeking understanding. Why doesn't the gemini protocool have anchors? I don't mean the <a href='link'> part of the "anchor" tag, but the <a href="#anchor_on_this_page'> sort. I remember this was one of the first bits about HTML that struck my interest when I was learning it back in the day. You could have a table of contents at the beginning of a document, and then link...
-- Response ended
-- Page fetched on Sun Jun 2 18:31:23 2024