Commons:Administrators' noticeboard

Shortcut: COM:AN

• Community portal
  • introduction
• Help desk
• Village pump
  • copyright
  • proposals
  • technical
• Administrators' noticeboard
  • vandalism
  • user problems
  • blocks and protections

This is a place where users can communicate with administrators, or administrators with one another. You can report vandalism, problematic users, or anything else that needs an administrator's intervention. Do not report child pornography or other potentially illegal content here; e-mail legal-reportswikimedia.org instead. If reporting threatened harm to self or others also email emergencywikimedia.org.
Vandalism []	User problems []	Blocks and protections []	Other []
Report users for clear cases of vandalism. Block requests for any other reason should be reported to the blocks and protections noticeboard.	Report disputes with users that require administrator assistance. Further steps are listed at resolve disputes.	Reports that do not suit the vandalism noticeboard may be reported here. Requests for page protection/unprotection could also be requested here.	Other reports that require administrator assistance which do not fit in any of the previous three noticeboards may be reported here. Requests for history merging or splitting should be filed at COM:HMS.
Archives
23, 22, 21, 20, 19, 18, 17, 16, 15, 14, 13, 12, 11, 10, 9, 8, 7, 6, 5, 4, 3, 2, 1	118, 117, 116, 115, 114, 113, 112, 111, 110, 109, 108, 107, 106, 105, 104, 103, 102, 101, 100, 99, 98, 97, 96, 95, 94, 93, 92, 91, 90, 89, 88, 87, 86, 85, 84, 83, 82, 81, 80, 79, 78, 77, 76, 75, 74, 73, 72, 71, 70, 69, 68, 67, 66, 65, 64, 63, 62, 61, 60, 59, 58, 57, 56, 55, 54, 53, 52, 51, 50, 49, 48, 47, 46, 45, 44, 43, 42, 41, 40, 39, 38, 37, 36, 35, 34, 33, 32, 31, 30, 29, 28, 27, 26, 25, 24, 23, 22, 21, 20, 19, 18, 17, 16, 15, 14, 13, 12, 11, 10, 9, 8, 7, 6, 5, 4, 3, 2, 1	40, 39, 38, 37, 36, 35, 34, 33, 32, 31, 30, 29, 28, 27, 26, 25, 24, 23, 22, 21, 20, 19, 18, 17, 16, 15, 14, 13, 12, 11, 10, 9, 8, 7, 6, 5, 4, 3, 2, 1	98, 97, 96, 95, 94, 93, 92, 91, 90, 89, 88, 87, 86, 85, 84, 83, 82, 81, 80, 79, 78, 77, 76, 75, 74, 73, 72, 71, 70, 69, 68, 67, 66, 65, 64, 63, 62, 61, 60, 59, 58, 57, 56, 55, 54, 53, 52, 51, 50, 49, 48, 47, 46, 45, 44, 43, 42, 41, 40, 39, 38, 37, 36, 35, 34, 33, 32, 31, 30, 29, 28, 27, 26, 25, 24, 23, 22, 21, 20, 19, 18, 17, 16, 15, 14, 13, 12, 11, 10, 9, 8, 7, 6, 5, 4, 3, 2, 1

^{Translate this page}

Administrators: Please make a note if a report is dealt with, to avoid unnecessary responses by other admins.

purge Admin backlog

---

Copyright:

• Copyright violations: ~262
• Unfree Flickr files: ~0
• Recent unfree Flickr images: ~0
• Media uploaded without a license as of 2025-01: ~385

Other:

• Duplicates: ~25
• Advertisements/spam: ~0
• Personal photos/selfies: ~1
• Other speedy deletions: ~40
• Categories for discussion: 84 months
• Media requiring a split up: ~0
• Requests for unblock: ~3
• Undeletion requests: ~11

Protected edit requests:

• Full protection: ~17
• Interface admin: ~10
• Technical: ~0
• Template protection: ~3
• Protection level: ~0

See also: DR, HMS, …

COMMONS DISCUSSION PAGES

• Commons Help desk
• Village pump (general discussion)
  • Copyright
  • Proposals
  • Technical
• Graphics and photography discussion
  • Photography critiques
  • Image improvement
    • Illustration workshop
    • Map workshop
    • Photography workshop
    • Video and sound workshop
• Categories for discussion
• Undeletion requests
• Deletion requests
• Volunteer Response Team/Noticeboard
• Translators' noticeboard
• Work requests for bots

---

• Contact administrators
  • Vandalism
  • User problems (Dispute resolution)
  • Blocks and protections
• Bureaucrats' noticeboard
• CheckUser requests
• Oversight requests

---

• Telegram
• IRC ^webchat
• Commons mailing list (archive)
• Commons' bugs on Phabricator

Note

• Remember to sign and date all comments using four tildes (~~~~), which translates into a signature and a time stamp.
• Notify the user(s) concerned via their user talk page(s). {{subst:Discussion-notice|noticeboard=COM:AN|thread=|reason=}} ~~~~ is available for this.
• Administrators: Please make a note if a report is dealt with, to avoid unnecessary responses by other admins.

deletion of upload comments

Is there a way to delete the comments listed in the first upload of a file. As an example, the comment in this file File:Peineta and two combs in a shop, Valencia.jpg reads 'Uploaded while editing "Peineta" on nl.wikipedia.org'. Can this be removed. I tried revision deletion in another file, but it did not have the desired effect. My question relates to a privacy issue. Thanks, Ellywa (talk) 21:18, 15 January 2025 (UTC)

I've hidden the edit summary in that file. Abzeronow (talk) 21:26, 15 January 2025 (UTC)

@Ellywa: I've also done a very slight crop as an overwrite to help me get rid of that comment. Feel free to revert the very slight crop. Abzeronow (talk) 21:34, 15 January 2025 (UTC)

No problem, so that is the trick. I can help somebody else now, thanks so much for your quick answer. Ellywa (talk) 21:36, 15 January 2025 (UTC)

@Abzeronow. For your information: I discovered the comment is still visible in the public log, in this case no problem at all, but it might be a problem for privacy issues. I noted it can be deleted from the public log as well, thanks again for your help. Ellywa (talk) 10:49, 16 January 2025 (UTC)

phab:T288327 since 2021. --Krd 11:09, 16 January 2025 (UTC)

Sigh... while WMF is doing so much to incorporate temporary user names, this remains unsolved. Ellywa (talk) 11:27, 16 January 2025 (UTC)

I see temporary user names as a necessary thing, IP addresses are not best for privacy and WMF doesn't want to require editors to register (although that would be better for us). Not requiring an overwrite to remove unwanted data would definitely be a quality of life improvement though. Abzeronow (talk) 23:39, 16 January 2025 (UTC)

I think this is planned to be fixed with the rest of the migrations in phab:T28741, but I'm not sure. AntiCompositeNumber (talk) 23:32, 20 January 2025 (UTC)

Block review: Adam Cuerden

The administrator GPSLeo recently blocked Adam Cuerden indefinitely without leaving any warnings whatsoever about their behavior. I strongly disagree with this block, however they feel otherwise. 1989 (talk) 18:03, 18 January 2025 (UTC)

I reduced the block duration to tree days. But please keep the discussion at one place and discuss this around here [1]. GPSLeo (talk) 18:10, 18 January 2025 (UTC)

CJS is unrelated to the action you made, that’s why I made a separate discussion here. 1989 (talk) 18:12, 18 January 2025 (UTC)

We can also make a separate thread here but the link the background is needed anyways. GPSLeo (talk) 18:17, 18 January 2025 (UTC)

@GPSLeo: I guess we ran into an edit-conflict. _Regards, Aafi ^(talk) 18:11, 18 January 2025 (UTC)

Oh, good that is was my block change first and then yours the other way around would look very bad for me for someone not knowing that it was not intended. GPSLeo (talk) 18:16, 18 January 2025 (UTC)

Given my comment at the discussion, my analysis is that a 24 hour block is enough at this time. But I'd suggest that other comments be made at the discussion pointed out by @GPSLeo. If they do not disagree with me reducing the block to 1 day, I guess I am good to close it from here as  Done. _Regards, Aafi ^(talk) 18:17, 18 January 2025 (UTC)

I don't agree with Adam about Charles, but I don't see the need for blocking Adam either. Please call down, and try to find a peaceful outcome. Yann (talk) 19:30, 18 January 2025 (UTC)

• Immediate desysoping for GPSLeo and Bedivere (unblock of Adam is obvious). Bedivere certainly would be no loss to the project and I can only echo Adam's description of them as "a terrible, capricious admin". Andy Dingley (talk) 20:40, 18 January 2025 (UTC)
  • Again,  Done: I have removed the shorter block as well. Let's have the rest fo the discussion where it is supposed to have. _Regards, Aafi ^(talk) 20:58, 18 January 2025 (UTC)

  @Andy Dingley: if you want to request desysop please start a new discussion —Matrix(!) _{ping one}^{when replying} {user - talk? - _uselesscontributions} 11:49, 20 January 2025 (UTC)

• And have the other one immediately indef me in retaliation? No thanks. Andy Dingley (talk) 12:28, 20 January 2025 (UTC)

  I have made mistakes, for sure. I have sincerely apologised for such mistakes. I don't find fair, however, that you say "certainly would be no loss to the project". Makes me feel my contributions are worthless. Sure, we may disagree on some things but I'd never dare to call you or your work to be worthless. Bedivere (talk) 00:34, 21 January 2025 (UTC)

@Andy Dingley: Bedivere neglected to mention their improper early closure of a deletion request without even reading the comments there. I didn't even realize until I noticed them comment here that their behavior was already under discussion. Berchanhimez (talk) 00:43, 21 January 2025 (UTC)

Are you harassing me now @Berchanhimez by chasing my edits and comments? Stop it right there. Bedivere (talk) 00:45, 21 January 2025 (UTC)

No, I watch this page and noticed you comment here. I normally don't look at this page unless I've made a post here, but since it was still on my watchlist, I was curious about your comment that you have "made mistakes". Color me not surprised that someone else has identified a mistake you made. Also, saying you have sincerely apologised for such mistakes is false - you have still not apologized for your inappropriate closure of that discussion. Berchanhimez (talk) 00:48, 21 January 2025 (UTC)

Of course I wasn't referring to that DR closure as I don't think it was a mistake. Bedivere (talk) 00:50, 21 January 2025 (UTC)

When I'm criticising an admin for rushing too quickly to apply an indefinite block, and get hit with someone rushing too quickly to apply an indefinite block, that feels like it's saying something about admin culture around blocking.

Saying that the actions of an admin, in blocking another user what I think were too hastily, were the actions of a terrible and capricious admin. There were language issues, I think - I meant that the actions were the kind of actions a capricious admin would make, but I can see how it could be read as more than that. Even still, skipping warnings, skipping any block that ends on its own, and jumping right to an indefinite ban, is... we all agree that's not good practice, right?

I'm a little hesitant to speak up, because I don't want anyone punished over this, and so I'm just going to call the people involved B and G. B jumped to an indefinite block while a noticeboard discussion was less than a day old, and I think it was a bad block. I also think that if we insist admins are always perfect, we're not going to have any admins. G blocked me indefinitely for a single sentence about B's block that, admittedly, wasn't perfectly phrased, but which was meant to criticise what I do think was a bad admin action. I don't know B, and, as I'm pretty sure I said in the discussion, I don't think a single block shows that much about B's adminship.

G is,I believe, a German-speaker, and machine translated my sentence, which probably didn't help matters, but I'm not upset at G. I'm kind of furious with a more nebulous "blocking culture" on Commons. If a single sentence seen as insulting can be used to give an indefinite block, apparently with the intent of forcing an apology before unblock, that's... really not great. Especially when you have to machine translate the sentence in question. (Luckily, I was away at a family event and this had somewhat blown over when I was back.)

But I don't think either B or G are bad people. I think that blocking policy is simply not being well-applied, nor understood.

Further, remember that blocks do have consequences: They can very easily drive users off the project. You're far more likely to get actual trolls back after a one year block than well-meaning but thoroughly disenheartened contributors. People move on. People find new outlets. I would presue that the only people likely to come back after a year block are exactly the people who shouldn't be allowed back in the first place.

Even a block that's corrected is going to have consequences. The logs still exist. That someone was blocked before can be used as evidence that they should be blocked again. And, of course, it absolutely kills any enthusiasm for contributing.

Now, Commons:Blocking policy is fairly good, on the whole. I'd probably say that that kind of block is explicitly forbidden: "blocks are preventative rather than punitive", "Controversial blocks may be discussed at the blocks and protections noticeboard, preferably before they are applied if at all possible. As a rule of thumb, when in doubt, do not block", " use a block duration that is proportional to the time likely needed for the user to familiarize themselves with relevant policies and adjust their behaviour."

So, is there any good way forwards? Because I do think the situation is pretty bad, but we don't need showtrials. We need to figure out why what are, as far as I can tell, well-meaning, sensible people would make actions so far out of policy. I don't want revenge, but I do want change. Because Commons is meant to be better than this. Adam Cuerden (talk) 08:12, 20 January 2025 (UTC)

Hi, As I said, I think you should not have been blocked, let alone indefinitely. Now I don't understand why GPSLeo blocked you. Language misunderstanding? Something else? I have no idea. Everybody can makes mistakes, and I did once too. I don't see anything in the policy that should be changed. Regards, Yann (talk) 09:52, 20 January 2025 (UTC)

I first did not want to continue to participate at this discussion as I do not want to justify for the mistake I made. But as we are now starting a policy discussion I want to share my view on the situation and the general topic. The reason for the block was a combination of language/cultural misunderstanding of the wording as very harassing and an overreaction after reading the escalating discussion. (Which obviously escalated even more after the block.) I trust you that the comment was not meant that attacking as I understood the comment. The blocking policy does not say much about block duration and blocks to enforce an apology with the possibility for a very fast unblock. Therefore if an inappropriate comment that would justify a block but that is not against the code of conduct the policy does not say if the user should be blocked for some days or should first be blocked infinitely and give the user the possibility to appeal immediately.

I could even think about a 4-eye-principle for blocks of long term contributors (defined by autopatrol rights) or a rule that long term contributors always have the possibility the make a statement before being blocked as long as they do not abuse this. GPSLeo (talk) 14:56, 20 January 2025 (UTC)

I do apologise for bringing you into this, I don't think you're the problem. It doesn't sit well with me to block with no warning, then coerce an apology as a requirement for unblock. Like, I am sorry if I upset B, but if I was blocked and saying that as a condition to get unblocked, even if it was sincere, how would you know? Better to warn or ask someone to redact their statement first. Adam Cuerden (talk) 23:50, 20 January 2025 (UTC)

Please undelete

• Category:NANP area code 753

for it is not empty any longer, and the deleting admin has meanwhile been unflagged. Thanks! -- Tuválkin ✉ ✇ 01:05, 19 January 2025 (UTC)

@Tuvalkin: just create it from scratch. I don't think it's interesting to restore a history of it having been categorized incorrectly as an area code in Missouri. - Jmabel ! talk 01:33, 19 January 2025 (UTC)

Sure, I will. I only asked because I thought it was policy to rather undelete instead of recreate, in these cases. -- Tuválkin ✉ ✇ 01:36, 19 January 2025 (UTC)

Depends whether it was deleted just for being empty, or it's plain wrong. In this case, it's plain wrong. - Jmabel ! talk 06:54, 19 January 2025 (UTC)

File:Dirk Schaefer 2024.jpg

Kann bitte jemand File:Dirk Schaefer 2024.jpg in die Category:Dirk Schäfer (boxer) einfügen? Ich darf das nicht, weil die Datei "mittels Kaskadensperroption geschützt ist". Danke --Seemannssonntag (talk) 11:11, 19 January 2025 (UTC)

 Done -- Auntof6 (talk) 13:01, 19 January 2025 (UTC)

user:Florizss

Vandal. Aranzavy (talk) 15:00, 19 January 2025 (UTC)

 Done. The user has not edited on current year, but nothing good has come from this account, so I decided to block Florizss as vandalism-only account. Taivo (talk) 17:48, 19 January 2025 (UTC)

File:TrumpPortrait.jpg

I cannot edit File:TrumpPortrait.jpg as it is locked. The source should be the following: https://x.com/dto_rok/status/1879743327781945429. PascalHD (talk) 23:09, 20 January 2025 (UTC)

 Done Added to source field. Abzeronow (talk) 23:18, 20 January 2025 (UTC)

Category:King George Henry

King George Henry (talk · contributions · Move log · block log · uploads · Abuse filter log) block user is a blocked user. He created this personal useless category thta should be deleted

 Done: deleting junk; strong final warning given. Any continuation should result in a block. - Jmabel ! talk 04:59, 21 January 2025 (UTC)

Remove the autopatrolled of User:BlackShadowG

The user is deceased. Пусть от победы☆к победе ведёт! 09:41, 21 January 2025 (UTC)

 Done RIP. Yann (talk) 10:24, 21 January 2025 (UTC)

questionable uploads by User:Wave of Pandas

This user has been uploading images starting in January 2024. The images are all night scenes in Hong Kong. None of them are useful, and some e.g. File:Panda wave.jpg, File:Lot of pandas.jpg seem to me silly. There are already a huge number of images of Hong Kong, most provided by very good photographers. Is this behavior an Administrator could examine? Thank you. Krok6kola (talk) 17:34, 21 January 2025 (UTC)

Possible block evasion by User:EX Centre from Star Avenue 2018? Omphalographer (talk) 18:04, 21 January 2025 (UTC)

The photos lack a description and categories but the quality is absolutely fine. I only see a problem with the panda photos as I a think they are not permanent and therefore not covered by FOP. GPSLeo (talk) 19:03, 21 January 2025 (UTC)

The photographs are the same low quality and subject matter (Hong Kong). I think you are right. Krok6kola (talk)

Update Needed: {{User admin}} Template on User Profile

Noticed that User:Srittau still has the {{User admin}} template on their user profile page, which might give the impression that they are still active.--SimmeD (talk) 21:21, 21 January 2025 (UTC)

Thanks. Also, could an admin unprotect the page again? I don't think the protection is still necessary. Sebari – aka Srittau (talk) 22:03, 21 January 2025 (UTC)

 Done to both. Abzeronow (talk) 22:09, 21 January 2025 (UTC)

Possible edit filter use case

Hello,

a fellow Wikimedia noticed that the graphics resource page Redbubble apparently produces a CMS naming pattern that is quite peculiar and visible on several files on Commons, see Commons:Administrators' noticeboard/Blocks and protections#File:Flat,750x,075,f-pad,750x1000,f8f8f8.jpg. I'd like to suggest an edit filter to tackle the likely COM:NETCOPYVIOs that these files make us incur. Its conditions could be in kind of pseudocode "IF NOT member of license reviewers AND action=upload of filename= *f8f8f8. THEN... // tracking or outright forbidding the upload". Tracking may be wiser, so as to spot the copyvios without encouraging the uploaders in making up avoidance filenames. Or, if the restriction to license reviewers is too strict, a check for the right of uploadfromurl could also work (if the filters allow that). I'd rather not have only autoconfirmed as threshold, as some amount of experience in dealing with internet sourced images would be needed to gauge whether the Redbubble graphics may be OK for us to host. Grand-Duc (talk) 01:54, 22 January 2025 (UTC)

@Grand-Duc, Autopatrolled should do the trick. All the Best -- Chuck ^Talk 03:33, 22 January 2025 (UTC)

Sock false tagging

a sock account is tagging files I have uploaded with missing copyright tag though they have proper licenses Baratiiman (talk) 07:35, 22 January 2025 (UTC)

Hi, It is not a sock account but Modern Sciences. However I don't think the deletion requests are justified, so I removed them. Yann (talk) 09:24, 22 January 2025 (UTC)

File:Flag of the Resident Commissioner of Basutoland.svg

What happened to file File:Flag of the Resident Commissioner of Basutoland.svg? Not loading, seems to be an error. Can you fix it? Otherwise, maybe just delete the file. Greetings, זיו「Ziv」 • For love letters and other notes 14:03, 22 January 2025 (UTC)

Clicking directly on the file I see "error on line 92 at column 38: Namespace prefix inkscape for connector-curvature on path is not defined", although that doesn't explain why this wasn't an issue before. I wondered if it was related to Phab:T384128, but that showed a different error. CMD (talk) 14:17, 22 January 2025 (UTC)

@Ziv and @Chipmunkdavis: Perhaps another task is in order.   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 14:34, 22 January 2025 (UTC)

Yes, if you click too many times you will see a meta screen saying "Error, too many requests". זיו「Ziv」 • For love letters and other notes 17:06, 22 January 2025 (UTC)

There are some errors in svg. Maybe @AntiCompositeNumber or someone well-versed in SVG editing can help. It is unrelated to admin' workload imho. _Regards, Aafi ^(talk) 17:11, 22 January 2025 (UTC)

Fixed, the file had some undefined XML attributes that are now treated as invalid. It looks like it got created in Inkscape, then edited in Adobe, and didn't get cleaned up correctly. I removed them and both the browsers and rsvg-convert are happy. In the future, COM:VPT is usually a better place to ask, but feel free to ping me about thumbnailing issues. AntiCompositeNumber (talk) 17:53, 22 January 2025 (UTC)

Thank you very much and also for the tip about the village pump. If I come across something like that again, I will contact them. Best regards, זיו「Ziv」 • For love letters and other notes 20:05, 22 January 2025 (UTC)

This section is resolved and can be archived. If you disagree, replace this template with your comment. --זיו「Ziv」 • For love letters and other notes 19:57, 23 January 2025 (UTC)

URGENT! Major damage to this project

As far as I can see, major damage has successively been done to Wikimedia Commons over the last few years by chopping up categories about people into individual "by year" categories making it

1. virtually impossible to find the best image to use for a certain purpose, and
2. virtually impossible to avoid uploading duplicates since searching/macthing imges has become virtually impossible.

Here is a perfect exsmple. I have a really good, rare picture of her, but I'll be damned if I'm willing to wade through all the "by-year" categories to try to see if Commons already has it. The user who uploaded this didn't even bother to place it in a personal category. Why should they, with all the work required to try to find the category at all & fit the image in there?

What if anything can be done about this mess which is steadliy getting worse all the time? Could some kind of bot fix it?

I really feel that this is urgent now and cannot be ignored any longer. The project had become worth much much much less through the problem described. Or have I missed/misunderstood something here? SergeWoodzing (talk) 21:42, 22 January 2025 (UTC)

Person by Year can be useful if there are a lot of images of a person so breaking it down by year can be useful. Now categorized into Sophie of Sweden category. Abzeronow (talk) 21:51, 22 January 2025 (UTC)

This is not an urgent thread to the project that would require immediate admin action. This is a regular discussion on guidelines and best practices and has already been discussed in the past without a clear outcome. If you want to make a new proposal on this use the Commons:Village pump/Proposals board. GPSLeo (talk) 21:51, 22 January 2025 (UTC)

OK I've moved this there. Amazed that someone would defend the existence of the by-year categories. I have not questioned their existence. Searching is the problem. --SergeWoodzing (talk) 10:02, 23 January 2025 (UTC)

I've started a CfD Commons:Categories for discussion/2025/01/Category:Sophie of Sweden by year and I agree with GPSLeo that this is NOT an urgent matter that requires immediate admin action. Abzeronow (talk) 21:57, 22 January 2025 (UTC)

@SergeWoodzing: Have you tried mw:Help:CirrusSearch#Deepcategory?   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 05:15, 23 January 2025 (UTC)

Uploads made by User:Estradadarwin16

Hi. I would like to seek assistance in deleting all of the images uploaded by User:Estradadarwin16 since these are mostly copyrighted logos. The said user was already blocked last December 13 and most of his uploaded images are yet to be deleted. -WayKurat (talk) 06:13, 23 January 2025 (UTC)

I've deleted the obvious copyvios. The remainders are plausibly {{PD-textlogo}} or {{PD-shape}} and will need a closer look. Pi.1415926535 (talk) 06:27, 23 January 2025 (UTC)

 Done. I nominated one more logo for regular deletion. Taivo (talk) 10:25, 23 January 2025 (UTC)

999real

• 999real (talk · contribs · deleted contribs · logs · edit filter log · block user · block log)

Unapproved bot. — Tarkoff / 13:58, 23 January 2025 (UTC)

No, I just used VisualFileChange...  $999$REAL 💬 ⬆   15:02, 23 January 2025 (UTC)

I guess they mean you'd need some consensus before performing those changes Bedivere (talk) 15:12, 23 January 2025 (UTC)

@999real: What did you change, and why?   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 16:56, 23 January 2025 (UTC)

I changed the template on many files with YouTube source and {{cc-by-3.0}} to {{YouTube|author}}  $999$REAL 💬 ⬆   16:59, 23 January 2025 (UTC)

@999real: You were editing files at a speed of 200 changes per minute, which is why I wrote this request. That's a very high speed. The template replacement task is not urgent, so it can be done at a low speed. — Tarkoff / 18:20, 23 January 2025 (UTC)

@Tarkoff: AFAICT, VFC has no adjustment for speed.   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 18:26, 23 January 2025 (UTC)

I didn't touch any setting in VisualFileChange. I do see it has option "Maximum number of requests to send to the API simultaneously" defaulted to 5, I will try setting it to 1 in the future.  $999$REAL 💬 ⬆   18:49, 23 January 2025 (UTC)

 Not done No action needed. @999real: you're fine. The Squirrel Conspiracy (talk) 22:59, 23 January 2025 (UTC)

Thanks  $999$REAL 💬 ⬆   00:59, 24 January 2025 (UTC)

User:GabagoolMuncher

User here has gamed the system for almost all of their edits by repeatedly reverting images over and over without explanation. 🗽Freedoxm🗽 (talk) 22:31, 23 January 2025 (UTC)

Oh, it's the useless flag revert LTA. Blocked. The Squirrel Conspiracy (talk) 23:03, 23 January 2025 (UTC)