Jump to content

Commons:Administrators' noticeboard

From Wikimedia Commons, the free media repository
Latest comment: 5 minutes ago by Loopy30 in topic Picture of the day - 02 Apr 2026

Shortcut: COM:AN

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-reports@wikimedia.org instead. If reporting threatened harm to self or others also email emergency@wikimedia.org.

Vandalism
[new section]
User problems
[new section]
Blocks and protections
[new section]
Other
[new section]

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
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
129, 128, 127, 126, 125, 124, 123, 122, 121, 120, 119, 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
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
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

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.


Could we change the protection to to something that still allows users like me access without relying on an admin?--Trade (talk) 06:32, 27 March 2026 (UTC)Reply

Fully protected for a year. Instead, I would autopatroller-protect it indefinitely, because during one year nothing special will happen in this matter. Taivo (talk) 09:41, 27 March 2026 (UTC)Reply
So, are you gonna do it? Trade (talk) 20:07, 28 March 2026 (UTC)Reply
Taivo, I agree. Vandalism of that file page seems limited to new users and anons. Even semi-protection would possibly be sufficient, but it should be much longer than a year. More like 10 years if not indefinite. Nothing special will happen to the matter in 10 years, but the image might get superseded in articles at some point which would remove the heat. - Alexis Jazz ping plz 21:25, 28 March 2026 (UTC)Reply
✓ Done. I changed protection. Now indefinitely autopatroller-protected. Taivo (talk) 21:38, 28 March 2026 (UTC)Reply

Request for file page protection

Hello, I request protection of this file page. This is a historical image (circa 1908) and is in the public domain. To prevent possible incorrect edits or vandalism, please consider protecting this page. Thank you.

https://upload.wikimedia.org/wikipedia/commons/d/de/Kunwar_Vishwanath_Singh.jpg Dy2834 (talk) 15:35, 27 March 2026 (UTC)Reply

@Dy2834: Please use internal links like File:Kunwar Vishwanath Singh.jpg.   — 🇺🇦Jeff G. please ping or talk to me🇺🇦 15:39, 27 March 2026 (UTC)Reply
Thanks you noted! I will use the proper internal link format File:Kunwar Vishwanath Singh.jpg for the protection request. 🙏 Dy2834 (talk) 15:45, 27 March 2026 (UTC)Reply
@Dy2834: We do not protect files unless there is on-going vandalism, which is not the case here. I fixed the license for you. Please do it yourself next time, and please add a source and categories. Yann (talk) 17:36, 27 March 2026 (UTC)Reply
Thanks for fixing the license and the guidance! I will make sure to add a source and categories myself next time. Dy2834 (talk) 02:31, 28 March 2026 (UTC)Reply
Checkmark This section is resolved and can be archived. If you disagree, replace this template with your comment. Shaan SenguptaTalk 13:48, 28 March 2026 (UTC)

Cleaning up CfDs

There are a lot of long-running CfDs that it would be nice to resolve, and I encourage everyone to consider helping out on that front.

Here's a couple I noticed that I don't feel competent to resolve, but the necessary information seems all to be there: Commons:Categories for discussion/2017/10/Category:Euphrasia officinalis, Commons:Categories for discussion/2017/10/Category:Euphrasia rostkoviana. Probably someone better at taxonomy categories than I am can resolve these two in 10 minutes or less. - Jmabel ! talk 04:55, 31 March 2026 (UTC)Reply

Unclosed deletion request – File: Kamil Art Fine art - Monika Bacardi (cropped).png

Hello,

I would like to kindly request administrative review of the following deletion request, which has been open for over a month without resolution:

https://commons.wikimedia.org/wiki/Commons:Deletion_requests/File:Kamil_Art_Fine_art_-_Monika_Bacardi_(cropped).png

The source is no longer verifiable and no evidence of a valid license has been provided.

Thank you in advance for your time and assistance. LicenseConcern2026 (talk) 11:40, 31 March 2026 (UTC)Reply

@LicenseConcern2026: Why does this one deserve special consideration over the ones which have been open for 202 days per COM:DR?   — 🇺🇦Jeff G. please ping or talk to me🇺🇦 11:46, 31 March 2026 (UTC)Reply
@LicenseConcern2026 adding to what Jeff G. said, one month isn't a long time for a regular DR. We have a lot more older DRs open. Also rather than nominating the cropped version, you should've nominated the main file. This cropped version would have followed the same path instantly. Shaan SenguptaTalk 12:07, 31 March 2026 (UTC)Reply
✓ Done
Gbawden (talk) 07:29, 1 April 2026 (UTC)Reply

Emergency spam filter

Because of the recent spam attack, I created an abuse filter throttling links added by new accounts Special:AbuseFilter/344. If there is no new spam and complaints from regular users, just disable or change it. GPSLeo (talk) 20:38, 31 March 2026 (UTC)Reply

Speedy decision for a deletion request

Hello, in my opinion Commons:Deletion requests/File:Musical instruments used in Strauss's Second Waltz.webm can be decided by speedy deletion, see my answer there. It needs, though, some cleanup on the file page itself, as well. — Speravir01:34, 1 April 2026 (UTC)Reply

Could someone delete all files by user:Europeancreatorsofai?

This is a seemingly abandoned spam account and most of it’s either AI slop or OOS anyway. Dronebogus (talk) 15:46, 1 April 2026 (UTC)Reply

Looks like there's now two separate deletion discussions for perhaps the same files. I didn't check all of them. RadioKAOS / Talk to me, Billy / Transmissions 16:29, 1 April 2026 (UTC)Reply
As of now, their only surviving upload is a coat of arms with {{Fact disputed}}. - Jmabel ! talk 19:25, 1 April 2026 (UTC)Reply
✓ Done. At first I hesitated, but after I found a sockpuppet, I decided to nuke them all. Taivo (talk) 08:20, 2 April 2026 (UTC)Reply

Please nuke Special:Log/upload/Worvandae

Per CentralAuth and m:Special:Permalink/29346267 § Global lock for Worvandae, the user is a verified sock of Đăng Đàn Cung. Whyiseverythingalreadyused (t · c · he/him) 06:57, 2 April 2026 (UTC)Reply

Oh yeah Special:Log/upload/Nguyen.Bao.Anh.9321 too Whyiseverythingalreadyused (t · c · he/him) 07:43, 2 April 2026 (UTC)Reply

Henry_Joseph_Hagger_(1).jpg

The above is one of a set of images from books dated between 1898 and 1912, which I have been photographing, titling, and uploading to Commons (see my contribs). Today I have been blocked (without formal notification on my talk page etc) from uploading the above very dull and respectable image of a 19th-century headmaster and vestry clerk with a beard. I have used the same type of licensing and sourcing for all of this set. Perhaps today my text has included some typo which I cannot identify. I have tried to rewrite the page title and text contents, with no successful upload permission.

The bot message is: "The page title "File:Henry Joseph Hagger (1).jpg" is restricted from editing or creation because it matches the following entry on the local or global blacklist: .*[НH]\W*[AΑΑ]\W*G\W*G\W*[EЕΕ]\W*R(?!(sta|ston|ty)).*, intended to prevent vandalism." I cannot see any parallel between this bot complaint and my page title or page text.

My latest (failed) attempt at a bot-pleasing page text is as follows:


Description Short biography of Henry Joseph Hagger (1828–1911), headmaster and vestry clerk.
Date
Source Pike, W. T. (1911). Pike, W. T. (ed.). Liverpool and Birkenhead in the Twentieth Century: Contemporary Biographies. Brighton, Sussex: W. T. Pike & Co
Author William Thomas Pike (died 1924)
Permission
(Reusing this file)
This is a faithful photographic reproduction of a two-dimensional, public domain work of art. The work of art itself is in the public domain for the following reason:
Public domain

The author died in 1924, so this work is in the public domain in its country of origin and other countries and areas where the copyright term is the author's life plus 100 years or fewer.


You must also include a United States public domain tag to indicate why this work is in the public domain in the United States.
This file has been identified as being free of known restrictions under copyright law, including all related and neighboring rights.
The official position taken by the Wikimedia Foundation is that "faithful reproductions of two-dimensional public domain works of art are public domain".
This photographic reproduction is therefore also considered to be in the public domain in the United States. In other jurisdictions, re-use of this content may be restricted; see Reuse of PD-Art photographs for details.
Public domain

This work is in the public domain in its country of origin and other countries and areas where the copyright term is the author's life plus 70 years or fewer.


This work is in the public domain in the United States because it was published (or registered with the U.S. Copyright Office) before January 1, 1931.

This file has been identified as being free of known restrictions under copyright law, including all related and neighboring rights.

Category:Henry Joseph Hagger


All my work is rather dull and inoffensive. I never use AI to compose text or images on WP. I do tidy up images on Gimp, but do not change content or practice deception. I cannot imagine what I could be doing worng. Please could you kindly let me know how I can continue my work without this bot blocking me? Thank you Storye book (talk) 08:43, 20 March 2026 (UTC)Reply

Update. I have now realised that the bot does not like the word, "Hagger" (the surname of the subject of the picture). Is that a vulgar or blasphemous word in American English? As an English person, I am not aware that the word is offensive in other versions of English, but maybe it is? For the present, I have changed "Hagger" to "Haggeer" on the filepage, and shall do so for the other pictures of him that I intend to upload. However this is a problem. This man was and still is a well-respected historical character in his town, and it will now be difficult for the people of his town to find his picture and details on Commons. Is there a way to solve this? Thank you. Storye book (talk) 11:20, 20 March 2026 (UTC)Reply
Note: the present upload is under the false name of "Haggeer": Henry Joseph Haggeer. Storye book (talk) 12:37, 20 March 2026 (UTC)Reply
@Storye book: Sorry, File:Henry Joseph Hagger (1).jpg is not an allowed title because of inclusion on our title blacklist with last modification Special:Diff/1141128360 and initial modification Special:Diff/9530690 to combat an LTA who has been attacking our project for over 15 years. Of course, any Admin could make an exception for that filename in particular. Do you contemplate any other specific filenames?   — 🇺🇦Jeff G. please ping or talk to me🇺🇦 14:19, 20 March 2026 (UTC)Reply
@Jeff G.: Thank you. The reason why I used that filename is that Henry Joseph Hagger is the man's name. Anyone wanting to write an article about him will need to use the surname "Hagger" as part of the title. As a page title for Wikipedia, or for Commons filename, or Commons category name, we would only need to use the variations "Henry Joseph Hagger", "H. J. Hagger", "H.J. Hagger", and "Hagger (surname)". Surely those exceptions could be permitted in this case? I cannot imagine that your vandal would consider using those variations for their activities? Wikidata already permits "Henry Joseph Hagger" as a Wikidata title, as is currently included on the Commons "Category:Henry Joseph Haggeer" page. So please would you kindly un-ban the variations which I have bolded above? So long as I am alive and working (maybe the next ten years if I am lucky – I am old) I shall be able to notice and report any vandal infractions on those pages. I check my watchlist daily for most of the year. Storye book (talk) 17:45, 20 March 2026 (UTC)Reply
Seems to me we could modify the regex to simply allow "Hagger". It's a real name, and far enough from the word at issue that it ought to be fine. Any objections? - Jmabel ! talk 20:57, 20 March 2026 (UTC)Reply
and, yes, we'd have to make sure there isn't an "N" before the "H". - Jmabel ! talk 20:59, 20 March 2026 (UTC)Reply

END of what was recovered from archive - Jmabel ! talk 03:43, 27 March 2026 (UTC) Reply
Is there someone comfortable with regexes who would like to take this on? It's a little tricky; I'm sure I could do it, but not quickly, and if there is someone for whom this is easy, please take it. - Jmabel ! talk 03:45, 27 March 2026 (UTC)Reply

Thank you for your reply, Jmabel. I look forward to seeing this issue resolved. Storye book (talk) 09:04, 27 March 2026 (UTC)Reply
I believe this edit should let "Henry Joseph Hagger" through without letting through any other additional string. Someone may want to check my work. - Jmabel ! talk 18:28, 27 March 2026 (UTC)Reply
Thank you, Jmabel. I'm not sure whether you wanted me to test it, or an admin. Anyway, I tried to move the page title Category:Henry Joseph Haggeer to Category:Henry Joseph Hagger, but as before, the bot would not let me, for the same reason as given above. Storye book (talk) 18:50, 27 March 2026 (UTC)Reply
Oh, of course! I tested it on the string "Henry Joseph Hagger", but not with anything before or after that! - Jmabel ! talk 19:13, 27 March 2026 (UTC)Reply
@Storye book: Special:Diff/1187731050 should fix it, but I'm a bit concerned about bad side effects. I suspect that if the string contains "Henry Joseph Hagger" then it can also contain the "bad" content this was meant to prevent, because it will already have passed the test before that is explored.
If someone can craft this better than I can, please do. - Jmabel ! talk 19:18, 27 March 2026 (UTC)Reply
Thank you, Jmabel. I appreciate that this isn't easy, and your efforts are much appreciated.
@Zzuuzz: please could you kindly take a look at this problem for us? Thank you. Storye book (talk) 19:29, 27 March 2026 (UTC)Reply
Jmabel seems to be doing a fine job, better than this non-commons-admin could do, but the regex seems to be checking for Hagger twice. I would probably try something like: (?<!Henry Joseph|H\. ?J\.) [H]AG.... And in terms of allowing problems, I'd think it would be OK. zzuuzz (talk) 20:07, 27 March 2026 (UTC)Reply
Thank you very much to Jmabel and Zzuuzz for kindly resolving most of the above issue. I have now been able to restore both the category name and filenames from "Henry Joseph Haggeer" to "Henry Joseph Hagger". One issue remains, though. The bot still does not permit the category "Hagger (surname)". It would be lovely if that could also be resolved - although I guess we could live without it unless or until pictures of other historical persons called Hagger turn up on Commons. Thank you both again for your trouble. Storye book (talk) 09:12, 2 April 2026 (UTC)Reply

Datasets about potential logos - March 2026 uploads

Hi all, we have released a new dataset of potential logos uploaded in March 2026, together with another one of those which have already been deleted as of 2026-04-02. We are sharing them with you for your consideration.

This is part of our current work with the logo detection tool. We hope it will be useful for your moderation activities.

If you encounter issues with the datasets or have comments/requests, please reach out to me or to Sannita (WMF).

Thanks for your attention! –-MFossati (WMF) (talk) 11:30, 2 April 2026 (UTC)Reply

Picture of the day - 02 Apr 2026

The English caption of the picture of the day has a typo. It should be Poplar hawk-moth (or even better - Poplar hawkmoth), and not Poplar hawk-mot. Loopy30 (talk) 11:44, 2 April 2026 (UTC)Reply