Keyword is too vague

@bradley_kent​ 

Not really. It goes to the intention of filmmaker which is usually pretty clear. Some people may find scary clowns silly but that doesn't mean the intention wasn't for the clown to be scary.

@adrian​ Some people (especially some children) find all clowns scary. That fact underscores that scariness is in the eye of the beholder.

In most instances, "evil-clown" and "killer-clown" will be better keywords than "scary-clown," especially given the subjectivity of the word "scary."  

@keyword_expert​ 

Again, it doesn't matter what some people find. It literally goes to the context of the feature.

@adrian 

What do you think of this hypothetical? Suppose that within the plot of a movie, a clown character simultaneously interacts with multiple other characters. Some of the other characters are amused by the clown, while others are scared by the clown.

A good keyword for this situation might be "scared-by-a-clown" (a keyword that doesn't yet exist). But would the keyword "scary-clown" apply? After all, some characters do find the clown scary (while others do not).

I'm not intending to suggest that "scary-clown" is an inherently bad keyword. It's not. I just think that in many situations, it will be an inferior keyword to  "killer-clown" and/or "evil-clown." 

@Michelle​ I agree with removing the block on "scary-" as a keyword prefix.

However, I recommend reinstating the block for the keyword "scary" itself (when not used a prefix). 

I see no value to "scary" as a keyword because it is too subjective. And I guarantee that if "scary" is not blocked, it will reappear in short order and will start being applied to titles. 

I suspect that the previous block against "scary-" as a prefix was originally intended to block the keyword "scary," but for whatever reason "scary-" as a prefix was blocked instead (thus blocking appropriate keywords like "scary-story," "scary-clown," etc.). This was like using a hammer to kill a fly. But rather than remove the hammer entirely, it should be replaced with a flyswatter (solely blocking the actual keyword "scary"). 

@adrian 

I am happy to report that "scary" by itself as a keyword is once again blocked. "Scary" as a prefix for other keywords remains unblocked.