Cat and Tech enthusiast from Germany. Account by @cyrus@wetdry.world
Yes.
After their plan of starting with local iMessage and expanding later didn’t turn out well, they turned it around. Start with Matrix, add local bridges later.
The current application is based on the Beeper Mini codebase, is Matrix-First and will soon allow you to use local bridges to better preserve E2EE. As seen by some MSCs opened up by the beeper team, they are also looking into encrypted chat backups with these local bridges.
Yeah but logically speaking that’s what EX looks fort, and chances are that it’ll work (because why else would it be in the response?)
Yes, the entire point is that it is the client where Sliding-Sync is being developed and tested.
Open https://yourserver.example/.well-known/matrix/client and see if this part exists in it:
"org.matrix.msc3575.proxy": {
"url": "https://slidingsync.lab.matrix.org"
}
if so, chances are it’ll just work.
Video rooms are coming, Element is currently working on MatrixRTC, for Matrkx-Native VoIP.
Demo is at https://call.element.io, Element X on mobile implements this and soon™ the desktop client will too.
It’s not a traditional matrix client mind you, and when I say “Matrix First” I mean architecturally.