PyICQt actually is implementing an XEP that defines how to handle nickname
changes, and after adding the contacts to your roster, they should all
resolve to nicknames automatically.... assuming your client supports the
proper XEP. (I don't recall which one off the top of my head, it's called
User Nicknames)
I did think about, at one point, tracking the nicknames on PyICQt itself
and having a real [EMAIL PROTECTED] type thing. I soon
realized, however, that there is no such thing as a unique nickname, so
you might have 3 people on your roster all with the nickname ninja.
So using the Jabber nickname is the ideal thing but it's hard to transmit
that information over jabber user. It's unfortunate that external
transports don't get some sort of better control over the roster. =/
Anyway, I think the latest Psi supports nicknames. You may be able to log
in with it (latest as in beta 0.11) once, let it fill in your nicknames,
and then log in with whatever your normal client is. Once the nicknames
are set in your roster, they're set. =)
Daniel
--
"The most addictive drug in the world is music."
- The Lost Boyz
> Hi !
>
> I just spent some times configuring ejabberd, icq & msn transport with
> the pyicq-t and pymsn-t transports.
> Now, here is the problem : I have a lot of icq contacts, and when I
> register with the icq transport, I receive an authorisation request
> from all my contacts. Now, whether I authiorise it or not, the ICQ
> contacts added in my roster show like : [EMAIL PROTECTED]
>
> The thing is that I have no clue which icq number is associated to
> which nickname. But if I click on "user info", I can see the nickname
> of the guy, and it's even written in the icq transport xml spool
> files.
>
> I wonder if there is a way to display the nickname instead of the
> associated ICQ number in the roster ? I don't really know how things
> works, but I guess the icq transport is responsible for that ? unless
> it is the final jabber client... ?
>
> Sorry for the weird english.
> Thank you !
> _______________________________________________
> py-transports mailing list
> py-transports@blathersource.org
> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
>
_______________________________________________
py-transports mailing list
py-transports@blathersource.org
http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports
