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

Note on MAM history prior to user joining channel

Browse Source
This commit is contained in:
Steve Kille 2017-02-19 16:10:06 +00:00 committed by Sam Whited
parent 9b58aac74e
commit 088968327f
1 changed files with 4 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
xep-0369.xml
View File

@ -1420,6 +1420,9 @@ This approach enables flexible support of multiple clients for a MIX channel pa
<li>The client MAY wish to display messages from a recent time period, perhaps finding more messages if the user subsequently requests.</li> <li>The client MAY wish to display messages from a recent time period, perhaps finding more messages if the user subsequently requests.</li>
</ol> </ol>
<p>To achieve this, the client will query the user's own MAM archive using &xep0313;, with the query filtered by the channel JID. This gives the client flexibility to retrieve and display message history in a manner appropriate to the client implementation.</p> <p>To achieve this, the client will query the user's own MAM archive using &xep0313;, with the query filtered by the channel JID. This gives the client flexibility to retrieve and display message history in a manner appropriate to the client implementation.</p>
<p>
The only exception to this is when a user wishes to access message history in the channel prior to when the user joined the channel. To achieve this, the client will use MAM to retrieve message history directly from the MAM Archive of the MUX channel.
</p>
</section3> </section3>
@ -2236,7 +2239,7 @@ This approach enables flexible support of multiple clients for a MIX channel pa
<section2 topic="MIX Management and Discovery" anchor="user-server-disco"> <section2 topic="MIX Management and Discovery" anchor="user-server-disco">
<p> <p>
Most interaction between a MIX client and a MIX channel is directly between the client and the channel channel. The participant's server relays the message but does not modify the messages. In particular configuration management and discovery is direct. Interaction will be direct, unless explicitly stated otherwise. Most interaction between a MIX client and a MIX channel is directly between the client and the channel. The participant's server relays the message but does not modify the messages. In particular configuration management and discovery is direct. Interaction will be direct, unless explicitly stated otherwise.
</p> </p>
</section2> </section2>
<section2 topic="IQ Support on Local Server" anchor="mix-diso"> <section2 topic="IQ Support on Local Server" anchor="mix-diso">