💾 Archived View for rawtext.club › ~sloum › geminilist › 006732.gmi captured on 2024-02-05 at 10:56:39. 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 space case for transparent gemtext compression

Stephane Bortzmeyer stephane at sources.org

Sat Jun 19 09:59:14 BST 2021

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

On Sat, Jun 19, 2021 at 02:15:45AM -0500, Christian Seibold <krixano at mailbox.org> wrote a message of 3 lines which said:

If you're using zips, Lagrange doesn't take 4 user actions, it takes

1. If other browsers don't have this functionality, then tell

them. Browsers should implement this, not the protocol. It's that's

simple.

If I understand correctly your proposal, you suggest to change,neither the protocol nor the gemtext format, but to push browserauthors to recognize text/gemini+gzip and act accordingly.

In that case, I see two issues:

• how the end user of a browser without compression support will knowin advance if the file is compressed or not? From the file extension?It is not always present.

=

ilovecompression.gmiz I cannot read it=

plain.gmi I can read it

• today, every browser can read every Gemini file. Your proposalseems to imply that some users will now see only a part of theGeminispace, the uncompressed one. This is the same problem we havewhen trying to use the Web with lynx or dillo: we can see only a partof it.