Jump to content

Commons:Administrators' noticeboard/User problems

Add topic
From Wikimedia Commons, the free media repository

Shortcuts: COM:AN/U • COM:ANU • COM:ANI

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
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
134, 133, 132, 131, 130, 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
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
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

Note

  • Before reporting one or more users here, try to resolve the dispute by discussing with them first. (Exception: obvious vandal accounts, spambots, etc.)
  • Keep your report as short as possible, but include links as evidence.
  • 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/U|thread=|reason=}} ~~~~ is available for this.
  • It is important to keep a cool head, especially when responding to comments against you or your edits. Personal attacks and disruptive comments only escalate a situation; Please try to remain civil with your comments.
  • Administrators: Please make a note if a report is dealt with, to avoid unnecessary responses by other admins.

ImperialHerald

[edit]

ImperialHerald (talk · contributions · Statistics · Recent activity · block log · User rights log · uploads · Global account information)
Repeated Copyios and obvious trolling, the user being uploading purposeless heraldic raster files duplicated or extracted from existing svgs, example with this CC0 file extracted from the CC3 svg, and the associated trolling. Other example: pointless png file created from the svg, and, incidentally PD. & with the associated trolling.--Kontributor 2K (talk) 09:45, 17 October 2026 (UTC)Reply

TBH, I'm much more concerned about your behaviour here, and would certainly support a large boomerang. Andy Dingley (talk) 19:07, 17 October 2026 (UTC)Reply
You're right, everything back to normal soon: example #1, example #2, etc. ✓ Done --Kontributor 2K (talk) 19:38, 17 October 2026 (UTC)Reply
What do you mean by that? Andy Dingley (talk) 00:25, 18 October 2026 (UTC)Reply
I meant that User:ImperialHerald had all their files restored to their original state, and that they will never hear about me again.
I'll add that this commitment applies, in future, to any case that I might find to be similar, whether closely or remotely.--Kontributor 2K (talk) 06:18, 18 October 2026 (UTC)Reply

@Andy Dingley:
Concerning your message on the user's tp, it's not just a matter of crediting the source SVG image, but also of ensuring that the license is compatible, as it can be read here for an example, or here on the CoA from which appears to have been taken this element which, by the way, is now, strictly speaking, simply a representation of a king and should therefore rather be in a category such as Category:Kings in heraldry, although it could as well be qualified a simple icon; another matter, by the way, being that there is no category like Category:SVG coat of arms elements - men for such extracted raster models. Perhaps it would relevant to create some, for the occasion.
So, above all, for now it's important to take all the time needed to go through all the files carefully to work out which files they were created from, and then to amend the licences accordingly – without forgetting, where necessary, to remove the corresponding structured data so that the files do not end up in the maintenance categories. If the user, according to this topic puts ‘most of their work into the public domain', it shouldn't be a problem though.
We also need to monitor all the new uploads until the user is fully autonomous, both in terms of licences and categorisation, for that matter.
For an example, this file, put in the public domain, does not credit any of the images used; here too, one needs to track down all the files used and amend the page accordingly. Furthermore, and by the way, we now stand with files that are completely at odds with the context, and the concept, in Category:Heraldic tinctures.
Also, I couldn't find a source image on Commons for File:Harp cendree, stringed argent.png and File:Heraldic fox mask.png; I would say, just to be on the safe side: ‘obviously own work'.
As for Category:Shield shape, mentioned in your message, it's a category I didn't know existed, which is actually a subcategory of Category:Shapes, and Category:Shields which is itself a subcategory of Category:Armour parts, so not an heraldic category at all; such files are generally put somewhere in there. Incidentally, the user actually categorised the files here –they were later moved by the bot–, which is hardly worth mentioning, given that ‘not looking where we put the files' seems to be a national sport on Commons.
That being said, in my view there is not just a question of file format –raster or svg–, but also maybe of en:WP:CIR –from some point of view–, and of COM:SCOPE, given that it's impossible for the files below, for an example, to be used on any wiki –or anywhere else for that matter:

Otherwise, perhaps it would be worth creating, still for the occasion, a global aside category named ‘Heraldry by children' or ‘Heraldry for children', or so, wouldn't it? So that people looking for this kind of images could find theme more easily –I mean that they won't ever find them on a wiki page like, for an example, this one, or even on a Category header, like here.
I'd like to take the opportunity to mention, in passing, that the example png-escallop is miscategorised, for only coats of arms (usually) stand in Category:Escallops argent, therefore it should be moved to Category:Escallops, since we don't scatter CoA elements in heraldic subcategories, whatever their colour.
In fact, we are currently witnessing the creation of some parallel heraldic portal, here one Commons, on a user page, since the image can't be used elsewhere –with the associated Category-stuffing–, where indeed ‘anyone can contribute'; so can you.
--Kontributor 2K (talk) 14:52, 21 October 2026 (UTC)Reply

user:A.Savin

[edit]

We know each other for a long time, the user is regularly rude towards me, but usually it had no sense to mention; this time he absolutely crossed the borders - the reason, the reaction. I'm asking for a topic ban for this user - not to write me on my talk page and not comment any my action even in an edit description anymore. I believe that Commons will survive if my small and rare mistakes will be corrected silently or by other people. And if he will continue to do something like this with others, I hope it will be useful to document that he can be like that. Анастасия Львоваru/en/de 17:13, 1 October 2026 (UTC)Reply

The user is notified. Анастасия Львоваru/en/de 17:14, 1 October 2026 (UTC)Reply
Was ist das Problem? Achso, Sie haben abermals Commons-Regeln verletzt, allen voran COM:OVERCAT, und hatten teilweise die Kategorie "Ships in Bremerhaven" dort hinzugefügt, wo gar keine Schiffe dargestellt sind. Und nun fühlen Sie sich beleidigt, dass ich die Edits zurückgesetzt und Ihnen eine Verwarnung geschickt habe. Ja nee, klar. --A.Savin 17:48, 1 October 2026 (UTC)Reply
abermals Commons-Regeln verletzt. Genau deswegen frage ich nach einem Topic Ban. Vielen Dank für die Demonstrationen. Анастасия Львоваru/en/de 18:11, 1 October 2026 (UTC)Reply
  • The problem is the hostility of your response. The OP moved a photo of a ship to an appropriate subcategory for ships. This was a good edit. You reverted them, also issued a vandalism warning. That is a hostile act and should not be taken unless the editor is clearly a vandal.
At most, you have a difference of opinion with this editor. On the evidence so far there is one edit where I would support your reversion, but in a batch of edits about a harbour it's not unreasonable if one is accidentally moved to a ships category when there is no ship present in that one. Editors are all fallible. This is not vandalism and it is not acceptable admin behaviour for you to treat it as such.
This is also typical behaviour for you, and has been so for a very long time. Andy Dingley (talk) 18:16, 1 October 2026 (UTC)Reply
+1. And support proposal for A.Savin to stay off of Lvova's user talk page. I'm not sure the "not commenting" in an edit description can entirely be enforced (and I wouldn't want to discourage A.Savin from using edit summaries), but certainly it is reasonable to ask him refrain in edit summaries from any suggestion of bad intent in the edits by Lvova or any established editor. A.Savin, if you really think Lvova or any other user is editing with bad intent, you can feel free to bring it here to COM:ANU, but please don't do so frivolously or out of pique. - Jmabel ! talk 14:04, 2 October 2026 (UTC)Reply
 Support. I was the victim of Alexander's uncivil personal attack and dismissal of my evidence in this edit 08:48, 17 March 2025 (UTC). For background, my report was technically correct, as I had previously given @Kürschner a final warning for uploading coypright violations in this edit 16:58, 25 February 2025 (UTC). Copyright violations endanger Commons, the WMF, and both internal and external reusers. I brought Commons:Civility over from English Wikipedia in this edit 10:39, 6 April 2019 (UTC) and refined it for use on Commons; others helped, and it is now policy. I just warned him.   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 14:24, 2 October 2026 (UTC)Reply
Well, seriously, you are accusing me of calling someone's incorrect edit vandalism because in your opinion that was actually a good-faith edit; but on the other hand you are talking of this particular Kürschner's upload as a copyvio by purpose, despite the fact that it is pretty obvious that this was a mistake too and you are accusing a clearly benevolent regular of nothing lesser than a copyright violation? And myself of supporting copyvios? Even you yourself don't know exactly, LOL... Maybe you should, just like in that famous joke about two Jewish guys naked in a bathhouse, seriously consider to "either remove your cross necklace or put your underpants on" ;-) --A.Savin 18:17, 2 October 2026 (UTC)Reply
@A.Savin: this thread is not about Jeff G.'s conduct, it is about yours. Deflecting is not going to help your case. - Jmabel ! talk 20:51, 2 October 2026 (UTC)Reply

With no sysop's reaction about me he continues like that, that, that and that directed at others. Анастасия Львоваru/en/de 18:08, 18 October 2026 (UTC)Reply

@Lvova: sorry I dropped the thread. I was traveling. I assumed some other admin would pick it up, but no one did. - Jmabel ! talk 20:59, 18 October 2026 (UTC)Reply
@A.Savin: If you have a serious complaint about Jeff G.'s edits, start a separate thread on this page about that. Otherwise, please let us stick to discussing your own conduct on this thread. If there is something specific where you think Lvova has also misbehaved, that would be relevant here; other parties' conduct is not. - Jmabel ! talk 21:01, 18 October 2026 (UTC)Reply
Personally, I think that what Lvova is asking for sounds entirely reasonable. The one concern I have is that if A.Savin is prevented from touching Lvova's work, Lvova has to also stay largely away from A.Savin's work. A.Savin: besides your own uploads, are there any particular areas where you work heavily, and Lvova sometimes "passes through," where the topic ban would be more workable if Lvova stays away from that work area? - Jmabel ! talk 21:07, 18 October 2026 (UTC)Reply
Are you joking? He stalks people wherever he appears, and based on this, I will be advised not to show up where there is a risk of running into him (QI, FI, photographs from Russia and Germany)? Анастасия Львоваru/en/de 11:48, 19 October 2026 (UTC)Reply
@Lvova: No, those wouldn't be reasonable requests on his part. But if you don't want him commenting on or altering your edits, you also have to stay away from where he has edited substantively, and if there are particular subject matter areas where he works routinely and you don't it would be reasonable for him to ask you to stay away from those as part of the disengagement you say you want. But so far he hasn't said anything, and if he doesn't come back here with something specific then the topic ban will happen without any reciprocity. - Jmabel ! talk 23:45, 19 October 2026 (UTC)Reply
Every day still the same. Анастасия Львоваru/en/de 16:44, 19 October 2026 (UTC)Reply
Wikimedia projects are aging, and their long-time veteran contributors are aging with them. Over time, such participants often "withdraw into themselves" and begin to live by their own version of the rules. And they are less and less inclined to take into account the opinions and actions of other participants. Calling everything he doesn't like "vandalism" is a typical example of this stage. (Out of politeness, I will refrain from more precise definitions.)
It seems colleague A. Savin has no intention of changing his behavior. In my opinion, if we limit ourselves to another stern warning now, then the next time the same thing happens, we should begin the process of revoking extended access rights. It looks like that will happen soon. --Kaganer (talk) 16:29, 21 October 2026 (UTC)Reply
@Kaganer I'm not sure what you mean by revoking extended access rights, since A.Savin was already desysopped by the U4C for incivility a year ago. At what point do we say enough is enough and start making blocks? AntiCompositeNumber (they/them) (talk) 22:55, 21 October 2026 (UTC)Reply
I'm sorry, my mistake. These was "revert", not "rollback"... Then only blocking, unfortunately... --Kaganer (talk) 23:11, 21 October 2026 (UTC)Reply

Conclusion

[edit]

A.Savin has been editing Commons, and has not come here to indicate any reciprocal limitations he would want on Lvova to make a topic ban more workable. At this point, it looks like a topic ban is the low end of what anyone here other than A.Savin seems to believe would be appropriate, and that is what was requested by Lvova, the person with the complaint here, so that is where I'm going.

A.Savin is directed not to write on Lvova's user talk page and not to comment any of Lvova's actions, either in an edit description or elsewhere. He is strongly urged to stay out of matters in which Lvova has been involved, with the understanding that he can't be expected to thoroughly check every file history before making an edit, especially any mass action that might incidentally touch a file Lvova has worked on. Still, I urge A.Savin to stick to the spirit of this as well as the letter; if this comes back to an admin matter again, expect admins to consider whether the spirit of this has been violated, not just the letter. I don't think the next step in case of violation would be a stricter topic ban; it would be a block. - Jmabel ! talk 02:47, 22 October 2026 (UTC)Reply

And he immediately commented my actions again with a demonstration, that he didn't understand the problem, and another sysop didn't stop it, almost supported (Das du inhaltlich recht hast, hat auch niemand angezweifelt) - I doubt, that no one disputes. Анастасия Львоваru/en/de 11:58, 22 October 2026 (UTC)Reply
I'll leave it to GPSLeo to comment on that, since he seems to be already involved. - Jmabel ! talk 17:16, 22 October 2026 (UTC)Reply
How is writing that a behavior is not acceptable an "almost support"? For the second one I have to apologise, you are correct that some of the reverts also where nonsense edits. I only had a look at some of the category edits where the revert was correct or opposing in QI and FP was justified. GPSLeo (talk) 17:43, 22 October 2026 (UTC)Reply
It's possible to explain how, but I think there is no need after the clarification, thank you. Анастасия Львоваru/en/de 18:52, 22 October 2026 (UTC)Reply

Special:Diff/1290130793 shows that I have informed A.Savin of this on his user talk page. - Jmabel ! talk 02:54, 22 October 2026 (UTC)Reply

User:Y22021996

[edit]

Y22021996 (talk · contributions · Move log · block log · uploads · Abuse filter log)  Y22021996 received their last warning for copyvio in April, and in April was also blocked for 1 week, then 1 month for copyvio. They now upload with source information, but list incorrect licenses that state the files are in the public domain when they don't meet the listed requirements of the license (e.g., File:ES Tunis 1994.jpg uses {{PD-Algeria}}). — Wracking ( talk / contribs / uploads ) 04:03, 19 October 2026 (UTC)Reply

✓ Done Indef. They're probably well meaning, but clearly don't get copyright and haven't used the last two blocks as opportunities to figure it out. Enough is enough. The Squirrel Conspiracy (talk) 04:36, 19 October 2026 (UTC)Reply

User:Fontenoy (1858)

[edit]

Fontenoy (1858) (talk · contributions · Move log · block log · uploads · Abuse filter log)  I was adding something (Category:La Meuse beer) and I got blocked. I tried to report the block, Commons:Abuse filter/Error reporting , but I ended up getting blocked again (LTA 263) while attempting to submit that report. If the reporting mechanism itself is blocked, is there nothing that can be done? Fontenoy (1858) (talk) 12:58, 19 October 2026 (UTC)Reply

@Fontenoy (1858): Hi. I am sorry that the former permissiveness of Commons has allowed so much abuse that Admins here had to enact such draconian private abuse filters that you got caught. The private ones may involve certain keywords and behaviors that I am not allowed to know due to the private nature of those filters regarding Long Term Abuser 263. Avoiding those exact keywords and behaviors when reporting would be your next best bet.   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 13:52, 19 October 2026 (UTC)Reply
Fontenoy (1858), this should be resolved. Please try your edit(s)s again. (I trust you understand that a new user attempting to add "bastard" has been historically abused.) Эlcobbola talk 16:55, 19 October 2026 (UTC)Reply
@Elcobbola: "You do not have permission to see details of this entry."   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 20:10, 19 October 2026 (UTC)Reply

User:GozerLeGozerien

[edit]

GozerLeGozerien (talk · contributions · Statistics · Recent activity · block log · User rights log · uploads · Global account information) Multiple recent copyvios after the last warning. Quick1984 (talk) 17:05, 19 October 2026 (UTC)Reply

Their last edit was at 12:22, which is after the warnings by Yann, but before the series of warnings by Belbury. This isn't unreasonable for a new editor and we should allow them time to engage and learn what the problem is, before responding harshly to it. Andy Dingley (talk) 17:12, 19 October 2026 (UTC)Reply
Yann's warning was a final one (The next time you upload a file that violates copyright, you will be blocked), given at at 14:34 yesterday. The user uploaded a bunch of movie posters today, and reuploaded File:Life-swayze2.jpg (an old press shot of Patrick Swayze), which Yann had deleted when giving them the final warning. Belbury (talk) 17:27, 19 October 2026 (UTC)Reply
✓ Done Blocked for 6 weeks. The Squirrel Conspiracy (talk) 18:07, 19 October 2026 (UTC)Reply
That is an unreasonable block. 6 weeks for a user who has only been here a couple of days and who has had no chance to reply at any discussion. Yann gave a simultaneous first and 'last' warning (7 minutes apart) based on the false statement "You have done so despite requests from editors not to do so, and despite their instructions." They had not done so. There had been no prior requests from other editors, nor instructions, explanation nor any sort of engagement. All engagement took place over this maximum of 7 minutes.
They did re-upload an image after this. But there still hadn't been any engagement to try and explain the issue, just templating of a brand-new user and we know how badly that works. Andy Dingley (talk) 18:43, 19 October 2026 (UTC)Reply
@Andy Dingley: Yann's final warning was at 14:34, 18 October 2026. Their latest round of copyvios were 24 hours later, at 12:22, 19 October 2026. Their block is for those uploads. We can't be responsible for users not reading warning templates, and the "This media may be deleted." template is about the clearest one we have, in the most languages. The Squirrel Conspiracy (talk) 02:31, 20 October 2026 (UTC)Reply
Yes, Yann's 'final warning' was only seven minutes after their first contact with GozerLeGozerien. That is not a reasonable interval for a brand new and naive user. It also relied on a false statement, that they had already uploaded after warnings. Andy Dingley (talk) 10:14, 20 October 2026 (UTC)Reply
 Comment I would not have blocked this account for 6 weeks, but nevertheless, a short block is in order. I would shorten the block if we get any response from GozerLeGozerien. Yann (talk) 13:11, 20 October 2026 (UTC)Reply
Agreed. It's the combination of no real warning, then a 6 week first block 'justified' by that, that's the problem here. Andy Dingley (talk) 14:46, 20 October 2026 (UTC)Reply
If Yann wants to reduce the block length, I don't object. The Squirrel Conspiracy (talk) 04:47, 21 October 2026 (UTC)Reply

User:Zaptain United

[edit]

Zaptain United is blocked from the English Wikipedia, and has been using commons to ping English Wikimedia editors (eg [1]). After a warning, Zaptain replied Fuck Admins. [..] I want to get banned honestly[2] BillHPike (talk) 18:40, 20 October 2026 (UTC)Reply

✓ Done I can't ban them, but I can (and did) indef-block them on Commons. - Jmabel ! talk 03:18, 21 October 2026 (UTC)Reply

User:げんき 公式 and ~2026-56069-42

[edit]

I began to suspect this is a sock puppets of Wikinger SpinnerLaserzthe2nd (talk) 04:13, 21 October 2026 (UTC)Reply

✓ Done this and half a dozen associated accounts indef-blocked. There may be more that needs rolling back than has yet been done. - Jmabel ! talk 05:40, 21 October 2026 (UTC)Reply

Wikiuser9876543212022

[edit]

  — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 11:38, 23 October 2026 (UTC)Reply

✓ Done. At first I thought, that no block is needed at all (only one deleted upload after block), but thing is worse than appeared in beginning. One month block (second block) plus I'll delete some copyvios. Taivo (talk) 12:24, 23 October 2026 (UTC)Reply

Jonnmann

[edit]

  — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 12:33, 23 October 2026 (UTC)Reply

Looks to me like they have received some very confusing feedback. For example, User talk:Jonnmann#File:Gråsiska - Acanthis flammea.jpg points to a DR that seems completely unrelated to the file in question. If I can't follow it, I can't see how they can be expected to.
For the one current DR for File:Rapport till SLU Artportalen-Skåne-2021.jpg, I can see how anyone not expert in copyright could think of this as "own work". Looks more like a reason to engage than a reason to call for administrative action. They've had a few files deleted, but mostly on self-nominations or things like confusion about the copyright status of banknotes, and the vast bulk of their uploads look mutually consistent and presumably fine.
@Jonnmann: if you don't understand why File:Rapport till SLU Artportalen-Skåne-2021.jpg has a copyright problem, please read COM:THIRD. - Jmabel ! talk 19:55, 23 October 2026 (UTC)Reply

UniViki – uploads of third-party images as "own work"

[edit]

UniViki (talk · contribs) (account created 17 October 2026) has uploaded about 20 files, most tagged "Own work" under CC0 or a self-applied CC BY 4.0. Several are published images by other organizations, released under licenses the uploader cannot change:

Other "own work" uploads (VERITAS-922 B, JESS2-847 b, FU Orionis North B, Proplyd 133-353) have no source, and I found no published record of the first two objects. Two uploads (File:Jupiter Showcases Auroras, Hazes (NIRCam Closeup) 2026.jpg, File:Hubble Ultra Deep Field(cropped).jpg) are correctly sourced. Could an admin review the uploads and advise the user on COM:OWN and COM:L? Elipses-Original (talk) 18:26, 23 October 2026 (UTC)Reply

I note that as of now, none of these images have even been nominated for deletion, which would usually come before a request for administrative action. - Jmabel ! talk 19:39, 23 October 2026 (UTC)Reply
@Jmabel: See Commons:Deletion requests/File:Artist’s impression of b planet of KIC 10735564 forming 2026.jpg.   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 22:34, 23 October 2026 (UTC)Reply
OK, so one of them has been nominated. I went through the first three mentioned here and saw nothing. - Jmabel ! talk 22:46, 23 October 2026 (UTC)Reply