Bluesky, a decentralized social network, allowed users to register usernames containing the n-word. When reports surfaced about a user with the racial slur in their name, Bluesky took 40 minutes to remove the account but did not publicly apologize. A LinkedIn post criticized Bluesky for failing to filter offensive terms from the start and for not addressing its anti-blackness problem. Bluesky later claimed it had invested in moderation systems but the oversight highlighted ongoing issues considering Twitter co-founder Jack Dorsey backs the startup. The fact that Bluesky allowed such an obvious racial slur shows it was unprepared to moderate a social network effectively.
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.
In 40 minutes or less?
According to BlueSky’s own timeline - the original account was deleted 18 days after it was created. They were quick to react once they knew about it, but they took too long to find it.
That was also followed by almost two weeks of activity without clearly making any statement about what was going on. Better late than never but this “Letter to the Community” should have been written over a week ago.
As for how long it should take to take an account offline on Lemmy - personally I’d like to see some kind of karma based system. If an active account that’s been around for years is flagged… maybe ignore that unless there are multiple flags. But if a brand new account or an old account that hasn’t been very active is flagged, kill it instantly and flag it to be investigated (and potentially restored).
Depends on the size of your instance, but it could happen.