Wikipedia:Edit filter/Requested
Requested edit filters |
---|
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-editfilterslists.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:
|
This page has a backlog that requires the attention of willing editors. Please remove this notice when the backlog is cleared. |
Index |
This page has archives. Sections older than 30 days may be automatically archived by ClueBot III when more than 1 section is present. |
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)
- I'm not sure if this has to do with why no one is replying, but I tried looking at the diffs when you first added them and found it hard to understand what type of edit you are asking for a filter about... presumably because you merged the histories of the pages and that changed the diffs. From a general description it also sounds difficult to figure out how detecting for copy-paste moves would work, seeing as the filter only has context of what is (and was) on the one page being edited in the action it triggered on.
- Is/was there something specific about these diffs that could be used to detect others like them? – 2804:F1...29:CE67 (talk) 00:20, 19 October 2024 (UTC)
- It basically boils down to "someone overwrites a redirect with a large amount of text and there is a draft at the same title"; from what I have seen that is almost always a copy/paste pagemove that requires a histmerge. Primefac (talk) 11:46, 19 October 2024 (UTC)
- Sorry for taking so long to reply.
- Unfortunately I don't think there is a way to know if an article exists at Draft:ArticleName from a filter action that happened at ArticleName unless there is a link to the draft in the new version (after the big addition) which would allow a search in the
new_html
for
. 1112 (hist · log) ("Notable people" disruption) does this.class="new" title="Draft:ArticleName
- This discussion for checking if it was a disambiguation link, for that same filter, thought it was not possible to
retrieve article content from a title
until someone brought that up. The variables(mediawiki) only seem to contain information about the page(s) where the action happened and/or about the user doing the action. - -
- On the other hand one of the edits did trigger and get tagged by 164 (hist · log) (Possible cut and paste moves). That filter works by checking, for users with less than 250 edits creating new pages (page_id 0), if the added content contains "[edit]" or maintenance templates to guess that it was copied from a different page; that's not as narrow as 'copied from the Draft', but it is something detectable at least.
- Now, would people agree with disallowing edits like that? I don't know.
- -
- I say this to more be informative, I hope others share their thoughts/ideas too. – 2804:F1...EE:EFBD (talk) 19:26, 21 October 2024 (UTC)
- It basically boils down to "someone overwrites a redirect with a large amount of text and there is a draft at the same title"; from what I have seen that is almost always a copy/paste pagemove that requires a histmerge. Primefac (talk) 11:46, 19 October 2024 (UTC)
Filter unsourced tornado / hurricane rating changes
edit- Task: Prevent or tag new editors that change tornado / hurricane intensity ratings without a source.
- Reason: This is a pretty common and obvious form of disruption, but it's hard to easily find using the edit history (most occur as a 0 byte change with no summary, similar to a standard typo fix) and an unsourced change is hardly ever helpful.
- Diffs:
- 2024 Greenfield tornado: IP editor changing EF4 to EF5 without a source. This diff is my reversion of those edits.
- 2024 Greenfield tornado: NOTHERE editor doing the same.
- 2024 Greenfield tornado: New editor doing the same.
- Tornado outbreak sequence of April 25 - 28, 2024: IP undoing previous vandalistic edits. Note that the bad edits had no summary.
- Tornado outbreak sequence of May 19 - 27, 2024: 1, 2, 3, and 4 edits by an LTA of this type of disruption. I know this LTA isn't the primary one doing this.
Also, I know this can happen with hurricanes; see the edits on Hurricane Beryl from early on July 2 and you'll see why it needed protection. GeorgeMemulous (talk) 13:37, 23 October 2024 (UTC)
- (denied removed) and Deferred to requests for page protection. The first diff you present seems like it was made in good faith (?) based on the edit summary alone, though I'm not too familiar with tornados. This seems to be something that pending changes would help with more than a filter, though. EggRoll97 (talk) 23:46, 23 October 2024 (UTC)
- Disruption has been ongoing since 2023 and isn't limited to those four pages, even if they are the most recent targets. Let me assemble a few more diffs from various pages: 2023 Rolling Fork tornado, 2021 Western Kentucky tornado, Tornado outbreak of March 31, 2023, Tornado outbreak of December 10, 2021, Tornadoes of 2020, 2015 Rochelle-Fairdale tornado, Tornadoes of 2014, Tornadoes of 2013, Tornadoes of 2013 again, Tornado outbreak of November 17, 2013, and one, two, three, and four instances on 2013 El Reno tornado. There are probably more out there and there are certainly more to come as this is one of the easiest ways to vandalize a tornado article (literally changing one number). Also note the first diff was a reversion to a clean version after multiple previous disruptive edits, as are at least one of these new examples. All tornado and tornado outbreak articles are vulnerable to this and disruption often occurs years after the event leaves the news cycle so protection may not be the way to go in my opinion. GeorgeMemulous (talk) 00:22, 24 October 2024 (UTC)
- Doing... Fair enough. I'll see if I can whip up a preliminary start to this. EggRoll97 (talk) 00:29, 24 October 2024 (UTC)
- I'll summarize a few points as you said you aren't too familiar with the topic:
- Tornadoes in the US and Canada are rated on the Enhanced Fujita scale, shortened to EF. This scale ranges from 0 to 5.
- Tornadoes in the rest of the world are often rated on the International Fujita scale, shortened to IF. Again, 0 to 5.
- Some countries still use the legacy Fujita scale, shortened to F. This goes from 0 to 12, but only 0 to 5 have ever been final.
- All are formatted similarly: F0, EF1, IF2, F3, EF4, IF5.
- Citations to verify typically come from the NCEI database or ESWD, but preliminary ratings often come from Twitter or a statement from the local NWS office.
- The TORRO scale is more or less unused and obscure to the point where it's an unlikely disruption target.
- Cheers! GeorgeMemulous (talk) 00:48, 24 October 2024 (UTC)
- Update, Still doing..., though at a fairly slow speed. If anyone wants to take over on coding, absolutely go ahead. Things in the real world have been taking a slight bit of a toll over the last bit. EggRoll97 (talk) 22:34, 30 October 2024 (UTC)
- I'll summarize a few points as you said you aren't too familiar with the topic:
- Doing... Fair enough. I'll see if I can whip up a preliminary start to this. EggRoll97 (talk) 00:29, 24 October 2024 (UTC)
- Disruption has been ongoing since 2023 and isn't limited to those four pages, even if they are the most recent targets. Let me assemble a few more diffs from various pages: 2023 Rolling Fork tornado, 2021 Western Kentucky tornado, Tornado outbreak of March 31, 2023, Tornado outbreak of December 10, 2021, Tornadoes of 2020, 2015 Rochelle-Fairdale tornado, Tornadoes of 2014, Tornadoes of 2013, Tornadoes of 2013 again, Tornado outbreak of November 17, 2013, and one, two, three, and four instances on 2013 El Reno tornado. There are probably more out there and there are certainly more to come as this is one of the easiest ways to vandalize a tornado article (literally changing one number). Also note the first diff was a reversion to a clean version after multiple previous disruptive edits, as are at least one of these new examples. All tornado and tornado outbreak articles are vulnerable to this and disruption often occurs years after the event leaves the news cycle so protection may not be the way to go in my opinion. GeorgeMemulous (talk) 00:22, 24 October 2024 (UTC)