Difference between revisions of "Multi-Session Nicks"

Jump to navigation Jump to search
2 bytes removed ,  08:07, 28 February 2019
m
no edit summary
m
(One intermediate revision by one other user not shown)
Line 10: Line 10:
* [https://www.ejabberd.im/ ejabberd]
* [https://www.ejabberd.im/ ejabberd]
* [http://isode.com/products/m-link.html M-Link]
* [http://isode.com/products/m-link.html M-Link]
* [https://igniterealtime.org/projects/openfire/index.jsp Openfire]
* [https://igniterealtime.org/projects/openfire/ Openfire]


It might be possible to implement nick sharing on an XMPP server, so it only sends a single presence to a MUC component. That would require the XMPP server to cache the MUC state information.
It might be possible to implement nick sharing on an XMPP server, so it only sends a single presence to a MUC component. That would require the XMPP server to cache the MUC state information.
Line 77: Line 77:
|M-Link x.xx||?||?||?||?||?
|M-Link x.xx||?||?||?||?||?
|-
|-
|prosody 0.9||forwards all||?||to IQ sender||to ?, marked with <x>, carbon prevention||?
|prosody 0.9 - 0.10||forwards all||?||to IQ sender||to ?, marked with <x>, carbon prevention||?
|-
|-
|prosody trunk||primary session (first joined)||primary session||to IQ sender||to all sessions, marked with <x>, carbon prevention||<x> with <item>s for all sessions
|prosody 0.11+||primary session (first joined)||primary session||to IQ sender||to all sessions, marked with <x>, carbon prevention||<x> with <item>s for all sessions
|-
|-
|}
|}
216

edits

Navigation menu