From cf6ac3e6c5cbd577ae77fed09711a6d12d985311 Mon Sep 17 00:00:00 2001 From: Melvin Keskin Date: Wed, 16 Feb 2022 15:18:51 +0100 Subject: [PATCH] XEP-0163: Release version 1.2.2 Add comma and fix typo --- xep-0163.xml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/xep-0163.xml b/xep-0163.xml index 96be6e2e..a4afddf4 100644 --- a/xep-0163.xml +++ b/xep-0163.xml @@ -26,6 +26,12 @@ pep &stpeter; &ksmith; + + 1.2.2 + 2022-02-16 + melvo +

Add comma and fix typo

 + 1.2.1 2018-03-18 @@ -406,7 +412,7 @@ -

As mentioned, a PEP service MUST send the last published item to all new subscribers and to all newly-available resources for each subscriber, including the account owner itself. (That is, the default value of the "pubsub#send_last_published_item" node configuration field must be "on_sub_and_presence"; this behavior essentially mimics the functionality of presence as defined in XMPP IM.) When processing a new subscription, the service MAY send not only the last published item but instead all items that are currently associated with the node (i.e., up to the maximum number of items at the node, which might be one if the node is a "singleton node" as described in XEP-0060). If the service has knowledge about the datetime that a subscriber's newly-available resource last received updated information from the node (e.g., as described in &xep0256;) then it MAY also send more items that only the last published item to the newly-available resource.

+

As mentioned, a PEP service MUST send the last published item to all new subscribers and to all newly-available resources for each subscriber, including the account owner itself. (That is, the default value of the "pubsub#send_last_published_item" node configuration field must be "on_sub_and_presence"; this behavior essentially mimics the functionality of presence as defined in XMPP IM.) When processing a new subscription, the service MAY send not only the last published item but instead all items that are currently associated with the node (i.e., up to the maximum number of items at the node, which might be one if the node is a "singleton node" as described in XEP-0060). If the service has knowledge about the datetime that a subscriber's newly-available resource last received updated information from the node (e.g., as described in &xep0256;), then it MAY also send more items than only the last published item to the newly-available resource.

Note: The "on_sub_and_presence" setting relates to the subscriber's presence, not the publisher's presence.