13
edits
Difference between revisions of "Multi-Session Nicks"
Jump to navigation
Jump to search
no edit summary
Neustradamus (talk | contribs) m |
|||
| (2 intermediate revisions by one other user not shown) | |||
| Line 7: | Line 7: | ||
Nick sharing is known to be supported by the following MUC service implementations: | Nick sharing is known to be supported by the following MUC service implementations: | ||
* [https://www.ejabberd.im/ ejabberd] | * [https://www.ejabberd.im/ ejabberd] | ||
* [https://github.com/ortuman/jackal Jackal IM] | |||
* [http://isode.com/products/m-link.html M-Link] | * [http://isode.com/products/m-link.html M-Link] | ||
* [https://metronome.im/ Metronome IM] | |||
* [https://www.erlang-solutions.com/products/mongooseim.html Mongoose IM] | |||
* [https://igniterealtime.org/projects/openfire/ Openfire] | * [https://igniterealtime.org/projects/openfire/ Openfire] | ||
* [https://prosody.im/ Prosody] | |||
* [https://tigase.net/xmpp-server/ Tigase XMPP Server] | |||
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 83: | Line 87: | ||
|Mongoose IM||?||?||?||?||? | |Mongoose IM||?||?||?||?||? | ||
|- | |- | ||
| | |Openfire||?||?||?||?||? | ||
|- | |- | ||
| | |Prosody 0.9 - 0.10||forwards all||?||to IQ sender||to ?, marked with <x>, carbon prevention||? | ||
|- | |||
|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 | |||
|- | |||
|Tigase 7.0.0+||Configurable per-room, default highest priority||N/A for multi-nick||N/A for multi-nick||to all sessions, NOT-marked with <x>||? | |||
|- | |- | ||
|} | |} | ||