Search icon

Uncategorized

10th Apr 2012

That awkward moment when Twitter realises the Titanic disaster actually happened…

There were a lot of minds blown on Twitter over the past 2 days, when people realised that the Titanic disaster actually happened in real life...yes, seriously...

JOE

Oh Twitter. You amuse us so. Although sometimes, if we’re being a little honest, we worry about your level of intelligence. In fact, this latest incident has just proved that you’re a bit dumb. Actually you’re dumber than a bucket of hair…

Case in point? Can we all just take a minute to reflect on that awkward moment when Twitter realised that the sinking of the Titanic was an actual historical event and not just a film?

Hysteria was widespread over the Twitter during the past two days when various people around the globe had an epiphany. What was that epiphany you ask? Well they had the bright idea to do a bit of research and surely enough they found out that the Titanic disaster happened. And it was real. And then they took to Twitter to share this knowledge with us all. The only problem? Eh…they’re about 100 years late…

Exhibit A:

Honestly? It’s actually a bit mind-boggling that these people somehow never heard about one of the most infamous disasters in history. A more disturbing thought, however, is the fact that the majority of these people probably went to the cinema to see Titanic without realising that it was a true story (or knowing what happened at the end…)

We can just imagine them sitting in the dark and screaming “Hey, watch out for that iceberg!!!” at the screen.

Anyway, despite the fact that there’s been constant media coverage about the upcoming anniversary on April 12, this just goes to show that there are a lot of people out there who need to learn what Google is and how they can use it to find out about important world events as they happen, not a century afterwards.

So, just to clarify in case you’re a little bit confused: the Titanic happened and, more importantly, Leonardo di Caprio and Kate Winslet had nothing to do with it.

Topics: