ziplinerss
I've switched to using allowlist/denylist in computer contexts because more descriptive and less semantically loaded or contested. Easy win-win.
Using 'black' to refer to the color of objects is fine by me.
'Black power!' as a political slogan self-chosen by groups identifying as black is fine too, in contexts where it is used as a tool in work against existing inequalities (various caveats could be added).
As for 'white/black' as terms for entities that are colorless but inherently valenced (e.g. the items designated white are positive and the items designated black are negative, such as risks or costs), I support switching to other terms when not very costly and when newer terms are descriptive and clear. Such as switching to allowlist/denylist in the context of computers.
As for import, I don't think it is a super important change and I don't think the change would make a huge difference in terms of reducing existing racially disproportional negative outcomes in opportunity, wealth, wellbeing and health. It is only a small terminology change that there's some good reason to accept and no good reason to oppose, so I'm on board.
Irrelevant since the terms allowlist/denylist do not presuppose conditionallity or pre-set time limits.
> If someone says to add an IP address to an allow access list, that’s longer
Allowlist/denylist (9 + 8 chars) is shorter than whitelist/blacklist (9 + 9 chars).
> Inventing a personal language
Sounds like you think the proposal was to invent a whole new language (or one per person)? I would be against that too. But it is really only about updating a technical industry term pair to a more descriptive and less semantically loaded pair. Win-win.
> we aren’t going to solve racism by literally removing black and white from our language.
Changing to allowlist/denylist would not remove the terms black/white from language. There is good reason for making the change that do not involve any claim that doing so would solve racism.