API

API is geek-speak for "Application Programming Interface." In day-to-day life, APIs are something the average person doesn't stop to ponder, sort of like how you don't really stop to think that your microwave oven has a microprocessor. You just use them. The term API takes on a new significance in the Social Media world, though, because of Twitter.
That's because Twitter offers very poor service to its users and a significant portion of those folks access the world's most popular micro-blogging platform via its API. The Twitter API is the means by which anyone using "client" software such as Seesmic Desktop, Tweetdeck, or HootSuite sends and receives tweets. Twitter limits the number of times their users can access the API in an hour, and these limitations have been the source of much frustration and speculation. High-volume Twitter users found the services low API limits to be a serious constraint. The service finally increased the hourly limit to 350, and that seemed to calm folks down a bit. Last month, however, Twitter chose to do work on the computer server infrastructure that implements the API. They cut the number of accesses from 350/hour to 175/hour, further tarnishing their reputation for poor performance and service.
Why Twitter decided to do major maintenance to their API infrastructure in the middle of the FIFA World Cup, the most popular sporting event in the world, is beyond me. Combine that with the on-going tragedy that is the BP oilspill in the Gulf of Mexico and the oh-so-critical "LeBron watch," and the lower limit was a recipe for disaster.
As of this morning, however, the API limit appears to be back at 350.
But don't worry, no doubt this afternoon's Germany-Spain match in the La Copa Mundial semi-finals will break it.