Community Blog Topic Results: What is your spoiler policy?
In last week's Community Blog Topic, we talked about everyone's spoiler policy. It was particularly timely due to all the brouhaha with the Siege of Orgrimmar and what happens at the end. Many people say that it's the individual's responsibility to avoid situations where spoilers can happen, while others say it is the responsibility of the speaker or the site to warn of spoilers.
SparkysShocker at Blood Sweat and Honor voiced a common opinion about the big warchief reveal.
... with the advent of LFR I think the safe time period to discuss major lore spoilers is once the last LFR wing is released, because at that point it is safe to assume that everyone who wants to see it for themselves has.
pvpscrub agrees.
Don't talk about the new warchief until LFR has access to the scenes. Then anyone who hasn't yet done it can stop reading if they're really interested in holding off.
JeffLaBowski at Sportsbard says it's conditional.
My general rule is 6 months on run of the mill lore, current movies/books. For something major like who won a major sporting event or say, the next expac in WoW–it's user beware! We can only shield you from so much.
angerfork at Geek Street Society says it depends on the audience.
If you need to throw out a spoiler, do it to the right audience and make sure you've given proper warning. And please, stupid though it may sound, don't do it in front of little children. If we want them to feel and live the magic that we do in so many of our geek experiences, we can't ruin it for them before they have a chance to experience it for themselves.
MentalMaggie from Polka Dots and Popcorn says there should always be a warning.
Warn people of a spoiler, no matter how new or old the content/movie/book is. But again, keeping in mind that accidents happen, if a movie or book is rather old, it is up to the person to mention they have not seen or read whatever it may be as the conversation starts to avoid such accidents.
EWOKinLA insists on taking perdonal responsibility.
My policy is "If you don't want Spoilers...Don't Read WOW Fansites or Listen to WOW Podcasts!!!!
slashafk from /AFK agrees.
But people need to be aware that if they visit sites such as WoW Insider, spoilers could be found from either the stories themselves or from the people posting comments, whether it's accidental or not. If you're a person that prefers to be in the dark about plot twists and turns, then perhaps cocooning yourself off from WoW sites and even the game itself would be the best thing for you.
As does lake_tortoise.
My policy: It's (almost) totally my responsibility to avoid spoilers.
Matthew2 says anything goes as long as it's not in beta.
Once its live for anyone, it can be talked about. It is NICE to say *spoilers* if it's new, not seen by everyone, but once it's common knowledge, that is more a courtesy imho.
If its in Beta or not Live, one should not talk about it without SPOILER ALERT being prominent (and clicking a link is awesome)
ArchLobster doesn't mind spoilers.
The telling of the story is more important than the surprise. You only see the end fresh once.
And BnDov3r spoils it for everyone.
... you're gonna love it when Thrall draws all the elemental powers to him with the Dragonsoul (turns out he still has it! I know, shocker!) and becomes Captain Azeroth, and then starts cleansing the world from all Sha corruption. Then all the faction leaders go out for shawarma.
Please don't put any spoilers in the comments. We're talking about spoilers but not revealing any here. But please do put suggestions for future Community Blog Topics below. We're always looking for good ideas.
