Andromxda 🇺🇦🇵🇸🇹🇼

Mastodon: @[email protected]

wiki-user: Andromxda

  • 19 Posts
  • 694 Comments
Joined 11 months ago
cake
Cake day: March 22nd, 2024

help-circle














  • Signal’s default, well-supported installations use Google services

    Signal only uses FCM for notifications, with a fallback mechanism (WebSockets) being available in all builds of the app, as well as Google Maps for location sharing (which most people probably don’t use anyway).

    so unless you’re an extremely atypical user, those services are present on most of your contacts’ devices

    Google Play services being present on people’s devices has nothing to do with Signal including the library. They are present on almost every Android device, because Google pressures OEMs to include them and grant them system level privileges.

    Let’s also remember that E2EE doesn’t protect the endpionts

    Yeah, but that’s the case with EVERY messenger app, so I really don’t know what your point is here?


  • As far as I know moxie, signals lead dev, considers only the use of the officially build and distributed client authorized to use their servers.

    Moxie has resigned a few years ago. The article you linked to is 9 years old, Signal leadership has changed a bunch of times since. Signal can’t detect that you’re running an alternative client, because that check would require them to include some new code in the official client. Even if they did this, they couldn’t just ban anyone who’s client doesn’t pass the check, since it could just be an older version of the official client. They could force everyone to use the official app, but they really have no reason to invest time and effort into enforcing this. Molly is only available for Android, and it isn’t even on the Play Store or the official F-Droid repo, so the user base naturally won’t be as big.