case: (Default)
Case ([personal profile] case) wrote in [community profile] fandomsecrets2018-02-11 02:32 pm

[ SECRET POST #4057 ]


⌈ 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.

Re: OP - kind of

(Anonymous) 2018-02-11 10:52 pm (UTC)(link)
The issue I see here is that saying authors should maybe add a "seriously guys I chose not to warn for a reason" puts all the burden on the authors to... warn people AGAIN that they chose not to warn? I'm not sure I understand why it's the author's responsibility to babysit readers this way. If an author chooses not to warn, they've chosen not to warn... for whatever reason. That WAS your warning, and no additional "no but seriously" tag should be needed.

Re: OP - kind of

(Anonymous) 2018-02-11 11:22 pm (UTC)(link)
Here's the thing, certain basic warnings are standardized in fandom. You warn for rape. You warn for character death. You warn for underage. If your fic has that stuff in it and you don't warn, people get mad at you, and IMO, rightfully so.

The one workaround you have as a fic writer is the "chose not to warn" tag. If you have stuff you need to warn for but for whatever reason you don't want to spell it out, you can use the "chose not to warn" tag. It was a system that worked because that tag effectively gives readers the heads up that the fic has applicable warnings they might want to avoid, while allowing the author to not actually give specific warnings.

When people use the "chose not to warn" tag for fics that don't have content that merits warnings, it dilutes the efficacy of the tag. The tag no longer functions as a general warning and heads up to readers who may want to avoid CD/underage/noncon. The tags comes to mean absolutely nothing about the content of the fic. The "chose not to warn" tag is no longer fulfilling its purpose, which is to provide a way for certain things to always be warned for, even in cases where the author doesn't want to use specific warnings.

Re: OP - kind of

(Anonymous) 2018-02-11 11:35 pm (UTC)(link)
The "chose not to warn" tag is no longer fulfilling its purpose, which is to provide a way for certain things to always be warned for

That's not the purpose of the tag.

You are ascribing an implicit meaning to this tag that doesn't exist.

The tag's sole purpose is to warn the reader that the author is not using warnings.

Re: OP - kind of

(Anonymous) 2018-02-11 11:43 pm (UTC)(link)
1) "Basic" warnings are not "standardized" in fandom. You're required to warn for certain things on AO3 (or indicate that you've chosen not to warn and your work may or may not contain these things) but that doesn't mean that everyone agrees that authors must warn for these things or they're terrible horrible people who deserve to be yelled at. There may be very loud people in fandom who argue that authors who don't warn deserve to be yelled at, but that doesn't make their views the standard.

2) Choosing not to warn is not meant to function as a general warning. It's meant for authors who don't feel like putting warning labels on their fic, for whatever reason.

Re: OP - kind of

(Anonymous) 2018-02-11 11:59 pm (UTC)(link)
"Basic" warnings are not "standardized" in fandom. You're required to warn for certain things on AO3

You seem to contradict yourself here. By basic warnings, I mean (and clarified that I meant) warnings for noncon, underage, character death. And yeah, those warnings absolutely are considered standard and necessary. If your fic requires one and you don't use one, you can default to "chose not to warn" but that's about it. If you don't warn at all, people will jump on you. I've never bothered to jump on an author for disregarding their warning tags before, but from everything I've seen, their error will be pointed out to them by multiple people.

Choosing not to warn is not meant to function as a general warning.

This is such an odd perspective to me. For one, because it totally contradicts everything I saw people saying about the tag back when AO3 was fist getting its legs under it. But also, because this concept of what the tag is for just doesn't make any sense. If you don't feel like using tags and you don't have anything you need to tag for, then...whyyy are you tagging in the first place? You don't feel like tags and you don't need to tag, yet you are...using a tag to demonstrate your desire to not tag?

The "chose not to warn" tag only makes functional sense if it is being used as a stand in for tags the author doesn't want to divulge. Otherwise it's literally redundant.

Re: OP - kind of

(Anonymous) 2018-02-12 12:03 am (UTC)(link)
You seem to contradict yourself here. By basic warnings, I mean (and clarified that I meant) warnings for noncon, underage, character death. And yeah, those warnings absolutely are considered standard and necessary.

Do you think that fandom begins and ends with AO3?

If you don't feel like using tags and you don't have anything you need to tag for, then...whyyy are you tagging in the first place? You don't feel like tags and you don't need to tag, yet you are...using a tag to demonstrate your desire to not tag?

By this logic, people who don't want to use tags shouldn't use AO3 ever, because even fics that are completely family friendly need the No Archive Warnings Apply tag.