Salta al contenuto principale


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.


Debacle reshared this.

in reply to Daniel Gultsch

u need molly.im with github.com/mollyim/mollysocket for unified push 🙃
in reply to tooshiesty ✅

@fluttersh yes and that's an extremely cumbersome work around for something they should be offering natively.
in reply to Daniel Gultsch

If I am not wrong, Signal does offer on their website, variants of their app without google's blobs implemented. I saw them on their github as well.

@fluttersh

in reply to Daniel Gultsch

Don't forget their policy on not allowing third party clients on their network.
in reply to Daniel Gultsch

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?

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.

in reply to Daniel Gultsch

das klingt auf jeden Fall gut. Danke das du hilfst dieses tolle Projekt aus der Nische rauszuholen. 👍

Seit foss warn auch per unifiedpush warnt ist so ein resend durchaus wichtig geworden.

Questa voce è stata modificata (6 ore fa)
in reply to Daniel Gultsch

What would you suggest as an alternative (not a facetious question - I'm genuinely curious)?
in reply to The Sleight Doctor 🃏🍉

@ApostateEnglishman I'm trying to phrase my statements in a way in which they don't sound like an advert, but I'm developing and Android instant messaging client called #Conversations_im which uses a federated instant messaging network called Jabber or XMPP.
in reply to Daniel Gultsch

Great! All the best with the project. I've dropped you a follow so I can keep up with progress. 👊🏼
in reply to Daniel Gultsch

@Daniel Gultsch @The Sleight Doctor 🃏🍉 I don't develop an xmpp client so it's not a problem if phrase it like an advert, right?

I second the recommendation for XMPP, as it is properly and actively federated, with an ecosystem that encourages small, healthy, community hosted, servers (hosting one for ~20 users is about as hard, expensive and time consuming as self-hosting a static website)

Questo sito utilizza cookie per riconosce gli utenti loggati e quelli che tornano a visitare. Proseguendo la navigazione su questo sito, accetti l'utilizzo di questi cookie.