It is being reported that the collapse of Twitter is near. Using a smoke and mirrors method of confirming that a integer identification system used by Twitter will be the culprit, the theory seems to be flawed. Some are now confirming that this may be no more than a publicity stunt and is being compared to Y2K. Remember Y2K?
For those of you who may have forgotten, Y2K was the bug that was going to render all of our computers as nothing more than door stops. Every day before 1-1-00, we were bombarded with tales of world collapse, world war 3, and other dire predictions that merely fizzled away.
According to one article, it states that:
A real Twitpocalypse seems unlikely, as it would mean that a large number of Twitter client developers have carelessly designed their systems with insufficient data limits. If anything, the Twitpocalypse is a lesson in implementing programming best practices for developers who use third party APIs. Standards-based web services like the Twitter API may be robust and reliable, but no API can guarantee that the data structures used in an application have been well designed.
FWIW. The doom and gloomers predict that June 15, 2009 will be what is called “Twitpocalypse” will happen. But don’t hold your breathe.