[Standards] XEP-0045 Room (JID) aliases

Maxime Buquet pep at bouah.net
Wed May 2 12:46:15 UTC 2018

On 2018/05/02, Florian Schmaus wrote:
> On 01.05.2018 13:03, Maxime Buquet wrote:
> > On 2018/05/01, Dave Cridland wrote:
> >>> I wanted to have fancyname at muc and serious-business at muc, pointing to
> >>> the same room.
> >>>
> >>> For this particular use case an alias might be best, The component knows
> >>> what other has joined what JID and speaks to them via this JID. I would
> >>> also be ok with a redirect though, having the component state "business
> >>> happens _there_".
> >>>
> >>> Redirect implies client support I assume, but that would also allow for
> >>> redirects to other components.
> >>>
> >>>
> >> Right.
> >>
> >> But if you have it in the same domain, then the domain can manage all this
> >> without the client being at all aware - there's no need for a specification
> >> here, since you're just using the existing one.
> > 
> > Which existing one? Can you point me to the place in 0045 for this?
> I think what Dave means is that a MUC service could simply merge two
> rooms, so that all participants appear in both rooms and both rooms have
> a single configuration, subject, etc.

As a muc admin, how do I tell the muc component that I want this
feature? Maybe this can be specified somewhere?

Maxime “pep” Buquet
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://mail.jabber.org/pipermail/standards/attachments/20180502/6435806c/attachment.sig>

More information about the Standards mailing list