God help you if an iPhone Twitter app needs a last minute update!
Chris Thomson
· 2 months ago
This was announced back at the end of July. That's plenty of time for iPhone app developers to update their Twitter applications.
barkerja
· 2 months ago
Of course, but is that plenty of time for Apple to approve the applications! lol. Sorry, just hating since I dropped the iPhone like a bad habit.
martani_net
· 2 months ago
wooo, I wonder who will post the tweet that will cause the twitpocalyse? that would be a legend :)
Kera Torrence
· 2 months ago
Wait how do I change it? Or how do I check what my ID thingy is??? O.o
martani_net
· 2 months ago
change what? you don't need to change anything, only if you have a twitter client that you developed YOURSELF then you have to be sure the IDs are handled with large numbers than 64 bit integers, maybe you can use strings to handle them or whatever you find suitable for this.
Kera Torrence
· 2 months ago
OH! Ok. Thanks. Haha, I'm not good with computer stuff. Thank you! :D
Name
· 2 months ago
Dude, Ben. 64 bits is not 4,294,967,296.
If 32 bits == 2,147,483,647, doubling that number only adds one additional bit of significance.
HZ
· 2 months ago
The only true Twitpocalypse is twitter itself and all the idiocy around it, including it's engineers.
It has nothing to do with 32bit vs 64bit integers - those numbers listed as limits are signed vs unsigned 32 bit integers. 64bit unsigned upper limit is 9,223,372,036,854,775,807.
Perhaps knowing how to use an application on the internet aside from twitter would be valuable when writing an article.
Chris Thomson
· 2 months ago
Hey Ben, this upcoming 'Twitpocalypse' is actually caused by the 32-bit unsigned integer limit, not the 64-bit integer limit. The previous Twitpocalypse was for 32-bit signed integers.
The Wandering Foodie
· 2 months ago
Why not just make it 4,000,000,000,000 and save the developers the hassle . . . or would that add more hassle . . . I probably wouldn't be asking this question if I was a developer.
jeux video
· 2 months ago
I realize they don’t have direct control over 3rd party apps, but back when the Twitter devs were aware of the first oncoming twitpocalypse, why didn’t they just make the first post-twitpocalypse tweetID something larger than you could fit in a 32-bit unsigned int?? 2^32+1. Problem solved, now where’s *my* millions in venture capital!?!?
This would have forced 3rd parties to adopt 64-bit tweetid’s months ago. But no, here we are again. Sometimes I think Twitter employees really dig failure.
Sally
· 2 months ago
Fie on your integers and bits. It's just that some apps will be taken up in the Rapture.
Sally
· 2 months ago
Fie on your integers and bits. It's just that some apps will be taken up in the Rapture.
lucasarruda
· 2 months ago
News #FAIL. How not to write something that you don`t have enough knowledge.
Orion
· 2 months ago
Well, looks like Twittelator Pro didn't survive intact. No longer refreshes properly but instead takes you back to the time of failure forcing you to scroll back to the present to see your lastest updates
All Comments
Ok. Thanks. Haha, I'm not good with computer stuff. Thank you! :D
If 32 bits == 2,147,483,647, doubling that number only adds one additional bit of significance.
It has nothing to do with 32bit vs 64bit integers - those numbers listed as limits are signed vs unsigned 32 bit integers. 64bit unsigned upper limit is 9,223,372,036,854,775,807.
Perhaps knowing how to use an application on the internet aside from twitter would be valuable when writing an article.
This would have forced 3rd parties to adopt 64-bit tweetid’s months ago. But no, here we are again. Sometimes I think Twitter employees really dig failure.
How not to write something that you don`t have enough knowledge.