Commons:Administrators' noticeboard

Shortcut: COM:AN

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

This is a place where users can communicate with administrators, or administrators with one another. You can report vandalism, problematic users, or anything else that needs an administrator's intervention. Do not report child pornography or other potentially illegal content here; e-mail legal-reportswikimedia.org instead. If reporting threatened harm to self or others also email emergencywikimedia.org.
Vandalism []	User problems []	Blocks and protections []	Other []
Report users for clear cases of vandalism. Block requests for any other reason should be reported to the blocks and protections noticeboard.	Report disputes with users that require administrator assistance. Further steps are listed at resolve disputes.	Reports that do not suit the vandalism noticeboard may be reported here. Requests for page protection/unprotection could also be requested here.	Other reports that require administrator assistance which do not fit in any of the previous three noticeboards may be reported here. Requests for history merging or splitting should be filed at COM:HMS.
Archives
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	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	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

^{Translate this page}

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

purge Admin backlog

---

Copyright:

• Copyright violations: ~46
• Unfree Flickr files: ~0
• Recent unfree Flickr images: ~2
• Media uploaded without a license as of 2026-02: ~141

Other:

• Duplicates: ~287
• Advertisements/spam: ~6
• Personal photos/selfies: ~48
• Other speedy deletions: ~58
• Categories for discussion: 134 months
• Media requiring a split up: ~0
• Requests for unblock: ~2
• Undeletion requests: ~14

Protected edit requests:

• Full protection: ~60
• Interface admin: ~11
• Technical: ~4
• Template protection: ~6
• Protection level: ~0

See also: DR, HMS, …

COMMONS DISCUSSION PAGES

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

---

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

---

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

Note

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

Coms problems with VRT (ticket 2025121610008447)

I have 128k edits on Commons since 2009, hence it would be fair to assume that by now, I know my way around the project and copyright. Having been elected to Tasman District Council, I thought it would be useful to get my hands onto official photos taken for this local authority. When those photos were taken, I checked with the photographer whether he has a contract in place that transfers the copyright to his client, which he said was indeed the case. Next, I checked with council staff whether they'd be happy to release the photos under a free license, which they were willing to do. I asked the council's legal counsel (Leith Townshend) whether he'd be the right person to sign off on the release of rights to the photos, which he agreed to. I then thought it's about time that I learned how use OpenRefine. Probably useful when you are dealing with 240 or so files, and I thought it's useful to have all the structured data defined, too. But that's beside the point.

Timeline of events is roughly like this:

• Dec 2025: finished uploading everything
• 9 Dec: I sent the release of rights email to TDC's legal counsel for him to forward this to VRT
• 17 Dec: TDC's legal counsel forwards the release of rights email to VRT
• 19 Dec: The VRT response comes back stating: "Unfortunately, we cannot use your content on the basis of statements such as "I allow Wikipedia to use my photos"."
• 19 Dec: My reply to that email was: "Well, that's not what Leith said. It was a cover note where he mentioned his "approval for the photos to be uploaded to Wikipedia" - that's a nicety rather than a legal description. The full release text was below that."
• 20 Dec: Email from VRT addressed to me: "The problem is that you were advised, improperly, to forward an email releasing the image under a specific licence. For legal reasons we don't accept forwarded permission statements, besides which it is not clear who is the copyright holder of the image and/or the photographer. First, can you clarify that and then have that person email a release permission statement so the image can be verified.

How did you become the exclusive copyright holder of this image <https://commons.wikimedia.org/wiki/File:Moko_Tepania_official_council_portrait.jpg>? I ask this because normally this is the photographer unless their contract specifies release of the copyright. Mostly photographer's give usage rights which is not sufficient to the Wikimedia Commons.

I've added detail below for the copyright holder to complete and they should email it from their verifiable email DIRECTLY to this thicket number.

For the copyright holder, they can use the template found on this page: <https://commons.wikimedia.org/wiki/Commons:Email_templates/Consent> or another way of producing a permission statement is through the Wikimedia Permission Release Generator, which can be accessed here: <https://tools.wmflabs.org/relgen/>.

This tool will guide you through the process of creating a release statement which we will be able to readily accept, and is the preferred method of releasing the rights to your media for use on Wikimedia projects such as Wikipedia.

Whatever method you choose to make the permission statement, once completed please send the resulting text in an email reply from your own email address and please MAKE SURE the following "[Ticket#:2025121610008447]" is included in the subject line of the email as reference in the reply otherwise it will not be connected to this ticket."

• 21 Dec: My response to that: "Firstly, it wasn't me who forwarded the email. The permissions email came from Leith Townsend; see the 16/12/2025 20:22 (CET) email below. I wrote the permissions statement for Leith. As a lawyer (he is Tasman District Council’s legal counsel), he will have no trouble understanding it.

Secondly, when the photographer took photos (including of me, e.g. this one), I asked him whether his contract with Tasman District Council deals with copyright. He said that yes, he transfers copyright to the council when he works for them, and that is stated in their contract.

Thirdly, regarding the Moko Tepania image, I think you are confused. I have nothing to do with that image. The upload history shows us that TheLoyalOrder put it on Commons."

• 4 Jan 2026: Email from me to VRT: "Happy new year from New Zealand. Can you please let me know what’s happening with this ticket?"
• 4 Jan: User:Krd starts deleting the photos with rationale "no ticket permission since..."
• 6 Jan: Email from VRT to Leith Townshend: "Please advise who is the creator (photographer) of the image(s), and by which reason Tasman District Council became holder of the full and exclusive copyright."

At this point, I'm getting a bit frustrated. Each photo has the photographer specified in the structured data (d:Q136889058). And I've already explained that the photographer transfers copyright to TDC when he works for them.

• 6 Jan: I thought I'd check in with Krd whether they can resolve this stalemate. Not sure why the conversation isn't archived as they appear to archive everything else; from the talk page history, the conversation is here. Most of that conversation was in German. Krd had a few issues with the ticked: unclear who the photographer is, why the client is the license holder, and the list of files submitted in an Excel spreadsheet without clickable links.
• 7 Jan: I've sent a list to VRT with clickable links for the files, along with an apology that I didn't know that this was the expectation.
• 7 Jan: Leith responds to the photographer query: "The Council contracts a photographer called James Mills from Think Visual to take pictures at some official events. I have just confirmed with James’ business partner that the copyright is owned by Council."
• 7 Jan: Query from VRT to Leith: "is James Mills the photographer who created the images we are discussing?"
• 8 Jan: Reply from Leith to VRT: "Yes"
• 14 Jan: I follow up with VRT: "Greetings from New Zealand. I was wondering what the status is of this ticket. All the questions that were asked of us have been answered. User:Krd deleted some 200 photos from this upload on 7 and 8 January. Nothing has been restored yet. Is there anything that’s outstanding?"
• 21 Jan: Follow up from me: "Would somebody from VRT please be so kind and let me know what the status is of this ticket? All the questions that were asked of us have been answered. However, the files that have been deleted have not be reinstated. Is there anything else left to resolve?"
• 5 Feb: As suggested below by Jeff G., I have followed up with VRT, citing the Copyright Act 1994.

How is this reasonable treatment of somebody trying to do the right thing all along? Why am I not being told what the outstanding issue is? Schwede66 08:28, 28 January 2026 (UTC)

@Schwede66: I think it would help matters if VRT had contact from James Mills or Think Visual confirming what happened, along with a copy of the contract with the Council and comment as to where to find the copyright transfer in that contract (citation of chapter and verse, as it were).   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 14:52, 28 January 2026 (UTC)

Why am I being put through this? The whole rights transfer is based on the copyright holder releasing the photos under a free license. To now have to run after the photographer and talk him into releasing his contract with TDC seems a steep task. I’m getting the impression that the VRT system is fundamentally broken and I shall stay away from them in future. Schwede66 16:07, 28 January 2026 (UTC)

Something also the VRT is unaware of is that under NZ copyright law, the copyright of commissioned photos is by default owned by the employer, which is not the standard elsewhere. So there is no need for @Schwede66 to get a release or confirmation in writing from the photographer, as the copyright transfer to TDC was automatic. Giantflightlessbirds (talk) 02:45, 29 January 2026 (UTC)

I certainly didn't know that, Mike. Thanks for that! Schwede66 03:51, 29 January 2026 (UTC)

Anyone got any thoughts on that input? Schwede66 07:05, 30 January 2026 (UTC)

I think you should not have gotten this kind of response, but I do not have access to Commons VRT, so I am not sure I can help you here. Thanks for trying to transfer the photos to the PD and uploading them on Commons. Ymblanter (talk) 12:23, 30 January 2026 (UTC)

Ok, I've had a look at New Zealand's Copyright Act 1994. Section 21 deals with ownership of copyright, and is titled "First ownership of copyright". Clause 3 reads:

Where—

(a) a person commissions, and pays or agrees to pay for, the taking of a photograph ...; and

(b) the work is made in pursuance of that commission,—

that person is the first owner of any copyright in the work.

Hence, Mike (Giantflightlessbirds) is right. The district council owns the copyright by default. Hence, it's not necessary to ask the photographer for the contract. Jeff G., would you concur? Schwede66 01:07, 3 February 2026 (UTC)

@Schwede66: I would agree. Please reply to the ticket citing such. Perhaps something nonpublic is gumming up the works.   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 14:18, 3 February 2026 (UTC)

Ok, I've written to VRT citing the Copyright Act 1994. I shall amend the above timeline. Schwede66 00:28, 5 February 2026 (UTC)

Four days later, there has been no reply. How is it a reasonable way to treat fellow editors by not even telling them what the problem is? Schwede66 18:31, 8 February 2026 (UTC)

Nothing really gumming it up, except the ticket is quite lengthy, and we are all volunteers, with our own limited capacity - both in time, and resources to understand if this is complex case or not, since one needs to read through quite a few emails to begin to understand what's going on). I've followed up from VRT's side. --Jonatan Svensson Glad (talk) 19:15, 8 February 2026 (UTC)

Request for deletion of prior versions of an image

Please see File:Elliot Rodger monthly allowance.jpg and observe that I have blurred out a portion of it for what I hope is obvious reasons, per Commons:Revision_deletion#When_Revision_Deletion_may_be_used. Thank you, --Hammersoft (talk) 00:57, 3 February 2026 (UTC)

 Done - Jmabel ! talk 22:05, 3 February 2026 (UTC)

Regarding confirmation and recognition of an allegedly deceased contributor.

User:Bob Burkhardt has two blocks Special:CentralAuth/Bob Burkhardt with the reason stating that he has "passed away" (in German).

• What is the process to confirm this here on Commons? --

Ooligan (talk) 09:31, 3 February 2026 (UTC)

We (or at least I) usually accept the deceased-statement at the users home-wiki, especially since this is usually where we learn of a user's death. In the case at hand, we have a detailed statement at [1].--Túrelio (talk) 09:44, 3 February 2026 (UTC)

@Túrelio, can any editor now add Category:Deceased Commons users to this user's page? -- Ooligan (talk) 10:47, 3 February 2026 (UTC)

I had done that already before my last edit (and thereafter protected the userpage). --Túrelio (talk) 10:49, 3 February 2026 (UTC)

@Túrelio, I see that now. Here is his alternate account: User:Library Guy. Should that also be treated the same? -- Ooligan (talk) 10:56, 3 February 2026 (UTC)

 Done now. --Túrelio (talk) 11:27, 3 February 2026 (UTC)

Source provided by Achim55 = https://www.facebook.com/events/shirley-public-library/local-artist-bob-burkhardt-art-show/528175199121485/ -- Ooligan (talk) 11:05, 3 February 2026 (UTC)

wow, didn't realise we lost so many.. Stemoc 11:28, 3 February 2026 (UTC)

See Commons:Deceased contributors plus Commons_talk:Deceased contributors#to do/add. --Túrelio (talk) 11:41, 3 February 2026 (UTC)

Thank you @Túrelio for your kind help and protection of the User page and alternate account of valued former volunteer contributor User:Bob Burkhardt.

Respectfully, -- Ooligan (talk) 23:22, 3 February 2026 (UTC)

Procedural: both the accounts have been globally locked as well. ─ Aafī on Mobile ^(talk) 19:16, 4 February 2026 (UTC)

Concern Regarding Systematic Bias and Non-Neutral Content

I am reporting a Wikimedia Commons account (account name: 999real) that systematically uploads images about the Iranian protests and revolution exclusively from the Islamic Republic’s government perspective.

The content appears to rely on state-produced or state-aligned sources while excluding independent documentation from civilians, journalists, and victims of state violence. This creates a one-sided and misleading visual record of events and conflicts with Wikimedia’s neutrality and balance principles.

I respectfully request a review of this account for potential systematic bias, non-neutral content curation, and compliance with Wikimedia Commons policies. Naida4343 (talk) 19:53, 3 February 2026 (UTC)

 Not done No admin action required; no policies are being violated here. Anyone is free to upload any content that is in scope and freely licensed. The Iranian state (quasi-state?) news agencies release their work under a free license, so anyone can upload them. If there's, say, a Flickr account from someone opposed the Iranian government that releases under a free license photos of protests from the protesters' perspective, that's also fine for anyone to upload. The Squirrel Conspiracy (talk) 20:05, 3 February 2026 (UTC)

As an aside, I do think that 999real's uploads are too indiscriminate - uploading all 20 photos of the same thing just because they're there, instead of choosing the best 1 or 2 - but that's not a policy violation, and many other users do the same thing, scraping entire Flickr accounts. To 999real's credit, they do go back and ask for photos to be deleted when they spot COM:DW issues, which a lot of people that just dump entire Flickr accounts here don't bother doing. The Squirrel Conspiracy (talk) 20:09, 3 February 2026 (UTC)

There are clear policy violations by @999real here. Writing a description like the one on File:تجمع «همبستگی ملی» و تشییع شهید امنیت در بجنورد 4 (Mehr, 2026).jpg without marking them as a citation is a violation of Commons:Harassment. "In alignment with the protection of editors from harassment described throughout the rest of this policy, edits that harass any living or recently deceased people, even if they are not members of the Wikimedia Commons community, are also prohibited. Per the oversight policy, such content will be deleted or suppressed and editors who post such material may be indefinitely blocked." GPSLeo (talk) 20:29, 3 February 2026 (UTC)

Writing a description like the one on File:تجمع «همبستگی ملی» و تشییع شهید امنیت در بجنورد 4 (Mehr, 2026).jpg without marking them as a citation — but the file description clearly does say that it is a citation ("Translation of original description"). Nakonana (talk) 21:15, 3 February 2026 (UTC)

The untranslated version has no note that it comes from the source and not from the uploader. GPSLeo (talk) 21:20, 3 February 2026 (UTC)

{{Original description disclaimer}} Can someone translate this then I can add it on all files I uploaded $999$REAL 💬 ⬆ 21:42, 3 February 2026 (UTC)

I fixed the template. It should now work as a value for the "Other fields" parameter in the information template. I also marked it for translation. GPSLeo (talk) 17:24, 4 February 2026 (UTC)

 Comment Please see the on-going discussion at COM:VP#Openly licensed propaganda/terrorist material. Yann (talk) 21:56, 3 February 2026 (UTC)

Please close PNG->SVG

Please close User_talk:CommonsDelinker/commands#Replace_images_with_.svg_version and forward to maintainers if deemed as successful. It has been open for over 3 years. Taylor 49 (talk) 16:43, 4 February 2026 (UTC)

I have indicated at the link provided above by Taylor 49 that that consensus is clear, but I do not know who can make this change to the bot. If someone knows, please ping the maintainer there. - Jmabel ! talk 00:57, 5 February 2026 (UTC)

Request of a comparison of contents involving a deleted file

Hello,

could an admin please check whether the contents of the deleted PDF linked on User talk:صباح الجبوري (e.g. File:الباحث اللغوي صباح علي السليمان.pdf) are the same than the content in Special:Diff/1159768493/1159786857? If yes, then that user's behaviour may warrant a block for self-promotional spamming, if not, then my scope warning could be enough. I checked the diff text per Google Translate, it looks like a biography with an evident conflict of interest. Regards, Grand-Duc (talk) 04:10, 5 February 2026 (UTC)

I haven't checked the file content but the file was deleted on 15 Aug 2025 and 30 Jan 2026 for being out of scope. An OoS warning is warranted Gbawden (talk) 06:46, 5 February 2026 (UTC)

Request by HarvestLife

Hi, I'm new here. Not sure how to start my own request, but I'd like to delete images I uploaded that are misnamed. I tried editing, but it looks like the titles remain in error, however the description is updated.

Error: Tatiana Manslany

General title/caption: Tatiana Manslany at How Brief premiere during 2026 Sundance Film Festival

Correct: Tatiana Maslany

General title/caption: Tatiana Maslany at How Brief premiere during 2026 Sundance Film Festival (5)

I'm re-uploading the images with the correct spelling.

There should be 8 images to delete.

Thank you! HarvestLife (talk) 17:40, 5 February 2026 (UTC)

@HarvestLife: Hi, Only users with the proper right can rename files, i.e. not new users. For now, please use {{Rename}}. Add this template to your files with the new names. Thanks, Yann (talk) 17:55, 5 February 2026 (UTC)

@HarvestLife: good photos.

To change file names, there is no need to delete. As Yann mentions, you can use {{Rename}}. Also, there should be a "Move" tool aailable for each file page (probably on your right nav, depending on your skin), which will fill in the {{Rename}} request in a manner that may be less error-prone than trying to do it by hand. - Jmabel ! talk 19:08, 5 February 2026 (UTC)

New tag for QuickEXIF

Hello! I'm developing a new user script ("QuickEXIF") to allow users to edit JPG EXIF data in-browser (source code here). To track changes made via the script, I'd like to request a new tag, if an admin could set one up for me:

• Tag name: QuickEXIF
• MediaWiki:Tag-QuickEXIF: [[Commons:QuickEXIF|QuickEXIF]]
• MediaWiki:Tag-QuickEXIF-description: EXIF changes made via the [[Commons:QuickEXIF|QuickEXIF]] user script

Thanks, ~Kevin Payravi (talk) 20:41, 5 February 2026 (UTC)

• @Kevin Payravi: tags created. - Jmabel ! talk 05:18, 6 February 2026 (UTC)

  @Jmabel: Thanks! I see the label/description pages, but I think the tag itself still needs to be created via Special:Tags. ~Kevin Payravi (talk) 05:30, 6 February 2026 (UTC)

   Done - Jmabel ! talk 06:11, 6 February 2026 (UTC)

Only for third person advice

This is not a complaint or some kind of report but just a thread for third person advice. Whyiseverythingalreadyused removed a comment by a temp account at Revision #1160415941 saying it was a personal attack. I don't think it was. So I reverted him and restored that comment at Revision #1160421048. He reverted me at Revision #1160427769. Ideally he should've come to my TP before reverting and tried to discuss this, but let's leave that aside. I would like to hear third user opinion as to should we consider "self-snitching at its finest" a personal attack? Shaan Sengupta^Talk 11:50, 6 February 2026 (UTC)

I don't about this specific edit, but more generally I find Whyiseverythingalreadyused's edits suspicious. I doubt this is a new user, but I don't have any evidence. Yann (talk) 12:00, 6 February 2026 (UTC)

Checkuser me Whyiseverythingalreadyused (t · c · he/him) 12:45, 6 February 2026 (UTC)

I mean... any checkusers interested (not Yann per Special:ListUsers/checkuser) Whyiseverythingalreadyused (t · c · he/him) 13:11, 6 February 2026 (UTC)

Yann is anyway not a CU. Shaan Sengupta^Talk 13:12, 6 February 2026 (UTC)

Bro I know Whyiseverythingalreadyused (t · c · he/him) 13:28, 6 February 2026 (UTC)

I just had the wrong words I guess Whyiseverythingalreadyused (t · c · he/him) 13:28, 6 February 2026 (UTC)

This discussion is no sufficient reason for performing an SPI. --Lymantria (talk) 09:25, 7 February 2026 (UTC)

@Lymantria, any comment on the main reason this thread was started? Whether the above highlighted comment violates NPA and deserves to be removed. Shaan Sengupta^Talk 09:28, 7 February 2026 (UTC)

@Shaan Sengupta in the context of an RFA, where the admin candidate seems overwhelmed by the negative responses, you might consider the self-snitching comment as, well, unfriendly, bullying perhaps. In light of the gender preference lines just before the self-snitching comment, I can imagine it is considered a PA, if you read it as reaction to that part of the discussion. I didn't initially read it that way. Borderline IMHO, you might have not reverted. --Lymantria (talk) 13:49, 7 February 2026 (UTC)

@Lymantria: The self-snitching comment may have been written about me; there is one user who calls me a snitch, and I consider that a PA.   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 13:58, 7 February 2026 (UTC)

@Jeff G. But you hadn't really been part of that discussion, had you? --Lymantria (talk) 14:55, 7 February 2026 (UTC)

@Lymantria: I made the first !vote.   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 23:42, 7 February 2026 (UTC)

@Lymantria, thanks for the correction. I'll try to be more careful with these in future. Also, that comment came as a response to Very unclear what to "address" and how. But again, if we go by the thread, it can be interpreted either way. Anyways, thanks again. Regards, Shaan Sengupta^Talk 16:03, 7 February 2026 (UTC)

I believe it does

I only asked for a CU because Yann said, "he might be a sock"

This is diverging way too far lol Whyiseverythingalreadyused (t · c · he/him) 12:12, 7 February 2026 (UTC)

Request for courtesy blanking of real name (uploader)

Hello,

I am the original uploader of all files listed here: https://commons.wikimedia.org/wiki/Special:ListFiles/Alberto_Buscat%C3%B3_V%C3%A1zquez

All files were uploaded in February 2020 using UploadWizard, under my real name.

I request courtesy blanking / suppression of my real name ("Alberto Buscató Vázquez") from all these files, as I no longer wish my real identity to be publicly associated with them.

I am not requesting deletion of the files, only anonymization of personal attribution where possible. I understand that the licenses remain unchanged.

Thank you very much. Alberto Buscató Vázquez (talk) 18:05, 7 February 2026 (UTC)

You have to attribute them so some pseudonyme first. Reply here after you did this. GPSLeo (talk) 19:24, 7 February 2026 (UTC)

If you use VFC, it's pretty easy to mass-change them to a pseudonym at once. - Jmabel ! talk 20:24, 7 February 2026 (UTC)

Elisha the FRICKIN Gamer hoax campaign

Sock

I have stumbled a pawn of hoax campaign online about a username or Nickelodeon show titled Elisha the FRICKIN Gamer will reportedly called a hoax on forms and a deleted Wikipedia page and the hoax being referenced on Reddit and if this title is a user it's probably a Spam bot or a fake title page on a platform called miraheze mentioning that he is a user and also a Nickelodeon show running from 1997 to 2002 and the page also falsely credits Mark krysko for this bogus work. Jack blue's clues (talk) 19:16, 7 February 2026 (UTC) @Jack blue's clues: My apologies, but I don't see what that has to do with Wikimedia Commons (this site) or what administrative action you are asking for. - Jmabel ! talk 20:26, 7 February 2026 (UTC) They were probably looking for Simple English Wikipedia[2] or Fandom wikia[3] and might not know the difference between the wikis. Nakonana (talk) 20:41, 7 February 2026 (UTC) Appears to be a sock of Elisha the FRICKIN Gamer. NguoiDungKhongDinhDanh 20:53, 7 February 2026 (UTC)  Done. Jack is globally locked. Taivo (talk) 09:31, 8 February 2026 (UTC)

Reporting a user regularly contributing images with incorrect license

User:Sergey M R is uploading images from Russian Empire on a regular basis, claiming they are CC. Quite obviously, the user is not old enough (must be 125!) to have made these pictures himself, and thus these images are, at best, PD-RusEmpire. It should be noted that this user has been permabanned on RU:WP for 9 years of providing fake sources, routine copyvio and evading permaban. Sorry if this is the wrong forum to post this type of notice, but it's the best suiting option of those that I could find. -- Wesha (talk) 19:35, 8 February 2026 (UTC)

While the uploads of post-1917 materials might be a problem, anything before the October Revolution can just be changed to {{PD-RusEmpire}}. No comment from me here on the user conduct issue. - Jmabel ! talk 21:44, 8 February 2026 (UTC)