[jdev] Handling of MUC within Candy

[Matthew Wild]

On 20 January 2014 20:28, Stefan Strigler <stefan.strigler at gmail.com> wrote:
>
> On 20.01.2014, at 21:03, Matthew Wild <mwild1 at gmail.com> wrote:
>
>> I personally think if you start a message with a room occupant in the
>> UI, the protocol should do the same, converse with that occupant in
>> that room. If I have a chat open with someone already, I am generally
>> unlikely to open a second chat with them in a room we are both in
>> (unless I forgot about the first one perhaps). This approach is always
>> going to work, it is consistent from the user perspective (sometimes
>> JIDs are available, sometimes they are not...), and so on.
>
> One alternative approach could be to
>
> a1) make all rooms be non-anonymous to know the real-jid of each participant
> OR
> a2) make sure users can't change their nickname and use the same throughout all rooms
> b) have a hidden default room (a lobby) that acts as a central hub sharing information about how's considered online
> c) use this lobby for direct messaging
>
> Depending on your environment this approach might make sense or not at all ;)

Well, yes. I should note that my arguments are based on general usage
on the XMPP network. I think closed environments (for example Michael
mentioned an in-game chat) are able to make their own decisions about
these kinds of things, as they ultimately control the whole thing from
the server to the protocol, client and overall user experience. I'm
quite certain there are scenarios where messaging user-to-user using
only real JIDs would work better.

Regards,
Matthew