Re: [RFC][Discussion] Change terminology to ExcludeList

> Am 18.06.2020 um 00:36 schrieb Jakob Givoni <jakob@givoni.dk>: > To repeat what has been said many times over now: It's when "black" is > associated with "bad" in a composite term like "blacklist" we should > consider being considerate of a group of people who actually have skin > of that color. > > Best, > Jakob TL;DR: Can we please do terminology changes for the right reasons, just like the RFC itself is proposing. Thanks. --- You can also define black as what pure black really is - void of everything - no light - nothing. Things we don't see. And white being light. Things we see. It does not necessarily need to have a connection with good and bad. You can also blacklist legitimate things, but you just don't want to process them right now. The issue is rather that we are talking about "good" and "bad" inputs and then connect that to a white- or blacklist. (Because usually the things we do not want to see are bad things) There however is no innate connection from something being black to it being bad, rather a coincidence via a couple hops. And only applying in most cases. For example: "I want to whitelist undesired inputs for logging." While I see that there is a case for a more unambiguous wording like opcache_file_exclude, this matter shall not be about the good-ness or bad-ness of the color black. P.s. And to be honest, I've never heard from a dark-skinned person that they felt actually oppressed by words like blacklist. And here my personal opinion, to be taken with a grain of salt: This whole white- and blacklist discussion is mostly "hey I want to make black people feel more welcome, let me call blacklist bad and condemn everyone not agreeing. Then I have done my good deed" - without having any actual impact on the well-being of dark-skinned people. - That's what it feels like for me, but I'm open to being corrected by those who are actually dark-skinned and impacted by it, in which case I'll immediately retract my last sentence. Bob