140Char

It seems as if there are a million Twitter applications, widgets, and ways to publicise your membership and latest Tweets, but things are a bit twickier when it comes to Plurk.

So far, there has been an unofficial API, and third party Plurk tools are thin on the ground. But even more annoyingly, I can’t use the official Plurk widget.

There’s a simple reason. They offer it for users to embed into a Facebook, Myspace, or blog page. But they’ve fixed the width, so trying to display it on this blog, for instance, means the sidebar will be blown apart. And the width is set at 300 pixels wide - way too much for most pages on Facebook or Myspace.

So for the moment, I’ll not be sharing my Plurking as much as my Tweeting.

You can still find me on Twitter. And on Plurk.

Blimey, things are definitely starting to happen outside of Plurk. First came the first Plurk Facebook app, Plurksync, which updates your status with your most recent Plurk. Unfortunately it’s likely to suffer the same problem as status updates via Twitter, when you end up seeing the same message across every service an individual uses.

Although my favourite incident with linking microblogging and Facebook saw friend and colleague David Cushman in a surreal, endless loop of updates between Twitter and Facebook.

And now comes the unofficial, reverse-engineered, not supported by the Plurk team API, RLPLurkAPI provided by Ryan Lim.

Oh, and from the official Plurk blog comes the news that they’ve tweaked the Karma points.