mu is clipping right along now, and I’m trying to trim it down so I’m not relying on third party APIs. The reason I’m doing this is so I can avoid problems that I had with Plurk Updater. The only requirements mu will have are the cURL and XML-RPC packages for PHP. It’s my hope that mu will run as efficiently and elegantly as possible.

Here’s my current to-do:

1. Verify login upon entering account details
2. Report if an update doesn’t go through (using HTTP status code 200 as a benchmark)
3. Queue posts if service is down, or send to similar service (twitbin, etc)
4. Limit amount of time each service has to send updates
5. Allow user to publish post at a later date and send update at that time

I’ve had some issues today with duplicate posting, but I think I’ve got that pegged down. Luckily, I didn’t have to make many changes upon WordPress 2.6 being released. I’m going to shoot to have mu finished by month’s end, which feels like a long way off right now. At the very least, I’d like to get items 1 and 2 included in the initial release, and would like to see 5 included ASAP. Keep waiting patiently – as always, comments and suggestions are encouraged.