Cache duration and response body size proposals

[Johann Galle]

Both of these proposals sound very much like introducing MIME type parameters
as geminis version of headers, which is something to be avoided if I read
the [FAQ] correctly.

> Proposal: Cache duration

This has been discussed at length in this mailing list and I personally do
not see a convincing case as to why this is necessary with typical small
gemini documents.

> Proposal: Response body size

There is a section in the FAQ specifically on why gemini does not have this:

tl;dr: It's not sensible for the small gemini documents, for larger files
you should use something else, e.g. torrent, IPFS etc.

> section 2.11 of the FAQ
> ...
> It is true that the inability for clients to tell users how much more of
> a large file still has to be downloaded and to estimate how long this may
> take means Gemini cannot provide a very user-friendly experience for large
> file downloads. However, this would be the case even if Content-length were
> specified, as such an experience would also require other complications to be
> added to the protocol e.g. the ability to resume interrupted downloads.
> Gemini documents can of course straightforwardly link to resources hosted via
> HTTPS, BitTorrent, IPFS, DAT, etc. and this may be the best option for
> very large files.

[FAQ]: gemini://gemini.circumlunar.space/docs/faq.gmi