💾 Archived View for rawtext.club › ~sloum › geminilist › 001621.gmi captured on 2020-09-24 at 01:45:34. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
Felix Queißner felix at masterq32.de
Sat Jun 13 11:38:06 BST 2020
- - - - - - - - - - - - - - - - - - -
Hey Sean and others!
*snips the whole protocol description*
I was too working on a gemini extension to allow arbitrary data uploadsas "10 INPUT" is a bit too restricted to ~700 byte of data payload.
But now that i read your gemini+put and gemini+delete extension, i thinki don't need to continue braining over my extension and it's flaws.
I really like the proposal. It's easy to implement and integrate both onserver and client side.The "gemini+delete" scheme is just the normal gemini handling routineand the upload routine can be put "in front" of a normal gemini requestand can be handled with the normal response handler.
The idea is for a user to be able to use a Gemini client to not only
browse Gemini content, but *create* and upload new content to a
server, from within the client (a client can shell out to an editor,
for instance). This should reduce the friction of generating content.
Yes, that was my vision as well. Allow users to write and update theirgemlogs from within a client. Right now, i'm sshing into my server andauthor all the files by hand. But just opening Kristall, going to mygemlog, activating my "editor certificate" and just start editing mysite is just appealing!
Regards- xq