Extension:AbuseFilter/gl

O AbuseFilter a extensión deixa privileged usuarios para pór accións específicas para ser tomado cando accións por usuarios, como edita, partido criterios seguros.

Por exemplo, un filtro podería ser creado para evitar usuarios anónimos desde engadir ligazóns externas, ou para bloquear un usuario que tira máis que 2000 caracteres.

Dereitos do usuario
Unha vez instalada a extensión, terá que configurar os dereitos de usuario en "LocalSettings.php".

Por exemplo, a seguinte configuración de exemplo permitiría ós administradores facer todo o que quixeran co AbuseFilter, e a todos ver o rexistro e a configuración pública do filtro:

Parameters

 * Emergency throttling

AbuseFilter comes with a feature that automatically throttles (disable) filters that have been edited recently and match a certain theresold of the latest actions.

This is done to prevent harmful edits on the filters to block every user that performs an action on the wiki or similar.

The condition to disable the filter depend on those variables:
 * - Percent of matches over the total amount of actions in the observed period.
 * - Count of matches of the filter in the observed period.
 * - Age of the filter to take it into account. If the last edit of the filter is older than this number of seconds, the filter won't be throttled, unless it's already throttled.
 * - Maximum number of recent actions to count against the threshold. Note that each action increments a counter, and once this counter reaches this configured value, this counter and the number of recent actions that matches all filters are reset to 0.

Throttled filters can be identified in the list of filters (Special:AbuseFilter) with the state,. Throttling happens silently, and there's no way to see when a filter got throttled.

When a filter gets throttled, it doesn't perform any dangerous action (the ones specified in ), and only "safe" actions are allowed. Throttled filters don't get enabled automatically. To disable the throttling, you need to edit the filter. Note that you need to actually change something from the filter: changing somethin from the filter's notes is sufficient.

Note that editing the filter updates its age, and can cause it to be disabled if it reaches again the conditions to be throttled in a short period since the last edit, leading to a unusable filter if your wiki has more abuse edits than legitimate ones. Filters can also get randomly throttled if the action count reaches, causing all filter matches count to reset to 0, and then someone repeatedly makes a filter to hit.

Creando e xestionando filtros
Unha vez instalada a extensión, os filtros poden ser creados/probados/cambiados/borrados e pode accederse ós rexistros desde a páxina de xestión de filtros de abuso Special:AbuseFilter.


 * Formato de regras - O basics de como para escribir un filtro
 * Accións
 * Regras globais
 * Guía para optimizar o uso límite da condición
 * Para importar filtros de Wikipedia: cando teña instalada a extensión, acceda a: w:Special:AbuseFilter, seleccione un filtro (por exemplo, w:Special:AbuseFilter/3), logo prema en "Exportar este filtro a outra wiki", copie o texto, acceda a: "Special:AbuseFilter/import" na súa wiki, e pegue o texto.

API
O filtro antiabuso engade dous módulos API, un para detalles dos filtros antiabuso ("abuseFilter") e outro para o rexistro de abuso, posto que é independiente doutros rexistros MediaWiki ("AbuseLog"). Non é posible crear ou modificar os filtros antiabusos usando a API.

list = abusefilters
Lista de información sobre os filtros


 * ;Parámetros
 * : O identificador de filtro desde onde iniciar a enumeración
 * : O identificador de filtro onde deter a enumeración
 * : A dirección na que se enumera (máis vello, máis novos)
 * : Mostrar só os filtros que cumpran con este criterio (habilitado|!habilitado|borrado|!borrado|privado|!privado)
 * : Número máximo de filtros a listar
 * : Propiedades mostrar (id|descrición|patrón|accións|hits|comentarios|último editor|data da última modificación|estado|privado) :
 * - The filter id to start enumerating from
 * - The filter id to stop enumerating at
 * - The direction in which to enumerate (older, newer)
 * - Show only filters which meet these criteria (enabled|!enabled|deleted|!deleted|private|!private)
 * - The maximum number of filters to list
 * - Which properties to get (id|description|pattern|actions|hits|comments|lasteditor|lastedittime|status|private)

Cando os filtros son privados, algunha sdas propiedades especificadas con  faltarán a menos que vostede teña os dereitos de usuario axeitados.


 * ;Exemplos :

list = abuselog
Lista de casos onde as accións activan un filtro abuso


 * ;Parámetros
 * : A data e hora dende onde comezar a enumeración
 * : A data e hora dende onde rematar a enumeración
 * : A dirección na que se enumera (máis vellos, máis novos)
 * : Mostrar só as entradas onde se intentou a acción por un determinado usuario ou a través da súa IP.
 * : Mostrar só as entradas onde as accións involucran unha páxina dada.
 * : Mostrar só as entradas que activan un filtro cun ID dado
 * : Número máximo de entradas a listar
 * : Propiedades mostrar(ids|usuario|título|acción|resultado|data e hora|detalles) :
 * - The timestamp to start enumerating from
 * - The timestamp to stop enumerating at
 * - The direction in which to enumerate (older, newer)
 * - Show only entries where the action was attempted by a given user or IP address.
 * - Show only entries where the action involved a given page.
 * - Show only entries that triggered a given filter ID
 * - The maximum number of entries to list
 * - Which properties to get (ids|user|title|action|result|timestamp|details)


 * ;Exemplo :

Possible errors

 * Some users might experience that creating new filters or modifying old filters fail and the user just gets redirected to the original page. If the Wiki is using SSL certificates, this error could possibly be because of the value, which might be using "http://" instead of "https://". An indication of this error will be, the browser giving https warning for Special:AbuseFilter pages. (Topic:T23dyyih0ofjada5)

Integration with other extensions
You can integrate AbuseFilter with other extension in various ways.

Adding variables for filtering
It is possible to add new variables, to be used in abuse filters. A list of examples is available. To do that, you should:


 * Add a handler for the AbuseFilter-builder hook. To add a variable, you should use, where   is the name of the variable, and   is the fragment of an i18n key. The full key will be.
 * Add the i18n messages you chose at the previous point.
 * Choose a hook handler where the variable will be computed. Depending on your use case, you could:
 * Implement the AbuseFilter-generateTitleVars hook; this is specifically thought for page-related variables;
 * Implement the AbuseFilter-generateUserVars hook; this is specifically thought for user-related variables;
 * Implement the AbuseFilter-generateStaticVars hook; this is specifically thought for "static" variables, i.e. variables whose value shouldn't depend on the context. This is rarely useful;
 * Implement the AbuseFilterAlterVariables hook; this is a bit more flexible than the other hooks, but it has a downside: your variable will not be available when examining past RecentChanges entries. If you want to implement that feature (and it's recommended to do so), you should use one of the hooks listed above, and use its third parameter.
 * Inside the hook handler, there are two ways to add a variable:
 * The "direct" way is calling . This is ideal only when the value is easy and quick to compute: the value is computed even if no active filter will use it.
 * The "lazy" way is calling . Here, 'method_name' is a (unique) identifier that will be used to compute the variable (it's recommended to prefix it with the name of your extension). To register the method, you should add a handler for the AbuseFilter-computeVariable hook; therein, you should check if the $method passed matches your 'method_name', and if so, compute the variable. Lastly, $params is an array of parameters that you'll need to compute the variable; these are passed to the computeVariable hook handler. For an example of this, you can check out CentralAuth's.

Adding rule groups
You can also add extra rule groups, which can be used to group existing abuse filters. Note that, at the moment, each filter can only be in a single group (T116642). Currently, the only known consumer of this feature is Flow. To do that, you should:
 * Append the name of the group to
 * Add some code to run the filters with your group. Note that AbuseFilter won't do that on its own. To do that, you should construct an  object, passing in the name of your group.

Véxase tamén

 * Varios wikis da WMF onde está activada (e con que configuración)