Unmoderated video chat
Since each occupant has its own occupant JID, an occupant can send a "private message" to a selected occupant via the service by sending a message to the intended recipient's occupant JID.
If the sender is a visitor (i.e., does not have voice in a moderated room), the service MUST return a error to the sender and SHOULD NOT reflect the message to all occupants; the only exception to this rule is that an implementation MAY allow users with certain privileges (e.g., a room owner, room admin, or service-level admin) to send messages to the room even if those users are not occupants.
An example follows (here the service changes the nickname to all lowercase). Occupant Changes Nickname, Modified by Service If the user attempts to change his or her room nickname to a room nickname that is already in use by another user (or that is reserved by another user affiliated with the room, e.g., a member or owner), the service MUST deny the nickname change request and inform the user of the conflict; this is done by returning a presence stanza of type "error" specifying a of the present occupant matches the bare JID of the user seeking to change his or her nickname, then the service MAY allow the nickname change.
In XMPP, availability is of course noted by a change in presence (specifically the If the room is configured to broadcast presence from entities with the occupant's role, the service then sends a presence stanza from the occupant changing his or her presence to the full JID of each occupant, including extended presence information about the occupant's role and full JID to those with privileges to view such information: Example 55.
This is done by including a status code of "170" in the initial presence that the room sends to the new occupant: Example 34.
If the user is entering a room in which the discussions are logged to a public archive (often accessible via HTTP), the service SHOULD allow the user to enter the room but MUST also warn the user that the discussions are logged.
If the room is non-anonymous, the service MAY include an A user might want to manage the amount of discussion history provided on entering a room (perhaps because the user is on a low-bandwidth connection or is using a small-footprint client).
Note well that this means the room subject (and changes to the room subject prior to the current subject) are not part of the discussion history.
Because the room needs to be involved in the invitation process only for members-only rooms, because members-only rooms are relatively rare, and because mediated invitations do not work when element whose value is the bare JID, full JID, or occupant JID of the inviter and send the invitation to the invitee specified in the 'to' address; the room SHOULD add the password if the room is password-protected): Example 57.