Viewing filter 368: Making large changes when marking the edit as minor

Filter parameters

Filter ID:	368
Description: (publicly viewable)
Filter hits:	42,952 hits
Conditions: (documentation)	minor_edit & (edit_delta < -500 \| edit_delta > 500) & user_editcount < 500 & !((article_namespace == 2 \| article_namespace == 3) & user_name in article_text) & !(article_namespace % 2 == 1) & !("bot" in lcase(user_name)) & !("bot" in user_groups) & !("Wikipedia:Sandbox" in article_prefixedtext) & !contains_any(summary, "reverted", "undid", "\|TW]]", "rvv") minor_edit & (edit_delta < -500 \| edit_delta > 500) & user_editcount < 500 & !((article_namespace == 2 \| article_namespace == 3) & user_name in article_text) & !(article_namespace % 2 == 1) & !("bot" in lcase(user_name)) & !("bot" in user_groups) & !("Wikipedia:Sandbox" in article_prefixedtext) & !contains_any(summary, "reverted", "undid", "\|TW]]", "rvv")
Notes:	This will trigger on edits that are marked as minor that have a size change of greater than 500 bytes (either removing or adding 200 or more characters). Obviously, this won't catch all non-minor edits, as a small size change can still be pretty darn major, but this should catch those who mark every single edit as minor. Ideally, once tested, this will give users a warning along the lines of "are you sure you want to mark this edit as minor?" explaining what minor edits are and how to turn off that stupid setting in preferences. - Hersfold, 18:16 Oct. 20 2010 Changing to not trigger on bot edits; most bots mark their edits as minor, and most of the early hits are indeed bots. - Hersfold, 18:30 Oct. 20 2010 Changed size of edit to 500 after finding that many triggered edits could have been minor, and were just adding references or the like. This also goes more in line with Recent Changes, which bolds edits that have a net change of 500 bytes or more. - Hersfold, 18:37 Oct. 20 2010 Disabling until I can figure out why this is eating up 68 (!) conditions. - Hersfold 22:14 Oct. 25 2010 Following some reassurance from Soap (thanks), I'm going to turn this back on with an added condition; if the user has more than 500 edits, it won't trigger for them. There are a large number of experienced users setting this off, and I'd like to assume that they know what they're doing. - Hersfold 22:25 Oct. 25 2010 Now will also not trigger within a user's own userspace. - Hersfold 22:32 Oct. 25 2010 As Gurch pointed out, I apparently fail at logic. NOW it won't trigger in someone's userspace. - Hersfold 15:39 Oct. 26 2010 Removing talk namespaces as well. Aside from that, many if not all of the recent triggers appear to be accurate, so I'm going to turn on warning and tagging. The warning invites reports of false positives, so hopefully that should help with any further problems. - Hersfold 15:42 Oct. 27 2010 Reordering conditions as requested on my talk page - hopefully will make this more efficient. - Hersfold 22:07 Oct. 27 2010 Adding check to avoid issues with sandboxes. --Reaper Ignore reverts of vandalism. --Reaper :removed, is this really necessary? It seems to be causing a lot of annoyance. -- Soap Marked as deleted - KoH
Flags:	Hide details of this filter from public view Enable this filter Mark as deleted
Filter last modified:	17:35, 12 February 2015 by Cenarium (talk \| contribs)
History:	View this filter's history
Tools:	Export this filter to another wiki {"data":{"rules":"minor_edit \u0026\r\n(edit_delta \u003C -500 \| edit_delta \u003E 500) \u0026\r\nuser_editcount \u003C 500 \u0026\r\n!((article_namespace == 2 \| article_namespace == 3) \u0026 user_name in article_text) \u0026\r\n!(article_namespace % 2 == 1) \u0026\r\n!(\"bot\" in lcase(user_name)) \u0026\r\n!(\"bot\" in user_groups) \u0026\r\n!(\"Wikipedia:Sandbox\" in article_prefixedtext) \u0026\r\n!contains_any(summary, \"reverted\", \"undid\", \"\|TW]]\", \"rvv\")","name":"Making large changes when marking the edit as minor","comments":"This will trigger on edits that are marked as minor that have a size change of greater than 500 bytes (either removing or adding 200 or more characters). Obviously, this won't catch all non-minor edits, as a small size change can still be pretty darn major, but this should catch those who mark every single edit as minor.\r\n\r\nIdeally, once tested, this will give users a warning along the lines of \"are you sure you want to mark this edit as minor?\" explaining what minor edits are and how to turn off that stupid setting in preferences. - Hersfold, 18:16 Oct. 20 2010\r\n\r\nChanging to not trigger on bot edits; most bots mark their edits as minor, and most of the early hits are indeed bots. - Hersfold, 18:30 Oct. 20 2010\r\n\r\nChanged size of edit to 500 after finding that many triggered edits could have been minor, and were just adding references or the like. This also goes more in line with Recent Changes, which bolds edits that have a net change of 500 bytes or more. - Hersfold, 18:37 Oct. 20 2010\r\n\r\nDisabling until I can figure out why this is eating up 68 (!) conditions. - Hersfold 22:14 Oct. 25 2010\r\n\r\nFollowing some reassurance from Soap (thanks), I'm going to turn this back on with an added condition; if the user has more than 500 edits, it won't trigger for them. There are a large number of experienced users setting this off, and I'd like to assume that they know what they're doing. - Hersfold 22:25 Oct. 25 2010\r\n\r\nNow will also not trigger within a user's own userspace. - Hersfold 22:32 Oct. 25 2010\r\n\r\nAs Gurch pointed out, I apparently fail at logic. NOW it won't trigger in someone's userspace. - Hersfold 15:39 Oct. 26 2010\r\n\r\nRemoving talk namespaces as well. Aside from that, many if not all of the recent triggers appear to be accurate, so I'm going to turn on warning and tagging. The warning invites reports of false positives, so hopefully that should help with any further problems. - Hersfold 15:42 Oct. 27 2010\r\n\r\nReordering conditions as requested on my talk page - hopefully will make this more efficient. - Hersfold 22:07 Oct. 27 2010\r\n\r\nAdding check to avoid issues with sandboxes. --Reaper\r\n\r\nIgnore reverts of vandalism. --Reaper\r\n:removed, is this really necessary? It seems to be causing a lot of annoyance. -- Soap\r\n\r\nMarked as deleted - KoH","group":"default","actions":{"warn":["abusefilter-warning-minoredit"]},"enabled":false,"deleted":true,"privacylevel":0,"global":false},"actions":{"warn":["abusefilter-warning-minoredit"]}}

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.