There's one thing that's very clear from reading through ORES' mistake reports online: People want to include freetext comments with their judgements.
However, there's a problem where any time you open up a new freetext field on the internet, someone's going to use it to Dox someone else or otherwise cause harm. So we're going to need some mechanism for curation and suppression. There are two options we're kicking around.
First class suppression support
Text fields would be stored within JADE and a full suite of suppression tools would be made available. Integrations with MediaWiki would allow patrollers to see JADE comments appear in the RecentChanges feed on their local wiki.
- Text is part of the system and any analysis users will want to do.
- Way more work to implement and easy to get wrong.
Outsource to Flow
Flow already integrates with MediaWiki's RecentChanges feed and has the capacity for suppression events. If we store freetext comments in a Flow post, then we don't need to re-implement the same suppression mechanisms that Flow already has.
- Much easier to implement
- Analyses will need to join to flow tables (??) to search text comments. A flow post is also a little overboard for our goals.