[Adium-devl] MSNp15 (libpurple im.pidgin.pidgin) in Adium 1.3.x

[Felipe Contreras]

On Tue, Sep 9, 2008 at 2:06 AM, Thibault Martin-Lagardette
<dracognizer at gmail.com> wrote:
> On Sep 9 , 2008, at 00:15, Evan Schoenberg wrote:
>
>> I'd like to propose moving Adium 1.3.x back to im.pidgin.pidgin for
>> MSN connectivity – that is, MSNp15 – for Adium 1.3.2.  libpurple
>> 2.5.1 fixed the immediate influx of msnp15 problems, and what we're
>> left with now is that it appears to be the better choice looking
>> forward.  As always, working with the library with a wider audience
>> helps us with bug reporting and development, and msn-pecan continues
>> to have problems sending display pictures and doesn't support
>> sending offline messages (which also means sending to invisible
>> users).
>>
>> I'd prefer that our side of helping to debug (and fix!) problems be
>> directed towards the ultimate code base we'll be utilizing.
>>
>> The primary known issue with msnp15 is that apparently it sends a
>> lot of data at signon, which means some users on slow connections
>> end up getting timeout errors.
>>
>> N.B.: I don't use MSN at all.  If you're using trunk and MSN, I'd
>> like to hear about any other concerns you have.
>>
>> -Evan_______________________________________________
>> Adium-devl mailing list
>> Adium-devl at adiumx.com
>> http://adiumx.com/mailman/listinfo/adium-devl_adiumx.com
>
>
> I do use MSN, but never encountered any issue talking with offline /
> invisible people. Even with Adium 1.3.1.
>
> However, even with Adium 1.3, I had plenty of crashes due to the msn-
> pecan library... And they rarely were the same errors. But 1.3.1 betas
> and stable never crashed yet. Wait and see... :)
>
> What does msn-pecan has that msnp15 doesn't ? Status messages ?

I don't like to compare the features, partly because I think msn-pecan
has better foundations, but also because it has less features :P

The next feature of msn-pecan is something that msnp15 doesn't have;
fast (direct) file transfers, there's partial code in the 'next'
branch, but my bet is that it will take some time.

-- 
Felipe Contreras