I just fetched my own vcard, and I'm seeing my msn address instead of my Nick.
On 1/2/06, Stian B. Barmen <[EMAIL PROTECTED]> wrote: > > > It seems that the trunk transport does not use the <nick/> from the > > > spool xml file. My MSN ID is [EMAIL PROTECTED], and my nick > > is Stian but > > > my msn friends see my nick as [EMAIL PROTECTED] in their > > contact list. > > > Can you confirm this problem? (tested on latest rev) > > > > AFAIR the transport now (i.e. since 0.10) uses the nickname > > from your Jabber vCard or the vcard-temp:x:update nickname in > > presence stanzas. > > > > I have the nick in my vcard aswell, but still I experience this problem. Am I > the only one? > > Best regards > Stian B. Barmen > > > _______________________________________________ > py-transports mailing list > [email protected] > http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports > -- - Norman Rasmussen - Email: [EMAIL PROTECTED] - Home page: http://norman.rasmussen.co.za/ From [EMAIL PROTECTED] Mon Jan 2 17:43:40 2006 From: [EMAIL PROTECTED] (Lars T. Mikkelsen) Date: Mon Jan 2 17:43:59 2006 Subject: [py-transports] PyMSNt file transfer In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> On Mon, Jan 02, 2006 at 03:43:02PM +0100, Stian B. Barmen wrote: > I have the nick in my vcard aswell, but still I experience this > problem. Am I the only one? Now I also noticed this issue. It appears that my nickname is set to my username just after signing in, however, as soon as I change my status the nickname will be set correct. The attached patch fixes the issue for me. Best regards, Lars -------------- next part -------------- Index: src/tlib/msn/msnw.py =================================================================== --- src/tlib/msn/msnw.py (revision 86) +++ src/tlib/msn/msnw.py (working copy) @@ -323,7 +323,7 @@ class SavedEvents: def __init__(self): - self.nickname = "" + self.screenName = "" self.statusCode = "" self.personal = "" self.avatarImageData = "" @@ -333,8 +333,8 @@ def send(self, msncon): if self.avatarImageData: msncon.notificationClient.changeAvatar(self.avatarImageData, push=False) - if self.nickname or self.statusCode or self.personal: - msncon.changeStatus(self.statusCode, self.nickname, self.personal) + if self.screenName or self.statusCode or self.personal: + msncon.changeStatus(self.statusCode, self.screenName, self.personal) for listType, userHandle in self.addContacts: msncon.addContact(listType, userHandle) for listType, userHandle in self.remContacts: From [EMAIL PROTECTED] Mon Jan 2 17:58:35 2006 From: [EMAIL PROTECTED] (Lars T. Mikkelsen) Date: Mon Jan 2 17:58:50 2006 Subject: [py-transports] PyMSNt file transfer In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> On Mon, Jan 02, 2006 at 10:14:35PM +1100, James Bunton wrote: > Please test and let me know what bugs you find! I got this error earlier today: 2006/01/02 17:07 CET [NotificationClient,client] << OUT RCT 5 2006/01/02 17:07 CET [NotificationClient,client] Error in line: OUT RCT 5 (Invalid Number of Parameters for OUT) I have no idea why the server chose to disconnect me, and I guess this error isn't related to the latest updates in trunk. Best regards, Lars From [EMAIL PROTECTED] Mon Jan 2 22:27:23 2006 From: [EMAIL PROTECTED] (Lars T. Mikkelsen) Date: Mon Jan 2 22:27:34 2006 Subject: [py-transports] PyMSNt file transfer In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> On Mon, Jan 02, 2006 at 03:20:01PM +0200, Norman Rasmussen wrote: > it still doesn't like me: > > 2006/01/02 15:17 SAST [XmlStream,client] INFO :: > (u'[EMAIL PROTECTED]/Psi-Home', '[EMAIL PROTECTED]') > :: [Failure instance: Traceback: exceptions.TypeError: discoFail() > takes exactly 1 argument (2 given) > /usr/lib/python2.3/site-packages/twisted/xish/utility.py:21:__call__ > /home/norman/src/svn/PyMSNt.trunk/src/disco.py:121:onIq > /usr/lib/python2.3/site-packages/twisted/internet/defer.py:254:callback > > /usr/lib/python2.3/site-packages/twisted/internet/defer.py:315:_startRunCallbacks > --- <exception caught here> --- > > /usr/lib/python2.3/site-packages/twisted/internet/defer.py:328:_runCallbacks > ] :: discoFail :: FTReceive :: {'self': 'instance', 'err': > <twisted.python.failure.Failure exceptions.TypeError>} I was also getting these exceptions. Apparently they occur because Twisted Xish 0.1 doesn't have the Element.getElement() function, which is used in DiscoRequest.discoResponse(). To get iChat to accept the file transfer offers, I also had to rename the "profile" attribute of the file element to "xmlns". This change looks correct according to JEP-0096. The attached patch fixes both these issues. While file transfers work (both OOB and S5B) I'm getting a lot of these warnings in debug.log: 2006/01/02 22:52 CET [OneSwitchboardSession,client] wait_data 2006/01/02 22:52 CET [OneSwitchboardSession,client] Unpacked fields: 0x3840E30L 0x3840E34L 0x1231CL 0x4320DL 0x4B2L 0x1000030L 0x3B6D4D3L 0x0L 0x0L 0x2L 2006/01/02 22:52 CET [OneSwitchboardSession,client] Warning in transfer: <tlib.msn.msn.SLPLink_FileReceive instance at 0xb758d18c> field9,2 This is with Microsoft Messenger for Mac 5.0.0 sending the file. Best regards, Lars -------------- next part -------------- Index: src/disco.py =================================================================== --- src/disco.py (revision 86) +++ src/disco.py (working copy) @@ -260,7 +260,10 @@ features = [] - query = el.getElement("query") + query = None + for child in el.elements(): + if child.name == "query": + query = child if not query: return [] Index: src/ft.py =================================================================== --- src/ft.py (revision 86) +++ src/ft.py (working copy) @@ -97,7 +97,7 @@ si.attributes["profile"] = disco.FT si.attributes["id"] = self.sid file = si.addElement("file") - file.attributes["profile"] = disco.FT + file.attributes["xmlns"] = disco.FT file.attributes["size"] = str(self.legacyftp.filesize) file.attributes["name"] = self.legacyftp.filename # Feature negotiation From [EMAIL PROTECTED] Tue Jan 3 12:19:03 2006 From: [EMAIL PROTECTED] (Magnus Henoch) Date: Tue Jan 3 12:19:15 2006 Subject: [py-transports] Feature request: announcement messages Message-ID: <[EMAIL PROTECTED]> It would be nice if admins could send announcement messages in Py*. I imagine three kinds of messages: - To all online users - To all registered users (send immediately) - "Message of the day": send to all online users immediately, and send to others on next login (with ability to remove the MOTD) All of this through ad-hoc commands, of course. Admins will need advanced clients anyways. Unfortunately this doesn't bother me enough to make me write the code ;) Magnus From [EMAIL PROTECTED] Tue Jan 3 16:50:29 2006 From: [EMAIL PROTECTED] (Maarten Fonville) Date: Tue Jan 3 16:51:52 2006 Subject: [py-transports] Re: PyMSNt file transfer In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Lars T. Mikkelsen wrote: > I was also getting these exceptions. Apparently they occur because > Twisted Xish 0.1 doesn't have the Element.getElement() function, which > is used in DiscoRequest.discoResponse(). > > To get iChat to accept the file transfer offers, I also had to rename > the "profile" attribute of the file element to "xmlns". This change > looks correct according to JEP-0096. > > The attached patch fixes both these issues. While file transfers work > (both OOB and S5B) I'm getting a lot of these warnings in debug.log: > I tried the patch you supplied, but it didn't work for me to get S5B file transfers working :( (against someone with trillian 3.1, don't know about the official MSN client) Maarten -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2 (MingW32) iD8DBQFDuqtVXjGr8JbE19URAk8IAKCoXYdXF4NTvqT5tldkOFOnRMX/vgCeLpXX +GsdKO0INczzlK+HROpdnRw= =MVam -----END PGP SIGNATURE-----
