-
Notifications
You must be signed in to change notification settings - Fork 0
Open
Description
A clear and concise description of what you want to happen:
- Implement a profanity filter to prevent the use of offensive language within the StudyWeave application.
- The filter should be applied to:
- User-generated content (e.g., flashcards, user profiles, comments).
- Any user input fields.
Describe alternatives you've considered:
- Manual moderation: Relying on human moderators to review and remove offensive content.
- Pros: High accuracy in identifying and removing offensive content.
- Cons: Time-consuming and resource-intensive. Can lead to delays in content moderation.
- User flagging system: Allowing users to flag offensive content, which is then reviewed by moderators.
- Pros: Efficiently identifies potentially offensive content.
- Cons: Relies on user vigilance and may not catch all instances of offensive language.
Additional context:
- Consider using a pre-existing profanity filter library or API for efficient and accurate filtering.
- The filter should be configurable to allow for adjustments to the sensitivity level.
- Provide clear feedback to users when their input is flagged as containing offensive language.
- Consider implementing a system for users to appeal flagged content if they believe it was incorrectly flagged.
Metadata
Metadata
Assignees
Labels
No labels
Projects
Status
Backlog