[ SECRET POST #2459 ]

[case]

⌈ Secret Post #2459 ⌋

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

01.


__________________________________________________



02.


__________________________________________________



03.


__________________________________________________



04.


__________________________________________________



05.


__________________________________________________



06.


__________________________________________________



07.


__________________________________________________



08.


__________________________________________________



09.


__________________________________________________



10.


__________________________________________________



11.


__________________________________________________

















Notes:

Secrets Left to Post: 00 pages, 000 secrets from Secret Submission Post #351.
Secrets Not Posted: [ 0 - broken links ], [ 1 - not!secrets ], [ 0 - not!fandom ], [ 0 - too big ], [ 0 - repeat ].
Current Secret Submissions Post: here.
Suggestions, comments, and concerns should go here.

Comments

[(Anonymous)]

is it really transphobic to be turned off by it

no

and expect warnings

kind of maybe

[(Anonymous)]

Fuck no, it isn't. It's not homophobic to expect a slash pairing to be warned for either, that's pretty par of the course. Why would it be transphobic to expect to be warned when a character is going to be portrayed as trans? They're not more nor less special than anybody.

[(Anonymous)]

I am operating under the impression that there is a difference between a "warning" and a "tag" (or whatever general term you want to use for a general informative label for something). And it seems like you're more seeing 'warning' as just another term for that kind of informational labeling in general. So maybe that's more where the difference is coming from - different impressions of what we're talking about based on different understandings of the word "warn" versus "tag"

I'm sure that we can acknowledge that we just use terminology in different ways and try to approach this constructively, ha ha, who am I kidding, this is going to be full of wank and we're all going to die

[(Anonymous)]

DA

The difference is plain semantic, though, since "Warnings:" has been used in fandom for a long time as if it was "Contains:" and most people don't "warn" because they thins there's something wrong with something, but because the "warning" is there so people who dislike something avoid it.

[(Anonymous)]

Warning: kink, blood, bondage, D/s

Are we shaming those people now?

[bringreligiontothewamwams]

Only until they say the safe word.

^ SA

[(Anonymous)]

In case it wasn't clear, I was agreeing with you. Like "yes, other sexual things get warnings too"

(frozen comment)

[(Anonymous)]

ayrt

Yeah, you're probably right.

I think probably the issue is confusion between that sense of 'warning' and trigger warnings, really - I think that's definitely what happened for me. People see warnings nowadays, they're accustomed to thinking of it in those terms - they're accustomed to warning meaning "I want to talk about this thing but I know that it's deeply traumatic for some people." So those two senses of the word get conflated and you get a big ol' thing going on.

(frozen comment)

[bringreligiontothewamwams]

Warnings are for stuff that is generally offensive, so warning for homo and trans people would be acceptable in fic written during the 1950s, but not any more. Conversely warning for racism would be a dumb thing to do in a 1930s written fic, because everyone went out and kicked a nigger on the way home from work (Warning preceding sentence contained racism), but really needs warned for now (except in Florida, where stalking and shooting a nigger is still legally endorsed). It is a moving target.

Trigger warnings are just stupid in general though and have diluted the value of tags and real warnings.

[(Anonymous)]

Oooh, how cool would it be if fandom could just adopt a "contains:" header instead of "warning"!

[(Anonymous)]

Except nobody likes warnings for slash. In 99%+ of slash ships, it's going to be obvious it's a slash story just from the characters named. I would think canonically trans* characters would not need to be "warned" for for the same reason- if you're familiar with the source, you know their story.

If the author is making a character not canonically stated to be trans* into a transperson, I would like to know before going into because it changes my understanding of that person's characterization, and that isn't obvious from names like most slash pairings are.

[(Anonymous)]

If the author is making a character not canonically stated to be trans* into a transperson, I would like to know before going into because it changes my understanding of that person's characterization, and that isn't obvious from names like most slash pairings are.

+1

[fingalsanteater]

This.

[(Anonymous)]

"Except nobody likes warnings for slash. In 99%+ of slash ships, it's going to be obvious it's a slash story just from the characters named."

Then I have to wonder why AO3 went so far as to create the option of marking the work as m/m, f/f, f/m or/and other.
Maybe it's because people do like to know if the story contains slash/femslash/het/something else or not and listing the characters/parings names isn't enough?

[(Anonymous)]

Maybe someone wants to look for ALL the f/f fic in a fandom. It'd be a pain to think of all the possible pairing names -- so just having to click f/f makes things like this a lot smoother. Nothing too mysterious about this imo.

[(Anonymous)]

In some cases, no, the character's names aren't enough. In video game fandoms where the protagonist has the same name regardless of gender (e.g. Mass Effect or Dragon Age), pairing tags are very important in finding the exact permutation of the OTP you want to read.

[(Anonymous)]

Just to be totally shallow, I sometimes search fandom+f/f, so it's appreciated in that way.

[(Anonymous)]

this

[(Anonymous)]

Those are kind of my thoughts, too. I don't see why every plot twist needs to be warned for...aren't plot twists by their very nature supposed to be surprising? So instead of plot twists in general, if the specific plot twist of "I am trans" is what squicks OP, then yes, I think it's a little transphobic.

[(Anonymous)]

Er no I don't think that counts as a "plot twist" if there's no twist about it and suddenly character #1 is trans and was trans all along and nobody cares. The plot doesn't go in any sudden new direction, it goes on as before. Not a twist.

[(Anonymous)]

Yep, the secret reads more like suddenly during the porny bits a "oh btw. this character is trans in this fic" was randomly thrown in there. That is so not a twist -- and if it's supposed to be one, then it's bad writing.

[(Anonymous)]

AYRT

If the character isn't trans, but turns out to be trans in this fic, that sounds like a bit of a plot twist to me. Also sounds like it was poorly written, though.

ayrt

[(Anonymous)]

A plot twist is a radical change in the expected direction or outcome of the plot of a novel, film, television series, comic, video game, or other work of narrative

Emphasis mine.

Sixth Sense wouldn't have had a plot twist if Bruce Willis had been a ghost, shrugged it off, and kept on being a therapist.

Calling it a plot twist might be more offensive than demanding a "warning", because you're implying trans* relationships are somehow radically different enough from cis ships to merit a plot twist and things would go radically different from there somehow

[bringreligiontothewamwams]

No. It is not a twist, it is an AU.

[(Anonymous)]

Only if you use the definition of "warning" that implies "this thing is bad".

I'm pretty sure that OP was using "expect warning" in the sense of "expect to be alerted before reading the fic, either by a warnings section or a tag or what-fucking-ever".