• rottingleaf@lemmy.world
      link
      fedilink
      English
      arrow-up
      3
      ·
      1 day ago

      It went out of popularity for a reason. I’d love a new protocol with XMPP’s mistakes fixed.

      BTW, OMEMO highlights one of those - it’s not as good as Signal by which it is inspired. Basically no metadata protection, which means that it’s as good as OTR with multiple devices.

      Some kind of Signal with federation (and good clients, not like signal-desktop) would be interesting. Maybe even p2p with some kind of relays (like in NOSTR) for history, offline messages, some kind of Telegram channels and such.

        • jagged_circle@feddit.nl
          link
          fedilink
          English
          arrow-up
          1
          ·
          19 hours ago

          Yes. Asynchronous communication is dependent on both users servers software and config. And that’s exactly why XMPP is disused.

          • oldfart@lemm.ee
            link
            fedilink
            English
            arrow-up
            1
            ·
            5 hours ago

            I’m sure there’s an option you can disable in server software to disable message storage. Why stop at this?

            XMPP can’t federate because there’s an option for disabling that too! 😧

            • jagged_circle@feddit.nl
              link
              fedilink
              English
              arrow-up
              1
              ·
              edit-2
              1 hour ago

              Its the other way around. Asynchronous communication was a feature added later in some software. By default it didn’t have it

              I’m saying it’d a deal breaker if all users dont have asynchronous communication.