💾 Archived View for rawtext.club › ~sloum › geminilist › 003103.gmi captured on 2020-11-07 at 03:21:34. Gemini links have been rewritten to link to archived content
-=-=-=-=-=-=-
Sean Conner sean at conman.org
Sat Nov 7 05:17:29 GMT 2020
- - - - - - - - - - - - - - - - - - -
It was thus said that the Great colecmac at protonmail.com once stated:
twins includes the response body size in the media type header by default. This
enables user experience improvements in Gemini clients, such as indicating
download progress. It is possible to disable this feature.
For anyone wondering what that looks like:
❯ gemget --header -o- gemini://twins.rocketnine.space/
Info: Started gemini://twins.rocketnine.space/
Header: 20 text/gemini; charset=utf-8; size=1128
It looks like a nice server, but to be honest I would remove this.
Serving non-standards is not what Gemini is about imo, and it's how
the Web became what it is today. And clients in general should be
strict and not accept things out-of-spec. For example Amfora won't
allow non-standard status codes, even if the first digit matches a
known code. It doesn't check for non-standard MIME params, but maybe
it should?
So what are the standard MIME parameters for text/plain? text/markdown? text/html? multipart/alternate? And what should a client do when itencounters a non-standard MIME parameter?
-spc