[ 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)]

No. You're confusing two different things. There is an option for 'no archive warning apply' but this secret maker is talking about 'choose not to warn' which is an entirely different thing.

[(Anonymous)]

If I could summarize what I understand OP's argument to be, it would be that people should only use "Choose Not To Warn" when there is an archive warning that would otherwise apply, and should use "No Archive Warnings Apply" in all situations in which no archive warnings apply, instead of doing what they do now which is use "Choose Not To Warn" in all situations.

[(Anonymous)]

But people on AO3 warn for literally everything, so choosing "No Archive Warnings Apply" just because none of OP's triggers apply doesn't do much for the poor trypophobic kid who figured they were safe because of the "no warnings apply" tag, but is now freaking out because the author didn't warn for holes.

[(Anonymous)]

That's not an archive warning, though.

I mean, I appreciate your point. I don't think that there's a perfect system.

[ninety6tears]

It's "author chose not to use archive warnings" which falls under the same category. Or are we talking about a freeform tag because that's not explicitly clear in the secret...