[Adium-devl] MSNp15 (libpurple im.pidgin.pidgin) in Adium 1.3.x
Robert Vehse
robert.vehse at gmx.de
Wed Sep 10 15:43:26 UTC 2008
Am 09.09.2008 um 00:15 schrieb Evan Schoenberg:
> 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
I'm happy to have merely one MSN-only contact in my list, not having
to rely on MSN.
However, from the standpoint of someone working in Trac and in the
forums MSN-Pecan looks like a regression to me. With MSNp9 we knew
there were certain features missing and most users had arranged
themselves with that and I cannot remember any MSN-related crashes.
Now I'm seeing a great influx of reports – a multitude of crashes
(at least nine of them right now!), connection problems, pictures and
aliases not showing and more.
For reference, here you can see all tickets with the "msn-pecan"
component: http://trac.adiumx.com/query?
status=new&status=assigned&status=reopened&component=msn-
pecan&order=type.
I can't say much about libpurple MSNp15 but MSN-Pecan seems almost as
bad what we had before and I never thought I would say that.
-Robby
More information about the devel
mailing list