Difference between revisions of "Multi-Session Nicks"
Jump to navigation
Jump to search
| Line 43: | Line 43: | ||
== Optimal XMPP server behavior == | == Optimal XMPP server behavior == | ||
* a server should not carbon-copy incoming MUC-PMs to other clients ( | * a server should not carbon-copy incoming MUC-PMs to other clients (this requires tracking of MUC presence, or analysis of the <x/> element) | ||
* a server should carbon-copy outgoing ("sent") MUC-PMs to other clients that are joined to the MUC, | * a server should carbon-copy outgoing ("sent") MUC-PMs to other clients that are joined to the MUC | ||
** if the server knows for sure those messages are MUC-PMs, it should add an <x/> tag to the message before CCing | |||
** as a fallback, the server may send the carbon copy to all (other) clients if it doesn't track MUC presence | |||
== Client-side workaround behavior == | == Client-side workaround behavior == | ||