The bulk update request #13585 is pending approval.
mass update jayk_(artist) -> jayk_and
Reason: avoid possible tag collisions
Posted under Tag Alias and Implication Suggestions
The bulk update request #13585 is pending approval.
mass update jayk_(artist) -> jayk_and
Reason: avoid possible tag collisions
Which tag would it be in conflict with? If it doesn't have any tag collisions, then it should be an alias.
"Jayk" seems to be a variation of "Jake", so the jayk_(artist) should be aliased to jake_(disambiguation) afterwards if you want to avoid tag collisions.
Updated
The JayK AND Twitter/x uses both names as if it wasn't obvious that Jayk is a shortened version of that name.
Updated
clawstripe said:
The JayK AND Twitter/x uses both names as if it wasn'tbobvious that Jayk is a shortened version of that name.
OP is concerned that another artist will use Jayk_(artist) in the future.
"Jayk_and" doesn't seem to have the potential problem.
yummytummysketties said:
OP is concerned that another artist will use Jayk_(artist) in the future.
"Jayk_and" doesn't seem to have the potential problem.
I'm aware. I'm just independently confirming that the names are linked.
clawstripe said:
I'm aware. I'm just independently confirming that the names are linked.
Do you think aliases are better in this situation?
I saw and voted here before I'd seen the other thread or the discussion on Discord. This is probably the better way to go if we're concerned about tag collisions. It may be best to next alias jayk and jayk_(artist) to something like jake_(disambiguation), and we'd still need to mupdate those posts over to jayk_and first anyway.
clawstripe said:
I saw and voted here before I'd seen the other thread or the discussion on Discord.
Ah that's why. Now I see.