• drkt@scribe.disroot.org
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    3 months ago

    The protocol is bloated to hell so third-party clients stand no chance, and the foundation spends more time bikeshedding or pissing away money than they do developing. It’s a doomed project.

          • InFerNo@lemmy.ml
            link
            fedilink
            English
            arrow-up
            1
            ·
            3 months ago

            The argument has always been, if when chat rooms are public, anyone can join and start logging the chats, encryption does nothing.

            It has the ability to connect over TLS, but that’s about it.

            I loved using it for its simplicity, except when using all the different flavours of nick registration (Q, NickServ, …).

      • ProdigalFrog@slrpnk.net
        link
        fedilink
        English
        arrow-up
        0
        ·
        edit-2
        3 months ago

        Slrpnk hosts an XMPP/Jabber for our users, mods and admins to communicate. Its worked pretty darn well for the past couple years, with very low resource needs.

        The clients are pretty slick now too, such as Cheogram or Monocles for mobile, and movim is an excellent web app with support for group calls.

        I’d certainly recommend it over Matrix/element.

        • muppeth@scribe.disroot.org
          link
          fedilink
          English
          arrow-up
          1
          ·
          3 months ago

          Not to mention you can run a server on anything pretty much and for surprisingly big amount of users. Toaster or potatoes will do just fine.

          • moonpiedumplings@programming.dev
            link
            fedilink
            English
            arrow-up
            1
            ·
            3 months ago

            https://www.devever.net/~hl/xmpp-incident

            This article discusses some mitigations.

            You an also use a platform like simplex or the tor routing ones, but they aren’t going to offer the features of XMPP. It’s better to just not worry about it. This kind of attack is so difficult to defend against that it should be out of the threat model of the vast majority of users.

          • poVoq@slrpnk.net
            link
            fedilink
            English
            arrow-up
            0
            ·
            3 months ago

            Significant improvements to certificate pinning and validation have been added to all major XMPP clients as a result of this incident, but it should also be clear that hosting a server on infrastructure under control by an antagonist government (see also Signal) is a very bad idea and hard to mitigate against.

            • eleitl@lemmy.zip
              link
              fedilink
              English
              arrow-up
              1
              ·
              3 months ago

              End to end encryption between clients (also for groups) seems to partly address the issue of a bad server. As for self-hosting, any rented or cloud sevices are very vulnerable to an evil maid. So either in-house hosting or locked cages with tamper-proof hardware remain an option.

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

                Their server infrastructure is (run by Pentagon and NSA best buddies AWS).

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

                    The infrastructure is under control of an antagonistic government, yes. Hetzner is also technically a private company, but they obviously willingly complied with requests from the German government.

            • rottingleaf@lemmy.world
              link
              fedilink
              English
              arrow-up
              0
              ·
              3 months ago

              Signal doesn’t suffer anything worse than DoS if a hostile party controls the central service. That’s its point and role. It’s based on the assumption that such hostile parties as governments don’t like DoS’ing central services, they prefer to be invisible.

              For other points and roles other solutions exist. One can’t make an application covering them all, that never happens.

              Briar again (I’ve finally read on it and installed it, and I love how it works and also the authors’ plans on the future possibilities based on the same protocols, but not for IM, say, there’s an article discussing possibility of RPC over those, which, for example, can give us something like the Web ; I mean, those plans are ambitious and if I want them to succeed so much, I should look for ways to defeat my executive dysfunction and distractions and learn Java). Except it would be cool if it allowed to toss data over untrusted parties, say, now if two Briar users in the same group are not in each other’s range, but there’s a third Briar user not in that group between them, their group won’t synchronize (provided they don’t have Internet connectivity). If one could allow allocating some space for such piggybacked data, or create some mesh routing functionality, then it would become a bit cooler.

              • poVoq@slrpnk.net
                link
                fedilink
                English
                arrow-up
                0
                ·
                3 months ago

                You are very naive if you think that is all the US government can do in regards to Signal, but suit yourself 🤷