Bluesky now checks against this array of slurs when creating a username
1–10 of 98 posts
Re: Bluesky now checks against this array of slurs when creating a username
#2Context: 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.
Re: Bluesky now checks against this array of slurs when creating a username
#3Add this to the list of "running a social network is hard" issues
Re: Bluesky now checks against this array of slurs when creating a username
#4S*yb*y is now a slur on the same level as racial slurs now?
Re: Bluesky now checks against this array of slurs when creating a username
#5[flagged]
Re: Bluesky now checks against this array of slurs when creating a username
#6Surprised they didn't do it sooner... this is like step 1 of automated moderation. If you've got an input, someone will put a slur in it.
Re: Bluesky now checks against this array of slurs when creating a username
#7S*yb*y is now a slur on the same level as racial slurs now?
No one has said that they are on the same level?
Re: Bluesky now checks against this array of slurs when creating a username
#8Hopefully they can avoid the Scunthorpe problem.
Re: Bluesky now checks against this array of slurs when creating a username
#9S*yb*y is now a slur on the same level as racial slurs now?
I don’t know why an array in source code would imply an ordering to you; it’s much more likely the author just picked a a list online.
Note that this list also contains several terms that are either reappropriations or contextual uses, and only applies to usernames. This is more or less what any social media network of a nontrivial size does.
Re: Bluesky now checks against this array of slurs when creating a username
#10> "gyp",
There goes the GYP project handle[0]. At least GNU Gimp is still safe :)