RE: https://chaos.social/@grote/116116403663138402
According to stats from F-Droid #Conversations_im is the most downloaded #UnifiedPush distributor.
#Tag
RE: https://chaos.social/@grote/116116403663138402
According to stats from F-Droid #Conversations_im is the most downloaded #UnifiedPush distributor.
Conversations (via #UnifiedPush) is the backbone that gives #Matrix its reliable and timely notifications. An eventually consistent graph database is a nice concept, but it takes #XMPP to put the real-time into real-time communications.
I’ll be in Chemnitz, Germany, for the last weekend of March at #CLT2026, talking again about #UnifiedPush.
https://chemnitzer.linux-tage.de/2026/en/programm/beitrag/202
What I love about #Conversations_im as a #UnifiedPush distributor—aside from #XMPP being a reliable, secure, and efficient protocol—is that it comes with a healthy dose of decentralization.
Sure, you can technically self-host a Sunup instance, but will you? XMPP already offers thousands of providers out of the box.
RE: https://social.tchncs.de/@kuketzblog/116014301228230002
The problem isn't Signal itself; it's that including the firebase-messaging dependency is akin to including malware, even if Play Services aren't installed on the user’s phone.
That’s why having alternatives such as #UnifiedPush is so important.
I think the talk Simon ( @S1m) and I gave on #UnifiedPush at #FOSDEM turned out very well. If you have 30 minutes and want to learn how push notifications in general and UnifiedPush in particular work, check out the recording.
I'm at #FOSDEM. If you want to chat with me about #Conversations_im or #XMPP come by our Jabber/XMPP Realtime Lounge in AW 1.124. We also have lots of stickers and other merch!
If you want to learn about #UnifiedPush, my talk is today (Saturday) at 16:00 in the FOSS on Mobile dev room.
I just finished the slides for our talk on UnifiedPush ( @unifiedpush) at FOSDEM 2026! Come see Simon ( @S1m) and me in the FOSS on Mobile devroom this Saturday at 16:00.
RE: https://gultsch.social/@daniel/113549020656921249
#Signal isn’t just AWS. It also has a hard dependency on Google’s push notification system (FCM) if you don’t want your battery to catch fire.
Signal’s attitude towards #UnifiedPush and #FDroid speaks volumes.
I installed #Signal and #Conversations_im on a clean install of #GrapheneOS on my Pixel 4a and measured the battery impact. The results are shocking!
Both messengers had only one contact: my regular phone.
I used my regular phone to send messages to the Pixel 4a (which was not used for anything else over the course of the experiment).
I always sent the same message via Signal and #XMPP (mixing up which app went first). In total I sent ~32 messages in intervals of 10mins to a few hours.
RE: https://gultsch.social/@daniel/113549020656921249
#Signal isn’t just AWS. It also has a hard dependency on Google’s push notification system (FCM) if you don’t want your battery to catch fire.
Signal’s attitude towards #UnifiedPush and #FDroid speaks volumes.
@daniel wo wir gerade beim Thema #UnifiedPush sind.
Wenn conversations offline ist - z.b. beim Flugmodus - verschwinden die push Nachrichten. Sie kommen nicht verspätet sondern gar nicht.
Könnte man die nicht zum Zielserver ins dortige MAM schicken? oder wenigstens eine "verpasste Benachrichtigung" Mitteilung?
RE: https://gultsch.social/@daniel/113549020656921249
#Signal isn’t just AWS. It also has a hard dependency on Google’s push notification system (FCM) if you don’t want your battery to catch fire.
Signal’s attitude towards #UnifiedPush and #FDroid speaks volumes.
I installed #Signal and #Conversations_im on a clean install of #GrapheneOS on my Pixel 4a and measured the battery impact. The results are shocking!
Both messengers had only one contact: my regular phone.
I used my regular phone to send messages to the Pixel 4a (which was not used for anything else over the course of the experiment).
I always sent the same message via Signal and #XMPP (mixing up which app went first). In total I sent ~32 messages in intervals of 10mins to a few hours.
Weekly GNU-like #MobileLinux Update (01/2026): Happy New Year!
https://linmob.net/weekly-update-01-2026/
#LinuxMobile #LinuxOnMobile #phosh #postmarketOS #FuriLabs #PinePhone #PlasmaMobile #GNOMEMaps #Kaidan #XMPP #NemoMobile #unifiedpush #Mobian #Droidian #pocketblue
Weekly GNU-like #MobileLinux Update (01/2026): Happy New Year!
https://linmob.net/weekly-update-01-2026/
#LinuxMobile #LinuxOnMobile #phosh #postmarketOS #FuriLabs #PinePhone #PlasmaMobile #GNOMEMaps #Kaidan #XMPP #NemoMobile #unifiedpush #Mobian #Droidian #pocketblue
It looks like @S1m and I had our #UnifiedPush talk accepted for the FOSS on Mobile devroom at #FOSDEM.
A detailed schedule has yet to be released, but the devroom takes place all day on Saturday.
RE: https://gultsch.social/@daniel/111528938093114289
I knew pretty early that the EU regulation for IM interoperability is not going the way we want it to go. However the regulator is now looking at push services (FCM, APNS) and I believe we can make some real impact there. We have working solutions and our demands are significantly more actionable.
I don’t know what I was expecting but it looks more and more like the Messaging Interoperability the EU promised will be each gatekeeper essentially publishing their client to server protocol and then you can either use multi protocol messengers or transports. No s2s federation.
Looks like one might be able to log in through the (propriety) c2s API with third party IDs though.