[Standards] UPDATED: XEP-0369 (Mediated Information eXchange (MIX))
kevin.smith at isode.com
Tue Sep 6 08:18:22 UTC 2016
> On 6 Sep 2016, at 09:00, Daurnimator <quae at daurnimator.com> wrote:
> On 6 September 2016 at 00:59, XMPP Extensions Editor <editor at xmpp.org> wrote:
>> Version 0.3 of XEP-0369 (Mediated Information eXchange (MIX)) has been released.
>> Abstract: This document defines 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.
>> Changelog: Addressing comments from review of 0.2 and expansion/clarification of MUC/MIX dual working (sek)
>> Diff: https://xmpp.org/extensions/diff/api/xep/0369/diff/0.2.3/vs/0.3
>> URL: http://xmpp.org/extensions/xep-0369.html
> Section 3:
>> Each participant is addressable by a single bare JID, which is a proxy JID (not the user's real JID) to make it straightforward to hide the user's real JID from other channel participants. Full JIDs comprised of this bare JID plus a resource are then constructed, allowing visibility into the number of online resources participating in a channel.
> Are the resources of full jids masked too?
> Section 5.1.3:
>> leaving the channel is a permanent action for a user across all clients, not just a matter of telling the channel that the user is not currently available or for a single client
> How can a user opt out of receiving messages on one of their (many) resources?
We sort this out as part of the PAM story.
> Section 5.1.6:
>> Unlike in Multi-User Chat (XEP-0045)  where coming online is a special action, coming online in MIX is implicit when presence status is set
> In MUC it didn't have to be; infact, often joining a room was no
> different to updating your presence.
In MUC it did have to be, because the join needed a special payload, and was sent as directed presence, not as broadcast.
More information about the Standards