Earlier quoted context omitted.
> If you bothered writing a spec, it might as well be unambiguous, no? Sure, people want unambiguous specs. However there is a list of literally dozens of working clients, servers, and libraries that were implemented based on the Gemini spec as is. Perhaps Daniels concerns are, in practice, not as important? https://github.com/kr1sp1n/awesome-gemini#clients I would also point out the hell that is the HTTP/1.0 and HTT…
Stating that it's easy to develop clients and servers for Gemini is fine. But it's not how curl works. IF a feature is to be accepted, it will have to be maintained for a long time. In fact, it would not surprise me that curl's eventual implementation will be regarded as a sort of reference, simply because curl is such a well-regarded project. So it's really important to get this right. And the spec is the only reali…
Re: The Gemini protocol seen by this HTTP client person
#111Can you provide a link to that ban threat story?