Here's a Guide for Discussing Spoilers
Wired offers a guide
By Matt Cantor, Newser User
Posted Jun 22, 2014 11:19 AM CDT
Peter Dinklage in a scene from "Game of Thrones."   (AP Photo/HBO, Helen Sloan)

(Newser) – Spoilers are a scourge of the Internet age: Between social media and entertainment sites, it can be tough to avoid learning what happened in the latest Game of Thrones before you watch it. Making things even more complicated, a Wired survey finds that people have very different views of proper spoiler conduct: Some 34%, for instance, say TV plot details can be revealed "a day or two" after airing, while 20% say you should wait a few weeks, and 11% say it's never OK to reveal them.

There's also disagreement on whether it's the responsibility of those who've seen the show to avoid revealing spoilers—or the responsibility of those who haven't seen it to avoid learning them. In an effort to calm the madness, Laura Hudson provides a guide to spoiler courtesy. Among its highlights:

  • You can talk about sports and reality show endings right away, but hold off a few days for scripted TV and a week for a movie.
  • If you're going to be upset about live-blogs of a show, simply don't go on Twitter during the show.
  • Don't read articles about shows you don't want to ruin. But those writing the articles should avoid putting spoilers in headlines shortly after an episode airs.
  • If you love it, just watch it: "The only way to be truly safe from spoilers is to transform them into something else: information you already know."
Hudson is, of course, just one voice among many: At Vulture in 2008, Dan Kois offered his own guidelines for when spoilers should be allowed in headlines (three days after a scripted TV show airs) and when they can appear within articles specifically about a show (the day after an episode airs). The New York Post and the AP have also made some suggestions—the Post says seasons or series that go out with a bang can be freely discussed within 24 hours of the finale, while the AP talks to an expert who points out that no one has a right to "spoiler alerts."

More From Newser
My Take on This Story
To report an error on this story,
notify our editors.
Here's a Guide for Discussing Spoilers is...
8%
4%
8%
42%
0%
38%
Show results without voting
You Might Like
Comments
Showing 3 of 5 comments
thewhiterider
Jun 27, 2014 2:32 PM CDT
Snape killed Dumbledore!
Ezekiel 25:17
Jun 23, 2014 5:55 PM CDT
So its the early 80's and the US still mostly had the small 2 to 4 cineplexes. So Jaws 2 came out and we had just seen it. This was the era caused by Star Wars where people lined up to get into theatres. The line was often around the whole building. Jaws 2 was like that so we were headed back to the Dodge Dart when one of our guys yells, "JAWS GETS ELECTROCUTED." All off the sudden these goat ropers were running in their Stetson alligator boots toward us and Jimmy was getting the car started as fast as he could. We barely made it out of the lot before one of the goat ropers tossed his can of Skoal at us. It was funny to see that stuff spill out on the main street. What Jimmy failed to realize though was we had two cars. The driver of the Honda Civic did not know the town very well at all. We drove around looking and never found him. We got back to our own town, 90 miles away and Mike calls to say he was in Arkansas due to taking the wrong highway not knowing he was going east when he thought he was going south. He had to wait until the next morning when the fuel station opened up, another artifact of the 80's.
Professor59
Jun 22, 2014 3:06 PM CDT
This is rough in an office setting, where dozens of people are within earshot. Particularly annoying are the ones who run out and grab a Harry Potter book or see a blockbuster movie at its midnight release, only to charge into work the next morning and proudly announce the twist ending. It would be easy to just ask someone if they've seen it, and then take them somewhere else to chat, but no, there are always going to be a_holes.