I'd like to point you to this one: https://mail.jabber.org/pipermail/
standards/2016-February/030925.html
Prosody does follow these business rules exactly.
Implementation details can be found here:
http://hg.prosody.im/prosody-modules/file/df86ce6bb0b4/mod_cloud_notify/business_rules.markdown
A
If iOS app has VoIP support it can use highly priority VoIP push
notifications (and can use it for any type of notifications - message or
voice call). It is delivered very fast and app can connect and determine
that it has an incoming call.
2018-04-13 13:33 GMT+05:00 Evgeny Khramtsov :
> Fri, 13
Fri, 13 Apr 2018 13:15:03 +0500
Ненахов Андрей wrote:
> The only correct way to send pushes is when user should recieve some
> new content (messages).
What about Jingle calls? Do we support them in the XEP? How a server
knows what to send?
___
Standard
Not necessary.
The only correct way to send pushes is when user should recieve some new
content (messages). If Prosody sends push notifications beyond message
ones, Prosody should be fixed.
2018-04-13 5:39 GMT+05:00 Anurodh Pokharel :
> I've been testing push notifications on Monal for iOS for
I've been testing push notifications on Monal for iOS for about a year,
pointing to the implementation on Prosody. I have observed that
notifications are sent for stanzas beyond message ones. In my case I only
care to alert the user if there are new messages, so the constant need to
connect and ch
