[ SECRET POST #5813 ]

[case]

⌈ Secret Post #5813 ⌋

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


01.



__________________________________________________



02.



__________________________________________________



03.



__________________________________________________



04.



__________________________________________________



05.



__________________________________________________



06.



__________________________________________________



07.



__________________________________________________



08.














Notes:

Secrets Left to Post: 02 pages, 33 secrets from Secret Submission Post #832.
Secrets Not Posted: [ 0 - broken links ], [ 0 - not!secrets ], [ 0 - not!fandom ], [ 0 - too big ], [ 0 - repeat ].
Current Secret Submissions Post: here.
Suggestions, comments, and concerns should go here.

Comments

[(Anonymous)]

This is such a weird post. It’s not how it works. The “community” hasn’t spoken about anything regarding this. Mpreg is not in every A/B/O work. And that doesn’t mean that the people who don’t write it aren’t part of the community.


And your slash example doesn’t really work. Because first off, when people say “warn for mpreg”, they mean “tag mpreg”. And tagging mpreg is common in the A/B/O community. Some people are just negligent, and that’s what the secret is complaining about. Those fringe people. And second, it’s not in the tag/warning section, but AO3 at least let’s readers know if the work has slash or not by having it be marked with M/F, M/M, and F/F. So slash is still “warned for” there, it’s just not because people are trying to sidestep around homophobes as much anymore. Telling people if the work has slash isn’t some lost thing that isn’t done anymore. And people, including in the A/B/O community, won’t stop wanting mpreg tagged either. I’ve never talked to anyone else in the community that thinks it’s baked into the concept enough that it shouldn’t be warned for when it happens. That’s just absurd.