Nuttso Hmm yeah I see the AA declaration in the Android manifest file for Molly UP.... I'll make a thread for it maybe. Thanks for the reply!!!

    Nuttso Thx a lot. We are working towards making molly the most secure communication app available. There are a lot of features on the roadmap that will be a game changer.

    Fingers crossed and I wish you or Simplex makes the finest, best chat app of all, 99.9% anonym, 99.9% secure and 99.9% private and 100% simple and fail safe for any user. So Briar + Cwcth + TOR + Simplex + Signal/Molly + 100% anonimity and all a beautiful simple UI should be melted together :D

    What are your main thoughts about SimpleX and Cwcth? Any truly major concerns?

      Are there any ideas to make Molly a stand-alone client which could be used by self hosted servers ala XMPP or something similar without relying on Signal servers?

        Hathaway_Noa Are there any ideas to make Molly a stand-alone client which could be used by self hosted servers ala XMPP or something similar without relying on Signal servers?

        We need to finish implementing monero. After that there are several features planned:

        Remote attestation (based on auditor)
        Sandboxing webrtc
        Text only molly
        Molly infrastructure (no personal identifiers)

            Nuttso

            Ideas, requests: Integrated TOR by a single switch and with a verification status bar which also shows the circuit? Customizable TTL for messages on server...? Optional online presence displaying like in Briar which would come with zero second TTL or maybe a few minutes (only in server RAM without persistance on reboot)?

                There's probably more projects I should donate to but am officially donating to GrapheneOS and now Molly.im. Secure os and a secure IM are extremely important.

                We have a list of messaging apps to chose from but it seems Molly.im is headed in a direction we should be supporting.

                easthvan all feature request are welcome. This year will be a great year for Molly. When monero gets implemented an audit will be a must. We would like to do it after monero, remote attestation and sandboxing webrtc is done. When these features are implemented we think about releasing a text only molly. Then we can sit down with the community and find the best way to handle Molly's own infrastructure. We would love to still keep it possible to talk to signal. On top of that add the possibility to talk on molly network.

                    10 days later

                    Nuttso About which version to use. I meant if that version of Molly in the link I posted above works with instant notification when database is at rest/locked? Do you have a version that works with FCM too? Link?

                        Nuttso you just need the fcm version. It also receives messages with a locked device

                        Ok does that mean you get instant notification when a message is received even when database is at rest?

                        Second, when registering for the first time and set a database password. Do you have to remember and use the same database password when reinstallning the app? Can database password be changed if you want to?

                            PMUSR Ok does that mean you get instant notification when a message is received even when database is at rest?

                            Yes. Locked database notifications work with FCM and mollysocket. Only not with websocket.

                            PMUSR Second, when registering for the first time and set a database password. Do you have to remember and use the same database password when reinstallning the app?

                            No.

                            PMUSR Can database password be changed if you want to?

                            Yes

                                  This is not intended as a criticism, but considering the problematic security of F-Droid, pointed out several times by the GrapheneOS account in this forum, I'm curious as to the reasoning behind publishing Molly on F-Droid.

                                    Relaks Molly is not published on F-Droid. The F-Droid team doesn't want it there anyway due to previous arguments between Signal and F-Droid. If Molly was ever published on F-Droid, it'd be via a reproducible build where Molly retains its key and is signed by them, not F-Droid.

                                    Molly has its own F-Droid repository. it's already available via GitHub with a self-updater, and the FOSS variant is also available on Accrescent (not due to some imposed restriction on Accrescent's part - that's just the variant that Molly's team chose to publish there).

                                      Relaks I might be wrong but they publish on their own repository (which can be accessed by Obtanium, or another F-Droid client like Droid-ify, if you don't want to use F-Droid), not on the F-Droid repository, and I have seen that at least one of the Molly versions prompts to self update after being installed via the F-Droid repository. Just saying this as there are issues with F-Droid but this avoids most of them.

                                      The only issue I guess is the fact that multiple app repositories are accessed by F-Droid clients, but as I said you don't need to use them.

                                      I don't speak on behalf of Molly by the way and may be wrong, just thought I would reply with my thoughts

                                      EDIT: oops more knowledgeable people replied before me anyway

                                      It looks like I may have been wrong about the Molly app repo repository versions self updating. Not sure

                                          Thank you very much for the clear answers. Very heartening that this is taken seriously.

                                          • N1b likes this.

                                          So, some feedback! Molly works just fine, at first I needed to do a Captcha on every (!) new chat, completely crazy (f**k Signal...), not sure if because VPN or the custom App or both.

                                          Now it works fine, coupling Signal Desktop too, and the Ability for a second phone / Pixel tablet / whatever is lit!

                                          roamer4223 F-Droid basic is the official client but updated to modern Android. Nobody on GrapheneOS should use the old F-Droid App! The 3rd party clients are often more modern (NeoStore, AuroraDroid, Droid-ify, ...), some are outdated (G-Droid, Foxydroid) and in general my best experience was with F-Droid Basic.

                                              missing-root yes, I personally use F-Droid Basic as well for the F-Droid and other repo apps. It is the best client, at the moment anyway imo 🙂 just didn't want to derail this into an F-Droid client debate haha

                                                5 days later