Live data from Hacker News

Bluesky now checks against this array of slurs when creating a username

github.com

71–80 of 98 posts

Re: Bluesky now checks against this array of slurs when creating a username

#71

They are missing the T word, the F word, the D word, the S word, and the M word. Now obviously only some of those are racial slurs but I think keeping this in the code base rather than a database is definitely asking for issues

Tesla, Ford, Daihatsu, Suzuki, Mitsubishi?

Re: Bluesky now checks against this array of slurs when creating a username

#72
post #71

They are missing the T word, the F word, the D word, the S word, and the M word. Now obviously only some of those are racial slurs but I think keeping this in the code base rather than a database is definitely asking for issues

Tesla, Ford, Daihatsu, Suzuki, Mitsubishi?

tranny, faggot, dick, slut, motherfucker

mind you, I only condone usage of the 3rd and 5th.

Re: Bluesky now checks against this array of slurs when creating a username

#73
post #50

Earlier quoted context omitted.

> Yes, but they're currently prefederation (can't run your own instance yet) What's stopping you?

You actually can now, but it's still in "sandbox" stage. https://atproto.com/blog/federation-developer-sandbox

So you could take their code, tell them to screw off, and run your own instances independently of them?

Re: Bluesky now checks against this array of slurs when creating a username

#74
post #41

R.I.P. my sauerkraut fan club Let me be the first to bring Jung into this, "What you resist, persists", in trying to avoid the usage of slurs, you had to go and commit them to a public branch of source code to be saved in the arctic vault for eternity.

Funny enough I went to a Krautrock mini-festival a few weeks ago, here in Germany. Nobody I know cares about the term "kraut". At this point it is just outdated WW2 lingo that never caught on here. I feel like "Kartoffel" is often used in a more offensive way. Although I've never really seen someone getting really offended.

Funny, I’ve heard potet in Norway as well. Is this a common slur in Germanic countries?

Re: Bluesky now checks against this array of slurs when creating a username

#75
post #44

> add more words that should be cought I hope they have fewer typos in their slur list than in their code comments :) I started reading the list from the bottom up, and saw the N word written with a W a first letter. I first thought they were going to do a .replace("W", "N") to avoid spelling the word in plain text. They'll have issues once github bans slurs from source code! ;)

It's not a typo. Google it. It's a derogatory term for white people who adopt black culture and mannerisms.

I think they mean cought vs caught

Re: Bluesky now checks against this array of slurs when creating a username

#77

Earlier quoted context omitted.

They're on the same level insofar as it's been deemed serious enough by someone to put on this list. Just funny to see it on a list filled with ethnic slurs and a couple disability slurs, looks very out of place to see an extremely-online insult alongside slurs with tons of historical baggage.

Does it really surprise you to see an extremely-online insult being included in a black list for an app for extremely-online people? I genuinely can't understand the confusion.

[deleted]

Re: Bluesky now checks against this array of slurs when creating a username

#78
post #16

Earlier quoted context omitted.

They are literally in the same flat array

That just means that they both meet the same bar. It doesn't follow that they are equally horrible. Murder and tax evasion are both crimes, does that mean they're on the same level?

[flagged]

Re: Bluesky now checks against this array of slurs when creating a username

#79
Isn't a blacklist typically a bad idea for all of the reasons people are listing in the comments (like scunthorpe)? I've never implemented a social media platform, but why would you use a blacklist as opposed to a flagging system with manual moderation (where maybe the flagged user gets sent to a quarantine where they're shadow banned until approval)? That way, as language evolves and new slurs are made, or somebody tries to circumvent the system, you can just manually ban that user. Is there a technical reason this is a bad idea?

Re: Bluesky now checks against this array of slurs when creating a username

#80
post #10

> "gyp", There goes the GYP project handle[0]. At least GNU Gimp is still safe :) [0] https://gyp.gsrc.io/

[flagged]

I've never heard of "Gyp" in my whole life and have no idea what it means.

Also, there are a lot more languages than English. Do you want to ban all acronyms that sound like a slur in one of them?

Post reply on HN