The terms "whitelist" and "blacklist" are words of colours and words of colours are not only for racism; a lot of words that might have one connotation in one c

The terms "whitelist" and "blacklist" are words of colours and words of colours are not only for racism; a lot of words that might have one connotation in one context has a very different meaning in a different context. Nevertheless, "allow list" and "deny list" are better descriptions of what they are doing than the words "whitelist" and "blacklist" are, anyways. (If your allow/deny lists include people (which, depending on what they are being used for, it might), then the allow list might include both white people and black people (even though people aren't really as white or black as white or black things, because your skin colour is not like #FFFFFF and #000000), and so might the deny list; I think "allow list" and "deny list" would be less confusing here. And if it includes documents with colours, well, you can still see the similar confusion, I suppose.) So, yes, use "allow list" and "deny list", just because they are better words than "whitelist" and "blacklist"; racism isn't the reason of it. (It is good to avoid being racist, but not at the expense of being meaningful. Of course, when you achieve a better meaning in a way that is not construed as being racist, as is the case here, then it is win win situation, isn't it?) However, I do not think existing APIs and commands should need to be changed, although the documentation for them can be changed, if the words "whitelist" and "blacklist" are not the names of commands. (The Apache HTTP configuration already uses the words "allow" and "deny", so that is good.)