The bulk update request #5633 is pending approval.

Reason: These tags all involve a character asking or demanding to do something to someone else, have something done to them, or have something done for them. Grouping them all under requesting could be helpful for tag discovery.

Many of these tags have low numbers, but *_request tags are relatively new, so they're merely undertagged.

I'm going to take this opportunity to say, we really ought to split impregnation_request down the middle. it's very strange that we consider both a request/demand to impregnate a character ("get pregnant") and a request/demand to be impregnated ("give me your puppies") as the same situation.

sipothac said:
I'm going to take this opportunity to say, we really ought to split impregnation_request down the middle. it's very strange that we consider both a request/demand to impregnate a character ("get pregnant") and a request/demand to be impregnated ("give me your puppies") as the same situation.

I didn't notice that both concepts were under the same tag, I agree, they shouldn't be grouped together, though I'm not sure what the tag name(s) should be.

maplebytes said:
I didn't notice that both concepts were under the same tag, I agree, they shouldn't be grouped together, though I'm not sure what the tag name(s) should be.

what about changing impregnation_request to only apply to the receiving party and creating a request_to_impregnate tag to cover the inverse case. I believe that quite a large majority of the posts populating impregnation_request are already the former example, so it'd make more sense to move the remainder to a new tag.

I'm a bit cautious about removing a use case for a tag like this because it'd potentially lead to confusion and mistags, but I'm not sure if there's really a better solution. leaving the current tag as is and creating two separate child tags will likely just have users continue to use the old tag as-is and not use the new tags.