A year ago I clarified my views on the #gemini protocol. I have since been told many times that I have misunderstood it. Sure.
⇧
A year ago I clarified my views on the #gemini protocol. I have since been told many times that I have misunderstood it. Sure.
Binary Large Octopus
in reply to daniel:// stenberg:// • • •#1 trackball mouse enjoyer
in reply to daniel:// stenberg:// • • •Floating Point Error
in reply to daniel:// stenberg:// • • •I read a post of some guy roasting Gemini the other day, in parallel to completing my Gemini setup.
Apparently that person was you 😅
daniel:// stenberg://
in reply to Floating Point Error • • •Martin Rocket
in reply to daniel:// stenberg:// • • •Ed Davies
in reply to daniel:// stenberg:// • • •No, RFC 3986 is explicit that a URL is a sequence of characters. E.g., the first bullet point in 1.2.1:
A URL on a advertising bill board is not a sequence (or “set”) of octets but it's still a URL.
daniel:// stenberg://
in reply to Ed Davies • • •Ed Davies
in reply to daniel:// stenberg:// • • •daniel:// stenberg://
in reply to Ed Davies • • •@edavies I did not quote the RFC and I did not use the RFC language in my post because I was talking about how URLs actually work. Not what RFC 3986 says.
URIs are in fact 7 bit ASCII for all practical purposes, so I can't think of any real-world case where a URI character is not an octet.
"URLs" and "IRIs" however...
Ed Davies
in reply to daniel:// stenberg:// • • •Indeed.
But I still think the wording could be better to make that distinction clear so people won't be mislead. Just a prefix of “for practical purposes” would go a long way.
(Real-world exception to 7-bit ASCII octets: a few characters in SMS text messages where '[' and ']' (e.g. for an IPv6 address) are escaped. But all buried in the messaging apps so not much of a practical issue for anybody not programming those.)
BTW, I really liked the rest of your take on Gemini. I looked into it a bit quite a while ago and liked a lot, particularly the client certificate idea in principle, disliked some aspects of the markup language (lack of images in text documents) but was really uncomfortable about the scanty and mixed up specifications. Thank you for taking the time to articulate similar ideas in so much more detail than I had the patience for.