FYI for the other commenters, UnifiedPush can work thru the Prosody mod_unified_push or any server with a up where Conversations (& its forks like Cheogram, Monocles, Blabber) can be a distributor. This has the added bonus of coming with an awesome decentralized XMPP chat server getting to reuse a single connection & single app to server instead of separate ones. Conversations is the most efficient chat client on Android in terms of resources (battery, network, RAM) so might as well keep it lightweight—which you are probably trying to get push notifications from the likes of Signal or Element, but what is the point when you have an efficient XMPP server for your chat needs?

However, I think UnifiedPush might be a bit flawed—as if the startup that created ntfy is pushing others to try to adopt their standard instead of getting folks on board with the older & capable MQTT (which also can be ran thru mod_mqtt on your XMPP server). I am not yet sure if this is a tinfoil take or not.

It’s still quite immature & I have my reservations that a big Haskell project can be maintained for the long-term seeing a lot of Haskell failings even in the short-term. It is a promising idea, but I am not ready yet to try it.

Host your own XMPP node outside the country’s jurisdiction, turn on E2EE if it weirdly wasn’t on by default, & don’t trust the big centralized servers they could easily ban. Apparently everyone wants to dismiss XMPP since you can disable the E2EE (since it is a generic protocol for lots of stuff) despite encryption being on by default on every modern client—so there is your deniability 🙃 Unlike Matrix, the average user can afford to run it on a toaster too.