On Mittwoch, 11. Juli 2018 04:02:23 CEST Kim Alvefur wrote: > Hello list, > > I have implemented tombstones for destroyed MUC rooms. My reading of the > sacred texts did not give me enlightenment as how to inform someone > who's attempting to enter the remains of such a place. I've so far opted > to return an <presence type=unavailable> with the same <destroyed> child > that was in the inital announcement of the rooms destruction. > > Of the clients I’ve tested so far, only Gajim seems to understand this. > Swift says something unspecific about failure to enter the room, while > Pidgin and poezio say nothing. > > So basically, this is the reply one gets to a MUC join: > > ``` xml > <presence type="unavailable" id="" to="me@localhost/r" > from="a@gc.localhost/n"> <x xmlns="http://jabber.org/protocol/muc#user";> > <item affiliation="none" role="none"/> > <destroy>You see only a crater.</destroy> > </x> > </presence> > > ``` > > Does this make sense?
Is there a reason to not use a presence type="error"? I’d expect clients to handle those already. I’d use a <gone/> type error, which encodes the semantics perfectly. <gone/> also allows for permanent redirects (which I think <destroy/> does, too). 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 _______________________________________________
