Proposal about content-size and hash

[Arav K.]

> So, this is actually solvable, in principle. It would require a
> backward-compatibility breaking change to the protocol, which would
> probably throw the Geminiverse into a period of chaos as clients and
> servers made the change at different rates. I haven't done anything
> like this since the early days when you could count Gemini
> implementations on your fingers and I had pre-existing relationships
> with all the authors, so the chaotic period was measured in mere days
> before we achieved perfect unity again. I have no idea how it would go
> down this time now that everybody and their dog has written some
> Gemini tooling, and I'm not at all convinced that the lack of
> Content-Size is such a big practical problem that it's worth this kind
> of upheaval.

This is a great idea, but Gemini seems to be beyond the point where this
is feasible.  Oh well.  I guess content-size won't be getting in after
all.

~aravk | ~nothien