๐Ÿ’พ Archived View for bbs.geminispace.org โ€บ u โ€บ mbays โ€บ 1221 captured on 2023-09-28 at 20:04:43. Gemini links have been rewritten to link to archived content

View Raw

More Information

โฌ…๏ธ Previous capture (2023-09-08)

โžก๏ธ Next capture (2023-11-04)

๐Ÿšง View Differences

-=-=-=-=-=-=-

Re: "THE GEMINI PROTOCOL SEEN BY THIS HTTP CLIENT PERSON"

Comment in: s/Gemini

Maybe we should take this opportunity to finish here the work started on gitlab of finalising the spec? I don't know how well Bubble will work for this kind of discussion, but it's at least more accessible than javascripty gitlab. If we can reach clear reasoned community consensus on the remaining (small) issues, we can hope that Solderpunk would approve and incorporate them into the official spec.

๐Ÿš€ mbays

2023-05-29 ยท 4 months ago

6 Later Comments โ†“

๐Ÿต michaelnordmeyer

@mbays Gitlab seems deprecated. The spec over there is outdated. Somewhere in the Gemini FAQ points to git://gemini.circumlunar.space/gemini-site

๐Ÿš€ skyjake

@mbays I think the problem with anyone else but Solderpunk finishing the spec is not with any technical solution, no matter how well-suited. No one but Solderpunk has the authority to do that work.

At best I could see an unofficial community-blessed "amendment" being put forth as a delta on top of the circumlunar specification, purposefully contradicting nothing in the official spec but just tightening things up based on experience from actual server and client implementations. Solderpunk might then at some point be interested in incorporating some of those things into the official specification.

๐Ÿš€ mbays

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

๐Ÿฆ€ jeang3nie

@stack1 exactly.

2023-05-30 ยท 4 months ago

๐Ÿ˜Ž flipperzero

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

Greetings everyone, the Gemini feature for curl is at risk of being closed: https://github.com/curl/curl/pull/11170 Any takers?

2023-07-12 ยท 3 months ago

Original Post

๐ŸŒ’ s/Gemini

โ€” My copy

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. *

๐Ÿ’ฌ satch ยท 16 comments ยท 12 likes ยท 2023-05-28 ยท 4 months ago