darkrain: well, it can do different things internally of course. but they just have CHAT object with id no matter how many people are there
darkrain: I presume when the id is still the same, it's same also internally, but that doesn't have to be the true
skype is moving away from p2p. all (or most) chat has already been moved to microsofts backend. http://www.theverge.com/2012/10/22/3529600/skype-for-windows-8-screenshots-release-date-october-26th
that's because p2p is harder to evesdrop conversations
Eelco: yes, interesting, eh?
Is it possible to share the slides on screen via Webex?
working on it
(No ™ just for hildjj)
just a moment
The video feeds really good right now, BTW.
As for some easy to install XMPP service recipes (sorry for not putting this in earlier) this might be nice to look into: https://juju.ubuntu.com/ <https://juju.ubuntu.com/docs/index.html>
Oh, that's Emil in shot now?
Dave Cridland, right
And now a pot plant.
Just looking at the fis spec - is there a particular reason why it couldn't be a pep node?
easy XMPP server install also via Puppet, e.g. https://github.com/rtyler/puppet-prosody
Ash no reason, and that would be best for file change events
@darkrain yeah noticed...
the main thing is that it would be better done as collection nodes, because of arbitrary directory depths
so a single node item could become too large to deal with nicely
Victor: Have you used it? or is that you?
I built my own puppet extension. Not really difficult btw
(and got the alias right)
emil is talking about http://datatracker.ietf.org/doc/draft-ivov-xmpp-cusax/
Adrian mentioned P-Asserted-Identity https://www.ietf.org/rfc/rfc3325
however, that won't work, because it is defined as follows:
A P-Asserted-Identity header field value MUST consist of exactly one
name-addr or addr-spec. There may be one or two P-Asserted-Identity
values. If there is one value, it MUST be a sip, sips, or tel URI.
If there are two values, one value MUST be a sip or sips URI and the
other MUST be a tel URI.