webapplicationsguide.com

The much loved Twitter has been abuzz with the so-called “Twitpocalypse”, a state at which software clients that uses the company’s API are to suddenly cease working. In what many are seeing as the
apocalypse of Twitter, the 32-bit signed binary number is a set limit at which the API can continue to work and function, reaching of which might result in a total system shutdown. The popularity of the said
micro-blogging site may have this as a major oversight due to it’s release on the 32-bit platform a few years back. Too many users posting too many posts, too quick for the system to handle that is causing
quite a stir with effects similar to the coming of the year 2000 when all hell was expected to break loose (nothing really happened).
Their whole development team has been on stand-by to address any bugs that come out to allow swift resolution of any problems that may occur. The company is acting pro-actively to the issue and everybody is trying to keep ahead of any problems, just hope no lasting effects come out or another nail in their coffin may have been signed that can result in a sway in their popularity. There has been no notable major problems so far as most of the third-party apps have reached the magic number yet the time is still young and somewhere out there may be a lowly app waiting to trigger some oblivious event that can bring about Twitpocalypse, or maybe not!