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

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.

Transplanted copy from User talk:Jameslwoodward, about myself

A Wikimedian began the discussion below on User talk:Jameslwoodward. I have the opinion that that page is not the best venue to talk about the alleged issues, hence I'm grafting the message here. Grand-Duc (talk) 19:46, 12 July 2026 (UTC)

Begin of copy.

Grand-Duc (talk · contribs) He has been filing excessively disruptive deletion requests. I kindly ask that you have him cease this behavior at once.

Commons:Deletion requests/File:JA8183 B747-346 JAL Japan Airlines(Reso'cha) NRT 09JUL01 (7026968593).jpg

Commons:Deletion requests/File:Boeing 747-400 - JAL - JA8183 (5723644644).jpg

Commons:Deletion requests/File:JA8183 Reso`cha Boeing 747-346SR Japan Airlines (JAL) (8637493082).jpg

Commons:Deletion requests/File:Boeing 747-346, Japan Airlines - JAL Reso`cha AN0309058.jpg

Commons:Deletion requests/File:JA8183 (8087571163).jpg

Commons:Deletion requests/File:JA8183 Reso`cha Boeing 747-346SR Japan Airlines (JAL) (8639157327).jpg

Commons:Deletion requests/File:Boeing 747-346, Japan Airlines - JAL Reso`cha AN0344534.jpg

Commons:Deletion requests/Files in Category:JA8149 (aircraft)

Commons:Deletion requests/Files in Category:JA8183 (aircraft) --Y.haruo (talk) 22:31, 11 July 2026 (UTC)

Far from having him cease, I encourage him to continue. These are all copyright violations and must be deleted. As I have said many times, the rule on de minimis requires that the copyrighted work be unimportant enough so that an average reader will not notice if it is omitted. That is plainly and clearly not true in these cases.

If you continue to make unfounded accusations such as this, you will be blocked from editing on Commons. .     Jim . . . (Jameslwoodward) (talk to me) 22:33, 11 July 2026 (UTC)

All of these are de minimis. I believe I have valid grounds for that conclusion, and I kindly ask that you refrain from directing personal attacks at me Y.haruo (talk) 22:45, 11 July 2026 (UTC)

So, it is all right for you to make unfounded personal accusations against Grand-Duc, but it is not all right for me to warn you that your behavior will lead to your being banned? .     Jim . . . (Jameslwoodward) (talk to me) 14:40, 12 July 2026 (UTC)

I got the ping, so I hope I'm not bothering Jim by writing here too.

First of all, I'd like to know how you, @Y.haruo, come to the conclusion that my DR are "excessively disruptive". Judging by how often my argumentation convinces an admin to close them by deleting, I don't think that my interpretation of Commons' policies on which I base the DR are too far-fetched and disruptive. It's much more of quality-assurance work to better the repositories, isn't it?

Furthermore, I've read and re-read your Japanese posting of law texts and its English translation. I think that the basic intention of the law is to make it legitimate for people to engage in exchanges about hobbies on social network services (SNS) and fan communities, up to and including Otaku ways, also using fundamentally copyright protected works (like Pokémon sculptures or vehicle liveries). The inclusion of that "socially acceptable" wording points to such an interpretation, it being facilitating common communication.

But this media use is quite different from an image hosting service and media repository like Commons is. On social networks, any image is bound to slip into the oblivion of the unseen depths of old feeds after some time, whereas Commons is hosting images in curated archives. The visibility there and the influence, the encroachment upon third-party intellectual property, is much more pronounced than in some random SNS feed.

Trudging on such a borderline between copyvio and OK is hardly recommended in the light of COM:PRP. Unless an appellate court or the highest court of law of Japan (or any other country, for that matter) is interpreting and concretizing the law, we IMHO can't boldly assume that such imagery is OK to host here, not when the wording is still fuzzy (by including both "socially acceptable endeavours" and " legitimate interests of copyright holders"). Regards, Grand-Duc (talk) 23:54, 11 July 2026 (UTC)

The Wikimedia Foundation does not seek new restrictions. What you are doing effectively narrows the previously accepted scope of De minimis, and that constitutes a new restriction. How many of the administrators who deleted files actually understand this point? Moreover, I am aware that you have distorted the Commons guidance on De minimis and misrepresented Japanese law when filing your deletion requests. This is by no means quality‑assurance work. Y.haruo (talk) 19:18, 12 July 2026 (UTC)

End of copy.

@Y.haruo: Please elaborate on how I "have distorted the Commons guidance on De minimis" in your eyes; and what exactly constitutes a misrepresentation of Japanese law. Especially the first point is hard for me to understand, I don't see anything in the wording on COM:DM that I have distorted. Regards, Grand-Duc (talk) 19:46, 12 July 2026 (UTC)

This would only be disruptive if they were closed as keep and Grand-Duc continued to nominate similar images. Traumnovelle (talk) 07:59, 13 July 2026 (UTC)

You argued that the image does not qualify as de minimis because it is categorized according to Disney motifs, but that is not correct. File:Louvre at night centered.jpg is also categorized under Category:Louvre Pyramid at night, and yet it has never been considered problematic. Whether something is de minimis must be determined by examining the image itself, not by looking at its categories. Your statement — "COM:De minimis not applicable, image categorized according to Disney motifs." — is a distortion of the de minimis guidance. SeeCommons:Deletion requests/Files in Category:JA8904 (aircraft), Commons:Deletion requests/Files in Category:JA873A (aircraft) in R2-D2 livery and Commons:Deletion requests/Files in Category:C-GWSV (aircraft). Y.haruo (talk) 16:09, 13 July 2026 (UTC)

Did you actually read Commons:De minimis#Guidelines? The sentence about categorisation is directly taken from the page you're saying I'm distorting. And, while I stayed quite short with "COM:De minimis not applicable, image categorized according to Disney motifs.", I meant to imply that the whole image impression was not covered by DM. If that was not concise and explanatory enough, then it's on me, but otherwise, the point still stands. The Louvre pyramid example is something maybe worth looking into, but you can't conclude, simply because nobody challenged the legitimacy of imagery within Category:Louvre Pyramid at night yet, the set is assuredly OK. Regards, Grand-Duc (talk) 17:56, 13 July 2026 (UTC)

I certainly have read it. Although it has been in place since 2012, it is only a broad guideline and has not been applied as an operational basis for deletion. Claiming afterward that you “meant something different” does not strike me as a sincere or honest way to engage.

Moreover, in Commons:Village pump/Copyright/Archive/2025/07#Pokemon Jets deletion requests you stated that "a deletion from for instance JA8962 in Pokémon livery (that's the 747-400 example above) can be kept when it's from FRA and has to be deleted when it's made in Heathrow or Narita." This is an unfounded and factually incorrect view with no source whatsoever, expressed solely to strengthen your own position.

Disrupting discussions and making false statements are, of course, grounds for blocking. Y.haruo (talk) 05:21, 15 July 2026 (UTC)

Actually, threatening people you're talking to with blocking because you believe disagreeing with you is making false statements and being disruptive is actually a way people have got blocked.--Prosfilaes (talk) 07:14, 15 July 2026 (UTC)

What a selective reading you've done in that VPC thread, @Y.haruo... You're apparently conveniently glossing over the actual explanation for "a deletion from for instance JA8962 in Pokémon livery (that's the 747-400 example above) can be kept when it's from FRA and has to be deleted when it's made in Heathrow or Narita." (-> it's the combination of Commons' way of doing things: a principle akin to a Home state regulation, combined with COM:FOP Germany#Permanent, the BGH Aida Kussmund case & COM:FOP UK & COM:FOP Japan) and also the analysis that JMabel did ("All of this is complicated by the fact that the risk involved is not just the risk of legal penalties, but also a certain dedication to intellectual honesty. We certainly often refuse to host material where there is a near-zero chance that the rights-holders would ever sue, and the PCP makes it very clear that we intend to keep to that policy, not just do anything we think we can get away with.")

Are we perhaps operating around a language barrier? I dont see where I expressed to mean something different, with "COM:De minimis not applicable, image categorized according to Disney motifs" I only shortened the reasoning about the inapplicability of DM, perhaps too much. But the categorisation argument is still a centrepiece of the DR rationale. Wasn't that visible?

Please let me ask you, Y.haruo: do you know some commentaries of or maybe court rulings about the Japanese DM law you've repeatedly quoted that speak about commercial usages of media produced under that statute? As written above, I think that the "socially accepted as legitimate and reasonable" does not cover commercial exploitations of imagery (besides those immanently happening on social networks). If I'm not mistaken, Japanese corporations and governmental bodies are actually quite strong against IP rights violations (examples: Sony and Nintendo using their might against game streamers, publishing houses having manga reading sites hosted abroad in e.g. Vietnam taken down, the ministry of agriculture, forestry and fishery fighting against "pirated" seeds and seedlings of Japanese-born crop varieties that are used in China and South Korea). This kind of politics present itself as reason to have a restrictive reading of "socially accepted as legitimate and reasonable".

That the Commons:De minimis#Guidelines allegedly hasn't been used as DR rationale in the 2010's is no reason to not do so currently. That idea is apparently quite convincing, most DR where I referred this guidelines actually ended in deletions (barring those still open). And last but not least: if you're making accusations like "[d]isrupting discussions and making false statements", you must be prepared to produce solid evidence for it, otherwise, it could easily appear like slander, I think. Regards, Grand-Duc (talk) 09:57, 17 July 2026 (UTC)

You are diverting the discussion, but the fact remains that you have repeatedly made false statements about Japanese law, and the same happened in the deletion request. In that DR, you invoked the pre‑2020 version of the law from 2015 and claimed that “These character images cannot fulfil this ‘incidental’ clause, as they are objectively prejudicing the opportunity of their IP owners’ illustrations to potential customers wanting to illustrate the characters.”

In my response to that DR, I explained—citing the Agency for Cultural Affairs—that Commons has no such unreasonable requirement, and that the 2020 amendment clarified and expanded the scope of the provision.

Despite being aware of this, you continue to rely on the outdated statute and repeat unreasonable arguments based on it. This conduct clearly fails to represent current Japanese law accurately and serves to push the deletion discussion in your favor. I wonder how many people have been misled by your false statements. see Commons:Deletion requests/File:ANA B747-481D JA8964 Pocket Monsters (5314675945).jpg, Commons:Deletion requests/File:JA8964 B747-481D ANA All Nippon(Pokemon) HND 10JUL01 (7046345265).jpg, Commons:Deletion requests/Files in Category:JA8957 (aircraft), Commons:Deletion requests/Files in Category:JA8965 (aircraft) and Commons:Deletion requests/Files in Category:Pokémon trains, Y.haruo (talk) 11:17, 18 July 2026 (UTC)

Let's use your posting in Commons:Deletion_requests/File:ANA_B747-481D_JA8964_Pocket_Monsters_(5314675945).jpg as base, OK?

You've posted what is apparently an excerpt of Japanese law (I'm a bit irritated by the "Copilot" part in the URL at the end, though. Copilot is Microsoft's AI system, can you guarantee that no hallucinations are included?).

In that translation, I do not see anything that is fundamentally different from what I said based upon older law revisions: this law says that a copyrighted element can be included when it constitutes a minor component of the material [...] —when considered in light of the proportion of the copyrighted work within said material, the precision of the reproduction of the copyrighted work within said material, and other factors; and [...]to the extent justified in light of whether there is a purpose of obtaining profit from the use of said incidentally included copyrighted work, the degree of difficulty in separating said incidentally included object or sound from said primary object or sound of reproduction or transmission, the role played by said incidentally included copyrighted work within said created or transmitted material, and other factors. Provided, however, that this shall not apply if such use would unreasonably prejudice the interests of the copyright owner in light of the type and purpose of said incidentally included copyrighted work and the manner of said use.

Please note that the part about unreasonable prejudice is still present! Furthermore, Pokémon liveries on planes and trains are certainly not minor to the usual spotter images, except when one has e.g. captured an airport overview where a Pokémon Jet is indeed a background feature. Regards, Grand-Duc (talk) 22:35, 20 July 2026 (UTC)

I'd refrain from using translation tools like Google when there is one site with the translation itself or this to compare, unless already acquired near-native Nihongo. ～ POKéTalker（═◉═） 07:34, 21 July 2026 (UTC)

From a rigorous reading of past deletion discussions, there's apparent hypocrisy amongst the deleting/keeping administration being in play here: the JA8578 taking off was kept (Jcb, Ellin Beltz, and Abzeronow in that order), retired and blocked users (Russavia in particular) having the deciding votes (Jdforrester), and this keeping of a JA8578 (Yann) was dishonoured by your (mis)interpretation (Ellywa), to name a few. Might add more discussions so everyone can notice historical inconsistency from the recent development; sensing a Western bias from a similar experience in a related Wikimedia project.

Would also note that Wikipedia articles across languages have been deprived of PokéJet images because of Großherzog's (and probably a few more's) recent requests here on Commons with these un-ceremonial deletions. Current version of the English (archived 2023). This shouldn't be ignored; so if there's no other alternative, the non-free use rationale template must be utilized on the already-stricken (through temporary undeletion) and what is left untouched. Good luck in what to put on all eight parameters; Großherzogs precedent might be disagreed upon by past administrators. I have been trying to put this JA8357 but unsure of the next step(s) to be given towards the photographer: upload to Commons or individual WP articles by (a heck number of) language(s). Side note, Bulbapedia has been extracting some of them from here before this row! a few were under CC0 (Public domain), how to explain being trumped by your allegations? ～ POKéTalker（═◉═） 07:34, 21 July 2026 (UTC)

"sensing a Western bias"

Hold on. What the fuck are you saying? Whyiseverythingalreadyused (t · c · he/him) 08:43, 21 July 2026 (UTC)

Language please, Whyiseverythingalreadyused. Because of some "precendent" applied just last year, much of the files in Commons have been deleted unceremonally; and this has affected many Wikipedia articles across different languages. Seems that the OP is trying to use the Copyright Law of Japan against at least one native-speaker trying to preserve. Thus, can make a comparison with an experience in Wiktionary when I tried to deal with a controversial administrator there in regards to what considers either a "native reading" or "irregular reading" to a Chinese character. We're being overwhelmed here! ～ POKéTalker（═◉═） 09:36, 21 July 2026 (UTC)

@Poketalker: Thanks for the official law translation page, that's a nice resource worth adding to COM:Japan IMHO. It doesn't read much different from the translation above, though.

But please stop the nonsense of a Western bias (for what it's worth, politically, Japan is Western-aligned anyway as far as I'm aware) or that I aim to persevere against a native speaker. This is easily disproven as I already tried to raise more awareness from natives, see ja:Wikipedia:Help for Non-Japanese Speakers#Information in copyright matters requested, "De minimis", to get the best possible fact-founded outcome. Any particular desire for Wikipedia illustrations is totally irrelevant in regard to copyright matters, though. There should be admins who're officiating both on Commons and EN-WP, so you could get in touch with them to (try to) have a selection transferred to EN under en:WP:NFCI / en:WP:NFCC, although I admit that it may be difficult to comply with en:WP:NFCC4 as a lot of Pokéjet images were sourced from Flickr. Simply bear this in mind: Commons:Derivative works#But how can we illustrate topics like Star Wars or Pokémon without pictures? with its first sentence, Admittedly, it may be difficult or even impossible to illustrate such articles. Regards, Grand-Duc (talk) 14:15, 21 July 2026 (UTC)

I am not aware of any legal precedent in which the depiction of an aircraft’s livery in a full‑view photograph has been found to violate copyright law. I also do not see any indication that Japanese copyright law diverges from international standards in this regard. Y.haruo (talk) 11:36, 23 July 2026 (UTC)

Even though the user’s own issue is currently being discussed here, he has submitted several new deletion requests. As usual, his claims are inconsistent with the current international standards for evaluating aircraft photography. However, this situation has revealed something new. I will explain this step by step. see Commons:Deletion requests/File:B-18007@PEK (20200403123859).jpg, Commons:Deletion requests/File:B-18916.jpg, Commons:Deletion requests/Files in Category:B-18007 (aircraft), Commons:Deletion requests/File:B-18007@PEK (20200403123859).jpg, Commons:Deletion requests/File:China Airlines MD-11 (N489GX) departing Taiwan Taoyuan International Airport.jpg, Commons:Deletion requests/Files in Category:B-18916 (aircraft) and Commons:Deletion requests/Files in Category:B-18916 (aircraft),

Commons follows the principle of being a Free Content Repository, and the introduction of Commons:De minimis in 2008 shows that it has long adopted the policy that content is acceptable as long as it is freely reusable, even when it falls under de minimis. Moreover, aircraft photographs showing the full airframe have consistently been considered de minimis worldwide, even when painted designs appear in the frame. Naturally, no court cases can be found in which such photographs were judged to constitute copyright infringement.

However, he has repeatedly filed deletion requests that go far beyond actual copyright law and established practice, and he has continued to distort the de minimis Guidelines while making false claims. This is an attempt by someone dissatisfied with the current application of policy to force a change in that policy, and the rapid succession of deletion requests is clearly aimed at undermining Commons’ fundamental principles.

As with the URAA discussions, this is a matter that must be decided through proper community debate, and such deletion requests cannot be accepted. Please do not allow continued attacks on the official policy. Regarding this matter, Commons:Deletion requests states that ‘Deletion requests are not the place to attempt to change Commons policy, nor may requests be made simply to make a point. Any such requests may be speedily closed. Please use the Village Pump or the policy talk page if you wish to propose a change in policy.’--Y.haruo (talk) 18:11, 25 July 2026 (UTC)

The sentence Commons follows the principle of being a Free Content Repository, and the introduction of Commons:De minimis in 2008 shows that it has long adopted the policy that content is acceptable as long as it is freely reusable, even when it falls under de minimis. is quite the red herring. Nothing in my actions hint at me not fully endorsing the project goals and respecting our guidelines and policies. Naturally, this also encompasses COM:De Minimis.

However, he has repeatedly filed deletion requests that go far beyond actual copyright law and established practice - well, the contents of Category:Pokémon related deletion requests/deleted (especially the pages having titles with airplane immatriculations, like JA***) show that there's not really an established practice in keeping such livery images (compare that with Category:Pokémon related deletion requests/kept).

To further foster my respect and endorsement of COM:DM, look at Commons:Deletion requests/Files in Category:JA8956 (aircraft): Nota bene: I did not nominate the whole content of the category, as I think that images like File:AllNipponAirways B747-400 fukuoka 20040926111804.jpg are obviously totally fine and something like File:ANA B747-400D(JA8956) (4262892086).jpg or File:All Nippon Airways Boeing 747-400D Breidenstein-1.jpg is not having enough precision (angled views, not sideways) in showing copyrighted material, so a defence of De minimis is more likely to be successful. In my opinion, File:ANA B747-400D(JA8956) (5699289759).jpg (not included) sets a good borderline between "keepable" and "to be deleted".

This is an attempt by someone dissatisfied with the current application of policy to force a change in that policy, and the rapid succession of deletion requests is clearly aimed at undermining Commons’ fundamental principles. has the look and feel of a bad faith assumption. In fact, I assert that it is the complete opposite, I'm doing the things I do just because I deeply respect Commons’ fundamental principles, including the COM:Precautionary principle. As few if any at all other people have challenged such imagery in deletion requests, the sheer amount of DR I opened is the obvious outcome of having a huge stack of allegedly problematic images all over the place. It's simply the result of the relationship between available manpower and stock of possible copyright violations.

Your sentence Moreover, aircraft photographs showing the full airframe have consistently been considered de minimis worldwide, even when painted designs appear in the frame. Naturally, no court cases can be found in which such photographs were judged to constitute copyright infringement is easily negated (when using scientific standards, with a counterexample being sufficient to disprove a theorem). I assert that there's a technical similarity between a Pokémon livery on a plane and the Aida cruise ship livery with the Kissing lips (the amount of hull / airframe covered by artwork is by percentage similar or higher for the jets). As it stands, the cruise ship livery was subject in a German copyright court case which went to the highest court of law, the Bundesgerichtshof. And far from denying it protection or referring to the De minimis excuse, the court ruled that the work is protected, but could be depicted under the FOP statute; references: COM:FOP Germany#Permanent. With this, everything in your assumption is disproven, as there is a copyright court case known (and documented on Commons) about vehicle liveries in an industrialised country.

The policies / guidelines about COM:DM, COM:FOP, COM:PRP, COM:CSM and COM:CRT are already quite good as they are, there's no need for a change, only the specifics in CSM and CRT could and should be updated whenever new information gets known. In fact, the person who's unhappy by the situation appears to be you, Y.haruo, so it would be upon you to advocate for a more lenient view/interpretation of COM:DM et al., not upon me to work on any change in policies or guidelines. The issue certainly does not reside within myself. Regards, Grand-Duc (talk) 17:49, 26 July 2026 (UTC)

 Comment There are areas (and this is one of them) where Commons has to weigh among conflicting goals, and whereas] we may at any given time have a more or less clear policy, we will always have outliers on both sides, probably even among the admins. On the one hand, we want to carve out strong, broad arguments for legitimate free use. On the other hand, we do not want to overstep and put ourselves or our reusers at risk of violating legitimate copyrights. There are downsides to being either too bold or too timid, and we are never going to all have exactly the same level of boldness.

Following up on that: I don't particularly see and administrative issue here, and would be inclined just to let the DRs play out. - Jmabel ! talk 19:06, 26 July 2026 (UTC)

Thanks for the outputs, here is my further  Comment as the request discussions are being stalled or in moratorium: this seems no longer a clash of Commons and differing countries' lawfare or that of West and (being-ruled-unfavorably) East, but tolerating such files for maybe future use. Those currently under the deletion request template will affect God knows how many Wikipedia articles and continuing on the path won't end well for (today's and future) photographers/uploaders here. Some of them have been slapped with the public domain template such as the B-18916 file. If Commons has no place for those, perhaps the Bulbagarden Archives is a safer bet than separate X-language Wikipedias for matching the latter's counterpart plus the non-free template (more time-consuming and potentially counterproductive than here); I'll have to contact my fellow POKéTalkers there regarding the recent and controversial deletions; who knows when the counterpart article will match or exceed in quality that of Wikipedias', tables and all. Is there even at least one for the related DisneyPlanes? The aviation community on WP has its own tolerance issue; many airline, fleet, and destination article being prone to misinformation due to lack of sources is just the tip of the iceberg. Already planned my future departure from the Wikimedia projects one-by-one because of what just happened a few months ago there...

On the derivative works page, LX revised that section back in 2007. Before that, the word "impossible" wasn't yet mentioned. So there must be more engagement and awareness to new uploaders: OK here or to other Wikimedia project? We've seen enough ignorance of the precautionary principle on their end, methinks. Much under the "deleted" category before Großherzog's starting 2025ish were not of PokéJets or otherwise lack of extra defense. It's time that Wikipedians interested join the remaining discussions while the files aren't yet acted upon.

And please, let more administrators past and present voice their opinion Y.haruo's interpretations before deciding on the critical next steps. The Japanese embassy notice still has yet to have a meaningful response as of this reply. How would we know a nominator doing similar is no different from someone like, a copyright troll? Domo, the first ～ POKéTalker（═◉═） 05:22, 2 August 2026 (UTC)

@Poketalker: I'm a native English speaker, and I cannot make sense of even half of what you just wrote. Is there some language in which you can express yourself more clearly? If there is, could try rewriting this in that language? - Jmabel ! talk 16:55, 2 August 2026 (UTC)

"It's time that Wikipedians interested join the remaining discussions while the files aren't yet acted upon."

@Poketalker: beware of the curse of canvassing. It has taken down a great many before you. By the way, that hall of infamy includes the pain-in-the-ass co-founder of Wikipedia, who was permanently banned after calling for his Twitter base to hijack the consensus-making process in favour of a failing WikiProject that he had proposed. Whyiseverythingalreadyused (t · c · he/him) 17:04, 2 August 2026 (UTC)

@Poketalker: As you've linked a Bulbapedia talk thread in Commons:Deletion requests/File:OSAKA ITAMI 26 OCTOBER 2002 ALL NIPPON BOEING 747-400 JA8964 (50633729578).jpg, I have kind of a technical advice. You will often see a chain of ciphers in parenthesis in the filenames, in the curent example, it's (50633729578). This is a telltale sign that the image in question has been sourced from Flickr, it's a Flickr ID that is Google-able. You'll find images that have been deleted here but may still be available on Flickr with that ID. So, if you're endeavouring in going the fair-use route, either on EN-WP or Bulbapedia, you can find illustrations still hosted on Flickr that were previously used on en:Pokémon Jet (refer to the CommonsDelinker entries in the page history) or cited in other DR.

Back to the main thing, about On the derivative works page, LX revised that section back in 2007. Before that, the word "impossible" wasn't yet mentioned. Yes, "impossible" wasn't used, but the page before that inclusion read "Admittedly, it is difficult. You'll probably have to refrain from illustrating such Wikipedia articles. However, there is plenty of photo opportunities for many topics that do not violate third party copyrights." Advising to probably have to refrain to do something because of third-party copyrights is substantially the same as saying that it's impossible. Second thing: if you happen to know some other Wikimedia universe venues frequented by people interested in copyright matters and ideally knowledgeable in Japanese, name them here, please. I likely won't object to extending an invitation for participation similar to ja:Wikipedia:Help for Non-Japanese Speakers#Information in copyright matters requested, "De minimis", I see some value in gathering more opinions. And the remainder of your rant doesn't really feel fitting to a copyright-based dispute, I have to concur there with Jmabel. Regards, Grand-Duc (talk) 15:14, 5 August 2026 (UTC)

"Probably have to refrain" is just a suggestion, otherwise it's just promoting a sort of self-censorship. Bulbapedia is ready to embrace these files regardless of the outcome(s), but I stress on retaining whatever Creative Commons licenses applied whether from Flickr or taken by uploaders themselves. Let's take this photo of JA8357 as a test case, shall we? It's been three years, but can continue correspondence with standard procedure in uploading to either here, a Wikipedia language(s) of choice, or Bulbagarden Archives. ～ POKéTalker（═◉═） 10:10, 8 August 2026 (UTC)

Grand-Duc (talk · contribs) continues to repeat the same argument based on the Commons:Project scope/Precautionary principle. However, as I stated at Commons:Deletion requests/File:JA8183 B747-346 JAL Japan Airlines(Reso'cha) NRT 09JUL01 (7026968593).jpg, the Agency for Cultural Affairs’ explanation regarding Article 30‑2 of the Japanese Copyright Act clearly provides the following example of a use that does require permission from the copyright holder: “Selling stickers or similar goods made from photographs in which a manga character appears incidentally, in a manner that exploits the character’s customer‑attraction power, even though the character only appears as an incidental element to the main subject of the photograph.” In other words, merely photographing an aircraft does not constitute copyright infringement.

Furthermore, the Agency clearly stated that “whether the use conflicts with the copyright holder’s existing market, or interferes with the potential market for the work in the future, must ultimately be determined on a case‑by‑case basis by the courts.” As of today, there is not a single court decision in Japan holding that photographing an aircraft, with incidental inclusion of artwork or livery painted on the aircraft, constitutes copyright infringement.

This is in no way supportive of his claims; rather, it demonstrates that he continues to provide false explanations about Japanese copyright law. And despite this, he has offered neither correction nor apology. I therefore submit once again that his conduct constitutes repeated disruption of the discussion. see Commons:Deletion requests/File:CHINA AIRLINES A321-271NX B-18101 HND RJTT 08-OCT-2022 (52412820078).jpg, Commons:Deletion requests/File:20220331 rokon jet of AIRDO JA607A left side at Tokyo international airport.png, Commons:Deletion requests/Files in Category:JA8149 (aircraft) and Commons:Deletion requests/File:OSAKA ITAMI 26 OCTOBER 2002 ALL NIPPON BOEING 747-400 JA8964 (50633729578).jpg. --Y.haruo (talk) 17:03, 14 August 2026 (UTC)

Mary Joanna

Mary Joanna (talk · contributions · Move log · block log · uploads · Abuse filter log) block user

Per the advice of EugeneZelenko, I'm bringing this here. Mary Joanna reverted my edit on the user page of Moataz1997, the edit being a fix of one of my bot's prior edits which was reverted because it broke a table. Their edit summary was "don't edit other user pages, stop it now", when I asked them about the revert on their talk page, they reverted my message with the edit summary "you should accept reverts like Special:Diff/1252111844 and don't edit user pages". I believe this is disruptive, given my bot previously edited their user page, and after I stated my opinion on the replacements they threatened to report me/my bot to COM:AN/V if it edits their user page, and their failure to provide a substantive reason to revert the edit reinstating the bot edit without issues. Tenshi Hinanawi (talk) 21:00, 27 July 2026 (UTC)

self report. see User_talk:Tenshi_Hinanawi#Your_bot_editing_my_talk_page_archive., his edits are unwanted. and this is clearly an editwar from Tenshi Hinanawi against the user page owner. --ɱ 21:12, 27 July 2026 (UTC)

As I had explained earlier in my message to you, "It seems apparent that the revert was because of the malfunction, not because they didn't want it." Tenshi Hinanawi (talk) 21:16, 27 July 2026 (UTC)

@Mary Joanna: That is an archive of the user talk page allocated for communicating with you; it is not yours. Tenshi Hinanawi's bot was authorized by a Bureaucrat and Admin here to make such edits at Commons:Bots/Requests/TenshiBot.   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 21:25, 27 July 2026 (UTC)

Wait, that was a user page, but it wasn't yours. Who elected you as the defender of the user pages?   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 21:32, 27 July 2026 (UTC)

The admin wrote: "If there are no objections". The objections you can find here. If a bot causes this trouble, the botflag should be reconsidered. And do you really protect editwar like this against the will? --22:01, 27 July 2026 (UTC)

Aside: personally I prefer <center> even though it is now deprecated by the current HTML standard, but I see the value in having the site conform to the standard. - Jmabel ! talk 21:34, 27 July 2026 (UTC)

the site is not conformed to the standard. for the User:Tenshi_Hinanawi-page it shows zero lint errors. but this is not true: https://validator.w3.org/nu/?doc=https%3A%2F%2Fcommons.wikimedia.org%2Fwiki%2FUser%3ATenshi_Hinanawi - The LintErrors-tool is only good for bossing others around in their user area: User:Tenshi Hinanawi is doing editwar about his bot edits. I'm going sleeping right now, it's late in germany. --ɱ 22:05, 27 July 2026 (UTC) PS: there is princip like en:Error-tolerant design. browsers don't have a problem with <center>. there is no need to remove this from user pages.

See this history. this diff is another edit war by User:Tenshi Hinanawi --ɱ 22:16, 27 July 2026 (UTC)

My revert was because there was no valid reason given to revert, and neither bots' edits were errant. The second edit was to prevent the bot from editing the page, but the user reverted it, which means the bot is not prevented from editing. It's impossible to follow both "do not edit this page" and "do not let your bot edit this page" when the method my bot excludes pages is via the {{Bots}} template that's on all major wikis. Tenshi Hinanawi (talk) 23:12, 27 July 2026 (UTC)

Unarchiving, this still needs to be resolved. Tenshi Hinanawi (talk) 10:19, 4 August 2026 (UTC)

You can resolve this by declaring doing no edit wars anymore. Your content contribution to this project is zero. Let other in peace, who're using this project as described here. --ɱ 👽 12:35, 4 August 2026 (UTC)

It's clearly not edit warring, and no one else has come forward to say that either. Even on dewiki (your home wiki), you would be in the wrong here on Moataz's user page, since reverts without explanation don't count. Yes, I edited Rockfang's archive afterwards against their wishes, but it was an inevitable result. On dewiki as well, you have a history of reverting lint fixes as well (1) and reporting people for it (2). Stop your baseless accusations. Tenshi Hinanawi (talk) 14:21, 4 August 2026 (UTC)

I can only see one thing: you want to dictate to others what they should do in their User pages. --ɱ 👽 14:35, 4 August 2026 (UTC) PS: and on dewiki, lint error fixes to the user pages by third parties are not welcome: „Only the user in question may edit their own user pages.”. The link from 2024/01/17 is too old, see de:Special:Diff/241364835. The Admin later revoked his decision.

Where have I dictated anything exactly? Tenshi Hinanawi (talk) 19:56, 4 August 2026 (UTC)

1, 2. --ɱ 👽 20:01, 4 August 2026 (UTC)

1, first sentence of 2. Tenshi Hinanawi (talk) 20:13, 4 August 2026 (UTC)

Instead of editing my user talk page archive after I specifically asked you not to you could have just said something like "okay I won't edit it. If you don't want my bot to edit it I suggest using nobots." Rockfang (talk) 22:08, 12 August 2026 (UTC)

@Rockfang: sure, but he'd have had to guess how much you understood about "nobots" (after all, you hadn't already done this yourself) and then gauge an appropriate degree of explanation. Instead, he made the one-time trivial edit, to which I honestly cannot see any rational objection, but which you reverted, making it inevitable that their bot would edit your page again. No, you are not liable to get an admin to censure them for that. I stand by my statement below that I don't see any administrative action needed here. - Jmabel ! talk 01:46, 13 August 2026 (UTC)

I never said anybody should be censured. I actually agree with you that no administrative action is needed. Rockfang (talk) 06:54, 13 August 2026 (UTC)

According to this page, as recently as 22:16, 27 July 2026 (UTC), the user was using "[[File:7-3-3 Hyperbolic Honeycomb Rotating.gif|20px]]" (File:7-3-3 Hyperbolic Honeycomb Rotating.gif) in her signature, in violation of policy COM:SIGN#Images in signature.   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 13:25, 4 August 2026 (UTC)

You see my last edit from 12:35 without using of images? there is no violation anymore. my signature is since the notification conform with this policy: „One possible alternative is to use Unicode characters instead.“ removed --ɱ 👽 --ɱ 👽 13:28, 4 August 2026 (UTC)

@Mary Joanna: Kindly retract that, nothing I wrote above is false.   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 14:35, 4 August 2026 (UTC)

You’re trying to pin a behaviour on me that I’ve stopped doing. That’s unfair. ɱ 👽 14:36, 4 August 2026 (UTC)

It might even imaginably be unfair, but it is certainly not "false flag". I am sure Jeff is neither pretending to be someone else, nor is he acting on someone else's behalf, nor is someone else impersonating him. - Jmabel ! talk 21:32, 4 August 2026 (UTC)

Perhaps I didn’t express myself clearly; my English isn’t the best. But I have put a stop to the behaviour that was criticised, so there’s no need to make a fuss about it here. --ɱ 👽 11:06, 5 August 2026 (UTC)

@Mary Joanna: Alright, but still a warning is in order: actual "false flag" behavior usually merits a block or ban. It is not an accusation to make lightly. I will presume from what you said that you used the term without understanding it, but if you use it again, expect it to boomerang. - Jmabel ! talk 23:57, 5 August 2026 (UTC)

In fact I chose my words poorly there, and I'd like to apologize to Jeff for that. I've edited my comment accordingly. --ɱ 👽 09:58, 6 August 2026 (UTC)

Seeing as no other admin has commented on this, Jmabel, would you be interested in handling this? Tenshi Hinanawi (talk) 18:19, 10 August 2026 (UTC)

 Not done Given that the "false flag" remark was retracted, I don't see any action needed here.

@Mary Joanna: you really do need to decide: either let the (authorized) bot make its routine edits on your user talk page, or let your user talk page be marked so the bot will not touch it. I don't care which you decide, but it is clearly going to be one or the other. Or, I guess, you can rage against the firstborn of Egypt, but it isn't going to accomplish much. - Jmabel ! talk 18:29, 10 August 2026 (UTC)

I did already set template:nobots. But do you really dont say anothing about, that Tenshi is doing edit war about his reverted bot edits? Is doing edit war ok? --ɱ 👽 19:39, 10 August 2026 (UTC)

 Not done I don't see any administrative action needed here. - Jmabel ! talk 21:01, 10 August 2026 (UTC)

Whybleedinside

• Whybleedinside (talk · contributions · Statistics · Recent activity · block log · User rights log · uploads · Global account information) (assign permissions)

Reuploads deleted copyvio after having been given final warning the other day. See evidence from User:SteinsplitterBot/Previously deleted files:

Timestamp	File	Uploader	Deleted file	Uploader
Aug 04 2026 01:22 PM	File:Теплообменное оборудование АО «Бугульминское ПТС».jpg	Whybleedinside (talk | contr | dcontr | accounts | blocks | 32 edits)	File:Foto-69-iz-75-1.jpg (Und | Log)	Whybleedinside (talk | contr | dcontr | accounts | blocks)

Jonteemil (talk) 10:13, 5 August 2026 (UTC)

 Done. I warned the user against recreation of deleted files and will delete the mentioned file. Taivo (talk) 14:29, 7 August 2026 (UTC)

@Taivo That annoys me quite a lot. {{End of copyvios}} includes This is your last warning. The next time you upload a file that violates copyright, you will be blocked. The user not only uploads a new copyvio, which would be stupid enough, but recreates the exact same copyvio that's already has been deleted once. That's a so blatant breach of policy and you just give them another warning, when the template already says LAST WARNING. Jonteemil (talk) 20:47, 7 August 2026 (UTC)

Gmyazbeckk

Gmyazbeckk (talk · contributions · Statistics · Recent activity · block log · User rights log · uploads · Global account information) (assign permissions)

Appears to be less here to create useful images than he is in uploading photos of his patented dome design or whatever that is. His name is Ghaouss Yazbeck (he literally said so at Category:Photographs by Ghaouss Yazbeck). The promise of improvement that he made at Commons:Administrators' noticeboard/Vandalism/Archive 29#Gmyazbeckk has no practical meaning, as he has continued to upload the tent stuff. I presume that's what got him indeffed on arwiki. Whyiseverythingalreadyused (t · c · he/him) 05:27, 6 August 2026 (UTC)

@Whyiseverythingalreadyused,  Done Indeffed as promo only account. I would have gone for a shorter block in the previous report but the user promised to improve, so I wanted to extend the ROPE. This time I am convinced for indef bcoz, one, arwiki block (Indef without TPA) and not acting per the promise made last time. I have deleted some content, plz let me know if something else needs to be taken care of. Thanks for the report. Shaan Sengupta^Talk 08:34, 6 August 2026 (UTC)

 Done. I declined unblock request. Still self-promotion-only account, no promise to improve. Taivo (talk) 14:22, 7 August 2026 (UTC)

Orkideh he

User: Orkideh he (talk · contributions · Move log · block log · uploads · Abuse filter log) block user
Reason for reporting: Please monitor if this user is continuing in posting content that is not pertinent to Commons. They repeatedly wrote walls of text on the COM:VPC in Arabic script that, according to a quick glance using Google Translate, may be fitting for a private blog or the like, but that content is certainly not suitable for Commons and likely not for any other Wikimedia project. I already posted a scope info and a vandalism warning on their talk page; this report is meant to raise some more awareness about their likely spamming endeavours. Regards, Grand-Duc (talk) 01:13, 7 August 2026 (UTC)

 Done. I blocked Orkideh for a month. Taivo (talk) 14:24, 7 August 2026 (UTC)

Alisahib2001

• Alisahib2001 (talk · contributions · Statistics · Recent activity · block log · User rights log · uploads · Global account information) (assign permissions)

Their third block, this time of six months, has just expired and they immediately starts recreating lots of their previously deleted copyvios. I think indef seems appropriate this time. Jonteemil (talk) 20:40, 7 August 2026 (UTC)

Indef. It's not even as if these are interesting content, they're just commercial logos. Andy Dingley (talk) 21:06, 7 August 2026 (UTC)

I suspect that a couple of specific examples would get some admin to focus on this much more readily than just saying "lots of their previously deleted copyvios". As it says at the top of this page, "include links as evidence". You presumably already found something, or you wouldn't be reporting here. - Jmabel ! talk 05:25, 8 August 2026 (UTC)

All the deletion notices with files in blue links on their user talk page have been deleted and now recreated. I believe admins are competent enough to realize that without needing links. Jonteemil (talk) 08:19, 8 August 2026 (UTC)

@Jmabel: Every bluelink in their deleted uploads. They also made an incomplete DR in Special:Diff/1148720640.   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 11:44, 8 August 2026 (UTC)

Thanks. Yes, I probably could have worked it out. My point is: don't make other people take the time to work out what you already worked out. Nearly every active admin is someone with too much on their plate. Most of us will work on what is either obviously important or obviously easy. You'll notice it's not just me that didn't pick this up: in the 20+ hours since the original complaint, no one did. I'll do it now. - Jmabel ! talk 18:09, 8 August 2026 (UTC)

 Done. Indef-blocked. - Jmabel ! talk 18:28, 8 August 2026 (UTC)

Perfect. Can you delete all reuploaded files as well? They certainly don't deserve a 7 days waiting period for permission. Jonteemil (talk) 20:32, 8 August 2026 (UTC)

It should be all of these files. Jonteemil (talk) 20:39, 8 August 2026 (UTC)

I don't think there is any tool to use that particular output to initiate a delete (maybe some mix of copy-paste, editing, and AWB?). I am busy IRL today, and am not taking on what looks like a pretty big manual task. If some other admin can delete those sooner rather than later, great. - Jmabel ! talk 22:32, 8 August 2026 (UTC)

Zatony118

• Zatony118 (talk · contributions · Statistics · Recent activity · block log · User rights log · uploads · Global account information) (assign permissions)

Yet another sock of Zatony2016. Evidence from User:SteinsplitterBot/Previously deleted files:

Timestamp	File	Uploader	Deleted file	Uploader
Aug 06 2026 06:00 AM	File:Sen. Tommy Tuberville Official Portrait, 118th Congress.jpg	Zatony118 (talk | contr | dcontr | accounts | blocks | 22 edits)	File:Sen. Tommy Tuberville (R-AL), Official Portrait, 118th Congress.jpg (Und | Log)	Zatony101 (talk | contr | dcontr | accounts | blocks)(different)

Jonteemil (talk) 23:56, 7 August 2026 (UTC)

 Done indef-blocked - Jmabel ! talk 05:30, 8 August 2026 (UTC)

Yayotpower

Continues to upload the same file already deleted twice as copyvio, despite given final warning by @Yann in May. Evidence from User:SteinsplitterBot/Previously deleted files:

Timestamp	File	Uploader	Deleted file	Uploader
Aug 08 2026 04:25 AM	File:Raisel Bustamante official portrait.jpg	Yayotpower (talk | contr | dcontr | accounts | blocks | 22 edits)	File:Official portrait of Raisel Bustamante in 2022.jpg (Und | Log)	Yayotpower (talk | contr | dcontr | accounts | blocks)
Aug 08 2026 04:25 AM	File:Raisel Bustamante official portrait.jpg	Yayotpower (talk | contr | dcontr | accounts | blocks | 22 edits)	File:Official Portrait of Raisel Bustamante 2022.jpg (Und | Log)	Yayotpower (talk | contr | dcontr | accounts | blocks)

Jonteemil (talk) 20:49, 8 August 2026 (UTC)

 Done Blocked for 2 weeks, file deleted. Yann (talk) 20:53, 8 August 2026 (UTC)

Aprenderenwiki

Aprenderenwiki (talk • contribs • block log • filter log) has repeatedly uploaded copyright violations despite being warned. --Ovruni (talk) 09:21, 10 August 2026 (UTC)

 Done Blocked for a week. Copyvios deleted. Yann (talk) 10:48, 10 August 2026 (UTC)

Mindmatrix

• User: Mindmatrix (talk · contributions · Move log · block log · uploads · Abuse filter log) block user
• Reasons for reporting: Uploading copyvios like File:130th Sandringham Flower Show 27-07-2011 (6083466684).jpg after final warning..

~2026-43964-16 (talk) 17:47, 10 August 2026 (UTC)

You're seeking action against a user for speedy deleting one of their own uploads after a G7 user request? Andy Dingley (talk) 18:06, 10 August 2026 (UTC)

One of the reasons for deletion was COM:TOYS. ~2026-43964-16 (talk) 14:45, 11 August 2026 (UTC)

 Not done, I may instead explore BOOMERANG. Shaan Sengupta^Talk 07:23, 11 August 2026 (UTC)

Hkeely using AI to fake skies and lighting

Hkeely (talk · contribs · deleted contribs · logs · edit filter log · block user · block log) appears to be using AI (motly Luminar Neo per the metadata) to completely fake the sky and lighting in a number of photos. In some cases, he uploads multiple contradictory versions:

• The Vermont State House goes from sunny to cloudy with a rainbow in 8 seconds
• Nottely Dam goes from sunny to sunset to a different sunset
• Huntingdon station is sunny yet somehow shadowless just 4 seconds before sunset

Many of the fakes are clever enough to look plausible, though some have obvious issues like shadows in the wrong direction. None of them are properly labeled as being manipulated; even if they were, they would likely still be out of scope. While Hkeely is clearly a skilled photographer, the fakes are a huge issue. Unless he can provide the un-manipulated originals, I don't see how we can keep these.

The issue appears to date at least back to 2023, where we see the exact same sky+planes background from one angle and a different angle, clear generation artifacts, and a brightly daylit noon sunset. Of Hkeely's 2,258 uploads – almost all of which were uploaded after the first fakes I've found – 961 are in use in mainspace across dozens of wikis. Given that scale, I wanted to bring both the dishonesty and the potential disruption of deletion here before filing a mass DR. — Preceding unsigned comment added by Pi.1415926535 (talk • contribs) 04:04, 11 August 2026 (UTC)

The big issue here is significant undeclared retouching. I'm not even sure we can presume AI; given a good collection of sky backgrounds, I could probably achieve this in GIMP without much difficulty. - Jmabel ! talk 06:22, 11 August 2026 (UTC)

• The rainbow is in the wrong place for the Sun. So this is no longer a photograph, it's a derivative artwork now showing Happy, Smiley Vermont. That's not entirely outside of scope, but it needs to be annotated as such. If we don't have policy in place requiring that annotation, we ought to write some ASAP. Andy Dingley (talk) 16:28, 11 August 2026 (UTC)

Cross-wiki troll

The user was blocked on enwiki and is here now. Acroterion (talk) 02:48, 14 August 2026 (UTC)

Globally locked. Acroterion (talk) 02:59, 14 August 2026 (UTC)

I think I got all of it. AntiCompositeNumber (they/them) (talk) 03:01, 14 August 2026 (UTC)

This section is resolved and can be archived. If you disagree, replace this template with your comment. AntiCompositeNumber (they/them) (talk) 03:01, 14 August 2026 (UTC)