i'm thinking the lack of age restrictions, influx of porn spammers and the obvious cases of cyberstalking coming out now.. will be the death of twitter.. Maybe it will just get washed away with gtalk in google wave?
Benjamin Dobson
· 6 months ago
Lack of age restrictions? Hmmm. I see how something like "if you are under the age of 13 you must have permission from a parent or guardian" is a good idea…but I haven't seen any five-year-olds on twitter at all.
Mike W
· 6 months ago
"Just like the Y2K bug, we think it’s most likely a hoopla about nothing."
So the point of the article is.....
Ben Parr
· 6 months ago
To keep you informed of something that is confusing a lot of people.
Justyn Howard
· 6 months ago
This issue is known to developers who have had plenty of time to re-work our code. Should be a non-issue just like Y2K, unless the developers of 3rd party apps have been sleeping.
@EllaJo08
· 6 months ago
I'd rather stockpile phone txts and daytime minutes and kbs.
James
· 6 months ago
http://www.twibeo.com is a Twitter-like site that lets you say what you're doing by sharing text, photos and videos right from the page! Join us @ http://www.twibeo.com
Aaron Landry
· 6 months ago
And why would Mashable post about something that is clearly a total hoax? Oh yeah, this will undoubtably be a trending topic. Traffic$$$$$$
Ben King
· 6 months ago
It's not a hoax, it's an actual limitation of database integers. The "twitpocalypse" is referring to the moment when the unique ID assigned to tweets surpasses the maximum number the database can hold, and thus breaking.
However, it's fairly easy to fix the problem, third-party developers just need to upgrade the size of their integer fields. Twitter.com itself has already done this.
Vera
· 6 months ago
I think twitter is about to get into the chaos :D.
Yeah, it'll be fine because They would tell us if there was a problem... Twitter are really good at communicating with their users...
Oh crap! Run for the hills!
AlexsSystem
· 6 months ago
Internet changes way too fast. New websites always come up and gets blown up and die once their time has come. Twitters time will come to and has nothing to do with a virus. Ever since the birth of internet social networking sites have been poping up and dying. Latest example to experience will be myspace.
Michael Bauser
· 6 months ago
If Twitter dies at 5am Saturday morning, nobody here will notice -- we'll all be busy hammering Facebook's servers while trying to claim our favored userids.
Miguel
· 6 months ago
This is clearly a hoax, it's true that an integer in MySQL can hold 2,147,483,647 BUT, MySQL also provides BIGINT's which can hold 9,223,372,036,854,775,807 unique ID's, how do I know this? I work with MySQL databases.
If you don't believe me read this MySQL post about numeric types.
In fact, an UNSIGNED integer can hold 4,294,967,295 , so twitter doesn't even have to switch to bigints, if they haven't already, which by the way is easy to do.
Ben King
· 6 months ago
Yes, that's exactly the point of this "twitpocalypse". Twitter used to use smaller ints, to fix this upcoming problem I believe they changed to BIGINT. The issue is whether or not third party developers (who cache tweets on their own servers) have updated their field sizes.
Miguel
· 6 months ago
Yeah, well, I don't know why any of these developers would use signed integers for numbers that will never need to be negative, if they did, they should be able to easily switch to unsigned or bigint like you said in your previous comment.
Nikolay Kolev
· 6 months ago
Yes, it's easy to change the type of a DB field... but the problem is that doing this on a huge, heavily used live DB can take forever and it's hard to do it without downtime, if done in the last minute. So, hopefully, they've done this migration already!
jpostman
· 6 months ago
You're pretty sure Twitter would have mentioned a pending problem? The masters of transparency and responsiveness?
Josh Fraser
· 6 months ago
They did. They put a note up on the developer forum a few weeks ago as a friendly "heads up".
Carrie
· 6 months ago
I can't stop laughing!
techsupport
· 6 months ago
What basis does this website predict a Twitpocalypse anyway?
g1smd
· 5 months ago
The exact ID number of the failure point is known.
The currently used ID number can be found easily enough at any time.
Work out how many tweets per second are being sent... and very simple maths can extrapolate a rough date and time for the failure.
It's not rocket science.
oriste
· 6 months ago
Sigh.
"When Twitter goes down..." - Twitter is not going to go down, Twitter is not even involved in this. Stop the innuendo. At worst some obscure 3rd party Twitter client might misbehave. So what? go back to the web version or pick another client. Problem solved.
Does Mashable really need this sensationalism to increase readership?
Ben Parr
· 6 months ago
Read the rest of the post. I break the sensationalism down like a sledgehammer to a glass sculpture. :)
james
· 5 months ago
'I break the sensationalism down like a sledgehammer to a glass sculpture.'
The funny part is, I actually think he's being serious!
carriesmith1800
· 6 months ago
Is it wrong for a man to have a sugar baby or a woman to have sugar daddy??
It is an absolutely extramarital relationship, but more and more services came out on Internet focusing on this kind of relationship.
such as ^-^ http://SugarDaddyChat.com/ ^-^ it's the biggest sugar dating site for beautiful woman and rich man!
darkened jade
· 6 months ago
The thing is, this is like making a movie about people taking over the internet, nobody cares. The world, miraculously enough, goes on. Even those, like me, who have fast become addicted to twitter and hit the on button to my computer as soon as I enter the house, realise that even if it goes down, a few days later everything is back to normal and all we're left with is another bad t-shirt.
rohmadbasuki
· 6 months ago
wow...nicend verry helpfull
Gerald Weber
· 6 months ago
On mai gawd! the Twitpocalype is coming! I'm stocking up on firearms and canned food as we speak! ;-)
rsy611
· 5 months ago
Yeah, everyone keeps comparing this to Y2K. And all I remember about Y2K is that.... absolutely nothing happened. Maybe I should start some ridiculous rumor on Twitter and see how many people I can get to believe it....
g1smd
· 5 months ago
Err, nothing happened? Not unless you include several nuclear power stations that had to go on manual override, various automated systems on the fritz until they were reset manually, and numerous places where you could see dates like 1/1/100 and 1/1/19100 the following day.
There was real potential for the whole financial system, and all utilities (which mostly run on automated systems) to break when the year flagged as 00 or 100 or 19100 instead of 2000. Millions of computer systems had to be updated and altered to avoid those problems.
The difficulty was in getting people to realise that these deficiences had been built into their systems. Many did not believe it - until they tested it.
There are more such incidents to follow in the next few years and decades as other systems run over the end of their numbering scheme... programmers have seemingly learned *nothing* about future-proofing their systems in the intervening time.
g1smd
· 5 months ago
*** If there was a serious bug that was going to affect your Tweetie, Seesmic Desktop, or TweetDeck, we’re pretty sure that Twitter would have made some mention by now. Even if there was an issue, Twitter could probably fix it on their end. ***
Wow! Just show how much you don't understand the technology why don't you?
The problem is real, and the problem cannot be fixed at Twitter's end. The problem is that the applications have not reserved a big enough space to store the tweet number. They haven't allowed for 'big enough' numbers. When the numbers are 'too big for the storage space' they are 'corrupted', just like when you only have 6 digits available, the number after 999999 is 000000 because there isn't room for the seventh digit.
In Twitter's case they are using much bigger numbers (32-bit as it happens). They have to, as there are several hundred tweets per second, 24 hours per day, and the service has been running for years.
They might be better off changing to a different numbering format, one that incorporates at least a part of the date as well (and with at least a 4-digit year), to avoid this happening again.
Just wow! on the uninformed nature of the article.
All Comments
So the point of the article is.....
However, it's fairly easy to fix the problem, third-party developers just need to upgrade the size of their integer fields. Twitter.com itself has already done this.
Greetings from http://www.verasoul.com
Oh crap! Run for the hills!
If you don't believe me read this MySQL post about numeric types.
http://dev.mysql.com/doc/refman/5.0/en/numeric-...
In fact, an UNSIGNED integer can hold 4,294,967,295 , so twitter doesn't even have to switch to bigints, if they haven't already, which by the way is easy to do.
The currently used ID number can be found easily enough at any time.
Work out how many tweets per second are being sent... and very simple maths can extrapolate a rough date and time for the failure.
It's not rocket science.
"When Twitter goes down..." - Twitter is not going to go down, Twitter is not even involved in this. Stop the innuendo. At worst some obscure 3rd party Twitter client might misbehave. So what? go back to the web version or pick another client. Problem solved.
Does Mashable really need this sensationalism to increase readership?
The funny part is, I actually think he's being serious!
It is an absolutely extramarital relationship, but more and more services came out on Internet focusing on this kind of relationship.
such as ^-^ http://SugarDaddyChat.com/ ^-^
it's the biggest sugar dating site for beautiful woman and rich man!
There was real potential for the whole financial system, and all utilities (which mostly run on automated systems) to break when the year flagged as 00 or 100 or 19100 instead of 2000. Millions of computer systems had to be updated and altered to avoid those problems.
The difficulty was in getting people to realise that these deficiences had been built into their systems. Many did not believe it - until they tested it.
There are more such incidents to follow in the next few years and decades as other systems run over the end of their numbering scheme... programmers have seemingly learned *nothing* about future-proofing their systems in the intervening time.
Wow! Just show how much you don't understand the technology why don't you?
The problem is real, and the problem cannot be fixed at Twitter's end. The problem is that the applications have not reserved a big enough space to store the tweet number. They haven't allowed for 'big enough' numbers. When the numbers are 'too big for the storage space' they are 'corrupted', just like when you only have 6 digits available, the number after 999999 is 000000 because there isn't room for the seventh digit.
In Twitter's case they are using much bigger numbers (32-bit as it happens). They have to, as there are several hundred tweets per second, 24 hours per day, and the service has been running for years.
They might be better off changing to a different numbering format, one that incorporates at least a part of the date as well (and with at least a 4-digit year), to avoid this happening again.
Just wow! on the uninformed nature of the article.