💾 Archived View for rawtext.club › ~sloum › geminilist › 007588.gmi captured on 2024-02-05 at 10:35:42. Gemini links have been rewritten to link to archived content

View Raw

More Information

⬅️ Previous capture (2021-11-30)

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

<-- back to the mailing list

A Writeable Gemini

indieterminacy at libre.brussels indieterminacy at libre.brussels

Thu Nov 11 15:16:24 GMT 2021

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

skyjake <skyjake at dengine.net> writes:

On 11. Nov 21, at 9.17, Balázs Botond <balazsbotond at gmail.com> wrote:
Btw, what was the motivation to limit input length to 1024 bytes in
the first place? I can't find anything about it in either the FAQ or
the specification.
Here's a relevant post from the archives where Solderpunk comments on the limit: https://lists.orbitalfox.eu/archives/gemini/2020/001672.html
An interesting thread to read, ta!
IMO, uploading content via URL query strings is not a great idea
because you must percent-encode all of it, and that can increase the
size quite a bit. Better to use alternate methods to upload a "raw"
octet stream.

I must admit having not touched octet streams before (whether raw orwell-cooked), what am I missing out on? Does anybody have pointers/suggestions?

I noticed a nice downstream post from Sean Conner, concerning hisexperience publishing via emails to his server=

https://lists.orbitalfox.eu/archives/gemini/2020/001722.html 2020-06-16 gemini+submit:// (was Re: Uploading Gemini content)

I get this approach a little more readily. Im wondering whether apublic-inbox type approach would be interesting:=

https://public-inbox.org/

Equally so, given its symbiosis with Grokmirror=

https://github.com/mricon/grokmirror
--jaakko

Jonathan