User talk:Suffusion of Yellow

From WikiProjectMed
Jump to navigation Jump to search

FilterDebugger

It looks like the implementation of ccnorm doesn't properly map '¡' to i. Special:AbuseLog/36337996 is currently shown as not a match. 0xDeadbeef→∞ (talk to me) 12:53, 11 November 2023 (UTC)[reply]

@0xDeadbeef: Thanks; looks like mw:Equivset has finally been updated! I'll rebuild with the newer version. Suffusion of Yellow (talk) 19:23, 12 November 2023 (UTC)[reply]
Should be fixed now. Suffusion of Yellow (talk) 19:40, 12 November 2023 (UTC)[reply]
works now, thanks! 0xDeadbeef→∞ (talk to me) 07:07, 13 November 2023 (UTC)[reply]
You might also want to keep an eye on phab:T357855. 1234qwer1234qwer4 20:30, 26 February 2024 (UTC)[reply]
Thanks, subscribed! Suffusion of Yellow (talk) 02:52, 1 March 2024 (UTC)[reply]

HAPPY HOLIDAYS 2023

Lower than expected recall

I have 1,279 things on my mind today so I'll mention this before I forget. Could you look at this guy's article? I'm on Discord. Daniel Quinlan (talk) 22:37, 29 December 2023 (UTC)[reply]

@Daniel Quinlan: Took care of it, thanks. Suffusion of Yellow (talk) 22:48, 29 December 2023 (UTC)[reply]
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)[reply]
Might be worth a try. I'll email you in a day or two. Suffusion of Yellow (talk) 03:25, 31 December 2023 (UTC)[reply]
@Daniel Quinlan: Sent you an email. Suffusion of Yellow (talk) 22:13, 31 December 2023 (UTC)[reply]

Filter 1242

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. OhNoitsJamie Talk 17:56, 1 January 2024 (UTC)[reply]

@Ohnoitsjamie: The concern EggRoll97 raised on the mailing list was fixed with Special:AbuseFilter/history/1242/diff/prev/30471. But I'd feel more comfortable without so many common words there; that regex still matches about 500,000 titles. (Protip: If Special:Search times out when looking for page titles, just download the whole list; it's only about only about 300 MB). Certainly, your latest update reduces the FPs quite a bit, but best to keep an eye on this. Suffusion of Yellow (talk) 21:16, 1 January 2024 (UTC)[reply]
If it possible to view profiling for individual filters? OhNoitsJamie Talk 22:01, 1 January 2024 (UTC)[reply]
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)[reply]

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

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:
regex := "(?x)
    fo+ba+[rz] # foobar and variants
   |xy+zz+y # xyzzy ...
";
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)[reply]
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.
I'll try to check out FilterDebugger sometime soon too. Daniel Quinlan (talk) 05:05, 11 January 2024 (UTC)[reply]

Frivolous topic

I have to wonder— is your username by any chance a reference to the I Ching calculator in The Long Dark Tea-Time of the Soul? 🌺 Cremastra (talk) 21:10, 10 January 2024 (UTC)[reply]

But of course. :-) Suffusion of Yellow (talk) 22:36, 15 January 2024 (UTC)[reply]

User script request

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

@DannyS712: I'm not really all that active right now; plus I have maybe 20 or so unfinished scripts that I'd rather get to first. If you want this done, go for it! Suffusion of Yellow (talk) 01:56, 25 January 2024 (UTC)[reply]
@Suffusion of Yellow okay, User:DannyS712/AbuseFilterMessageLinks.js --DannyS712 (talk) 09:06, 25 January 2024 (UTC)[reply]

Improving Filter 1045

Hi Suffusion of Yellow, do you think the additions of {{Close paraphrasing}} could also be added to line 9? Thanks Nobody (talk) 14:34, 7 February 2024 (UTC)[reply]

@1AmNobody24: Thanks,  Done. Suffusion of Yellow (talk) 22:20, 10 February 2024 (UTC)[reply]

A barnstar for you!

The Technical Barnstar
This is absolutely amazing, thank you. 1234qwer1234qwer4 20:29, 26 February 2024 (UTC)[reply]
@1234qwer1234qwer4: Thanks! Always nice to know someone other than me is using these tools. Suffusion of Yellow (talk) 02:53, 1 March 2024 (UTC)[reply]

Scripts++ Newsletter – Issue 24

MediaWiki message delivery (talk) 02:37, 1 March 2024 (UTC)[reply]

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:

  • Proposal 2, initiated by HouseBlaster, provides for the addition of a text box at Wikipedia:Requests for adminship reminding all editors of our policies and enforcement mechanisms around decorum.
  • 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 18, initiated by theleekycauldron, provides for lowering the RfB target from 85% to 75%.
  • Proposal 24, initiated by SportingFlyer, provides for a more robust alternate version of the optional candidate poll.
  • 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.
  • Proposal 28, initiated by HouseBlaster, tightens restrictions on multi-part questions.

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:

MediaWiki message delivery (talk) 10:53, 14 March 2024 (UTC)[reply]

Moving a filter clause

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? OhNoitsJamie Talk 13:48, 26 March 2024 (UTC)[reply]

(talk page watcher) Probably 614 (hist · log)? 0xDeadbeef→∞ (talk to me) 14:50, 26 March 2024 (UTC)[reply]
Perfect, thank you 0xDeadbeef! OhNoitsJamie Talk 14:52, 26 March 2024 (UTC)[reply]
No problem. Just noting: the list of filters monitored by the bot is configured at Template:DatBot filters. 0xDeadbeef→∞ (talk to me) 14:53, 26 March 2024 (UTC)[reply]

LTA

Since you've seemed to have related experience, Wikipedia:Edit_filter_noticeboard#Adding_potential_LTA_filter. Q T C 20:25, 29 March 2024 (UTC)[reply]

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

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.

Thanks, Codename Noreste 🤔 talk 23:58, 3 April 2024 (UTC)[reply]

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)[reply]
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 🤔 talk 00:25, 4 April 2024 (UTC)[reply]
Does it at least say "disabled" in the title text? Suffusion of Yellow (talk) 00:31, 4 April 2024 (UTC)[reply]
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 🤔 talk 00:37, 4 April 2024 (UTC)[reply]
But you see it on the the documentation page, I take it? That's weird; that should be the same CSS. I'll look at this more later, but try other browsers, zoom in, zoom out, etc. Suffusion of Yellow (talk) 01:25, 4 April 2024 (UTC)[reply]
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)[reply]
Oh and the order doesn't matter; everything in common.js will be executed before any of the imported scripts. Suffusion of Yellow (talk) 00:06, 4 April 2024 (UTC)[reply]

Magic

The Magician's Barnstar
Looking at Special:AbuseFilter/1297, I think you could convert ClueBot NG into edit filter code and people wouldn't notice for a while. ~ ToBeFree (talk) 20:59, 15 April 2024 (UTC)[reply]
Thanks, ToBeFree! I do hope to able to set that to disallow, but edits like Special:Diff/1218192315 are going to be tricky. Suffusion of Yellow (talk) 21:31, 15 April 2024 (UTC)[reply]
That diff isn't vandalism? ~ ToBeFree (talk) 21:44, 15 April 2024 (UTC)[reply]
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)[reply]
Interesting. Weird. ~ ToBeFree (talk) 23:52, 15 April 2024 (UTC)[reply]
(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)[reply]

done, can follow up at T363020 of course. — xaosflux Talk 20:54, 19 April 2024 (UTC)[reply]

Thanks, I'll leave the IP the vague note. Suffusion of Yellow (talk) 21:00, 19 April 2024 (UTC)[reply]

This edit caught my eye...

Thought you might find it of interest. At Sneedville, Tennessee *previously known as Chvcksville* was added...using a V instead of a U...so very clever. Shearonink (talk) 00:14, 26 April 2024 (UTC)[reply]

Well, I'm sure they feel clever, at least. I don't think this is a major problem anymore; best just to treat it as a WP:RBI matter when they slip past the filter. Suffusion of Yellow (talk) 00:22, 26 April 2024 (UTC)[reply]