-
Notifications
You must be signed in to change notification settings - Fork 1.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
App allows slurs in the usernames #1008
Comments
There's no reason the PDS and client can't have a ban list of words for usernames. It's not perfect but it's something. |
To any of the devs who might read this, where exactly does this code live concerning content moderation so the community could take a go at it? Bluesky, although it's an "open beta" has expanded to a very sizable community of users with understandable moderation demands, of they could just have some hardcoded validations for at least the flagship instance like arrays of profanity for the major languages spoken across the main Bluesky instance that could be a step forward in positive user experiences. |
Not a dev, but the roadmap for federation relies on the concept of custom moderation services. These services will label posts, and people will be able to subscribe to these services, (similar to custom feeds) and decide for themselves what content they want to hide. The source code for this is not readily available to my knowledge. |
The code has been updated through team and community contributions to handle these issues. For reference, see:
Please let me know if there are any remaining issues but I believe these cover it. |
Describe the bug
A user with a racial slur in their username has been allowed on the platform. This is not the first time it has happened
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Blocked. Even for custom URLs it should be blocked.
Details
Additional context
You have aggressive AI filters that mark women's bodies as lewd and NSFW, but you don't do the same for racial slurs? This is a huge oversight.
The text was updated successfully, but these errors were encountered: