• Lemmchen@feddit.org
    link
    fedilink
    English
    arrow-up
    5
    ·
    2 days ago

    And to use it with a similar feature set, everyone is using different extensions which also have to be supported by the clients. I know there is this one server implementation (name escapes me at the moment) and Conversations on the client side, but it’s hardly the standard and we’re not really talking about plain XMPP then anymore.

    • matcha_addict@lemy.lol
      link
      fedilink
      English
      arrow-up
      1
      ·
      2 days ago

      Have you used XMPP recently and ran into the issue of non-obscure servers, clients, or self-hostable implementations using different extensions or not supporting them? (I actually haven’t experienced this even on the obscure ones, but can’t confirm for all of them). Please do not make that accusation, because that I’d really not what happens in reality.

      it’s hardly the standard

      Why not when… It literally is? And all major implementations follow it? That is by definition a standard.

      and we’re not really talking about plain XMPP then anymore.

      Why not? “extensible” is in the name. It is meant to be extended. The protocol is being used exactly as planned and intended.

    • poVoq@slrpnk.net
      link
      fedilink
      English
      arrow-up
      2
      arrow-down
      1
      ·
      2 days ago

      The same is true if you use a Matrix server other than Synapse and a client other than Element. If fact these days the spec incompatibilities are way worse on Matrix than on XMPP.