4 ms·

Absolutely not. It doesn't have commands and probably a lot more. It also does not have parity by having deliberate breakage like calls. It's a sluggish buggy

Absolutely not. It doesn't have commands and probably a lot more. It also does not have parity by having deliberate breakage like calls. It's a sluggish buggy mess, so I guess you could say it has parity in that aspect.

yaky 1y ago
After installing and configuring coturn, and then finding out that ElementX requires Element Call instead feels like a "fuck you" from developers.
- Arathorn 1y ago
  what guide were you following that told you to install coturn for Element X? It shouldn't be /that/ surprising that Element X's group-capable calling requires a group call server, and in general most people seem happy to not have to worry about coturn given the server acts as a relay.
  - yaky 1y ago
    The instructions are from Synapse docs: https://element-hq.github.io/synapse/latest/setup/turn/coturn.html https://element-hq.github.io/synapse/latest/setup/turn/cotur... Element (not ElementX), the official/preferred app, works with coturn for 1-on-1 calls. But ElementX does not. IMO it is surprising to break 1-on-1 call functionality.
    - Arathorn 1y ago
      In Matrix 2.0, all calls are group capable (much like Matrix itself doesn’t specialcase DMs - they are just rooms with 2 people). So yes, no coturn is needed. We haven’t got as far as interop between legacy Matrix 1:1 calling and Matrix 2.0 style MatrixRTC though, which I can see being annoying - but overall the admin burden should be simpler than running a coturn. We’ll update the synapse docs to explain that coturn isn’t needed for MatrixRTC calls.
entrepy123 1y ago
> It's [Element X is]...sluggish... I regret to concur. On an iPhone PRO MAX with iOS 18.7-latest, my stopwatch says: - Element X loads to list All Chats in 3 seconds. - Element Classic loads to list All Chats in <1 second. And Element X is supposed to be the "fast one", due to Rust SDK, etc. etc. I'm giving Element X etc. the benefit of the doubt and will see them through. But there NEEDS TO BE a user-advocate or project-manager just wailing on usability internally at Element. If you need such a person, find someone, and if you can't find anyone, hit me up, but I would think someone should be filling this role already. In addition to bundling and network effects, one magic thing that helped grease the skids for some apps like AOL Instant Messenger or Facebook Messenger (in its glory days) or WhatsApp/Discord/Telegram or whatever gain very wide adoption was their relatively seamless user experience. As much as the Parent sounds like complaining, I think it's complaining in good faith. We want Matrix to succeed.
- Arathorn 1y ago
  Hm. Something sounds wrong here, then. On my iPhone 12 Pro Max on iOS 26, my account (~5000 rooms) opens in about 2s in Element X iOS. On the classic app it’s about 10s (ie unusable). Roughly how many rooms are you in? and what server is this on (it could be a serverside problem)? And what precise build of the app?
  - entrepy123 1y ago
    > how many rooms are you in? 8 on both (same account) > and what server is this on (it could be a serverside problem)? It's a hosted SaaS personal homeserver. So yes, quite possibly a server-admin issue. I've just put in a ticket to find out. EDIT: Synapse 1.139.0 > And what precise build of the app? Element X Version 25.10.0 (190) EDIT: After updating to Element X Version 25.10.1 (192) [latest Update from App Store], about 2 seconds is observed -- still slower than Classic, but a little better than before. I will still finish following up regarding Server issues/info with server admins; hopefully that fixes it. Thanks a ton for all you do! Good to know it's not the expectation.
    - 1y ago

yaky 1y ago

After installing and configuring coturn, and then finding out that ElementX requires Element Call instead feels like a "fuck you" from developers.

Arathorn 1y ago
what guide were you following that told you to install coturn for Element X? It shouldn't be /that/ surprising that Element X's group-capable calling requires a group call server, and in general most people seem happy to not have to worry about coturn given the server acts as a relay.
- yaky 1y ago
  The instructions are from Synapse docs: https://element-hq.github.io/synapse/latest/setup/turn/coturn.html https://element-hq.github.io/synapse/latest/setup/turn/cotur... Element (not ElementX), the official/preferred app, works with coturn for 1-on-1 calls. But ElementX does not. IMO it is surprising to break 1-on-1 call functionality.
  - Arathorn 1y ago
    In Matrix 2.0, all calls are group capable (much like Matrix itself doesn’t specialcase DMs - they are just rooms with 2 people). So yes, no coturn is needed. We haven’t got as far as interop between legacy Matrix 1:1 calling and Matrix 2.0 style MatrixRTC though, which I can see being annoying - but overall the admin burden should be simpler than running a coturn. We’ll update the synapse docs to explain that coturn isn’t needed for MatrixRTC calls.

entrepy123 1y ago

> It's [Element X is]...sluggish... I regret to concur. On an iPhone PRO MAX with iOS 18.7-latest, my stopwatch says: - Element X loads to list All Chats in 3 seconds. - Element Classic loads to list All Chats in <1 second. And Element X is supposed to be the "fast one", due to Rust SDK, etc. etc. I'm giving Element X etc. the benefit of the doubt and will see them through. But there NEEDS TO BE a user-advocate or project-manager just wailing on usability internally at Element. If you need such a person, find someone, and if you can't find anyone, hit me up, but I would think someone should be filling this role already. In addition to bundling and network effects, one magic thing that helped grease the skids for some apps like AOL Instant Messenger or Facebook Messenger (in its glory days) or WhatsApp/Discord/Telegram or whatever gain very wide adoption was their relatively seamless user experience. As much as the Parent sounds like complaining, I think it's complaining in good faith. We want Matrix to succeed.

Arathorn 1y ago
Hm. Something sounds wrong here, then. On my iPhone 12 Pro Max on iOS 26, my account (~5000 rooms) opens in about 2s in Element X iOS. On the classic app it’s about 10s (ie unusable). Roughly how many rooms are you in? and what server is this on (it could be a serverside problem)? And what precise build of the app?
- entrepy123 1y ago
  > how many rooms are you in? 8 on both (same account) > and what server is this on (it could be a serverside problem)? It's a hosted SaaS personal homeserver. So yes, quite possibly a server-admin issue. I've just put in a ticket to find out. EDIT: Synapse 1.139.0 > And what precise build of the app? Element X Version 25.10.0 (190) EDIT: After updating to Element X Version 25.10.1 (192) [latest Update from App Store], about 2 seconds is observed -- still slower than Classic, but a little better than before. I will still finish following up regarding Server issues/info with server admins; hopefully that fixes it. Thanks a ton for all you do! Good to know it's not the expectation.
  - 1y ago