Proposal about content-size and hash

[Ali Fardan]

On Tue, 03 Nov 2020 15:51:20 +0000
khuxkm at tilde.team wrote:
> Alright, fine, I'll cede that point. Still, if anything, 5.5.2 and
> 5.5.3 show that new features that have been suggested have, in fact,
> made it into the spec. If we tell people not to suggest new features
> at all, we might miss out on some things we otherwise may have wanted.

I'm absolutely not against these two gemtext features, I'm just
suggesting that for the spec paper to be finalized, there has to be an
agreement within the community that the protocol is ready and there's
no more to be added.  Until of course, a newer version of the protocol
gets released, but that's for the far future when technology evolves,
for example, when TLS becomes obsolete.

> But how can I differentiate "EOF, the file is over" vs "EOF, the
> socket died"?

Suppose you have content length in the header and the content received
didn't match the content length, what would you do then? What purpose
would it serve to know if it's a socket dying EOF or end of stream EOF?