I created the fork mentioned above. This came about after a brief and not as productive as it could have been debate on Twitter with a very opinionated SJW (and I don't mean that as a pejorative).
For clarity, I am not an SJW. I am still somewhat on the side of the fence where people say things like "it's established language, why change it?", "these terms have nothing to do with race" and "is anyone really offended by this?".
The why's and wherefores of this issue have been, are now and will continue to be hotly debated from many angles by many people.
I inexpertly created the PR not because I believe it's important for the language to change to avoid causing offence to anyone, but because someone else thought it was important and I had the wherewithal and just-about-there-but-perhaps-not level of skill to actually make the change. The cost to me was small, but the meaning of this to someone else was significant.
Let me walk that back a little before someone gets deep in the minutiae of my own use of language and reads anything between the lines. I don't write creatively enough to put invisible words between my lines. Where I said above that I don't think changing the language is important, I actually do think that if other people think it's important, the change should be made.
To curtail any "but it's only a vocal minority and we shouldn't just change things because a few people decide to read too much into technical terminology and take it the wrong way"... the fact that this is clearly a hot topic and you are likely experiencing some degree of heightened emotion whenever this comes up is itself argument for the change to go ahead.
If you want to ice this cake (OK, sometimes I get a little creative. This happens when you get older) and stick to comfortable, purely technical arguments: We live in a multinational society and software is global. Use of language for sake of clarity and ease of understanding should be considered. In my PR I used "allowlist" and "blocklist". Someone has already raised a technical reason to not use "blocklist" and I agree. "allowlist" and "denylist" seem perfect candidates.
Now... if anyone knows where I screwed up my PR, do let me know!
P.S. I didn't use any automated find & replace. I did go through the source and used 'find' to see all instances of 'white' and 'black' and I considered each change carefully. That's why 'black hole' is still in there as well as the original terms included in the database upgrade scripts.