Rozšíření:ORES

This page is a translated version of the page Extension:ORES and the translation is 19% complete.
Základní informace k tomuto rozšíření MediaWiki
OOjs UI icon advanced-invert.svg
ORES
Stav rozšíření: stabilní
ORES extension screenshot.png
Popis Toto rozšíření integruje data z projektu ORES do zobrazení RecentChanges.
Napsal(i) Kunal Mehta, Amir Sarabadani, Adam Roses Wight
MediaWiki >= 1.37.0
Změny v databázi dělá
Tabulky ores_classification
ores_model
Licence GNU General Public License 3.0 nebo pozdější
Zdrojový kód
  • $wgOresBaseUrl
  • $wgOresFrontendBaseUrl
  • $wgOresCacheVersion
  • $wgOresAggregatedModels
  • $wgOresWikiId
  • $wgOresEnabledNamespaces
  • $wgOresRevisionsPerBatch
  • $wgOresExcludeBots
  • $wgOresFiltersThresholds
  • $wgOresModelClasses
  • $wgOresUiEnabled
  • $wgOresModels
Quarterly downloads 26 (Ranked 150th)
Přeložte rozšíření ORES, používá-li lokalizaci z translatewiki.net
Vagrant role ores
Problémy Otevřené úkoly · Nahlásit chybu

Rozšíření ORES integruje data ze služby ORES do zobrazení RecentChanges.

Currently, the ORES backend service is only set up for Wikimedia wikis, and significant work would be required to set it up for third-party MediaWiki installations.

Changes that "need review" and may be damaging are highlighted in Special:RecentChanges.
A "needs review" flag is added to the Special:RecentChanges legend.

Installation

  • Stáhněte soubor/y a vložte je do adresáře pojmenovaného ORES ve vaší složce extensions/.
  • Následující kód přidejte na konec vašeho souboru LocalSettings.php :
    wfLoadExtension( 'ORES' );
    
  • Yes Dokončeno – Přejděte na stránku Special:Version vaší wiki a zkontrolujte, zda bylo rozšíření úspěšně nainstalováno.

You need to run CheckModelVersions.php maintenance script once it's deployed (and after that you can run PopulateDatabase.php too)

Config variables

Here's the config variables and their default values and a little description about them.

// URL of the service
$wgOresBaseUrl = 'https://ores.wikimedia.org/';
// Either to exclude edits made by bot to score
$wgOresExcludeBots = true;
// Models to score
$wgOresModels = [
    'damaging' => [ 'enabled' => true ],
    'goodfaith' => [ 'enabled' => true ],
    'reverted' => [ 'enabled' => true ],
    'wp10' => [ 'enabled' => true ],
];
// Thresholds of different sensitivies in ORES
$wgOresDamagingThresholds = [ 'soft' => 0.7, 'hard' => 0.5 ];
// Namespaces the ORES should score. Empty array means all namespaces.
// If not empty, it will only works on the given namespaces.
// Determine namespaces like [ 0 => true, 120 => true ].
$wgOresEnabledNamespaces = [];
// Database id for ORES service. If not determined, it'll use database name.
// You can choose 'testwiki' that ORES service sends last two digits of rev_id flipped.
// For example: https://ores.wikimedia.org/v1/scores/testwiki/damaging/12345
$wgOresWikiId = null;

ORES service responses

ORES extension is merely more than an interface to the ORES service. The service returns a probability score of edits being damaging like this (API v1):

{
  "724030089": {
    "damaging": {
      "prediction": false,
      "probability": {
        "false": 0.8917716518085119,
        "true": 0.10822834819148802
      }
    }
  }
}

It means this edit (diff=724030089) is 10% likely to have caused damage. Note that 90% likely doesn't mean 9 out of ten cases will be vandalism. Choosing thresholds should be done via analysing recall (percentage of vandalism it can catch) or false positive rate. In ORES the "soft" threshold is when recall is 75% (meaning it will include 75% of all damaging edits) and the "hard" threshold is when recall is 90%. You can get the thresholds from model info (an example).

Database schema

ORES extension introduces two new tables: ores_model and ores_classification. See the full database schema description.


Extension workflow

Scores

Once an edit is made the extension triggers a job to hit the service and store the results in the ores_classification table. It means it will not include scores for edits made before the deployment. In order to fill the database you can run the maintenance script PopulateDatabase.php. It will hits the service and keeps the score for the last 5,000 edits. You can run it several times if needed.

Once a model gets updated to a newer version CheckModelVersions.php maintenance script needs to be ran to update the ores_model table which will cause to scores stored in the ores_classification table become deprecated. You can clean these obsolete scores by running PurgeScoreCache.php maintenance script.

Interface

The extension won't show anything when deployed but it will add itself as a beta feature (Rozšíření:BetaFeatures is a dependency of this extension) and once it's enabled by the user it will use hooks in ChangesList (RecentChanges, Watchlist, and RelatedChanges) in both old and enhanced mode and highlights when score exceeds the given threshold.