[Standards] XEP-0045: Handling presence type='error' coming from s2s

Jonas Wielicki jonas at wielicki.name
Mon Dec 18 16:47:08 UTC 2017

On Freitag, 15. Dezember 2017 09:19:00 CET Jonas Wielicki wrote:
> As for the more general problem of how to handle s2s failure induced kicks,
> I think that a new status code which is used in addition to the 307 code
> (for compat) would be useful. This new code would indicate that the kick
> was caused by a technical error and not by a moderator removing a user
> (this would be reinforced by the absence of an <{…muc#user}actor/>
> element). New/updated clients could then adapt the view accordingly (and
> showing "$user got disconnected" instead of "$user got kicked" or "$user
> left"), while old clients retain the existing behaviour.

I made a Pull Request with a proposed wording:


kind regards,
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.jabber.org/pipermail/standards/attachments/20171218/f09ecac6/attachment.sig>

More information about the Standards mailing list