[ SECRET POST #4336 ]

[case]

⌈ Secret Post #4336 ⌋

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

01.



__________________________________________________



02.


__________________________________________________


03.


__________________________________________________



04.


__________________________________________________



05.


__________________________________________________



06.


__________________________________________________



07.


__________________________________________________



08.
[OP noted they'd like to apologize for leaving out the l in "evil" and once leaving out the second e in Colleen Camp's name]












Notes:

Secrets Left to Post: 03 pages, 54 secrets from Secret Submission Post #621.
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)]

And that's not asking to be told about the content of a fic? I guess you could argue semantics about "warned" vs. "alerted" or something, but it doesn't seem like productive hair splitting to me. I personally don't think it's bad to want spoilers either, but usually people who want them for movies and TV don't contact the writer/creator directly to ask for them.

[(Anonymous)]

I think that my issue with "warning" is that it implies to me that like... the motivation for asking for spoilers is fundamentally the same as the motivation for asking for trigger warnings/content warnings in fic, and I don't think that's the case.

I think that's really it though, and maybe that is a semantic distinction, IDK

[(Anonymous)]

+1