Topic: Anus BUR

Posted under Tag Alias and Implication Suggestions

dfY6C

Member

The bulk update request #505 is pending approval.

create alias non-mammal_anus (0) -> anus (28482)
create alias penis_in_anus (2) -> penis_in_ass (1752)
create alias tailhole (18) -> anus (28482)
create implication darkened_anus (97) -> anus (28482)
create implication detailed_anus (366) -> anus (28482)
create implication hyper_anus (65) -> huge_anus (113)
remove implication hyper_anus (65) -> anus (28482)
create implication musk_cloud (1052) -> musk (1474)
create alias juicy_anus (5) -> puffy_anus (2561)
create alias visible_anus (51) -> anus (28482)
create implication brown_anus (42) -> anus (28482)
create implication building_in_anus (6) -> anus (28482)
create implication caprine_anus (11) -> anus (28482)
create implication cervine_anus (15) -> anus (28482)
create implication grey_anus (5) -> anus (28482)
create implication leaking_anus (19) -> anus (28482)
create implication lightened_anus (3) -> anus (28482)
create implication looking_at_anus (7) -> anus (28482)
create implication two_tone_anus (26) -> multicolored_anus (2)
create implication multicolored_anus (2) -> anus (28482)
create implication musky_anus (0) -> anus (28482)
create implication musky_anus (0) -> musk (1474)
create implication puckered_anus (68) -> anus (28482)
create implication rainbow_anus (2) -> anus (28482)
create implication teal_anus (2) -> anus (28482)

Reason: Adding on to topic #822 and topic #823 with some more anus tags that I found or thought of. The first 8 lines are ported from e621. The unimplication/implications with hyper_anus are for it to now be part of the usual hyper_X -> huge_X -> big_X -> X implication chain that other hyper tags also do, and of course this is how the hyper_anus tag works on e621 as well. The rest were added by me. The alias for juicy anus is because this tag was used to seemingly just describe what puffy anus already does. The alias for visible anus is because this seems to describe... just an anus really? If an anus wasn't visible, something like covered anus or partially visible anus could be used, but otherwise a "visible anus" would just be anus, similar to how there is an existing alias for exposed_anus -> anus. A tag implication in here that's off-topic is musk_cloud -> musk as that was something I noticed that was active on e621 while looking for anus tags (namely musky_anus led me to that).

EDIT: I have changed two_tone_anus -> anus to two_tone_anus -> multicolored_anus based on other two tone tags that implicate the same thing such as two_tone_fur -> multicolored_fur being a valid and existing implication on e6ai and e621. This also means that there will be an implication chain that goes two_tone_anus -> multicolored_anus -> anus.

Updated

KalethOrebiter

Privileged

dfy6c said:
create implication hyper_anus (65) -> huge_anus (113)

I don't know about
create implication hyper_anus (65) -> huge_anus (113)

isn't the scale size [big/large] -> [huge] -> [hyper] ?

I think we make a distinction, but I need to dig to be sure. Anyway, I wouldn't made that implication: of course "hyper" is "huge", and "huge" is "big". But, I think people searching for "big" are not looking for "hyper". In other words, it would force users to search for big -huge -hyper to exclude those more niche kinks

dfY6C

Member

kalethorebiter said:
words

I think you're looking or thinking about it in reverse. This wouldn't mean hyper_anus would be implied when putting big_anus, it would be that big_anus would be implied if hyper_anus was put as a tag. That's how other hyper tags work on both e621 and e6ai, and the hyper_anus tag on e621 already has this exact implication in place there. It's not going up to hyper from the smaller sizes, it's going down from hyper. A post that used big or huge_anus would not automatically include hyper_anus this way, but putting hyper_anus would put huge_anus, big_anus, and anus through implications.

Actually, disregard the above paragraph, I got confused.

So yes, it's true that searching big_anus would include hyper_anus tagged posts but so does searching anus by itself even without this change. The tag implication still applies as that is the convention taken by both e621 and e6ai, but e6ai's hyper_anus implication wasn't updated to the current standard yet. I get what you're saying but, objectively speaking, a hyper anus is descriptively a huge/big anus so it's still accurate. Besides, even without using e621 as a reference, this implication chain already exists here for other hyper tags so searching big_penis on e6ai already includes hyper_penis posts as well, so people are already accounting for something like this in the system along with the standard anus tag search showing hyper_anus stuff anyway. People who don't like hyper would (and should) have hyper tags in their blacklist regardless of this change being approved or not as they would for any tags they don't want to see and they probably already were doing this if they were just searching anus and were seeing some of the hyper ones from that. I think guests/logged out users can use the blacklist as well.

Updated

FlowerSylveon

Privileged

kalethorebiter said:
I don't know about
create implication hyper_anus (65) -> huge_anus (113)

isn't the scale size [big/large] -> [huge] -> [hyper] ?

I think we make a distinction, but I need to dig to be sure. Anyway, I wouldn't made that implication: of course "hyper" is "huge", and "huge" is "big". But, I think people searching for "big" are not looking for "hyper". In other words, it would force users to search for big -huge -hyper to exclude those more niche kinks

there are less tags for hyper and huge but the right scale for these kinds of tags is hyper -> huge -> big
because it's the implication tree