moparisthebest/xeps
1
0
Fork 0
mirror of https://github.com/moparisthebest/xeps synced 2024-11-21 08:45:04 -05:00
Code Issues Releases Wiki Activity

XEP-0045: change feature according to Council feedback

Browse Source
This commit is contained in:
Georg Lukas 2018-03-08 10:39:50 +01:00
parent 7123a7a4ed
commit b017284eea
1 changed files with 7 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

14
xep-0045.xml
View File

@ -1180,13 +1180,13 @@
name='A Dark Cave'
type='text'/>
<feature var='http://jabber.org/protocol/muc'/>
<feature var='http://jabber.org/protocol/muc#stable_id'/>
<feature var='muc_passwordprotected'/>
<feature var='muc_hidden'/>
<feature var='muc_temporary'/>
<feature var='muc_open'/>
<feature var='muc_unmoderated'/>
<feature var='muc_nonanonymous'/>
<feature var='muc_stable_id'/>
</query>
</iq>
]]></example>
@ -1932,7 +1932,7 @@
</message>
]]></example>
<p>The service SHOULD reflect the message with the same 'id' that was generated by the client, to allow clients to track their outbound messages. If the client did not provide an 'id', the server MAY generate an 'id' and use it for all reflections of the same message (e.g. using a UUID as defined in &rfc4122;).</p>
<p><strong>Note:</strong> the requirement to reflect the 'id' attribute was added in version 1.31 of this XEP. Servers following the new specification SHOULD advertise that with a disco info feature of 'muc_stable_id' on both the service domain and on individual MUCs, so that clients can check for support.</p>
<p><strong>Note:</strong> the requirement to reflect the 'id' attribute was added in version 1.31 of this XEP. Servers following the new specification SHOULD advertise that with a disco info feature of 'http://jabber.org/protocol/muc#stable_id' on both the service domain and on individual MUCs, so that clients can check for support.</p>
<p>If the sender is a visitor (i.e., does not have voice in a moderated room), the service MUST return a &forbidden; error to the sender and MUST NOT reflect the message to all occupants. If the sender is not an occupant of the room, the service SHOULD return a &notacceptable; error to the sender and SHOULD NOT reflect the message to all occupants; the only exception to this rule is that an implementation MAY allow users with certain privileges (e.g., a room owner, room admin, or service-level admin) to send messages to the room even if those users are not occupants.</p>
</section2>
@ -5016,6 +5016,11 @@
<desc>Support for the muc#roominfo FORM_TYPE</desc>
<doc>XEP-0045</doc>
</var>
<var>
<name>http://jabber.org/protocol/muc#stable_id</name>
<desc>This MUC will reflect the original message 'id' in 'groupchat' messages.</desc>
<doc>XEP-0045</doc>
</var>
<var>
<name>muc_hidden</name>
<desc>Hidden room in Multi-User Chat (MUC)</desc>
@ -5066,11 +5071,6 @@
<desc>Semi-anonymous room in Multi-User Chat (MUC)</desc>
<doc>XEP-0045</doc>
</var>
<var>
<name>muc_stable_id</name>
<desc>This MUC will reflect the original message 'id' in 'groupchat' messages.</desc>
<doc>XEP-0045</doc>
</var>
<var>
<name>muc_temporary</name>
<desc>Temporary room in Multi-User Chat (MUC)</desc>