in reply to waso nytpu

mastodon - Link to source

waso nytpu

Hmm, and regarding the UTF-8 URLs, IIRC there was a big debate in the mailing list about whether or not clients should punycode IDNs, or transcode them to a different encoding, or just verbatim pass all URLs; and Solderpunk decided to just UTF-8 encode all URLs over the wire which is IMO not any better and possibly worse. Introduces lots of complexity: should clients normalize the Unicode (IME more complex and difficult than punycoding), and if so with what strategy? Should you still percent-encode the path or can you now leave that unencoded too? Lots of issues.
This entry was edited (1 year ago)
in reply to daniel:// stenberg://

mastodon - Link to source

dressupgeekout 🦓

I love Gemini to bits, and I host my own server and everything, but the fact TLS is a REQUIREMENT from Day 1 has kinda bugged me to be honest.

If I were to write my own Gemini client (which is supposed to be 'easy') then I'd have to have all the crypto bits in place before I can ensure my code is on the right track to verify I can even make a proper connection at all. I guess I owe it to myself to be better acquainted with TLS in practice, but, meh, I wish I didn't NEED to.

Also, Gemini feels like a PERFECT FIT for retro computers to disseminate and consume information over the internet... except the TLS bits make it out of reach! I would love to be able to surf across Gemini on my old Atari ST, but with only 1 MB of RAM and a 8MHz CPU I'm not sure how feasible that is without some kind of proxy -- which you correctly state in your article has problems in itself.

in reply to daniel:// stenberg://

pleroma - Link to source

MCMic

I do not get your point about utf8 in URI. There was a big debate on utf8 in domain part and wether to punycode, which I kind of lost I think, but for the path part I do not see the ambiguity, you encode as utf8. and percent escaping is also allowed.
But you take an example where you have data and you do not know its encoding, then it's useless data, no? If you have to guess encoding it means a non-utf8 uri would not have helped, the guessing would have happenned on server side?
in reply to daniel:// stenberg://

mastodon - Link to source

HD Moore

It reads like you spent more time critiquing the spec than the developers spent implementing it. It rings of “but my protocol will be cooler and more exclusive” while ignoring why we have the current state. Gemini would be better off as a subset of the current web (http+tls+their silly media format). I have similar concerns around IPFS, where the p2p and content-addressed URIs encourage vs avoid censorship and surveillance (also the p2p base protocol is a free ddos net, wee).
⇧