Sometime around May 11, the Facebook Twitter app stopped working. Or, at least, it stopped updating the Facebook status field. Instead all it does now is post your tweets to your wall. To most users, it appeared the Twitter app had simply stopped working since it was no longer performing its main function. This generated a lot of discussion in the Facebook Twitter App forum as more and more users reported the breakage:

By May 13 there was still no official response from Twitter on what was going on, so user tim.neumark filed a bug in the Twitter API database.

The next day Twitter API developer tokofu claimed Facebook had asked Twitter to make the change:

“We made a change to use a newer Facebook API to add content to the stream that no longer updates status. We think it provides a better experience based on what Facebook is asking developers to do.”

“You can always manage the settings Twitter has with Facebook through your Edit Applications tab.”

What’s meant by that last sentence is unclear as there is nothing in the indicated dialog that changes the behavior of the app in any way with regard to updating status.

Tokofu’s post was the nearest thing so far to an official statement on the breakage. This was followed by several days of people posting comments on the bug report noting that “better experience” is not how they’d describe a bug that breaks the app’s ability to perform its primary function. The flurry of comments prompted Twitter to close the bug report as “invalid” and users were asked to stop commenting.

Shortly afterwards on May 18, a new issue appeared on Twitter’s help pages in the “Known Issues” category: Twitter updates my Facebook wall but not my status

There was new spin on the story now. Instead of claiming it was an intentional change requested by Facebook to give the users a “better experience”, they seem to claim it was the unexpected result of moving to a new Facebook API (didn’t it occur to anyone to test it?!) They further claim Twitter is now “working with Facebook to see if there’s a way to push updates with the new API in a manner that updates both your wall and your status”. The issue has accumulated over 60 comments from users asking for the problem to be fixed, or for Twitter to revert to the older, working Twitter App until a fix is found for the new one.

After three weeks, neither Facebook nor Twitter appear to have made any progress on fixing the problem and most users of the Twitter app still have an empty status field. Oddly, third party Twitter apps such as Smart Twitter continue to work normally, so many users of the official Twitter app have switched.

Posts on the Facebook Twitter app discussion forum suggest that the move was an intentional effort by Facebook to cripple the Twitter app because Facebook viewed it as cutting down on the number of potential page hits for Facebook. By blocking remote status updates, Facebook could force users to log in and update their status manually, garnering more advertising views. It’s unclear (to me at least) whether there’s anything to this rumor or whether it’s pure speculation on the part of frustrated Twitter users. If it’s accurate, then I would expect Facebook to deprecate the old API that allows apps to update user status, disabling all the third party Twitter-to-Facebook apps as well. That hasn’t happened yet.

Given Facebook’s history of bad decisions and gaffes lately, I’m ready to believe anything.

My blog was neglected for the last half of 2009. I haven’t been totally offline. I’ve continued posting regularly to my photo blog and twitter (which feeds my Facebook, Myspace, and LinkedIn accounts) as well as making daily posts to robots.net. But my personal website has fallen into disrepair. It’s time to reboot things. First off, you may notice I’ve moved my blog to its own domain, steevithak.com, from its old home on my business website.

Over the last few years, I’ve consolidated my online presence from lots of different user names to just one: steevithak. It’s hard to spell, nobody knows how to pronounce it, but it’s uniquely me and gives me a user name that’s always available. Don’t worry, only machines refer to me as steevithak. If you’re human, keep on calling me Steve in person.

Back to my blog; I started blogging 1999 before it was commonly called blogging. I wrote my own set of PERL scripts to manage the process. So in rebooting my blog, I was faced with a 10 year blog archive in a one-of-a-kind format. The earliest blogs lacked titles and none of them were tagged with keywords, so I decided to manually convert them one at a time, adding the missing elements. Over a period of time, I reconstructed my entire blog archive using Pivot.

As the end of 2009 neared, Pivot 2.x was released, so I converted everything to that format. In December of 2009, I made a last minute decision to switch again to Word Press, which offered several features Pivot lacked. Pivot 2.x also proved to be mind-bogglingly slow, perhaps because it couldn’t deal with a 10 year archive stored in a flat file database! The conversion from Pivot to Word Press initially looked difficult but I found a script that was able to move the entries and titles. I modified it to also preserve the keywords I’d spent so much time adding.

So the new website integrates my blog, my photostream, and my twitter feed in one location. The blog will continue to be syndicated to my robots.net and Advogato.org profiles, manually for the moment but I think a Word Press plugin supporting the mod_virgule XML-RPC protocol may be forthcoming.

Now all I have to do is make life in 2010 interesting enough to blog about! I’m not worried. Something tells me we’re in for a good year.

I’ve never managed to blog much more than a couple of times a month, so if anyone reading this actually cares what I’m up to, you might want to follow me on twitter or check my canonical home page where you can see the relatively frequent photo stream updates from my crappy mobile phone camera. By the way, if you’re looking for other robot builders to follow on twitter, check out Wired’s list of 52 Robot Geeks on Twitter.

Speaking of twitter, I really need to find a good way to get that integrated into mod_virgule. And speaking of mod_virgule, I once again completely failed to find time to work on it. But I’ve exchanged some email with another programmer who might be brave enough to start doing some hacking on the code, so maybe that will get me motivated in July!

I created a robots.net twitter feed and robots.net facebook page for robots.net this month. So far the facebook page is ahead with over 160 fans while the twitter feed only has about 38 followers so far. To be fair the facebook page went online a couple of weeks earlier so we’ll see if it hangs on to the lead over time.

I’m still struggling to find time to devote to mod_virgule but squeezed in a few more hours of C coding on the new HTML parser. It’s now running on a test server with a subset of Advogato’s database. So far, so good. Blog aggregation and parsing seems to be working, as do local blog posting, article posting, and article comments. The magnitude of the changes makes this update a bit of scarier than usual for robots.net and Advogato. If nothing breaks in the next week or so of testing, though, I’ll cross my fingers and make it live.

I continue to drag my Canon 40D around with me everywhere and since my last blog post, I’ve shot photos of the Funky Finds Spring Fling craft show in Ft. Worth, the Aveda Walk for Water event in Dallas, the aforementioned VEX Robotics World Championship, the Cottonwood Arts Festival in Richardson, the 2009 DFW Dragon Boat Festival in Las Colinas, oh, and a few pics of my friends at Vivanti Group in Deep Ellum. In the retro-photo department, I posted some BW 127 photos shot with a Kodak Brownie Reflex Synchro. Yesterday, a package arrived containing that rarest of things, color 127 film, from a small manufacturer in Canada. I’ll probably run a roll through the Bencini Comet S sometime soon.

ta0kira followed up with some further comments on the topic including the question of whether other sites interleave syndicated posts with content that originates locally. There are a few such as Facebook (see below) but Advogato has always done things that were a little, ummm, experimental in nature. He has a good point that it would be nice to be able to select whether or not to see the syndicated posts. It has also be suggested in the past that an ideal solution is to give each user the ability to create their own personalize recentlog view.

One aspect to consider is that there are several ways of syndicating your blog to Advogato that may go unnoticed. Posts syndicated by RSS or ATOM are explicitly marked as such in the recentlog but syndication by XML-RPC or the older HTTP POST method go unnoted. My blog posts, for example, originate on my personal blog and are then syndicated to Advogato and robots.net using the HTTP POST method; and to Facebook by RSS. Facebook’s blog syndication services are horrendously bad incidently, turning each blog post into a nondescript thing called a “note” with no clear indication of what it is or why it exists.

Another recentlog issue that’s been mentioned several times lately is that some people are piping their twitter feeds into the recentlog via RSS. I agree this can be annoying but rather than block twitter feeds, I’d like to see them rerouted into a user status field, much like Facebook or Myspace. For example, I use twitter and my tweets update my user status field on Facebook. Maybe it’s time to add a user status field to mod_virgule sites like Advogato?