Hi Matthew, I wouldn't say it's not the standard behaviour of XMPP clients. In fact the only client I can think of that will use real JIDs for private messages in rooms is Pidgin (and, well, I think Adium too - but they share a lot of code). Ok (as mentioned in the other reply), I more or less tested only with Adium/Pidgin.
As a user I find this behaviour extremely irritating. People who are not on my roster message me, I don't know their nick or what room they came from, and if their server doesn't allow messages from non-contacts I also can't reply back to them. I can't see their presence, and I might not want to add a stranger to my roster just for one chat. 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. Yes, that’s exactly what I think as well. Adding a user to a roster only makes sense if you really like to stay in contact with her/him. It’s even more important if you don’t have a fully-fledged client (like Candy). Because then people might not even know what a roster is (because they just want to chat). - Michael
_______________________________________________ JDev mailing list Info: http://mail.jabber.org/mailman/listinfo/jdev Unsubscribe: [email protected] _______________________________________________
