<-- back to the mailing list

a space case for transparent gemtext compression

Christian Seibold krixano at mailbox.org

Sat Jun 19 12:05:22 BST 2021

- - - - - - - - - - - - - - - - - - - 
I'm not too too sure about this. As I see it, using *any* file type
other than text/gemini as default choice for the content will break the
geminispace.
Gemini browser have to implement text/gemini[0], not text/gemini+gzip,
text/html or text/x-markdown, and if text/gemini+gz (or whatever) starts
to gain a bit of popularity it *will* break the geminispace IMHO.
and I totally agree with you here. You can serve any type of content
over Gemini, so what's all this fuss about? You have a strange use case
where you need compression? Fine, you can do it. Good for you. But
please don't waste our time by telling how much cool would be to change
every browser just to read the usual 1-2K[1] pages.

Read the whole thread. I never once suggested compressed gemtext should be default. I suggested it can be supported in some clients when clicking on a link. Other people are having a problem with this, not me. I fully support sending compressed files over gemini, because it's allowed by the spec.