>>>>> DH == Daniel Henninger writes:
DH> What version of Twisted2 are you running?  It might be that it needs
DH> an upgrade.

I cleaned up Twisted and freshly installed TwistedSumo-2.0.1.
Now it prints this deprecation messages:
/usr/lib/python2.4/site-packages/twisted/web/proxy.py:22: 
DeprecationWarning: twisted.protocols.http has moved to twisted.web.http. 
See http://twistedmatrix.com/projects/web.
  from twisted.protocols import http
/usr/local/src/pyaim-t/src/tlib/domish.py:425: DeprecationWarning: 
twisted.protocols.sux has moved to twisted.web.sux. See 
http://twistedmatrix.com/projects/web.
  from twisted.protocols import sux

But it works perfectly!

Seems that Twisted-2.1.0 doe currently not work.

Thanks for all your help!

-- 
Marcus
From [EMAIL PROTECTED]  Tue Oct 25 14:37:33 2005
From: [EMAIL PROTECTED] (Magnus Henoch)
Date: Tue Oct 25 14:36:54 2005
Subject: [py-transports] PyMSNt: roster-subsync packets don't include
        nickname
In-Reply-To: <[EMAIL PROTECTED]> (James Bunton's
        message of "Sun, 23 Oct 2005 01:03:17 +1000")
References: <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>

James Bunton <[EMAIL PROTECTED]> writes:

> In that case its possible that you haven't see the nicknames of these 
> contacts yet.
> You can only see somebody's nickname if they're online. Whenever the 
> official MSN client receives a nickname, it stores that in your MSN 
> roster on the server.
> Your MSN roster is where the nicknames are coming from. So if they've 
> never been stored there by the official MSN client, then you won't get 
> them in roster pushes.

That makes sense.  I haven't used an MSN client for years...

The program I'm hacking is a registration tool that authorizes all
contacts, and (hopefully) gives them sensible names in the roster.
What would be the best way to achieve that?

Magnus
From [EMAIL PROTECTED]  Tue Oct 25 21:16:01 2005
From: [EMAIL PROTECTED] (James Bunton)
Date: Tue Oct 25 21:16:21 2005
Subject: [py-transports] PyMSNt: roster-subsync packets don't include
        nickname
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>

On 26/10/2005, at 12:37 AM, Magnus Henoch wrote:

> James Bunton <[EMAIL PROTECTED]> writes:
>
>> In that case its possible that you haven't see the nicknames of these
>> contacts yet.
>> You can only see somebody's nickname if they're online. Whenever the
>> official MSN client receives a nickname, it stores that in your MSN
>> roster on the server.
>> Your MSN roster is where the nicknames are coming from. So if they've
>> never been stored there by the official MSN client, then you won't get
>> them in roster pushes.
>
> That makes sense.  I haven't used an MSN client for years...
>
> The program I'm hacking is a registration tool that authorizes all
> contacts, and (hopefully) gives them sensible names in the roster.
> What would be the best way to achieve that?

If they're not online, and MSN official client hasn't previously stored 
their nick on the server list, there's nowhere to get a better name for 
them.
You could maybe set them as [EMAIL PROTECTED] to look a bit nicer, I 
wouldn't recommend that though because some clients may look for roster 
entries with no name attribute to handle differently.

---

James

Reply via email to