I may have finally figured out how to handle future posts and call a plugin when the post goes live. I was previously using the ‘publish_post’ action hook, but that doesn’t work for future posts. I figured that there are a lot of bloggers who publish their posts in the future, so this became a critical feature that I wanted mu to have from the beginning.

Another thing I’ve done to mu is to cut out Pownce support. I decided that I don’t want to distribute my API key, which is the only way I could get Pownce to accept messages sent to it. I still haven’t integrated ping.fm into the plugin, and I’m not entirely convinced that I want to. I personally don’t use it, but if there’s enough community support for it, I can look into it at a later date.

The final major update to mu is the inclusion of multiple URL shortening services. Every person has their preference of which service to use, so I’ve included TinyURL, bit.ly, is.gd, snurl, and ri.ms into mu. The user has the choice of which service (if any) to use in the default mu options. If there are others, they can be added pretty easily, but this should be a sufficient set for now.

As for things I’ve yet to accomplish, the last pieces of the puzzle are to verify login credentials when they’re entered and to report errors when posting. If one of the updates goes awry, it will alert the user while still sending out updates to other services.