moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-25 10:42:19 -05:00
Code Issues Releases Wiki Activity

Editorial

Browse Source
This commit is contained in:
Steve Kille 2018-05-22 16:26:48 +01:00
parent 81f8ca7350
commit cd3e4d0116
1 changed files with 12 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

16
xep-0369.xml
View File

@ -35,6 +35,14 @@
<shortname>MIX-CORE</shortname> <shortname>MIX-CORE</shortname>
&ksmithisode; &ksmithisode;
&skille; &skille;
<revision>
<version>0.11.1</version>
<date>2018-05-22</date>
<initials>sek</initials>
<remark><p>
Editorial;
</p></remark>
</revision>
<revision> <revision>
<version>0.11.0</version> <version>0.11.0</version>
<date>2018-05-21</date> <date>2018-05-21</date>
@ -429,7 +437,7 @@
<ol> <ol>
<li>MIX has "channels", which are equivalent to MUC rooms.</li> <li>MIX has "channels", which are equivalent to MUC rooms.</li>
<li>MIX separates out various services, in particular messages and presence. A MUC channel is implemented as a set of PubSub nodes, and a user (not client) can subscribe to a set of nodes. This control means that users can subscribe to presence and/or messages, which gives useful flexibility. This addresses requirements 3 and 5. Subscribing to message and presence nodes gives a service broadly equivalent to MUC.</li> <li>MIX separates out various services, in particular messages and presence. A MIX channel is implemented as a set of PubSub nodes, and a user (not client) can subscribe to a set of nodes. This control means that users can subscribe to presence and/or messages, which gives useful flexibility. This addresses requirements 3 and 5. Subscribing to message and presence nodes gives a service broadly equivalent to MUC.</li>
<li>Messages and presence sent by a MIX channel use the same formats as MUC and do not use PubSub encodings.</li> <li>Messages and presence sent by a MIX channel use the same formats as MUC and do not use PubSub encodings.</li>
@ -446,7 +454,7 @@
<li>In MIX, a Nick belongs to the user and not to each client.</li> <li>In MIX, a Nick belongs to the user and not to each client.</li>
<li> <li>
Presence is exchanged in MIX by use of a proxy JID, which is a stable JID on the domain of the MUC channel that identifies the user. This proxy JID is used instead of the "Nick as a Resource" mechanism in MUC. To support this, the proxy JID is a primary part of defining a MIX channel participant. Proxy JIDs are also used in MIX-ANON to provide a "JID Hidden" mechanism, to give a service similar to MUC semi-anonymous, that will prevent JID harvesting (requirement 7). Presence is exchanged in MIX by use of a proxy JID, which is a stable JID on the domain of the MIX channel that identifies the user. This proxy JID is used instead of the "Nick as a Resource" mechanism in MUC. To support this, the proxy JID is a primary part of defining a MIX channel participant. Proxy JIDs are also used in MIX-ANON to provide a "JID Hidden" mechanism, to give a service similar to MUC semi-anonymous, that will prevent JID harvesting (requirement 7).
</li> </li>
@ -890,7 +898,7 @@
<p>The default MIX model is that only channel participants are allowed to subscribe to nodes. A MIX channel MAY allow non-participant subscription to some nodes. This will be handled by clients directly subscribing to the desired PubSub nodes.</p> <p>The default MIX model is that only channel participants are allowed to subscribe to nodes. A MIX channel MAY allow non-participant subscription to some nodes. This will be handled by clients directly subscribing to the desired PubSub nodes.</p>
<p>The user's server needs to make roster changes as part of the join functionality, as specified in MIX-PAM. This means that the join request to the MIX service will come from the user's server from the user's bare JID.</p> <p>The user's server needs to make roster changes as part of the join functionality, as specified in MIX-PAM. This means that the join request to the MIX service will come from the user's server from the user's bare JID.</p>
<example caption="User's Server sends Join request to MIX Channel"><![CDATA[ <example caption="User's Server sends Join request to MIX Channel"><![CDATA[
qn<iq type='set' <iq type='set'
from='hag66@shakespeare.example' from='hag66@shakespeare.example'
to='coven@mix.shakespeare.example' to='coven@mix.shakespeare.example'
id='E6E10350-76CF-40C6-B91B-1EA08C332FC7'> id='E6E10350-76CF-40C6-B91B-1EA08C332FC7'>
@ -1345,7 +1353,7 @@ qn<iq type='set'
<section1 topic='Acknowledgements' anchor='ack'> <section1 topic='Acknowledgements' anchor='ack'>
<p>Peter St Andre provided key early input to MIX and worked on the original specification with Kevin Smith. </p> <p>Peter St Andre provided key early input to MIX and worked on the original specification with Kevin Smith. </p>
<p>Thanks to the following who have made contributions to the ongoing MIX specification development: Dave Cridland, Tarun Gupta, Philipp Hancke, Waqas Hussain, Timothée Jaussoin, Evgeny Khramtsov, Georg Lukas, Tobias Markmann, Ralph Meijer, Edwin Mons, Emmanuel Gil Peyrot, Manuel Rubio, Florian Schmaus, Lance Stout, Sam Whited, Jonas Wielicki, Matthew Wild and one anonymous reviewer.</p> <p>Thanks to the following who have made contributions to the ongoing MIX specification development: W. Martin Borgert, Dave Cridland, Tarun Gupta, Philipp Hancke, Waqas Hussain, Timothée Jaussoin, Evgeny Khramtsov, Georg Lukas, Tobias Markmann, Ralph Meijer, Edwin Mons, Emmanuel Gil Peyrot, Manuel Rubio, Florian Schmaus, Lance Stout, Sam Whited, Jonas Wielicki, Matthew Wild and one anonymous reviewer.</p>
</section1> </section1>
</xep> </xep>