[ SECRET POST #1595 ]

[case]

⌈ Secret Post #1595 ⌋


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


01.



__________________________________________________

02.


__________________________________________________

03.


__________________________________________________

04.


__________________________________________________

05.


__________________________________________________

06.


__________________________________________________

07.


__________________________________________________

08.


__________________________________________________

09.


__________________________________________________

10.


__________________________________________________

11.


__________________________________________________

12.


__________________________________________________

13.


__________________________________________________

14.


__________________________________________________

15.


__________________________________________________

16.


__________________________________________________

17.


__________________________________________________

18.


__________________________________________________

19.


__________________________________________________

20.


__________________________________________________

21.


__________________________________________________

22.


__________________________________________________

23.


__________________________________________________

24.


__________________________________________________

25.


__________________________________________________

26.


__________________________________________________

27.


__________________________________________________

28.


__________________________________________________

29.


__________________________________________________

30.


__________________________________________________

31.


__________________________________________________

32.


__________________________________________________

33.


__________________________________________________

34.


__________________________________________________

35.


__________________________________________________

36.


__________________________________________________

37.


__________________________________________________

38.







Notes:

Secrets Left to Post: 07 pages, 170 secrets from Secret Submission Post #228.
Secrets Not Posted: [ 1 - broken links ], [ 0 - not!secrets ], [ 0 - not!fandom ], [ 0 - too big ], [ 0 - hit/ship/spiration ], [ 0 - omgiknowthem ], [ 0 - take it to comments ], [ 1 - repeats ]
Current Secret Submissions Post: here.
Suggestions, comments and concerns should go here.

Comments

[cherrycoloured.livejournal.com]

The person who said that is being ridiculous and sounds homophobic. Homosexuality doesn't need to be warned for. If that person can't read the pairing line, it's their fault.

[(Anonymous)]

Some people don't like reading slash.

[cherrycoloured.livejournal.com]

Obviously, but there is a difference between saying someone should warn for slash and saying that writer should have put that the story contains slash in the summary. Saying that they should warn for homosexual content is really offensive. Of course, one should be able to tell there will be slash in the fic from the pairing line, so it's the reader's fault for not looking at that.

[nyteowl112.livejournal.com]

What bothers me about this argument is that its all based on semantics.

'Can I go to the bathroom?' 'Don't you mean "May I go to the bathroom"?'

I mean, its not to say that I don't get the point of what you're saying, but at the end of the day, its arguing how to be the most politically correct. Which is, in itself, a whole other can of worms.

I know that the two have different connotations, don't get me wrong. But its frustrating to hear an argument based all around how you worded something.

[cherrycoloured.livejournal.com]

I completely disagree. How one words things matters a lot. If even one simple word can change the way something is read, it is important. The difference between "warnings" and "contains" is the difference between alienation and acceptance. Also, I don't see anything wrong with being "politically correct", it just means "inclusive and taking oppression into account."

[(Anonymous)]

Oppression for putting the word slash in the "wrong" place?

[cherrycoloured.livejournal.com]

Saying that someone's sexuality needs to be warned for is really offensive, especially since pretty much no one warns for heterosexuality.

[(Anonymous)]

Okay, well, think about if it were another issue. Ex: gender. It's the difference between "Pairing is Female X/_____" and "Warning: WOMEN". One is a normal statement about the subject of the fic, and the other is a kind-of offensive unnecessary warning. It's semantics, yes, but it's not so much about being politically correct as it is about not sounding like a prick or an idiot.

[(Anonymous)]

then they can deal wid it

[(Anonymous)]

Looks to me like they dealing with it. You're the one who are making a fuss.

[(Anonymous)]

Woah woah, do you know me anon?

[ciilantro.livejournal.com]

Trust me anon, not all do.

[(Anonymous)]

DA. You shouldn't warn for homosexual content as in mentioning that a character is gay. No warning needed for that. But you should warn for explicit gay porn as much as you should warn for explicit het porn. Some people get turned off by some things. I can't read het for my life, and I very much appreciate a warning for het (again, for explicit sex scenes, not for the mention of a heterosexual relationship) at the beginning of a fic so I'm not suddenly confronted with something that turns me off in the middle of a fic. I assume people who don't like to read slash feel the same.

If the pairing is mentioned in the pairing line, of course, you don't need to warn for anything. But still, I'm grateful that many slash writers have the decency to warn if there's surprise!het somewhere in their fic.