Topic: [APPROVED] invalidate .

Posted under Tag Alias and Implication Suggestions

The bulk update request #3030 is active.

change category . (16) -> invalid

Reason: Seems to almost entirely be accidentally used, can't imagine . as a tag ever having much use.

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

Updated by auto moderator

thegreatwolfgang said:
Should just alias directly to invalid_tag, similar to ).
I don't know how changing .'s tag type to invalid would help in anything.

Agreed, this isn't a tag that people need to know what to correct it to--its appearance is almost assuredly accidental.

Disagreed - there's really no harm in knowing what mistake people made, it cleans up all the same when clearing invtags:>0. (which I do multiple times weekly)

If somebody keeps making the same mistake then can learn or be told to quit it, I have no idea what I did wrong in all of these instances.

I could waste tons of time inspecting the tag list to work out what could possibly be missing, or spending ages looking at what's aliased to invalid_tag to see what I was missing, when in reality I might've just typed ")" by accident. If that just showed on the post, I could just remove it and move along faster.

EDIT: 40 minutes later I finally worked out what I think happened with the most recent one, I probably typed "long hair" instead of "long_hair". I would've worked that out instantly if long was invalid category instead. There's a chance that wasn't even the problem either and due to the nature of how aliasing works we'll never find out.

Updated

The bulk update request #7270 is active.

remove alias ) (0) -> invalid_tag (0)
change category ) (0) -> invalid
change category ( (0) -> invalid

Reason: I think there may be a benefit to having these tags in the invalid category instead of being aliased to invalid tag, since these are very likely the result of typos, and the tagged can see what had gone wrong
( has been used quite a bit

EDIT: The bulk update request #7270 (forum #397559) has been approved by @slyroon.

Updated by auto moderator

  • 1