Chat room with no sign up request
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. If the client did not provide an 'id', the server MAY generate an 'id' and use it for all reflections of the same message (e.g. 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 The service SHOULD reflect the message with the same 'id' that was generated by the client, to allow clients to track their outbound messages. (The room MUST NOT send any discussion history before it finishes sending room presence as specified in the Presence Broadcast section of this document.) Whether such history is sent, and how many messages comprise the history, shall be determined by the chat service implementation or specific deployment depending on local service policy or room configuration. Delivery of Discussion History  information qualified by the 'urn:xmpp:delay' namespace to indicate that they are sent with delayed delivery and to specify the times at which they were originally sent. Service Sends New Occupant's Presence to New Occupant After sending initial presence as shown above, depending on local service policy or room configuration a room MAY send discussion history to the new occupant. itself (a service MAY ignore or reject messages that do not have a type of "groupchat").
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 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.
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.
The existence of two different invitation methods might cause confusion among client developers.
The service MUST send complete message stanzas only (i.e., it MUST not literally truncate the history at a certain number of characters, but MUST send the largest number of complete stanzas that results in a number of characters less than or equal to the 'maxchars' value specified).