Is it expected for #Tusky to use more than a single #UnifiedPush channel ? For comparison, #FluffyChat uses a single one, despite managing multiple accounts..
Recent searches
Search options
#UnifiedPush
1 post1 participant0 posts today
Да-конешно, "наша реализация UnifiedPush самая правильная, стабильная, энергоэффективная и вообще крутая, поэтому идите лесом со своим ntfy, удаляйте давайте его"
https://codeberg.org/iNPUTmice/Conversations/issues/216#issuecomment-3107023
Codeberg.orgUse unified push notificationsCan Conversations actually use unified push notifications to save battery life on devices with no GCM/FCM at all?
I've read conversations can be set to be set to become a push notifications provider. But that's not what I'm looking for, instead I'm looking for conversations to use push notifi...
My second #OpenBSD #port that got merged into the #ports tree: MollySocket [1]
Mollysocket is for every #Signal user that wants to ditch Google-dependent notifications.
Together with #Molly [2] you can be sure that notifications will only be routed over systems that you choose, using #UnifiedPush.
This OpenBSD port in particular comes with a useful README that should help you to get started quickly. Let's hope that it makes it into 7.7-release :)
See: https://cvsweb.openbsd.org/ports/net/mollysocket/
[1] https://github.com/mollyim/mollysocket
[2] https://molly.im/
Mollysocket is for every #Signal user that wants to ditch Google-dependent notifications.
Together with #Molly [2] you can be sure that notifications will only be routed over systems that you choose, using #UnifiedPush.
This OpenBSD port in particular comes with a useful README that should help you to get started quickly. Let's hope that it makes it into 7.7-release :)
See: https://cvsweb.openbsd.org/ports/net/mollysocket/
[1] https://github.com/mollyim/mollysocket
[2] https://molly.im/
cvsweb.openbsd.orgports/net/mollysocket/OpenBSD source via CVSweb
#molly #unifiedpush #nextpush #signal
For some reason I only receive Molly notifications when the app is open... 
I would like to receive the notification when I'm not looking at the app, especially when the phone's screen is locked.
Any ideas?
Replied to Bhavani Shankar 
@bshankar Depends on the actual NEED. There are 3-4 common paths that we see: 1. Remove the NEED, maybe it wasn't that important anyway 2. Replace Google Push with #UnifiedPush 3. Replace Play Services with #microG 4. Replace the camera/QR lib with a FOSS one.
Continued thread
Wieso sagt mir niemand, dass #Unifiedpush * auf up* Topics haben will auf der privat installierten Instanz, die ich so verrammelt habe, dass nix durchging, was kein Auth mitschickt? (Wenn man darüber nachdenkt, ist es wohl mehr als logisch)
Manchmal. Wald, Bäume...
Replied to 
mnmlist 
mnmlist 
@mnmlist
Also, wenn ich das richtig verstanden habe, funktioniert #UnifiedPush mit #Molly und #Nextpush nur, wenn du einen Molly-Socket irgendwo laufen hast: https://github.com/mollyim/mollysocket
Das heißt vermutlich wird Molly bei dir aktuell immernoch über den Websocket die Benachrichtigungen empfangen.
Ich habe ein #degoogled Android mit #grapheneos und ohne Play Services. Darauf konnte ich mit UP und Mollysocket (Airgapped) den Akkuverbrauch von Molly auf einen Bruchteil (< 1%) verringern.
GitHubGitHub - mollyim/mollysocket: MollySocket allows getting Signal notifications via UnifiedPush.MollySocket allows getting Signal notifications via UnifiedPush. - GitHub - mollyim/mollysocket: MollySocket allows getting Signal notifications via UnifiedPush.
Habe vorgestern mal #Molly mit #UnifiedPush via #NextPush auf meinem Smartphone eingerichtet .. funzt auch .. die Akkulaufzeit scheint subjektiv verkürzt im Gegensatz zum original Signal was ich vorher nutzte .. irgenwie war damit zu rechnen, immerhin ist 'ne zusätzlich App im Spiel .. aber wie sind so Ehre Erfahrungswerte? .. kann man das irgendwie optimieren?
Replied in thread
@chewie By using Signal-FOSS or Molly-FOSS you just force the Signal app to use its WebSockets-based notification fallback mechanism. But if you have Play services installed and have granted them network permissions, you might as well just use FCM for notifications. It saves battery life compared to each app maintaining its own background network connection.
If you're using @mollyim you also have a third option for receiving notifications: @unifiedpush
But since Signal doesn't support it natively, you need a mollysocket server that receives the Signal notifications and translates them into UnifiedPush format. The mollysocket server is connected to your Signal account as a linked device, but it does not have your decryption keys. There are public instances of mollysocket like mollysocket.adminforge.de
The easiest and best way to get started with UnifiedPush (IMO) is the recently released Sunup distributor app.
GitHubGitHub - mollyim/mollysocket: MollySocket allows getting Signal notifications via UnifiedPush.MollySocket allows getting Signal notifications via UnifiedPush. - GitHub - mollyim/mollysocket: MollySocket allows getting Signal notifications via UnifiedPush.
Hi @gotosocial
FYI I've tested my #nextpush server with @Tusky and #gotosocial account for #unifiedpush notifications and it works as expected 
I report this because release notes from «Scroingly Sloth» read
(And if you're using Tusky, make sure you've got ntfy installed).
«or nextpush conected to a nextcloud server with a running unifiedpush app» (or something similar)
TIL #conversations is not just an end to encrypted, federated messenger, it can also send notifications to your apps through #unifiedpush
#xmpp #android #e2ee #decentralised
#xmpp #android #e2ee #decentralised
Replied in thread
@delta to bring push notification also to the fdroid installations #chatmail server should support #unifiedpush.
Replied in thread
@dalias @cas @jawsh Then again push notifications (the ones you receive when the app is not running) should be handled through a dedicated daemon, not the app itself. #UnifiedPush for example.
Ich hab da einen lokalen Server, der nicht wirklich gut Mails verschicken kann. Trotzdem möchte ich benachrichtigt werden, wenn ein `unattended-upgrade`schiefgeht. Die Lösung: nen Webhook auf das #UnifiedPush von meiner #NextCloud:
```
watchmedo shell-command -W --command 'curl -d "$(echo p | mail)" https://cloud.schmidl.dev/index.php/apps/uppush/push/<langes Token aus NextPush>' /var/mail/schtobia
```
Ⓥ
Notification of calls on Android phones using #UnifiedPush , seem to have been completely broken for many (all?) people since the move from version 1.5.28 to 1.5.30.
A bug was filed over a year ago. A number of people there say they can't get calls at all and even offer money for bugfix dev work, but so far no one from the team has even commented on it.
https://github.com/element-hq/element-android/issues/8761
What info would help or can you recommend a dev to pay to work on this?
GitHubno call ringing when using own ntfy server · Issue #8761 · element-hq/element-android
Hej fedisie z Androidem. Których UnifiedPush distributors używacie?
I jak właściwie się po naszemu mówi na te zunifikowane dystrybutory popchnięć? xD
It would be great if @briar could do push notifications via UnifiedPush instead of sitting in the background 
Quite cool seeing more apps in ntfy 
Gibt es hier Nutzer, die folgende Kombi erfolgreich laufen haben?
#UnifiedPush auf #nextcloudpi hinter reverse proxy #nginx (in meinem Fall liegt nginx auf einem anderen Server).
Push Nachrichten werden vom Socket (in meinem Fall #mollysocket ) losgeschickt, werden jedoch von der selbstgehosteten nextcloudpi unifiedpush provider Kombi nicht weitergeleitet.
Auch andere Apps mit UP reagieren nicht.
Gerne #retröt
@mollyim
I was using #Molly FOSS UP with #NextPush.
Current Molly FOSS insists to scan a QR code for #UnifiedPush setup, but NextPush doesn’t provide one.
Do I really need MollySocket? The old version worked well without another service.