<html><head><style>body{font-family:Helvetica,Arial;font-size:13px}</style></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;">Hi Matthew,</div><div id="bloop_customfont" style="font-family:Helvetica,Arial;font-size:13px; color: rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br></div><div><blockquote type="cite" class="clean_bq" style="font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255);"><span><div><div>I wouldn't say it's not the standard behaviour of XMPP clients. In<span class="Apple-converted-space"> </span><br>fact the only client I can think of that will use real JIDs for<span class="Apple-converted-space"> </span><br>private messages in rooms is Pidgin (and, well, I think Adium too -<span class="Apple-converted-space"> </span><br>but they share a lot of code).<span class="Apple-converted-space"> </span></div></div></span></blockquote></div><p>Ok (as mentioned in the other reply), I more or less tested only with Adium/Pidgin.</p><p><br></p><div><div><div><div><blockquote type="cite" class="clean_bq" style="font-family: Helvetica, Arial; font-size: 13px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px; background-color: rgb(255, 255, 255);"><span><div><div>As a user I find this behaviour extremely irritating. People who are<span class="Apple-converted-space"> </span><br>not on my roster message me, I don't know their nick or what room they<span class="Apple-converted-space"> </span><br>came from, and if their server doesn't allow messages from<span class="Apple-converted-space"> </span><br>non-contacts I also can't reply back to them. I can't see their<span class="Apple-converted-space"> </span><br>presence, and I might not want to add a stranger to my roster just for<span class="Apple-converted-space"> </span><br>one chat.<span class="Apple-converted-space"> </span><br><br>I personally think if you start a message with a room occupant in the<span class="Apple-converted-space"> </span><br>UI, the protocol should do the same, converse with that occupant in<span class="Apple-converted-space"> </span><br>that room. If I have a chat open with someone already, I am generally<span class="Apple-converted-space"> </span><br>unlikely to open a second chat with them in a room we are both in<span class="Apple-converted-space"> </span><br>(unless I forgot about the first one perhaps). This approach is always<span class="Apple-converted-space"> </span><br>going to work, it is consistent from the user perspective (sometimes<span class="Apple-converted-space"> </span><br>JIDs are available, sometimes they are not...), and so on.<span class="Apple-converted-space"> </span></div></div></span></blockquote></div><p>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. </p><p>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). </p><p>- Michael</p><div></div></div></div><div></div></div></body></html>