News for hackers. Stuff that matters.
[dead]
Re:Things you should do now (2011) by alexwebb2 on Friday February 19, 2021 @10:03AM (#26193885)
Serious answer: this is still very much in flux. We're not at the point where you'd get audible gasps from using these terms, but in certain audiences you'll get some raised eyebrows.

If you believe that having "black=bad, white=good" connotations built into our jargon is harmful in some way, then yes, you should strive to use alternate terms.

If you don't think that's harmful, and you're forceful in defending "black=bad, white=good" as being too established and too inconvenient to change, that's when you're likely to get pushback.

Personally I've been trying to use "deny-list" and "allow-list" (with partial success – changing your jargon is hard). They feel a bit clunky, but I suspect that clunkiness will fade with time.

Re:Things you should do now (2011) by DavidHilbert on Friday February 19, 2021 @11:01AM (#26194483)
its not blacklist and whitelist because "black=bad, white=good", black is the abscense of light, hence the light is blocked, white would obviously be the opposite. So its black because you are blocking things, and white because you aren't.
[dead]
Re:Things you should do now (2011) by wizzwizz4 on Friday February 19, 2021 @01:25PM (#26196183)
“Blacklist” and “whitelist” are confusing terms. Why does “black” mean “no”? There are plenty of reasons to use better terms in new projects other than “they upset people” – though that should be a good enough reason on its own.
Re:Things you should do now (2011) by Eric_WVGG on Friday February 19, 2021 @09:01AM (#26193199)
You’re not wrong that a segment of the population has deigned this term offensive, but it’s maybe a very extreme fringe segment. A lot of self-proclaimed “woke” types would roll their eyes at this one. But the same language reformers did convince GitHub to rename “master” branches to “main” so who knows.

Regardless, this article is from 2011, so it predates the discussion.

Re:Things you should do now (2011) by neogodless on Friday February 19, 2021 @09:29AM (#26193492)
While I'll avoid the political nature, I do find the terms are misused. In Firefox extensions, for security it's more intuitive (based on prior usage) for security-related extensions like an ad block. Anything on a whitelist is allowed (to include ads), and on the blacklist, it is not allowed (ads are blocked).

But I have another extension that just modifies the format of some pages to make them easier on my eyes. It took experimentation for me to realize that items on the whitelist are modified, while those on the blacklist are not. My intuition told me whitelists are for sites that are good the way there are, and sites that are hard on the eyes should be put on the blacklist.

It's not the worst mix-up in the world, and perhaps many smarter than myself would have no such confusion, but I think it could be avoid with words that mean what they do. There's plenty of room in the extension configuration to put "apply to these sites" or "transformed", as well as "allow original format" or "unchanged."

Re:Things you should do now (2011) by kleton on Friday February 19, 2021 @09:35AM (#26193559)
This article was written before Year Zero
Re:Things you should do now (2011) by kaeruct on Friday February 19, 2021 @10:46AM (#26194340)
I've seen blocklist as a replacement for blacklist, but what do people use instead of whitelist?
Re:Things you should do now (2011) by edoceo on Friday February 19, 2021 @11:01AM (#26194490)
I use 'permit_list' and 'reject_list'. Even before the colour based issue - because these names were more clear to me.
Re:Things you should do now (2011) by dragonwriter on Friday February 19, 2021 @10:46AM (#26194342)
“allowlist"
Re:Things you should do now (2011) by faeyanpiraat on Friday February 19, 2021 @05:04AM (#26191379)
Sigh..
Re:Things you should do now (2011) by teddyh on Friday February 19, 2021 @05:25AM (#26191499)
What? Did I miss a memo or something? I would have hoped to get an actual answer to my question instead of rhetorical sighs (and downvotes). Note: I am not a native English speaker.
Re:Things you should do now (2011) by adrianN on Friday February 19, 2021 @05:34AM (#26191568)
This topic is pretty close to flamebait so it gets downvoted would be my guess.
Re:Things you should do now (2011) by corty on Friday February 19, 2021 @05:47AM (#26191666)
Yes, but why? How? I'm a non-native-speaker as well, and these things might be obvious to you, but they aren't to me. Is it a "should not use it", "must not use it", "maybe" or "it's fashionable"? How bad would it be if I accidentially use it, more like a four-letter-word or more like "well, he's a foreigner, he doesn't know"?
Re:Things you should do now (2011) by unethical_ban on Friday February 19, 2021 @10:44AM (#26194314)
I'm the opposite of the other person: Use the known terms until someone complains. Very few people have a problem with `blacklist` just like very few people had a problem with `master` branch.
Re:Things you should do now (2011) by thomasahle on Friday February 19, 2021 @06:06AM (#26191792)
That's the problem with flamewars. You can't really recommend in any direction without baiting the flames. You'll just have to look for previous discussions and decide for yourself.
Re:Things you should do now (2011) by circlefavshape on Friday February 19, 2021 @09:46AM (#26193669)
It totally depends on context and the culture of the people you are communicating with. Safest option is not to use it
Re:Things you should do now (2011) by coldtea on Friday February 19, 2021 @09:08PM (#26200800)
Not very safe either, since then you impose an american preoccupation based on their history and modern politics to the rest of the world...
Re:Things you should do now (2011) by throwaway525142 on Friday February 19, 2021 @06:02AM (#26191775)
Re:Things you should do now (2011) by coldtea on Friday February 19, 2021 @09:07PM (#26200796)
>What? Did I miss a memo or something?

Yes, there was never some contract that we all signed or some thing some majority of us formally voted that says "we're not supposed to call it a blacklist/whitelist anymore.

Just what some random groups decided and enforced at their own domains (companies, orgs, etc.).

It's also based on an American preoccupation with race issues, seeing everything through it's own guilt-ridden history, concerns not relevant to other parts of the world (where code is written and English is also spoken, as first or second language for IT).

The connotations of black/white s terms have nothing to do with slavery or blacks, the term blacklist was first used (recorded) in an English theater play, as the list of the enemies of the kind (black alluding to shady, dark motives, etc, not to skin color), and its common colloquial use in the 20th century was also not about blacks or had anything to do with slavery: it was the list where employees put union members, strikers, etc not to hire.

It's better for people in the US to concentrate on fixing actual racial issues (from incarceration rates and cop shootings, to school funding, redlining and loan access) than to play with words to pat itself in the back.

People all over the world have used black/white to certain things (sometimes the inverse too, e.g. in some asian cultures white is associated with death), and it has nothing to do with the US practicing slavery, seggregation, and racism to blacks.

We use those terms with some connotations for centuries before blacks were sold as slaves to pick your cotton, even at times when slaves where whites working for other whites (as in Ancient Persia, Greece, the Roman Empire, feudal times, and so on).