Difference between revisions of "XEP-Remarks/XEP-0045: Multi-User Chat"
Jump to navigation
Jump to search
| Line 14: | Line 14: | ||
It's not specified what should happen if an entity sends an initial presence when it's already joined. Implementations should behave towards the joining entity like it successfully joined. | It's not specified what should happen if an entity sends an initial presence when it's already joined. Implementations should behave towards the joining entity like it successfully joined. | ||
= MUC PM messages are not distinguishable from other MUC messages = | |||
http://mail.jabber.org/pipermail/standards/2015-May/029819.html | |||
Revision as of 10:37, 8 May 2015
Stable Message IDs
http://mail.jabber.org/pipermail/standards/2014-July/029012.html
Ambiguities
http://mail.jabber.org/pipermail/standards/2014-April/028805.html
Introduces 'ofrom' Extended Stanza Addressing (XEP-33) type
in http://xmpp.org/extensions/xep-0045.html#enter-history, which is not found in XEP-33 (nor XEP-33s schema).
MUC join
It's not specified what should happen if an entity sends an initial presence when it's already joined. Implementations should behave towards the joining entity like it successfully joined.
MUC PM messages are not distinguishable from other MUC messages
http://mail.jabber.org/pipermail/standards/2015-May/029819.html