A wise decision, no doubt, but I think it’s fair to say this migration has been met with mixed feelings.
Yes, Chatter has some benefits over Yammer, the ability to receive updates from sales opps as they move through the system perhaps being among them. However, I for one have been yearning for certain Yammer features, some of which seem pretty fundamental, namely the ability to update Chatter on the move, using those familiar and ubiquitous protocols, Email, IM and SMS.
My so-called ‘smart phone’ is a lowly iPhone 3.1.x (practically prehistoric) with appalling support for Chatter — the official Chatter app won’t run, and Seesmic only allows me to read Chatter, insisting on crashing whenever I try to post an update. A frustrating experience, to say the least.
Fortunately, all was not lost! Chatter, as it turns out, has a pretty complete API, and a RESTful one at that! Familiar territory for us. I quickly set to work, writing a rudimentary API client library (source code over on Github), and building a simple web app on top of this, which is now running happily in the cloud atop Google’s glorious App Engine.
So, here it is… Mega Chunt , providing Chatter users everywhere with the ability to chunt using email, IM and SMS , just be careful how you pronounce it!
 — why ‘Mega Chunt‘ you ask? Good question! ‘Chunting‘ is our term of endearment for the act of creating a status update on the Chatter platform. As tweet is to Twitter, so chunt is to Chatter. Mega, because it’s well, MEGA!
 — so, SMS support is currently a bit of a hack using the awesome IFTTT service. To do this, first enable the SMS channel. Then, create a new IFTTT task that responds to an SMS message by emailing the message to your magic Mega Chunt email address. Simple!