Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Google independent notification messaging (do not rely on FCM) #579

Open
anton-isidore opened this issue Jul 5, 2024 · 3 comments
Open

Comments

@anton-isidore
Copy link

With implementation of the BOLT12 it became very important to be online to receive payments.

On GrapheneOS we got this notification warning us:
image

Instead of relying on Google servers it would be great to have own way of delivering notification in case Google Play Services are not present on the phone.

Market standard seems to be running a foreground service. This is what Signal, Telegram, Element, ... and many other apps are doing.

There is also UnifiedPush but I am not sure if it is usable in this context (there is already issue for it here: #554)

Sources:

@anton-isidore anton-isidore changed the title Implement Google independent notification messaging (dont rely on FCM) Google independent notification messaging (do not rely on FCM) Jul 5, 2024
@MasterixCZ
Copy link
Contributor

It would be nice if Phoenix was more FOSS and friendly to deGoogled operating systems

@xronin01
Copy link

xronin01 commented Jul 7, 2024

add support for UnifiedPush 🙏🙏🙏

@dpad85
Copy link
Member

dpad85 commented Jul 8, 2024

The warning message about FCM could let the user choose to run the app as a permanent foreground service. It should not be too hard to do since we are already using a foreground service to run the app in the background. UnifiedPush however would need much more work.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants