User

Talk
link={{{3}}}
Dashboard

Articles

Scripts

Tools

Templates

Userboxes

Awards

Dashboard

User:Xenocidic/dashboard/users

Immediate requests Entries
Candidates for speedy deletion as attack pages 0
Wikipedians looking for help 0
Requests for unblock 90
Wikipedia semi-protected edit requests 85
Wikipedia extended-confirmed-protected edit requests 88
Wikipedia template-protected edit requests 5
Wikipedia fully protected edit requests 1
Wikipedia conflict of interest edit requests 25
Requested RD1 redactions 1
Candidates for speedy deletion as copyright violations 1
Candidates for speedy deletion 7
Open sockpuppet investigations 19
Click here to locate other admin backlogs


News

Edit filters

Requested edit filters (WP:EF/R)

Filter unsourced tornado / hurricane rating changes

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)
Update, probably don't see myself working on this, but a filter should be made. Not sure if anyone wants to pick this up by chance. EggRoll97 (talk) 04:55, 9 November 2024 (UTC)
@EggRoll97 and GeorgeMemulous: Here is some basic filter code we could use:
!("extendedconfirmed" in user_groups) &
page_namespace == 0 &
!(added_lines contains "<ref") & (
  scaleStr := "(?:E|I)?F[0-5]";
  removed_lines contains scaleStr &
  added_lines contains scaleStr
  !(removed_lines = added_lines)
)
What this should do is check if anyone is adding hurricane scale numbers and removing different ones without a source. Thanks, – PharyngealImplosive7 (talk) 17:50, 10 November 2024 (UTC).
Testing at 1324 Looks good for testing. I've been busy over the last bit, but I can toss this in and keep an eye on it (by the way, an & was forgotten at the end of line 6). Thanks! EggRoll97 (talk) 23:44, 10 November 2024 (UTC)
I think the current filter is broken that it could not catch the changes, even with FilterDebugger. contains would have to look for the entire phrase itself, while irlike is recommended for regex. Here's what I wrote instead:
page_namespace == 0 &
page_title irlike "hurricane|tornado" &
!contains_any(user_groups, "extendedconfirmed", "sysop", "bot") &
edit_delta <= 2 &
(
    scaleStr := "\b[EI]?F[0-5]\b";
    not_intensity_num := "[^0-5]";
    removed_lines rlike scaleStr &
    added_lines rlike scaleStr &
    str_replace_regexp(added_lines, not_intensity_num, "") != str_replace_regexp(removed_lines, not_intensity_num, "")
) &
!(summary irlike "^(?:revert|rv|undid)")

I am pinging both PharyngealImplosive7 and EggRoll97. Codename Noreste 🤔 Talk 01:30, 11 November 2024 (UTC)

I would suggest rlike since the scale ratings are usually marked with capital letters, but otherwise, looks good. Also do bots really make these changes? Anyways thanks for the help. – PharyngealImplosive7 (talk) 03:20, 11 November 2024 (UTC)
Bots make a lot of edits that change a line that doesn't contain '<ref' so excluding bots near the top means the filter doesn't needlessly check all the way to removed_lines or added_lines.
The last line's comparison seems unfinished, I think you meant to compare if the scale added is different than the one removed (i.e. not an unrelated change to the same line), but the current check is if removed and added lines are different, which is (surely?) always the case. – user usually at 2804:F14::/32, currently 143.208.239.58 (talk) 03:52, 11 November 2024 (UTC)
Modified the suggested code to use rlike for the regex, and added a condition piece to only target pages with the title tornado. Codename Noreste 🤔 Talk 04:14, 11 November 2024 (UTC)
Also, I noticed that you changed my original regex to (?:E|I)?F[0-5]{1,2}. Numbers above 5 are not used in any scale we are tracking, though they could exist theoretically on the Fujita Scale. As a result, I think you should delete the "{1,2}" part. – PharyngealImplosive7 (talk) 04:52, 11 November 2024 (UTC)
Looks good, though I've added hurricane to the page_title check, since this appears to occur with hurricane ratings as well. EggRoll97 (talk) 04:53, 11 November 2024 (UTC)
@EggRoll97: The regex also might need to be fixed, see my comment above. – PharyngealImplosive7 (talk) 04:56, 11 November 2024 (UTC)
{1,2} denotes that one minimum or two maximum numbers are allowed in the regex, but I will remove it from the filter's regex. Codename Noreste 🤔 Talk 05:05, 11 November 2024 (UTC)
And it's removed, PharyngealImplosive7. Note that I also changed (?:E|I)? to [EI]? as it only denotes a set of these two letters, so I don't think a non-capturing group is needed here. Codename Noreste 🤔 Talk 05:09, 11 November 2024 (UTC)
Yes that looks good. The IP in the conversation suggested we modify the last line of the regex (whether added lines is the same as removed lines. Any ideas on how to fix that like the IP said? – PharyngealImplosive7 (talk) 05:12, 11 November 2024 (UTC)
Maybe changing == to in would work? Codename Noreste 🤔 Talk 05:14, 11 November 2024 (UTC)
Just saw the comment about needing the regex fixed. Sorry, I was working on the filter with an old version of this page, so I didn't see the comment about fixing it until now. I've just removed the {1,2} from the regex, and changed (?:E|I)? to [EI]?. EggRoll97 (talk) 05:16, 11 November 2024 (UTC)
@EggRoll97: you should add word boundaries around that regex, this is matching %anything%F[0-5] making the [EI]? redundant.
Anon does have a point about comparing added/removed_lines. This checks if somebody edits an existing line containing that sequence but not if that sequence has been changed (this is what OP wants) - e.g.: if somebody solely adds a period somewhere in a line containing that sequence, this will trip. XXBlackburnXx (talk) 11:09, 11 November 2024 (UTC)
I've added the word boundaries, though I'm not sure if it's supposed to encase just the [EI] or the entirety of the string. Not sure about the comparison of added/removed. Codename Noreste's solution may work with changing == to in. EggRoll97 (talk) 13:29, 11 November 2024 (UTC)
I'm pretty sure it is supposed to encase the entire string like you have done, but about the changing of the == to in, I can second that idea. – PharyngealImplosive7 (talk) 14:38, 11 November 2024 (UTC)
And finally, this filter would probably also catch good-faith edits that are reverting this kind of vandalism, so I would suggest adding a line that says !(summary irlike "^(?:revert|rv|undid)") to the filter. – PharyngealImplosive7 (talk) 14:49, 11 November 2024 (UTC)
I've updated the code. – PharyngealImplosive7 (talk) 15:33, 11 November 2024 (UTC)
It's not the best, but you could technically replace all [^0-5] characters (with str_replace_regexp) in both added and removed lines with an empty string and then compare the resulting strings, supposedly what that then would be checking is if any 0 to 5 number was changed, removed or added in the edit (or swapped order...), which would probably reduce most of the potential false positives. A more ideal change would be to get all the matches and compare that, but I don't know how to do that efficiently. Mind you, this would replace the in version, though I'm unsure what that actually does.
Something else: Checking if it's a revert is cheap (and reverts happen often), could move that up. – 2804:F1...DF:61D4 (::/32) (talk) 16:44, 11 November 2024 (UTC)
Yeah I moved the revert code up, though I'm not sure about your other idea. If you could make some code, it would help more. Also pinging @EggRoll97: to see if he could implement the most recent changes to the filter. – PharyngealImplosive7 (talk) 17:39, 11 November 2024 (UTC)
It's an idea based off of Special:AbuseFilter/1248, though instead of replacing the number to see if the rest is the same it would be something like:
scaleStr := "\b[EI]?F[0-5]\b";
not_intensity_num := "[^0-5]";

//.. other code

str_replace_regexp(added_lines, not_intensity_num, "") != str_replace_regexp(removed_lines, not_intensity_num, "")

Essentially removing all characters except 0 to 5, comparing the resulting sequence of numbers to see if it changed. – 2804:F1...DF:61D4 (::/32) (talk) 19:11, 11 November 2024 (UTC)

Yeah, I understand what you mean. I've gone ahead and implemented your suggestion with a few minor changes, but it would be great if an EFH/EFM could review the changes and implement them. – PharyngealImplosive7 (talk) 19:40, 11 November 2024 (UTC)
At the risk of elongating this section even more, just curious, why !(x == y) instead of x != y? – 2804:F1...DF:61D4 (::/32) (talk) 19:54, 11 November 2024 (UTC)
I mean in general it is used to clarify in a more clear way what is supposed to be equal and what is, but it really doesn't matter that much. I can change it if you like. – PharyngealImplosive7 (talk) 20:03, 11 November 2024 (UTC)
Remodified the code again because this is getting nowhere. I placed the summary exclusion code at the very bottom, and intentionally placed page_namespace at the very top of the filter, and page_title at the second top for performance reasons. I removed the reference addition exclusion by replacing it with edit_delta <= 2 (equals or less than 2 bytes) since the edit_delta for these changes are going to be usually 0. Codename Noreste 🤔 Talk 20:39, 11 November 2024 (UTC)
@Codename Noreste, PharyngealImplosive7, and 2804:F14:8092:C01:116E:4A01:43DF:61D4: Implemented the changes, with the exception of the edit_delta check replacing the added refs check. That would seem to me to hit every change to an intensity number even with new references? It seems best to just keep the added references check, no? EggRoll97 (talk) 20:46, 11 November 2024 (UTC)
For now, I'm not sure of a good way to actually exclude sourced changes while logging unsourced ones. Codename Noreste 🤔 Talk 20:48, 11 November 2024 (UTC)
Yes I was about to comment about that. After analyzing the edits provided, I noticed that some are above 2 in edit delta, especially when they vandalize other sections of the page. As a result, I believe we should keep the references check. – PharyngealImplosive7 (talk) 20:48, 11 November 2024 (UTC)
However for now, now that the filter has been significantly modified, we should probably leave it to be tested until we get a few hits and can assess how it is doing. Courtesy ping to @Departure–: to let him know the filter should be more or less ready. – PharyngealImplosive7 (talk) 20:54, 11 November 2024 (UTC)

Preventing Page Blanking

  • Task: Restricting non-autoconfirmed users (recently registered accounts and IPs) from blanking pages in the Wikipedia: namespace.
  • Reason: This is my first time requesting an edit filter, so I apologize in advance if this has already been proposed and declined. Over the past few days, I’ve noticed instances of page blanking in Wikipedia namespace pages, including manuals, policies, and shortcuts. I believe it could be beneficial to implement a filter to prevent such actions. Additionally, I'd like to invite editfilters to consider applying this filter to other namespaces, such as Main: and Portal:.
  • Diffs: 1, 2, 3, 4, 5, 6.

— Tres Libras (talk) 19:50, 18 November 2024 (UTC)

We already have filter 1151 (hist · log) for this purpose, but it only allows 2 blankings in 30 minutes before that filter prevents any more from anonymous and non-autoconfirmed users. Codename Noreste 🤔 Talk 21:00, 18 November 2024 (UTC)
Ah, I see. I was surprised that enwiki doesn’t have anti-blanking filters in place. On other wikis, these filters completely prevent blanking, so I assumed the same would apply here. Thank you for your response! — Tres Libras (talk) 21:12, 18 November 2024 (UTC)
The redirect blankings also get picked up by filter 1318 (hist · log) which I've been patrolling daily, so those aren't the big problem. Filter 1151 (hist · log) probably could need improvement, but I don't think any EFM is currently interested in trying it. Nobody (talk) 06:20, 19 November 2024 (UTC)

Prevent insertion of lyrics from Thick of It

  • Task: Add certain lyrics to filter 614 (such as /From the screen to the ring/)
  • Reason: To prevent new users from inserting lyrics from the song (usually vandalism), which avoids edits from being revdelled
  • Diffs: Special:Diff/1258652804, Special:Diff/1253354917; these had lyrics from the song, but were revdelled.

--Leonidlednev (TCL) 22:16, 20 November 2024 (UTC)

Special:Diff/1258868399 the Thick of It copy-paste struck again. ABG (Talk/Report any mistakes here) 02:08, 22 November 2024 (UTC)
Special:Diff/12590417372804:F1...86:EF41 (::/32) (talk) 01:38, 23 November 2024 (UTC)

Prevent insertion of "smartschoolboy9"

OpalYosutebito (talk) 03:38, 22 November 2024 (UTC)

I think we could just add the simple regex smartschoolboy9 to the filter. That should fix the problem. – PharyngealImplosive7 (talk) 01:41, 23 November 2024 (UTC)
That sounds a lot easier. Thanks for the help! - OpalYosutebito (talk) 01:44, 23 November 2024 (UTC)

Prevent Zalgo text

  • Task: Disallow Zalgo text for new users, and warn older or extended confirmed users.
  • Reason: It can disrupt the readability of an article. Additionally, quoting Zalgo text's Wikipedia article, "[as] Zalgo text has been used maliciously to crash or overwhelm messaging apps", an excess amount of Zalgofied characters (e.g. a whole Wikipedia article where every character has 100 or more combining diacritics) could crash web browsers.
  • Diffs: While I have seen no instances of vandals adding Zalgo text so far, I believe it should be preemptively filtered out.

Doctor Zoath (talk) 04:47, 24 November 2024 (UTC)

Filter 1035 — Pattern modified
Last changed at 06:54, 24 November 2024 (UTC)

Filter 945 — Actions: throttle; Flags: disabled

Last changed at 20:37, 23 November 2024 (UTC)

Filter 1170 — Pattern modified

Last changed at 01:00, 23 November 2024 (UTC)

Filter 1326 (new) — Actions: showcaptcha,throttle; Flags: enabled,private; Pattern modified

Last changed at 19:30, 22 November 2024 (UTC)

Filter 1178 — Actions: warn

Last changed at 18:52, 20 November 2024 (UTC)

Filter 225 — Pattern modified

Last changed at 16:50, 20 November 2024 (UTC)

Filter 1325 (new) — Actions: none; Flags: disabled,public; Pattern modified

Last changed at 02:04, 20 November 2024 (UTC)

Articles

Administrator intervention against vandalism (WP:AIV)

Reports

User-reported

Requests for page protection (WP:RFPP)

Backlog CLEAN!

Permissions

Account creator (WP:PERM/ACC)

Account creator

AutoWikiBrowser (WP:PERM/AWB)

AutoWikiBrowser


I want to get into the swing of helping out in more ways other than RCP/PCP. Manually editing each article can only do so much. This would be handy to have. Synorem (talk) 06:14, 13 November 2024 (UTC)

Do you have any specific task in mind for this? * Pppery * it has begun... 21:58, 17 November 2024 (UTC)
Particularly for tasks like fixing broken templates and adding article-improvement templates. Since I frequently go through hundreds of articles a day via Huggle, AWB would help by allowing me to quickly add these templates without having to manually search for them and copy-paste them into each article. A recent issue that comes to mind was dealing with a few instances of {{cn}} spam, as seen here and here. This would help clear up stuff like this. Synorem (talk) 03:32, 18 November 2024 (UTC)

I've been making edits to chemistry/drug-related articles that add the class=skin-invert-image filter to molecular line drawings and other diagrams with dark shapes on light/transparent backgrounds. This makes them a lot more readable in dark mode and is the suggestion on how to handle this per [1]. It's becoming more and more of a pain to do this manually, and I think a touch of regex will make this easier for me.

For an example, check out Mineralocorticoid receptor antagonist and what it looked like before adding the filters here. ― Synpath 00:17, 23 November 2024 (UTC)

 Already done (automated response): This user already has AutoWikiBrowser access. MusikBot talk 19:50, 23 November 2024 (UTC)
@Synpath I've granted your request for AWB access. I'm excited to see the work you'll do, it's important and requires a specialized skill set that not everyone has. In 30-45 days (might take me awhile with the holidays coming up) I'll review your AWB edits and leave a note on your talk page. This isn't meant to be disruptive, imply that you've done anything wrong, or signal that I don't trust you or your work. Just a polite check in to make sure everything is going smoothly and to help give you some tips and feedback. I made some silly mistakes when I was first granted AWB access so it's just my way of helping others not screw up like I did. If you have any questions or run into any issues please feel free to leave a message on my talk page and I'll try my best to help you. Dr vulpes (Talk) 19:51, 23 November 2024 (UTC)
Thanks for the approval and the interest! I've induced my fair share of facepalming because of semi-automated experiments, so I'll be glad for a review of the edits down the line to catch anything I might have missed. ― Synpath 20:50, 23 November 2024 (UTC)
Mass message sender (WP:PERM/MMS)

Mass message sender

I'm currently planning to host a campaign and will be needing it to make my communication easier, faster and saver as an organiser. Royalesignature (talk). 17:04, 21 November 2024 (UTC)

Could you share more details about this campaign? Have you made a request at Wikipedia talk:Mass message senders before? —Ganesha811 (talk) 21:34, 21 November 2024 (UTC)
https://meta.wikimedia.org/wiki/Wiki_Kwara_Odyssey_Project
And this https://meta.wikimedia.org/wiki/Exploring_the_Cultural_Heritage_of_Yoruba_Compounds_Wikimedia/Topic_list
Attached is the links to the metapages of those projects and I'm yet to request Wikipedia talk:Mass message senders Royalesignature (talk). 03:31, 24 November 2024 (UTC)
@Royalesignature did you have an update to @Ganesha811's questions? Dr vulpes (Talk) 19:29, 23 November 2024 (UTC)
Thanks for reaching out I've provided the update just now.
Thanks Royalesignature (talk). 03:33, 24 November 2024 (UTC)
New page reviewer (WP:PERM/NPR)

New page reviewer

I have been reviewing at AfC from a while. I would like to help with the NPR backlog. My AfD stats are a bit weak, but I believe I can quality for a trial. Thanks! ~/Bunnypranav:<ping> 13:09, 22 November 2024 (UTC)

Thank you for volunteering, Bunnypranav. The AfC history tool is only showing fourteen reviews, which together with your limited AfD and article creation records does not really give me enough to go on. You're on the right track, but please come request again after some more experience at AfC and/or AfD.  Not done for now. – Joe (talk) 15:32, 22 November 2024 (UTC)
@Joe Roe Thanks for the quick response. Considering my more backend experience in Wikipedia, and at WP:AFC/R, see redirs created, can I be granted a short trial? Say 15 days or less? Thanks! ~/Bunnypranav:<ping> 16:25, 22 November 2024 (UTC)
@Bunnypranav Take a look into attending WP:NPRSCHOOL. I did it and it was a really eye opening experience for me. It made me really understand the rules and helped me become a much better editor. It also improved my voting and reasoning at AfD. Attending and graduating from WP:NPRSCHOOL is a really strong indicator that you're ready for this permission. It's how I got started with NPP so I might be a little biased. Dr vulpes (Talk) 19:41, 23 November 2024 (UTC)
Thanks for the advice, will do it. ~/Bunnypranav:<ping> 07:51, 24 November 2024 (UTC)
Pending changes reviewer (WP:PERM/PCR)

Pending changes reviewer

I am a regular editor on Wikipedia. I have new page review, autopatroller, rollback permission and participate in draft article reviews. I would enjoy helping with pending changes review. Demt1298 (talk) 19:55, 21 November 2024 (UTC)

 Done * Pppery * it has begun... 04:33, 22 November 2024 (UTC)

I have been actively involved in RC Patrolling as part of anti-vandalism efforts on Wikipedia for quite some time. I believe obtaining the Pending Changes Reviewer permission would be a logical next step. I am well-versed in Wikipedia's vandalism policy, including what constitutes vandalism and what does not. Additionally, I have thoroughly read and understood the basic content policies, such as Biographies of Living Persons (BLP) , Neutral Point of View, No Original Research, Verifiability, and 'What Wikipedia Is Not. I am also familiar with the basic legal policy outlined in Wikipedia:Copyrights. With over 13,000 contributions to Wikipedia, I feel confident that I am now ready to take on this responsibility. Thank you! Baqi:) (talk) 14:03, 22 November 2024 (UTC)

 Done Hey man im josh (talk) 14:09, 22 November 2024 (UTC)
Rollback (WP:PERM/R)

Rollback

I am a newpage editor with autopatrol approval. I have been monitoring the Recent Chane list working to revert mainly vandalism while continuing to maintain my own editing. Demt1298 (talk) 15:10, 21 November 2024 (UTC)

 Done. HJ Mitchell | Penny for your thoughts? 19:42, 21 November 2024 (UTC)

Ever since I became active on Wikipedia, my main interest has been combatting vandalism. With over a month of experience patrolling recent changes, I would therefore like to apply for rollback to better assist with the project, potentially utilizing tools such as Huggle. VolatileAnomaly (talk) 10:30, 22 November 2024 (UTC)

 Done —Femke 🐦 (talk) 19:34, 22 November 2024 (UTC)

I have been patrolling recent changes on-and-off for around 6 months now. Been looking to try out tools like Huggle or AV to replace the manual "ctrl+clicking diff links on recent changes and seeing if they're bad". I have read the necessary pages, and I understand how rollback may be used. mwwv converseedits 18:25, 22 November 2024 (UTC)

 Done —Femke 🐦 (talk) 07:56, 23 November 2024 (UTC)

I've been patrolling Recent Changes for a long time now and wanted to try something different: Huggle and/or AntiVandal. I haven't been extremely active lately, but my work should be clearing up soon. I've read WP:ROLLBACK and always try to warn editors. Thank you for your consideration. Relativity ⚡️ 22:06, 23 November 2024 (UTC)

 Done Elli (talk | contribs) 23:28, 23 November 2024 (UTC)

Requesting rollback to help with my anti-vandalism work. I understand the guidelines and already consistently warn users and use appropriate edit summaries. Cremastra ‹ uc › 03:01, 24 November 2024 (UTC)

 Done. PhilKnight (talk) 03:49, 24 November 2024 (UTC)

BRFAs