💾 Archived View for rawtext.club › ~sloum › geminilist › 007603.gmi captured on 2023-09-28 at 16:17:30. Gemini links have been rewritten to link to archived content

View Raw

More Information

⬅️ Previous capture (2021-11-30)

-=-=-=-=-=-=-

<-- back to the mailing list

Uploading content over gemini

Philip Linde linde.philip at gmail.com

Mon Nov 15 01:44:13 GMT 2021

- - - - - - - - - - - - - - - - - - - 

On Thu, 11 Nov 2021 23:03:02 -0500Alex <alex at alexwennerberg.com> wrote:

While both of these are technically feasible, they are a bit wonky, and for large files would involve many requests. What I’m wondering is whether these are ideas worth considering — ways to upload files without extending or replacing Gemini. Any thoughts?

Hi Alex,I think it's fine if Gemini remains a tool primarily to download anddisplay text and other files. As such, there is no need to "replace"Gemini because it's out of scope of the protocol. That said, and I'vethink I've actually seen an example of this before, within the currentspec you could implement a line oriented editor, in the style of ed(1)using 1x status responses. Documents could then not just be uploaded,but authored directly within Gemini.

A sufficiently smart client™ could format a local document as asequence of inputs to such a line based editor. For that kind of use itdoesn't need to be complex. Just a way to open an editing session, away to open a new line, a way to append to the current line and a wayto terminate the editing session. E.g.

c: gemini://example.com/document/edits: 3x to gemini://example.com/document/edit/session/afdef947f9s: Repeated 1x responses until terminated or session timeout

oHello! this is the first line, opened with "o"+ and this is its continuation, added with "+"oThis is the next line.oThe next input after this terminates the session, with ".":.

This will of course generate many requests, but at the cost of sensiblehuman use you could allow escape codes to indicate line feeding, so youcould use all the space allowed in a request

Another idea is to use email. Blog-by-email if you will, orcomment-by-email could be implemented as an automatic process. Butrunning an email server may not be a walk in the park. This seems moresensible to me, but I'm not looking to run my own mailserver. Maybe atool could regularly connect to an existing IMAP server and work withthat.

-- Philip