Hmm. Perhaps we have a little bit of wiggle room, but my reading of RFC 3986 section 2.2 leads me to believe that, if nothing else, the characters: ":", "/", "?", "#", "[", "]", and "@" are reserved characters in the generic URI scheme (which I presume means they are also reserved in all protocol-specific schemes), so if those appear in a client's response to a query prompt, they *need* to be encoded 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, but IMHO it's barely even up for discussion how to proceed here - we do it how HTTP does it so we can leverage the pre-existing libraries in every programming language under the sun, in keeping with the idea that Gemini machinery should be easily assembled from existing parts as much as possible. Cheers, Solderpunk
---
Previous in thread (4 of 11): 🗣️ Natalie Pendragon (natpen (a) natpen.net)
Next in thread (6 of 11): 🗣️ Natalie Pendragon (natpen (a) natpen.net)