undefined | Better HN

0 pointsfloren8mo ago0 comments

2019: Gemini introduced

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

0 comments

uamgeoalsk8mo ago

Your use of "they" here is misleading. Many, if not most, people in the Gemini community see no need for Titan. The existence of a new protocol doesn’t imply that Gemini is somehow lacking. A Gemini client that doesn’t support Titan is still a fully-featured Gemini client.

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!

florenOP8mo ago

You're right, I mischaracterized Spartan. Although it is very similar to Gemini, it's not compatible because the author decided even 2-digit response codes were foolish luxury, and as you mentioned there's the TLS thing. Of course, we still call it HTTP even when it transits a TLS connection, but that's not The Gemini Way so...

True minimalists will, of course, use the Mercury protocol: https://raw.githubusercontent.com/floren/mercury/master/SPEC

j / k navigate · click thread line to collapse