3 ms·

Element X Matrix client now on iOS early release

11 points by raybb 3y ago

Arathorn 3y ago
Better URL perhaps: https://element.io/labs/element-x https://element.io/labs/element-x We're super excited about this release, even if it's an early one - Element X is the first Matrix client which outperforms WhatsApp/Telegram/iMessage and friends, both in terms of performance & UX.
- dfabulich 3y ago
  “Element X currently targets messaging rather than collaboration; other features will be added later this year.” What does this mean? What’s the difference between “messaging” and “collaboration”?
  - Arathorn 3y ago
    Messaging = iMessage/WhatsApp/Signal/~Telegram Collaboration = Slack/Teams/Discord Element itself does both, but Element X currently is just starting by polishing its Messaging features. So the missing features for collaboration are things like threads, spaces (aka workspaces), widgets (embeddable apps), voice/video rooms, multiaccount support, group permissions, polls, etc.
    - mawalu 3y ago
      Thanks for you work! I'm hyped for a faster mobile client and definetly need to setup the sliding-sync proxy for my HS. Can you already say something about encrypted search support in Element X? I really like how transparent encryption works for DMs nowadays in Element but for non-powerusers it is often really confusing why the can't search their chats (on the current gen mobile clients at least). I fully understand that this is a difficult problem and less state on the client definitely does not make it easier. Also since you mentioned it, is multiaccount support something that we can realistically expect to see in Element X someday (maybe even in a v1.0?). If I remember correctly for the previous iterations of the clients the status was mostly "maybe one day" or "the architecture does not really support it".
      - Arathorn 3y ago
        > Can you already say something about encrypted search support in Element X? It's planned, and should be way easier to do than on old Element given we can hook the clientside search indexer (https://github.com/matrix-org/seshat https://github.com/matrix-org/seshat), which happens to be in Rust, directly into matrix-rust-sdk and thence both EIX and EAX. Whereas previously we'd have had to do custom integs with Seshat on EI and EA like the current one on Element Desktop, which just becomes a maintenance nightmare. Hopefully should be ready in the next months. > Also since you mentioned it, is multiaccount support something that we can realistically expect to see in Element X someday (maybe even in a v1.0?). If I remember correctly for the previous iterations of the clients the status was mostly "maybe one day" or "the architecture does not really support it". Definitely. We actually had it pre-Element in Matrix Console, and then it got lost in Element. The hope is to get it into Element X relatively early (as it's a pain in the ass to add it late)
- raybb 3y ago
  Is the android early release coming down the pipeline anytime soon? Would love to use it and help report bugs and give feedback! I'm a heavy user or voice messages and the lag and issues around them on Android drive me crazy right now
  - Arathorn 3y ago
    it's a few weeks away. However, voice messages isn't in the initial release; it will follow shortly though. Hopefully the entirely new codebase will help resolve lag and other issues (please make sure the current issues are filed on github.com/vector-im/element-android/issues though, so we don't accidentally port them in EX...)
jonas-w 3y ago
Does anyone know if there are plans to integrate the sliding-sync-proxy into synapse itself?
- Arathorn 3y ago
  Yes, eventually. Right now the sliding sync MSC is still in flux (e.g. we just realised today that it's missing an explicit flag to notify once the client has caught up with the server, rather than guessing via heuristics: https://github.com/vector-im/element-x-ios/issues/1269#issue-1791318666 https://github.com/vector-im/element-x-ios/issues/1269#issue...). As a result, the implementation (which is in golang) is being kept separate from Synapse for now while we iterate on it; plus it's a separate set of folks working on it. This also means that SS can be used with any existing server (dendrite, conduit etc) as needed. It'll get added natively to Synapse eventually, but it'll likely be quite a way off.
  - jonas-w 3y ago
    Perfect makes sense, and that it also works with other matrix server implementations is even better, thank you for your efforts!

11 points by raybb 3y ago

Better URL perhaps: https://element.io/labs/element-x https://element.io/labs/element-x We're super excited about this release, even if it's an early one - Element X is the first Matrix client which outperforms WhatsApp/Telegram/iMessage and friends, both in terms of performance & UX.

dfabulich 3y ago
“Element X currently targets messaging rather than collaboration; other features will be added later this year.” What does this mean? What’s the difference between “messaging” and “collaboration”?
- Arathorn 3y ago
  Messaging = iMessage/WhatsApp/Signal/~Telegram Collaboration = Slack/Teams/Discord Element itself does both, but Element X currently is just starting by polishing its Messaging features. So the missing features for collaboration are things like threads, spaces (aka workspaces), widgets (embeddable apps), voice/video rooms, multiaccount support, group permissions, polls, etc.
  - mawalu 3y ago
    Thanks for you work! I'm hyped for a faster mobile client and definetly need to setup the sliding-sync proxy for my HS. Can you already say something about encrypted search support in Element X? I really like how transparent encryption works for DMs nowadays in Element but for non-powerusers it is often really confusing why the can't search their chats (on the current gen mobile clients at least). I fully understand that this is a difficult problem and less state on the client definitely does not make it easier. Also since you mentioned it, is multiaccount support something that we can realistically expect to see in Element X someday (maybe even in a v1.0?). If I remember correctly for the previous iterations of the clients the status was mostly "maybe one day" or "the architecture does not really support it".
    - Arathorn 3y ago
      > Can you already say something about encrypted search support in Element X? It's planned, and should be way easier to do than on old Element given we can hook the clientside search indexer (https://github.com/matrix-org/seshat https://github.com/matrix-org/seshat), which happens to be in Rust, directly into matrix-rust-sdk and thence both EIX and EAX. Whereas previously we'd have had to do custom integs with Seshat on EI and EA like the current one on Element Desktop, which just becomes a maintenance nightmare. Hopefully should be ready in the next months. > Also since you mentioned it, is multiaccount support something that we can realistically expect to see in Element X someday (maybe even in a v1.0?). If I remember correctly for the previous iterations of the clients the status was mostly "maybe one day" or "the architecture does not really support it". Definitely. We actually had it pre-Element in Matrix Console, and then it got lost in Element. The hope is to get it into Element X relatively early (as it's a pain in the ass to add it late)
raybb 3y ago
Is the android early release coming down the pipeline anytime soon? Would love to use it and help report bugs and give feedback! I'm a heavy user or voice messages and the lag and issues around them on Android drive me crazy right now
- Arathorn 3y ago
  it's a few weeks away. However, voice messages isn't in the initial release; it will follow shortly though. Hopefully the entirely new codebase will help resolve lag and other issues (please make sure the current issues are filed on github.com/vector-im/element-android/issues though, so we don't accidentally port them in EX...)

jonas-w 3y ago

Does anyone know if there are plans to integrate the sliding-sync-proxy into synapse itself?

Arathorn 3y ago
Yes, eventually. Right now the sliding sync MSC is still in flux (e.g. we just realised today that it's missing an explicit flag to notify once the client has caught up with the server, rather than guessing via heuristics: https://github.com/vector-im/element-x-ios/issues/1269#issue-1791318666 https://github.com/vector-im/element-x-ios/issues/1269#issue...). As a result, the implementation (which is in golang) is being kept separate from Synapse for now while we iterate on it; plus it's a separate set of folks working on it. This also means that SS can be used with any existing server (dendrite, conduit etc) as needed. It'll get added natively to Synapse eventually, but it'll likely be quite a way off.
- jonas-w 3y ago
  Perfect makes sense, and that it also works with other matrix server implementations is even better, thank you for your efforts!