|
|
| Update: On 10 February 2021, change made by Harpsicorder, Abuse Filter set from disallow to warn/tag. Reason is not all external links may be made in harmful intent. | | Update: On 10 February 2021, change made by Harpsicorder, Abuse Filter set from disallow to warn/tag. Reason is not all external links may be made in harmful intent. |
|
| |
|
| Added customized warning --Justarandomamerican | | Added customized warning --Justarandomamerican |
|
| |
|
| apply to IPs, too | | apply to IPs, too |
|
| |
|
| Changed warning message & title --X | | Changed warning message & title --X |
|
| |
|
| Major reconfiguring of the filter has been done (along with thorough testing of the new conditions by using the examine feature). I did the following changes: | | Major reconfiguring of the filter has been done (along with thorough testing of the new conditions by using the examine feature). I did the following changes: |
|
| |
|
| 1) I changed the current page_namespace condition to "equals_to_any(page_namespace, 2, 3)", and have moved it to the very top. | | 1) I changed the current page_namespace condition to "equals_to_any(page_namespace, 2, 3)", and have moved it to the very top. |
| 2) Below that, I changed "!"sysop" in user_groups" to "!contains_any(user_groups, "autopatrol", "sysop", "bot")", and have added the autopatrolled and bot user groups. | | 2) Below that, I changed "!"sysop" in user_groups" to "!contains_any(user_groups, "autopatrol", "sysop", "bot")", and have added the autopatrolled and bot user groups. |
| 3) Below the latter conditions, I have put the remaining three conditions inside a (), and have put both of the added_links in the same line (line 6). | | 3) Below the latter conditions, I have put the remaining three conditions inside a (), and have put both of the added_links in the same line (line 6). |
|
| |
|
| With the new conditions, the reconfigured filter will still function as the previous change, but it's reconfigured to something advanced, at the very least. — 64andtim | | With the new conditions, the reconfigured filter will still function as the previous change, but it's reconfigured to something advanced, at the very least. — 64andtim |
|
| |
|
| Changed warning message to "MediaWiki:Abusefilter-warning-41". — 64andtim | | Changed warning message to "MediaWiki:Abusefilter-warning-41". — 64andtim |
|
| |
|
| Remove user page and namespace condition -Justa | | Remove user page and namespace condition -Justa |
|
| |
|
| Removed the parenthesis condition, placed user_editcount on the first line and placed the exempt user groups condition at the last line. – Codename Norte (3/8/24) | | Removed the parenthesis condition, placed user_editcount on the first line and placed the exempt user groups condition at the last line. – Codename Norte (3/8/24) |
|
| |
|
| Disable as it is effecting users adding confirmation links. -X | | Disable as it is effecting users adding confirmation links. -X |
|
| |
|
| Enable, exempting RfP. -Justa | | Enable, exempting RfP. -Justa |
|
| |
|
| Disable, still not working. -X | | Disable, still not working. -X |
|
| |
|
| Re-enable again, page_prefixedtitle != 'Test_Wiki:Request_for_permissions' on line 4 was the issue; I switched it to page_id != 702 and checked if it caught anything other that TW:RfP. It finally works again! -- Codename Noreste, June 26 2024 | | Re-enable again, page_prefixedtitle != 'Test_Wiki:Request_for_permissions' on line 4 was the issue; I switched it to page_id != 702 and checked if it caught anything other that TW:RfP. It finally works again! -- Codename Noreste, June 26 2024 |
|
| |
|
| No reason for filter 41 to remain private; I do not believe this is targeted to spammers who attempt various ways to bypass this filter, and automated spambots aren't going to try and avoid this as well. It could also allow non-admins to review this filter's log to check for spam or other kinds of false positives. But fellow administrators who help with abuse filters, you may revert this if you disagree. -- Codename Noreste, July 5 2024 | | No reason for filter 41 to remain private; I do not believe this is targeted to spammers who attempt various ways to bypass this filter, and automated spambots aren't going to try and avoid this as well. It could also allow non-admins to review this filter's log to check for spam or other kinds of false positives. But fellow administrators who help with abuse filters, you may revert this if you disagree. -- Codename Noreste, July 5 2024 |
| | |
| | Excluding user space. -- Codename Noreste, August 20 2024 |
