webweaving: a bit on XMPP

So it looks like the client can have an embedded XMPP server, and an account on said server. Which means that the client can then use its Jabber account to send and receive updates. All without having to configure Jabber accounts at a central location.

And yes, the IP address of the user will most likely change with every time they log on to the internet, but that can be worked around by doing an external IP check/report, then using the reported external IP. Add a "username" as the resource in node@domain/resource.

Or maybe have a remote table to resolve username to IP. Then have node@domain/resource look like username@username/resource.

"The domain identifier for every server or service that will
communicate over a network MAY be an IP address but SHOULD be a fully
qualified domain name (see [DNS])."

(http://www.ietf.org/rfc/rfc3920.txt)