<-- back to the mailing list

a space case for transparent gemtext compression

Christian Seibold krixano at mailbox.org

Sat Jun 19 10:48:09 BST 2021

- - - - - - - - - - - - - - - - - - - 
I know, in my previous message replied specifically to your message vr 18 june 14:24. Is there something wrong with that?

It looked like you were replying to Johann Galle, not me, as I didn't mention the specific compression you were talking about - I deliberately kept my message more general. I did, however, read about what you wanted.

The Gempub doesn't load immediately and I suspect there will always be the extra download and open step. Of course I can send patches, fork browsers or roll my own gemini client and encourage people to additionally compress their individual gemtexts with PPMd and their capsule with Gempub.

Yes, **currently** it takes multiple steps for lagrange to open a zip, but my point is it CAN be instant without having to implement it in the protocol. It absolutely *can* be implemented in client so that it's instant.

Anyways, you can make suggestions to skyjake on Station or on the lagrange github (https://github.com/skyjake/lagrange) so that it can be made more instant. There will always be 1 extra step (the "download and open" button) due to the fact that zips are more like a compressed directory - that is unless we figure out how to fix the url handling of things within zips. However, compressed single files can absolutely be instantly decompressed by a client that implements this.

Also, if TLS 1.3 has compression (thanks for telling me that, I didn't know that), then it makes supporting specific compressions in clients unnecessary, because we are going to be switching to TLS 1.3 in the future, from what I've gathered.