[ SECRET POST #2780 ]

[case]

⌈ Secret Post #2780 ⌋

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

01.


__________________________________________________



02.


__________________________________________________



03.


__________________________________________________



04.


__________________________________________________



05.


__________________________________________________



06. [repeat]


__________________________________________________



07.


__________________________________________________



08.


__________________________________________________



09.


__________________________________________________



10.


__________________________________________________



11.


__________________________________________________



12.







Notes:

Secrets Left to Post: 02 pages, 034 secrets from Secret Submission Post #397.
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)]

But why take it out on fandom? If you liked a pairing before they became a couple and then you were disappointed when they became official…well…that's sad but it's not the fandom's job to fix that for you.

That's all I'm saying.

And you can always go back and re-watch those portions of your pairing that you do enjoy in canon with the knowledge that they will get together.

I just don't see why anyone would be upset with slash fans in this case. Shouldn't you be mad at the writers?

[(Anonymous)]

Except I don't? I was really only replying the first bit because it was apparently mindboggling to you that someone could like a pairing but dislike how it was handled in canon.

Sometimes canon doesn't completely satisfy and so people turn to fic to explore relationships, things canon left vague, etc. Fix it fic exists for a reason.

[(Anonymous)]

Yeah…I can see where that was confusing.

I thought we were talking about general character interactions rather than just the actual part where the couple becomes canon. So I was bit confused as to why, if you found their interactions in general to be unsatisfying, you would ship them in the first place.

I've never really shipped something like that though. Any canon couples that I ship I've always liked their canon relationship and the way it's depicted.

But I can see how (just as an example) a Book 1-4 Harry/Ginny shipper might be disappointed with the canon relationship come Book 6. Which is the point you were trying to make, I suppose.

Just took me a little while to get it.

[(Anonymous)]

Oh, no worries! I'm sorry if I came off as an ass. :)

Nah, I was talking about the handling of the relationship after it becomes canon. Not general interactions.

I think I've got one ship that I was disappointed about how it was handled in canon. Not sure if counts since they never really git together. The potential was there and it looked like they might, but shit happened and yeah.

Yeah, that's the point I was trying to make.

[dancing_clown]

Maybe I missed something in the original comment you replied to or in the secret I've already kind of forgotten, but I don't actually see a ton of people doing this thing that you claim.

[(Anonymous)]

Well earlier on I did write "Maybe not here, but I see tons of canon pairing fans (especially on tumblr) lamenting the prevalence of slash" which was what my point was about.

It's usually always tumblr. Not really a surprise there.

I've just seen some really nasty stuff -- like one user who tore a fic to shreds and called the author a misogynist because she had tagged it with the canon couple but broke them up. Which, okay, it's frustrating to have that happen. But this was a super long fic (over 100,000 words) and the canon relationship actually took up a good deal of the fic even though it wasn't endgame so I thought it was fair for the author to use the tag.

At the very least, I thought the author getting called a misogynist was way over the line.