💾 Archived View for rawtext.club › ~sloum › geminilist › 006766.gmi captured on 2023-11-14 at 09:06:56. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2021-11-30)
-=-=-=-=-=-=-
Francis Siefken fsiefken at gmail.com
Sun Jun 20 09:36:52 BST 2021
- - - - - - - - - - - - - - - - - - -
2021 06 19 15:23 mbays <mbays at sdf.org> wrote:
If I understand correctly, TLS 1.3 actually *removed* compression.
Yes, I saw it, I erred - such a disappointment. So in the absence ofa protocol specification that leaves mime-type handling by the client usingtwo seperate gmi files, but as Peter Much remarked somewhere else in thisthread that doesn't cover compression of dynamic cgi data streams (which isless of a use case for gemini perhaps - unless).
P.S. here's how one could handle gzipped gemtext in diohsc, causing it
to be presented as if it were uncompressed text/gemini:
set geminator text/gemini+gzip gzip -dc -
I wasn't aware of diohsc, a really nice line mode browser which reminds meof the tridactyl add-on. It has www and gopher proxy support, displayof images throug ascii. It's amazing! Transparent inline decompression withgmi.gz works (so hopefully other clients can follow). I am still strugglingwith getting 7z and zstd decompression to work - i'll figure it out. Itwould be nice if I can get diohsc to run on termux in the oculus quest andandroid phone so I can browse my gmi files with espeak (or a better androidtts alternative).Thanks so much for writing it.
Kind regards from the netherlands,Francis Siefken-------------- next part --------------An HTML attachment was scrubbed...URL: <https://lists.orbitalfox.eu/archives/gemini/attachments/20210620/f9998083/attachment.htm>