case: (Default)
Case ([personal profile] case) wrote in [community profile] fandomsecrets2020-08-06 06:25 pm

[ SECRET POST #4962 ]


⌈ Secret Post #4962 ⌋

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


01.



__________________________________________________



02.


__________________________________________________


03.


__________________________________________________



04.


__________________________________________________



05.


__________________________________________________



06.


__________________________________________________



07.

























Notes:

Secrets Left to Post: 01 pages, 08 secrets from Secret Submission Post #710.
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.

(Anonymous) 2020-08-07 02:20 am (UTC)(link)
But... AO3 does have people tagging M/F?
philstar22: (Default)

[personal profile] philstar22 2020-08-07 02:23 am (UTC)(link)
Yes, and tagging is great. What the comment was talking about was that they liked back in the day slash being warned for, with things like "this fic contained slash." I'm saying that I think that is only good if het fics also contain similar labels.

(Anonymous) 2020-08-07 02:39 am (UTC)(link)
DA - IMO, in a fandom that is 90% het, it makes sense for het to be the presumed dynamic, and to let people know when the main source of shippy content is slash (or if the fic is gen). OTOH, in a fandom that is primarily slash, it makes sense for slash to be the presumed dynamic, and to let people know when the main source of shippy content is het.

That said, it's kind of irrelevant now, since those things are pretty much always tagged for on AO3 as a matter of course.