[ 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)]

"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)]

Yes, but that's not the only use for it, isn't it?

It's common for people to tag a fic A/B and then mark it as Gen, too, since it's gen despite what can seems like thanks to their relationship tag.

I have seen also many fics that tag the characters, but don't use the relationship tags. As a result a 'A, B, m/m' is the only hint we have that they're the main paring and the fic not being gen.

And let's not mention the issue with genderswamp fics...

[(Anonymous)]

I think some of this secret's thread has fallen into the genderswamp. ;)

[(Anonymous)]

I do think this option's only intent was to make searching for stuff easier. Authors not using the system productively is another matter altogether ...

[(Anonymous)]

Except AO3 is well known for not making searching easier, but for giving priority to the author's freedom to mark/tag their works in the way they want. That's why thinking they created such an option only for searching and not also for people who want to mark their work as het/slash/femslash/gen/other is something I can't do.

(It doesn't help that on FFnet people keep asking for the same option so they can avoid het/slash/gen, instead of wanting to find het/slash/gen easily)

[(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.