On Donnerstag, 5. Oktober 2017 12:39:38 CEST Jonas Wielicki wrote: > One idea I have is to use (2), but also specify a new feature and > <presence/> payload for MUC (let’s call it <no-join/>). A MUC service would > handle it as follows: > > 1. If the sender is currently joined, the presence is handled as usual. > 2. If the sender is currently not joined, *no* GC 1.0 join takes place. > Instead, a <presence unavailable/> is sent back, which MAY carry the > original status code and message from when the sender was last removed > from the MUC and SHOULD include the 'kicked' status code. (In contrast to > <rejoin-if-needed/>, this does not rejoin the sender automatically.)
As there has been some confusion: here, it would make sense to also add a specific (to be defined) status code which indicates that this was a desync kick (as suggested in my first email in this thread), to avoid clients automatically re-joining after other kicks. kind regards, Jonas
signature.asc
Description: This is a digitally signed message part.
_______________________________________________ Standards mailing list Info: https://mail.jabber.org/mailman/listinfo/standards Unsubscribe: standards-unsubscr...@xmpp.org _______________________________________________
