4 ms·
> pushing for a broken state resolution algorithm (decentralized consensus) without a formal analysis, which means it's now reached its 5th or 6th version and
by ryukafalz 5y ago
> pushing for a broken state resolution algorithm (decentralized consensus) without a formal analysis, which means it's now reached its 5th or 6th version and Matrix clients are all incompatible with one another (because only Element implements them all) and once they have been upgraded rooms cannot be downgraded so in many places only Element can chat
This is false. Clients don't do state res, servers do. Clients don't care.
- pkulak 5y agoYeah, I didn't want to say anything because I'm no expert, but as far as I can tell, Matrix clients use a Rest API. It's not like they are resolving state deltas locally or something. It seems like the big complexity right now is the encryption, since that, by definition, has to happen on the client. There's a concerted effort, however, to make that as easy as possible with shared libraries and such.
- Arathorn 5y agoMeanwhile on the serverside, there have only been two versions of state resolution; the original beta version that turned out to be buggy, and the current fixed one which has been heavily scrutinized and is okay: https://matrix.org/blog/2020/06/16/matrix-decomposition-an-independent-academic-analysis-of-matrix-state-resolution https://matrix.org/blog/2020/06/16/matrix-decomposition-an-i.... The amount of incorrect info in the GP post is very unfortunate - although I too wish that open standard comms protocols spent more time collaborating than spitting at each other.