Jump to content

Wikipedia:Edit filter/Requested

From Wikipedia, the free encyclopedia
    Requested edit filters
    Shortcuts

    This page can be used to request edit filters, or changes to existing filters. Edit filters are primarily used to address common patterns of harmful editing.

    Private filters should not be discussed in detail. If you wish to discuss creating an LTA filter, or changing an existing one, please instead email details to wikipedia-en-editfilters@lists.wikimedia.org.

    Otherwise, please add a new section at the bottom using the following format: 

    == Brief description of filter ==
*'''Task''': What is the filter supposed to do? To what pages and editors does it apply?
*'''Reason''': Why is the filter needed?
*'''Diffs''': Diffs of sample edits/cases. If the diffs are revdelled, consider emailing their contents to the mailing list.
~~~~

    Please note the following:

    • Edit filters are used primarily to prevent abuse. Contributors are not expected to have read all 200+ policies, guidelines and style pages before editing. Trivial formatting mistakes and edits that at first glance look fine but go against some obscure style guideline or arbitration ruling are not suitable candidates for an edit filter.
    • Filters are applied to all edits. Problematic changes that apply to a single page are likely not suitable for an edit filter. Page protection may be more appropriate in such cases.
    • Non-essential tasks or those that require access to complex criteria, especially information that the filter does not have access to, may be more appropriate for a bot task or external software.
    • To prevent the creation of pages with certain names, the title blacklist is usually a better way to handle the problem - see MediaWiki talk:Titleblacklist for details.
    • To prevent the addition of problematic external links, please make your request at the spam blacklist.
    • To prevent the registration of accounts with certain names, please make your request at the global title blacklist.
    • To prevent the registration of accounts with certain email addresses, please make your request at the email blacklist.

    Click here to create a new request



    New users adding sock / block templates to other user's pages

    [edit]
    • Task: Disallow new users / IPs from adding block templates including sock blocking templates to users that aren't blocked
    • Reason: In general there's almost no reason for any but the most seasoned IPs or new accounts to add block templates that are typically automatically added by the blocking admin. Either a total block of new users adding block templates, or only for non-blocked accounts.
    • Diffs: Special:Diff/1184722881 (likely) single-time vandal doing this type of disruption happening on an administrator's page. This user may have been auto-confirmed, so this may need to apply to all non-ECP+ users.

    GeorgeMemulous (talk) 23:57, 7 September 2024 (UTC)[reply]

    I'm making some regex right now, but what I'm concerned about is that this edit is from over a year ago. Do you have any other more recent examples? Because otherwise, it wouldn't be necessary to create a whole new filter. – PharyngealImplosive7 (talk) 02:11, 8 September 2024 (UTC)[reply]
    Don't we already have 1157 (hist · log) that does this purpose? Codename Noreste 🤔 Talk 03:00, 8 September 2024 (UTC)[reply]
    Clearly that didn't stop this particular instance of disruption. Although, I can't think of many times this was added recently. I do know of an LTA that's recently been adding unblock requests to their own pages as an already unblocked account, so maybe that could be added? Either way, disruption is disruption, but if it isn't that common I suppose a filter is unnecessary. GeorgeMemulous (talk) 18:35, 8 September 2024 (UTC)[reply]
    Just stumbled upon an example from just now of a disruptive editor adding a block template to an unblocked IP's page. See here. Not disallowed by any existing filter. GeorgeMemulous (talk) 23:56, 9 September 2024 (UTC)[reply]
    803 (hist · log) could probably also be adjusted for sleeper accounts like this one. Nobody (talk) 05:44, 9 September 2024 (UTC)[reply]

    Duplicate Disambiguation Entries

    [edit]
    • Task: Disallow edits to disambiguation pages that add an entry already on the page.
    • Reason: This filter would be useful on long disambiguation pages such as King (disambiguation), where adding a duplicate entry is easy.
    • Diffs: Special:Diff/1243174404

    Faster than Thunder (talk | contributions) 22:57, 12 September 2024 (UTC)[reply]

    Does this happen often? If it happens once every few months occassionally, it seems like a filter isn't worth it. Do you have edits recently done by multiple editors that are duplicate disambiguation entries? – PharyngealImplosive7 (talk) 01:13, 13 September 2024 (UTC)[reply]
    I am wondering if there is not a way to provide a pre=save notice to the editor, rather than blocking the edit altogether. BD2412 T 03:12, 13 September 2024 (UTC)[reply]
    That sounds like a warning filter with a custom warning message. Nobody (talk) 08:59, 13 September 2024 (UTC)[reply]

    Disallow ranges of IPs who are adding unsourced bloats to Argentine demographics

    [edit]
    • Task: Disallow edits from particular IP ranges changing demographics of immigrants in Argentina (and hopefully, later expandable to other Latin American countries that they target). The list of ranges are in Wikipedia:Administrators' noticeboard/IncidentArchive1167#Unsourced bloat on Argentine demographics. These IP ranges are shared with other editors, but most if not all changes on numbers about Argentina are the same kind of bloats.
    • Reason: To stop the persistent unsourced bloats/hoaxes on demographics of Argentines etc., which appear to come from the same editors hopping around.
    • Diffs: Patterns per article title:

    While investigating this case, I noticed some of their edits were caught by an edit filter eg. [1], [2], [3], [4]. I wonder if that filter (or anything else) can be refined to more comprehensively prevent them, hence this request. --Wotheina (talk) 02:57, 29 September 2024 (UTC)[reply]

    School articles

    [edit]
    • Task: Prevent vandalism to school articles
    • Reason: There's some sort of social media competition going on to insert the name of a rapper as head teacher of the editor's school. These are not setting off any other filters and are being missed.
    • Diffs: [5] [6] [7] [8] [9] [10] [11] [12] [13] [14] [15] [16] [17] [18] [19] [20] [21] [22]
    • Match: new editor or IP and inserting Sean Combs or Sean "Diddy" Combs or Diddy or Diddler or Sean John or Puff Daddy or P Diddy (and variations). Refinement: perhaps trigger only if the article has school or academy or similar words in the article title. 81.2.123.64 (talk) 11:36, 30 September 2024 (UTC)[reply]
    Seeing this a lot right now. Would be best to filter by Category:High schools as well. Catalyzzt (talk) 14:34, 30 September 2024 (UTC)[reply]
    Maybe not directly related to the tiktok trend, but since I started working on reverting Diddy vandalism, I've also noticed youtubers often being similarly inserted into articles, most notably Markiplier as seen with these diffs [23][24][25][26][27][28] LaffyTaffer (talk) 20:30, 30 September 2024 (UTC)[reply]
    I think we could just add some regex to filter 614 (hist · log), which covers these meme trends. Some regex we could add could be (?:sean\s(?:\"?diddy\"?\s)?(?:(?:combs)|(?:john)))|(?:p?\s?didd(?:(?:y)|(?:ler)))|(?:puff\sdaddy)|(?:p\sdiddy) to the already existed filter. – PharyngealImplosive7 (talk) 23:35, 30 September 2024 (UTC)[reply]

    Comment Disruption is still ongoing and indeed a disruption-only account for this specific type of disruption has popped up: see Special:diff/1248790500 — Preceding unsigned comment added by GeorgeMemulous (talk • contribs) 14:09, 1 October 2024 (UTC)[reply]

    Still ongoing. It's relentless. — ClaudineChionh (she/her · talk · contribs · email) 22:53, 2 October 2024 (UTC)[reply]
    • Related: We have an existing filter — changing height and/or weight — that could be adapted here. I’m assuming it works by spotting changes in infoboxes. If so, the same filter could be used to flag changes to principal= and superintendent= in the schools infobox. 81.2.123.64 (talk) 00:05, 3 October 2024 (UTC)[reply]

    Disallow extremely large edits

    [edit]
    • Task: Disallow editors from making extremely large disruptive edits to pages. This should not apply to undoing previous vandalism, nor should it apply to existing redirects or new pages; this only should apply to the addition of large amounts of text to a page.
    • Reason: There's almost no purpose for edits over a specific size threshold to be sent to mainspace; I would guess they'd be only disruptive. Any individual edit larger than the largest article (currently Opinion polling for the 2024 United Kingdom general election, 885,708 bytes), or perhaps a lower threshold of around 500,000 bytes should be disallowed and not allowed to exist as a diff (Wikipedia is not a file host and these edits would take up a significant and unnecessary amount of space). These edits, while typically quickly reverted, really shouldn't happen in the first place.

    Diffs: Special:Diff/1248611730 - A WP:GAMEing editor adding 1.6 million bytes of disruptive content to a WP:BLUELOCK page. GeorgeMemulous (talk) 16:12, 30 September 2024 (UTC)[reply]

    I mean that's clearly an LTA, so it would probably be better to discuss this in the recommended places (mentioned in the red banner that shows up in the edit notice of this page).
    On the other hand, is any amount of filtering going to stop them from being disruptive with less bytes? If the edits are quickly reverted that seems good enough?
    Mind you, ignoring the LTA part, we do have a filter that prevents 1 million+ bytes changes, though expanding it to cover extended-confirmed users might warrant discussion. – 2804:F1...11:99EF (talk) 20:47, 30 September 2024 (UTC)[reply]
    I wasn't interested in this as an LTA case. ECP users shouldn't be able to make million-byte edits either, I would think? Either way, anyone else who games the system or uses a compromised account can produce this form of disruption. I'd personally set the limit at 500,000 as well, but 1,000,000 is a number we can all agree on. GeorgeMemulous (talk) 21:24, 30 September 2024 (UTC)[reply]
    The existing filter is 812 (hist · log) ("Unreasonably large addition of content"). Honestly it should at least be changed to apply to autoconfirmed users.
    This board can be a bit slow and, if my reading of past edits in this board is accurate, it's better if there's nothing left to discuss (like reaching a consensus elsewhere on what amount of bytes should be unacceptable and if extended confirmed users should or shouldn't be permitted to make such edits). – 2804:F1...11:99EF (talk) 22:05, 30 September 2024 (UTC)[reply]
    This does make sense. @EggRoll97 could you change line 1 to !contains_any(user_groups, "extendedconfirmed", "sysop", "bot") &? Nobody (talk) 07:54, 7 October 2024 (UTC)[reply]

    Warn and tag creations that may violate NOTCHANGELOG

    [edit]

    Here is some of the filter code which can be further refined: 

    page_title rlike ".*version history" & page_last_edit_age == null

    Message:

    Awesome Aasim 19:35, 1 October 2024 (UTC)[reply]

    (Non-EFH comment) These type of issues often also occurs when new editors publishes a draft about a software, they just make a bulleted list of updates and changes... My only concern is that these shenanigans aren't really that common. ABG (Talk/Report any mistakes here) 23:51, 3 October 2024 (UTC)[reply]
    If only there was some intelligent way to detect this... ahhh.... We probably need some sort of AI-powered abuse filter to help detect and warn about these common mistakes. Awesome Aasim 16:48, 4 October 2024 (UTC)[reply]
    We probably would get false positives no matter how we do this, so tagging might be too much. Nobody (talk) 07:43, 7 October 2024 (UTC)[reply]
    Recent changes has 12 tags starting with 'possible' and one starting with the word 'possibly', false positives are expected in all of those. – 2804:F1...32:A716 (talk) 07:59, 7 October 2024 (UTC)[reply]

    Edit filter for copy-paste pagemoves

    [edit]
    • Task: Prevent copying drafts into the article space. This would apply to all editors, and would target the article space.
    • Reason: a very common entry in Category:Candidates for history merging these days is a page that was copy/pasted from the draft space, either because there is an existing redirect in the way or because the page was draftified and the creator (or someone else) likely does not know how to request a redirect be deleted (usually via {{db-move}} or WP:RM/TR).
    • Diffs: Special:Diff/1248536996, Special:Diff/1249173005

    I'll note that this sort of filter will not necessarily stop copy/paste pagemoves from the draft space where the article is a redlink (e.g. Special:Diff/1245946107 or Special:Diff/1249205898) but it will hopefully stop copy/pastes over redirect. Primefac (talk) 21:11, 5 October 2024 (UTC)[reply]

    Retrieved from "https://en.wikipedia.org/w/index.php?title=Wikipedia:Edit_filter/Requested&oldid=1249868789"