The tag implication #51747 broken_chastity_key -> broken_key has been rejected.
Reason: self explanatory
EDIT: The tag implication broken_chastity_key -> broken_key (forum #375338) has been rejected by @slyroon.
Updated by auto moderator
Posted under Tag Alias and Implication Suggestions
The tag implication #51747 broken_chastity_key -> broken_key has been rejected.
Reason: self explanatory
EDIT: The tag implication broken_chastity_key -> broken_key (forum #375338) has been rejected by @slyroon.
Updated by auto moderator
I think this should be an alias. chastity broken_key would contain the same results, with very few false positives, and no need for a separate tag that won't always be tagged. The chastity key itself is indistinguishable from a non-chastity key, a key is a key, it would be the presence of a chastity device itself that makes the distinction, making this an unnecessary compound tag.
watsit said:
I think this should be an alias. chastity broken_key would contain the same results, with very few false positives, and no need for a separate tag that won't always be tagged. The chastity key itself is indistinguishable from a non-chastity key, a key is a key, it would be the presence of a chastity device itself that makes the distinction, making this an unnecessary compound tag.
I agree with this
The bulk update request #5505 is active.
create alias broken_chastity_key (0) -> broken_key (151)
Reason: see above
need to reject the OP first though
EDIT: The bulk update request #5505 (forum #375727) has been approved by @slyroon.
Updated by auto moderator
The tag implication broken_chastity_key -> broken_key (forum #375338) has been rejected by @slyroon.
The bulk update request #5505 (forum #375727) has been approved by @slyroon.