UnifiedPush Plan for Murena /e/-OS
I would love to work for or with Murena on their /e/-OS phone. UnifiedPush support is one of the first things I would propose to do.
UnifiedPush is in my humble opinion one of the most important recent developments for freedom phones. It grants us freedom from Google’s near monopoly push notification system FCM. I have followed the development of UnifiedPush it from its OpenPush origins.
What have I done so far?
I have deployed ‘ntfy’, a UnifiedPush compatible server implementation, on my home network. I documented and published my installation script (which uses Ansible and Docker), and successfully submitted it for inclusion in the popular Matrix installer matrix-docker-ansible-deploy, so matrix self-hosters can deploy it easily.
My self-hosted push service now serves notifications to several of the apps I use.
If given the chance to advance UnifiedPush support, I would propose a plan something like this:
- deploying a UP server for /e/ users (one for the Murena central server, and one in each self-hosted deployment), initially choosing one of the existing kinds of UP server (probably NextPush because obviously it's built to fit into nextcloud);
- creating a UP distributor as an /e/-OS system app, by adapting an existing one (NextPush, to match the server), and making it auto-discover/configure the server from the /e/-OS account info;
- working with important client apps (/e/-OS default apps first) to add support to them;
- perhaps tweaking the U.P. server and distributor to better suit this use case, if and when needed.
I am posting this in the e-foundation forum discussion “Add UnifiedPush to /e/OS to make it possible for developers to avoid FCM and better support F-Droid applications”
Follow/Feedback/Contact: RSS feed · Fedi follow this blog: @julian@wrily.foad.me.uk · matrix me · Fedi follow me · email me · julian.foad.me.uk Donate: via Liberapay All posts © Julian Foad and licensed CC-BY-ND except quotes, translations, or where stated otherwise