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 [email protected] 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.

  • @[email protected]
    4•9 months ago

    Conversations can be a unified push distibutor: https://unifiedpush.org/users/distributors/conversations/

    …and I’d trust it (battery-wise) with that. I have an old tablet with conversations running without battery restrictions on it, and if I’m not actually picking it up and using it it regularly goes 1-2 weeks on an 80% battery charge before it dies, the whole time giving audible notifications for XMPP messages/calls (which I attend to on other devices).

    • @[email protected]OP
      3•9 months ago

      Yeap, I noticed it being a unified push distributor, actually in its settings on can find the option to enable it.

      OK, I won’t worry about battery usage then. But the argument about unified push notifications not being useful, but the GCM/FCM actually found useful is somehow hard to understand. But I understand what you’re saying about battery usage. Thanks a lot !

    • @[email protected]
      1•9 months ago

      This is suuuper cool! So you just need a second android device and can run the UnifiedPush on there?