Today I decided that I wanted to increase my general laziness and automate setting my Twitter and iChat messages at the same time. Seems reasonable and as I’m never the first to have an idea, I’m sure someone has already built something for this. A quick Google search yielded a great script for Quicksilver here and the improved version with iChat support here. Wonderful.

So I think, ok this works like a charm, now lets extend this and add Facebook support! Oh wait, already been done here. Well, I remember hearing about a new Facebook API for supporting status updates that was released after that last script version which relied on a mobile hack. Ah yes this looks like it, I’ll build something using the official Facebook API and all will be good!

But it turns out that’s not going to work because first I find this TechCrunch article which points out a problem with my approach and the Facebook terms put the final nail in the coffin. The same policy that applied to this method would apply to Soeren’s method and any anything that I create because they all violate those ridiculous terms of use.

What kind of crap is that? I can build services that interact with Facebook, provided I only do it on Facebook’s site.

Oh yea that’s almost a win.