kirimita

And there is this gist for the app side, if you need something to share: https://gist.github.com/mar-v-in/2a054e3a4c0a508656549fc7d0a...

Here is a blog post to use the play services, without the proprietary lib and API: https://unifiedpush.org/news/20250131_push_for_decentralized...

This is also what UnifiedPush lib to use FCM does (https://codeberg.org/UnifiedPush/android-embedded_fcm_distri...)

Which is documented in this gist: https://gist.github.com/mar-v-in/2a054e3a4c0a508656549fc7d0a...

That's already how it works, the 3rd app is usually the Google services. The setup described on the blog post allows user to use the Google services OR another service

If you are interested, you can read the specifications: https://unifiedpush.org/developers/spec/android/. The same question actually exists for firebase-messaging (Google) too (answer here: https://github.com/firebase/firebase-android-sdk/blob/cf5fe2...)

> But I think UnifiedPush or ntfy instructions should make these steps more clear (or I failed to find it), even if just to say "it's actually that easy" to save our time looking.

We are working on the documentation: https://codeberg.org/UnifiedPush/documentation/pulls/16

How mobile push notifications currently bring centralization to decentralized services, and how we can avoid it, even for mainstream configurations.

(As I said in a previous discussion about Firefox) I really wish it was possible to enable DRM for a single container.

For your information, your suggestion has been the solution https://github.com/deckerst/aves/pull/519

I'd love to be able to enable DRM for a single container. Until then, I have to continue with profiles.

> You only need to create a dispatcher app that will relay the notifications to third party apps.

That part is what specify UnifiedPush. It does not specify the communication between the push server and the distributor.

From the blog post:

> One key feature of UnifiedPush is that the communication between the push server and the distributor is not specified. This means that a variety of technologies can be employed, such as WebSockets, Server-Sent Events, *XMPP*, raw TCP, or even SMS, whatever works best for the user.

It is an UnifiedPush distributor, so it can replace FCM for applications supporting it. Here are most of the applications supporting UnifiedPush right now: https://unifiedpush.org/users/apps/

It is also possible to bridge your discord room to a matrix room : https://www.t2host.io/discord/

Data does not _reside_ unencrypted with End to Bridge Encryption : https://docs.mau.fi/bridges/general/end-to-bridge-encryption...