I’m looking into hosting one of these for the first time. From my limited research, XMPP seems to win in every way, which makes me think I must be missing something. Matrix is almost always mentioned as the de-facto standard, but I rarely saw arguments why it is better than XMPP?

Xmpp seems way easier to host, requiring less resources, has many more options for clients, and is simpler and thus easier to manage and reason about when something goes wrong.

So what’s the deal?

  • BrikoX@lemmy.zip
    link
    fedilink
    English
    arrow-up
    5
    ·
    6 months ago

    Why is JSON better than XML? It’s more modern, sure, but from technical perspective it is not objectively better right? Not something worth switching protocols for.

    XML is unnecessarily complicated. By trying to cram everything into the spec, it’s cumbersome and hard to parse.

    You mention XMPP has transports as opposed to Matrix bridges. I thought they give you roughly the same outcome. What’s the difference?

    The goal is the same, but the way they archive that is different. For transport to work, you need an account on each platform you are using the transport on. It relays the messages through that account by mimicking the client. While bridges work by relaying the messages between rooms and not specific users.

    My understanding is limited, so if you are interested, please do your own research.

    • poVoq@slrpnk.net
      link
      fedilink
      English
      arrow-up
      6
      ·
      edit-2
      6 months ago

      Most Matrix bridges to commercial chat systems also require accounts on those networks. That’s the only way to make them work on most of these systems.

      I guess you are specifically referring to the Matrix to Discord bridge that does work like you describe, but a similar bridge has existed for XMPP to Discord in the past but is currently broken and unmaintained. The currently working XMPP to Discord transport does require you to puppeteer a personal Discord account, but that is rather because of a different focus of the used transport framework than any technical limitation of XMPP in that regard.

      • BrikoX@lemmy.zip
        link
        fedilink
        English
        arrow-up
        2
        ·
        6 months ago

        All platforms that don’t have public API access will require a way to relay that information, but I was talking about the difference in how the messages are relayed. Matrix bridges work fundamentally on each platform/protocol having its own room and relaying the messages through the bridged room instead of the user as XMPP does. That’s why you can relay the same messages to multiple rooms on Matrix, but can’t do the same on XMPP.

        • poVoq@slrpnk.net
          link
          fedilink
          English
          arrow-up
          1
          ·
          6 months ago

          No, that is only an implementation detail, you can easily do a very similar thing with XMPP group-chats.

          In fact the way Matrix does it is a major limitation and the source of an endless amount of issues with their IRC bridge.

    • Cyclohexane@lemmy.mlOP
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      1
      ·
      6 months ago

      cumbersome to parse

      Parsers have already existed for so long in every major language. Why need to worry about parsing?

      And why need to worry about transports working differently if they achieve the same thing? They seem similarly convenient if I understood what you said correctly

      • oldfart@lemm.ee
        link
        fedilink
        English
        arrow-up
        1
        ·
        6 months ago

        Additionally, libraries for XMPP exist in most languages, there is a varying degree of completeness, but they all do a good job of hiding XML from the programmer