identifier: tweaks and additions to slur list #1319
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -1047,30 +1047,29 @@ const famousAccounts = [ | |
| 'zerohora', | ||
| ] | ||
|
|
||
| // naive, incomplete list of slurs and unacceptable words | ||
| const slurs = [ | ||
| 'bluegum', | ||
| 'chink', | ||
| 'chinks', | ||
| 'coolie', | ||
| 'coolies', | ||
| 'coon', | ||
| 'coons', | ||
| 'coont', | ||
| 'golliwog', | ||
| 'golliwogs', | ||
| 'gook', | ||
| 'gooks', | ||
| 'gyp', | ||
| 'gyps', | ||
| 'half-breed', | ||
| 'halfbreed', | ||
| 'half-breeds', | ||
| 'halfbreeds', | ||
| 'heeb', | ||
| 'heebs', | ||
| 'hitler', | ||
| 'kaffer', | ||
| 'kaffers', | ||
| 'kaffir', | ||
|
|
@@ -1081,53 +1080,54 @@ const slurs = [ | |
| 'kafirs', | ||
| 'kike', | ||
| 'kikes', | ||
| 'kkk', | ||
| 'klukluxklan', | ||
| 'muzzie', | ||
| 'n1gga', | ||
| 'n1gger', | ||
| 'nazi ', | ||
|
There was a problem hiding this comment. Trailing space here appears incorrect. |
||
| 'negorid', | ||
|
There was a problem hiding this comment. This looks like a typo. Shouldn't it be |
||
| 'negress', | ||
| 'nig', | ||
| 'nigg3r', | ||
| 'nigg4h', | ||
| 'nigga', | ||
| 'niggah', | ||
| 'niggas', | ||
| 'niggaz', | ||
| 'nigger', | ||
| 'niggerachi', | ||
| 'niggerette', | ||
| 'niggerican', | ||
| 'niggerino', | ||
| 'niggeroid', | ||
| 'niggers', | ||
| 'nigglet', | ||
| 'nigguh', | ||
| 'nigguhs', | ||
| 'nig-nog', | ||
| 'nig-nogs', | ||
| 'nigs', | ||
| 'paki', | ||
| 'pakis', | ||
| 'pedophile', | ||
| 'pickaninnie', | ||
| 'pickaninnies', | ||
| 'pickaninny', | ||
| 'pickaninnys', | ||
| 'raghead', | ||
| 'ragheads', | ||
|
There was a problem hiding this comment. Remind me why this needs to be removed from the list? Isn't this abelist language? There was a problem hiding this comment. As @mackuba is saying, and as a speaker of 4 Latin languages, I have to agree that doesn't make sense to just blacklist some of these words because they are of common use (no pejorative) and we should find more sophisticated ways of moderation and avoid hate. Further explanation here: There was a problem hiding this comment. I disagree strongly. Having the ability to use this word in usernames is not worth the tradeoff of making others feel unwelcome. I’d like this to be a community that prioritizes psychological safety, especially when there are other ways to say “delay” in multiple languages. There was a problem hiding this comment. So, that totally explains why some of the other words are being removed too... /s I'm sure there are other uses of the word, but it's most known use is as an ableist slur. Remind me again why you're making this a hill to die on, fighting so hard for the use of a word to mean delay or slow down? Who's going to be hurt by the removal of this word? (No one). Who will be hurt by the USE of this word? (Lots of folks) There was a problem hiding this comment. nod I can ALMOST guarantee that no one that works in this space ever feels like it's a solved problem. Ever. At least those that choose to work in the space rather than being voluntold to. :) And I recognize, particularly the edge case negro for example, brings with it complications around common usage in Spanish. The decision points I'm seeing here are likely: 1) What's the moderation cost to handle the edge case, 2) How many users will be upset by not being able to use "Black" in Spanish in their username, 3) How many people will be offended by seeing "negro" pop up in their feeds? They could likely do some user studies to test this theory. I will say, from my perspective the BEST way to test this theory while also creating a safe environment for as many users as they can, is to do what they're doing, and ban far and wide. Be as inclusive of any words you can find in as broad a swath as possible across all languages. Go how far you think you should go, then go farther. When folks start chiming in "WTF?! Why did you ban xxxx?!" you can start to have some decent data around the impact because it's super explicit. It's much harder to get data the other way (not impossible certainly). But like, a user that leaves the platform (or just doesn't engage but doesn't leave) because they were tired of seeing slurs in usernames is harder to capture (unless you ask specifically in some kind of exit poll, but even then it's not likely you'll get large engagement because the person is already done with the platform). Paramount is creating a safe space. In ALL languages. When you've gone too far and are at panic room level lockdown, you can ALWAYS back off and consider those edge cases at the other end once you've established some data around just how folks feel. But if your space isn't safe, you'll never find out cause folks aren't engaged with the platform. There was a problem hiding this comment. These are very interesting points and arguments to consider @GabeWeiss. I will think about them. Thank you very much for taking your time to explain and sharing your takes! There was a problem hiding this comment. @ferranrego of course! Right back at ya. Glad it stayed civil. :D There was a problem hiding this comment. I'm not arguing that you can't use that word in your own language. I'll sideline "negro" for a bit, because I realize that it means "black" in Spanish. "Retard" on the other hand is very offensive and has very little use outside of some edge cases that you mentioned. Again, how many businesses are hurt because they can't use "retard" in their username? I'd argue very few. Yet, because it is allowed, we have "Capt Retard" as a username now. I find it very telling that your argument to have the freedom to use your language as you wish negates my need to not be called a "retard". I'm not sitting over here telling you that English is superior or that we should consider English swear words above other use cases. What you bring to the table, specifically for "retard" is a rare case, where it's easily abused. Beyond that, there are other words I'd rather not type here that have been removed that have ZERO use case outside of being a slur. Outside of the word "negro", I don't see any reason why any of the words that have been removed (especially "retard") have any clear and common use case in any language. You're taking a one-off situation and holding it up as the standard, claiming that I'm being English-superior, which I am not. I'm just saying that your use of certain words as an edge case does not negate my need for not being called a version of stupid that implies that people with intellectual disabilities should be killed. I know you don't like this being a good/bad case, but I'd rather not have people imply certain things in their usernames, which I think is more important that someone's "freedom" to use a certain word. There was a problem hiding this comment. I understand the linguistic perspectives in this discussion. It's always been the case that a slur in one language may be a colloquial use in another. But at the end of the day:
To put it simple - you don't know, and you can't know the full harmful effects caused by the word. You are not an expert. No matter how much you try to justify that you are. You cannot possibly make an informed decision.
|
||
| 'redskin', | ||
| 'sambo', | ||
| 'sambos', | ||
| 'spade', | ||
| 'spades', | ||
| 'spic', | ||
| 'spics', | ||
| 'squaw', | ||
| 'squaws', | ||
| 'wetback', | ||
| 'wetbacks', | ||
| 'yid', | ||
| 'yids', | ||
| ] | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
...hate to spam up this already heavily traffic'd commit, but why were these removed?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also / on the same note 「 jap 」 and 「 japs 」
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
reverted in
#1332#1333There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, #1333 was closed without being merged. I don't think we'll ever know the reason why this removal was made.