Proposal about content-size and hash

[Sean Conner]

It was thus said that the Great Philip Linde once stated:
> On Mon, 02 Nov 2020 18:54:32 +0000
> prisonpotato at tilde.team wrote:
> 
> > a new response code, like 22: Response with size.
> > 
> > 20 text/gemini
> > 22 100 text/gemini
> 
> The spec currently explicitly prohibits this kind of use of the status
> codes, but it could be a new first-digit response code, e.g. 7x. This
> would naturally take some time for the implementations to adopt.
> 
> I personally don't miss content-length in practice, but I think the
> fact that it wasn't included in the protocol from the beginning is the
> most compelling argument against it. That said, I'd happily implement,
> something like a new status code to account for such a change in my
> client. When would servers dare use it, though?

  Now.

  As I'm wont to do, I will often code up some weird "proof-of-concept" for
my Gemini server, and if anyone wants to play around with this concept,
there's a server for that:

	gemini://gemini.conman.org/test/testsize.gemini

  The above page will return a normal 20, but all the links on it will
return a 22 with a size, then MIME type.

  -spc (Will implement dodgy specs on a whim for $200, Alex)