Topic: BUR collection: Aliasing of non-TWYS family tags to proper lore tags - Thread

Posted under Tag Alias and Implication Suggestions

The bulk update request #5934 is pending approval.

create alias parent_and_intersex_child (6) -> parent_and_child_(lore) (37506)
create alias parent_dom_child_sub (9) -> parent_and_child_(lore) (37506)
create alias parent_penetrating_child (5) -> parent_and_child_(lore) (37506)
create alias parent_penetrating_cub (1) -> parent_and_child_(lore) (37506)
create alias parent_penetrating_son (2) -> parent_and_son_(lore) (22348)
create alias parent_penetrating_duaghter (1) -> parent_and_daughter_(lore) (14722)
create alias parent_penetrating_daughter (0) -> parent_and_daughter_(lore) (14722)
create alias parent_swap (10) -> parent_(lore) (44641)
create alias parent_penetrated (3) -> parent_(lore) (44641)
create alias father_penetrating_son (1622) -> father_and_son_(lore) (11172) # has blocking transitive relationships, cannot be applied through BUR
create alias father_dom_son_sub (183) -> father_and_son_(lore) (11172)
create alias father_fingering_son (37) -> father_and_son_(lore) (11172)
create alias father_rimming_son (13) -> father_and_son_(lore) (11172)
create alias father_penetrating_daughter (678) -> father_and_daughter_(lore) (6831)
create alias father_fingering_daughter (23) -> father_and_daughter_(lore) (6831)
create alias father_fisting_daughter (1) -> father_and_daughter_(lore) (6831)
create alias father_penetrating_child (20) -> father_and_child_(lore) (17883)
create alias father_penetrating (86) -> father_(lore) (19827)
create alias father_penetrated (21) -> father_(lore) (19827)
create alias father_rimmed (1) -> father_(lore) (19827)
create alias father_rimming (1) -> father_(lore) (19827)

Reason: Stumbled across a post tagged with son_penetrating_mother and realized that such a tag in the general category violates TWYS. Going deeper, it seems like there are a LOT of tags like this, so I decided to alias them all to the appropriate lore tags. If you need lore for each character, you cannot use TWYS to state what the characters are doing to each other.

Also, parent_penetrating_duaghter is not a typo in the BUR, that's the actual tag that was created.

This is the first of three BURs, there are a total of 53 lines including a correction for the erroneous spelling noted above, this exceeds the 25-entry maximum of a BUR. This BUR will handle "parent" and "father". The second BUR will handle the spelling correction, "mother", and "child". The final BUR will handle "son" and "daughter"

Updated

The bulk update request #5935 is pending approval.

create alias mother_penetrating_son (243) -> mother_and_son_(lore) (12032)
create alias mother_fingering_son (14) -> mother_and_son_(lore) (12032)
create alias mother_rimming_son (6) -> mother_and_son_(lore) (12032)
create alias mother_riding_son (1) -> mother_and_son_(lore) (12032)
create alias mother_penetrating_daughter (63) -> mother_and_daughter_(lore) (9155)
create alias mother_fingering_daughter (9) -> mother_and_daughter_(lore) (9155)
create alias mother_teaching_daughter (1) -> mother_and_daughter_(lore) (9155)
create alias mother_licking_daughter (1) -> mother_and_daughter_(lore) (9155)
create alias mother_and_intersex_child (6) -> mother_and_child_(lore) (21343)
create alias mother_penetrated (31) -> mother_(lore) (27268)
create alias mother_penetrating (4) -> mother_(lore) (27268)
create alias mother_swap (1) -> mother_(lore) (27268)
create alias child_swap (100) -> parent_and_child_(lore) (37506) # has blocking transitive relationships, cannot be applied through BUR
create alias child_dom_parent_sub (6) -> parent_and_child_(lore) (37506)

Reason: This is the second aforementioned BUR

Updated

The bulk update request #5936 is pending approval.

create alias son_dom_parent_sub (7) -> parent_and_son_(lore) (22348)
create alias son_penetrating_parent (9) -> parent_and_son_(lore) (22348)
create alias son_penetrating_mother (1022) -> mother_and_son_(lore) (12032)
create alias son_fingering_mother (12) -> mother_and_son_(lore) (12032)
create alias son_penetrating_father (511) -> father_and_son_(lore) (11172)
create alias son_dom_father_sub (227) -> father_and_son_(lore) (11172)
create alias son_rimming_father (36) -> father_and_son_(lore) (11172)
create alias son_fingering_father (5) -> father_and_son_(lore) (11172)
create alias son_penetrated (69) -> son_(lore) (23737)
create alias son_penetrating (38) -> son_(lore) (23737)
create alias son_swap (73) -> son_(lore) (23737) # has blocking transitive relationships, cannot be applied through BUR
create alias son_prey (2) -> son_(lore) (23737)
create alias son_rimmed (2) -> son_(lore) (23737)
create alias daughter_penetrating_mother (26) -> mother_and_daughter_(lore) (9155)
create alias daughter_penetrating_father (8) -> father_and_daughter_(lore) (6831)
create alias daughter_penetrated (43) -> daughter_(lore) (14840)
create alias daughter_penetrating (1) -> daughter_(lore) (14840)
create alias daughter_swap (22) -> daughter_(lore) (14840) # has blocking transitive relationships, cannot be applied through BUR

Reason: This is the third aforementioned BUR

Also, I can't find any info on this error I see in these BURs: "duplicate of has blocking transitive relationships, cannot be applied through bur". Could someone please explain that to me?

atomicblaze21 said:
Also, I can't find any info on this error I see in these BURs: "duplicate of has blocking transitive relationships, cannot be applied through bur". Could someone please explain that to me?

I assume it's blocked by other pending AIBURs like this one

snpthecat said:
I assume it's blocked by other pending AIBURs like this one

Good catch. Didn't realize that pending BURs could cause issues with new ones. Interestingly enough, one of the admins rejected that BUR you linked soon after you posted this reply, not likely a coincidence.

After looking at it in more detail, you have
create alias parent_penetrating_duaghter (1) -> parent_and_daughter_(lore) (11973) in the first BUR but then you have
mass update parent_penetrating_duaghter -> parent_penetrating_daughter in the second BUR. I assume it would be best to swap the BUR they're in, and have the correct spelling aliased to parent_and_daughter_(lore)

snpthecat said:
I assume it's blocked by other pending AIBURs like this one

BURs don't generate conflicts, but standalone alias/implication requests do. In this case, the responsible thread appears to be topic #40641.

snpthecat said:
After looking at it in more detail, you have
create alias parent_penetrating_duaghter (1) -> parent_and_daughter_(lore) (11973) in the first BUR but then you have
mass update parent_penetrating_duaghter -> parent_penetrating_daughter in the second BUR. I assume it would be best to swap the BUR they're in, and have the correct spelling aliased to parent_and_daughter_(lore)

I decided to change the spelling in a separate BUR than the one that would have the alias, I though I was gonna run into the "transitive properties" error since I didn't know that that error is caused by pending BURs. I could have re-ordered it to have the Parent prefix be in one of the later BURs thus allowing a spelling correction before an alias assignment. However, I'm pretty sure that the thing with aliases is that the alias tag is still able to be renamed just like a canonical tag.

Okay, I'd forgotten I'd made these, so I'm bumping this back up with a couple changes, as well as updated issues with new transitive relationships:

I removed the mass update parent_penetrating_duaghter -> parent_penetrating_daughter in the second BUR and replaced it with adding create alias parent_penetrating_daughter -> parent_and_daughter_(lore) to the first BUR. This should rectify both the original issue as well as the spelling issue.

The alias create alias father_penetrating_son -> father_and_son_(lore) has been blocked by topic #44908, which has overwhelmingly negative feedback.

There is a new issue with aliasing child_swap, son_swap, and daughter_swap, which were added to new implications as shown in topic #32151. The problem here is that parent/child relationships aren't reliably TWYS and should be aliased to their respective lore tags.

  • 1