This is a little project I’ve been working on for about a year now. Protocol support is currently MSNP2 - MSNP18 and YMSG9 - YMSG12, though MSNP21, YMSG13 - 16, and OSCAR are also in development.
Not just doing classic protocols either; I also plan to support open standards/modern protocols as well, such as XMPP and maybe Matrix.
I started work on implementing messaging on WLM 2011/2012 yesterday. It’s not functional yet (I have to make it work alongside circles), but I’m getting there.
Something I should also note is that WLM 2012 seems to behave really weirdly. On Windows 7, it takes several attempts to get it to log in successfully, and after it logs in, the window just disappears and is unable to be accessed. Launching WLM just launches another instance instead of re-opening the existing one (I didn’t patch the clients for polygamy when testing this, to clarify). On modern Windows, it’s slightly different. Instead of the window completely disappearing, it works fine… but only for around 15 seconds, then the connection drops. None of these issues happen on 2011.
Dunno what the cause is (maybe the client is expecting something that I’m not giving it?), but I’m looking into it.
Work on MySpaceIM support started; all that’s currently implemented is a boilerplate network handler, as well as client-side support for our patching component (binary patching is no longer necessary! ).
For Yahoo!, server-side config files for imviornments, audiblemenu, etc were added. These features still aren’t fully implemented, however.
For MSN, proper support for the larger banner ads that appear on WLM 2011/2012’s full view has been added. I’ve also added support for the video feed that will sometimes replace the ad banner on the contact list. Images of both are below.
For AIM, there’s been more work done towards making presence interop work correctly. Though, it’s far from complete.
Looks good, WLM 15+ is its own can of worms, it’s a lot more work than people claim it is, and it’s even harder when you have to make it compatible with AIM, ICQ, Yahoo, and in NINA & Escargot’s case, AOL, Q-Link, and more stuff that cannot be revealed yet, and have it work properly, no spaghetti code, maintainable and expansible code.
Working on AOL, AIM, MSN, Windows Live, Yahoo, ICQ, Q-Link, growing a community, researching, updating the existing server code which sucks (and is essentially what that server is using), etc, etc.
Oh, and also working on our existing jobs too, and providing weekly updates.