Signal is the world’s most widely used truly private messaging app, and our cryptographic technologies provide extra layers of privacy beyond the Signal app itself. Since launching in 2013, the Signal Protocol—our end-to-end encryption technology—has become the de facto standard for private commu...

We estimate that by 2025, Signal will require approximately $50 million dollars a year to operate—and this is very lean compared to other popular messaging apps that don’t respect your privacy.

  • u_tamtam@programming.dev
    26·
    1 year ago

    If you are curious, you should give XMPP a shot, it’s equivalent to Signal in terms of encryption, but anyone can host their own. Signal is ideologically opposed to anyone but themselves being in control of your account, and because of that I don’t want to trust them.

      • admiralteal@kbin.social
        18·
        1 year ago

        And now here I am, nostalgic for the good old days of having one chat app that could connect you to everyone over XMPP/jabber.

      • squeakycat@lemmy.ml
        8·
        1 year ago

        Indeed. Xmpp is lost as a general purpose chat app for everyone. I have many issues with matrix but it’s the best chance we have, particularly with bridges.

        • kpw@kbin.social
          8·
          1 year ago

          XMPP is the IETF Internet Standard while Matrix is just another custom IM protocol managed by a venture capital funded startup which keeps losing money.

          • squeakycat@lemmy.ml
            3·
            1 year ago

            I don’t disagree with that statement; however, that doesn’t make it something the general public will embrace. Its mess of extensions are top little too late. That ship has long sailed. And I say this as someone that prefers using XMPP for 1:1 chats

        • u_tamtam@programming.dev
          41·
          1 year ago

          Edit: Sorry, I responded to the wrong parent.

          I don’t believe Matrix is better positioned than XMPP to succeed. On a technical aspect, Matrix hasn’t managed to stabilize its protocol, and they’ve been a decade into it. This has resulted in only a single organization being in charge of the protocol, the client and the server implementations. This isn’t sound, this isn’t sustainable. And now, unsurprisingly, this organization is in a financial crisis, has lost important customers, has no budget secured to maintain its staff in the next years, and recently underwent a major licensing change that we can only interpret as a shift towards an opencore model at the detriment of the regular user.

          • slacktoid@lemmy.mlEnglish
            1·
            1 year ago

            The license change is to a GPL variant from the Apache license. How does that affect the regular user? Wouldn’t it be better?

            • u_tamtam@programming.dev
              2·
              1 year ago

              I can’t pretend to know the future, but if you read between the lines and the justifications provided, this isn’t really about AGPL per se, but about Element brokering AGPL exceptions. Practically we can expect all kinds of forks with opencore options that might enshittify the user experience in different ways, and further solidification of Element’s single-handed control over Matrix (which had been a prime concern for many years). Matrix is by the day closer to the closed-source centralized silos it was first pretending to oppose.

      • u_tamtam@programming.dev
        4·
        1 year ago

        Neither XMPP nor Matrix will ever become “the next WhatsApp”: the current internet has seen too much consolidation for the tech majors to permit it (and open and federated protocols can’t compete, do not have the marketing budget nor the platforms to promote their software, but I salute the EU’s Market Act attempt to shake-up the status quo).

        But that doesn’t really matter IMO. What (I believe) is important in the grand scheme of things is that such protocols remain alive, maintained and secure, so that:

        • small-scale instances can flourish and contribute to a more resilient/efficient internet (think of family-/district-level providers ; this is the kind of service I personally offer: family members and friends at large appreciate that the messages and data that we exchange aren’t shared over some cloud or facebook server for no good reason)

        • IM identities can persist over time: if you are a business or an individual, you may want to look into having a stable/lasting contact address, that will survive the inevitable collapse of facebook/whatsapp/instagram/… If you are old enough, your current email address probably existed before facebook. Why not your IM address?

        And yes, I hear you, this is rather niche, but what got me there (and on XMPP in particular) is having been long-enough on the internet to become tired of the never-ending cycle of migrations from service to service. More and more people will have a similar experience as time goes, so this niche will only grow :)

          • kpw@kbin.social
            3·
            1 year ago

            WhatsApp started is an XMPP client, but they use lots of proprietary extensions (doesn’t matter since they don’t federate). You can build very robust and scalable messengers with it if you want to.

            The open source implementations are developed by like 1-2 guys in their spare time and they’re not far behind (and sometimes even ahead) other federated messengers which received tens of millions in venture capital funding.

          • leetnewb@beehaw.org
            3·
            1 year ago

            Which xmpp clients have you used? Conversations and its forks seem far from janky. Movim is nice, Dino is looking good, Kaidan is looking pretty good. Prose could be interesting.

      • kpw@kbin.social
        2·
        1 year ago

        If you need to convince your friends to use some app it might as well be XMPP compatible instead of another walled garden. If you can get your friends on board, you win, even if nobody else uses it.

      • u_tamtam@programming.dev
        1·
        1 year ago

        I assessed XMPP vs Matrix about 8 years ago, and strikingly, the basis on which it didn’t make the cut still applies today. Here’s what I responded to a sibling post: https://programming.dev/comment/5408356

        In short, Matrix dug themselves into a complexity pit with an inadequate protocol, survived for a while on venture capital money (upscaling servers and marketing at all cost), all of it dried up, and now they are in financial trouble. Matrix won’t disappear overnight, but is definitely losing the means to run the managed instances and the client/server ecosystem.

          • u_tamtam@programming.dev
            1·
            1 year ago

            If you read between the lines, Matrix 2 is practically about handing the client state over to the server (what they refer to as “sliding sync”). Realistically, this is an admission that the protocol is too complex to be handled efficiently on the user’s devices. I’m not saying there are not clear benefits (and new trade-offs) to the approach, just that in the grand scheme of things the complexity is shifted elsewhere (and admins foot a larger bill).

          • Zworf@beehaw.org
            1·
            1 year ago

            And Element X as client.

            They are kinda shooting themselves in the foot with all their big rewrites though. Like Vector, Riot, Element, Element X (and I think before vector/riot there was another official client). And Synapse/dendrite… It feels like they spread their development over too many fronts.

        • Kaldo@kbin.social
          1·
          1 year ago

          Is Matrix’s problem just the large scale? I thought it worked relatively well if you’re just using it for personal needs like smaller servers and personal bridges.