4 ms·
Pull requests aren't going to solve the current issues with Matrix. I believe that the problem arises from the protocol design itself. And cutting back on the c
by goku12 1y ago
Pull requests aren't going to solve the current issues with Matrix. I believe that the problem arises from the protocol design itself. And cutting back on the current specification is not viable for an already deployed project.
Here are some reasons why I think it's the protocol. Synapse is the only fully functional home server. Both dendrite and conduit are struggling to reach feature parity. This could be either due to the protocol being too complex or it being extended too fast. I have seen signs of both. Meanwhile, practically all web clients like element, cinny and schildi are all based on the same codebase. Native clients like Fractal and Nheko do exist. But it looks like they are also going to need the rust library behind elementx to attain full function. This lack of diversity among the clients are also indicative of the protocol complexity (similar to how nearly every web browser is based on Chrome's blink engine).
- Arathorn 1y agoThis is not correct. Matrix is deliberately asymmetrical - it’s easier to write clients than servers (although that balances has shifted somewhat with E2EE). The reason Dendrite has fallen behind is simply because we couldn’t afford to split focus between it and Synapse. Meanwhile the various Conduit projects seem to be keeping up quite well despite being entirely hobby projects. Clientside, there are entirely separate production grade stacks with full featuresets in at least typescript (eg Element Web), rust (EX, Fractal), Dart (FluffyChat), KMP (Trixnity), C++ (Nheko), Go (Beeper) and more. I can guarantee their authors would very heavily push back on the “you need rust-sdk to attain full function”, not least as many of those have more features than rust-sdk. This is not a WebKit situation.