Matt at WordPress has published a post where he mentions that WordPress now has support for the Twitter API.
identi.ca has had this for a while for all I know, but WordPress has an immensely larger user base. So it’s almost as if the API has been forked and can now be on its way to achieving an open standard recognition. I’m just waiting for the RFC, or something.
This simplifies the problem that I’ve recognised lately with there being too many social networks to actually stay social. I’m talking about the dilemma where one has to pick friends to communicate with, because you can’t stay online on all communities and all microblogging sites. It’s hard enough to keep track on all RSS feeds for ordinary news and relevant blogs. In either case, now a bot which republishes dents (tweets) on all microblogging sites is much simpler to maintain with a somewhat unified API.
So this may also very well be the next step to the end of the world. Imagine the day identi.ca gets a Twitter account, and Twitter gets an identi.ca account. These accounts are then linked together using a bot alongside the simple API implementation. All this bot does – just like many services today – is to repost any dents and tweets on other similar sites. As soon as at least two of these bots are running on interlinked sites, it is the end of the world as we know it.
Anyway, I actually thought the concept of forking an API was much more interesting, so I’ll just stop my retarded thoughts of an unlikely scenario. Later I’ll probably discuss what an API is and if – for example – you can copyright it, or somehow (except through mad software patents) claim immaterial ownership of one.

microblogging is really useful when you want to broadcast short updates. i am still leaning towards traditional blogging.`’`