Abstract: This specification defines XMPP protocol extension allowing XMPP clients to specify JIDs for which the XMPP server SHOULD NOT generate Push Notifications.
- 1. Introduction
- 2. Scope
- 3. Requirements
- 4. Mute notifications
- 4.1. Discovering support
XEP-0357: Push Notifications defines a way for the XMPP server to generate push notifications by publishing them to the application specific XMPP Push Notification Component. However, that extension does not specify any rules for generating push notifications, nor any rules for filtering them forcing XMPP servers to publish notifications about any incoming messages while XMPP client is not connected.
This extension was created to provide a way to inform the XMPP server that it SHOULD not generate push notifications for particular JIDs.
This documents specifies ways of defining rule for filtering generated push notifications by skipping push notifications from particular JIDs. This rule is an extension to payload send to enable push notifications as specified in XEP-0357: Push Notifications.
The XMPP server MUST support XEP-0357: Push Notifications as this specification is the extension to push notifications.
In some cases users want not to receive notifications from particular sender, ie. from some bots sending them unimportant messages.
Before enabling this feature, a client SHOULD determine whether user’s server supports filtering push notifications based on the list of muted conversations; to do so, it MUST send a Service Discovery (XEP-0030)  information query to the user’s bare JID:
Example 1. Client queries server regarding protocol support
<iq firstname.lastname@example.org/mobile' email@example.com' id='x13' type='get'> <query xmlns='http://jabber.org/protocol/disco#info'/> </iq>
Example 2. Server communicates protocol support
<iq firstname.lastname@example.org' email@example.com/balcony' id='disco1' type='result'> <query xmlns='http://jabber.org/protocol/disco#info'> <identity category='account' type='registered'/> <feature var='tigase:push:filter:muted:0'/> ... </query> </iq>
To enable this filter, XMPP client SHOULD send enable request with
<muted /> element qualified by the
This element SHOULD contains list of
<item /> elements which should have
jid attribute set to the bare JID for which push notifications SHOULD NOT be generated.
Example 3. Enabling filter
<iq type='set' id='x42'> <enable xmlns='urn:xmpp:push:0' jid='push-5.client.example' node='yxs32uqsflafdk3iuqo'> <muted xmlns='tigase:push:filter:muted:0'> <item firstname.lastname@example.org' /> <item email@example.com' /> </muted> </enable> </iq>