Change Details

In T352439 we implemented a simple approach to reverting which directly uses the Liftwing API. Ultimately what we're looking for is to be able to get edit scores from the Revert Risk model in the ORES extension so that we can scale better in production and batch our requests. **Acceptance criteria** * If the ORES extension is available, Automoderator should fetch Revert Risk scores from it instead of the Liftwing API.

In T352439 we implemented a simple approach to reverting which directly uses the Liftwing API. Ultimately what we're looking for is to be able to get edit scores from the Revert Risk model in the [[ https://www.mediawiki.org/wiki/Extension:ORES | ORES extension ]] so that we can scale better in production and batch our requests. **Acceptance criteria** Using the ORES extension, Automoderator should fetch Revert Risk scores from it instead of the Liftwing API.

In T352439 we implemented a simple approach to reverting which directly uses the Liftwing API. Ultimately what we're looking for is to be able to get edit scores from the Revert Risk model in the [[ https://www.mediawiki.org/wiki/Extension:ORES | ORES extension ]] so that we can scale better in production and batch our requests. **Acceptance criteria** * IfUsing the ORES extension is available, Automoderator should fetch Revert Risk scores from it instead of the Liftwing API.