Extension:AbuseFilter/Actions/es

Visión general
AbuseFilter puede tomar varias acciones, incluso más de una a la vez. "Registrar" y "etiquetar" son las más suaves y no impedirán que se guarde la edición. "Limitar" y "advertir" son acciones especiales, las cuales no hacen mucho por sí solas: la primera solo aumenta silenciosamente un contador interno, mientras que la segunda advierte al usuario de lo que va a hacer, permitiéndole modificar la edición según el texto de la advertencia (o abstenerse de guardar la edición del todo). "No permitir" es, en cambio, una acción más fuerte y evita por completo que se guarde la edición. Las otras acciones, es decir, "bloquear la recepción de permisos obtenidos automáticamente", "bloquear", "eliminar de los grupos" y "bloqueo por intervalo", son incluso más fuertes y cada una de ellas evita que la edición se guarde y aplica una acción específica sobre el usuario.

Algunas de estas acciones (específicamente bloquear, eliminar de los grupos y bloquear la recepción de permisos obtenidos automáticamente) pueden ser revertidas por usuarios con el permiso abusefilter-revert. It allows users to access the /revert subpage, where they can specify a time period and get a list of revertable actions performed by a specified filter. By confirming the revert, all of these actions will be undone. The form for reverting actions taken by a filter can be accessed with a link found in every filter page, right below the one for accessing the history.

List of actions
The following actions are available in the AbuseFilter extension:

Logging
All filter matches are logged in the abuse log. This cannot be turned off.

Warning
The user is warned that their edit may not be appreciated, and is given the opportunity to submit it again. You may specify a specific system message containing the warning to display.

Throttling
The filter will only match if a rate limit is tripped. You can specify the number of actions to allow (a positive integer), the period of time in which these actions must occur (a positive integer), and how those actions are grouped (at least one criterion from the list below, lowercase).

The groupings are which sets of people should have aggregate (shared) throttles. That is, if you type, then the same user must match the filter a certain number of times in a certain period of time. You may also combine groups with commas to specify that throttle matches sharing all criteria will be aggregated. For example, using, X filter matches in Y seconds from the same IP address to the same page will be required to trip the remainder of the actions.

Here is the full list of available groups:


 * – IP address.
 * – User account.
 * – /16 range.
 * – User account creation date, server time.
 * – Edit count &mdash; hack so that you can detect distinct users.
 * – The whole site.
 * – Página

Disallowing
Actions matching the filter will be prevented, and a descriptive error message will be shown.

Revoking auto-promoted groups
Actions matching the filter will cause the user in question to be barred from receiving any extra groups from  for 5 days. This can be restored at the debug tools page.

Blocking
Users matching the filter will be blocked for the time specified, with a descriptive block summary indicating the rule that was triggered.

Removing from privileged groups
Users matching the filter will be removed from all privileged groups (sysop, bureaucrat, etc). A descriptive summary will be used, detailing the rule that was triggered.

Range-blocking
Somewhat of a "nuclear option", the entire  range from which the rule was triggered will be blocked for 1 week.

Tagging
The edit or change can be 'tagged' with a particular tag, which will be shown on Recent Changes, contributions, logs, new pages, history, and everywhere else. These tags are styleable, so you can have items with a certain tag appear in a different colour or similar.