This XEP needs at least a note discouraging the use of the fields "message- sender" and "message-body" because of privacy implications.
In the wild the field "message-body" is left empty for low priority pushes (in short: pushes not related to message stanzas containing a body) and set to something like "New Message!" for high priority pushes. This is at least needed for iOS apps not having VoIP permissions. The field "message-count" is ambiguous and should be removed completely or defined what is counted by it. The prosody implementation hardcodes its value to "1". The field "pending-subscription-count" is not used by prosody at all. I don't know if other implementations use it. The business rules proposed by Daniel should be incorporated into the XEP as well: https://mail.jabber.org/pipermail/standards/2016-February/030925.html Prosody's implementation rationale for these are explained here: https:// hg.prosody.im/prosody-modules/file/tip/mod_cloud_notify/business_rules.markdown Cheers, Thilo Am Dienstag, 2. Oktober 2018, 10:14:21 CEST schrieb Sam Whited: > On Tue, Oct 2, 2018, at 10:05, Ненахов Андрей wrote: > > Is this enough, or is there some sort of special procedure for a > > nomination? > Nope, there's no sort of special procedure (that I'm aware of). I've added > it to the council agenda and we will discuss it sometime in the next few > weeks (probably not tomorrow since it's a bit last minute, but you never > know). > > —Sam > _______________________________________________ > Standards mailing list > Info: https://mail.jabber.org/mailman/listinfo/standards > Unsubscribe: standards-unsubscr...@xmpp.org > _______________________________________________ _______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org _______________________________________________
