37

Currently, on Stack Exchange, it is customary to burninate a tag first, and block it from creation only if it becomes a recurring issue. I'm sure there's a good reason for this, but it eludes me.

Why do we do it this way?


If we burninate a tag, we're saying the tag is completely unwanted. It's either a meta tag, generates no helpful context, or has no meaning. The community wants it gone.

Burnination without blocking implies that it's okay if the tag returns, because we didn't take action to remove it permanently when we very easily could have. The question in my mind is: If a community has decided that a tag has no merit whatsoever, then what is the purpose of allowing it the luxury of returning?

This is what's confusing me. We burninate tags all the time, and they're always tags we never want to see again. If they keep coming back, we block them. This doesn't make sense to me - if we're just going to keep killing them until we decide to stop them from coming back, why not just stop them from coming back in the first place?

25

The short answer here is that tag blocking was not designed as an integral part of the tag system. It's an add-on, intended for rare problems that cannot be handled any other way. That may not remain true forever, but that's how it is right now.

The long answer is that there's effectively no difference between burninating a tag and... never using the tag in the first place. Oh, there are lots of little details that vary, but if you imagine a scenario where someone creates a tag by using it on a question and then immediately removes it within the grace period so there's no record of it in the revision history... Well, that tag will be deleted by the system at the end of the day, and as far as the system is concerned it looks exactly the same as an intentional mass-removal (burnination) would.

The end result? A lot of tags get deleted, for all sorts of reasons. Blocking all of them would be a lot of overhead at best, and potentially harmful at worst. For every tag that gets removed with prejudice, there are easily hundreds that are removed because they were simple typographical errors... Or simply don't have enough questions to warrant keeping around.

One might imagine a system where blocking - and burnination - work rather differently: instead of wiping all traces of the tag from the system, the tag would merely be marked either "inactive" or "prohibited", and either ignored or ignored and blocked as a result. In such a system, blocking would be a superset of burnination, and any tag that required conscious effort to remove would naturally qualify for it.

But, that is not how the current system was designed, nor is adding such functionality a trivial extension of what exists today. When we talk about "blocking", we're not even referring to a system specific to tags - rather, it is a system intended to block harmful or malicious input from users, completely divorced from the tag system. Indeed, the most common tag that are blocked are tags that never existed: each new site comes with a block list entry for that site's topic, thus preventing the [chess] tag on https://chess.stackexchange.com/ and the [rebase] tag on https://worldbuilding.stackexchange.com/ (don't ask).

8
  • Biology has ^newb$ as an intrinsic tag, I'm not sure I really want to know what crazy mechanism is behind the creation of these intrinsic tags. Oct 27 '14 at 16:52
  • 3
    Dammit, that was supposed to be ^babby$
    – Shog9
    Oct 27 '14 at 19:08
  • 2
    Dang. Now I just really want to know why [rebase] would be blacklisted on worldbuilding...
    – Stevoisiak
    Apr 25 '17 at 0:24
  • 3
    "and the [rebase] tag on worldbuilding.stackexchange.com (don't ask)" - Ok, I'm asking. May 5 '18 at 2:43
  • Hello, there. I'm just curious, should the term "blacklist/ed" be substituted with block/ed on every post submitted in the past? What happens if a user, unfamiliar with the new directive, conducts a search using the recently-discontinued term? They are unlikely to discover the most relevant posts. I have nothing against adopting the new expression "block", it's perfectly valid but I am unsure whether deleting "blacklist" and its derivatives in old posts is actually productive and useful.
    – Mari-Lou A
    Sep 2 '20 at 7:47
  • @Mari-LouA In this case I'd agree with changing the words, as per the edit description this is linked to from a FAQ post. In other cases I think it isn't worth the effort to remove the terms. As for not being able to find it, I suspect this post to keep using the terminology and be a signpost to use the current terminology.
    – Luuklag
    Sep 2 '20 at 9:46
  • @Luuklag there's a problem with that question, it writes "black list" as two words although answers, including updated SE policy, spells it correctly.
    – Mari-Lou A
    Sep 2 '20 at 9:51
  • @Mari-LouA yes, I found it as a hit on an answer as well, but it will lead you there either way, so no problems.
    – Luuklag
    Sep 2 '20 at 9:52
11

One major reason is that it is simply not necessary in most cases to blacklist. Not all tags come back, and if you have an attentive community they'll often quickly remove bad tags if they appear again.

Blacklists are useful for tags that appear to be a good idea at first, but that are problematic if you think about it a bit longer. Those are likely to be recreated by well-meaning users, and blacklisting them makes sense.

There are a few drawbacks to blacklisting a lot of terms:

  • you need an SE employee for each change
  • a very large list of blacklisted terms makes it harder to review it
  • the blacklist is based on regular expressions, a small mistake can block unexpected things
  • I doubt the blacklist is optimized for large lists, there could be a performance penalty for checking a few hundred regular expressions every time someone uses a tag

Blocking users automatically from easily recreating tags that were intentionally removed before might be useful, but blacklists are not the correct tool for that. I could see a less invasive mechanism that e.g. just warns users if the tag they are about to create was previously removed, or increases the reputation required to recreate tags.

1
  • 2
    Is point 3 much of an issue in practice? For example, the regular expressions for math.SE's blacklisted tags currently each match at most two patterns (almost all of which are singular/plural pairs).
    – user642796
    Oct 27 '14 at 8:03
2

Only SE devs can blacklist a tag, for obvious reasons. The procedure of blacklisting a tag is exhaustive and takes time, as explained by this answer

Burninating a tag simply means that a tag is not needed in the current time. But that doesn't mean that it should be disallowed forever. A word that is unwanted one day can become the subject of many questions later.

Tag blacklist should only be done when we are sure that such a tag will never return. Blacklisting generally means that a tag is bad.

That said, there is no need to blacklist a tag just because it is a typo, it is unlikely to come back, and you don't want to annoy the devs with such requests that don't really help the site in the first place.

1
  • 1
    Well, the procedure only takes time for the community. For the devs, I imagine it's no more complicated than adding a word to a list. As commentary on the second part, while this is true, I've never seen an example of this being the case. Every burnination I've seen has been permanent - they've never been welcomed back. However, the part about typos does make sense to me.
    – user206222
    Oct 27 '14 at 7:00

You must log in to answer this question.