14

One reason students-t can potentially keep reappearing is that it starts with "Student". We don't have any other tags starting with this word. So instead of blacklisting this tag, I suggest to create students-t-test as a synonym of t-test and students-t-distribution as a synonym of t-distribution. Then whoever starts typing "student..." in the tag field ...


4

FYI, I noticed a few weeks ago that kernel had come back from the dead (a little early for Halloween), again. I just removed it from the last question of this batch, but bumping this here as a reminder to active users that the tag is bad and should be killed again if it pops up again.


4

So I'm going to map kernel-density-estimate & kernel-regression to a new kernel-smoothing.


4

Here is my proposal: Objective: eliminate the meta tag big-list. The tag would be removed by the method of blacklisting (see slhck's answer). That means the tag is removed and it can't be recreated (also, it does not trigger bumping of posts). Premise: minimize bumping of threads while performing necessary actions. Constraints: 3 threads would require ...


2

Update: If the tag is automatically destroyed after 24 hours without a thread (see @amoeba's comments above), it isn't clear that anything needs to be done. Because it seems likely to lead to some mis-taggings regardless of which tag it is made a synonym of, I would lean towards 'blacklisting' as the safest option.


2

It is clear that big-list is a bad tag; it is a meta tag, it is used inconsistently, and it should go. However, batch-removing & blacklisting a tag seems to be a complicated procedure that requires an intervention of SE developers; site moderators cannot do it. In contrast, "burninating" a tag simply means manually removing the tag from all questions; ...


1

With regard to blacklisting kernel, please read: How should we make tag blacklist requests?—site mods can't blacklist tags themselves. Noting that kernel hasn't recrudesced, & that SE might well take that as grounds for not blacklisting it, I'd rather not bother. It has, & @amoeba's had to deal with it. Upvote this answer if you agree it's not ...


Only top voted, non community-wiki answers of a minimum length are eligible