💾 Archived View for bbs.geminispace.org › u › skyjake › 2196 captured on 2023-11-04 at 16:58:27. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2023-09-28)
-=-=-=-=-=-=-
You should think of Titan as fully equivalent to Gemini, but when making a request, the client gets to append a payload as well.
So Titan can totally be used for reading resources, too. I think the only missing part here is to instruct the client exactly what happens when opening a titan:// link. Currently the only defined behavior is to ask the user to provide the payload (with token & MIME) and then submit the request.
So what we need is for the client to know that it can just submit the titan:// request as is first without a payload, then receive the data from the server, and finally redo the request with the payload.
2023-06-18 · 5 months ago
— Let the record show that this discussion was continued in the fediverse...
Maybe I'm missing something: why doesn't i.e. titan://domain.tld/resource/raw work?
edit: Definitely missed it. The issue, I gather, is that the resource isn't requested over Titan. Okay. So instead, does Titan allow arbitrary parameters in the URL (i.e. next to ;token=)? Could one of those be defined in Titan to hint to clients to get the resource from Titan first?
2023-08-07 · 3 months ago
Editable gemini pages — I reconsidered my earlier ideas about editable gemini pages based on @skyjake's feedback. Now I'm thinking that a response code of "21" (Success+Editable) could indicate that the response body could be edited and uploaded via the titan protocol at the same URI used to make the request. This allows a client to know when a page can be loaded into a large editor window and uploaded as one body using the titan protocol. A response of "21" can be treated the same as a...