Here is what Wikipedia has to say about Mask (computing).
If you click on the very general mask (386), masking (194), and masked (20) tags, what you wind up with is a hodgepodge. I'd ban those terms but have "mask" provoke more specific ones in the tag prompter. What specific ones? Well, the questions appear fit into these categories:
bit masking - how to turn 0xDECAFBAD into 0x00000BAD, that sort of thing. There are tags for bitmask (117) and bit-masks (6), but a fair number of the general mask questions fit here. I think the best name for this tag would be
image masking - As per Wiki, this is essentially an implementation method for clipping/transparency which uses a bit mask. Lots of functions in APIs exist with "Mask" or "ClipMask" in the name, and so a fair number of the general mask questions fit here as well. Few have bothered to narrow this one...but there is opacitymask (21), cgimagemaskcreate (3), cgimagecreatewithmask (3), and the unused but somehow still alive tags transparency-mask (0) and image-masking (0). I would steer these to
image-masking, which may or may not make a good synonym for
input filtering - Our friends at Microsoft, jQuery community, and elsewhere want to call it "input masking" when you are trying to constrain the typing to match a format string. I don't use the word "mask" this way, and Wikipedia doesn't mention it either. So I'd personally retag maskedinput (30) questions as input-filtering (20), and throw in
input-maskingas a synonym for
input-filteringto help anyone typing in a question. Some domain-specific tags that may or may not be valuable to keep in their own right are maskedtextbox (84), maskededittextender (40), jquery-mask (9), maskededitvalidator (5). The radmaskededitbox (4) should be merged with telerik-radmaskedtextbox (2), and I don't know if ([telerik] [radmaskededitbox]) is the better solution than [telerik-radmaskedtextbox] or not.
webkit-mask-image - this is a very particular non-standard CSS extension that probably deserves its own tag for questions that deal with this. There is one webkit-mask (2) with only two uses, but there seem to be a lot of questions about it in the pool. I would rename it to
autoresizingmask - Another very-specific thing, this time an iOS feature autoresizingmask (66): "An integer bit mask that determines how the receiver resizes itself when its superview’s bounds change". I don't care what that means, but it's obviously something other people care about and deserves to keep its tag.
netmask is that thing that most of the time is 255.255.255.0, and I'd probably redirect netmask (17) as a synonym for the more descriptive
So to sum up:
- mask/masking/masked questions get sorted and after that these tags go away.
- main umbrella terms after the change are
input-maskingwhich maps to
- well-defined stuff that just has "mask" in the name sticks around.