Per {T158225}, the ORES extensions should be able to be configured such that:
- It does not add a beta feature-- ORES is on by default.
- The "Hide probably bad edits" filter is available to everyone, regardless of preference, though it is implemented in a new way on RC page and has a new name (see below)
- The "r" flags on RC are visible to everyone
- Highlighting rows based on damaging-ness--aka "Classic ORES"— IS NOT AVAILABLE TO RC PAGE USERS. On Watchlist, it is put behind a new preference (see below).
==Preferences stuff that needs to be handled
- **Hide probably good edits from recent changes** This Recent Changes option currently appears only after users have selected the ORES beta, and is unselected by default.
- It will now become a standard option for everyone--though it is still UNSELECTED by default
- If it was selected by existing ORES users or is selected by new users, then on the RC page, activate the following filter and display it as a default in the Active Filter Display Area: May have problems.
- Meanwhile, re-word the preference to align it with the new functionality, like so: "Show only edits that may have problems (and hide probably good edits)."
- (The "Hide probably good edits from Watchlist" preference remains where it is—on the Watchlist—and continues to do what it does there.)
- **Highlight probably damaging edits on Watchlist and Contributions (using ORES) **Add this __new Preference__ to the Watchlist prefs in the "Revision Scoring" section. It turns on classic ORES shading on Watchlist and Contributions.
- For existing ORES users, this will be turned on by default when they are migrated.
- For everyone else, this preference will be off by default.
- It's expected that as we move more pages to the new interface, this preference will control fewer and fewer pages. One day, we'd like to replace "classic" ORES entirely.This preference in no way should be read as committing to supporting this.
- **Ores Sensitivity** The existing subsidiary preference for ORES Sensitivity will be grouped with the new "Highlight probably damaging edits" preference, because it depends on it. It is subsidiary.
- It will continue doing whatever it does now, but not for Recent Changes.