> What part of XMPP is doing that? I think you're talking about a bug in an implementation of XMPP not the protocol itself. Its like saying you go to an address and get the wrong website. Hard to blame an issue like that on HTTP rather than a server or a client that implements it.
XMPP relies on clients having the Carbon Copy plugin installed.
Some clients have it installed, some clients do not.
If I have 3 devices connected to XMPP, which one gets a message sent to me is rather hard to determine. Often times it is the one I have most recently sent a message from, but other times it is not, and I will not get messages delivered to any of my other devices until I physically go home and log out of my desktop.
XMPP relies on clients having the Carbon Copy plugin installed.
Some clients have it installed, some clients do not.
If I have 3 devices connected to XMPP, which one gets a message sent to me is rather hard to determine. Often times it is the one I have most recently sent a message from, but other times it is not, and I will not get messages delivered to any of my other devices until I physically go home and log out of my desktop.