💾 Archived View for rawtext.club › ~sloum › geminilist › 001024.gmi captured on 2020-10-31 at 01:59:44. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2020-09-24)
-=-=-=-=-=-=-
solderpunk solderpunk at SDF.ORG
Sun May 24 18:33:03 BST 2020
- - - - - - - - - - - - - - - - - - -
Hmm. Perhaps we have a little bit of wiggle room, but my reading of RFC3986 section 2.2 leads me to believe that, if nothing else, thecharacters:
":", "/", "?", "#", "[", "]", and "@"
are reserved characters in the generic URI scheme (which I presume meansthey are also reserved in all protocol-specific schemes), so if thoseappear in a client's response to a query prompt, they *need* to beencoded some how - and for obvious reasons!
You're right, however, that exactly how they are encoded is up to us.That's a surprise to me! So the spec will have to address this, butIMHO it's barely even up for discussion how to proceed here - we do ithow HTTP does it so we can leverage the pre-existing libraries in everyprogramming language under the sun, in keeping with the idea that Geminimachinery should be easily assembled from existing parts as much aspossible.
Cheers,Solderpunk