The social media evidently have it in for Rob O’Hara:
When I post new posts on robohara.com, notifications get posted to Facebook (via the FacePress plugin) and Twitter (via WordTwit). When I need to update both Facebook and Twitter at the same time, I’ve been using TweetDeck.
Over the past week FacePress, WordTwit, and TweetDeck have all stopped working. Cheese and rice, man.
It started with TweetDeck, which forced an upgrade and then informed users that the new version no longer supports Facebook. Essentially that means that TweetDeck now only supports Twitter. That’s stupid. If it only supports Twitter, then why would I use TweetDeck? The entire point of TweetDeck was that I could funnel multiple social streams into one single interface. If TweetDeck only supports Twitter, then I’m not sure what purpose it serves. From now on I’ll just go back to using Twitter’s default interface. TweetDeck has been deleted.
The reason TweetDeck did this, of course, is because Twitter bought it and didn’t want to expend any development time supporting someone else’s API, especially Facebook’s. (Early versions of TweetDeck even supported MySpace, fercryingoutloud.)
While troubleshooting TweetDeck, I noticed that my last couple of blog posts didn’t get posted on either Facebook or Twitter. Apparently, over the past week both sites updated their APIs, causing older plugins (like the ones I was running) to stop working. Facebook said, “update your plugin”. I checked the FacePress website and was informed that the plugin hadn’t been updated in three years. Greeeeeeeat. After an hour on Google I found that Jetpack for Facebook offers the same functionality — I just didn’t know it because I’ve been running an older version of Jetpack. After upgrading it, I was able to link robohara.com with Facebook once again.
Now this is out of my wheelhouse, since I’ve worked diligently to keep this site and Facebook as far apart as possible, but allow me to put in a few kind words for Jetpack, which I use on all my sites except this one: it does a whole lot without making you jump through (too many) hoops.
I had to do the same thing with Twitter. WordTwit had to be upgraded and new security keys had to be generated. After going all of that, I realized that Jetpack handles Twitter connections as well as Facebook connections, so after doing all the work to get WordTwit to work again I uninstalled it and added Twitter to Jetpack as well. Sheesh.
I used WordTwit for a while, but ultimately switched to WP to Twitter, mostly because it was better about serving up error messages. And in fact, most of the errors I encounter are due to slipping time stamps — server time here never exactly matches Twitter’s server time — or a failure to rouse the gnomes at bit.ly, rather than anything related to the plugin itself.