Community Tech/Trust and Safety tools
This page documents a project the Wikimedia Foundation's Community Tech team has worked on or declined in the past. Technical work on this project is complete.
We invite you to join the discussion on the talk page. You may track this project's progress on T167184.
The Trust and Safety tools project will update two critical tools used by the WMF Support & Safety team: the Legal Takedown tool, and the Child Protection Takedown tool. These were written by James Alexander several years ago, and they're out-of-date. Community Tech will update the tools, and get them into a maintainable state.
Important links[edit]
- lcatools.corp.wikimedia -- James A. will give us access so we can work on the tools
- Note: LCA = Legal Community Advocacy, an old name for Trust and Safety
- Github
- Initial investigation ticket: task T159898
-
LCATools front page -
Legal Takedown tool[edit]
Description[edit]
This is a form to fill out information about a DMCA takedown (both data about the takedown itself, as well as the file or page that is being taken down), and attach a file with additional information as needed.
The form sends data (and the file) to Lumen Database (formerly Chilling Effects) via their API, and receives (for log and sugar case) the Lumen ID/URL.
The tool formats posts for:
- WMFwiki -- provides link to post on WMFWiki and allows copy and paste of the main post
- the User Talk page of the uploader -- also allows you to make the edit directly via MW OAuth in addition to copy/paste
- When the takedown is on Commons, it formats posts for Commons Village pump and the Commons DMCA noticeboard. (It also allows one click posting of those via OAuth in addition to copy/paste).
The tool also creates a SugarCRM case with basic info about the takedown.
A separate sub tool: Tool to only report to Lumen without formatting the posts/creating sugar case (mostly for when the API was down or issues happened).
Changes[edit]
Right now, the tool only tracks the files that are taken down. We also want to track the requests that don't lead to a takedown, so there should be a full log. Some of the fields should not be mandatory, and there should likely be an option added for request granted (image removed) or denied (image kept on Commons.)
We may need this to write to SalesForce instead of Sugar. TBD (Question for Jalexander-WMF: Will we want this to write to SalesForce? Or still sugar?)
Child Protection Takedown tool[edit]
Description[edit]
This is a form to fill out with information about the Child Protection (pornography) takedown with basic step by step (more complete steps are in a larger policy doc), including uploading the image taken down and collecting information about the user.
It uses the National Center for Missing and Exploited Children API to submit image and user data as required by law.
It creates a log entry and Sugar case, including Image Hash and report ID along with report metadata.
There's a Special page: NCMEC retraction tool. This retracts a specific report to NCMEC, and only works if the report wasn't completed, such as a failure in one of the steps of the multi step API submission for NCMEC. There's no "auto-rollback" feature built in at the moment.
Changes[edit]
This tool currently uses Sugar; we'll probably switch to Salesforce.
Currently, we have to do one image at a time; this needs multi-file support.