A quick primer on XMPP & how/why you should host your own server for low-resource-usage, encrypted chat & other pubsub server.

  • TCB13@lemmy.world
    link
    fedilink
    English
    arrow-up
    9
    ·
    edit-2
    11 months ago

    “Denshi explains the basics of XMPP: The future of decentralized messaging.” > finally someone that actually understands what they’re saying. Matrix is questionable open-source and privacy disaster, XMPP is tested, reliable, secure and above all a truly open standard and decentralized it just lacks some investment in better mobile clients.

    What people fail to see is that XMPP is the only solution that treats messaging and video like email: just provide an address and the servers and clients will cooperate with each other in order to maintain a conversation. Everything else is just an attempt at yet another vendor lock-in.

    • toastal@lemmy.mlOP
      link
      fedilink
      English
      arrow-up
      3
      ·
      11 months ago

      This is why I don’t trust Rich Communication Services (RCS) being developed by the big tech giants. I can almost guarantee it’s meant to meet minimum legal requirements otherwise Google, Facebook, et al. would have reverted their services to XMPP federation on a protocol with now even more years of battle testing.

      • setVeryLoud(true);@lemmy.ca
        link
        fedilink
        arrow-up
        2
        ·
        11 months ago

        The only part of RCS that’s open is the protocol used for servers, like Google’s Jibe and Samsung’s messages server, to talk to each other.

        There is currently no easy way to run such a server yourself, there are none available, and even if one did become available and you could run it, good luck making it talk to the big boys’ servers as they could just dismiss you as spam.

    • toastal@lemmy.mlOP
      link
      fedilink
      English
      arrow-up
      1
      ·
      11 months ago

      Good catch! The Lemmy UI isn’t straightforward. I thought I needed to upload a separate image for the post—not that you choose between URL vs. image despite the UI seemingly allowing both. Fixed!