Wikipedia:Edit filter noticeboard
- Last changed at 14:39, 25 June 2025 (UTC)
Filter 797 — Flags: disabled
- Last changed at 12:25, 25 June 2025 (UTC)
Filter 1286 (deleted) — Flags: disabled
- Last changed at 06:53, 25 June 2025 (UTC)
Filter 1278 — Flags: disabled
- Last changed at 00:40, 25 June 2025 (UTC)
Filter 1022 — Flags: disabled
- Last changed at 22:59, 24 June 2025 (UTC)
Filter 1175 (deleted) — Flags: disabled
- Last changed at 23:19, 24 June 2025 (UTC)
Filter 1259 (deleted) — Flags: disabled
- Last changed at 23:14, 24 June 2025 (UTC)
Filter 1265 (deleted) — Flags: disabled
- Last changed at 23:14, 24 June 2025 (UTC)
Filter 1163 — Pattern modified
- Last changed at 16:58, 21 June 2025 (UTC)
This is the edit filter noticeboard, for coordination and discussion of edit filter use and management.
If you wish to request an edit filter or changes to existing filters, 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 350 enabled filters and 48 stale filters with no hits in the past 30 days. Filter condition use is ~1030, out of a maximum of 2000. ( ).
Index 1, 2, 3, 4, 5, 6, 7, 8, 9, 10 11, 12, 13, 14, 15 |
This page has archives. Sections older than 10 days may be automatically archived by Lowercase sigmabot III. |
Unfiltered user script
[edit]While I started writing User:Daniel Quinlan/Scripts/Unfiltered to help administrators with vandalism and other abuse, I've also found it useful when working on edit filters, reviewing EFFPR reports, etc. so I figured it might be worth mentioning it here. The script provides a complete view of user edit activity on user contributions pages by displaying edit filter hits, including removed and unsuccessful edits. Deleted contributions are also shown for administrators.
If you already use User:Ingenuity/AbuseFilterContribs.js, this new script similarly displays disallowed edits, but it does a lot more than that (you won't want to load both scripts at once). Any feedback is appreciated! Daniel Quinlan (talk) 03:23, 13 June 2025 (UTC)
- I think the colors could need some improvements, the contrast ratio on some could be improved. The dark mode gadget also has a issue with the yellow and the aquamarine of the warn and tag filters. Nobody (talk) 05:36, 13 June 2025 (UTC)
- @1AmNobody24: The colors seem reasonable to me, especially on dark mode (I'm using dark mode on Vector 2022). Could you send me an email with a screenshot, pointing out the issues and linking the page? Note that you can also modify the styling with CSS in your common.css page. The CSS is here in the code. Thanks. Daniel Quinlan (talk) 08:23, 13 June 2025 (UTC)
- Mail sent, probably a skin issue since I'm using Vector legacy. Nobody (talk) 08:40, 13 June 2025 (UTC)
- Ouch. It looks like the dark mode colors are being used in light mode and vice versa. I'll try to see if I can reproduce the issue with Vector legacy to see if there's an easy fix, but I'm probably not going to spend a ton of time fixing things for legacy skins. Daniel Quinlan (talk) 09:18, 13 June 2025 (UTC)
- Another thing I'm wondering right now is why I don't see some filter hits while looking at the contributions of a IP range. Nobody (talk) 11:50, 13 June 2025 (UTC)
- That should work although there has to be at least one normal contribution visible for the specific IP. Which IP range and which hits? You can email me if needed. Daniel Quinlan (talk) 16:43, 13 June 2025 (UTC)
- That explains it. 213.145.66.94 is the IP I was looking at. Nobody (talk) 08:38, 14 June 2025 (UTC)
- @1AmNobody24: Were you looking at 213.145.66.94 as part of a range or were you looking at just that one address? The latter shows the filter hit for me as expected. It's only ranges that require a contribution before an individual IP is checked. Daniel Quinlan (talk) 10:30, 14 June 2025 (UTC)
- I was looking at the /24 range as it's a VPN proxy used by the LTA of filter 1321. While doing that and looking at the recently blocked IPs of that range, 213.145.66.94 came up and I wondered why I wasn't able to see it while looking at the range. Nobody (talk) 10:56, 14 June 2025 (UTC)
- @1AmNobody24: I added a new button to query any IPs lacking visible contributions if it's a /24 or smaller IPv4 range. It even starts automatically when there are zero visible contributions, but it's a bit slow and expensive so it doesn't run automatically otherwise. Doing this for IPv6 is a non-starter for obvious reasons. Thanks for the feedback! Daniel Quinlan (talk) 02:43, 16 June 2025 (UTC)
- I made another improvement to help alleviate the issue of IP addresses lacking visible contributions. For small IPv4 ranges, it now also automatically queries IPs that have user talk pages. Daniel Quinlan (talk) 04:32, 16 June 2025 (UTC)
- I was looking at the /24 range as it's a VPN proxy used by the LTA of filter 1321. While doing that and looking at the recently blocked IPs of that range, 213.145.66.94 came up and I wondered why I wasn't able to see it while looking at the range. Nobody (talk) 10:56, 14 June 2025 (UTC)
- @1AmNobody24: Were you looking at 213.145.66.94 as part of a range or were you looking at just that one address? The latter shows the filter hit for me as expected. It's only ranges that require a contribution before an individual IP is checked. Daniel Quinlan (talk) 10:30, 14 June 2025 (UTC)
- That explains it. 213.145.66.94 is the IP I was looking at. Nobody (talk) 08:38, 14 June 2025 (UTC)
- That should work although there has to be at least one normal contribution visible for the specific IP. Which IP range and which hits? You can email me if needed. Daniel Quinlan (talk) 16:43, 13 June 2025 (UTC)
- Another thing I'm wondering right now is why I don't see some filter hits while looking at the contributions of a IP range. Nobody (talk) 11:50, 13 June 2025 (UTC)
- Trying to support legacy skins with the dark mode gadget is a dubious use of time and effort. The gadget is an outdated hack that causes heaps of problems mostly avoided by Vector 2022's dark mode. I've updated the fallback colors to have better contrast in both light and dark modes, which means they're ultimately a compromise. If you want better colors than the new fallbacks, you'll need to override them in your own CSS.
- I'd also strongly recommend switching to Vector 2022. It was a bit jarring at first, but with a few tweaks it's been great, especially for dark mode. Daniel Quinlan (talk) 22:15, 13 June 2025 (UTC)
- Ouch. It looks like the dark mode colors are being used in light mode and vice versa. I'll try to see if I can reproduce the issue with Vector legacy to see if there's an easy fix, but I'm probably not going to spend a ton of time fixing things for legacy skins. Daniel Quinlan (talk) 09:18, 13 June 2025 (UTC)
- Mail sent, probably a skin issue since I'm using Vector legacy. Nobody (talk) 08:40, 13 June 2025 (UTC)
- @1AmNobody24: The colors seem reasonable to me, especially on dark mode (I'm using dark mode on Vector 2022). Could you send me an email with a screenshot, pointing out the issues and linking the page? Note that you can also modify the styling with CSS in your common.css page. The CSS is here in the code. Thanks. Daniel Quinlan (talk) 08:23, 13 June 2025 (UTC)
- Arguably better than Ingenuity's script, IMO. And it works globally! Codename Noreste (talk · contribs) 07:55, 14 June 2025 (UTC)
- Thanks for this; I especially like the feature that shows which filter has disallowed/warned/tagged the edit in question. – PharyngealImplosive7 (talk) 09:32, 14 June 2025 (UTC)
- @Daniel Quinlan Could you take a look how the filter hits show on this account? It looks kinda off to me. Nobody (talk) 09:47, 16 June 2025 (UTC)
- It should be fixed now. Daniel Quinlan (talk) 12:03, 16 June 2025 (UTC)
Filter 1347 needs to recognise syntaxhiglight tags
[edit]This filter caught one of my edits as supposedly adding a protection template to an unprotected page. However, the addition was done between syntaxhighlight tags which escape wikitext (just like nowiki) so the page wasn't even tagged as protected. Despite this, my false positive report got denied and I was told not to add protection templates to unprotected pages even though I never did that (check the revisions. The page was not tagged because the template is escaped between the syntaxhighlight tags). Can someone just fix the filter so it doesn't keep catching valid edits. Warudo (talk) 19:09, 15 June 2025 (UTC)
- @Warudo:
Fixed EggRoll97 (talk) 03:03, 16 June 2025 (UTC)
- @EggRoll97: I generalized the fix to be based on the text rather than the page title since we can't really predict where people will make similar edits (and grouped it with the other exceptions in the filter). Daniel Quinlan (talk) 05:20, 16 June 2025 (UTC)
Tasnim
[edit]Requesting an edit filter for WP:TASNIMNEWSAGENCY, which although previously deprecated, is still used by unsuspecting or malicious editors thanks to the lack of a warning filter like in similar deprecated sources. Borgenland (talk) 07:53, 19 June 2025 (UTC)
- Instead of making a new filter, we could just add
tasnimnews
to the .com section of 869 (hist · log). – PharyngealImplosive7 (talk) 15:11, 19 June 2025 (UTC)
More slang for the filters?
[edit]I believe the word 'lolcow' should be added to at least one edit filter to warn/disallow for IPs and new accounts. It has very few legitimate uses on Wikipedia articles and holds a risk of being used for BLP violations, for example this vandalism that didn't trip any filters. Since this is Internet slang, could it go in filter 614, or in filter 1,296 and 1,297 if warning would be better at this stage? Entranced98 (talk) 13:01, 21 June 2025 (UTC)
- Is this vandalism really all that common to warrant being added to a filter, as we don't want use filter conditions for no reason? If so, could we see some more diffs of this type of vandalism? – PharyngealImplosive7 (talk) 22:46, 21 June 2025 (UTC)
- In agreement with the above, I'd like to see at least another diff or two demonstrating more widespread vandal usage. EggRoll97 (talk) 03:44, 22 June 2025 (UTC)
- Thanks for the input - while I have seen a couple more instances of this term's use for vandalism while trawling recent changes, I'll admit I can't quite remember the pages it happened on, silly me! I'll provide additional diffs if I catch some more incidents while patrolling though, and fresher vandalism will help to show if this is becoming an active trend. Happy to shelve this in the meantime. Entranced98 (talk) 14:38, 22 June 2025 (UTC)
- In agreement with the above, I'd like to see at least another diff or two demonstrating more widespread vandal usage. EggRoll97 (talk) 03:44, 22 June 2025 (UTC)
IPReputation variables
[edit]A couple days ago the IPReputation AbuseFilter integration was enabled. This adds a number of variables (id.) to Special:AbuseFilter, which could be useful for Special:AbuseFilter/1362 and the like. DatGuyTalkContribs 10:33, 24 June 2025 (UTC)
- I don't like that those are all protected variables. Nobody (talk) 11:03, 24 June 2025 (UTC)
- Courtesy ping to @Daniel Quinlan:. – PharyngealImplosive7 (talk) 15:49, 24 June 2025 (UTC)
- EFMs also may want to create a test IPReputation filter where they expirement with these variables and see how they work before adding them to any actual filter. – PharyngealImplosive7 (talk) 15:52, 24 June 2025 (UTC)
- Courtesy ping to @Daniel Quinlan:. – PharyngealImplosive7 (talk) 15:49, 24 June 2025 (UTC)
Potentially unneeded filters??
[edit]All the filters listed below are private; please avoid revealing details of them in public.
- 718 (hist · log): No hits since August 2024, and before that only sporadic hits from 2020 to 2024.
797 (hist · log): No real hits since 2019881 (hist · log): No hits since September 2021- 980 (hist · log): No hits since April 2024
1022 (hist · log): No hits since 20211175 (hist · log): No hits since February 2024- 1240 (hist · log): No hits since 2023
1259 (hist · log): No hits since January 20241265 (hist · log)??: No hits since October 20241278 (hist · log): No hits since 20231286 (hist · log): No hits since August 2024
Thanks – PharyngealImplosive7 (talk) 21:29, 24 June 2025 (UTC)
- I added LTA filter 881 as well. Codename Noreste (talk · contribs) 22:08, 24 June 2025 (UTC)
- It's probably worth pinging the primary authors (see Chesterton's Fence). I'll disable 1022. Per the filter notes, this LTA was active in late 2022; TBH I wouldn't be surprised if they return or are still around somewhere, but we can address that when it's identified. -- zzuuzz (talk) 22:58, 24 June 2025 (UTC)
- Courtesy pings to @Darkwind, MusikAnimal, Cyp, Galobtter, ToBeFree, Tamzin, DatGuy, Ingenuity, Daniel Quinlan, and Lustiger seth: – PharyngealImplosive7 (talk) 23:10, 24 June 2025 (UTC)
- I've deleted 1265 and 1259. —Ingenuity (t • c) 23:14, 24 June 2025 (UTC)
- Thanks for the ping! 1175 is indeed not needed anymore. Disabled and deleted. ~ ToBeFree (talk) 23:19, 24 June 2025 (UTC)
- I've disabled 1278. Daniel Quinlan (talk) 00:41, 25 June 2025 (UTC)
- Thanks for notification. I've deleted #1286 now. -- seth (talk) 06:54, 25 June 2025 (UTC)
- disabled 797. — xaosflux Talk 12:25, 25 June 2025 (UTC)
- 881 seems like OK to disable, AF target was replaced with a rangeblock already. — xaosflux Talk 12:29, 25 June 2025 (UTC)
- No objections to disabling #881 — disabled now. Cyp 14:40, 25 June 2025 (UTC)