416
edits
Difference between revisions of "XEP-Remarks/XEP-0045: Multi-User Chat"
Jump to navigation
Jump to search
XEP-Remarks/XEP-0045: Multi-User Chat (view source)
Revision as of 18:26, 17 December 2022
, 18:26, 17 December 2022→Why do I need to host my MUC component on subdomain.example.org?: Mention disco#items on room to get occupant list
(New section: Why do I need to host my MUC component on subdomain.example.org?) |
(→Why do I need to host my MUC component on subdomain.example.org?: Mention disco#items on room to get occupant list) |
||
| Line 74: | Line 74: | ||
Clients will generally expect to be able to create rooms on the address that is given to them in disco#items on the host (the "MUC component"). | Clients will generally expect to be able to create rooms on the address that is given to them in disco#items on the host (the "MUC component"). | ||
[https://xmpp.org/extensions/xep-0045.html#disco-rooms disco#items on a component] will get you a list of rooms hosted on it, while [https://xmpp.org/extensions/xep-0045.html#disco-roomitems disco#items on a room] should get you a list of occupants, even though servers generally don't disclose the occupant list this way. It is possible to get the occupant list (presences) by joining the room. This seems to be the only possibly conflicting feature, if a room and a component were to be used on the same address. | |||
Maybe a more explicit disco feature should be added to say "You can create rooms off here". Without this, it isn't possible to say whether room creation is actually possible other than trying and reading the error. It would also probably look very awkward for a client to try to create a room off a "component"/"room" hosted at "foo@domain", trying to create "bar@foo@domain" which isn't a valid JID. | Maybe a more explicit disco feature should be added to say "You can create rooms off here". Without this, it isn't possible to say whether room creation is actually possible other than trying and reading the error. It would also probably look very awkward for a client to try to create a room off a "component"/"room" hosted at "foo@domain", trying to create "bar@foo@domain" which isn't a valid JID. | ||