💾 Archived View for rawtext.club › ~sloum › geminilist › 007597.gmi captured on 2023-12-28 at 15:55:50. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2021-11-30)
-=-=-=-=-=-=-
Alex Schroeder alex at alexschroeder.ch
Fri Nov 12 09:24:16 GMT 2021
- - - - - - - - - - - - - - - - - - -
I think that Titan exists and is on the same level of complexity as Gemini, and it’s used in Lagrange, Elpher with Gemini Write, and a bunch of command line tools.
I think the details of POST requests are tricky: another encoding, parameters in the headers, parameters in the body. Even a PUT might be simpler. But again, you have header parameters to consider. In a way, Titan is just a PUT request with a fixed number of headers (parameters). It’s the perfect trade off.
But as I wrote on https://alexschroeder.ch/wiki/2021-11-05_Capsules_for_Phoebe:
“after yet another discussion on the Gemini IRC channel where people said that the Titan protocol was a bad fit for Gemini, or that it was only fit for the particular wiki needs I had, or that writing stuff on Gemini via the web or uploading files via FTP or SCP was good enough. Well, I disagree. And not only do I disagree, but I wrote plenty of solutions:
Titan, obviously – I made it central to Phoebe; I wrote a command line client; I wrote an extension called Gemini Write for Elpher, an Emacs-based Gemini clientSpartan – out of curiosity, I implemented a Spartan plugin for Phoebe; I wrote a command line clientHTTPS – I implemented a web plugin for Phoebe, both for browsing and for editingWebDAV – I implemented a WebDAV plugin for Phoebe and made sure it worked for both cadaver and Gnome FilesHopefully it is understandable that I have little patience for people complaining about the existing solutions. There are so many of them, all I want to see is people supporting anything, anything at all, for their clients.
Luckily, thankfully, @jk has added Titan support to Lagrange.”
I would love for these endless circular discussions to end one day and for people to just write the client they want. Perhaps this is the main problem: people keep thinking about new ways to upload content because they don’t see many clients supporting it, thinking that the existing ideas must be too complex. But that is not true. I even implemented the Iapetus proposal for both client and server! All these proposals don’t need to be discussed, they just need to be implemented – and as I have shown, I think they can be implemented faster than they can be discussed on the mailing list, IRC, or anywhere else.
Just do it.
I ended up writing instructions on how to use it for my capsules (i.e. not wikis), in case you haven’t tried Lagrange:
https://transjovian.org:1965/phoebe/page/Capsules
https://transjovian.org:1965/phoebe/page/Capsule%20update%20using%20Lagrange%20on%20the%20phone
https://transjovian.org:1965/phoebe/page/Capsule%20update%20using%20Lagrange%20on%20the%20desktop
Here’s the Emacs Lisp code I used to add Titan to Elpher:
https://alexschroeder.ch/cgit/gemini-write/about/
Here’s a short video of how it can look:
https://alexschroeder.ch/videos/gemini_write_demo.mp4
Cheers
Alex