[ SECRET POST #4057 ]

[case]

⌈ Secret Post #4057 ⌋

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

01.



__________________________________________________



02.


__________________________________________________



03.


__________________________________________________



04.


__________________________________________________



05.


__________________________________________________



06.


__________________________________________________



07.











Notes:

Secrets Left to Post: 02 pages, 38 secrets from Secret Submission Post #581.
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)]

Surely saying "this might have triggers" is doing better than saying "this doesn't have triggers" if the fic turns out to actually contain triggers.

But I think this is one of the fundamental problems with the system the way that it is now. IMO "No Archive Warnings Apply" shouldn't be taken to mean that there are no triggers in the fic. Rather, "No Archive Warnings Apply" should be taken to mean that no archive warnings apply. "Archive Warnings" is a different, and much more specific, category than just talking about all triggers in general. And that's a large part of the reason why I think it would be more useful if used in that way. I think that's a useful distinction that would simplify things enormously for everyone.

Some people just don't like using warnings, and this system allows them to not use warnings while not leaving people who need warnings out in the cold.

Sure, and that's why I acknowledge it's probably never going to actually work the way that I'd like it to, even though I think it would ultimately make much more sense and be generally better.

[(Anonymous)]

When I said triggers, I meant archive warnings. Saying "this might contain archive warnings" is better than saying "no archive warnings apply" if it turns out that you were mistaken and archive warnings do actually apply.

[(Anonymous)]

So the concern is specifically with stories that are edge cases for the archive warnings?

I don't have a problem with people erring on the side of caution in cases like that. I also think that's a long way away from the idea that you need to tag with "Choose Not To Warn" for every fic because you can never predict what's going to trigger something. Archive warning edge cases aren't really the thing that I have a problem with.