💾 Archived View for bbs.geminispace.org › u › mbays › 1232 captured on 2024-08-31 at 14:04:00. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2024-05-26)
-=-=-=-=-=-=-
Re: "THE GEMINI PROTOCOL SEEN BY THIS HTTP CLIENT PERSON"
@skyjake Solderpunk has the final say, agreed. This would just be to hash out again exactly what is unclear in the spec and see if there can be some consensus on how it should be clarified.
2023-05-29 · 1 year ago
🦀 jeang3nie · 2023-05-30 at 18:53:
@stack1 exactly.
😎 flipperzero · 2023-05-30 at 22:09:
I replied a messload to this whole thing through so many diff platforms. I'll leave a very summarized one here.
I think the guy's heart is in the right place, but he's missing the spirit entirely. The whole thing breathes an air of unwarranted self-important presumed authority. That said, I think there are valid criticisms in terms of security certification or file transfer (although I resent they assume it's ALL text/plain, being the mod of s/music smfh) but some of which @skyjake 's apps have given very accessible solutions to.
That's about it for my say in this, i'm sure i'll have more to post about later lolol.
🧩 ERnsTL · 2023-07-12 at 18:55:
Greetings everyone, the Gemini feature for curl is at risk of being closed: https://github.com/curl/curl/pull/11170 Any takers?
THE GEMINI PROTOCOL SEEN BY THIS HTTP CLIENT PERSON — This is a very interesting blog post by curl maintainer Daniel Stenberg. The suggestions he has for the Gemini protocol are summarized below: * 1. Split the spec into three separate ones: protocol, URL syntax, media type. Expand the protocol parts with more exact syntax descriptions and examples to supplement the English. * 2. Clarify the client certificate use to be origin based, not host name. *