Wikipedia:Edit filter noticeboard

"WP:EFN" redirects here. For information on the {{efn}} template, see WP:EXPLNOTE.

Welcome to the edit filter noticeboard

WATCH Recent filter changes (): Filter 1267 (new) — Actions: disallow; Flags: enabled,private; Pattern modified Last changed at 13:10, 22 September 2023 (UTC) Filter 971 — Pattern modified Last changed at 00:28, 20 September 2023 (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, 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 304 enabled filters and 37 stale filters with no hits in the past 30 days. Filter condition use is ~873, out of a maximum of 2000. (). See also the profiling data and edit filter graphs. Click here to start a new discussion thread

FilterDebugger

For a while now, I've building a tool to replace Special:AbuseFilter/test with something more useful. It's been lurking on my local machine, slowly congealing more features as they occur to me, and it feels a bit selfish to leave it there. It needs some work still, but I'm curious as what y'all think of think of what I've done so far. Features:

• See which part of edit matched the regex
• See which part of the regex matched the edit
• Immediate response as you type; no need to submit anything to a server and wait
• Test any batch size that will fit in memory
• Test from recent changes, older revisions, abuse logs, or a local file
• Does not require EFH/EFM access; all the tests are run client-side, so anyone can use it

Of course, there are going to be lots of bugs. And I can't replicate every feature of PCRE with JavaScript regexes. But for most filters, it should produce reasonably accurate results.

Anyway, if you are on a modern, up-to-date browser, try installing User:Suffusion of Yellow/FilterDebugger.js, and navigating to Special:BlankPage/FilterDebug/filter/614. Please report bugs, and suggest improvements! Suffusion of Yellow (talk) 22:50, 3 August 2023 (UTC)

This is outstanding! Thanks so much for taking the time to improve a tool that, to be honest, has needed improvement for awhile. I’m going to install it now! - 🔥𝑰𝒍𝒍𝒖𝒔𝒊𝒐𝒏 𝑭𝒍𝒂𝒎𝒆 (𝒕𝒂𝒍𝒌)🔥 23:55, 4 August 2023 (UTC)

Update: I’m getting the error: Sorry, but your browser is too old to support FilterDebugger.

My browser is the latest chrome browser, so I’m not sure how it’s too old. - 🔥𝑰𝒍𝒍𝒖𝒔𝒊𝒐𝒏 𝑭𝒍𝒂𝒎𝒆 (𝒕𝒂𝒍𝒌)🔥 23:59, 4 August 2023 (UTC)

@Illusion Flame: Can you try again? I made that message a bit more detailed. (And what version exactly?) Suffusion of Yellow (talk) 00:45, 5 August 2023 (UTC)

Ooh, that looks super nice. Works for me. Galobtter (talk) 21:43, 5 August 2023 (UTC)

I have been using this for false positive reports and it has been working perfectly! Thanks for creating this amazing tool. 0xDeadbeef→∞ (talk to me) 02:53, 26 August 2023 (UTC)

• @Suffusion of Yellow: Doesn't work on my iPad in either Microsoft Edge or Safari. Is this a desktop-only feature? Taking Out The Trash (talk) 18:13, 5 September 2023 (UTC)

  @Taking Out The Trash: Does your version of Safari support regex behind? That was only added a few months ago, and there's really no easy way to evaluate many PCRE regexes without it. \b in JavaScript means an ASCII word boundary, so the \bs are turned into (in the worst case) (?:(?![^\p{L}\p{N}_])(?<![\p{L}\p{N}_])|(?![\p{L}\p{N}_])(?<![^\p{L}\p{N}_])). AFAIK Edge on iOS will use the same version of WebKit as Safari, so will have the same problem.

  Adding: I briefly tested this with a a Linux WebKit-based browser and nothing was obviously broken, so it should in theory work with the latest versions of Safari. Suffusion of Yellow (talk) 22:15, 5 September 2023 (UTC)

Thank you for this, this is fantastic. ProcrastinatingReader (talk) 12:59, 18 September 2023 (UTC)

Impostor/attack accounts

The string "Harushiga" (User:Harushiga) should be added to the username blacklist as this user is frequently impersonated by trolls. Partofthemachine (talk) 00:44, 16 August 2023 (UTC)

You meant the socks of AudiGuy-1204? ToadetteEdit ^(chat)/_(logs) 18:30, 17 August 2023 (UTC)

Typically, per WP:DENY, it's correct to refer vaguely to "trolls" and "LTAs" instead of naming names if at all possible. casualdejekyll 21:19, 19 August 2023 (UTC)

Primarily, but they are sometimes impersonated by other LTAs as well. Partofthemachine (talk) 02:33, 21 August 2023 (UTC)

Removing button from MediaWiki:abusefilter-warning-empty-edit-request

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.

---

Having a blue button will just direct people to create a false positive report without reading through the actual message. People are less likely to make false positive reports if we only have the link but not the button. 0xDeadbeef→∞ (talk to me) 04:58, 27 August 2023 (UTC)

It seems reasonable to remove the big blue button; we want people to fully read that one, and it probably actually makes it less likely that we'll ever see the content of that edit request. — Red-tailed hawk _(nest) 02:42, 28 August 2023 (UTC)

Agreed. casualdejekyll 23:55, 28 August 2023 (UTC)

The discussion above 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.

WPWP Nigerian photo competition filter 1258

... Has been handily circumvented by Chinemeremprince, who I just blocked. Just letting people more experienced with edit filters know. Also pinging Materialscientist, who had some dealings with this user and has done things with filters. Graham87 09:10, 27 August 2023 (UTC)

They aren't participating in WPWP if they don't use a hashtag. 0xDeadbeef→∞ (talk to me) 13:42, 27 August 2023 (UTC)

Yeah, this is intended. I do wonder exactly how much collateral there would be to disallowing "WPWP", though. (Don't think it'd be common enough to test.) casualdejekyll 00:04, 29 August 2023 (UTC)

They've just reached out and apparently thought they were using a hashtag, or something ... Graham87 (talk) 08:20, 21 September 2023 (UTC)

Edit request for Efilter 1076

Would it possible to exclude admins from Efilter 1076? Admins generally should be trusted and don't need to be tracked when they move articles to Draft space. -- Sohom (talk) 16:15, 8 September 2023 (UTC)

Sohom, thanks for the message. On that ground, we might get a request to extend the argument to autopatrollers too, but it might not be prudent either way. The tracker, similar to page deletion logs, allows these actions to recorded for future history. This is just an EF tracker and does not impede any edit either way by warning or preventing. Thanks, Lourdes 04:48, 18 September 2023 (UTC)

Ah, good point, I hadn't thought about this from that point-of-view :) Sohom (talk) 14:39, 18 September 2023 (UTC)

On the other hand, that filter probably should be set to warn so people know they shouldn't do this, in which case exempting admins would make sense. * Pppery * _{it has begun...} 23:11, 20 September 2023 (UTC)

Should edit filter 971 have detected this?

I came across a log of filter 971 triggering(<log>) and upon checking the user's contributions I noticed that they were the one who added the original image as well (<diff>) - the original image is also a missing file, however only the attempt to change it to a ".png" triggered the filter's warning, not the initial edit, because the filter does not check for ".webp" images.

Is adding a link to a missing ".webp" file something the filter should be detecting and warning for? – 2804:F14:80FB:2E01:9513:7B7D:14E3:DEDD (talk) 00:15, 19 September 2023 (UTC)

I've added the webp extension to the filter. 0xDeadbeef→∞ (talk to me) 00:28, 20 September 2023 (UTC)