case: (Default)
Case ([personal profile] case) wrote in [community profile] fandomsecrets2014-12-21 03:45 pm

[ SECRET POST #2910 ]


⌈ Secret Post #2910 ⌋

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

01.


__________________________________________________



02.


__________________________________________________



03.


__________________________________________________



04.


__________________________________________________



05.


__________________________________________________



06.


__________________________________________________



07.


__________________________________________________



08.



__________________________________________________



09.











Notes:

Secrets Left to Post: 03 pages, 055 secrets from Secret Submission Post #416.
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.

(Anonymous) 2014-12-22 01:16 am (UTC)(link)
I consider "I Choose Not to Warn" plenty of warning. I acknowledge that warnings exist, and that triggers exist (I have a few myself). If I'm an asshole for making that decision, I'm an asshole. People have been creating works for millennia. I'd rather work in that grand tradition than try to cover every little tiny thing people want warning for nowadays.

I find it amusing that in an age where if you spoiler something, you're terrible if it's an original work, NOT spoiling things is heinous in terms of a fanwork. *shakes head*

(Anonymous) 2014-12-22 01:37 am (UTC)(link)
"Choose Not to Warn" is still a warning, though, and equally as good. It's people who do nothing, no warnings at all, that are the problem.

Also, canon spoilers are different from fanfiction spoilers for obvious reasons.