<cassidy> daf: I'm trying to use it but got some problems. I got the right nick from RequestAliases() but not with the AliasesChanged signal.
<cassidy> daf: I suppose it's because user can define the alias they want for remote contacts or something
<cassidy> daf: So, what I did is to recall RequestAliases() in AliasChanged cb and use this alias instead of the one passed by the signal
<cassidy> daf: It seems to works fine but looks a little bit strange, don't it ?
<daf> hmm, that's odd
<cassidy> the alias from the signal is the hash of the pub key
<cassidy> and the alias from RequestAliases() is the right alias
<daf> internally, Gabble has a ranking of different alias sources
<daf> so what you may be seeing is that it emits the signal on a less-good source
<daf> but then later gets a better source and uses thast
<daf> can you try debugging it?
<cassidy> ok, I'm gonna take on look on gabble
<Robot101> hmm
<Robot101> what nickname storage are you using?
<cassidy> what do you mean ?
<Robot101> where are you changing the nickname to see if the signal works?
<cassidy> we have a _set_self_buddy_info() to send PEP properties. I add SetAliases on the self_handle there
<cassidy> I only change the alias of the local contact, not remote contacts
<Robot101> aha
<Robot101> aliases in gabble are implemented using: roster, <nick> (which you get/send in <presence> when subscribing to people) or by vcard
<Robot101> setting your own nick will change your vcard
<Robot101> so yeah, there's some bug there
<cassidy> I don't want to overwrite alias of remote contact as I always want to use the one defined by them
<Robot101> we want to add support for publishing your <nick> on a PEP node
<Robot101> but I think that needs some more generalised PEP machinery from daf
<cassidy> currently, it would be easier to just add a "name" in the OlpcBuddyInfo interface
<Robot101> yes, but we're trying to use the right XMPP constructs for stuff if possible
<cassidy> yeah, that's more sane, for sure. So, the bug here is that my AliasesChanged signal doesn't give me the good alias when a remote contact changes is own alias? right ?
<Robot101> you don't get any signals off the server when vcards change, so it's just something odd with emitting the right signals when we're changing our own vcard
<Robot101> it's still a bug though
<cassidy> ok. But so I won't be notified of remote alias changes until we use PEP to publish nick
<Robot101> right
<cassidy> ok, I understand. thanks for explanations :)