On Wed, 2008-01-23 at 06:51 -0500, Evan Schoenberg wrote:
> I get asked by those crazy MSN users all the time what the status of
> MSNp14 is. Per the roadmap, there's just one open issue... is that an
> accurate reflection of where it stands?
Apology for the late reply.
No, it's not an accurate reflection of the status. Currently there's
msnp14 which is in i.p.p, then there's msnp15 in a branch. Both code
bases do not renew the cookie/token (msnp14 doesn't even try, msnp15
tries, but not correctly), so soap actions will eventually fail after
you are logged in for a while. For msnp15, the "a while" is at least 8
hours, so it's less a problem for that branch. It should be pretty easy
to fix the msnp15 side.
A few weeks ago when msn servers went down I got a crash from msnp14, I
have the backtrace here, I should probably figure it out.
Then there's random problems from people who can't log in. Most of which
are because of gnutls. I don't know if it's because of the way we use
it, or real gnutls bugs. Some of them are probably real gnutls bugs, but
at least one person reported that 2.2.0 still fails for him. This is not
msnp14 specific though, but someone more familiar with the issue should
figure out which gnutls version (if any) is stable enough, or drop it
altogether.
Another problem that people seem to encounter is ADL failures. I suspect
this may be because of some buddy list out of sync issues, but I have no
idea at this point. Do people still get 1000 dialog prompting for sync
buddy list these days?
Those are some issues I remember off my head. I tried to look through
the bug list, but trac gave me error about every other request. I know
nothing much had come from me these days and some people may be a little
frustrated, well, it doesn't look like this will change dramatically in
the next few weeks, so those who want msnp14/5 to progress faster would
need to do something about it.
