wow just wow while i can't say i didn't see this one coming but it always amazes me where greed could lead someone
this post was submitted on 01 Jul 2023
1564 points (96.5% liked)
Piracy: ꜱᴀɪʟ ᴛʜᴇ ʜɪɢʜ ꜱᴇᴀꜱ
54500 readers
354 users here now
⚓ Dedicated to the discussion of digital piracy, including ethical problems and legal advancements.
Rules • Full Version
1. Posts must be related to the discussion of digital piracy
2. Don't request invites, trade, sell, or self-promote
3. Don't request or link to specific pirated titles, including DMs
4. Don't submit low-quality posts, be entitled, or harass others
Loot, Pillage, & Plunder
📜 c/Piracy Wiki (Community Edition):
💰 Please help cover server costs.
 |
 |
|---|---|
| Ko-fi | Liberapay |
founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
Yeah, at my company we switched to allow/block listed last year. Whitelisted and blacklisted are verboten
The best reasoning I saw for this change was for clarity for non native English speakers. If you're learning the language "allowlist" is definitely more clear in meaning than "whitelist"
Not really, at least in Spanish we’ve always said “listas blancas/listas negras”.
I don't know what you are talking about.
Even if our dialects (Mexican) didn't have vestigial racism and fake dichotomies, permitir y bloquear is as straight forward as you can get.
IT switched from white/black literally years ago, if your department didn't, you are quite stuck in time.
In Spanish you have https://eslemmy.es/
Sure... But unless you know what either of those terms means, it's just gibberish like ping.
Glad fizzbuzz doesn't fit into the gibberish category
A lot of companies seem to be doing this, personally I think trying to make a connection between race and tech is a bit far fetched. Nobody thinks of race when talking about whitelists and blacklists...
In public repos where these changes are merged in to FOSS projects, they get little resistance too - although I could see concern of a potential backlash if anyone questioned the alleged benefit of such a change.
Imagine if this approach was taken with the (now outdated) IDE interface? Instead of "Primary Master, Primary Slave, Secondary Master, Secondary Slave", there'd maybe be "Primary Primary, Primary Secondary, Secondary Primary, Secondary Secondary" 😵
Hasn't Kubernetes already replaced master-slave with master/manager-worker? Seems like there are plenty of alternatives.
Manager-worker seems classist and problematic /s
That does sound like a very sensible alternative given the context
kill all children
My company has recently started disallowing these words in code. The funny part though is the first few lines of the Jenkins job responsible for checking this stuff proudly states "Waiting for slave node to start checks."
I know it's a minor fix in the jenkinsfile but I chuckle every time I see it.