This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.
Would it be possible to do something similar as a new thing focused on administrator talk pages? I'm not sure about the best actions to take, but it seems like a strong indicator for initial edits. Daniel Quinlan (talk) 00:05, 30 December 2023 (UTC)
I've restored that filter (with some modifications); that targets a very active LTA who edits across several large broad ranges. There should be limited collateral because of the AND condition on those ranges. I'm not on the mailing list, so I'm not sure what concern you are talking about. OhNoitsJamieTalk17:56, 1 January 2024 (UTC)
Not in any way that I know of. AFAIK the best that's publicly available is the "Of the last X actions, this filter has matched..." at the top of each filter page, which isn't all that helpful because it only shows the average, not the worst case. Users with the right kind of logstash access (e.g. MusikAnimal) can view of log of "slow filters" but I don't know to what extent it's proactively monitored. Suffusion of Yellow (talk) 22:11, 1 January 2024 (UTC)
Improving filter 397
Hi Suffusion of Yellow. I noticed that filter 397 was matching on a fair number of innocuous words and it also looked like some words could be added so I did some pretty extensive work to improve the filter and make it more maintainable. It could be made a bit faster by not computing the second ccnorm() result unless it's needed, but I want to see how fast the revised version is before I bother doing that. Please let me know if you have any concerns, questions, or feedback. Daniel Quinlan (talk) 05:07, 10 January 2024 (UTC)
Thanks! I wouldn't worry about performance (within reason) for non-mainspace filters, so long as you check the namespace before you do anything expensive. The majority of other filters will short-circuit at page_namespace == 0, so the total runtime will be low. One thing about 397 (hist·log) is that it almost always overlaps with 803 (hist·log). So all that work seems like a bit of a wasted effort. It might be worth looking for other filters to merge some of those regexes into. 384 (hist·log), 260 (hist·log) haven't had major additions in years. One more thing: if you're going go to through the trouble of commenting each part of the regex, might it make sense to use extended syntax:
That way there's no need to list every part twice. Lastly, I might have already plugged this to you, but I built User:Suffusion of Yellow/FilterDebugger for exactly this sort of work. It won't work if you're using any really tricky regex (possessive repeats, recursion, etc.) but should be good enough for this. Suffusion of Yellow (talk) 00:07, 11 January 2024 (UTC)
Thanks. It looks like the performance is the same as before because so few edits make it past the initial conditions (as expected).
I wasn't sure if free-spacing was supported, but that might come in handy. I'm hoping to revise several filters based on abuse expressions and 397 seemed like a relatively easy place to start. 384 looks like a good next stop and I suspect most if not all of the patterns can be shared.
Hi. Now that I'm an EFM, I realize that it would be helpful to have a script that linked each warning/disallow message name (like "abusefilter-disallowed-WPWP-extendedconfirmed" on Special:AbuseFilter/1258 for example) to the relevant message (MediaWiki:abusefilter-disallowed-WPWP-extendedconfirmed). Any chance you would be interested in writing such a script? If not I can take a crack at it but you seem to have cornered the market on edit filter-related scripts so I figured I'd ask. Thanks, --DannyS712 (talk) 20:36, 18 January 2024 (UTC)
Hello everyone, and welcome to the 24th issue of the Wikipedia Scripts++ Newsletter, covering all our favorite new and updated user scripts since 24 December 2021. Uh-huh, we're finally covering the good ones among the rest! Aren't you excited? Remember to include a link in double brackets to the script's .js page when you install the script, so that we can see who uses the script in WhatLinksHere! The ScriptInstaller gadget automatically does this. Aaron Liu (talk) 01:00, 1 March 2024 (UTC)
Got anything good? Tell us about your new, improved, old, or messed-up script here!
Featured script
Making user scripts load faster by SD0001 is this month's featured script, which caches userscripts every day to eliminate the overhead caused by force-downloading the newest version of scripts every time you open a Wikipedia page. Despite being released in April 2021, our best script scouters have failed to locate it due to its omission from the US of L. For security reasons, the script only supports loading JavaScript pages.
Newly maintained scripts
After earthly attempts at improving the original have failed...
Ahecht has created a fork of SiBr4/TemplateSearch, which adds the "TP:" shortcut for "Template:" in the search box, and updated it to be compatible with Vector 2022.
AquilaFasciata/goToTopFast is a much faster fork of the classic goToTop script that also adds compatibility for Minerva and Vector 2022.
Without caching. Each script takes 400–500ms. A particularly large script takes 1.11 s! Internet download speed is 50 Mbps.With caching enabled. Each script takes just 1-2 ms to load.
Improve a script
Unfortunately, this section has remained nearly identical. Help us out here!
To a lesser extent, the same goes for PrimeHunter/Search sort. I wish someone would integrate the sorts into the sort menu instead of adding 11 portlet links.
Dragoniez/SuppressEnterInForm stops you from accidentally submitting anything due to pressing enter while in the smaller box, and works on almost anything... except the InputBox element itself, used in subscription lists and the Signpost Crossword! Oh, the humanity!
Doǵu/Adiutor(pictured) provides a nice, integrated interface to do some twinkley tasks such as copyvio detection, CSD tagging, and viewing the most recent diff.
Eejit43 has quite the aesthetically pleasing scripts, all made in TypeScript.
/afcrc-helper is a replacement for the unmaintained Enterprisey/AFCRHS and processes Redirects for Creation and Categories for Creation requests.
/ajax-undo stops the "undo" button from taking you to another page while providing a text box to provide a reason for the revert.
/redirect-helper(pictured) adds a much better interface for editing and redirects, including categorization, for which valid categories are dictated by /redirect-helper.json.
/rmtr-helper helps process technical requested moves without being able to actually move them.
Guycn2/UserInfoPopup(pictured) adds a flyout after the watchlist star on userspace pages that displays the common information you might use about a user.
Jeeputer/editCounter, under userspace, adds a portlet link to count your edits by namespace, put them in a table, and put that table in a hardcoded subpage, all in the background.
Hilst/Scripts/sectionLinks converts all section links to use the § sign, which are known to be preferred over the ugly # by 99% of the devils I've met.
PrimeHunter/Category source.js adds portlet links to tell you where a category for an article comes from and supports those from template transclusions.
Sophivorus's MiniEdit adds some nice, li'l buttons next to paragraphs to edit their wikitext with a minimal interface.
Edit-listings
Dragoniez/ToollinkTweaks adds more and customizable links next to users in page history, logs, watchlist, recent changes, etc.
Firefly/more-block-info optimizes the display of rangeblocks in contribution pages. Doesn't work outside the English locale of any wiki, unfortunately.
NguoiDungKhongDinhDanh/AjaxLoader makes paging links (e.g. older 50, 500, newest) load without refreshing and makes you realize how slow your internet actually is.
Appearance-ricing
Ahecht/RedirectID adds the redirect target to all redirects. For all the WP:NAVPOPS haters. (Do these exist?)
Dragoniez/MarkBLockedGlobal: Remember the "strike blocked usernames" gadget? Now you can use a red, dotted line to highlight rangeblocks and global locks!
Jonesey/common(pictured) has some styles to overhaul your Vector 2022 experience. It reduces padding everywhere, and makes the top bar animation faster.
Aaron Liu/V22 is a fork that narrows the sidebars instead of upheaving them, reverts the January 2024 dropdown changes, and restores the old page-link color for links that don't go outside the current wiki.
Nardog: SmartDiff is a spiritual successor to Enterprisey/fancy-diffs. It makes the page title part of links in diffs clickable, along with template and parser function calls. Unnamed parameters can be configured per template to also be linked. All links are styled based on the normal CSS classes of rendered links.
For the paranoid: Rublov/anonymize replaces your username at the top of the screen with the generic "User page" text. Remember, it is your duty to persuade everyone that editing is an honor.
/AjaxBlock provides a dialog box for easy input of reasons while blocking users.
/Selective Rollback(pictured) provides a dialog box to customize rollback edit summaries and does them without reloading the page. Seriously, why doesn't MediaWiki already do this?
/flickrsearch adds a portlet link to search for uploadable flickr images about the subject.
/randomincategory adds a portlet link when on Category pages to go to a random page in the current category.
Vghfr/EasyTemplates adds a portlet link to automatically insert some of the most common inline {{fix}} templates.
Yes, we're just doing 'em as we go now. Thanks for reading through this looong issue, if you did! I'm sure this'll send a record for the longest issue ev-ah. You may need to wait even longer for the last issue, as our reserve of old-y and goodie scripts have ran out... We encourage you to try and do some of the requests or improvement tasks. See you in Summer, hopefully!
RFA2024 update: no longer accepting new proposals in phase I
Hey there! This is to let you know that phase I of the 2024 requests for adminship (RfA) review is now no longer accepting new proposals. Lots of proposals remain open for discussion, and the current round of review looks to be on a good track towards making significant progress towards improving RfA's structure and environment. I'd like to give my heartfelt thanks to everyone who has given us their idea for change to make RfA better, and the same to everyone who has given the necessary feedback to improve those ideas. The following proposals remain open for discussion:
Proposals 3 and 3b, initiated by Barkeep49 and Usedtobecool, respectively, provide for trials of discussion-only periods at RfA. The first would add three extra discussion-only days to the beginning, while the second would convert the first two days to discussion-only.
Proposal 5, initiated by SilkTork, provides for a trial of RfAs without threaded discussion in the voting sections.
Proposals 6c and 6d, initiated by BilledMammal, provide for allowing users to be selected as provisional admins for a limited time through various concrete selection criteria and smaller-scale vetting.
Proposal 7, initiated by Lee Vilenski, provides for the "General discussion" section being broken up with section headings.
Proposal 9b, initiated by Reaper Eternal, provides for the requirement that allegations of policy violation be substantiated with appropriate links to where the alleged misconduct occured.
Proposals 12c, 21, and 21b, initiated by City of Silver, Ritchie333, and HouseBlaster, respectively, provide for reducing the discretionary zone, which currently extends from 65% to 75%. The first would reduce it 65%–70%, the second would reduce it to 50%–66%, and the third would reduce it to 60%–70%.
Proposal 13, initiated by Novem Lingaue, provides for periodic, privately balloted admin elections.
Proposal 14, initiated by Kusma, provides for the creation of some minimum suffrage requirements to cast a vote.
Proposals 16 and 16c, initiated by Thebiguglyalien and Soni, respectively, provide for community-based admin desysop procedures. 16 would desysop where consensus is established in favor at the administrators' noticeboard; 16c would allow a petition to force reconfirmation.
Proposal 16e, initiated by BilledMammal, would extend the recall procedures of 16 to bureaucrats.
Proposal 17, initiated by SchroCat, provides for "on-call" admins and 'crats to monitor RfAs for decorum.
Proposal 25, initiated by Femke, provides for the requirement that nominees be extended-confirmed in addition to their nominators.
Proposal 27, initiated by WereSpielChequers, provides for the creation of a training course for admin hopefuls, as well as periodic retraining to keep admins from drifting out of sync with community norms.
To read proposals that were closed as unsuccessful, please see Wikipedia:Requests for adminship/2024 review/Phase I/Closed proposals. You are cordially invited once again to participate in the open discussions; when phase I ends, phase II will review the outcomes of trial proposals and refine the implementation details of other proposals. Another notification will be sent out when this phase begins, likely with the first successful close of a major proposal. Happy editing! theleekycauldron (talk • she/her), via:
My 1094 filter is primarily intended for LTAs, but some recent additions has it picking up lots of primary-school vandalism related to Skibidi Toilet (e.g. [1]). It seems like it would be more appropriate to merge those clauses to an existing filter that targest that type of disruption. Do you know of an existing filter that would be a good candidate for that and is monitored by a bot for WP:AIV autopostings? OhNoitsJamieTalk13:48, 26 March 2024 (UTC)
@OverlordQ: Sorry for the late reply. I see you've removed the thread and don't have email enabled. There's not much to say in public, except that filters don't work terribly well against that sort of LTA. Email me if you want to discuss more. Suffusion of Yellow (talk) 22:06, 2 April 2024 (UTC)
Filter highlighter problem, and a question
Your filter highlighter script shows that a disabled filter, whether public or private, is enabled even though it's not, and it's missing the line across the filter's name for disabled filters.
Question: do I place window.effpUseDev = true; above or below
importScript('User:Suffusion of Yellow/effp-helper.js');? That's because I want to enable experimental features for effp-helper.
Um, which filter? Results are cached for up to 30 minutes; otherwise there would be a extra ~150K API request with every page load. I just disabled a few filters; is it one of those? Suffusion of Yellow (talk) 00:05, 4 April 2024 (UTC)
I meant that the filter highlighter script displays that any disabled filter is enabled without the line crossing out the filter's name indicating that filter is disabled, even though those disabled filters are actually disabled. Codename Noreste 🤔 talk00:25, 4 April 2024 (UTC)
When I hover over a random public filter, say for example Special:AbuseFilter/1, it is actually disabled, and the information says that it is disabled. However, I do not see any line crossing out the filter's public description name indicating that it is visually disabled. Codename Noreste 🤔 talk00:37, 4 April 2024 (UTC)
Hmm, in Firefox when I choose "always underline links" the strikeout doesn't show for me either. Maybe you have some similar setting? I don't know if that's possible to override, but I'll look at it. Suffusion of Yellow (talk) 02:57, 4 April 2024 (UTC)
You would think so. But search YouTube for a video called 'QT Hush - "The Peeky-Boo Caper" (1960)'. (I won't link to it since it's probably a copyvio). When the title card comes up at about 00:25, it clearly says "The Peeky-Poo Caper". I suspect very few people care about this subject. Suffusion of Yellow (talk) 22:06, 15 April 2024 (UTC)
(talk page watcher) Speaking of filters, 1297 caught Special:Diff/1219231893 of an IP posting "your mom" vandalism of which I just reverted; that filter tagged it, while 320 (hist·log) did not catch it at all. 1297 could possibly detect any false negatives other filters may not catch, and that diff technically counts as a false negative of filter 320. Anyway, if filter 1297 tracks a huge number of vandalism that filters 12, 225, 260, 380, 384, and 614 may not catch if at all, then 1297 would also be justifiable in my opinion. Codename Noreste 🤔 𝙇𝙖 𝙎𝙪𝙢𝙖14:39, 16 April 2024 (UTC)
Do not share any personal information that be tracked to your real-life identity. It's not likely in your case, but Wikipedia users have been known to get death threats. "Deleting it after" won't help; everything you say on Wikipedia is recorded in the page history. Suffusion of Yellow (talk) 22:33, 30 April 2024 (UTC)
Hi, sorry about all the mess on my friend's talk page. We will figure it out, how to talk to each other on a different website. So here is a cupcake as an apology. Quirkykiana (talk) 22:38, 30 April 2024 (UTC)
Thank you! You weren't causing any major harm, but if that had gone on for thousands of edits, someone would have eventually taken harsher action. Suffusion of Yellow (talk) 22:46, 30 April 2024 (UTC)
Reminder to vote now to select members of the first U4C
You are receiving this message because you previously participated in the UCoC process.
This is a reminder that the voting period for the Universal Code of Conduct Coordinating Committee (U4C) ends on May 9, 2024. Read the information on the voting page on Meta-wiki to learn more about voting and voter eligibility.
The Universal Code of Conduct Coordinating Committee (U4C) is a global group dedicated to providing an equitable and consistent implementation of the UCoC. Community members were invited to submit their applications for the U4C. For more information and the responsibilities of the U4C, please review the U4C Charter.
Please share this message with members of your community so they can participate as well.
Hello, Suffusion of Yellow. Please check your email; you've got mail! Message added 18:43, 4 May 2024 (UTC). It may take a few minutes from the time the email is sent for it to show up in your inbox. You can remove this notice at any time by removing the {{You've got mail}} or {{ygm}} template.
RFA2024 update: phase I concluded, phase II begins
Hi there! Phase I of the Wikipedia:Requests for adminship/2024 review has concluded, with several impactful changes gaining community consensus and proceeding to various stages of implementation. Some proposals will be implemented in full outright; others will be discussed at phase II before being implemented; and still others will proceed on a trial basis before being brought to phase II. The following proposals have gained consensus: