cross-posted from: https://lemmy.ml/post/12692350

Anyone aware of a conversations fork with support for unified push notifications? Or a similar xmpp android app with omemo (just the same as conversations’ support) and unified push notifications support, available through the official f-droid repor or a f-droid repo if not available from the official ones?

BTW, I noticed !xmpp@lemmy.ml community was locked. Any particular reason for that?

Also, Converstions requests to set unrestricted use of battery, to use battery under background without restrictions. So it seems unified push notifications would help, though this github issue sort of indicates unified push notifications wouldn’t help, so it just tells me there’s no intention to include support for it on Conversations, but not that it wouldn’t help save battery.

  • solrize@lemmy.world
    link
    fedilink
    arrow-up
    0
    ·
    9 months ago

    Thanks, this is interesting, I didn’t know how that stuff works. I did read in the news that in practice, most push notifications went through Apple and Google. But if you can self-host then that helps. So I guess the delivery method is normal internet? I was guessing it was special stuff at the carrier level. Does the phone have to poll the push distributor every so often? So it’s not really push in that case.

    • kixik@lemmy.mlOP
      link
      fedilink
      arrow-up
      1
      ·
      9 months ago

      The phone doesn’t poll, instead it goes to sleep, and gets awakened by the push notifications. Just like GCM/FCM ones. Part of the key thing, because not any one can self host, is that it requires very little information in comparison, and some providers are open source and even free SW. The one I use is ntfy, there’s the next cloud (next push), and not long ago you can use the conversation push service (up.conversation.im) through the Convesations xmpp client. I was aware of Conversations capable of becoming a unified push distributor, but actually was looking for it to use a unified push distributor instead.

      But I was informed already it’s not necessary, and doesn’t make much sense, by being very low power consumer, even though it requires to keep unrestricted battery consumption on the background. So no issues by Conversations not supporting using a unified push notifications distributor.