The bulk update request #5702 has been rejected.

create implication white_tuft (1837) -> tuft (448066)
create implication black_tuft (710) -> tuft (448066)
create implication brown_tuft (617) -> tuft (448066)
create implication blue_tuft (478) -> tuft (448066)
create implication grey_tuft (460) -> tuft (448066)
create implication tan_tuft (531) -> tuft (448066)
create implication red_tuft (277) -> tuft (448066)
create implication purple_tuft (208) -> tuft (448066)
create implication orange_tuft (242) -> tuft (448066)
create implication green_tuft (151) -> tuft (448066)
create implication pink_tuft (183) -> tuft (448066)
create implication blonde_tuft (2) -> tuft (448066)
create implication light_tuft (126) -> tuft (448066)
create implication dark_tuft (57) -> tuft (448066)
create implication rainbow_tuft (3) -> tuft (448066)
create implication two_tone_tuft (107) -> tuft (448066)
create implication multicolored_tuft (142) -> tuft (448066)
create alias monotone_tuft (10) -> tuft (448066)

Reason: Tuft color implications. This overall BUR has tags used that amount to over 1000 posts, and have yet to be implicated to the base tag. Color/location specifics were aliased instead for reasons seen below.

monotone_tuft is an alias for this reason:

watsit said:
I'd alias it to just tuft, yeah. It may be one of the more used tuft color tags, but still, 99% of tufts are monotone. If it were properly fully tagged on everything it should apply to, it would have nearly the same count as tuft itself, which makes it not useful to search separate from tuft.

EDIT: The bulk update request #5702 (forum #379645) has failed: Error: rainbow_tuft already implies tuft through another implication (create implication rainbow_tuft -> tuft)

EDIT: The bulk update request #5702 (forum #379645) has failed: Error: Antecedent tag must not be aliased to another tag (create implication blonde_tuft -> tuft)

EDIT: The bulk update request #5702 (forum #379645) has been rejected by @Rainbow_Dash.

The bulk update request #5703 is active.

create alias white_head_tuft (5) -> head_tuft (43117)
create alias black_head_tuft (7) -> head_tuft (43117)
create alias brown_head_tuft (4) -> head_tuft (43117)
create alias blue_head_tuft (7) -> head_tuft (43117)
create alias grey_head_tuft (4) -> head_tuft (43117)
create alias tan_head_tuft (2) -> head_tuft (43117)
create alias monotone_head_tuft (0) -> head_tuft (43117)
create alias red_head_tuft (4) -> head_tuft (43117)
create alias purple_head_tuft (2) -> head_tuft (43117)
create alias orange_head_tuft (3) -> head_tuft (43117)
create alias green_head_tuft (1) -> head_tuft (43117)
create alias pink_head_tuft (2) -> head_tuft (43117)
create alias blonde_head_tuft (2) -> head_tuft (43117)
create alias light_head_tuft (0) -> head_tuft (43117)
create alias dark_head_tuft (2) -> head_tuft (43117)
create alias rainbow_head_tuft (0) -> head_tuft (43117)
create alias two_tone_head_tuft (0) -> head_tuft (43117)
create alias multicolored_head_tuft (0) -> head_tuft (43117)

Reason: Part 2

EDIT: The bulk update request #5703 (forum #379646) has been approved by @Rainbow_Dash.

The bulk update request #5704 is active.

create alias white_ear_tuft (0) -> ear_tuft (18449)
create alias black_ear_tuft (0) -> ear_tuft (18449)
create alias brown_ear_tuft (1) -> ear_tuft (18449)
create alias blue_ear_tuft (1) -> ear_tuft (18449)
create alias grey_ear_tuft (0) -> ear_tuft (18449)
create alias tan_ear_tuft (6) -> ear_tuft (18449)
create alias monotone_ear_tuft (0) -> ear_tuft (18449)
create alias red_ear_tuft (2) -> ear_tuft (18449)
create alias purple_ear_tuft (0) -> ear_tuft (18449)
create alias orange_ear_tuft (1) -> ear_tuft (18449)
create alias green_ear_tuft (0) -> ear_tuft (18449)
create alias pink_ear_tuft (0) -> ear_tuft (18449)
create alias blonde_ear_tuft (0) -> ear_tuft (18449)
create alias light_ear_tuft (0) -> ear_tuft (18449)
create alias dark_ear_tuft (0) -> ear_tuft (18449)
create alias rainbow_ear_tuft (0) -> ear_tuft (18449)
create alias two_tone_ear_tuft (0) -> ear_tuft (18449)
create alias multicolored_ear_tuft (0) -> ear_tuft (18449)

Reason: Part 3

EDIT: The bulk update request #5704 (forum #379647) has been approved by @Rainbow_Dash.

The bulk update request #5705 is active.

create alias white_cheek_tuft (1) -> cheek_tuft (90208)
create alias black_cheek_tuft (2) -> cheek_tuft (90208)
create alias brown_cheek_tuft (1) -> cheek_tuft (90208)
create alias blue_cheek_tuft (4) -> cheek_tuft (90208)
create alias grey_cheek_tuft (2) -> cheek_tuft (90208)
create alias tan_cheek_tuft (1) -> cheek_tuft (90208)
create alias monotone_cheek_tuft (0) -> cheek_tuft (90208)
create alias red_cheek_tuft (0) -> cheek_tuft (90208)
create alias purple_cheek_tuft (2) -> cheek_tuft (90208)
create alias orange_cheek_tuft (3) -> cheek_tuft (90208)
create alias green_cheek_tuft (0) -> cheek_tuft (90208)
create alias pink_cheek_tuft (0) -> cheek_tuft (90208)
create alias blonde_cheek_tuft (0) -> cheek_tuft (90208)
create alias light_cheek_tuft (2) -> cheek_tuft (90208)
create alias dark_cheek_tuft (1) -> cheek_tuft (90208)
create alias rainbow_cheek_tuft (0) -> cheek_tuft (90208)
create alias two_tone_cheek_tuft (1) -> cheek_tuft (90208)
create alias multicolored_cheek_tuft (0) -> cheek_tuft (90208)

Reason: Part 4

EDIT: The bulk update request #5705 (forum #379648) has been approved by @Rainbow_Dash.

The bulk update request #5706 is active.

create alias white_neck_tuft (15) -> neck_tuft (62529)
create alias black_neck_tuft (1) -> neck_tuft (62529)
create alias brown_neck_tuft (1) -> neck_tuft (62529)
create alias blue_neck_tuft (0) -> neck_tuft (62529)
create alias grey_neck_tuft (4) -> neck_tuft (62529)
create alias tan_neck_tuft (2) -> neck_tuft (62529)
create alias monotone_neck_tuft (0) -> neck_tuft (62529)
create alias red_neck_tuft (0) -> neck_tuft (62529)
create alias purple_neck_tuft (1) -> neck_tuft (62529)
create alias orange_neck_tuft (0) -> neck_tuft (62529)
create alias green_neck_tuft (4) -> neck_tuft (62529)
create alias pink_neck_tuft (4) -> neck_tuft (62529)
create alias blonde_neck_tuft (0) -> neck_tuft (62529)
create alias light_neck_tuft (0) -> neck_tuft (62529)
create alias dark_neck_tuft (0) -> neck_tuft (62529)
create alias rainbow_neck_tuft (0) -> neck_tuft (62529)
create alias two_tone_neck_tuft (0) -> neck_tuft (62529)
create alias multicolored_neck_tuft (0) -> neck_tuft (62529)

Reason: Part 5

EDIT: The bulk update request #5706 (forum #379649) has been approved by @Rainbow_Dash.

The bulk update request #5707 is active.

Reason: Part 6

EDIT: The bulk update request #5707 (forum #379650) has been approved by @Rainbow_Dash.

There are more. Working on it

The monotone_ ones seem incredibly unnecessary to me. Tufts are small enough that the vast majority will be monotone, making them little different from the plain tuft tags, and the multicolored_ tags can be used to find non-monotone ones.

I also think <color>_<location>_tuft is a bit much, looking at all these implications they require. <color>_tuft in general feels unnecessary too, since tufts will typically be fur or feathers that will already have color tags applied.

watsit said:
The monotone_ ones seem incredibly unnecessary to me. Tufts are small enough that the vast majority will be monotone, making them little different from the plain tuft tags, and the multicolored_ tags can be used to find non-monotone ones.

I also think <color>_<location>_tuft is a bit much, looking at all these implications they require. <color>_tuft in general feels unnecessary too, since tufts will typically be fur or feathers that will already have color tags applied.

I didn't make the tags, some exist already so it makes the most sense to imply all of them for future use

definitelynotafurry4 said:
I didn't make the tags

You're making the implications, though. IMO, they should be aliased away instead since they're largely just cluttering up posts' tag lists, and aren't reliable or useful.

watsit said:
You're making the implications. IMO, they should be aliased away instead.

I'm making the implications because they should imply the base tag. I also disagree that they should be aliased away when a few thousand posts use them. No point in being less specific. If so, many implications shouldn't exist.

At the very least, the base color ones should implicate, which if that's all that's accepted, I'm fine with. The only reason I see to not accept the other though is to not inflate tags, but in that case they will need to be removed/aliased from all existing posts.

Edit: after thinking about it more, I actually agree with you, and will edit the BUR

The bulk update request #5708 is active.

create alias white_chest_tuft (10) -> chest_tuft (134573)
create alias black_chest_tuft (2) -> chest_tuft (134573)
create alias brown_chest_tuft (0) -> chest_tuft (134573)
create alias blue_chest_tuft (2) -> chest_tuft (134573)
create alias grey_chest_tuft (1) -> chest_tuft (134573)
create alias tan_chest_tuft (3) -> chest_tuft (134573)
create alias monotone_chest_tuft (0) -> chest_tuft (134573)
create alias red_chest_tuft (0) -> chest_tuft (134573)
create alias purple_chest_tuft (0) -> chest_tuft (134573)
create alias orange_chest_tuft (1) -> chest_tuft (134573)
create alias green_chest_tuft (0) -> chest_tuft (134573)
create alias pink_chest_tuft (3) -> chest_tuft (134573)
create alias blonde_chest_tuft (0) -> chest_tuft (134573)
create alias light_chest_tuft (0) -> chest_tuft (134573)
create alias dark_chest_tuft (0) -> chest_tuft (134573)
create alias rainbow_chest_tuft (0) -> chest_tuft (134573)
create alias two_tone_chest_tuft (0) -> chest_tuft (134573)
create alias multicolored_chest_tuft (0) -> chest_tuft (134573)

Reason: Part 7. Changed from implications to aliases, see forum post for discussion

EDIT: The bulk update request #5708 (forum #379657) has been approved by @Rainbow_Dash.

Is the above what you wanted?

definitelynotafurry4 said:
Edit: after thinking about it more, I actually agree with you, and will edit the BUR

I'm still not sold on <color>_tuft, but if others prefer to keep them, I won't push strongly on it. Except monotone_tuft, that I do strongly feel should be aliased away even if the colors stay.

I also wonder if <color>_<location>_tuft should be aliased to <location>_tuft instead, in either case. If someone tries to tag it, I think the location would be more important to keep in the resulting tag than the color.

watsit said:
I'm still not sold on <color>_tuft, but if others prefer to keep them, I won't push strongly on it. Except monotone_tuft, that I do strongly feel should be aliased away even if the colors stay.

I also wonder if <color>_<location>_tuft should be aliased to <location>_tuft instead, in either case. If someone tries to tag it, I think the location would be more important to keep in the resulting tag than the color.

Yeah I was debating using that as the location is more important, so I'll switch them again and if anyone else wants to weigh in on it, it's always possible to change them back, but yeah the location is the more important part , I agree.

Alright the hopefully final edit is in, not so sure about the monotone one myself, what would you rather it be aliased to, just tuft? It is one of the more used tuft color tags at the moment, so it would feel slightly odd to alias it now

definitelynotafurry4 said:
not so sure about the monotone one myself, what would you rather it be aliased to, just tuft? It is one of the more used tuft color tags at the moment, so it would feel slightly odd to alias it now

I'd alias it to just tuft, yeah. It may be one of the more used tuft color tags, but still, 99% of tufts are monotone. If it were properly fully tagged on everything it should apply to, it would have nearly the same count as tuft itself, which makes it not useful to search separate from tuft.

watsit said:
I'd alias it to just tuft, yeah. It may be one of the more used tuft color tags, but still, 99% of tufts are monotone. If it were properly fully tagged on everything it should apply to, it would have nearly the same count as tuft itself, which makes it not useful to search separate from tuft.

Edited over

The bulk update request #5702 (forum #379645) has failed: Error: rainbow_tuft already implies tuft through another implication (create implication rainbow_tuft -> tuft)

definitelynotafurry4 said:
The bulk update request #5702 has been rejected.

create implication white_tuft (1837) -> tuft (448066)
create implication black_tuft (710) -> tuft (448066)
create implication brown_tuft (617) -> tuft (448066)
create implication blue_tuft (478) -> tuft (448066)
create implication grey_tuft (460) -> tuft (448066)
create implication tan_tuft (531) -> tuft (448066)
create implication red_tuft (277) -> tuft (448066)
create implication purple_tuft (208) -> tuft (448066)
create implication orange_tuft (242) -> tuft (448066)
create implication green_tuft (151) -> tuft (448066)
create implication pink_tuft (183) -> tuft (448066)
create implication blonde_tuft (2) -> tuft (448066)
create implication light_tuft (126) -> tuft (448066)
create implication dark_tuft (57) -> tuft (448066)
create implication rainbow_tuft (3) -> tuft (448066)
create implication two_tone_tuft (107) -> tuft (448066)
create implication multicolored_tuft (142) -> tuft (448066)
create alias monotone_tuft (10) -> tuft (448066)

Reason: Tuft color implications. This overall BUR has tags used that amount to over 1000 posts, and have yet to be implicated to the base tag. Color/location specifics were aliased instead for reasons seen below.

monotone_tuft is an alias for this reason:

EDIT: The bulk update request #5702 (forum #379645) has failed: Error: rainbow_tuft already implies tuft through another implication (create implication rainbow_tuft -> tuft)

Most of the implications have already been approved through another BUR, the remaining ones not active are
alias monotone_tuft -> tuft
imply blonde_tuft -> tuft

Monotone tuft would need to have its aliases and implications removed first before it can pass through BUR. Additionally, do we want to keep blonde_tuft?

The bulk update request #5702 (forum #379645) has failed: Error: Antecedent tag must not be aliased to another tag (create implication blonde_tuft -> tuft)

The bulk update request #5702 (forum #379645) has been rejected by @Rainbow_Dash.

The bulk update request #5703 (forum #379646) has been approved by @Rainbow_Dash.

The bulk update request #5704 (forum #379647) has been approved by @Rainbow_Dash.

The bulk update request #5705 (forum #379648) has been approved by @Rainbow_Dash.

The bulk update request #5706 (forum #379649) has been approved by @Rainbow_Dash.

The bulk update request #5707 (forum #379650) has been approved by @Rainbow_Dash.

The bulk update request #5708 (forum #379657) has been approved by @Rainbow_Dash.