cocoaforge

It was moved to "some version in the future", which could be 2.3.1 or could be a version after. Releasing an incomplete MSN implementation which sometimes refused to connect and crashed intermittently would do nobody any favors.

hmm http://felipec.wordpress.com/2007/11/29 ... or-pidgin/

Will we get this Hack in adium version of Libpurple just for the time being.

MSNP14 has been a long wait with no ETA to date.

Hi everybody,
LibPurple has already builtin the support for MSNP14 but it is not activated by default when compiling. On Windows I have been using an unofficially compiled MTN build since September which has the MSNP14 activated and I can see other people's MSN status messages and I can also have my own personal status message.
I don't know why Pidgin team hasn't activated MSNP14 by default, maybe they are working in fixing some bugs. I can tell from personal experience that the MTN Pidgin with MSNP14 never crashed on Windows.
So, even if it may have some bugs hidden somewhere, the MSNP14 branch IS present in LibPurple and IS stable enough to work for "everyday" use.
I think that there is a flag (maybe a simple #define) to tell the compiler which protocol to use in the LibPurple build (MSNP9 or MSNP14).
See you,
Pietro

Until Pidgin considers it stable enough to ship with, we're not going to be using the MSN P14 code.

zac wrote:Until Pidgin considers it stable enough to ship with, we're not going to be using the MSN P14 code.

May I ask why you are waiting for them? Has that always been the case with upcoming features?

Why not take a chance with this? Would be hella nice. Everyone but the Adium team and seemingly the Pidgin team seems to think it's stable, no?

Just curious.

Visualize wrote:

zac wrote:Until Pidgin considers it stable enough to ship with, we're not going to be using the MSN P14 code.

May I ask why you are waiting for them? Has that always been the case with upcoming features?

Because it would be smart/prudent. If the vendor who provides us our backend library is saying to not use this software because it's buggy to all hell and doesn't work half the time, we would be fools to use it.

Visualize wrote: Why not take a chance with this?

Because it's not smart. See the commend from Evan above.

Visualize wrote: Would be hella nice.

You are wrong sir. Not connecting to MSN randomly is better than connecting but missing a few features?

Visualize wrote: Everyone but the Adium team and seemingly the Pidgin team seems to think it's stable, no?

Who else is everyone? Both projects are the largest consumers of libpurple. As such, if the people who basically have worked on libpurple for 15 years say "no, let's wait and make it work instead of pushing out something half baked" you listen.

We realize you guys want some features, but you need to back off and let the people who make the code decide when it's ready.

I will surely back off. I have to stop thinking out loud and making assumptions left and right.

I apologize.

What I meant with "everyone" is basically that one guy saying that it never crashed once on Windows - which is a big thing.

seemingly the Pidgin team seems to think it's stable, no?

No. There's a reason Pidgin is not shipping with MSNP14 enabled.

Visualize wrote:I will surely back off. I have to stop thinking out loud and making assumptions left and right.

I apologize.

What I meant with "everyone" is basically that one guy saying that it never crashed once on Windows - which is a big thing.

a couple weeks ago, it was crashy, unreliable in terms of connectivity, and sported memory leaks. It is definitely not ready to be used by anyone with high (that is, reasonable, for adium) expectations.

I think a big part of the frustration here is because of the impression that other, comparable open source projects (KMess, AMSN) have very good MSN support, while libpurple has lagged badly behind in this area for quite some time. Until quite recently there wasn't really any forward progress on it at all. Now, what forward progress there has been is out of reach.

For a large chunk of the IM population MSN is their sole IM protocol and the standard that all the people they want to talk to use. I'm one of those people and I can certainly understand the frustration being felt here.

Sadly, about the only solution I can see here is to drop libpurple for MSN support and move to another library for it. However, I'm quite certain that would bring its own set of pain during the transition and is probably a route the developers don't want to go down.

You guys are way to impatient....Just give the pidgim team some time in order to get everything working smoothly!

SeaWolf wrote: Sadly, about the only solution I can see here is to drop libpurple for MSN support and move to another library for it.

I don't know of any libraries in compatible languages that have thorough MSN support; regardless of that though, I suspect the effort involved in switching would be much larger than the effort involved in fixing the MSNP14 prpl for libpurple.

Catfish_Man wrote:I don't know of any libraries in compatible languages that have thorough MSN support; regardless of that though, I suspect the effort involved in switching would be much larger than the effort involved in fixing the MSNP14 prpl for libpurple.

I thought as much, it just feels as though getting the support in libpurple is something that is just never going to happen. After all, it has been a long, long time coming.

i'm sure you could wait a few more months

zerock wrote:i'm sure you could wait a few more months

Actually, I gave up waiting well over a year ago and started using AMSN instead. I'd really much rather be using Adium, but I've come to accept that it will probably be a long, long time before it gets to the level that AMSN is at.

Well the only thing that seems to be blocking MSNP14 is that receiving offline message crashes.

Hopefully this bug get fixed ASAP.

And does anyone know if they have implemented sending custom emoticons yet?

SeaWolf wrote:

zerock wrote:i'm sure you could wait a few more months

Actually, I gave up waiting well over a year ago and started using AMSN instead. I'd really much rather be using Adium, but I've come to accept that it will probably be a long, long time before it gets to the level that AMSN is at.

amsn is purely msn, is it not? Kinda makes sense that their msn support would be superior...

At this point, I think this thread has reached the end of it being useful for the time being. Until msp14 is officially supported in a released version of Adium (beta or not) it'd probably be best to wait on this folks.