[ 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

Re: well, here's a thought.

[mimi-sardinia.livejournal.com]

Well for my personal opinion, a presumed slashfic suddenly being het would possibly not turn me off, since I like het, but a presumed het fic that unexpectedly turns femmeslash quite possibly would turn me off.

I do however think the key word in all of this is "unexpectedly". If the OP had been aware there would be trans* in the fic, even if the fic did not tag for who would be trans*, they might be less unhappy.

Also: I have read a fic like that. It had one of the main pairing turn out to be repressed trans*. Thing is, the fic does have a trans* warning but does not say outright who it is for. It also has build-up that foreshadows the reveal, but from my own experience, it can be missed as just being signs of a repressed gay character. When the reveal happened I was "What?! He's mentally a she?! Ohhh! That's what that meant!".