element-x-android VS element-call

Yep, a good example is the element X rewrite

They use Jetpack on Android

https://github.com/vector-im/element-x-android

And SwiftUI on iOS

https://github.com/vector-im/element-x-ios

But both use the same underlying Matrix Rust SDK

https://github.com/matrix-org/matrix-rust-sdk

So they share the core part of the app between platforms, but everything user facing is native

And the cake under the cherry is… Element X is open-source[1][2]!

I really can't wait for Beeper[3] to rebuild their fork on top of Element X (it's currently based on Element, formerly called Riot). If this happens this will be an absolute game-changer in the messaging ecosystem.

[1] https://github.com/vector-im/element-x-ios

[2] https://github.com/vector-im/element-x-android

[3] https://www.beeper.com/

You can get the latest build here: https://github.com/vector-im/element-x-android/actions/runs/4203105910

Element X is an entirely new client written in Rust + Swift UI/Jetpack Compose (https://github.com/vector-im/element-x-ios and https://github.com/vector-im/element-x-android) which will eventually replace the legacy Element apps (https://github.com/vector-im/element-ios and https://github.com/vector-im/element-android).

The features already exist serverside; we're just working on getting them out of beta.

Let me know what you guys think. You can check out the github here and experiment with it via the first link.

Looks like there's an open protocol and an open source client implementation for video calls. https://github.com/vector-im/element-call

This is great! Jitsi has never clicked for me. I tried it a few times, and read about it, and was never excited about it. I just tried Element Call, albeit an empty room, and the UI feels right.

There's now also https://github.com/vector-im/element-call.

They have SFU support as of recently, so it should work scale similarly to Jitsi et al.

Would second recommending giving Matrix a try, native voip is actively being worked on in the form of Element Call. But to access it in Element you currently have to use the develop client. Otherwise you have to use 3rd party voip software in the form of Jitsi in the stable release.

Element Call github

With screening for unapproved callers, this would really replace every other platform!

Currently we don't force TURN, so in practice this means that voice packets go direct between the clients if possible, and so the IP addresses of the clients are necessarily exposed to each other.

However, this is utterly trivial to fix: matrix-js-sdk already exposes https://github.com/matrix-org/matrix-js-sdk/blob/96ba061732b... and we simply haven't exposed it as a setting in Element Call yet. I've filed a bug for it at https://github.com/vector-im/element-call/issues/251 - thanks for bringing it up!

In terms of moderation: this is no different to moderation in Matrix as a whole, where we're already busy working on shared greylists (MSC2313 and friends) - https://matrix.org/blog/2020/10/19/combating-abuse-in-matrix... has more details at the end.