Matrix homeserver development be like
* 10 minutes of writing code
* 2 hours of trying to work out a spec omission and asking people
* 5 minutes of writing code
* 30 minutes of filing spec issues
* 15 minutes of writing code
* two days of waiting for clarification on something ambiguous in the spec
I like the premise of the protocol, but sheesh, the spec has some serious quality issues, and it's making it almost impossible to get anything done on my homeserver project without losing focus, because the whole thing constantly blocks on spec holes
Can we get an experienced IETF RFC writer on this or something?
@joepie91 tbh most of the ietf rfc specs I read are the most unreadable things I have ever seen. However I fully agree that matrix spec is not readable. Imho I would go as far as saying that the new design made it somewhat worse too.
@MTRNord The IETF RFCs are often difficult to read, but there's generally one thing you can just assume: that it will contain the answer to your question. There's a reliable source you can fall back on.
The Matrix spec is written more like a tutorial, which is superficially more readable, but in practice ~all the information about the corner cases and procedures is missing.
@MTRNord (I've long ago floated the idea of having an IETF-style reference spec and a separate 'layer' of guidance on how to read it and where to find stuff, but this was shot down because the intention was to have one singular spec that's both informative and readable. And well...)
