Jump to content

Wikipedia:Edit filter noticeboard

From Wikipedia, the free encyclopedia
    Welcome to the edit filter noticeboard
    Filter 960 — Pattern modified
    Last changed at 16:55, 11 June 2025 (UTC)

    Filter 614 — Pattern modified

    Last changed at 22:56, 10 June 2025 (UTC)

    Filter 1170 — Pattern modified

    Last changed at 15:39, 8 June 2025 (UTC)

    Filter 1347 — Pattern modified

    Last changed at 01:50, 8 June 2025 (UTC)

    Filter 812 — Pattern modified

    Last changed at 22:06, 7 June 2025 (UTC)

    Filter 50 — Pattern modified

    Last changed at 23:49, 6 June 2025 (UTC)

    Filter 113 — Pattern modified

    Last changed at 00:09, 7 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.



    [edit]

    Filter 231 uses !(added_links to remove urls from the filter, but this has the effect that this edit doesn't get picked up by it, due to {{coord}} (produces a geohack.toolforge url) from {{Infobox French commune}} grabbing type as a optional parameter, which includes the population number. This has the effect that changes to | population can never be picked up by filter 231. I don't think this is the desired behaviour. Nobody (talk) 08:14, 12 May 2025 (UTC)[reply]

    From what I see this effects at least all 573k uses of {{Infobox settlement}}. Nobody (talk) 08:23, 12 May 2025 (UTC)[reply]
    Maybe something like !(added_lines irlike "\|\s*population\s*=\s*\d") would work, but we may need more narrow regex. – PharyngealImplosive7 (talk) 16:00, 14 May 2025 (UTC)[reply]
    I had to fix the regex above by removing the multiple/duplicate backslashes. Codename Noreste (talk · contribs) 05:06, 15 May 2025 (UTC)[reply]

    Has been set to disallow by me. I'm not opposed to making this a throttle and/or merge this into another filter (LTA ranges?).

    Do not discuss specifics here, please use the mailing list. beef [talk] 08:08, 19 May 2025 (UTC)[reply]

    Extensions to filter 39 for Welsh schools

    [edit]

    I've noticed plenty of articles about schools in Wales use their Welsh-language names as titles, often containing the word 'ysgol' - Category:Welsh-language schools has quite a few examples. Kids being what they are means these pages get their fair share of vandalism, so would it be worth including 'ysgol' in the titles targeted by filter 39 (for school-related article vandalism etc.) to make disruption to these pages easier to catch? Entranced98 (talk) 18:08, 19 May 2025 (UTC)[reply]

     Done This seems like a helpful edition, and I don't see too many problems given how narrow the filter string is. EggRoll97 (talk) 03:10, 20 May 2025 (UTC)[reply]
    Thanks, much appreciated! Entranced98 (talk) 10:23, 20 May 2025 (UTC)[reply]

    Why is the filter 34 private?

    [edit]

    I understand this is a private filter, so this can't be discussed in-detail here, but I would assume that the pattern for the filter would not warrant being private, unless there is a specific reason why ofc. Otherwise it might be worth changing to Public. Opinions? Lordseriouspig 07:20, 26 May 2025 (UTC)[reply]

    Was made private in 2009. I currently don't see why it should be made private, unless it also catches attempts to dox another editor or something. beef [talk] 09:58, 26 May 2025 (UTC)[reply]
    Making the filter public may make evading the filter too easy for some LTAs. Reviewing the logs, it does look like a significant number of recent matches are LTA socks. Daniel Quinlan (talk) 13:10, 26 May 2025 (UTC)[reply]
    Interesting, I would have assumed that the filter would be similar to filter 3, but if it would be easily bypassed, I would agree that it should be kept private. Lordseriouspig 20:35, 26 May 2025 (UTC)[reply]
    Obviously I can't see what it's filtering, but I suppose the question is whether whatever it was doing in 2009 is still ongoing 15 years later? Fortuna, imperatrix 10:04, 26 May 2025 (UTC)[reply]
    Filter history indicates that it was, at least for some time, a targeted filter, therefore BEANS applied and making it private made sense. Not sure if the filters purpose hasn't changed over time. Nobody (talk) 11:32, 26 May 2025 (UTC)[reply]
    I concur with Daniel that it's worth keeping that filter private. Codename Noreste (talk · contribs) 19:31, 26 May 2025 (UTC)[reply]

    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)[reply]

    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)[reply]
    @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)[reply]
    Mail sent, probably a skin issue since I'm using Vector legacy. Nobody (talk) 08:40, 13 June 2025 (UTC)[reply]
    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)[reply]
    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)[reply]
    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)[reply]
    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)[reply]