This is an archive of past discussions with User:Suffusion of Yellow. 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.
Thanks for the advice. Though sometimes they continue on with their trollish behavior and its unlikely that they'll be bored and move on, because they're just that determined even when ignoring them. Plus, looking at this particular anon user, it seems they've been using a VPN of the sort to evade blocks. Best to look into this if possible. Thank you. 2604:B000:B137:FF36:64D8:D16E:1F5F:541F (talk) 15:28, 22 November 2022 (UTC)
Interesting. Hope they can contact this company about this particular incident. I don't live in Italy myself so I don't know anything about it, but maybe there are Italian users on here (preferably admins) that could look into this. 2604:B000:B137:FF36:64D8:D16E:1F5F:541F (talk) 22:06, 22 November 2022 (UTC)
There are more vandals than you probably realize. The usual method of dealing with them is just revert, block, ignore. Unless they're doing something illegal, generally no one is going to report them in the "real world". I except ISPs just drop abuse@ emails in the bit bucket, unless they're coming from law enforcement. Plausible threats of violence can be reported to the email listed at WP:EMERGENCY. I don't consider this a plausible threat (reads more like a child trying to sound tough), but if you disagree, feel free to report them. Suffusion of Yellow (talk) 22:24, 22 November 2022 (UTC)
ArbCom 2022 Elections voter message
Hello! Voting in the 2022 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 12 December 2022. All eligible users are allowed to vote. Users with alternate accounts may only vote once.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
Whatever you celebrate at this time of year, whether it's Christmas or some other festival, I hope you and those close to you have a happy, restful time! Have fun, Donner60 (talk) 00:16, 23 December 2022 (UTC)}}
I would have thought that most requests like this come from people just copy-and-pasting the instructions, in which case it will be capitalized just like in the original, and include the signature. Any examples which suggest otherwise? This sort of edit isn't exactly disruptive, so it needs to be really common to justify a filter. Suffusion of Yellow (talk) 22:58, 4 February 2023 (UTC)
@HJ Mitchell: Disabled for now, because I'm not sure what to do with that. It's supposed to be tracking a Firefox bug that causes unintentional page corruption when you close and then reopen an editing tab, so in theory it should be applied to all non-bot users. Suffusion of Yellow (talk) 20:40, 18 March 2023 (UTC)
@Galobtter: I could go either way also. I set it back to disallow for now; that wasn't supposed to be a half year long test! The condition limit has been doubled, so pruning filters is now more about runtime, and mental strain on those trying to remember what ~300 filters do. But no objection to disabling. Suffusion of Yellow (talk) 23:14, 24 March 2023 (UTC)
Thanks! Updated it a bit, since apparently at least user_age is correct now. I don't see how the other variables could be easily fixed; The "real" added_lines isn't saved anywhere unless a filter trips (hence 1201 (hist·log)), and answering "what was this user's edit count at this time" seems like an expensive database query to run on 100 users. And I'm happy batchtest-plus has found at least a few users. Suffusion of Yellow (talk) 22:18, 5 April 2023 (UTC)
EFH
Hi Suffusion of Yellow, I've been considering requesting EFH, as a lot of the filters are private, especially the ones that always have false positives, and I have a basic understanding of perl regex, with intent to learn more. I was wondering if you would consider me as someone who would be a good candidate for the right. On a side note, Illusion Flame has proposed disabling filter 1248, as its just constantly filling up the filter log. Thanks, Zippybonzo | Talk (he|him) 15:38, 1 May 2023 (UTC)
@Zippybonzo: I would probably not support at this time. I generally like to see at least one of:
Long-term dedication to filter-related matters. I can only find about 50-60 edits to filter-related pages, mostly going back about three weeks.
Serious in-depth digging. Figure out which part of the filter matched, and whether it's fixable, etc. I realize there's a chicken-and-egg problem here, since you need EFH to access Special:AbuseFilter/test and other tools. But do the best you can.
Extensive experience with other technical matters; e.g. bots, user scripts, or complex template/module editing. Not seeing much of that.
Now, my standards are probably higher than some others. I see EFH as "EFM in training", a view not shared by everyone. But I'd suggest waiting. Do keep up the good work, though. Suffusion of Yellow (talk) 20:46, 1 May 2023 (UTC)
Yeah, I limit the scripts/gadgets I use for that exact reason. I think that piece of advice could fit into a larger essay about editing with readers in mind; WP:READER could be turned into that but doesn't quite fit currently. Cheers, {{u|Sdkb}}talk22:43, 19 May 2023 (UTC)
I was thinking more along the lines of Edsu's hat, e.g. "How could you have missed that notice!? It's bright orange and filling the screen!" "What notice? I never got a notice." "Of course you did. Are you just trying to gaslight us..." etc. Suffusion of Yellow (talk) 23:19, 19 May 2023 (UTC)
Hello, Suffusion of Yellow. Your account has been granted the "extendedmover" user right, either following a request for it or demonstrating familiarity with working with article names and moving pages. You are now able to rename pages without leaving behind a redirect, move subpages when moving the parent page(s), and move category pages.
Please take a moment to review Wikipedia:Page mover for more information on this user right, especially the criteria for moving pages without leaving a redirect. Please remember to follow post-move cleanup procedures and make link corrections where necessary, including broken double-redirects when suppressredirect is used. This can be done using Special:WhatLinksHere. It is also very important that no one else be allowed to access your account, so you should consider taking a few moments to secure your password. As with all user rights, be aware that if abused, or used in controversial ways without consensus, your page mover status can be revoked.
If you do not want the page mover right anymore, just let me know, and I'll remove it. Thank you, and happy editing! Spicy (talk) 22:30, 28 May 2023 (UTC)
Thanks
I'm not even sure what the filter was angry about, but I was reverting in a paragraph on LGBT populations, so I guess that had something to do with it. Thanks again for dealing with that vandal! 47.227.95.73 (talk) 20:21, 30 May 2023 (UTC)
Yeah, it's supposed to catch multiple uses of some words, e.g. "He's gay, totally gay..." and so on. You've probably been told this about seven million times already, but if you create an account, you'll be excluded from most filters one you're autoconfirmed. Suffusion of Yellow (talk) 20:28, 30 May 2023 (UTC)
Before you answer this question, please read my user page to see why I am asking you this question. You do not have to answer this question at all if you wish. If you do answer this question, could you please state if you are okay with your username being used, possibly publicly? Thank you-- DisposableUser12345 (talk) 01:24, 14 June 2023 (UTC)
"Does not have the privilege of reporting other users to ANI"
While I understand that someone like WP:LTA/BKFIP making frivolous ANI requests should have those ANIs closed, I don't understand what you mean by "privilege" on the ANI you've recently closed. If you could explain to me that would be great. (Sorry if my question sounds kind of annoying.) Millows!| 🪧03:12, 2 August 2023 (UTC)
@Millows: "That would be great", heh? So, an analogy: Say you're a manager at some company. There's this employee, who does reasonably good work, but just doesn't get along with anyone. One day, you let him go. The next day, he shows up, walk in to your office, and says "I walked by Peter's desk on the way in, and saw him put the wrong coversheet on his TPS report". You tell him he needs to leave; he doesn't work here anymore. The next day he shows up again, this time wearing a new hat, and again complaining about Peter's TPS reports. Again you tell him to leave. He does this every day, for years, each time wearing a new hat. Do you, every day, walk over to Peter's desk and say "we need to talk about your TPS reports". No, that would be allowing a fired employee to harass another worker. Now, back to Wikipedia. This point is, it doesn't matter if the report is "frivolous" or not. We shouldn't even look at it. If we did, then, then we'd be creating a recipe for any banned user to "get" their "enemies"; just create ANI reports over and over until one of the 847 admins is having bad day, and falls for it. Such reports need to be shut down swiftly, regardless of the merits, before things get out of hand. I of course don't mean reports like "User:X is threatening to shoot up a school". Obviously, WP:UCS (and basic decency) means you look at that.
A much shorter, and more policy-based, answer would be WP:BMB. But some people over-use BMB to imply that any 12-year old who gets blocked for a five-minute vandalism spree is somehow prohibited for life from ever creating a new account, or that we should blindly restore vandalism and BLP violations, if the reverting user was evading a block. Again WP:UCS. Suffusion of Yellow (talk) 20:25, 3 August 2023 (UTC)
You've got mail!
Hello, Suffusion of Yellow. Please check your email; you've got mail! Message added 16:21, 5 August 2023 (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.
I think I remember you do some coding for filters...
But anyway...maybe you could take a look at these edits for the creative ways some folks are getting around all the Chuck Feed etc stuff: [2] & [3]. I'd never seen the "code" workaround & the other wording is also connected to the meme. Thanks, Shearonink (talk) 02:07, 12 September 2023 (UTC)
Hello. I'm considering requesting EFH soon, and would like any advice you might be able to toss my way. I'm mainly involved with false positives (edits seen here) and, ever since your FilterDebugger script, I've been able to examine the causes behind a filter tripping more easily. It's mostly the reasons I'd expect (the problematic edits are usually a no-brainer), though I've found a few interesting ones here and there. EggRoll97(talk) 05:37, 2 November 2023 (UTC)
If you want to what I think, it's that creating the EFH right was a mistake; it's a read-only right which makes "abuse" (e.g. poor security practices) impossible to detect. And I've never felt we have a shortage of EFHs; it's always more EFMs (willing to actually update filters) that we need. So I tend to sit out most EFH requests, because it's usually not my objection to the specific candidate. My concern is always the next user showing up with "well, you granted it to user:X and I clearly have more experience", and you've got to admit that they're right. Then we end up with an attack surface of 2000 EFHs. Will all that said, I think I will support you, but, for the reasons given above, it's not going to be the sort of "strong support" where I badger any opposers... If you want to know what other people will think, the four previous requests are going to be an issue. Definitely be up front about that, link to the archives from your request, and explain what's different. Also, always happy to know that someone finds FilterDebugger useful; any suggestions for improvement? Suffusion of Yellow (talk) 20:25, 4 November 2023 (UTC)
I can't say I disagree with your concerns (namely because a point was raised a few years ago that it might be better to just run the gauntlet for adminship instead, given the level of sheer trust that would be necessary), and share at least a part of them. As for FilterDebugger, no specific feedback. I will say that getting into it without any experience does take a bit of tinkering, but all good things do, so I'd say that's a plus more than anything. I'd say FilterDebugger is perhaps the reason I actually started taking a look at why filters tripped, rather than just whether the edit was supposed to be disallowed, and mainly because it made it so easy to do so. EggRoll97(talk) 02:45, 5 November 2023 (UTC)
FilterDebugger not working
Apparently, when I use Google Chrome on a laptop or my iPhone 8 Plus, it only shows the title Debugging edit filter with a blank page below said title. Is there any way to fix the issue? Thanks. — 64andtim (chat • see here) 03:13, 16 November 2023 (UTC)
Does this work on any machine (e.g. Windows, Linux, Android, if available)? This could be a conflict with one of your other user scripts or gadgets.
Can you give me your user agent? If you don't want to make it public, can you email it? AFAIK "Chrome" on iOS is still just wrapper for Safari; and Safari only recently added some features that FilterDebugger depends on. But you should be getting an error message about your browser being too old, instead of just a blank page.
Are there any WP:CONSOLEERRORs? Again, if you can email if you like.
@64andtim: Sorry can't figure this out. Copied both your common.js and global.js into an alt account, and with the almost the same browser (on Linux), and every skin, it works for me. Does it at least work in safe mode? Try:
@64andtim: Thanks, that was helpful! Managed to reproduce almost exactly those messages (in both Firefox and Chrome) by enabling the "Image Annotator" gadget. If you're using that gadget, try disabling it. Suffusion of Yellow (talk) 23:41, 17 November 2023 (UTC)
I've turned Image Annotator off, and it does work! Maybe you should put on your FilterDebugger documentation page that for the script to work, they should disable the Image Annotator gadget off in their preferences. Thank you! — 64andtim (chat • see here) 23:45, 17 November 2023 (UTC)
Hello! Voting in the 2023 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 11 December 2023. All eligible users are allowed to vote. Users with alternate accounts may only vote once.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
Pick me, pick me, pick me, to help turn that blue. Also I feel like I have more to say than I did when we last discussed this 3 years ago about the concern you expressed at the time. Best, Barkeep49 (talk) 21:08, 3 December 2023 (UTC)
I'm going to selectively interpet your "thanks" to my edit about having more to say as an OK to email you those thoughts. So you've got mail. Best, Barkeep49 (talk) 23:13, 3 December 2023 (UTC)
It was bit more of a "I'll let you know when I'm ready, but it seems rude for me to leave a complement totally unacknowledged". I have read your email, though, and I'll try to reply soon. Suffusion of Yellow (talk) 03:01, 4 December 2023 (UTC)
I just wanted to stop by: it will be great to have you as an admin. Your technical experience is one of the best we have on this site right now. I know that this has probably been said many times by many others, and this is ultimately your decision, but you have my support. 0xDeadbeef→∞ (talk to me) 03:07, 4 December 2023 (UTC)
...this edit slipped by. I don't know how to construct filters but seems like Sn**dville, TN would be ripe for exploitation by these SPAs. And if I don't get a chance before Christmas & New Years...Happy Holidays. And I appreciate all you do around here. Shearonink (talk) 01:41, 5 December 2023 (UTC)
Whether you celebrate Christmas, Diwali, Hanukkah, Kwanzaa, Festivus (for the rest of us!) or even the Saturnalia, here's hoping your holiday time is wonderful and - especially -
that the New Year will be an improvement on the old. CHEERS!
Share these holiday wishes by adding {{subst:User:Shearonink/Holiday}} to your friends' talk pages.
New year, new scripts. Welcome to the 23rd issue of the Wikipedia Scripts++ Newsletter, covering around 39% of our favorite new and updated user scripts since 24 December 2021. That’s right, we haven’t published in two years! Can you believe it? Did you miss us?
Got anything good? Tell us about your new, improved, old, or messed-up script here!
User:Alexander Davronov/HistoryHelper has now become stable with some bugfixes and features such as automatically highlighting potentially uncivil edit summaries and automatically pinging all the users selected.
To a lesser extent, the same goes for User:PrimeHunter/Search sort.js. I wish someone would integrate the sorts into the sort menu instead of adding 11 portlet links.
Aaron Liu: Watchlyst Greybar Unsin is a rewrite of Ais's Watchlist Notifier with modern APIs and several new features such as not displaying watchlist items marked as seen (hence the name), not bolding diffs of unseen watchlist elements which doesn’t work properly anyways, displaying the rendered edit summary, proper display of log and creation actions and more links.
Alexis Jazz: Factotum is a spiritual successor to reply-link with a host of extra features like section adding, link rewriting, regular expressions and more.
User:Aveaoz/AutoMobileRedirect: This script will automatically redirect MobileFrontend (en.m.wikipedia) to normal Wikipedia. Unlike existing scripts, this one will actually check if your browser is mobile or not through its secret agent string, so you can stay logged in on mobile! Hooray screen estate!
Deputy is a first-of-its-kind copyright cleanup toolkit. It overrides the interface for Wikipedia:Contributor copyright investigations for easy case processing. It also includes the functionality of the following (also new) scripts:
User:Elominius/gadget/diff arrow keys allows navigation between diffs with the arrow keys. It also has a version that requires holding Ctrl with the arrow key.
Frequently link to Wikipedia on your websites yet find generating CC-BY credits to be such a hassle? Say no more! User:Luke10.27/attribute will automatically do it for ya and copy the credit to yer clipboard.
User:MPGuy2824/MoveToDraft, a spiritual successor (i.e. fork) to Evad37's script, with a few bugs solved, and a host of extra features like check-boxes for choosing draftification reasons, multi-contributor notification, and appropriate warnings based on last edit time.
/CopyCodeBlock: one of the most important operations for any scripter and script-user is to copy and paste. This script adds a copy button in the top right of every code block (not to be confused with <code>) that will, well, copy it to your clipboard!
m:User:NguoiDungKhongDinhDanh/AceForLuaDebugConsole.js adds the Ace editor (a.k.a. the editor you see when editing JS, CSS and Lua on Wikimedia wikis) to the Lua debug console. "In my opinion, whoever designed it to be a plain <textarea> needs to seriously reconsider their decision."
GANReviewTool quickly and easily closes good article nominations.
ReviewStatus displays whether or not a mainspace page is marked as reviewed.
SpeciesHelper tries to add the correct speciesbox, category, taxonbar, and stub template to species articles.
User:Opencooper/svgReplace and Tol's fork replaces all rasterized SVGs with their original SVG codes for your loading pleasures. Tell us which one is better!
ArticleInfo displays page information at the top of the page, directly below the title.
/HeaderIcons takes away the Vector 2022 user dropdown and replaces it with all of the icons within, top level, right next to the Watchlist. One less click away! There's also an alternate version that uses text links instead of icons.
.jpg)
