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.

  • poVoq@slrpnk.net
    link
    fedilink
    arrow-up
    1
    ·
    edit-2
    7 months ago

    There is a tutorial here: https://joinjabber.org/tutorials/service/unifiedpush/

    Basically there is no more efficient way to do it than via XMPP, FCM is also an XMPP service. So the best is really to use Conversations as an UP end-point to get notifications from other apps. AFAIK it doesn’t use a websocket, but a native xmpp connection for it, which is even more efficient.

    The reason Conversations also supports FCM is that some Android phone vendors are extremely aggressive in putting apps into sleep mode and only FCM notifications work reliably on those.