RE: gultsch.social/@daniel/1135490…

#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.


Peter Vágner reshared this.

in reply to Radasbona

@radasbona Die angedachte Lösung ist das der "Rewrite Proxy" / "Push Server" (also up.conversations.im) die Nachricht nochmal sendet. Das ist besser weil es auf WebPush-Ebene sowas wie TTL und topics (Deduplizierung) gibt und der Push Server das besser verwalten kann wenn er versteht was da abgeht.

Der Push Server weiß auf Protokollebene auch schon wann der client wieder online ist. Aber das resend Ding ist noch nicht implementiert.