We've been having this discussion (unfortunately, mostly in chat) since the movie came out, and I think the regulars (and a few CMs) are in agreement with you that the spoiler markup and generic titles are out of hand. You'll know pretty well by now that this isn't uncommon when a new movie comes out, we get a flood of badly-despoiled questions, and after a ...
Yes, a picture can be a spoiler.
A single frame could be a spoiler in plenty of ways:
A corpse tells us that somebody is dead
Conversely, we could see somebody alive who was previously thought dead
We could see a character or object that was unexpected
Multiple characters together tells us about a meeting or a confrontation
and so on.
As with text-based ...
First of all, lets get this out of the way, so we can focus on the real question:
Edit Wars Are Bad, Stop Having Them
If you make an edit to a question, and the OP rolls it back, stop there. If you want to make an edit to a question and you see that it's been edited before and then reverted, stop there. Don't keep making edits that the OP is just going to ...
It's not an inherent spoiler because you're not obviously given the context. The tag would be only a minor spoiler, and only if you view the question. In this case, the question is about a broader topic to try and avoid a spoiler, so it doesn't need the series tag. If the question's title were (massive star-wars spoiler ahead)
then I would be inclined to ...
A Chrome extension, there is. Force Block, preemptively all Force Awakens Spoilers, it blocks.
Block pages containing spoilers from Star Wars: The Force Awakens, with smart pattern detection and a whitelist for false alarms.
You have to use HTML tags.
I’m not quite sure why the regular Markdown formatting works in blockquotes but not in spoiler blocks; I dug into it a while back but never got very far with it. The limited subset of HTML supported by SE mostly just works in spoiler blocks.
For linebreaks, use <br>:
>! This is a spoiler block <br> with ...
You should definitely include spoilers. The two biggest reasons that I can think of are:
The spoilers or plot twists are usually very memorable if done well. This means that the spoiler or plot twists are more likely to lead to a correct identification. I'm not an expert on the work you give in your example. When I read the first description It wasn't clear ...
I agree with both sides of the argument in that post. That is, I agree that:
1) On a site where most questions will be directly about or directly dependent on plot elements, the user should beware and expect to encounter spoilers. Sometimes, it's just not avoidable. That said,
2) The person complaining in this particular question was especially upset that ...
I created a UserScript which does just this – you specify a list of tags, and it will unhide spoilers on any question that uses those tags.
Here’s the code for the script:
As others have said, do include as much information as possible, so do include it somewhere.
But should it be in a spoiler tag?
No need if it's routine, something like "hero beats baddies", not a memorable twist, like "Space opera, floppy-haired hero fights man in black and destroys planet-killing super-weapon". You need that info about the planet-killing ...
There's a few different things going on here. I'll take them in order of importance.
1) Stop editing this question.
Once the OP has explicitly rejected your edit, stop being a jerk by continuing to try to edit it against their wishes. Seek meta consensus.
Three rollbacks is ridiculous. Nine title edits is doubly ridiculous.
2) Why didn't a moderator ...
First let me point out that you can flag anything you want for any reason you want - that doesn't mean the flag will be marked helpful :-)
Yes, this can certainly be a valid reason for flagging.
If someone asks a question about Harry Potter which specifically requests no spoilers from the last 2 books (or 3 films), and someone else leaves ...
Tag questions properly!
The system is set up for the user who does not want to be spoiled to take steps to do so.
Luckily, SE provides us with an easy avenue to do so, ignoring tags.
If a user wants to avoid spoiler for a specific franchise they can if the question is tagged properly.
For the particular question I have no reason to hide general star-wars ...
Warning: if you haven't seen The Force Awakens, don't read any of the spoilers in this post!
Technological solutions (read: hiding certain tags) have a limited usefulness. For one thing, they depend on other people using those tags.1 The other, bigger problem is that tag filtering doesn't work at all in many places, like the review queues, individual user ...
In my opinion, this question title is a borderline case where it may be a bit spoilery (I don't think it's that big of a spoiler), but we will have to live with it either way.
Lets take the commenter's points one at a time:
It's been almost a month since TFA was released
Based on our previous spoiler discussions, this is actually irrelevant. The general ...
According to this comment from eons ago, no one here can. However you can ask it on Meta Stack Exchange and they may help.
As far as I can research, the mods (and certainly the users) are unable to change the formatting page specifically for SFF. It is set by the developers, although changes have been implemented from Meta.SE they won't add every example in.
I feel that this can be solved by better editing, easily. Rough approximations:
Why wasn't capturing Superman sufficient for Zod's goal?
What were the necessary requirements (ingredients?) for McCoy to make his serum?
This doesn't make the title sound like a Jeopardy wannabe, while maintaining lack of spoilers.
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 ...
The original spoiler guidelines established on meta stated
Avoid spoilers completely in the title. This doesn't mean using [REDACTED] or silly things like that, it means coming up with another way to summarise the question.
Avoid spoilers in the first chunk of the question, because this text is often included (even if it is in spoiler tags) in links ...
While I understand the appeal, I don't see the benefit of such additional functionality out-weighing the effort to implement it, or the complaints it may cause.
Quite frankly, I'm not even certain spoilers are possible in chat. There's already functionality tied to using a mouse-over effect (it highlights all other messages related to the specific ...
There are plenty of answers on this site that are mostly spoilers, but an answer that was entirely a spoiler would not be very useful.
For me, when I have those situations, I will try to summarize the answers with all identifying information removed as much as possible, and then expand on the details in the spoiler.
At the very least, you want to get the ...
Yes, include spoilers (behind spoilertags if you want).
Spoilers may be necessary in order to correctly identify a story: a particular kind of twist ending might be a story's most distinguishing characteristic. (For example, take Neil Gaiman's American Gods: various elements of the story are similar to Joanne Harris's Runemarks or Rick Riordan's Percy ...
The easiest way to put blank lines and breaks into spoiler text (or any blockquote text) is to use the 'break' command
>! My text goes here. <br> This text goes on the next line. <br> <br> <br> I can also use multiple breaks to create multiple line breaks.