On 9/26/06, Brian Safford <[EMAIL PROTECTED]> wrote:
> Apologies in advance for the off-topic post, but I'm wondering if anyone
> on this list has had any experience with the 'C' yahoo transport.

Yes, it breaks horribly with jabberd2 > s8 (not sure what it does with
jabber inc's xcp).  Each time you login it re-requests auth.  That's
what caused me to swap to the python yahoo transport, (and in time
what has caused the python transport to improve so much)

> Specifically if it is easy to disable the buddy list import function.

I doubt it, why would you want to disable this sort of functionality?
(unless it's those auth requests)

-- 
- Norman Rasmussen
 - Email: [EMAIL PROTECTED]
 - Home page: http://norman.rasmussen.co.za/
From [EMAIL PROTECTED]  Tue Sep 26 08:31:03 2006
From: [EMAIL PROTECTED] (Norman Rasmussen)
Date: Tue Sep 26 08:31:10 2006
Subject: [py-transports] Recent pyirct and pyyimt updates
Message-ID: <[EMAIL PROTECTED]>

For those following the CVS branches:

    * PyIRCt:
          o Fixed sending private messages in a channel
          o Tries to reconnect to the jabber server if the connection
fails on startup
          o Alter services detection to handle regional dns entries
(like ethereal)
          o Added adhoc command for /rules

    * PyYIMt:
          o Tries to reconnect to the jabber server if the connection
fails on startup
          o Detects avatar changes and send the new hash via presence
(both jep-0008 and jep-0153 style)
          o Make vCards work if the user doesn't have an avatar
          o Make vCards work in chatrooms
          o Added jabber:iq:gateway support
          o Added a config entry to enable/disable chatrooms

-- 
- Norman Rasmussen
 - Email: [EMAIL PROTECTED]
 - Home page: http://norman.rasmussen.co.za/
From [EMAIL PROTECTED]  Tue Sep 26 14:28:05 2006
From: [EMAIL PROTECTED] (Brian Safford)
Date: Tue Sep 26 14:28:14 2006
Subject: [py-transports] slightly off topic
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
        <[EMAIL PROTECTED]>
Message-ID: <[EMAIL PROTECTED]>

The jabber roster entry for each buddy shows up with
subscription='none', which appears to cause Jabber XCP to have lots of
extra roster activity whenever presence changes.

I'd really like to test the Yahoo python transport with Jabber XCP, but
am at a loss on how to even get started given the apparent absence of
documentation on how to configure the transport.

I've been able to get PyAIMt and PyMSNt working with Jabber XCP.  PyAIMt
and PyMSNt appear to have figured out what Jabber XCP requires, given it
has:

<!-- Use Jabber.com's XCP component protocol extensions. -->
<useXCP/>

It would be really nice if the Yahoo python transport could leverage
what PyAIMt and PyMSNt have done regarding Jabber XCP.

Regards,
Brian Safford
EDS

On Tue, 2006-09-26 at 10:20 +0200, Norman Rasmussen wrote:
> On 9/26/06, Brian Safford <[EMAIL PROTECTED]> wrote:
> > Apologies in advance for the off-topic post, but I'm wondering if anyone
> > on this list has had any experience with the 'C' yahoo transport.
> 
> Yes, it breaks horribly with jabberd2 > s8 (not sure what it does with
> jabber inc's xcp).  Each time you login it re-requests auth.  That's
> what caused me to swap to the python yahoo transport, (and in time
> what has caused the python transport to improve so much)
> 
> > Specifically if it is easy to disable the buddy list import function.
> 
> I doubt it, why would you want to disable this sort of functionality?
> (unless it's those auth requests)
> 

Reply via email to