88
Bluesky CEO responds | 2023-07-22 Letter to the Community
(blueskyweb.xyz)
A nice place to discuss rumors, happenings, innovations, and challenges in the technology sphere. We also welcome discussions on the intersections of technology and society. If it’s technological news or discussion of technology, it probably belongs here.
Remember the overriding ethos on Beehaw: Be(e) Nice. Each user you encounter here is a person, and should be treated with kindness (even if they’re wrong, or use a Linux distro you don’t like). Personal attacks will not be tolerated.
Subcommunities on Beehaw:
This community's icon was made by Aaron Schneider, under the CC-BY-NC-SA 4.0 license.
On one hand they definitely should have been aware about the possibility of abuse like this, especially since so many of them came from Twitter but on the other hand I've always thought that it was asking a lot to have to have developers be exposed and put in a list of slurs specifically to be able to block them out. :(
They probably don't have a list of slurs as much as they use partial variations in Regular Expressions for filtering, which I guess could be better or worse, depending on how you look at it. Better: they don't have to see the whole slur. Worse: they have to think deeply about the slur and all the variations of it that might arise.
As they mentioned in the blog post though, simply matching slurs inside of a string will ban a lot of innocent people
It's the Scunthorpe problem.
yeah wordlists for any kind of moderation can easily catch false positives
I remember some post where someone's username Nasser got censored to N***er making it look way fucking worse. One of the Dark Souls games.