Basically working on all the matrix 2.0 stuff, which hasn’t landed yet, although it’s “almost done” now apparently.
Said matrix 2.0 stuff fixes encryption (i.e, makes it seamless like signal), proper voice and video chat and adds sliding sync which makes everything much faster
I tried to look this up to see what its status was. It looks like 2.0 was out (or mostly out) in 2024. Element X talks about using some of the features discussed in one of the Matrix 2.0 blogs, but I dont see explicit version numbers listed anywhere. For example, that sliding sync you mentioned is listed as implemented in the Element X client
It’s kind of confusing but: basically some matrix 2.0 features are implemented in an non-finished state by element X (and synapse) as a testbed for those features, but the actual features aren’t finalised or implemented in most clients. The MSC’s (matrix spec changes) aren’t merged, so clients won’t want to implement it.
2/4 of the MSC’s required for 2.0 are merged as of now, and the other two are close.
2024 was when those features began to be ready to be beta tested, but it takes a long time to get a protocol finalised, since it can’t be easily changed once done.
Think of it like a wayland protocol that isn’t merged, but a desktop, say kde, has an implementation already.
Thanks for the correction. I guess watching the appropriate MSC page would be a good way to check in on the status from time to time? Or the blog once it’s all done I guess.
Basically working on all the matrix 2.0 stuff, which hasn’t landed yet, although it’s “almost done” now apparently.
Said matrix 2.0 stuff fixes encryption (i.e, makes it seamless like signal), proper voice and video chat and adds sliding sync which makes everything much faster
I tried to look this up to see what its status was. It looks like 2.0 was out (or mostly out) in 2024. Element X talks about using some of the features discussed in one of the Matrix 2.0 blogs, but I dont see explicit version numbers listed anywhere. For example, that sliding sync you mentioned is listed as implemented in the Element X client
It’s kind of confusing but: basically some matrix 2.0 features are implemented in an non-finished state by element X (and synapse) as a testbed for those features, but the actual features aren’t finalised or implemented in most clients. The MSC’s (matrix spec changes) aren’t merged, so clients won’t want to implement it.
2/4 of the MSC’s required for 2.0 are merged as of now, and the other two are close.
2024 was when those features began to be ready to be beta tested, but it takes a long time to get a protocol finalised, since it can’t be easily changed once done.
Think of it like a wayland protocol that isn’t merged, but a desktop, say kde, has an implementation already.
Thanks for the correction. I guess watching the appropriate MSC page would be a good way to check in on the status from time to time? Or the blog once it’s all done I guess.