If a moderator attempts to kick himself, the service MAY deny the request and return a &conflict; error to the sender. (Although the act of kicking oneself may seem odd, it is common in IRC as a way of apologizing for one's actions in the room.)
In a moderated room, a moderator may want to manage who does and does not have "voice" in the room (i.e., the ability to send messages to all occupants). Voice is granted based on the visitor's room nickname, which the service will convert into the visitor's full JID internally. The moderator grants voice to a visitor by changing the visitor's role to "participant" (the <reason/> element is optional):
+In a moderated room, a moderator may want to manage who does and does not have "voice" in the room (i.e., the ability to send messages to all occupants). Voice is granted based on the visitor's room nickname, which the service will convert into the visitor's full JID internally. The moderator grants voice to a visitor by changing the visitor's role to "participant".
The <reason/> element is OPTIONAL:
+The <reason/> element is OPTIONAL:
+The service MUST then inform the moderator of success:
@@ -2628,6 +2664,18 @@An admin or owner can ban one or more users from a room. The ban MUST be performed based on the occupant's bare JID. In order to ban a user, an admin MUST change the user's affiliation to "outcast".
The <reason/> element is OPTIONAL.
+The <reason/> element is OPTIONAL.
+The service MUST add the user to the member list and then inform the admin of success:
@@ -2823,6 +2885,20 @@The <reason/> element is OPTIONAL.
+The service MUST remove the user from the member list and then inform the moderator of success:
@@ -2995,6 +3071,20 @@The <reason/> element is OPTIONAL.
+The service MUST add the user to the moderator list and then inform the admin of success:
@@ -3030,6 +3120,20 @@The <reason/> element is OPTIONAL.
+The service MUST remove the user from the moderator list and then inform the admin of success:
@@ -3868,6 +3972,20 @@The <reason/> element is OPTIONAL.
+The service MUST add the user to the owner list and then inform the owner of success:
@@ -3917,6 +4035,20 @@The <reason/> element is OPTIONAL.
+A service MUST NOT allow an owner to revoke his or her own ownership privileges if there are no other owners; if an owner attempts to do this, the service MUST return a &conflict; error to the owner. However, a service SHOULD allow an owner to revoke his or her own ownership privileges if there are other owners.
@@ -4031,6 +4163,20 @@The <reason/> element is OPTIONAL.
+The service MUST add the user to the admin list and then inform the owner of success:
@@ -4080,6 +4226,20 @@The <reason/> element is OPTIONAL.
+The service MUST remove the user from the admin list and then inform the owner of success:
@@ -5124,8 +5284,7 @@ xmpp:darkcave@macbeth.shakespeare.lit?invite;jid=hecate@shakespeare.lit;passwordNote: Because MUC roomnicks follow the Resourceprep profile of stringprep, they are allowed to contain a space character, whereas IRC nicknames do not. Although a given client MAY support quotation characters for this purpose (resulting in commands such as '/ban "king lear" insanity is no defense'), most common quotation characters (such as " and ') are also allowed by Resourceprep, thus leading to added complexity and potential problems with quotation of roomnicks that contain both spaces and quotation characters. Therefore it is NOT RECOMMENDED for Jabber clients to support IRC-style shortcut commands with roomnicks that contain space characters.
-Note: Many Jabber clients also implement a '/me ' command, where the command is followed by a verb or verb phrase (e.g., '/me laughs'). This command does not result in any MUC or IRC protocol action and is therefore not shown in the foregoing table. Instead, the message is sent as-is (e.g., <body>/me laughs</body>) and the receiving client performs string-matching on the character data of the &BODY; element to determine if the message begins with the string '/me '; if it does the receiving client will show the message in a special format, usually italicized text sometimes prepended by the "*" character:
-* stpeter laughs
+Note: Many Jabber clients also implement a '/me ' command as described in &xep0237;. This command does not result in any MUC or IRC protocol action and is therefore not shown in the foregoing table.