Convincing people to use apps such as Signal is hard work and most can’t be convinced. But with those you manage to convince, do you feel happy to talk to them on Signal?

The problem is these people use Signal on Android/IOS which can’t be trusted and IOS has recently been in the news for having a backdoor. And it has also been revealed that american feds are able to read everyone’s push notifications and they do this as mass surveillance.

So not only do you have to convince people to use Signal which is an incredibly difficult challenge. You also have to convince them to go into settings to disable message and sender being included in the push notifications. And then there’s the big question is the Android and IOS operating systems are doing mass surveillance anyway. And many people find it taking a lot of effort to type on the phone so they install Signal on the computer which is a mac or Windows OS.

So I don’t think I feel comfortable sending messages in Signal but it’s better than Whatsapp.

These were some thoughts to get the discussion started and set the context.

  • JubilantJaguar@lemmy.world
    link
    fedilink
    arrow-up
    2
    ·
    9 hours ago

    If the E2EE is enabled and the client software source is available and reproducible, then, indeed, it could be called Telegram or anything else, it doesn’t matter.

    The particular issue with Telegram is, as you say, the default setting. And also that its encryption algo is not universally trusted.

    • andylicious1337@lemmy.world
      link
      fedilink
      arrow-up
      1
      ·
      8 hours ago

      ok but if the source of the server is not know, how can the client be save?

      I know how e2ee works but couldn’t a bad closed-source server still be a problem?

      btw. not trying to call you out, I just really want to know, cuz I cant get my head around it 🙈🙊

      • JubilantJaguar@lemmy.world
        link
        fedilink
        arrow-up
        1
        ·
        8 hours ago

        The message is encrypted using a key. The key exchange was done over a direct secure channel to the other client, in much the same way as you connect to your bank’s website using HTTPS. The server therefore does not have the key and can only see encrypted text.

        Assuming the client software has not been compromised at either end, then the server will never see anything other than garbled ciphertext.

        BTW, this is also the case with Whatsapp, for example. But the problem with Whatsapp is that the client software is closed source. So you have to trust them not to, for example, surreptitiously phone home with a separate copy of your message. Very unlikely but you have no way to check when the client software is a black box.

        But what’s running on the server is not the issue in either case.