FCM time_to_live "throttling" specifics?

[ky...@kayak.com]

Since GCM is now FirebaseCM, seems like I should ask here:

https://developers.google.com/cloud-messaging/concept-options#ttl

"advantage of specifying the lifespan of a message is that GCM never throttles messages with a time_to_live value of 0 seconds."

Under what circumstances are FCM msgs throttled?

It doesn't sound like it's to prevent push notification bombing of a user because the docs go on to say that it does a best effort to send msgs if the TTL is set to 0 which seems backwards from what I'd expect if you want the to prevent the user from being bombed?

Is it N msgs/hour if you have TTL > 0?

or N msgs/day or N msgs/week? so when they connect their device after being offline for a while, they don't get flooded?

And does msg priority affect the throttling at all?

Thanks for any clariications...

 ken

[Doug Stevenson]

Ken,

We occasionally apply limits to message rate to preserve user experience on devices (aka battery) and to reduce abuse. Most apps never hit these. Those that do commonly don't even notice because it turns out we aren't that dramatic about it. We encourage you to reach out to us if you observe problems. We will engage with you to understand your use case and determine if you are hitting these limits. However, as a policy we don't publish our throttling limits and reserve the right to adjust them based on the concerns mentioned already.

Doug