Matrix, the open protocol for secure decentralised communications

Highlights include Sliding Sync (instant login/launch/sync), Native OIDC (industry-standard authentication), Native Group VoIP (end-to-end encrypted large-scale voice & video conferencing) and Faster Joins (lazy-loading room state when your server joins a room).

  • 👁️👄👁️@lemm.eeEnglish
    5·
    1 year ago

    Kind of a mix between Discord and IRC. Although it doesn’t have servers like Discord and is more of individuals rooms. In fact they made bridges an important feature, so an IRC room and Matrix room can be merged together without either side really noticing a difference. Same with Discord and a ton of other programs.

    • Rootiest@lemm.eeEnglish
      10·
      1 year ago

      Although it doesn’t have servers like Discord

      They’re called Spaces on Matrix

      • 👁️👄👁️@lemm.eeEnglish
        3·
        1 year ago

        If you actually tried spaces, you’d realize they’re incredibly clunky and not even close to discord rooms. You can’t even search for them. They’re not quite there yet, they leave a lot to be desired.

        • AeroLemming@lemm.eeEnglish
          4·
          1 year ago

          Yeah, Matrix fucking sucks. The organization scheme is obtuse and confusing, it takes longer to send a message over Matrix than it does to post a comment on Lemmy, and it has those god-awful read indicators that you can’t turn off.

          Lemmy was written in Rust, while Matrix was written in Python. I can’t blame poor design on Python, but I’m sure the poor performance is not a coincidence.

          • 👁️👄👁️@lemm.eeEnglish
            8·
            1 year ago

            The organization does suck, I do agree with that. It still needs a lot of UX improvements too. Though you can turn off read indicators in the settings, and I feel like it is a lot faster then commenting on Lemmy. Lemmy being written in rust is actually causing a lot of issues. It’s not a good language for web applications and it’s really starting to show. It also hasn’t prevented security issues either.

            Synapse, the most up to date matrix server, is really slow and resource intensive for sure. But, it’s currently in middle of being replaced with Dendrite. It doesn’t support all the bleeding edge features, but Dendrite has caught up enough to be able to run servers just fine now. In fact Dendrite is light enough to be ran in the mobile Element client, or at least that’s the plan in the near future while they work on p2p. You can read more about it here: https://matrix-org.github.io/dendrite/faq

            • AeroLemming@lemm.eeEnglish
              1·
              1 year ago

              You can’t disable sending read indicators in Element last I checked, only receiving them. What kind of problems is Lemmy having?

              • 👁️👄👁️@lemm.eeEnglish
                1·
                1 year ago

                You can check the beehaw writeup if they didn’t defederate already. They’ve been having too many issues with Lemmy, and it’s been a battle with the developers. On Element desktop you can disable sending read receipts, but not mobile which is stupid.

                • AeroLemming@lemm.eeEnglish
                  1·
                  1 year ago

                  I found this if it’s what you mean, but all it mentions tech-wise is that Lemmy is slow to develop. This does make sense, is it what you’re referring to?

      • caseyweederman@lemmy.ca
        1·
        1 year ago

        I think you and those responding to you are conflating Matrix and Element and Synapse.
        Spaces are a UI feature in Element for grouping rooms. Element is only one of many Matrix clients.
        Element, the client, is written in typescript and kotlin.
        https://github.com/vector-im

        Synapse, a server implementation using the Matrix protocol, is indeed written in Python.
        There are several other servers, written in Go, Rust, C, and C++.
        https://matrix.org/ecosystem/servers/

        Matrix is the protocol itself. Blaming it for UI problems is like blaming TCP for the toolbars in Internet Explorer: very remotely correct.

        • Derin@lemmy.beru.co
          9·
          1 year ago

          You’re not correct about spaces being a UI feature.

          Spaces are now part of the protocol and are stored server side with your account data. Other clients - like fluffychat - can work with spaces just like Element.

          They were element only back while they were being tested, but are now a direct replacement for the old - deprecated - groups functionality.

        • Rootiest@lemm.eeEnglish
          2·
          1 year ago

          You had me second-guessing for a minute, but I think the other commenter is correct.

          One can definitely use Spaces in other clients, even Beeper supports them. So if it was an Element-specific feature, it doesn’t appear to be any longer.

          • ReversalHatchery@beehaw.org
            2·
            1 year ago

            Yeah, spaces need server side support too. Technically they are just rooms that are handled differently, but it’s not just a UI feature.