💾 Archived View for bbs.geminispace.org › s › Lagrange › 18549 captured on 2024-08-31 at 15:49:03. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2024-08-19)
-=-=-=-=-=-=-
Re: "Did you (@skyjake) consider implenting the "edit" Titan..."
I think I like this!
Jul 13 · 7 weeks ago
Considering how easy it is to accidentally implement sending a blank (size=0) titan request in a client, as seen in issue #671 in the lagrange github repo, I really wish a "delete" parameter would be added to titan. Just had a crash from my desktop a few minutes ago after implementing titan on my server and after opening up lagrange again, it sent a size=0 request to the server. This isn't a lagrange specific issue by any means. The only thing that saved me from dealing with a deleted file was seeing the issue yesterday and specifically disallowing size=0 requests as a result.
🕹️ skyjake [mod...] · Jul 14 at 03:32:
Yes, I do plan to implement it. Haven't quite just had the time yet.
There are a few Titan bugs that also need fixing in Lagrange and those will be addressed in the future, too.
I will say that if I were to create a gemini client with titan support that has a "reopen tabs from last sessions" feature, I would have implemented the client to have the exact same size=0 bug. This realization is why I wish there was something to differentiate size=0 from delete so I could continue to ignore size=0 and more unambiguously delete.
🚀 mbays [OP] · Jul 14 at 18:14:
@skyjake Thanks, that's good to hear. By the way, I noticed a bug in Lagrange: semicolons in the gemini url aren't percent-escaped when producing the titan url, so uploading from gemini://example.com/;size=5 results in a titan url with two size parameters, which is presumably intended to be invalid (though the spec doesn't explicitly say so).
Did you (@skyjake) consider implenting the "edit" Titan parameter? [gemini link] "edit" extension to Titan spec To summarise that proposal: a successful request "titan://example.org/example;edit" returns data for the user to edit, which is then submitted as a normal Titan request to the same path. I think this would make Titan editing much more usable. Without it, editing text is rather awkward. I don't see how to improve on how Bubble does it -- sending the user to a gemini page with the...