From 404be3213e710d2aecb7f9951cc846bfc9787947 Mon Sep 17 00:00:00 2001 From: JC Brand Date: Wed, 3 Feb 2021 14:58:07 +0100 Subject: [PATCH] XEP-0452: Clarify that users need to have their nicks registered in order for the MUC to be able to notify them when they're not present. --- xep-0452.xml | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/xep-0452.xml b/xep-0452.xml index 32de86a0..28f5f0ec 100644 --- a/xep-0452.xml +++ b/xep-0452.xml @@ -51,9 +51,10 @@ -

A user's client must be able to receive forwarded groupchat messages from a MUC in which the user is mentioned, while not having an active session in that MUC (i.e. without joining it).

-

The user will have to be affiliated with the MUC, in order to receive the forwarded groupchat messages and whether or not mesages are forwarded will be determined by a configuration setting on the MUC.

-

The MUC owner(s) will therefore determine whether notifications are sent out, and may opt in or out by being affiliated or not with the MUC. Affiliations are long lived associations between users and MUCs, and therefore transcend individual sessions in MUCs.

+

A user's client must be able to receive forwarded groupchat messages from a MUC in which that user is mentioned, while not having an active session in that MUC (i.e. without joining it).

+

For this to be possible, the MUC needs to know the user's JID and MUC nickname even when that user is not currently present in the MUC. &xep0045; section 7.10 ("Registering with a Room") describes a mechanism whereby a user can register a nickname with a MUC and it is recommended that this is the mechanism used to keep track of users across sessions.

+

Whether or not mesages are forwarded will be determined by a configuration setting on the MUC.

+

The MUC owner(s) will therefore determine whether notifications are sent out, and if activated, users may opt in or out (or have that done for them by a privileged user) by having their nicknames registered or not with the MUC.