Aliasing kindred_(lol) → kindred
Link to alias

Reason:

kindred from league of legends is otherworldly more popular than some DC character nobody has heard about. So to cut down on keystrokes, I say kindred_(lol) becomes aliased to just kindred, while the three posts inhabiting kindred right now be retagged to kindred_(dc)

-1, and not the reverse either.

Kindred means family (or, specifically a group of related individuals). If you check the wiki, there is a DC comic character named Kindred, a feline. Neither deserve priority of the name, it should instead be disambiguated into the family type tags, the characters from Lol, and the DC comics one.

Siral_Exan said:
-1, and not the reverse either.

Kindred means family (or, specifically a group of related individuals). If you check the wiki, there is a DC comic character named Kindred, a feline. Neither deserve priority of the name, it should instead be disambiguated into the family type tags, the characters from Lol, and the DC comics one.

We already have tags for family related things, right? I don't see why we should keep 'kindred' as a free tag since nobody is actually going to use in that way. I'd say in the context of a furry website, if you ever typed 'kindred' then you most likely meant the lol character.

Pendraggon said:
We already have tags for family related things, right? I don't see why we should keep 'kindred' as a free tag since nobody is actually going to use in that way. I'd say in the context of a furry website, if you ever typed 'kindred' then you most likely meant the lol character.

Well then... "so to cut down on keystrokes..." is a truly selfish and worthless reason, and the site already uses the suffixes on a massive scale.

As I already said: nothing, to be specific character-wise, gets priority of a suffix-less name. Further against you is:

https://e621.net/forum/show/203996
https://e621.net/forum/show/203995
https://e621.net/forum/show/186392 (Where this was commented with another character, by Furrin Gok)
https://e621.net/forum/show/186187
https://e621.net/forum/show/176636 (Knotty Curls explains this time, but Parasprite had something to say )
https://e621.net/forum/show/172752 (A case where disambiguation was used)

All this from a 152 search that I stopped at 110s because of 30-40 pages of nothing...

Ok, so would this be solved by instead implicating kindred to kindred_(lol)? As seen in most of the examples you posted. That way we can have the best of both worlds. As for the alias, deleting the original tag may not be a good idea after all.

Implying means you'd have two characters, one currently used for the DC universe and one for _(lol), whenever you just tag kindred; tagging kindred_(lol) will only have one tag. This means that all of the current searches for kindred from DC will find kindred_(lol) as well. That is still bad. Even removing the DC character and giving them their own tag is still bad, since that still leaves two kindred tags.

There is no circumventing the suffixes, and as stated disambiguating kindred might be the better because there are plenty of tags in which family may be implied (albeit it is an unusual word to use "normally"), such as mother, father, grandpa, daughter, cousin, aunt, uncle, son, nephew, grandma, brother, sister, and the variety of tags that feature combos of those.

Kindred_(DC) and Kindred_(LoL) will be the other two on the list.

I'm not sure what you mean by that. kindred from dc should be moved to kindred_(dc), and then kindred as a tag should be implicated to kindred_(lol), so when you tag kindred only, it would show up as kindred_(lol) while also allowing people who search 'kindred' to find the league character. It's the best of both worlds, and doesn't escape the suffix system. As you can see, characters like rengar utilize this, so you can search 'rengar' but still have rengar_(lol) show up everywhere.

Siral_Exan said: This means that all of the current searches for kindred from DC will find kindred_(lol) as well. That is still bad. Even removing the DC character and giving them their own tag is still bad, since that still leaves two kindred tags.

But there are two kindred tags anyway? That is inescapable as there are two kindreds involved, here. Also, implicating kindred to kindred_(lol) while keeping DC's kindred in there would indeed be stupid, I wasn't planning on keeping DC's kindred just tagged as 'kindred', anyway!

You seem to be focusing on the proper usage of 'kindred'. And we seem to be disagreeing on its proper use. In this case, I think it would be proper for an admin to decide what its meaning should be used for, and working from there.

you, then, do know that if you use the tag "kindred" with an implication, you imply whatever you made the implication with...right?

And, you do know that kindred_(lol) is not the only character with that name. As in, there is another character who shares the name kindred. Which means people who use the name kindred want to find kindred, and it may not be kindred_(lol). Meaning an alias, or as you keep saying "implication", to kindred_(lol) makes the other character harder to find if they do not know about suffixes.

Shockingly enough, that argument (it can mean multiple things) is why we have _(disambiguation) pages. Even without the family tags, you suggest to remove the name kindred, and give it to only one character, when there are two characters that both deserve it. If we want to go by age, DC is older than LoL, maybe it should keep the base name instead...

I seriously think you need to read up on how aliases and implications work: removing/singling the tag kinsman makes it harder for people to find alternatives of it. It will make finding kindred_(DC) harder to find by making all searches with kinsman (without a suffix) redirect to kindred_(LoL) ALWAYS.

If you cannot understand what this means, then go ask anyone else, and they can explain it for you.

Seeing how low amount of content there is from other kindreds, it would make sense to have the lol to be just kindred.

However to avoid any confusions and to be consistant with both tagging system and lol characters tagging, it would be far better solution to disamb the tag and have _(lol) and _(dc) respectavely. Aliasing kindred to kindred_(lol) would mean there's change of misstagging, implication would mean that all posts would have both character tags to on post which is not right either.

So -1 to this and +1 to disambing kindred and creating kindred_(dc).

Disam, clean the current tag to _(dc), keep _(lol) in use. Don't alias/implicate anything, it's not needed.

This is why we use suffixes.

Mario69 said:
Seeing how low amount of content there is from other kindreds, it would make sense to have the lol to be just kindred.

However to avoid any confusions and to be consistant with both tagging system and lol characters tagging, it would be far better solution to disamb the tag and have _(lol) and _(dc) respectavely. Aliasing kindred to kindred_(lol) would mean there's change of misstagging, implication would mean that all posts would have both character tags to on post which is not right either.

So -1 to this and +1 to disambing kindred and creating kindred_(dc).

Ah, then I've gotten mixed with implications. Disambing kindred would be a nice compromise to make sure no mistakes happen, but ultimately I feel searching kindred should lead to kindred_(lol) (while leaving kindred_(lol) to show up in the tags). If that isn't possible, disambing would be suitable. +1 to that.

Ratte said:
Disam, clean the current tag to _(dc), keep _(lol) in use. Don't alias/implicate anything, it's not needed.

This is why we use suffixes.

Didn't see this, that is suitable.

Deleted original suggestion.

Added `kindred_(disambiguation)`