> The more people play with Gemini, the more they'll want to "extend" it... and the closer they'll bring it to HTTP
Then it's not Gemini. Interestingly this is why it was decided for Gemini not to have a protocol version. To prevent extension.
Then it's not Gemini. Interestingly this is why it was decided for Gemini not to have a protocol version. To prevent extension.
2022-ish: Titan created (based on existed of https://web.archive.org/web/20220126075826/https://transjovi...).
The spec for Titan (https://portal.mozz.us/gemini/transjovian.org/titan/page/The...?) appears to be an implementation of PUT for Gemini, but since Gemini doesn't have verbs (GET is implied) it does it by creating a whole new "protocol" titan://
So you're right, they didn't extend the Gemini protocol, they created an entirely new protocol which many clients, servers, and libraries now implement because the functionality was desirable.
Wonder what they'll call the protocol that implements DELETE... maybe Deorbit?
Edit: oh there's also Spartan (2022), another protocol which is Gemini but if there are bytes after the request line, it's an implicit PUT: https://raw.githubusercontent.com/michael-lazar/spartan/refs...
Additionally, your description of Spartan is simply incorrect. There are several significant differences between it and Gemini - the most obvious being that Spartan doesn’t use TLS at all!
True minimalists will, of course, use the Mercury protocol: https://raw.githubusercontent.com/floren/mercury/master/SPEC