Viewing filter 164: Possible cut and paste moves

Filter parameters

Filter ID:	164
Description: (publicly viewable)
Filter hits:	38,109 hits
Statistics:	Of the last 71,695 actions, this filter has matched 1 (0%). On average, its run time is 0.05 ms, and it consumes 0.8 conditions of the condition limit.
Conditions: (documentation)	page_id == 0 & page_namespace == 0 & user_editcount < 250 & new_size > 500 & new_wikitext irlike "\[edit\]\|\{\{(?:unreferenced\|advert\|coi\b\|upe\b\|undisclosed paid\|notability\|pp\|cleanup\|article for deletion\/dated\|refimprove\|multiple issues)" page_id == 0 & page_namespace == 0 & user_editcount < 250 & new_size > 500 & new_wikitext irlike "\[edit\]\|\{\{(?:unreferenced\|advert\|coi\b\|upe\b\|undisclosed paid\|notability\|pp\|cleanup\|article for deletion\/dated\|refimprove\|multiple issues)"
Notes:	Per RAF. Detects probable cut and paste moves where a large new page is created with either [edit] text in it (indicative of copying the HTML rather than the source) or with message boxes already on it. Narrowing search pattern to tags that would rarely be placed by the article's creator except in a copy-paste. ~ Someguy1221 :Made this case insensitive. -DF Added tag: possible cut and paste move. --Drilnoth Limited this filter to user with editcount less than 2000. - Ruslik Autoconfirmed only, presumably everyone with the move tag will make actual moves -Prodego Optimizing - KoH Add a few tags from filter 237 in order to merge the two filters. Change order of tests for (presumably) faster operation. Change from not auto-confirmed only to less than 250 edits, as inexperienced editors often do copy & paste moves despite having the technical ability to use the move button. Change tag to read "... or recreation" since that is another explanation for where the tags came from. -ThaddeusB please don't change the name of a tag already applied to edits, as it creates a new one, instead change the description - Cen Optimize (nest per Dragon's Flight, see if it changes from 0.66 ms and 2 conditions). RF 2015-02-18 Cleanup, update deprecated, simplify. --SoY 18 Mar 2019 Update to match names of templates that were renamed in 2010, add {{UPE}} and {{undisclosed paid}}, fix FP on {{coin-stub}}, simplify more. --SoY 18 Mar 2019 Small changes. Converted group into a non-capturing group, since the capture is not used. Escaped the / character in the "article for deletion/dated" condition. --Oshwah 7/10/2022
Flags:	Hide details of this filter from public view Enable this filter Mark as deleted
Filter last modified:	20:51, 10 July 2022 by Oshwah (talk \| contribs)
History:	View this filter's history
Tools:	Export this filter to another wiki {"data":{"rules":"page_id == 0 \u0026\r\npage_namespace == 0 \u0026\r\nuser_editcount \u003C 250 \u0026\r\nnew_size \u003E 500 \u0026\r\nnew_wikitext irlike \"\\[edit\\]\|\\{\\{(?:unreferenced\|advert\|coi\\b\|upe\\b\|undisclosed paid\|notability\|pp\|cleanup\|article for deletion\\/dated\|refimprove\|multiple issues)\"","name":"Possible cut and paste moves","comments":"Per RAF. Detects probable cut and paste moves where a large new page is created with either [edit] text in it (indicative of copying the HTML rather than the source) or with message boxes already on it.\r\n\r\nNarrowing search pattern to tags that would rarely be placed by the article's creator except in a copy-paste. ~ Someguy1221\r\n\r\n:Made this case insensitive. -DF\r\n\r\nAdded tag: possible cut and paste move. --Drilnoth\r\nLimited this filter to user with editcount less than 2000. - Ruslik\r\n\r\nAutoconfirmed only, presumably everyone with the move tag will make actual moves -Prodego\r\n\r\nOptimizing - KoH\r\n\r\nAdd a few tags from filter 237 in order to merge the two filters. Change order of tests for (presumably) faster operation. Change from not auto-confirmed only to less than 250 edits, as inexperienced editors often do copy \u0026 paste moves despite having the technical ability to use the move button. Change tag to read \"... or recreation\" since that is another explanation for where the tags came from. -ThaddeusB\r\n\r\nplease don't change the name of a tag already applied to edits, as it creates a new one, instead change the description - Cen\r\n\r\nOptimize (nest per Dragon's Flight, see if it changes from 0.66 ms and 2 conditions). RF 2015-02-18\r\n\r\nCleanup, update deprecated, simplify. --SoY 18 Mar 2019\r\n\r\nUpdate to match names of templates that were renamed in 2010, add {{UPE}} and {{undisclosed paid}}, fix FP on {{coin-stub}}, simplify more. --SoY 18 Mar 2019\r\n\r\nSmall changes. Converted group into a non-capturing group, since the capture is not used. Escaped the / character in the \"article for deletion/dated\" condition. --Oshwah 7/10/2022","group":"default","actions":{"tag":["possible cut and paste move"]},"enabled":true,"deleted":false,"hidden":false,"global":false},"actions":{"tag":["possible cut and paste move"]}}

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)

possible cut and paste move