Re: a space case for transparent gemtext compression

• 🗣️ From: Stephane Bortzmeyer (stephane (a) sources.org)
• 📅 Sent: 2021-06-19 08:59
• 📧 Message 17 of 50

On Sat, Jun 19, 2021 at 02:15:45AM -0500,
 Christian Seibold <krixano@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 browser
authors 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 know

in 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 proposal

seems to imply that some users will now see only a part of the
Geminispace, the uncompressed one. This is the same problem we have
when trying to use the Web with lynx or dillo: we can see only a part
of it.

---

Previous in thread (16 of 50): 🗣️ Christian Seibold (krixano (a) mailbox.org)

Next in thread (18 of 50): 🗣️ Christian Seibold (krixano (a) mailbox.org)

View entire thread.