<META> overloading...

[Sean Conner]

It was thus said that the Great Petite Abeille once stated:
> Presently, a successful status code may look like:
> 
> 20 text/gemini; charset=utf-8
> 
> Would it be reasonable to consider the structure of <META> as equivalent to a modernized MIME header?
> 
> We already have the charset, so... as we have 1024 bytes to play with...
> 
> ... we could add a couple of further information such as Content-Length [1], Content-Disposition [2], Content-Language [3], and Date[4]..
> 
> Perhaps something like this:
> 
> 20 text/gemini; charset=utf-8; length=28102; name="Speculative specification"; date=2020-05-26; language=en-US
> 
> A slim 107 bytes altogether. All optional. 
> 
> Heresy?

  I previously proposed the filesize for this, and solderpunk rejected that
(reasoning here: https://lists.orbitalfox.eu/archives/gemini/2020/000808.html).
And I'm not a fan at all of Content-Disposition because of the way web
browsers implement it (no!  I don't want to save that!  I want to *see* it! 
Let me see it in the browser!).  I think language will pass, but that's
about it ...

  -spc