The 2009 Twitpocalypse concerned overflow of 31-bit precision. Twitter has not yet hit 53-bits for raw number of Tweets, in fact, they passed 32-bits in 2014 an

The 2009 Twitpocalypse concerned overflow of 31-bit precision. Twitter has not yet hit 53-bits for raw number of Tweets, in fact, they passed 32-bits in 2014 and might not have reached 33-bits, yet. Moving to strings for Javascript was really just safety planning for the future since: > Given the current allocation rate, they'll probably never overflow Javascript's precision nor get anywhere near the 64-bit integer space. https://twittercommunity.com/t/discussion-for-moving-to-64-bit-twitter-user-ids/9890/2 https://twittercommunity.com/t/discussion-for-moving-to-64-b...