Titan

FYI you should be aware of the Titan protocol. This lets you write to a Gemini server. Authentication is done via client certificates. So, there would need to be some scheme for associating client certificates with existing user accounts. => transjovian.org/titan Titan Protocol => https://lists.orbitalfox.eu/archives/gemini/2020/000528.html Client certificates => https://lists.orbitalfox.eu/archives/gemini/2020/000987.html Client certificate musings I was not familiar with client certificates. But the Lagrange help file has a primer in section 1.6. => https://git.skyjake.fi/gemini/lagrange/raw/branch/release/res/about/help.gmi ## 1.6 Identities (client certificates) => https://www.ssl.com/article/private-and-public-keys/ Private And Public Keys Section 4.3 of the Gemini specification also talks about client certificates. => gemini.circumlunar.space/docs/specification.gmi 4.3 Client certificates Lagrange added support for Titan in version 1.6. => https://github.com/skyjake/lagrange/releases/tag/v1.6.0 Lagrange v1.6 Release Notes Maybe Titan can be added to the todo list for Flounder. Then we would be able to interact with Flounder without requiring HTTPS or SFTP. Regards, -- Mike

On Thu, Aug 12, 2021 at 04:52:00PM -0500, Michael Mientus wrote: > FYI you should be aware of the Titan protocol. This lets you write to a > Gemini server. Hi Michael, I am loosely aware of the Titan protocol. Thanks for your email. I have two comments: First, I currently spend very little time working on Flounder, do to other obligations, so I'm not focused on new features Second, while the Titan protocol is interesting, my approach with flounder is to be very conservative about the features or extensions I implement. There are many competing "Gemini but POST" protocols, and I am waiting for things to settle a bit, where the community picks one winner, to decide which one I may want to implement. If you or someone you know wants to put together a patch for this, I would be open to it though! Alex