[ SECRET POST #5359 ]

[case]

⌈ Secret Post #5359 ⌋

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


01.



__________________________________________________



02.



__________________________________________________



03.



__________________________________________________



04.



__________________________________________________



05.



__________________________________________________



06.



__________________________________________________



07.









Notes:

Secrets Left to Post: 01 pages, 24 secrets from Secret Submission Post #767.
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)]

I don't understand why this is so hard to get for some people.

[(Anonymous)]

It's hard to get something you don't want to get.

[(Anonymous)]

I get it, I just don't like it. I think it is a dick move to not warn for things at least that are common triggers. It is one thing to use it just in case but also have other warnings. But authors who use that and nothing else are jerks.

[(Anonymous)]

Fwiw "I don't like it, agree to disagree" is different from "I just don't understaaaaaaand"

[(Anonymous)]

They ARE warning you. They're warning you that this story may have common triggers, or it may not, and they're not going to say either way. That IS a warning. It's a warning that if you need trigger warnings, this story might not be safe for you.

It's different from No Archive Warnings Apply, which is a promise that it doesn't have any of those four elements.

[(Anonymous)]

+1

[(Anonymous)]

The use of that tag is a warning. If you think you won't be able to deal with whatever an author might throw at you without a specific warning, don't read the fic. It's really that simple, no one's forcing you to read it.

[(Anonymous)]

It would be more of a dick move to not put anything than to put a basic "read at your own risk" note, which is what this tag functions as.

[(Anonymous)]

https://archiveofourown.org/works/22491910

[esteefee]

"[CntW] gives you what you need to protect yourself, but it doesn't give you what you need to access every piece of art you possibly could."

Yup.

Also, one point not mentioned in the essay is the necessity for the tag in doing massive imports of works from ancient archives that didn't have warnings, or where the tags don't line up with AO3's. In order to save those works before the old archives go down and they are lost forever, the works will be tagged CntW automatically. Authors can choose to re-tag them later if they wish, but the point is, they've been saved from oblivion.

[(Anonymous)]

Thank you, I'll keep that for reference!

[(Anonymous)]

No, you don't actually get it.

[(Anonymous)]

Look, if that tag is enough to define the author as a dick to you, then don't read that author. Simple as that. The rest of us don't have a problem with it because we consider it a useful tag.

[(Anonymous)]

No, they're not. But you certainly are.

[(Anonymous)]

One time I wrote a fic that dealt with upsetting things. I did tag for some common triggers but I also was afraid I would miss some and other elements were complete spoilers so I used the "chose not to warn" option to say "Hey, this isn't a safe fic." If that's a dick move, I don't know what to say to you.

[(Anonymous)]

THIS, one thousand percent. People who think their ~artistic vision~ is more important than not triggering people are assholes. Also, if you're going to have Dead Dove content in your fic and not warn for it, you're failing to uphold your side of the deal. If you're out there writing underage incest and not explicitly warning for it, that's fucked up.

[(Anonymous)]

If you can't handle surprise underage incest, the did not warn tag *is your warning.* You don't read those fics if it *might* be there. That's fandom for ya. It's always been a free space for writing your most fucked up ideas in. You can keep to fics with no content warnings. If that makes you feel limited or like a baby, too bad. Grow a thicker skin or proceed with the training wheels on.

[(Anonymous)]

The way books work is going to blow your mind.

[(Anonymous)]

It's not anyone else's responsibility but yours to manage your triggers.

That's like going to a pool with murky water and a sign that says "we can't guarantee what is or isn't in this water," and getting mad because you went in anyway and got bitten by a snake.

[(Anonymous)]

+1

If you have triggers and want to go into the murky CNTW waters anyway, get yourself a reading buddy who'll read first and tell you in detail whether it's safe for you or not. I know a few people who do that with books.

[(Anonymous)]

So what makes you think you're entitled to click on a fic that very clearly indicates that it may contain unpleasant things and expect to get anything else?

[(Anonymous)]

And yet every time someone dares complain about readers, comments, etc., writers are told they should be writing for themselves and their own enjoyment, not worrying about what readers think of it or acting as if they’re entitled to any sort of feedback (that is, there is no side of the “deal” that readers need to uphold). So which is it? Are we supposed to focus on our own ~artistic vision~ or the reciprocal reader-writer relationship and the responsibilities of shared fandom communities?

+10000

[(Anonymous)]

Wow, so many insensitive, self-involved jerks ITT. Y'all really out here making a Schrödinger's box out of people's triggers for the purpose of some passive-aggressive "don't tell me what to do" bullshit. Thank god every fandom I've ever been in has been less of a misanthropic backwater than F!S, tbh.

Re: +10000

[(Anonymous)]

If you're too stupid to avoid clicking on something that clearly flags that there might be things you don't like in there, you're too stupid to be allowed on the internet.