-
Notifications
You must be signed in to change notification settings - Fork 102
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
Comments
It would be nice if Phoenix was more FOSS and friendly to deGoogled operating systems |
add support for UnifiedPush 🙏🙏🙏 |
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. |
comon really? Some Foss App devs are able to integrate Unified Push Support, but Aqinq cant? That just sounds like an excuse for me? I used GrapheneOS, and I cant use Phoenix, although I would like to because of the App that requires googles fcm bullshit to work. |
PLS add unified Push Support! |
With implementation of the BOLT12 it became very important to be online to receive payments.
On GrapheneOS we got this notification warning us:
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:
The text was updated successfully, but these errors were encountered: