mollyim-android

https://github.com/mollyim/mollyim-android/blob/285650e38613... I'm pretty unconvinced that this is a sane or useful thing to do.

Molly is a fork of signal that is allowed to access Signals APIs and their APIs are much more open than any other similar service [1] . Signal is not really designed for communicating with people that you don't know in real life such that you can be beyond suspicion that they would be archiving messages but it is basically impossible to monitor if your conversations are being archived if someone is just taking pictures of their phone with another device. [1] https://github.com/mollyim/mollyim-android

Apologies for the mistake. I'm running a Signal fork called Molly[0]; the feature I mentioned seems to be unique to that fork, based on a search of the code. However, it shows that the data is being provided to the client by the server, in some way. This is a guess, but it may be because sending clients have to encrypt with a key for each device. Here's the code: https://github.com/mollyim/mollyim-android/blob/26403ab1806a... https://github.com/mollyim/mollyim-android/blob/26403ab1806a... [0] https://molly.im/ [0] https://github.com/mollyim/mollyim-android

Not if you're using Molly-FOSS, which strips all Google integrations down to a shared library level. UnifiedPush instead of Firebase. OSM for location sharing instead of GMaps. There are de-googled AOSP-based mobile OS's such as GrapheneOS that can be used with Molly-FOSS as well. It's not necessarily the perfect end goal, but for those who are at an earlier phase of their privacy journey, GrapheneOS + Molly-FOSS is a massive improvement over stock Android + stock Signal, while maintaining a relatively minimal disruption to their ordinary workflows with e2ee messaging on an android-based smartphone. https://molly.im/ https://github.com/mollyim/mollyim-android

There is still Molly as a fork, but no idea how hardened it actually is. After Moxie's statement at the time I kind of ditched everything regarding Signal's ecosystem. I understand the business perspective of it, but it's kind of pointless trying to say this is open source when it's illegal to press the Fork button on GitHub, you know. https://github.com/mollyim/mollyim-android

> message history functionality is too restrictive for me. At least a way you can get around this is to do the backing up by desktop. I'm assuming you're on an iPhone because Android supports backup. If you are Android, see Molly: https://github.com/mollyim/mollyim-android > Telegram strikes a good balance, and wins at the UI/UX game. Telegram gets the "lol" because it's not default E2EE. They advertise themselves as E2EE but most people are not using this feature because it's opt in. If you're going to seriously position yourself as a security app, the defaults have to be secure. It's the bare minimum. And E2EE isn't even available for group chats... WhatsApp is more secure (telegram also gathers metadata)... I do think signal has stagnated while there are many things that could really be improved, including low hanging fruit like ju

You can with Molly[0], which is a much better client and a great team behind it. [0] https://github.com/mollyim/mollyim-android

You may be able to install something like https://github.com/mollyim/mollyim-android in the EU ... eventually.

I'm sure it will become possible soon. The code is already there on iOS, as the app also work on iPad, but hidden behind the internal feature flag [0]. Same with Android [1]. If your second device in an Android, you can already use it now with [Molly](https://github.com/mollyim/mollyim-android). Also, WhatsApp recently added this feature, so the expectations from potential new users who switched is now there. [0] https://community.signalusers.org/t/allow-android-ios-device... [1] https://community.signalusers.org/t/allow-android-ios-device...

There are quite a few forks that connects directly to the Signal servers, [Molly](https://github.com/mollyim/mollyim-android) being the most well-known I believe. From my understanding, they're not a fan of it (not sure if it's officially against their TOS or not) but they don't go out of their way to stop them. At least as long as you don't use the Signal name and make it clear you're not an official app. Even in this blog post about usernames, they clearly make sure to mention them: "This means that in about 90 days, your phone number privacy settings will be honored by everyone using an official Signal app."

The team has been working to get UP support added to Molly, a fork of Signal for Android. https://molly.im/ https://github.com/mollyim/mollyim-android/pull/152

Regarding Signal, I don't think they have been approached yet... https://github.com/UnifiedPush/wishlist/issues/8 I think the consensus was that we wanted to wait for UnifiedPush to be more mature before approaching them, but it's probably about time. S1m made an interesting implementation for the (compatible) Signal fork Molly: https://github.com/mollyim/mollyim-android/pull/152 The implementation is quite interesting: it adds a linked device that does not receive encryption keys, but sends push notifications to the client.

Molly[1], a fork of Signal, seems to work fine. I've used it for a long time and never had any issues with it (and it connects to Signal fine). But for security reasons one of their changes was dropping SMS, so switching to it won't do you any good there. [1]: https://github.com/mollyim/mollyim-android

The Molly[1] fork of Signal already removed SMS support. [1]: https://github.com/mollyim/mollyim-android

There are third party apps that connect to Signal's servers such as Molly. https://github.com/mollyim/mollyim-android