Extension:AbuseFilter/es

La extensión AbuseFilter permite a los usuarios que dispongan de los permisos correspondientes establecer acciones específicas que deberán llevarse a cabo cuando un usuario realice una acción, por ejemplo, una edición, que coincida con determinados criterios.

Por ejemplo, podría crearse un filtro para evitar que usuarios anónimos añadan enlaces externos, o para bloquear automáticamente a un usuario que borre más de 2000 caracteres de una página.

Permisos de usuario
Una vez instalada la extensión, tendrás que configurar los permisos de usuario en "LocalSettings.php".

Por ejemplo, la siguiente configuración permitiría a los administradores hacer todo lo que quieran con AbuseFilter, y a todo el mundo ver el registro y la configuración de los filtros:

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 something 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 y administrando filtros
Una vez instalada la extensión, los filtros pueden ser creados/probados/cambiados/borrados y se puede acceder a los registros desde la página administrativa especial que añade la extensión: Especial:FiltroAntiAbusos.


 * Formato de las reglas - Lo básico sobre cómo escribir un filtro
 * Acciones
 * Reglas globales
 * Guía para optimizar el uso límite de la condición
 * Para importar filtros de Wikipedia, una vez que hayas instalado la extensión dirígete a Especial:FiltroAntiAbusos, selecciona un filtro (por ejemplo, Especial:FiltroAntiAbusos/6), haz clic en "Exportar este filtro a otro wiki", copia el texto, vé a "Especial:FiltroAntiAbusos/importar" en tu wiki y pega el texto.

API
AbuseFilter añade dos módulos de lista a la API: uno con los detalles de los filtros antiabuso ("abusefilters"), y otro con el registro de abusos, ya que es independiente de otros registros de MediaWiki ("abuselog"). No es posible crear o modificar los filtros antiabusos usando la API.

list = abusefilters
Listar información acerca de los filtros.


 * ;Parámetros
 * : El ID del filtro desde el que empezar a enumerar
 * : El ID del filtro con el que concluir la enumeración
 * : La dirección en la que enumerar (older, newer)
 * : Mostrar sólo los filtros que cumplan con estos criterios (enabled|!enabled|deleted|!deleted|private|!private)
 * : El número máximo de filtros a listar
 * : Propiedades a obtener (id|description|pattern|actions|hits|comments|lasteditor|lastedittime|status|private) :
 * - 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)

Cuando los filtros sean privados, algunas de las propiedades especificadas con  faltarán, a menos que dispongas de los permisos de usuario adecuados.


 * ;Ejemplos :

list = abuselog
Listar los casos en los que las acciones hicieron saltar un filtro antiabuso.


 * ;Parámetros
 * : Fecha y hora desde la que empezar a enumerar
 * : Fecha y hora en la que detener la enumeración
 * : En qué dirección enumerar (older, newer)
 * : Mostrar sólo los registros donde la acción fue intentada por un determinado usuario o dirección IP
 * : Mostrar sólo los registros donde se veía afectada una página en concreto
 * : Mostrar sólo los registros que hicieron saltar un determinado ID de filtro
 * : Número máximo de registros a listar
 * : Qué propiedades obtener (ids|user|title|action|result|timestamp|details) :
 * - 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)


 * ;Ejemplo :

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. To do that, you should:


 * Add a handler for the 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 hook; this is specifically thought for page-related variables;
 * Implement the hook; this is specifically thought for user-related variables;
 * Implement the 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 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  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éase también

 * Varios wikis de la WMF donde está activada la extensión (y con qué configuración)