Danbooru

Tag Implication: necktie_on_head -> necktie

Posted under General

What, is the database running out of room? I think the tag count is irrelevant - if it makes sense, there should be an implication.

Deciding on whether or not to create an implication should hinge on if we actually want to use the tag at all.

Updated

I still stand by our old sensible numbers for implications of 50 posts minimum. I have put off bringing this argument up for quite a while because jxh stopped following it but I may as well point out the logic behind it.

Currently only ~2.1% of posts have more than 100 posts, ~3.6% have more than 50. If this is cut down to general tags the numbers jump to ~15% and ~20% respectively. With a large majority of posts having not even 50 posts this was not a totally illogical limit to impose. 50 is a good point at where a tag is established and most likely worthwhile and a point beyond where someone's going to fold it into another tag thinking they're helping the greater good.

I'm with Bapabooiee on this one. If it makes semantic sense and the tag is in use, there's little reason not to make an implication.

EDIT: Log makes sense too, but like he said, we have been approving implications for small tags a lot lately. Also I can't think of anything necktie_on_head could possibly be rolled up into.

Bapabooiee said:
What, is the database running out of room?

When I look at the growing list of features that albert had to cut off over the past months, basically because the database reached critical mass in certain areas, I think that way yes.

And with that I also think the trade-off —thread's purpose vs bothering the forum— isn't fair until the reason starts to get somewhat significant, notably if you can quickly handle the matter yourself before that point (for the record I own a nice bunch of stuff that I never asked the forum about because it looked like a hassle for everyone, and I'm probably not alone to do so).

Cyberia-Mix said:
And with that I also think the trade-off —thread's purpose vs bothering the forum— isn't fair until the reason starts to get somewhat significant, notably if you can quickly handle the matter yourself before that point (for the record I own a nice bunch of stuff that I never asked the forum about because it looked like a hassle for everyone, and I'm probably not alone to do so).

I keep on re-reading this, but I have no idea what you're trying to say.

Could you please clarify?

I'd rather not make a thread for something before it seems really necessary.
Reasons include having the time to handle the discussions likely to ensue (which concerns everyone contributing to the forum), and jxh wanting to kill himself over all he has to catch-up.

When talking about an implication, if it's a small tag I'll apply it manually and leave things that way. If it's big enough to need regular control then I'll request the implication.

That remains my personal stance but seriously, submitting an alias/implication for every little thing, all the more when it always has to be handled by the same person, is doubly oblivious to me.

Updated

Well, yeah, the traditional reluctance to do aliases and implications for really small changes was about not wanting to set a precedent where every. damn. minor. thing. gets a thread. Because if we really wanted to enact a complete semantic hierarchy encompassing all our tags we would probably have a million implications and aliases. So Log and Cyberia are not incorrect.

On the other hand, if it has been posted, and makes perfect sense, and I'm already reading the thread... well, it doesn't take me very much longer to hit the button and leave a "Done" and move on. Otherwise I'd feel like I wasted the effort of opening the thread and thinking about it. =P If I start seeing 100 minor requests in a day, then okay yeah something will need to change. But we're not there yet. My main problem keeping up isn't the volume of threads, it's the extremely limited time I have to come onto the forums thanks to work (once a week for full sweeps, basically).

All that to say, "Done".

1