mastodon - Link to source

When not using Google Play services (e.g. #GrapheneOS, #LineageOS users), #Signal can be a real battery drain. @mollyim with @unifiedpush on the other hand is extremely battery efficient.

Here's how to set this up, using #Nextcloud as the UnifiedPush provider: kroon.email/site/en/posts/moll…

Using Molly (Signal) with UnifiedPush

I finally started using Molly to send and receive messages via Signal. Molly is a hardened fork of Signal for Android, offering features such as an encrypted message database, automatic locking, shredding no longer needed secrets from RAM, notificati…
Guido Kroon
#signal #nextcloud #lineageos #grapheneos @UnifiedPush @Molly

reshared this

in reply to Nick

mastodon - Link to source

Daniel Gultsch

@ratcatcher @signalapp It’s a bit complicated but broadly speaking both the Mastodon server and the Matrix server have support for an internet standard called 'WebPush'. That’s where the server HTTP POSTs the push notification to, and that’s how the notification chain gets started that eventually ends up on your phone. But the Signal server doesn’t support that standard.
@Signal @Nick
in reply to Nick

mastodon - Link to source

Daniel Gultsch

@ratcatcher For the client that is true. (And Molly does for example talk directly to #Conversations_im). However the problem arises when the server sees a new message it needs to do 'something'. Like it needs to tell 'someone'. And that something to someone needs to be standardized.

In the animation on unifiedpush.org/developers/int… the top, purple arrow. That’s WebPush. And Signal doesn’t do that. And then MollySocket is a translation proxy for that.

Introduction

UnifiedPush is a protocole that allows you to get push notifications, while letting the user choose the provider they wish to use.
UnifiedPush
#conversations_im @Nick
in reply to Nick

mastodon - Link to source

Daniel Gultsch

Oh that’s the part where it’s probably better for @mollyim to take over this conversation. But yes, it needs to run on a server somewhere. Running it locally would probably be fairly resource intensive. The goal of MollySocket is more or less to shift that resource consumption to a server. If you were running it locally you might as well not use UP at all.
@Molly
This entry was edited (17 hours ago)
⇧