[ SECRET POST #2492 ]

[case]

⌈ Secret Post #2492 ⌋

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

01.


__________________________________________________



02.


__________________________________________________



03.


__________________________________________________



04.


__________________________________________________



05.


__________________________________________________



06.


__________________________________________________



07.


__________________________________________________



08.


__________________________________________________



09.


















Notes:

Secrets Left to Post: 02 pages, 028 secrets from Secret Submission Post #356.
Secrets Not Posted: [ 0 - broken links ], [ 0 - not!secrets ], [ 0 - not!fandom ], [ 0 - too big ], [ 0 - repeat ].
Current Secret Submissions Post: here.
Suggestions, comments, and concerns should go here.

Comments

[(Anonymous)]

that kind of shit is exactly why i refuse to put any warnings on my stuff anymore beyond "read at your own risk." if you don't warn for someone's super-obscure trigger, you're liable to get yelled at for it, just like that.

this way i can just say tough shit, because i said right there that i don't warn.

[armlessphelan]

Shoot, I did that with a fic, got angry capitol letters over being triggered by a character dying offscreen, and when I pointed out that it was marked "read at your own risk" I was accused of toying with people's mental health.

Trigger warnings seem to be less "this could throw you into a panic attack" and more "this makes me sad/angry/unhappy and you're an asshole for not coddling me".

[(Anonymous)]

Really? Not even warnings for non-con, character death, abuse, or underage? Because that would make you a shitty person.

da

[(Anonymous)]

why? if the author states that they don't warn for anything and you read it anyway and get triggered, guess whose fault that is? yours.

warning for a lack of warnings is a warning. it says that you shouldn't read it if you have any triggers. also, hate to break it to you but no one "owes" warnings for anything, and it doesn't make them a shitty person if they decide not to warn.

i hate this entitled attitude that authors owe readers anything, yes even warnings. if you have triggers, then you should stick to fic archives that require warnings. otherwise? it really is "read at your own risk." the world does not need to wrap itself in bubble wrap for you.

[(Anonymous)]

Nope. And I'm fine with being a shitty person for not wanting to spoiler my own fic right at the first chapter or in the summary. Yes, I know I lose readers by "choosing not to warn", but that label was made for a reason.

I'm not unsympathetic. One of my favorite series ended a season with about the worst kind of triggery-for-me death imaginable (because I was actually in that situation and survived, but I still have flashbacks). What did I do? Went for a walk, then talked with a trusted friend.

It's a risk you have to weigh whether it's worth the possible trigger to read/watch almost anything outside the realm of fandom, and this whole "trigger warning" thing was not around in the bygone days of, say, fanzines. It's a relatively new invention. I'm an old timer, and I'd rather be able to "point to a sign", as it were, than try and justify why I warned/didn't warn for this or that.

[(Anonymous)]

Yeah. I used to warn for non-con and underage but I recently changed my policy to "choose not to warn", after seeing too many people getting shit for not using the correct trigger warnings no matter how much they tried to cover everything. I'm feeling much better with my new policy.