The bulk update request #10093 is pending approval.

Reason: Alias version of bulk update request #3005. That BUR was apparently rejected due to disagreements on if the (family)_penetrating_(family) tags should exist at all, so here is a variant that removes them. These tags badly need to be integrated with the incest lore tags and I'd like to get the needle moving on this.

This BUR will also create parental incest (lore) and sibling incest (lore) tags. I believe these are valid due to the precedent set by twincest, and will provide some of the functionality lost by removing the x/p/y tags.

The bulk update request #10094 is pending approval.

Reason: Second half of bulk update request #10093.

Originally I was more in favour of aliasing [family1]_penetrating_[family2] to [family1]_on_[family2] but this is much better (and keeps the functionality mostly intact) and doesn't lead to an explosion of tags.

Also, no grandparental_incest_(lore) or ancestral_incest_(lore)?

Also you do not need to mass update a tag if you're aliasing it (to the same destination)

You'll also need to change the category of the new sibling/parental incest to lore

snpthecat said:
Also, no grandparental_incest_(lore) or ancestral_incest_(lore)?

Added.

snpthecat said:
You'll also need to change the category of the new sibling/parental incest to lore

Do regular members have the permissions to do so?

snpthecat said:
Also you do not need to mass update a tag if you're aliasing it (to the same destination)

I thought mass updates directly alter the posts, while aliases leave the original tags until the post is edited by someone.

beholding said:
I thought mass updates directly alter the posts, while aliases leave the original tags until the post is edited by someone.

No, aliases change the posts automatically. The post's "Changes" page won't show the change until the post's tags are edited by someone (whom the change gets attributed to), but it is changed right away. The same thing happens with mass updates, it just won't change future uses of the tag.

beholding said:

Do regular members have the permissions to do so?

No. That's why we can use BURs (through the line category sibling_incest_(lore) -> lore) to do so.

I thought mass updates directly alter the posts, while aliases leave the original tags until the post is edited by someone.

Mass updates and aliases both directly alter the posts. The changes being tacked onto the next person to edit the post is the same for both mupdate and alias. The changes occur no matter what, it's just the system doesn't want to add a tag change to every post under the tag for every alias or update that goes through (when you have active AIBUR approvals on popular tags the strain on the server will be massive)

Understood. BUR scripts have been updated accordingly.

The bulk update request #10095 is pending approval.

Reason: Related x-on-y tags that should probably be included as well.

beholding said:
The bulk update request #10094 is pending approval.

create alias father_penetrating (88) -> incest_(lore) (53478)
create alias father_penetrated (23) -> incest_(lore) (53478)
create alias mother_penetrating (5) -> incest_(lore) (53478)
create alias mother_penetrated (34) -> incest_(lore) (53478)
create alias son_penetrated (75) -> incest_(lore) (53478)
create alias son_penetrating (44) -> incest_(lore) (53478)
create alias son_penetrating_parent (14) -> parental_incest_(lore) (0)
create alias daughter_penetrating (1) -> incest_(lore) (53478)
create alias daughter_penetrated (45) -> incest_(lore) (53478)
change category grandparental_incest_(lore) (0) -> lore # missing
create implication grandparental_incest_(lore) (0) -> incest_(lore) (53478)
create implication grandparental_incest_(lore) (0) -> grandparent_and_grandchild_(lore) (970)
create alias grandfather_penetrating_grandson (48) -> grandparental_incest_(lore) (0)
create alias grandson_penetrating_grandfather (25) -> grandparental_incest_(lore) (0)
create alias grandfather_penetrating_granddaughter (4) -> grandparental_incest_(lore) (0)
create alias granddaughter_penetrating_grandfather (0) -> grandparental_incest_(lore) (0)

Reason: Second half of bulk update request #10093.

I also recommend the tag implies grandparent and grandchild (lore)

snpthecat said:
I also recommend the tag implies grandparent and grandchild (lore)

Wasn't aware that existed. Added.

make sure to imply parental_incest_(lore), sibling_incest_(lore) etc. to incest_(lore).

pleaseletmein said:
make sure to imply parental_incest_(lore), sibling_incest_(lore) etc. to incest_(lore).

I have.

This is now pushing into the realm of excessive, but what do you think of having something like stepparental_incest_(lore), stepsibling_incest_(lore), adoptive_parental_incest_(lore), and adoptive_sibling_incest_(lore) would be good as subcategories of pseudo incest (lore)?

snpthecat said:
This is now pushing into the realm of excessive, but what do you think of having something like stepparental_incest_(lore), stepsibling_incest_(lore), adoptive_parental_incest_(lore), and adoptive_sibling_incest_(lore) would be good as subcategories of pseudo incest (lore)?

I think they sound excessive, but if enough users have a use for them, their existence is justified.