WebSocket in Molly-FOSS vs Molly-UP

Falcon

Hi folks

I'm trying to understand what exactly UP, NTFY etc. is...

Here I read that:

Molly-FOSS uses WebSocket
Molly-UP uses UP and WebSocket (if UP is unavailable)

But UP (via NTFY) is also a WebSocket.
So there's WebSocket everywhere!

What exactly are the differences in these websockets?

Is the benefit of using Molly-UP with NTFY only when I use more than one application using UnifiedPush (NTFY), because then all applications use one UP channel?

If I only have one UP application, it doesn't matter Molly-FOSS or Molly-UP, because in both of them the notifications are handled by WebSocket?

splattergames

Falcon it only really matters if you enable at-rest encryption of the Molly database. In that case the app is inactive and unable to receive notifications. And that's where UnifiedPush comes in, since it runs over ntfy. Other than that, if Molly is the only app capable of using UP, it's not really worth it.

missing-root

Afaik yes, one channel reduces requests and UP also supports polling, so sending multiple things at once

xxx

splattergames In that case the app is inactive and unable to receive notifications.

I use this behavior to keep my battery life currently.

splattergames if Molly is the only app capable of using UP, it's not really worth it

I'm not sure molly/Signal with websocket can eat the battery pretty quick.

trilogy6202

From what I have gathered Signal's (and hence Molly's) websocket implementation isn't as well optimized for "battery consumption" as ntfy so ntfy + Molly UP should consume less battery than Molly FOSS even if it is the only service/app on your phone utilizing UP.

I haven't really tested this claim though.

Viewpoint0232

trilogy6202

I think Molly fixed the battery use problem that Signal has with Websockets.

So in terms of battery use it should be: Molly with Websockets = Molly with UP > Signal with Websockets

As others mentioned, UP starts making more sense if you also use another app that uses UP for notifications. It's the same logic as with Play Services: having just one open connection for multiple apps.

edit: I believe this is the pull request to apply Molly's Websocket improvements to the normal Signal app: https://github.com/signalapp/Signal-Android/pull/13337

xxx

trilogy6202

Lastest Molly-Foss has UP build in. So there's no need for molly-up anymore. Makes switching a lot easier.

I'm testing Molly-Foss with ntfy at the moment.

Onlyfun

Guys does anybody know if it's possible to make all incoming files automatically saved on device without further dependency on the client app?

i cant find any info, so prob its not possible? And to make sure the attachment is securely saved is manually open/download?

I haven't used WhatsApp for years, but i feel like it used to have such feature. So i assume signal/molly could also have it?

trilogy6202

Viewpoint0232 Thanks for sharing. I didn't know that. I personally use ntfy for server notifications but good news for a lot of people I imagine.

trilogy6202

xxx Interesting. So I assume that they will be deprecating the UP version and I should probably switch to the foss version then. Do you by any chance have a link to an announcement or something?

xxx

trilogy6202 Do you by any chance have a link to an announcement or something?

https://github.com/mollyim/mollyim-android/releases/tag/v7.26.1-1

trilogy6202

xxx Thanks a lot.