-
Notifications
You must be signed in to change notification settings - Fork 628
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Discussion] Usage of the term "whitelist" #219
Comments
At Airbnb, we use eslint-plugin-inclusive-language to enforce the use of inclusive language in our codebase, and would also like to be able to use Perhaps @leizongmin what do you think? Would you accept such a pull request? |
Hi, @lencioni I would be happy to accept such pull request. |
Enforce silly language rules one country care about is not good. No one care about your race or sensitive words. Stop putting rules for other country, culture. We do not care about easy offend United States and UK people. You are not important as you think. Blacklist Whitelist used forever in computers and do not mean your race problem in United States and UK. You did slaves, not world. Get over yourself. |
Yeah... A lot of countries have some history of slavery, or worse, as I'm sure you're well aware during World War 2 Germany wasn't good to people of colour and did have slavery (more focused on Russians, but still slavery): https://www.rbth.com/history/329852-ostarbeiter-soviet-captives-in-germany So it really does seem that you should be a bit more concerned about this kind of language than you are. Ultimately this is about what people who are affected by it think, salty people, German or otherwise, don't really get a say. |
Firstly thanks to all the contributors for this fantastic module.
Was wondering if the owners were open to removing the usage of "whitelist". My current organization tries to steer away from this terminology/connotation in our codebases. Happy to do the PR myself.
Alternatives for blacklist/whitelist are denylist/allowlist and blocklist/passlist.
Kindest,
Jon
The text was updated successfully, but these errors were encountered: