? ????????? ?? ??????? 08 ???? 2006 17:55 James Bunton ???????(a): > On 08/06/2006, at 11:15 PM, Alexey Nezhdanov wrote: > > Noticed quite unexpected feature of pyMSN-t - after I registered > > account with > > transport and mutally subscribed it with another account, > > registered in gaim > > messages begin coming not from initial account nickname, but from > > name of > > jabber account that transport is registered with. > > It seems that pyMSN-t changed the nickname at some point. How can I > > disable > > that feature (or where to look in the code to comment it out?). It > > seems that > > config file not have that option. > > > > Forgot to mention: I'm using r170 - that is also applicable to my > > previous > > mail about transport going down in case of rapid receiving stanzas. > > > > -- > > Respectfully > > Alexey Nezhdanov > > Yes. This is known and expected behaviour for the transport. > It sets your nickname one of the following (in order of preference): > * The <nickname/> tag sent in a presence packet > * The NICKNAME field of your vCard > * The FN field of your vCard > * The user portion of your JID > > There is no way to turn it off. You could possibly hack the source to > disable it, but I wouldn't recommend it. I suggest you just set your > desired nickname in your Jabber vCard. It gets checked once every > time you log in with the transport, and again if you're lucky and > your client sends the right data in the presence packets. For me it is a problem because I'm using "good" (with nickname set) MSN account with temporarily registered random jabber account. That is done within script so there is absolutely no hint about what nickname should be. It is just supposed that it is already set to correct value.
> James -- ? ?????????, ??????? ????????
