Email or username:

Password:

Forgot your password?
daniel://'s posts Post Back to profile
Top-level
nytpu

@bagder
> Its quite similar to going back to GOPHER.
It should be noted that Gemini was literally intended as “Gopher but with TLS and more palatable markup” rather than anything related to modern HTTP.

However your other points not related to the markup/visual style are perfectly accurate IMHO

28 May 2023 at 14:28 | Wall-to-wall | Open on tilde.zone
4 comments
nytpu

@bagder 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.

@bagder 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...

28 May 2023 at 14:51 | Open on tilde.zone
daniel:// stenberg://

@nytpu yeah, it seems totally crazy to me and seriously under-documented what exactly it means

28 May 2023 at 14:55 | Open on mastodon.social
tomasino

@bagder @nytpu agreed. that was one of the most frustrating bikeshedding decisions. Nobody chiming in really understood the complexity of the URI spec or the implications of what they were proposing, and it went totally against the other goals of the project.

Using TLS, for instance, was chosen because library support was so common and accessible it lowered the barrier to server and client creation. Tweaking URL parsing made things harder without any tangible benefit.

I hope that gets scrapped, personally. And yes, carving the spec into 2 (protocol and document format) has been discussed already and piloted. It just hasn't made its way back to the official living document. That would help as well.

Where I think we'll probably see more pushback is on TOFU (I fully support DANE, but DNSSEC is still such a barrier), and chunking. There's a major philosophy of 1-request-per-document which seems antithetical to chunking.

Regardless, all 100% valid criticism and from one of the most reputable sources. I'm sure the whole community will be discussing this for weeks to come. Cheers!

@bagder @nytpu agreed. that was one of the most frustrating bikeshedding decisions. Nobody chiming in really understood the complexity of the URI spec or the implications of what they were proposing, and it went totally against the other goals of the project.

Using TLS, for instance, was chosen because library support was so common and accessible it lowered the barrier to server and client creation. Tweaking URL parsing made things harder without any tangible benefit.

28 May 2023 at 15:01 | Open on tilde.zone
daniel:// stenberg://

@tomasino @nytpu in fact, using plain old CA is the *least* complex and most established system and way more secure than TOFU...

Thanks for the comment. I fully understand that my views and opinions may not align very well with many of the people in and fans of the Gemini project.

28 May 2023 at 15:06 | Open on mastodon.social
Go Up