-
Notifications
You must be signed in to change notification settings - Fork 218
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
Add a page explaining the sensitive content filtering approaches #2550
Comments
I'll handle the copywriting aspect of this page! |
Here is my early draft of this text: https://docs.google.com/document/d/1gZ8blFT96cMyMomHuPUS-_LqK9v9GRCChG0Y9b6-EBQ/edit?usp=sharing Please note that this is a VERY rough draft and is in no way a concrete representation of the final form of this documentation. Please share feedback here. I've added individual maintainers as editors to the document. |
@sarayourfriend should we mark this as blocked because we are awaiting input from another team for the final text? |
Yes, good call. For posterity, we're blocked waiting for a review from legal advisors to confirm the text is copacetic. |
I believe we've got confirmation on the wording and can move ahead with converting this into a page on our frontend! |
Problem
The content safety wall #2462 shows different text based on different values of the
sensitivity
field provided by the API #2549.Description
These differences in text can be subtle and may not immediately make clear to the user why a particular media has been flagged as sensitive. It would be helpful to have a page explaining the different factors considering when flagging a media item.
Essentially it would be mapping of keys in the
sensitivity
field in the API response to explanatory text that can be linked to from the content safety wall if the user needs more information about our process.The text was updated successfully, but these errors were encountered: