[Standards] Proposed XMPP Extension: MUC Auto-Join

Peter Saint-Andre stpeter at jabber.org
Fri Jun 1 21:15:08 UTC 2007

Rachel Blackman wrote:
>> On one hand, I really like having a Conference Room (which is just a
>> JID) on my roster. It's integrated with what I want to do, the Roster
>> GUI is already defined and present, and I'm used to interacting with
>> people and starting a conversation by clicking on a user in the roster.
>> It's a very pragmatic solution, and fits quite well.
>> On the other hand, a conference room is different, and having it on the
>> roster doesn't make sense. For example, looking at my roster I can't
>> tell a conference room from a normal user. Maybe I threw it in a Group
>> called "Conference Rooms", but that's pretty weak in terms of metadata.
> I think honestly we might want to consider:
> * A 'category' in the roster items, such as category='conference';
>   a blank category is assumed to be 'client'.  Categories would be taken
>   from disco category types.  This would allow clients to sort chatrooms
>   (or add a custom client-side avatar) in some manner appropriate for the
>   UI.

Can't you get this info via caps?

> * Some method to do a 'from' presence subscription with a chatroom.  I
>   may not want auto-invites, but I may want presence.  This is a great
>   thing because, let's say a conference server goes offline.  Boom, the
>   conference rooms vanish from my roster, and I know they're unavailable.
>   When they're online, I just click on one and boom, I join.

Right, you get that with a mutual subscription. The 'to' gives you 
entity capabilities, but nothing says you must make the subscription 

Oh and BTW nothing says that a conference room could not have an avatar, 
a vCard, and everything else.


-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/x-pkcs7-signature
Size: 7358 bytes
Desc: S/MIME Cryptographic Signature
URL: <http://mail.jabber.org/pipermail/standards/attachments/20070601/0c3f94cf/attachment.bin>

More information about the Standards mailing list