jdev - 2022-11-30

hi all! when a muc-capable component shuts down, it should send a presence with status code 332. should this presence be of type "error" or "unavailable"? does the presence below look OK? it does not seem to trigger anything in the UI of gajim and movim, so I guess it must be wrong somehow? ```xml <presence type="error" to="participant@example.com/resource" from="room@conference.example.com"> <x xmlns="http://jabber.org/protocol/muc#user"> <status code="332" /> </x></presence> ``` ✏

I would have gone for unavailable

Looks like Prosody used to send it in `<presence type="unavailable"/>`

type=error without <error> seems weird

thanks! unavailable was my first attempt, but then I tried error. so the presence looks and neither gajim nor movim are actually handling it? ✏

thanks! unavailable was my first attempt, but then I tried error. so the presence looks OK and neither gajim nor movim are actually handling it? ✏

```lua local stanza = st.presence({type = "unavailable"}) :tag("x", {xmlns = "http://jabber.org/protocol/muc#user"}) :tag("item", { affiliation='none', role='none' }):up() :tag("status", { code = "332"}):up(); ```

oh, affiliation and role none are required?

That's how you say "you're kicked" and then the status code is why

Hm, do you see any example of only a <status> ?

https://xmpp.org/extensions/xep-0045.html#example-171 but then it's a message

ha, the "you were kicked" part was probably what I missed indeed, thanks

thanks a lot!

np :)

Seems there's no text about this in XEP-0045, just the registry entry. Feel free to PR suggested text?

Zash: sth like 6(Entity Use Cases).8 - MUC Service shuts down?

nicoco, under https://xmpp.org/extensions/xep-0045.html#service seems natural?

right. section 11. didn't go this far yet :-)

I scrolled trough the table of contents :)