I'm inclined to think so after looking at the answers to this question:

How could Leia sense a specific death among so many?

Read, hover, read, hover, read, hover...

Do we really need spoiler protection on answers to questions? If the question title is sufficiently vague, and the question itself uses spoiler tags, and nonetheless someone is clicking on the question to read it, can we safely assume at that point that they want to see the answers and we don't need to protect them from spoilers?

  • 3
    Our spoiler policies boil down to: be courteous to others, and spoilers never expire. Beyond that, it's up to individual users.
    – phantom42
    Jan 5, 2016 at 18:06
  • if you search this meta you will find spoiler discussions dating back years with this exact same complaint, all with basically the same answer. We have a spoiler policy, some users don't know and/or don't care to follow it, and it's up to the community to fix them.
    – KutuluMike
    Jan 5, 2016 at 18:23
  • 1
    @MikeEdenfield, can you provide a link to the policy?
    – Kyralessa
    Jan 5, 2016 at 18:26
  • 2
  • which is a summary of an earlier one: meta.scifi.stackexchange.com/questions/968/…
    – KutuluMike
    Jan 5, 2016 at 18:30
  • @MikeEdenfield, I saw that question, but mine is about a different thing: Specifically, the answers. My assertion is not that we don't need spoiler warnings (I think we do) or that we don't need spoiler-free titles (I think we do), but that we don't need to protect against spoilers in answers.
    – Kyralessa
    Jan 5, 2016 at 18:32
  • The second link I provided gives guidelines for answers.
    – KutuluMike
    Jan 5, 2016 at 18:34
  • And you notice this now? ;-)
    – TARS
    Jan 5, 2016 at 19:00
  • @TARS, well, till now I'd been avoiding spoilers. :P
    – Kyralessa
    Jan 5, 2016 at 19:01
  • Personally, I think if you are having issues with spoilers you have two choices. One: don't come to the Stack until you have seen the movie or show in question if you don't want to be accidentally exposed to information. By the nature of the site, that is always a possibility. Two: Not take the issue so seriously. It's a movie or television series, its not the winning lottery numbers. One should enjoy one's fandom but not to the point it controls every aspect of your existence. If it does, then perhaps it's time to step away for a while and re-evaluate your hobby. Jan 5, 2016 at 23:58
  • 1
    @Thaddeus, you've got it backwards. The problem isn't seeing the spoilers. The problem at this point is not seeing them. The problem is a question and answer I want to read that has a hundred spoiler sections in it. It's tedious to read. Sure, if I select all, I can see them. If I add a custom style temporarily, I can see them. But I feel like we can do better.
    – Kyralessa
    Jan 6, 2016 at 0:10
  • 1
    There was a style change you could make so that the blank sections would be visible, that seemed like a good fix. If it were made into a simple to use toggle, that would alleviate the problem for everyone. Jan 6, 2016 at 0:12
  • I was actually thinking about posting a meta question about preferred formatting for long answers that are super spoiler heavy (mine was one of those in the linked question) and it has always been my understanding that on a whole, the community prefers too many spoiler tags to too few. That said, spoiler tags everywhere annoys me as a writer because trying to format long answers that contain multiple spoiler-worthy incidents as supporting evidence is a pain. FWIW, I did not personally enjoy having negotiate between readability and spoiler-blocks, but I did it for the community.
    – Aith
    Jan 6, 2016 at 4:40

1 Answer 1


Off the top of my head, I can think of a few reasons we want spoiler markup in answers:

  • Review queues. Because you can't exclude tags from the queues, I got more than a few things spoiled for The Force Awakens just because I spend a lot of time there. This is perhaps a weaker reason, because many of the queues focus on questions, and the ones that focus on answers overwhelmingly focus on new or bad answers (which are less likely to use spoiler markup in the first place), but still; if the rationale for hiding spoilers is courtesy (and it is), then even small courtesies are positive things.

  • Mods. So, I'm not a mod (obviously). I don't know how modding really works. But I'm fairly confident that mods still have to moderate on things they have not seen. Our intrepid mod team still has to keep an eye on unpleasantness in The Force Awakens questions (and answers), even if they have not seen the film. Spoiler markup in answers is a (admittedly small, in he grand scheme) courtesy we can offer to them.

  • Ongoing series/franchises. This is my biggest argument. I realize this question is motivated by the glut of The Force Awakens questions, so this reason may not apply in the specific case, but it does in general. We have a lot of questions asking about ongoing franchises or series, and people don't always wait until they're fully caught up to ask their questions.

    This is also a problem with older works, mind; I know of at least two users (you know who you are), who asked questions about The Lord of the Rings books (a series that was completed sixty years ago) while in the middle of reading them.

    As an example, consider How did John Winchester escape from hell? (top-voted answer by me), a Supernatural question. Although I couldn't be sure, the question strongly suggested to me that the asker hadn't watched past season 6, while the show is currently in its 11th season. Accordingly, I put some things in spoiler markup, because the OP may not have gotten far enough in the show to know those things. Should I not have done that, and changed the OP's viewing experience later on? I don't feel like I have that right.

Having said that, I do appreciate that some people don't care about spoilers (whether they've already consumed the media being spoiled, or if they just don't care at all), and for them reading something like the linked question (and its answers) can be frustrating. I get that. But I think there are better solutions than blanket-banning spoiler markup in answers:

  • A global "disable spoilers" button. This would be a network-wide change, have to be requested on Meta.SE, and may not be accepted (I haven't done the research to see if it's been done already), but something like that TVTropes has: a button on each page saying "I don't care about spoilers; make everything visible to me" would handily resolve this problem. People who care about spoilers have them, people who don't do not.

  • Better use of spoiler markup. One thing I try to do (not always successfully) is try to make reading the spoiler markup an optional experience. If you're familiar with the work, you should be able to glean enough detail from the surrounding (unspoilerified) context to have an idea what the spoilered content is going to say. This admittedly doesn't work for people who haven't seen a work and don't care about spoilers anyway, but I'm open to suggestions on that front.

    Contrariwise, we could try to condense use of spoilers into a few larger blocks, rather than having spoilerified sentence fragments peppered throughout. This has its own problems, notably that for some answers necessarily have so many spoilers that the answer becomes less useful for being almost-entirely spoilered. But it would reduce the amount of mouse movements, which is something.

  • Always happy to hear more suggestions and things I missed Jan 5, 2016 at 19:09
  • 2
    I like these ideas. What if the button were tag-specific? So I could elect to show all spoilers for The Force Awakens, which I've seen, but keep them hidden for things I haven't seen.
    – Kyralessa
    Jan 5, 2016 at 20:58
  • @Kyralessa Doing a little more research, a similar feature was suggested before, with little official response. You could pretty easily simulate it with a user-script, but going tag-specific might be hard Jan 5, 2016 at 21:06

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .