The tag alias #60960 musk_cloud -> musk is pending approval.

Reason: Bringing this over from my post on e621:

Two years ago, breath_cloud was aliased to breath, with the mentality being that a breath cloud is essentially the default depiction of a breath 99.9% of the time. With that in mind, I believe this applies to musk in pretty much the exact same way. In my eyes, a musk cloud of some kind is essentially the default depiction of musk 99.9% of the time, and there doesn't really seem to be a need to have these separated.

There is an implication for musk_cloud -> musk within the transitive changes. I don't know if that would cause a problem with it being a tag implying itself during approval or if the system handles that gracefully without needing to worry about it. Let me know if there needs to be an unimplication for that.

On the mention of the breath_cloud -> breath alias, I am already handling that in my recent GIGA BUR.

The bulk update request #863 is pending approval.

remove implication musk_cloud (1194) -> musk (1865)

Reason: After doing some testing in a local instance, this will be needed to prevent some weirdness with the transitive change (without this, musk_cloud would both alias and imply to musk at the same time, which is wrong).

An alias must be true 100% of the time, otherwise you'll get mistags that user won't be able to avoid.

The question is, can we have musk depicted without the musk cloud? To me it feels like some images are tagged as such when there's sniffing and heavy sweating is involved.

Though a quick search show there's a lot of missing musk_cloud tags

kaleth said:
An alias must be true 100% of the time, otherwise you'll get mistags that user won't be able to avoid.

The "99.9%" thing isn't technically literal, it's just fluff from me repeating the wording from the now-aliased breath_cloud from e621.

The question is, can we have musk depicted without the musk cloud? To me it feels like some images are tagged as such when there's sniffing and heavy sweating is involved.

Those would then be tagged more accurately as x_sniffing (armpit_sniffing, butt_sniffing, etc.), excessive sweat, and possibly x_fetish (armpit_fetish, foot_fetish, etc.) combined rather than musk, and even then you wouldn't "see" musk, it would probably just be implied which isn't Tag What You See anyway. The visual definition for musk in this case would be a musk cloud by default since the viewer doesn't have any other real way of knowing there's musk without it.

Though a quick search show there's a lot of missing musk_cloud tags

And thus is the crux of the issue as people seem to just associate the cloud with the musk by default anyway, leading them to not tagging musk_cloud 🤷

That's why having that tag separated is completely unnecessary at this point.