Tigase public XMPP services are the only one that offer MIX - state of the art approach to groupchat messages! Take advantage of it by using xmpp.cloud with our clients - BeagleIM and SiskinIM.

Our free, public XMPP installation: xmpp.cloud is packed with features: domain hosting, file uploads, TURN/STUN server for your audio/video calls, high availability due to running as a cluster with automatic recovery and all of this while scoring 100% XMPP compliance and perfect A grade in a popular test tools. And now it got even better!

Group chat - the problem

For a very, very long time MUC (defined in XEP-0045: Multi-User Chat) was the only option available in XMPP realm that allowed people to exchange messages in a group. At the beginning, when it was typical to have constant connection to the server, everything was working just fine, but over the course of time new challenges arose. People started to use more and more their mobile devices and connections to the server became anything but permanent (be that because of spotty internet connection or limitations imposed by mobile device manufacturer). In that environment MUC started to show it’s architectural problems: if you are not connected you are not an occupant of the MUC room and therefore you don’t receive any messages. This was a problem!

Previous attempts to improve the situation

There a couple of attempts to mitigate this situation: XEP-0410: MUC Self-Ping (Schrödinger’s Chat) for the situations where federation link would get broken and user would be unaware that it’s not in a room anymore, Multi-User Chat Light, which would allow to permanently register to the room without presence or vendor specific non XSF variations of “MUC subscription”. There were also workarounds with with long-lived user sessions (terminating underlying network connection without closing XML stream) that were quite inefficient.

What is XMPP MIX

MIX stands for Mediated Information eXchange (MIX) and it’s basics are defined in XEP-0369: Mediated Information eXchange (MIX):

“an XMPP protocol extension for the exchange of information among multiple users through a mediating service. The protocol can be used to provide human group communication and communication between non-human entities using channels, although with greater flexibility and extensibility than existing groupchat technologies such as Multi-User Chat (MUC). MIX uses Publish-Subscribe to provide flexible access and publication, and uses Message Archive Management (MAM) to provide storage and archiving.”

Specification outlines several requirements of which those seems to be the most interesting:

  • “A user’s participation in a channel persists and is not modified by the user’s client going online and offline.”
  • “Multiple devices associated with the same account can share the same nick in the channel, with well-defined rules making each client individually addressable.”
  • “A reconnecting client can quickly resync with respect to messages and presence.”

MIX itself serves as an umbrella for set of MIX-related XMPP extensions that specify the exact protocol. Two of them are required for the implementation to be considered as MIX compliant:

In addition to the above extensions, there are several other that are optional:

How does it work?

The most stark difference to MUC is that MIX requires support from both server that hosts the channel and user’s server. This is done to facilitate the notion that the user (and not particular connection or client application) joined the group and allows for greater flexibility in terms of message delivery (which can be send to one or many connections, or even generates notification over PUSH). Another important difference is the flexibility to choose which notifications from the channel user wants to receive (that can be messages, presence, participators or node information). In the most basic approach, when user decides to join a channel, it sends an IQ stanza to it’s own local server indicating address of the desired channel and list of MIX nodes to which it wants to subscribe. User’s server then forward’s subscription request to the destination, MIX server. As a result user receives subscription confirmation and from this point onwards will receive notifications from the channel, independently of it’s current network connection. Another essential bit of MIX is the reliance on XEP-0313: Message Archive Management to control message history and the complementary interaction between MIX server and user’s server. Main channel history is handled by the MIX server, but user’s that joined the channel will retrieve and synchronise message history querying their local server, which will maintain complete history of the channels that user has joined (based on the received notifications). This also means that even if the channel is removed, user is still able to access it’s history through local MAM archive (limited to time when user was member of the channel). As a result, chatter between client, client’s server and mix server is also reduced and unnecessary traffic is eliminated.

Benefits for mobile-first applications relying on push

All of this helps especially with clients that relay on constrained environment - be that unreliable network connection or operating system that limits time that application can be running. Because there is no dependency on the dynamic state of user presence/connection the issue with occupant leaving and (re)joining the room is eliminated - user gets the notification always. What’s more, thanks to shared responsibilities between MIX and user’s server, and the latter getting all notifications from MIX channel, it’s possible to generate notifications without relaying on workarounds (that most of the time are not reliable or impact resource usage).

In case of Tigase XMPP server it gets better thanks to our experimental filtering groupchat notifications feature, which allows user controll when to receive PUSH notifications from group chats (always, only when mentioned or never)

Is MUC obsolete?

We think that MIX is the way forward, but we also know that this won’t happen overnight. Because of that MUC is still supported in all our applications and Tigase XMPP Server implements XEP-0408: Mediated Information eXchange (MIX): Co-existence with MUC to allow all non-MIX client to participate in MIX channel discussions using MUC protocol.

Tigase xmpp.cloud service with MIX support

Our xmpp.cloud installation offers MIX today! It supports MIX-CORE, MIX-PAM (with MAM), MIX-ADMIN, MIX-MUC, MUX-MISC (message retraction)

For now, neither MIX-PRESENCE (we only inform about channel participants without explicit publication their presence) nor MIX-ANON (there is only support for ‘private messages’) are available.

open channel

How to use it

First of all - you need an XMPP client that supports MIX, for now this is limited to BeagleIM for macOS and SiskinIM for iOS. Creating and joining channel is not different to joining MUC room:

  1. select open channel:

open channel

  1. fill out the form:

channel join form

  1. start chatting!


Other benefits of xmpp.cloud

As mentioned at the beginning of this article, in addition to MIX, xmpp.cloud offers a lot:

  • never worry about server downtime - it’s a clustered installation, which means that at every point in time there will always be at least one server to connect to
  • host your own domain for free - it’s enough to point your domain’s DNS SRV records to tigase.me and add it in xmpp.cloud system (as described in the documentation)
  • better PUSH for your mobile devices - more granular configuration and encrypted notifications
  • anti-SPAM mechanism to squash unwanted messages
  • free audio/video server (STUN/TURN) for you calling needs
  • perfect A security grade: xmpp.net security score
  • 100% XMPP compliance 100% XMPP compliance