8 ms·

I noticed that they renamed the Element mobile app to Element Classic. Has Element X reached feature parity and stability yet? For how long will Classic be main

I noticed that they renamed the Element mobile app to Element Classic. Has Element X reached feature parity and stability yet? For how long will Classic be maintained?

_def 1y ago
As of lately, Spaces are now supported in Element X which possibly brings it to feature parity (at least I wouldn't know what's missing, and I've been using Element X now for some months because of these plans)
noident 1y ago
> The outgoing Element mobile app (‘classic Element’) will remain available in the app stores until at least the end of 2025, to ensure a smooth transition https://element.io/blog/mas-migration-unleashes-element-x-on-matrix-org/ https://element.io/blog/mas-migration-unleashes-element-x-on... I can't find any other communication from Element Creations other than that. The renaming to Element Classic doesn't bode well considering that Element X still doesn't support a vast number of home servers and a number of Synapse authn/authz features. If they remove it from the app store, my advice for my users is going to be to switch to fluffychat, and I'll eventually migrate away from Synapse to some flavor of Conduit.
Arathorn 1y ago
Element X now has initial support for threads & spaces (as of last week), which were the main things missing from full parity with Element Classic.
- JuniperMesos 1y ago
  Good to know! These are very important features and not having them really gets in the way of switching off of classic. I am worried about "intial" support - what is going to break with threads and spaces that I try to join with thr new Element X?
- conor- 1y ago
  Sorry to hijack this thread to ask - but what is the current state of sliding sync? Does it still require a separate proxy service to enable sliding sync if you're self-hosting a homeserver; or is it upstreamed into synapse? Also is there a list of clients that are sliding sync aware?
  - Arathorn 1y ago
    upstreamed into Synapse as of Sept 2024, and the proxy was sunset in Nov 2024: https://matrix.org/blog/2024/11/14/moving-to-native-sliding-sync/ https://matrix.org/blog/2024/11/14/moving-to-native-sliding-... Not that many clients have actually adopted it though, because the MSC is still not 100% finalised - it's currently entering the final review stages at last now over at https://github.com/matrix-org/matrix-spec-proposals/pull/4186 https://github.com/matrix-org/matrix-spec-proposals/pull/418.... Right now Element X uses it (exclusively), and Element Web has experimental support for it; I'm not sure if any others actually use it yet.
basilikum 1y ago
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
neiljohnson 1y ago
You can learn more about Element X migration plans from last weekend's Matrix conference here https://youtu.be/_cahXxr8d-4?si=0b9qyjiEYVpMczDy&t=442 https://youtu.be/_cahXxr8d-4?si=0b9qyjiEYVpMczDy&t=442

I noticed that they renamed the Element mobile app to Element Classic. Has Element X reached feature parity and stability yet? For how long will Classic be maintained?

_def 1y ago

As of lately, Spaces are now supported in Element X which possibly brings it to feature parity (at least I wouldn't know what's missing, and I've been using Element X now for some months because of these plans)

noident 1y ago

> The outgoing Element mobile app (‘classic Element’) will remain available in the app stores until at least the end of 2025, to ensure a smooth transition https://element.io/blog/mas-migration-unleashes-element-x-on-matrix-org/ https://element.io/blog/mas-migration-unleashes-element-x-on... I can't find any other communication from Element Creations other than that. The renaming to Element Classic doesn't bode well considering that Element X still doesn't support a vast number of home servers and a number of Synapse authn/authz features. If they remove it from the app store, my advice for my users is going to be to switch to fluffychat, and I'll eventually migrate away from Synapse to some flavor of Conduit.

Arathorn 1y ago

Element X now has initial support for threads & spaces (as of last week), which were the main things missing from full parity with Element Classic.

JuniperMesos 1y ago
Good to know! These are very important features and not having them really gets in the way of switching off of classic. I am worried about "intial" support - what is going to break with threads and spaces that I try to join with thr new Element X?
conor- 1y ago
Sorry to hijack this thread to ask - but what is the current state of sliding sync? Does it still require a separate proxy service to enable sliding sync if you're self-hosting a homeserver; or is it upstreamed into synapse? Also is there a list of clients that are sliding sync aware?
- Arathorn 1y ago
  upstreamed into Synapse as of Sept 2024, and the proxy was sunset in Nov 2024: https://matrix.org/blog/2024/11/14/moving-to-native-sliding-sync/ https://matrix.org/blog/2024/11/14/moving-to-native-sliding-... Not that many clients have actually adopted it though, because the MSC is still not 100% finalised - it's currently entering the final review stages at last now over at https://github.com/matrix-org/matrix-spec-proposals/pull/4186 https://github.com/matrix-org/matrix-spec-proposals/pull/418.... Right now Element X uses it (exclusively), and Element Web has experimental support for it; I'm not sure if any others actually use it yet.

basilikum 1y ago

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

neiljohnson 1y ago

You can learn more about Element X migration plans from last weekend's Matrix conference here https://youtu.be/_cahXxr8d-4?si=0b9qyjiEYVpMczDy&t=442 https://youtu.be/_cahXxr8d-4?si=0b9qyjiEYVpMczDy&t=442