Wikipedia:Edit filter noticeboard
Welcome to the edit filter noticeboard |
---|
Filter 1112 — Pattern modified
This is the edit filter noticeboard, for coordination and discussion of edit filter use and management. If you wish to request an edit filter, please post at Wikipedia:Edit filter/Requested. If you would like to report a false positive, please post at Wikipedia:Edit filter/False positives. Private filters should not be discussed in detail here; please email an edit filter manager if you have specific concerns or questions about the content of hidden filters. There are currently 332 enabled filters and 43 stale filters with no hits in the past 30 days. Filter condition use is ~1020, out of a maximum of 2000. ( ). See also the profiling data and edit filter graphs. |
Index 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 11, 12, 13 |
This page has archives. Sections older than 10 days may be automatically archived by Lowercase sigmabot III. |
Page protection
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
I protected Wikipedia:Edit filter/False positives/Reports for 1 day 3 hours due to persistent vandalism from multiple accounts. Ohnoitsjamie and other administrators, please feel free to lift the protection earlier at your discretion. Daniel Quinlan (talk) 03:26, 8 July 2024 (UTC)
- Good protection, but it looks like these diffs (Special:Diff/1233248166, Special:Diff/1233232866, Special:Diff/1233232682, and others with more than 100,000 text bytes added) will need to be revision-deleted because of disruptive Zalgo text. Codename Noreste 🤔 Talk 03:46, 8 July 2024 (UTC)
Not the same person this time, but I'd just like to make people aware (I probably don't need to, tbh, but just making sure) that @JJMC89 has protected EFFPR for 48 hours. – 2804:F14:8084:CE01:9034:B5CB:942A:939E (talk) 20:43, 1 August 2024 (UTC)
Set filter 707 to disallow?
[edit]Per the recent hits, it's working great, and we need to stop this type of disruption on that page. Also, check that filter's notes. Codename Noreste 🤔 Talk 06:45, 25 July 2024 (UTC)
- No objections, though probably best to put in a custom edit notice to re-target to the edit filter noticeboard instead since it targets the EFFPR page, something like:
![]() | An automated filter has identified this edit as potentially unconstructive. Please be aware that vandalism will result in revocation of your editing privileges. If this edit was disallowed in error, please make a new section on the same page you were editing. |
- This perhaps? EggRoll97 (talk) 21:16, 25 July 2024 (UTC)
- If we plan to use your proposed disallow message, it should be made on MediaWiki:Abusefilter-disallowed-EFFPR by an admin; alternatively, we could use the default disallow message, but users would click on the Report error button because there's a button to press, and would lead to pointless reports of people begging for help on WP:EFFPR. Also, I believe the word
disruption
is probably more accurate thanvandalism
, since filters 768 and 984 use the former word, but not 707. Codename Noreste 🤔 Talk 21:34, 25 July 2024 (UTC)
- If we plan to use your proposed disallow message, it should be made on MediaWiki:Abusefilter-disallowed-EFFPR by an admin; alternatively, we could use the default disallow message, but users would click on the Report error button because there's a button to press, and would lead to pointless reports of people begging for help on WP:EFFPR. Also, I believe the word
Here's the new disallow message code if anyone's interested:
{{edit filter warning | action = disallow | text = <div style="text-align: center;">An automated filter has identified this edit as potentially unconstructive. Please be aware that [[Wikipedia:Vandalism|vandalism]] will result in [[Wikipedia:Blocking policy|revocation of your editing privileges]]. If this edit was disallowed in error, please make a new section on the same page you were editing.</div> | fplink = no }}
Codename Noreste 🤔 Talk 21:36, 25 July 2024 (UTC)
- Based on the IP's comments below, we could simply direct to leave a new section on the false positives page, but without the report error button featured in the default disallow message, making the message,
An automated filter has identified this edit as potentially unconstructive. Please be aware that vandalism may result in revocation of your editing privileges. If this edit was disallowed in error, please make a new section on the same page you were editing.
I don't think there really needs to be a report error button since the filter is very narrowly targeted and shouldn't have any false positives. Also, Codename Noreste, I've BOLDly changed the filter description to "disruption" instead. Doesn't seem like that big of a deal whether it's referred to as vandalism or disruption, but who knows. EggRoll97 (talk) 03:00, 26 July 2024 (UTC)- Feel free to modify the message code I posted and the proposed disallow message to reflect what you said, and about changing from vandalism to disruption, I'm not sure how to describe 707 in public, but it catches more than just vandalism obviously. Codename Noreste 🤔 Talk 03:03, 26 July 2024 (UTC) (I modified it anyway) -- Codename Noreste
- Based on the IP's comments below, we could simply direct to leave a new section on the false positives page, but without the report error button featured in the default disallow message, making the message,
- Obviously private, but is reporting false positives about this at EFFPR even a problem? Is it actually going to set off the filter too? – 2804:F1...E9:11BA (talk) 00:25, 26 July 2024 (UTC)
- Reporting false positives will not trigger the filter. Codename Noreste 🤔 Talk 00:30, 26 July 2024 (UTC)
- I think
If this edit was disallowed in error, please leave a message on the edit filter noticeboard
should point to WP:EFFPR, not EFN. –Novem Linguae (talk) 03:05, 26 July 2024 (UTC)- I modified the message to reflect this, but I took out the big warning thing. Codename Noreste 🤔 Talk 03:11, 26 July 2024 (UTC)
- Yeah, that looks good. EggRoll97 (talk) 03:12, 26 July 2024 (UTC)
- Minor change, but "may be blocked" sounds a little soft, so I'm modifying the notice to say "will" instead of "may". – PharyngealImplosive7 (talk) 02:55, 27 July 2024 (UTC)
- Yeah, that looks good. EggRoll97 (talk) 03:12, 26 July 2024 (UTC)
- I modified the message to reflect this, but I took out the big warning thing. Codename Noreste 🤔 Talk 03:11, 26 July 2024 (UTC)
Done MediaWiki page creation requested, and I'll toggle the disallow as soon as an admin makes the page. EggRoll97 (talk) 15:34, 27 July 2024 (UTC)
- I've created the page. I have two observations. First, does this need to be private? I'm not aware of any private-type issues, but I haven't looked far. Second, there's a boolean condition which is 'true and true or true'. The precedence is probably written up somewhere, but I find non-parenthesised conditions like this highly confusing and subject to errors. Maybe clarify the intention? -- zzuuzz (talk) 16:30, 27 July 2024 (UTC)
- @Zzuuzz: I'm actually not sure if it needs to be private. It was private on the initial iteration, so I didn't change the visibility when re-enabling. No objections to publicizing, though. As for the boolean condition, it seems to be parenthesized, but I woke up fairly early today so I'm not sure if I'm looking in the same place that you are. EggRoll97 (talk) 16:46, 27 July 2024 (UTC)
- I think we're looking at the same thing, but I probably wasn't clear. Let's have an example:
(year == 2024 and month == 7 or day = "Saturday")
. It's difficult to know what this means. Maybe the year needs to be 2024, or it can be any Saturday? The documentation says not. In fact I'll quote the documentation:A & B | C is equivalent to (A & B) | C, not to A & (B | C). In particular, both false & true | true and false & false | true evaluates to true
. Complicated huh. Compare to:((year == 2024 and month == 7) or day == "Saturday")
or perhaps(year == 2024 and (month == 7 or day == "Saturday"))
(and it can get really complicated when people start adding more conditions). -- zzuuzz (talk) 17:31, 27 July 2024 (UTC)- Agreed. Always use parentheses with boolean algebra. For readability. –Novem Linguae (talk) 17:50, 27 July 2024 (UTC)
- I've even confused myself above. It can be any Saturday. It certainly is one today.. -- zzuuzz (talk) 18:03, 27 July 2024 (UTC)
- What lines of filter 707 was this starting the boolean problem? Codename Noreste 🤔 Talk 18:18, 27 July 2024 (UTC)
- @Zzuuzz: Assuming you're referring to lines 15-19 (I've now unhidden the filter, because it shouldn't be catching much more than drive-by vandals), I think the fix would just be
(new_size < 300 & old_size > 300 & edit_delta < -250) &
. EggRoll97 (talk) 18:34, 27 July 2024 (UTC)- I have no objections to 707 being public, but after testing the new code, this doesn't seem to catch the blanking disruption, rather just header removal disruption. Also pinging PharyngealImplosive7 since 707 is already unhidden. Codename Noreste 🤔 Talk 18:39, 27 July 2024 (UTC)
- I've even confused myself above. It can be any Saturday. It certainly is one today.. -- zzuuzz (talk) 18:03, 27 July 2024 (UTC)
- Agreed. Always use parentheses with boolean algebra. For readability. –Novem Linguae (talk) 17:50, 27 July 2024 (UTC)
- I think we're looking at the same thing, but I probably wasn't clear. Let's have an example:
- @Zzuuzz: I'm actually not sure if it needs to be private. It was private on the initial iteration, so I didn't change the visibility when re-enabling. No objections to publicizing, though. As for the boolean condition, it seems to be parenthesized, but I woke up fairly early today so I'm not sure if I'm looking in the same place that you are. EggRoll97 (talk) 16:46, 27 July 2024 (UTC)
- I've created the page. I have two observations. First, does this need to be private? I'm not aware of any private-type issues, but I haven't looked far. Second, there's a boolean condition which is 'true and true or true'. The precedence is probably written up somewhere, but I find non-parenthesised conditions like this highly confusing and subject to errors. Maybe clarify the intention? -- zzuuzz (talk) 16:30, 27 July 2024 (UTC)
I think that we should make a modification to this filter. It's working great so far except in one place, when users remove their own false positive report (see this catch for example). The user was just removing their own report.
Maybe we could add this condition to new_size < 300 & old_size > 300 | edit_delta < -250
:
!(removed_lines irlike "\={2}\s*" + user_unnamed_ip + "\s*\={2}") & !(removed_lines irlike "\={2}\s*" + user_name + "\s*\={2}")
to fix this (which should exclude people from removing their own reports). – PharyngealImplosive7 (talk) 19:05, 27 July 2024 (UTC)
- Do you have any other non-variable condition that checks for IP addresses other than
user_unnamed_ip
? Codename Noreste 🤔 Talk 20:15, 27 July 2024 (UTC)- No, I don't. If anyone else does I am open to suggestions. – PharyngealImplosive7 (talk) 21:28, 27 July 2024 (UTC)
- @EggRoll97: Any progress on adding this to the filter to reduce the amount of FPs? – PharyngealImplosive7 (talk) 23:22, 3 August 2024 (UTC)
- I'm not sure this does what you used it for? The wording at mw:Extension:AbuseFilter/Rules format#Protected variables makes me think this variable currently shows the IP and when temporary accounts get enabled it will still show the IP, but you're using it to search if the account name/IP is in the removed lines, which user_name already does for accounts and IPs and presumably will continue to do for temporary account names too.
- Not to mention, using it will apparently make the filter permanently protected from being viewed by users who do not have the
abusefilter-access-protected-vars
permission. – 2804:F1...E6:56E2 (talk) 23:42, 3 August 2024 (UTC)- Hmmm. That's interesting. I don't know what to do then to check for IPs since this doesn't work. – PharyngealImplosive7 (talk) 23:44, 3 August 2024 (UTC)
- The second line works for both IPs and accounts, and will also continue to work when temporary accounts are added (I've seen no indication that it won't).
- The docs of user_name say it's the IP for IPs. – 2804:F1...E6:56E2 (talk) 00:07, 4 August 2024 (UTC)
- Oh thank you for letting me know. I thought that the second line would only work on registered accounts. – PharyngealImplosive7 (talk) 00:15, 4 August 2024 (UTC)
- Hmmm. That's interesting. I don't know what to do then to check for IPs since this doesn't work. – PharyngealImplosive7 (talk) 23:44, 3 August 2024 (UTC)
- Just recording here that I have seen this, just have been a bit busy lately. I'll review it when I have time, unless another EFM stops by in the meanwhile. EggRoll97 (talk) 02:47, 7 August 2024 (UTC)
- @EggRoll97: Any progress on adding this to the filter to reduce the amount of FPs? – PharyngealImplosive7 (talk) 23:22, 3 August 2024 (UTC)
- No, I don't. If anyone else does I am open to suggestions. – PharyngealImplosive7 (talk) 21:28, 27 July 2024 (UTC)
Racist term that needs blacklisting
[edit]Coming here from Wikipedia:Administrators' noticeboard/Incidents#Racist comments by IP user. Asking for the blacklisting/filtering of wikt:pajeet/wikt:poojeet, a highly offensive racist slur that has seen a surge in usage in recent times. Appears to be used by trolls and bad-faith editors/IP users.
A suggestion for an addition to Special:AbuseFilter/384, has been made at the ANI thread above. Gotitbro (talk) 14:44, 1 August 2024 (UTC)
- That is quite easy to fix. Just add
\bp(?:a|o{2})je{2}t\b
to the end of the regex. – PharyngealImplosive7 (talk) 23:44, 2 August 2024 (UTC)- 384 only covers the main namespace (articles); we could add it to 478 (hist · log) for the talk page namespace or similar. Codename Noreste 🤔 Talk 01:23, 3 August 2024 (UTC)
- I share the same concerns as the admins at the ANI thread, personally. The edits are fairly stale and aren't very active disruption. EggRoll97 (talk) 04:54, 3 August 2024 (UTC)
- I don't think it matters, since these are spread over several months, and there is no evidence that a single user is responsible for most of these. –LaundryPizza03 (dc̄) 04:25, 4 August 2024 (UTC)
Set filter 1319 to disallow
[edit]The following discussion is closed. Please do not modify it. Subsequent comments should be made on the appropriate discussion page. No further edits should be made to this discussion.
This is a request that this filter be set to disallow. See filter notes, but please do NOT discuss this publicly. I can explain through the mailing list or individual email if needed. EggRoll97 (talk) 04:57, 3 August 2024 (UTC)
- I've fixed one problem. There seems to be another problem at the end of line 4. I'm still trying to parse the rest of it. -- zzuuzz (talk) 07:30, 3 August 2024 (UTC)
- I disagree with setting this to disallow. I've sent the reasons to a new thread on the mailing list. 0xDeadbeef→∞ (talk to me) 15:14, 3 August 2024 (UTC)
- I'm not a list member, but I think sometimes there's a time and a place. Other than that, no strong opinions about it. Anyway, I've edited the filter to address the concern I previously had. It has changed the meaning, so please review. It still needs some work methinks. -- zzuuzz (talk) 18:30, 3 August 2024 (UTC)
- I'll withdraw this based on the discussion on the mailing list. zzuuzz, I've indicated in a filter note the problem mentioned on the mailing list. With that in mind, probably fine to keep this as log-only. The edit you made seems fine from a glance. EggRoll97 (talk) 19:54, 3 August 2024 (UTC)
- I'm not a list member, but I think sometimes there's a time and a place. Other than that, no strong opinions about it. Anyway, I've edited the filter to address the concern I previously had. It has changed the meaning, so please review. It still needs some work methinks. -- zzuuzz (talk) 18:30, 3 August 2024 (UTC)
- I disagree with setting this to disallow. I've sent the reasons to a new thread on the mailing list. 0xDeadbeef→∞ (talk to me) 15:14, 3 August 2024 (UTC)
Recurring Hindi vandalism
[edit]There have been edits of Hindi vandalism that have references to violence (including sexual violence) with very similar patterns. These edits, which merit revision deletion, should be disallowed. A new filter may need to be added. I saw a pattern with those recent edits:
- Special:AbuseLog/38383740
- Special:AbuseLog/38318102
- Special:AbuseLog/38235628
- Special:AbuseLog/38230745
- Special:AbuseLog/38216602
- Special:AbuseLog/38213790
- Special:AbuseLog/38175638
- Special:AbuseLog/37768642
- Special:AbuseLog/37489599
- Special:AbuseLog/36989457
- Special:AbuseLog/36367421
This has been recurring for about a year (from one year ago there is Special:AbuseLog/35487610). Eyesnore talk💬 15:09, 4 August 2024 (UTC)
- Just to note that's User:Master12112wp. Filter 1231 has some relevant content. -- zzuuzz (talk) 16:51, 4 August 2024 (UTC)
- According to the LTA case, filter 1160 (hidden) is mentioned and enabled, but I believe none of the recent edits with changes similar to the one I mentioned triggered that filter. Eyesnore talk💬 17:24, 4 August 2024 (UTC)
CAPTCHA consequence for edit filters
[edit]Hello all! I've been keeping an eye on this one for a couple days, but requiring someone to complete a CAPTCHA is finally enabled as an edit filter consequence. The full description is "Require the user to complete a CAPTCHA in order to proceed with the action. Users with permission to skip a CAPTCHA are exempt." This, of course, means that autoconfirmed users won't be affected by it, but it would require any new and unregistered users who hit a filter to complete a CAPTCHA, meaning it may be a somewhat effective tool at slowing down spambots and IP-only vandals. EggRoll97 (talk) 11:53, 7 August 2024 (UTC)
- How about this, for example:
- 13:25, August 7, 2024: Example triggered filter 1, performing the action "edit" on Wikipedia:Sandbox. Actions taken: Show CAPTCHA; Filter description: General test filter (details | examine | debug)
- Instead of showcaptcha, we just say Show CAPTCHA. Also, two questions:
- Thank you. Codename Noreste 🤔 Talk 17:25, 7 August 2024 (UTC)
- I verified that EFM's can enable the captcha consequence without also being admins (see log). — xaosflux Talk 19:31, 7 August 2024 (UTC)
Proposal for 1157 update
[edit]1157 catches tagging even if the Template prefix is used, but it fails to catch edits using the TM: alias, the msg: prefix, or both (as in msg:TM:
or msg:Template:
which also work). See Special:Diff/1239799166 and Special:Diff/1239799326. Pinging @DannyS712 who added the Template: check. Nickps (talk) 16:40, 11 August 2024 (UTC)
- We should also add (
Sir Sputnik \(mobile\)
) to the ignoreusers string per this. Codename Noreste 🤔 Talk 16:45, 11 August 2024 (UTC) - Actually, you should probably ignore this since it's actually impossible to catch everything with an edit filter. Things like {{soc{{void}}k}} cannot be caught with a regex. But, if you decide to add something anyway, I forgot to mention in my original request that things like {{w:sock}}, {{en:sock}} as well as any combinations like {{MSG:w:w:en:en:en:w:TM:sock}} are also valid. Nickps (talk) 08:13, 12 August 2024 (UTC)
Special:AbuseFilter/957 and disambiguation pages
[edit]An anon's attempt to do this edit was disallowed by Special:AbuseFilter/957, designed to stop removal of article lead sections. However, the page in question, NDS, is a disambiguation page, and the edit was merely splitting it into topic-based sections. I believe that disambiguation pages should be excluded from this specific filter. Animal lover |666| 05:47, 14 August 2024 (UTC)
- WP:EFFPR may be a good place to report these in the future. –Novem Linguae (talk) 08:49, 14 August 2024 (UTC)
- I came here after a report was filed by the anon in question. Animal lover |666| 16:50, 14 August 2024 (UTC)
I think filters similar to 1154 would be suitable to use the new show CAPTCHA function. Opinions? Lordseriouspig 11:28, 14 August 2024 (UTC)