There's also http://trac.adium.im/ticket/14965 which is quite a problem and therefore getting constant complaints over Twitter and many duplicate tickets. That, and 3 other tickets would be closed with an updated Libpurple, leaving a few (mainly isolated) tickets and Facebook left for the 1.4.2 milestone.
So yeah, I couldn't agree more with getting a beta out assuming Facebook is going to take a while, could always just push it to 1.4.3 until it gets done. Doesn't seem very logical blocking a release of some annoying issues if no one is actively working on Facebook at the moment. Not much harm in adding FBXMPP during the beta period, as well. On 4 Mar 2011, at 15:11, Shawn Khan wrote: > Hello all, > > I have been looking at the tickets and this one: > http://trac.adium.im/ticket/13654 has been commented on a lot, which is an > MSN Bug. From what I have heard Libpurple has been updated in 1.4.2hg which > should add MSNp16 including "multiple points of presence" support. If we are > able to get a beta out this bug would be fixed. > > I am also sure there are other reasons for Adium to release a new beta, but > that is the biggest one I see as of right now. > > If I am correct people are waiting for the FBXMPP to be finished before we > release a new beta. I just don't see that happening anytime soon as this is > massive and there are not a lot of people working on this. Unless we set a > deadline for the FBXMPP and Beta, we are going to wait forever for this. In > the end yes we need to get FBXMPP done as best as possible but alway having > fresh eyes on this is good. > > Thanks, > Shawn
