Sorry for being so dumb, but I don't understand what will this change for the end-user.
For now, using psi, you see a very sexy [EMAIL PROTECTED] if you add a contact. But Psi can retrieve the nickname in the "add new contact" dialog. What will change with this Patch ? (anyway, many thanks to all people who contribute to free software :-) ) Ploum On 4/15/05, Daniel Henninger <[EMAIL PROTECTED]> wrote: > *chuckle* I was wondering that myself but elected to "just apply it" this > morning instead of mucking with it. ;D I'll go back and ditch the nick > attribute and adjust things accordingly. > > Daniel > > -- > "The most addictive drug in the world is music." > - The Lost Boyz > > > On Fri, Apr 15, 2005 at 10:24:39PM +1000, James Bunton wrote: > >> Just wondering, why didn't you use the name argument to > >> sendRosterImport instead of making a new one? > >> > >> --- > >> > >> James > >> > >> > >> On 15/04/2005, at 9:16 PM, Jonas ?dahl wrote: > >> > >> >Server side nicknames imported from the server side contact list isn't > >> >properly propagated. This patch adds this functionality. > >> > > >> >As roster-subsync isn't supported in any clients that we know of there > >> >is a > >> >web registration form that Magnus has made. > >> > > >> >http://zion.olf.sgsnet.se:8080/wakka/WUR > >> > > > > > Good point :) > > > > We didn't notice it, because name was used to create the jid one level up > > in > > icqt.py in updateSSIContact. The nick variable there is required but not > > in > > sendRosterImport. Thanks for noticing. > > > > /Jonas > > _______________________________________________ > > py-transports mailing list > > [email protected] > > http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports > > > > _______________________________________________ > py-transports mailing list > [email protected] > http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports > From [EMAIL PROTECTED] Fri Apr 15 17:17:09 2005 From: [EMAIL PROTECTED] (=?ISO-8859-1?Q?Jonas_=C5dahl?=) Date: Fri Apr 15 17:17:21 2005 Subject: [py-transports] Nicknames in roster-subsync in PyICQ-t In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> Ploum Ploum wrote: >Sorry for being so dumb, but I don't understand what will this change >for the end-user. > >For now, using psi, you see a very sexy [EMAIL PROTECTED] if >you add a contact. >But Psi can retrieve the nickname in the "add new contact" dialog. > >What will change with this Patch ? (anyway, many thanks to all people >who contribute to free software :-) ) > >Ploum > >On 4/15/05, Daniel Henninger <[EMAIL PROTECTED]> wrote: > > >>*chuckle* I was wondering that myself but elected to "just apply it" this >>morning instead of mucking with it. ;D I'll go back and ditch the nick >>attribute and adjust things accordingly. >> >>Daniel >> >>-- >>"The most addictive drug in the world is music." >> - The Lost Boyz >> >> >> >>>On Fri, Apr 15, 2005 at 10:24:39PM +1000, James Bunton wrote: >>> >>> >>>>Just wondering, why didn't you use the name argument to >>>>sendRosterImport instead of making a new one? >>>> >>>>--- >>>> >>>>James >>>> >>>> >>>>On 15/04/2005, at 9:16 PM, Jonas ?dahl wrote: >>>> >>>> >>>> >>>>>Server side nicknames imported from the server side contact list isn't >>>>>properly propagated. This patch adds this functionality. >>>>> >>>>>As roster-subsync isn't supported in any clients that we know of there >>>>>is a >>>>>web registration form that Magnus has made. >>>>> >>>>>http://zion.olf.sgsnet.se:8080/wakka/WUR >>>>> >>>>> >>>>> >>>Good point :) >>> >>>We didn't notice it, because name was used to create the jid one level up >>>in >>>icqt.py in updateSSIContact. The nick variable there is required but not >>>in >>>sendRosterImport. Thanks for noticing. >>> >>> To the end user this will mean that when registering to the transport with a client with roster-subsync support, all the names will be as they were on the ICQ contact list. Though, as far as I know, no client supports this except WUR (http://zion.olf.sgsnet.se:8080/wakka/WUR) which can be used to register with a transport via a web interface. Feel free to test this on our server, http://www.cd.chalmers.se/projekten/jabber/medlem.html (it's in swedish though). /Jonas -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 256 bytes Desc: OpenPGP digital signature Url : http://modevia.com/pipermail/py-transports/attachments/20050415/adef362b/signature.pgp From [EMAIL PROTECTED] Fri Apr 15 22:19:33 2005 From: [EMAIL PROTECTED] (James Bunton) Date: Fri Apr 15 22:19:46 2005 Subject: [py-transports] PyMSNt update In-Reply-To: <[EMAIL PROTECTED]> References: <[EMAIL PROTECTED]> <[EMAIL PROTECTED]> Message-ID: <[EMAIL PROTECTED]> Damn. I was hoping I'd fixed that with the message trackingg :| Well, at least fixed it so that any undelivered messages were returned as errors. Thanks for letting me know it's still not working. I'll have another look at it. --- James On 16/04/2005, at 2:04 AM, Gonzalo Barrio wrote: > I just download and try it. It works fine but the problem that I send > to you is not resolved. > I don't know why it's happening but I can reproduce it always. > The only thing I notice is that the problematic contacts are behind > http > proxys, they use messenger 6.2 with proxy http. They can chat with all > 6.2 messenger without problem but with PyMSN only if they start the > conversation, and if they keep the chat window open. When they close no > other message arrive to they, but they can send me messages if they re > open the chat window. > I can't find anything else relevant but I can search. > > Thanks James for all. > > Gonzalo Barrio. > > > James Bunton wrote: > >> Hi all. >> >> As some of you might know, I've been doing lots of bugfixing on PyMSNt >> lately. >> The latest CVS is quite a lot more stable than any previous release. >> >> Right now it's running on Portugal Telecom servers, with up to 500 >> concurrent sessions. >> >> I've just put up a tarball of what I'm planning to release as 0.9.3 >> soon. You can grab it from >> http://msn-transport.jabberstudio.org/tarballs >> Either that or just run "cvs update" in your 0.9.x installation. >> >> The major updates are: >> * debug.log file is moveable by sending SIGHUP >> * SIGHUP also reloads the config file >> * Tracks messages sent to MSN servers for more reliable messaging >> * debug.log smartness. Only log 100 lines before exceptions, as well >> as the exception itself >> * Config file parser warns rather than dies if a config option is not >> understood >> * Stability fixes >> * More stability fixes >> >> If you manage to break this in any way please let me know. I'd like to >> make 0.9.3 as solid as possible. >> >> >> After this I'll either continue working on file transfer, or start on >> avatars. >> Hopefully I'll know soon :) >> >> Happy testing everybody! >> >> --- >> >> James >> >> _______________________________________________ >> py-transports mailing list >> [email protected] >> http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports >> >> > > > _______________________________________________ > py-transports mailing list > [email protected] > http://www.modevia.com/cgi-bin/mailman/listinfo/py-transports >
