Viewing abuse filter 5: Restrict Removal of Stub Notices to Sysops

Filter parameters

Filter ID:	5
Description: (publicly viewable)
Conditions:	( contains_any(removed_lines, "{{irrelevant}}", "{{incomplete}}", "{{garbage}}") ) & !(user_groups contains "sysop") ( contains_any(removed_lines, "{{irrelevant}}", "{{incomplete}}", "{{garbage}}") ) & !(user_groups contains "sysop")
Notes:	# AnotherConsumerRightsPerson (10 November 2025) - Have disabled due to Filter 4 being the same thing but better, and this takes up time to run, but enable again # if I'm wrong. # AbuseFilter Rule: Restrict Removal of Stub Notices to Sysops Only # # Description: # This is an AbuseFilter rule for MediaWiki that prevents regular users and anonymous editors # from removing specific stub notices (`{{irrelevant}}`, `{{incomplete}}`, `{{garbage}}`) from articles. # Only users in the "sysop" (administrator) group are allowed to remove these notices. # The purpose of this rule is to ensure that these warnings remain in place until reviewed # and removed by a moderator so people don't get salty and remove notices from their own articles. They can edit the article but can't remove the notice. # # Rule Syntax: # The rule uses MediaWiki's AbuseFilter language, which operates on conditions and actions. # Here is the full rule with comments explaining each part: ( # `contains_any` checks if any of the specified strings (stub templates) were removed in the edit. contains_any(removed_lines, "{{irrelevant}}", "{{incomplete}}", "{{garbage}}") ) & !( # `user_groups contains "sysop"` ensures the rule applies only to users who are NOT sysops. user_groups contains "sysop" ) # How the Rule Works: # 1. The `removed_lines` variable holds the content removed in an edit. # 2. `contains_any(removed_lines, "{{irrelevant}}", "{{incomplete}}", "{{garbage}}")`: # - Checks if any of the three templates were part of the removed content. # - If yes, this part evaluates to true. # 3. `user_groups contains "sysop"`: # - Checks if the user making the edit belongs to the "sysop" group. # - The `!` (NOT) operator ensures the rule applies to users who are NOT in the "sysop" group. # 4. The rule triggers if: # - The edit removes one or more of the stub notices, AND # - The editor is not a sysop. # Actions to Take: # You can configure the following actions for this rule: # - Disallow: Prevent the edit entirely. # - Warn: Show a message to the user explaining why their edit is disallowed. # - Tag: Mark the edit for review by admins. # - Typically, "Disallow" is sufficient for this scenario. # Example Warning Message: # "You are not allowed to remove the stub notices {{irrelevant}}, {{incomplete}}, or {{garbage}} unless you are a sysop. Please contact an administrator if you believe this is a mistake." # Editing This Rule: # For a newbie with no coding experience: # 1. Log in as a user with permission to modify AbuseFilters (usually sysop or higher). # 2. Go to `Special:AbuseFilter` and find this rule. # 3. Edit the rule as follows: # - To add new stub templates, include them in the `contains_any` function, like this: # contains_any(removed_lines, "{{irrelevant}}", "{{incomplete}}", "{{garbage}}", "{{new_template}}") # - To change who can remove stub notices, modify the `user_groups` condition: # Example: `!(user_groups contains "superadmin")` will restrict removal to superadmins only. # 4. Save the filter and test it using the "Test" feature to ensure it behaves as expected. # Testing the Rule: # - Use the "Test" feature on the AbuseFilter management page. # - Input sample edits (removed lines with stub templates) and check if the rule triggers correctly. # - Test edits as a sysop and a non-sysop to confirm that permissions work properly. # Notes for Maintenance: # - Keep the warning message clear and user-friendly. # - Log attempts to remove these templates for audit purposes. # - Review the filter regularly to ensure it is functioning as intended.
Flags:	Warning: This filter was automatically flagged as harmful. As a safety measure, the following action will not execute: Block autopromote. Please check whether the high rate of matches is expected. If so, you can save the filter again to remove this restriction. Hide details of this filter from public view Enable this filter Mark as deleted
Filter last modified:	18:35, 9 December 2025 by AnotherConsumerRightsPerson (talk \| contribs)
History:	View this filter's history
Tools:	Export this filter to another wiki {"data":{"rules":"(\r\n contains_any(removed_lines, \"{{irrelevant}}\", \"{{incomplete}}\", \"{{garbage}}\")\r\n) \u0026 !(user_groups contains \"sysop\")","name":"Restrict Removal of Stub Notices to Sysops","comments":"# AnotherConsumerRightsPerson (10 November 2025) - Have disabled due to Filter 4 being the same thing but better, and this takes up time to run, but enable again # if I'm wrong.\r\n# AbuseFilter Rule: Restrict Removal of Stub Notices to Sysops Only\r\n# \r\n# Description:\r\n# This is an AbuseFilter rule for MediaWiki that prevents regular users and anonymous editors \r\n# from removing specific stub notices (`{{irrelevant}}`, `{{incomplete}}`, `{{garbage}}`) from articles.\r\n# Only users in the \"sysop\" (administrator) group are allowed to remove these notices.\r\n# The purpose of this rule is to ensure that these warnings remain in place until reviewed \r\n# and removed by a moderator so people don't get salty and remove notices from their own articles. They can edit the article but can't remove the notice. \r\n# \r\n# Rule Syntax:\r\n# The rule uses MediaWiki's AbuseFilter language, which operates on conditions and actions. \r\n# Here is the full rule with comments explaining each part:\r\n\r\n(\r\n # `contains_any` checks if any of the specified strings (stub templates) were removed in the edit.\r\n contains_any(removed_lines, \"{{irrelevant}}\", \"{{incomplete}}\", \"{{garbage}}\")\r\n) \u0026 \r\n!(\r\n # `user_groups contains \"sysop\"` ensures the rule applies only to users who are NOT sysops.\r\n user_groups contains \"sysop\"\r\n)\r\n\r\n# How the Rule Works:\r\n# 1. The `removed_lines` variable holds the content removed in an edit.\r\n# 2. `contains_any(removed_lines, \"{{irrelevant}}\", \"{{incomplete}}\", \"{{garbage}}\")`:\r\n# - Checks if any of the three templates were part of the removed content.\r\n# - If yes, this part evaluates to true.\r\n# 3. `user_groups contains \"sysop\"`:\r\n# - Checks if the user making the edit belongs to the \"sysop\" group.\r\n# - The `!` (NOT) operator ensures the rule applies to users who are NOT in the \"sysop\" group.\r\n# 4. The rule triggers if:\r\n# - The edit removes one or more of the stub notices, AND\r\n# - The editor is not a sysop.\r\n\r\n# Actions to Take:\r\n# You can configure the following actions for this rule:\r\n# - Disallow: Prevent the edit entirely.\r\n# - Warn: Show a message to the user explaining why their edit is disallowed.\r\n# - Tag: Mark the edit for review by admins.\r\n# - Typically, \"Disallow\" is sufficient for this scenario.\r\n\r\n# Example Warning Message:\r\n# \"You are not allowed to remove the stub notices {{irrelevant}}, {{incomplete}}, or {{garbage}} unless you are a sysop. Please contact an administrator if you believe this is a mistake.\"\r\n\r\n# Editing This Rule:\r\n# For a newbie with no coding experience:\r\n# 1. Log in as a user with permission to modify AbuseFilters (usually sysop or higher).\r\n# 2. Go to `Special:AbuseFilter` and find this rule.\r\n# 3. Edit the rule as follows:\r\n# - To add new stub templates, include them in the `contains_any` function, like this:\r\n# contains_any(removed_lines, \"{{irrelevant}}\", \"{{incomplete}}\", \"{{garbage}}\", \"{{new_template}}\")\r\n# - To change who can remove stub notices, modify the `user_groups` condition:\r\n# Example: `!(user_groups contains \"superadmin\")` will restrict removal to superadmins only.\r\n# 4. Save the filter and test it using the \"Test\" feature to ensure it behaves as expected.\r\n\r\n# Testing the Rule:\r\n# - Use the \"Test\" feature on the AbuseFilter management page.\r\n# - Input sample edits (removed lines with stub templates) and check if the rule triggers correctly.\r\n# - Test edits as a sysop and a non-sysop to confirm that permissions work properly.\r\n\r\n# Notes for Maintenance:\r\n# - Keep the warning message clear and user-friendly.\r\n# - Log attempts to remove these templates for audit purposes.\r\n# - Review the filter regularly to ensure it is functioning as intended.","group":"default","actions":{"blockautopromote":[],"disallow":["removing stub notice"],"tag":["potentially salty about stub notice"]},"enabled":false,"deleted":false,"privacylevel":0,"global":false},"actions":{"blockautopromote":[],"disallow":["removing stub notice"],"tag":["potentially salty about stub notice"]}}

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

Block the user and/or IP address from editing

Block the user and/or IP address from editing their own talk page

Block duration for non-registered users:

Block duration for registered users:

Remove the user from all privileged groups

Tag the edit for further review

Tags to apply:

potentially salty about stub notice