-
-
Notifications
You must be signed in to change notification settings - Fork 752
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
Consider setting FCM priority to "high" for better delivery #70
Comments
Thank you for the suggestion. I remember seeing it, but there was some comment about not misusing it, or otherwise there will be some penalty. I forgot, but I'll read up on it again. |
Ah yes it's right there
|
wait so do you think this means that if i display a notificaiton visible to the user, then the de-prioritization won't happen? |
I think it may be worth setting the FCM priority to high for ntfy priorities 4 and 5, but I think I may need to create a limiter to regulate how often it's used. I will have to do some more research. |
@abrender With the next server release, messages with priority 4+5 (high+max) will be FCM high priority messages |
I noticed that Instant Delivery is recommended for instant alerts because "Without instant delivery, messages may arrive with a significant delay".
A bit of snooping reveals that you can set the priority of a message to "high", which will "allow FCM to wake up a sleeping device when necessary". That functionality appears to be limited/bucketted but "if, in response to a high priority message, a notification is displayed in a way that is visible to the user, then your app standby bucket quota will not be consumed by that message".
The text was updated successfully, but these errors were encountered: