Viewing abuse filter 4: Page blanking

Filter parameters

Filter ID:	4
Description: (publicly viewable)
Filter group:
Statistics:	Of the last 422,612 actions, this filter has matched 1 (0%). On average, its run time is 0.49 ms, and it consumes 2.3 conditions of the condition limit.
Conditions: (documentation) (condition usage)	(action = 'edit') & !("autopatrol" in user_rights \| user_editcount >= 200) & (page_namespace == 0 \| page_namespace == 4 \| page_namespace == 6 \| page_namespace == 10 \| page_namespace == 14) & ((new_size < 10 & old_size > 100) \| (new_size == 0 & old_size != 0)) & !("#redirect" in lcase(added_lines)) & !("{{" in added_lines & "}}" in added_lines) & !("Sandbox" in page_title) (action = 'edit') & !("autopatrol" in user_rights \| user_editcount >= 200) & (page_namespace == 0 \| page_namespace == 4 \| page_namespace == 6 \| page_namespace == 10 \| page_namespace == 14) & ((new_size < 10 & old_size > 100) \| (new_size == 0 & old_size != 0)) & !("#redirect" in lcase(added_lines)) & !("{{" in added_lines & "}}" in added_lines) & !("Sandbox" in page_title)
Notes:	Related filters: * filter 14 - for blanking pages in the user/user talk namespaces * filter 42 - for section blanking This filter is for page blankings in the gallery (0), file (6) and category (14) namespace. * Add template namespace (10). --The Evil IP address * Add project namespace (4). --Krinkle Triggered for anyone not autoconfirmed. * Raised to trigger for anyone not a sysop, there's no reason for blanked pages. Only extra work for admins to clean up. -- Krinkle * Actually there are legitimate reasons to blank a page; I was hit by this filter just before I became an admin. Allow edit count greater than 200. (I left the "sysop" in despite redundancy for code safety, in case there were a temporary single-purpose admin account or something.) - KoH 'sysop' in user_groups --> "autopatrol" in user_rights -- Steinsplitter Change line 4 to not trigger where new_size and old_size are both 0. -Mdaniels
Flags:	Hide details of this filter from public view Enable this filter Mark as deleted
Filter last modified:	01:54, 3 May 2023 by Mdaniels5757 (talk \| contribs)
History:	View this filter's history
Tools:	Export this filter to another wiki {"data":{"rules":"(action = 'edit')\r\n\u0026 !(\"autopatrol\" in user_rights \| user_editcount \u003E= 200)\r\n\u0026 (page_namespace == 0 \| page_namespace == 4 \| page_namespace == 6 \| page_namespace == 10 \| page_namespace == 14)\r\n\u0026 ((new_size \u003C 10 \u0026 old_size \u003E 100) \| (new_size == 0 \u0026 old_size != 0))\r\n\u0026 !(\"#redirect\" in lcase(added_lines))\r\n\u0026 !(\"{{\" in added_lines \u0026 \"}}\" in added_lines)\r\n\u0026 !(\"Sandbox\" in page_title)","name":"Page blanking","comments":"Related filters:\r\n* filter 14 - for blanking pages in the user/user talk namespaces\r\n* filter 42 - for section blanking\r\n\r\nThis filter is for page blankings in the gallery (0), file (6) and category (14) namespace.\r\n* Add template namespace (10). --The Evil IP address\r\n* Add project namespace (4). --Krinkle\r\n\r\nTriggered for anyone not autoconfirmed.\r\n* Raised to trigger for anyone not a sysop, there's no reason for blanked pages. Only extra work for admins to clean up. -- Krinkle\r\n* Actually there are legitimate reasons to blank a page; I was hit by this filter just before I became an admin. Allow edit count greater than 200. (I left the \"sysop\" in despite redundancy for code safety, in case there were a temporary single-purpose admin account or something.) - KoH\r\n'sysop' in user_groups --\u003E \"autopatrol\" in user_rights -- Steinsplitter\r\n\r\nChange line 4 to not trigger where new_size and old_size are both 0. -Mdaniels","group":"default","actions":{"disallow":["abusefilter-disallowed"],"warn":["abusefilter-warning-blanking2"]},"enabled":true,"deleted":false,"privacylevel":0,"global":false},"actions":{"disallow":["abusefilter-disallowed"],"warn":["abusefilter-warning-blanking2"]}}

Actions to take when matched

Trigger actions only if the user trips a rate limit

Number of actions to allow:

Period of time (in seconds):

Group throttle by:

user

See the documentation on mediawiki.org.

Trigger these actions after giving the user a warning

System message to use for warning:

Page name of other message:

(without "MediaWiki:" prefix)

Prevent the user from performing the action in question

System message to use for disallowing:

Page name of other message:

(without "MediaWiki:" prefix)

Revoke the user's autoconfirmed status

Tag the edit in contributions lists and page histories

Tags to apply:

Require the user to complete a CAPTCHA in order to proceed with the action. Users with permission to skip a CAPTCHA are exempt.