1. 24
    1. 3

      Does Element X require being installed from the app store (as the article seems to imply), or will existing installs of Element be upgraded automatically to Element X (as was always the story)?

      1. 6

        classic Element will eventually upgrade to Element X, but for now the two exist in parallel (given Element X is still missing a few features like threads & spaces)

        1. 11

          Threads and spaces seem like rather big features to be missing in a release advertising itself as production-ready. They’re pretty important to the holistic experience of chatting.

      2. 2

        Finally, cryptographic warnings are being eliminated. Historically, as end-to-end encryption was rolled out throughout Matrix, not all apps verified the identity of their users, triggering confusing and unactionable warnings to users. We are now shifting towards only letting devices whose ownership has been verified by their owner participate in conversations, killing those warnings - as well as other underlying protocol changes to eliminate warnings.

        Yikes. That sounds like a move towards “trust me bro, this is encrypted, never mind the TLA in the group”

        1. 20

          I think I’m missing your objection - If I understand correctly, they’re changing things from showing a warning when some device is unverified to preventing the unverified device from interacting at all. Surely that’s strictly a security increase?

          1. 6

            you are correct; the other post has got entirely the wrong end of the stick.

          2. 7

            The E2EE story in Matrix has always been a joke, and I guess they plan to keep it that way.

            1. 3

              It depends on the use case. I run a small private Matrix server, mostly me and my wife’s family, and the constant E2EE warnings and lost encryption keys are nothing but confusion and frustration to everyone else. So this feature will likely be a big UX improvement, but that’s mostly because encryption barely matters in my use case.

            2. 2

              With the sliding sync, is it normal that I have to wait like 30 seconds in a 1 on 1 room to see the most recent messages? Even the ones I sent.

              1. 1

                absolutely not. should be instant. please file a bug

              2. 1

                I’m unable to use it with my custom conduit server. Trying to use it as “custom provider” just doesn’t show any results. Is this a know limitation? The legacy Element does still and always did work with it.

                1. 1

                  Yeah, this is a known limitation with Conduit, something about the new sliding scale implementation that Element X relies on.

                2. [Comment removed by author]