Spoiler Alert: How Our Favorite Sites Are Ruining Our Favorite Shows

Wednesday, April 16, 2014 - 11:00 AM

The Hollywood Reporter's homepage after a big night for 'Game of Thrones' The Hollywood Reporter's homepage after a big night for Game of Thrones (The Hollywood Reporter)

SPOILER ALERT: This article about spoilers contains spoilers for the second episode of Game of Thrones, season four. 

Dear Internet,

I know your job is hard. I know you’re all competing for clicks. I know it’s not in your nature to keep a secret. But please, please stop spoiling the shows I love. Or at least stop pretending you care about those of us who might still be in the dark.

Don’t get me wrong: you’re pretty much my best friend. But when I miss my favorite show, I need you to not give all the major plot points away within 12 hours. This Monday morning, having not seen the second episode of Game of Thrones’ new season, I felt like I was traversing a spoiler minefield online — every headline, article, image, and tweet a possible threat.

A big moment, you say? Hm. 

Oh right. Those two were planning a wedding, weren't they?
Hopefully this one is less, erm, red than the last.

Oh dear. 

Welp, that narrows it down. 

It wouldn’t take a warg to figure out what transpired, but pretty soon I wouldn’t need to figure much at all.

A headline at Vulture read "Primer: He Who Plays Game of Thrones’ Joffrey." Not bad, but then you see the the sub-head: “You might not be seeing much of Jack Gleeson going forward.” Really, Vulture? Why is that? Over on Entertainment Weekly’s homepage, a few too many images of an exceptionally obnoxious-looking Joffrey were accompanied by a "Game of Thrones: the 9 most satisfying deaths" post. And then there’s Rolling Stone who did away with any spoiler-alerting effort with its morning-after post titled “George R.R. Martin on Who Killed Joffrey.” 

As always, the coup de grâce was provided by BuzzFeed. The site wasn’t just interested in giving away the big surprise death at the end of the episode, but also forecast how the big death happened. A spoiler of future episodes! I didn't even know that was a thing. 

BuzzFeed's Game of Thrones coverage

Look, Internet, you're my favorite thing to do when I'm not off enjoying the TV and movies and music that I love talking about when I'm hanging out with you. These are the stories, characters, and sounds you and I care most about. So let's keep this relationship honest. You either tell me straight up what you saw last night (Rolling Stone-style) or do a better job of keeping it to yourself.


Slideshow: How the Internet ruined Game of Thrones this week

Entertainment Weekly

Entertainment Weekly tries for the subtle approach but still suggests a death.

New York Daily News

New York Daily News tells us Game of Thrones killed off a major character.

Gawker

Gawker provides an image to suggest which major character died.

Vulture

Vulture is subtle on its homepage, but...

Vulture

...also not subtle at all.

Vulture

See if you can piece together what happened on Sunday’s Game of Thrones only using Monday’s Most Viewed articles.

Rolling Stone

Rolling Stone goes straight for the gizzard and gives it all away.

Tags:

More in:

Comments [5]

Peg from the Finger Lakes

Plenty of us have read the books of "Game of Thrones," so we already know what's going to happen. This has never spoiled my enjoyment of getting to watch the film interpretation. I just hope JRR stays alive long enough to finish the last book(s).

Apr. 16 2014 08:32 PM
andy from manhattan

Kill your internets. ;]

Apr. 16 2014 03:17 PM
Mike East from NYC

:)

Apr. 16 2014 02:41 PM

Sorry, Mike! We've added a bold SPOILER ALERT at the top. So many great episodes are in your future.

Apr. 16 2014 01:20 PM
Mike East from NYC

I totally agree, but this article just spoiled it for me (I'm on the netflix/dvd schedule, so I'm always one season behind on everything). Don't forget to point the finger back at yourself.

Apr. 16 2014 12:27 PM

Leave a Comment

Email addresses are required but never displayed.

Supported by

Supported by

Feeds