skip to content »

norilskmc.ru

No membership chating

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.

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.

In a moderated room, this privilege is restricted to occupants with a role of participant or higher. Occupant Sends a Message to All Occupants If the sender has voice in the room (this is the default except in moderated rooms) and the message does not violate any service-level or room-level policies (e.g., policies regarding message content or size), the service MUST change the 'from' attribute to the sender's occupant JID and reflect the message out to the full JID of each occupant. Service Reflects Message to All Occupants 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.

Discovering the Features Supported by a MUC Service 6.3. In MUC this is done by sending updated presence information to the room, specifically by sending presence to a new occupant JID in the same room (changing only the resource identifier in the occupant JID). Occupant Changes Nickname The service then sends two presence stanzas to the full JID of each occupant (including the occupant who is changing his or her room nickname), one of type "unavailable" for the old nickname and one indicating availability for the new nickname.

To allow for proper synchronization of these messages to the user's other clients by If the sender attempts to send a private message of type "groupchat" to a particular occupant, the service MUST refuse to deliver the message (since the recipient's client would expect in-room messages to be of type "groupchat") and return a A common feature of chat rooms is the ability for an occupant to change his or her nickname within the room.

Note: It is known that not all service implementations support MUC history management, so in practice a client might not be able to depend on receiving only the history that it has requested.

No membership chating-22

(Note: The 'urn:xmpp:delay' namespace defined in [15]; some implementations include both formats for backward compatibility.) The service MUST send all discussion history messages before delivering the room subject and any "live" messages sent after the user enters the room.

If a user attempts to enter a room while it is "locked" (i.e., before the room creator provides an initial configuration and therefore before the room officially exists), the service MUST refuse entry and return an If the room does not already exist when the user seeks to enter it, the service SHOULD create it; however, this is not required, since an implementation or deployment MAY choose to restrict the privilege of creating rooms. If the user attempts to change their room nickname but nicknames are "locked down", the service MUST either deny the nickname change request and return a presence stanza of type "error" with a In text chat systems such as IRC, one common use for changing one's room nickname is to indicate a change in one's availability (e.g., changing one's room nickname to "thirdwitch|away"). See the Nickname Conflict section of this document for details.This specification defines an XMPP protocol extension for multi-user text chat, whereby multiple XMPP users can exchange messages in the context of a room or channel, similar to Internet Relay Chat (IRC). The invitee MAY choose to formally decline (as opposed to ignore) the invitation; and this is something that the sender might want to be informed about.In addition to standard chatroom features such as room topics and invitations, the protocol defines a strong room control model, including the ability to kick and ban users, to name room moderators and administrators, to require membership or passwords in order to join the room, etc. In order to decline the invitation, the invitee MUST send a message of the following form to the It may be wondered why the invitee does not send the decline message directly to the inviter. This is done by including a status code of "170" in the initial presence that the room sends to the new occupant: Example 34.