I recently created a plugin to send an update to your Plurk account (Plurk Updater). It was at that point that I decided that I really needed a plugin that allowed me to specify on a post-by-post basis if I actually wanted to send the update to either Plurk or Twitter. Thus, mu was born.
mu stands for “Microblog Updater”. It is a conglomeration of my Plurk Updater and Twitter Updater. I thought, why stop there? Currently, mu works with Twitter, Plurk and FriendFeed, and partially with Jaiku (they’re having API issues). I have aspirations to extend mu to work with Identi.ca and possibly ping.fm. This will make mu a powerful, all in one solution for updating all your microblogs without any extra intervention on your part.
One great thing about mu is that it will allow the user to build a list of default services mu will send updates to. If, while they’re writing the post, a user decides that the default list doesn’t suit the post, they’ll simply have to scroll down to the services box and check the services they want and don’t want. mu will be a true plugin, and there won’t be any code modification or hacking that needs to be done by the end user.
The other cool thing mu takes care of is update formatting. Each service has their own recommended format updates should appear in, and mu handles them all. Twitter’s format is different from Plurk’s, which is similar to FriendFeeds, but is different from Jaiku’s. mu handles the headache so you don’t have to. It just appears without you worrying about it.
If you have suggestions for additional services you’d like to see in mu, leave them in the comments.
Here’s a few screenshots of what mu looks like:
Options Page
Account details page:
Services Options (on edit page):







1 comment so far ↓
July 10th, 2008 at 11:03 am
Very nice, Mark. You’re a revolutionary.