> In a situation like this it helps tremendously to study the xml I/O.
> Transports may play tricks and set the name element of the roster item
> to something automatically. A xml log reveals this. I think I display
> the bare (ugly) JID by default but haven't checked it.
Remember that I can't yet copy/paste from the XML console... ;-)
Oh, yes: you can see this bug in the latest video/screenshot tutorial. :-)
> In a situation like this it helps tremendously to study the xml I/O.
> Transports may play tricks and set the name element of the roster item
> to something automatically. A xml log reveals this. I think I display
> the bare (ugly) JID by default but haven't checked it.
Remember that I can't yet copy/paste from the XML console... ;-)
Oh, yes: you can see this bug in the latest video/screenshot tutorial. :-)