Molly.im

DeletedUser534

gristle-cause What about battery life?

How do Molly and Molly-FOSS compare to Signal when using websocket for notification?

xxx

DeletedUser534 compare to Signal when using websocket

Molly is a tad better. Also Molly shuts down itself when the database gets encrypted (this saves a lot battery).

DeletedUser534

xxx I'm not sure that I follow. Does that mean that Signal continues to be active all the time or?w
How much better is "tad"?

xxx

DeletedUser534 that mean that Signal continues to be active all the time

Molly and/or Signal have to be active all the time to receive notifications (unrestricted battery) without a push solution.
Websocket -> Signal stays active all the time or you get no notifications.
Websocket -> Molly stays active until the database gets locked -> you get no notifications when its locked.
UnifiedPush/GooglePush is another level. It saves a lot of battery.

Websocket will eat your battery.

spacecdt

uthunku No, I recieve notifications just fine via MollySocket while the database is locked. I believe there is an option for it in Molly's settings under Notifications.

DeletedUser534

xxx Thanks.

I only need notifications for one app - I wonder if there is any difference then between websocket and UP?

UP is great when there are multiple apps but I suppose there is no difference in battery for only one app?

Donatello

xxx xxx
What do you mean exactly, doesn't Molly-FOSS give notifications when the phone is locked if I am using the websocket?

What about Signal calls?

It works just fine in normal Signal for me and the battery drain isn't that drastic tbh.

xxx

DeletedUser534 I wonder if there is any difference then between websocket and UP?

It's night and day. Furthermore you get notifications when Molly is at rest. Use a translation service in case: https://www.kuketz-blog.de/messenger-wechsel-von-signal-zu-molly-unifiedpush-mollysocket-ntfy/
I use sunup as distributor. Ntfy worked fine for me also.

gristle-cause

Any Molly.im + RethinkDNS users?

Ive got a wireguardVPN proxy running, and the 'block when DNS is bypassed' universal firewall rule enabled. Molly itself has no rules blocking any potential connections

Yet, I find that universal firewall rule blocks Molly, a lot. It's logged >500 outbound calls from Molly over the past week, and seems to correlate with connection issues over phone calls. I can't figure out why/how Molly persistently works around my enforced wireguard DNS

Nuttso

Donatello the phone can be locked, but if you lock the DB you won't receive notifications. For generic notifications you need to use unifiedpush.

Sideofsmalandsrulle

I'm starting to feel a little concerned about the project, as the update frequency is starting to slip. The latest version was released over a month ago. Is this a security risk?

0xC0DED0D0

Sideofsmalandsrulle Suppose I should leave it to Nuttso, as the maintainer, to reply. But as another user I'd just like to say that personally I'm not concerned.

Molly seems to be pretty consistently two weeks behind Signal on releases. Latest Signal currently isn't much more than 6 days old: https://github.com/signalapp/Signal-Android/releases/tag/v7.70.1

With that, Molly is still being tweaked independently: https://github.com/mollyim/mollyim-android/compare/v7.68.5-1...main

"Rumours of Molly's death are greatly exaggerated"..?

eggy

Sideofsmalandsrulle there seems to be only a single maintainer actively supporting the Molly.im Android app. It's probably too hard for him to keep up now. He did just write on Matrix that he was sick for a couple of days, so he was away. AFAIK, Signal changed their Android build code in the last month or so, so the Molly dev very likely has some conflicts to dig through and it seems to be technically difficult to catch up to upstream Signal.

I believe Molly is still secure as Signal is very stable and Signal hasn't been making any security-related releases to their mobile client.

Nuttso

Sideofsmalandsrulle We don't follow signals update schedule. Only if there is something security relevant.

Sideofsmalandsrulle

Okay, thank you for your answers. And a big shout-out to you, Molly team. Keep up the good work!

xxx

@Nuttso
mollysocket is somkind broken. https://discuss.grapheneos.org/d/31475-mollysocket-seems-to-be-broken
Is there a solution coming?

Nuttso

xxx S1m is still investigating this issue. 99% of our resources are currently focused on flatline. Have some more patience please

xxx

Nuttso
Thank you! Take you're time. I just learned WebSocket works much better than a few years ago. So I'm happy with it currently.

Nuttso

We know how to fix it. Just need some time. Easy workaround: remove the linked device named mollysocket

xxx

Nuttso Easy workaround: remove the linked device named mollysocket

Sorry This repairs Unified Push? Once or permanent?

Nuttso

xxx permanent fix will be shipped when we have time

« Previous Page Next Page »