Chat room 18
In addition, there is no one-to-one correspondence between roles and affiliations; for example, someone who is not affiliated with a room may be a (temporary) moderator, and a member may be a participant or a visitor in a moderated room. Roles are temporary in that they do not necessarily persist across a user's visits to the room and MAY change during the course of an occupant's visit to the room.
An implementation MAY persist roles across visits and SHOULD do so for moderated rooms (since the distinction between visitor and participant is critical to the functioning of a moderated room).
* Default; configuration settings MAY modify this privilege.
These two association types are distinct from each other in MUC, since an affiliation lasts across visits, while a role lasts only for the duration of a visit.
This specification (Multi-User Chat or MUC) is not compatible to the groupchat 1.0 protocol, but provides advanced features such as invitations, room moderation and administration, and specialized room types.
This document addresses common requirements related to configuration of, participation in, and administration of individual text-based conference rooms.
The Jabber/XMPP community developed and implemented a basic groupchat protocol as long ago as 1999.
That "groupchat 1.0" (GC) protocol provided a minimal feature set for chat rooms but was rather limited in scope.
Search for Chat room 18:
All of the requirements addressed herein apply at the level of the individual room and are "common" in the sense that they have been widely discussed within the Jabber/XMPP community or are familiar from existing text-based conference environments (e.g., Internet Relay Chat as defined in This limited scope is not meant to disparage such topics, which are of inherent interest; however, it is meant to focus the discussion in this document and to present a comprehensible protocol that can be implemented by client and service developers alike.