case: (Default)
Case ([personal profile] case) wrote in [community profile] fandomsecrets2012-06-22 06:42 pm

[ SECRET POST #1998 ]


⌈ Secret Post #1998 ⌋

Warning: Some secrets are NOT worksafe and may contain SPOILERS.

01.


__________________________________________________



02.


__________________________________________________



03.


__________________________________________________



04.


__________________________________________________



05.


__________________________________________________



06.


__________________________________________________



07.


__________________________________________________



08.


__________________________________________________



09.
[Peter Gabriel]


__________________________________________________













[ ----- SPOILERY SECRETS AHEAD ----- ]












10. [SPOILERS for the Hunger Games]



__________________________________________________













[ ----- TRIGGERY SECRETS AHEAD ----- ]













11. [WARNING for abuse]



__________________________________________________



12. [WARNING for rape]

[Hetalia]


__________________________________________________



13. [WARNING for abuse]



__________________________________________________



14. [WARNING for gore, animal abuse]
http://i.imgur.com/SjfD3.jpg
[images of actual dead animals and stuff.]



__________________________________________________



15. [WARNING for rape]

[Video Games Awesome Live]


__________________________________________________



16. [WARNING for abuse]

[Avatar: the Last Airbender]


__________________________________________________



17. [WARNING for rape]

[American Horror Story]


__________________________________________________



18. [WARNING for dub-con, grooming, brainwashing]



__________________________________________________



19. [WARNING FOR general discussion of triggery topics (there's bound to be triggering material in the comments)]


__________________________________________________








Notes:

Secrets Left to Post: 00 pages, 000 secrets from Secret Submission Post #285.
Secrets Not Posted: [ 0 - broken links ], [ 1 - not!secrets ], [ 1 (warning for rape) - not!fandom ], [ 0 - too big ], [ 0 - repeat ], [ 1 2 - posted twice ].
Current Secret Submissions Post: here.
Suggestions, comments, and concerns should go here.
duendedefined: (Meenah)

oops, incoming tl;dr

[personal profile] duendedefined 2012-06-22 11:32 pm (UTC)(link)
Wholeheartedly agreed.

I do take triggers seriously, but Jesus fucking Christ, it's unreasonable to expect that you should warn for everything that might POSSIBLY be a trigger. There are definitely things you should warn for, yes, but I don't think "ableism" is one of them. (I'm speaking as someone who has a disability (an autism spectrum disorder, to be exact) and finds the very term "ableism" to be HORRIBLY overused, though, so I may be a bit biased anyway.) And if it's something the character would say or has canonically said, there really shouldn't be any need to warn for it.

Another thing is that some people (myself included) are triggered by things that aren't commonly thought of as triggers. For instance, in my case, the names Nick, Laura, and Kate bring back some pretty awful memories--not quite a trigger per se, but it's not exactly a comfortable experience seeing those names. And yet I don't go around saying "TRIGGER WARNING: THIS FIC MIGHT CONTAIN THE NAME OF SOMEONE WHO HURT YOU" or whatever. That would be silly.

tl;dr I think trigger warnings have gotten way out of hand, and also that "ableism" is such an overused thing to bitch about that I honestly cannot take it seriously anymore.

Re: oops, incoming tl;dr

(Anonymous) 2012-06-22 11:51 pm (UTC)(link)
And yet I don't go around saying "TRIGGER WARNING: THIS FIC MIGHT CONTAIN THE NAME OF SOMEONE WHO HURT YOU" or whatever. That would be silly.

Definitely. I've actually run across people complaining about names in canon or fic being triggery on two separate occasions. I completely understand why a name would be triggery for a person, but I really have to eyeroll is someone complains about running across a name like they should have had a warning first. You can't warn against a name without naming the name and causing the person distress anyway! There's also the "What about real life?" problem the anon mentioned above. If the name is common enough, there are going to be people out there with the same name who never did anything wrong and shouldn't have to warn people that they... have a name, I guess.
fuchsiascreams: (Default)

Re: oops, incoming tl;dr

[personal profile] fuchsiascreams 2012-06-23 05:11 am (UTC)(link)
are you fucking kidding me.

Re: oops, incoming tl;dr

(Anonymous) 2012-06-23 07:11 am (UTC)(link)
where do you people hang out, like, i've never even come close to seeing people complaint about triggery names
kittybeard: (Default)

Re: oops, incoming tl;dr

[personal profile] kittybeard 2012-06-23 12:03 am (UTC)(link)
NO KIDDING. I mean shit man, I would never expect someone to warn for spaghetti or the name Liz (..yes, spaghetti is tied to a bad experience, I WISH I was kidding!)

Re: oops, incoming tl;dr

(Anonymous) 2012-06-23 12:31 am (UTC)(link)
I agree that you can't automatically expect everyone in the world to know all of everyone else's triggers, but if someone who reads your fic has mentioned that a certain thing is a trigger, why is it not a good idea to warn for it? If you *already know* that some people in your fandom circles are triggered by ableism, why not let them know that your fic might contain it? You can't expect people to be psychic, but you can expect them to acknowledge things that they know about, even the more obscure ones.

Re: oops, incoming tl;dr

(Anonymous) 2012-06-23 02:32 am (UTC)(link)
Let me put it this way: it's shit we deal with irl. All the time. It's like warning for racism or homophobia. Yeah, it might trigger someone (I seriously doubt 90% of people using the word trigger are honestly using the word correctly), but if you're really worried about triggering someone, don't write about it. If you want to make sure no one's offended, don't do something offensive.

Re: oops, incoming tl;dr

(Anonymous) 2012-06-23 04:16 pm (UTC)(link)
To me, it's the point of the matter. I find it really entitled that people think they have the right to be warned for everything under the sun. I also find myself raising an eyebrow when an author seems to be expected to fall down apologizing when someone mentions that they were triggered be the story. Offer sympathy, sure, and even warn if you want to, but I don't get this "OMG, I'm so sorry!" thing. It puts blame on a person who hasn't actually done anything wrong. The whole situation just makes me uncomfortable.
streetcake: (HS- What the eff??)

Re: oops, incoming tl;dr

[personal profile] streetcake 2012-06-23 01:31 am (UTC)(link)
I've seen someone add a trigger warning to someone else's post because they used the word 'derp' once in a huge wall of text.

I'm not against trigger warning for ableism, but I agree that it's overused.
fuchsiascreams: (Default)

Re: oops, incoming tl;dr

[personal profile] fuchsiascreams 2012-06-23 05:12 am (UTC)(link)
..wh..

..I don't even..

Re: oops, incoming tl;dr

(Anonymous) 2012-06-23 02:28 am (UTC)(link)
"TRIGGER WARNING: THIS FIC MIGHT CONTAIN THE NAME OF SOMEONE WHO HURT YOU"

I get unpleasant feelings when I read the name "Sarah". Can you put a warning on your fic if your OC is named Sarah? Thanx.

What would be nice is if people wouldn't include it. If a character is regularly ableist, you don't need to warn. If they're not, why is it necessary to the fic? Just don't be ableist.

Re: oops, incoming tl;dr

(Anonymous) 2012-06-23 02:33 am (UTC)(link)
Yeah, I'm a staunch defender of basic warnings (violence, rape, etc) but getting super specific about every single thing when you have no idea what every trigger can be is just going way too far.

Re: oops, incoming tl;dr

(Anonymous) 2012-06-23 02:40 am (UTC)(link)
I agree about the names thing. Seeing the name Colin can bring back very, very triggery memories for me (I can't even look at the screen as I type it) but I don't expect anyone to warn for a NAME. That would be ridiculous.

Re: oops, incoming tl;dr

(Anonymous) 2012-06-24 12:21 pm (UTC)(link)
For me, it's Marian and Shelli. I also can't stand seeing "Sassy" anymore.

Re: oops, incoming tl;dr

(Anonymous) 2012-06-25 03:55 am (UTC)(link)
As a name or as the word for someone who talks back? Or both? :(