|
|
|
# UnifiedPush as OS Service
|
|
|
|
|
|
|
|
See:
|
|
|
|
The problem: Important FLOSS mobile messaging apps, and their respective servers, are tied to Google FCM for their push messaging.
|
|
|
|
|
|
|
|
- `around 2023` [/e/ community post \#46197](https://community.e.foundation/t/add-unifiedpush-to-e-os-to-make-it-possible-for-developers-to-avoid-fcm-and-better-support-f-droid-applications/46197 "Add UnifiedPush to /e/OS to make it possible for developers to avoid FCM and better support F-Droid applications") -- people expressing interest in UnifiedPush support
|
|
|
|
The solution: Now there is a good FLOSS alternative, the UnifiedPush standard. I want to build around UnifiedPush, to enable our libre mobile ecosystem to work efficiently without tying this function to a particular service provider.
|
|
|
|
|
|
|
|
The assessment: UnifiedPush (UP) is by now well proven, with multiple implementations of all its components (UP server, UP distributor, client apps, app-servers). It is actively being refined, some of that work funded by NLNet/NGI. Murena's /e/OS recently made the first step in integrating support in the OS. I published an analysis of that step, followed by a summary of the wider scope of work needed around it. The next steps that will contribute most effectively to its wider adoption include:
|
|
|
|
|
|
|
|
- integrating UP in key apps (some have willing devs, others need contributions)
|
|
|
|
- providing UP as a service provider (server/service side, and mobile OS integration)
|
|
|
|
- documenting (best practices for implementors, client-server protocol and options...), sharing, promoting
|
|
|
|
|
|
|
|
My blog posts:
|
|
|
|
|
|
|
|
- all my [articles tagged UnifiedPush](https://wrily.foad.me.uk/tag:unifiedPush)
|
|
|
|
- `2024-11-27` [UnifiedPush — Wider Developments](https://wrily.foad.me.uk/unifiedpush-wider-developments) -- what else we need to make this work
|
|
|
|
- **`2024-11-27` [UnifiedPush — Wider Developments](https://wrily.foad.me.uk/unifiedpush-wider-developments) -- what else we need to make this work**
|
|
|
|
- `2024-11-19` [Going Google-Free with UnifiedPush in /e/OS](https://wrily.foad.me.uk/going-google-free-with-unifiedpush-in-e-os) -- analysis of initial ntfy integration in /e/OS 2.5
|
|
|
|
- `2023-03-29` [UnifiedPush Plan for Murena /e/-OS](https://wrily.foad.me.uk/unifiedpush-plan-for-murena-e-os) -- me expressing interest in working on this
|
|
|
|
|
|
|
|
See also:
|
|
|
|
|
|
|
|
- `early 2023` [/e/ community post \#46197](https://community.e.foundation/t/add-unifiedpush-to-e-os-to-make-it-possible-for-developers-to-avoid-fcm-and-better-support-f-droid-applications/46197 "Add UnifiedPush to /e/OS to make it possible for developers to avoid FCM and better support F-Droid applications") -- I and others express interest in /e/OS supporting UnifiedPush.
|
|
|
|
|
