Difference between revisions of "Tech pages/Multi-User Chat"

Jump to navigation Jump to search
(→‎Discussion Venues: removed the list that was deleted in 2013)
Line 40: Line 40:
* Smack (Java)
* Smack (Java)
* XMPP4R (Ruby)
* XMPP4R (Ruby)
== Discussion Venues ==
The XMPP Standards Foundation maintains a dedicated email list ([http://mail.jabber.org/mailman/listinfo/muc muc@xmpp.org]) about MUC, intended as a low-volume venue for discussion of MUC implementation and protocol issues. As with all XSF technology lists, the muc@xmpp.org list is open to all interested individuals.
* Info page and subscription information
* Subscribe via email
* Discussion archives

Latest revision as of 13:12, 5 December 2017


MUC is Multi-User Chat, an XMPP extension for multi-party information exchange similar to Internet Relay Chat (IRC), whereby multiple XMPP users can exchange messages in the context of a room or channel. 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. Because MUC rooms are based on XMPP, they can be used to exchange not only plaintext message bodies but a wide variety of XML payloads.


MUC is defined in one primary specification (XEP-0045) and several ancillary specifications:



The following XMPP servers include built-in support for MUC:

  • ejabberd
  • Jabber XCP
  • Openfire
  • Prosody
  • Tigase

External Components

The following standalone components can be used with a wide variety of XMPP servers:

  • mu-conference
  • palaver


  • Adium
  • Gajim
  • Jappix
  • JWChat
  • mcabber
  • Pidgin
  • Profanity
  • Psi/Psi+
  • Salut à Toi


  • AnyEvent:XMPP (Perl)
  • gloox (C++)
  • jabber-net (.Net)
  • libpurple (C)
  • Smack (Java)
  • XMPP4R (Ruby)