Viewing filter 957: Removal of article lead

You are viewing an old version of this filter. The statistics quoted are for the most recent version of the filter. • Return to this filter's history.

Filter parameters

Filter ID:	957
Description: (publicly viewable)
Statistics:	Of the last 152,007 actions, this filter has matched 61 (0.04%). On average, its run time is 0.22 ms, and it consumes 1.2 conditions of the condition limit.
Conditions: (documentation)	!"confirmed" in user_groups & page_namespace == 0 & ( stringy := "{{infobox"; stringy2 := "'''"; contains_all(lcase(removed_lines), stringy, stringy2) & !(contains_any(lcase(added_lines), stringy, stringy2)) & new_size > 500 & /* exclude blankings, which is covered by filter 3 / !(lcase(added_lines) rlike "#redirect\|{{((db-(attack\|g10))\|wi)}}") ) !"confirmed" in user_groups & page_namespace == 0 & ( stringy := "{{infobox"; stringy2 := "'''"; contains_all(lcase(removed_lines), stringy, stringy2) & !(contains_any(lcase(added_lines), stringy, stringy2)) & new_size > 500 & / exclude blankings, which is covered by filter 3 */ !(lcase(added_lines) rlike "#redirect\|{{((db-(attack\|g10))\|wi)}}") )
Notes:	Tested on filter 953. Quit a bit of vandalism that just involves removing the lead of an article, including the infobox. There's overlap with other filters but a reasonable proportion of edits get through that needs to be disallowed and wouldn't be catcheable by other filters I know of. Currently just logging and if there are no false positives will post on EFN about setting to disallow. -Galo Increase new_size exclusion limit, so that there should be no conversions to redirects and the like caught. -Galo 2019.01.14 Set to disallow per [[Special:PermaLink/879231787#Setting_filter_957_to_disallow?]] -Galo 2019.01.20
Flags:	Hide details of this filter from public view Enable this filter Mark as deleted
Filter last modified:	07:11, 20 January 2019 by Galobtter (talk \| contribs)
History:	View this filter's history
Tools:	Export this filter to another wiki {"data":{"rules":"!\"confirmed\" in user_groups \u0026\r\npage_namespace == 0 \u0026 (\r\n stringy := \"{{infobox\";\r\n stringy2 := \"'''\";\r\n contains_all(lcase(removed_lines), stringy, stringy2) \u0026\r\n !(contains_any(lcase(added_lines), stringy, stringy2)) \u0026\r\n new_size \u003E 500 \u0026 /* exclude blankings, which is covered by filter 3 */\r\n !(lcase(added_lines) rlike \"#redirect\|{{((db-(attack\|g10))\|wi)}}\")\r\n)","name":"Removal of article lead","comments":"Tested on filter 953. Quit a bit of vandalism that just involves removing the lead of an article, including the infobox. There's overlap with other filters but a reasonable proportion of edits get through that needs to be disallowed and wouldn't be catcheable by other filters I know of. Currently just logging and if there are no false positives will post on EFN about setting to disallow. -Galo\r\n\r\nIncrease new_size exclusion limit, so that there should be no conversions to redirects and the like caught. -Galo 2019.01.14\r\n\r\nSet to disallow per [[Special:PermaLink/879231787#Setting_filter_957_to_disallow?]] -Galo 2019.01.20","group":"default","actions":{"disallow":["abusefilter-disallowed-article-lead-removed"]},"enabled":true,"deleted":false,"privacylevel":0,"global":false},"actions":{"disallow":["abusefilter-disallowed-article-lead-removed"]}}

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:

(see Wikipedia:Tags for use and formatting)

(please don't rename a tag here, see link above)

(one per line, no commas, publicly visible)

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

You are viewing an old version of this filter. The statistics quoted are for the most recent version of the filter. • Return to this filter's history.