Live data from Hacker News

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

github.com

41–50 of 98 posts

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

#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.

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

#43
post #2

Context: Yesterday a user created a Bluesky account using the N-word as their handle and, unsurprisingly, people were not happy and there was clamor for the Bluesky dev team to add a filter at the account creation level.

My only surprise is that it took this long

[flagged]

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

#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! ;)

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

#45

Earlier quoted context omitted.

The name was so popular in Italy it ended up becoming a “slur” (though personally the only time I’ve ever heard someone called Guido is when that was their name). I wonder if that will ever happen with other languages and their common names, I’m Russian so I immediately think of “Sergey” as one of our ultra common names.

It's not a slur exactly, but in the United States, "Ivan" is a common name used to refer (usually dismissively) to Russians.

I've heard the same thing happen with Mohammed

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

#46

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.

R.I.P. my friend Tito

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

#47
post #29

I think that the reappropriation of slurs, like yankee, whig, tory, queer, etc., is a positive thing. But this practice serves to lock them in place, helping to insure that they remain slurs. https://en.wikipedia.org/wiki/Reappropriation

This is proof that vampires are real and they walk among us. You need to prune slurs more than two centuries old. Otherwise the mortals will catch on to you.

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

#50

Forgive my naïveté but isn’t bluesky open source and decentralized? So wouldn’t say some group just spin up an instance without these restrictions?

Yes, but they're currently prefederation (can't run your own instance yet ) and still making architectural decisions about how moderation will work. they're balancing onboarding new users with keeping up with high expectations of their current userbase. I'm not sure how the federation story compares with mastadon, I've mostly heard talk of composite block lists (everyone you block is public on bluesky so you could ha…

> Yes, but they're currently prefederation (can't run your own instance yet)

What's stopping you?

Post reply on HN