Jump to content

Commons:Village pump

This page is semi-protected against editing.
From Wikimedia Commons, the free media repository

Shortcut: COM:VP

↓ Skip to table of contents ↓       ↓ Skip to discussions ↓       ↓ Skip to the last discussion ↓
🌐 Village pumps for other languages
COMMONS DISCUSSION PAGES
Welcome to the Village pump

This page is used for discussions of the operations, technical issues, and policies of Wikimedia Commons. Recent sections with no replies for 7 days and sections tagged with {{Section resolved|1=--~~~~}} may be archived; for old discussions, see the archives; the latest archive is Commons:Village pump/Archive/2025/03.

Please note:

  1. If you want to ask why unfree/non-commercial material is not allowed at Wikimedia Commons or if you want to suggest that allowing it would be a good thing, please do not comment here. It is probably pointless. One of Wikimedia Commons’ core principles is: "Only free content is allowed." This is a basic rule of the place, as inherent as the NPOV requirement on all Wikipedias.
  2. Have you read our FAQ?
  3. For changing the name of a file, see Commons:File renaming.
  4. Any answers you receive here are not legal advice and the responder cannot be held liable for them. If you have legal questions, we can try to help but our answers cannot replace those of a qualified professional (i.e. a lawyer).
  5. Your question will be answered here; please check back regularly. Please do not leave your email address or other contact information, as this page is widely visible across the internet and you are liable to receive spam.

Purposes which do not meet the scope of this page:

Search archives:

   

Start a new discussion

# 💭 Title 💬 👥 🙋 Last editor 🕒 (UTC)
1 Vector 2022 will be the default skin 14 11 PantheraLeo1359531 2025-03-05 14:20
2 Brunei Darussalam Newsletter 2 2 Pangalau 2025-03-07 12:43
3 Summaries of the last two Commons Community Conversations now available 6 3 PantheraLeo1359531 2025-03-05 17:20
4 "This file did not pass file verification." 9 3 Bawolff 2025-03-06 09:21
5 Is there a reason Commons doesnt allow us to convert MP4 files to WEBM when uploading? 12 8 Omphalographer 2025-03-07 19:37
6 Non-confirmed users still allowed to use Upload Wizard? 2 2 Commander Keane 2025-03-07 21:53
7 Respect and non-disturbance for long-term prolific contributor 43 15 RoyZuo 2025-03-12 02:18
8 Larger version is 180° rotated 4 3 TheDJ 2025-03-10 12:51
9 Decade by category navbox 10 3 Tvpuppy 2025-03-08 19:13
10 Universal Code of Conduct annual review: proposed changes are available for comment 1 1 Keegan (WMF) 2025-03-07 18:50
11 Clothing by date 7 5 ReneeWrites 2025-03-11 07:43
12 Theatre by year 8 2 Rathfelder 2025-03-11 20:25
13 Wishlist for new features on Commons 1 1 PantheraLeo1359531 2025-03-10 16:26
14 "AutoCats" script for automatic categories 1 1 Yaron Koren 2025-03-10 16:32
15 Possible mass upload of Trump-sensitive photos 5 4 Gaurav 2025-03-11 23:38
16 Categories under Category:FoP-Switzerland 1 1 JWilz12345 2025-03-11 12:33
Legend
  • In the last hour
  • In the last day
  • In the last week
  • In the last month
  • More than one month
Manual settings
When exceptions occur,
please check the setting first.
Village pump in Rzeszów, Poland [add]
Centralized discussion
See also: Village pump/Proposals   ■ Archive
Template: View   ■ Discuss    ■ Edit   ■ Watch
SpBot archives all sections tagged with {{Section resolved|1=~~~~}} after 1 day and sections whose most recent comment is older than 7 days.

January 24

Vector 2022 will be the default skin

A two-minute video about Vector 2022

Hello. We are the Wikimedia Foundation Web team. We are here to announce that the Vector 2022 skin will become the default desktop skin here on 10 February. We will gladly answer your questions, concerns, or additional thoughts! We will also help you adjust things which Vector 2022 may not be compatible with. Check out our FAQ – you will find many useful answers there.

If you are using Vector legacy skin, you may find yourself receiving the Vector 2022 skin. You may select Vector legacy as your global preference to avoid seeing the change. Logged-in users can at any time switch to any other available skins, or stay with Vector 2022 and enjoy choosing between its light and dark mode. Users of other skins will not see any changes.

Why are we changing the skin now

For technical reasons (listed below), we need to deploy the skin soon. After deployment, we will continue discussing issues and questions about the interface, and we'll be ready to work with you on various issues like gadget compatibility.

More details on why we need to deploy the skin now
  • Due to releases of new features only available in the Vector 2022 skin, our technical ability to support both skins as the default is coming to an end.  Keeping more than one skin as the default across different wikis indefinitely is impossible. This is about the architecture of our skins. As the Foundation or the movement in general, we don't have the capability to develop and maintain software working with different skins as default. This means that the longer we keep multiple skins as the default, the higher the likelihood of bugs, regressions, and other things breaking that we do not have the resources to support or fix.  
  • Vector 2022 has been the default on almost all wikis for more than a year. In this time, the skin was proven to provide improvements to readers while also evolving. After we built and deployed on most wikis, we added new features, such as the Appearance menu with the dark mode functionality. We will keep working on this skin, and deployment doesn't mean that existing issues will not be addressed. For example, as part of our work on the Accessibility for Reading project, we built out dark mode, changed the width of the main page back to full (T357706), and solved issues of wide tables overlapping the right-column menus (T330527).
  • Vector legacy's code is not compatible with some of the existing, coming, or future software. Keeping this skin as the default would exclude most users from these improvements. Important examples of features not supported by Vector legacy are: the enriched table of contents on talk pages, dark mode, and also temporary account holder experience which, due to legal reasons, we will have to enable. In other words, the only skin supporting features for temporary account holders (like banners informing "hey, you're using a temp account") is Vector 2022.

How to request changes to the skin

We are guessing that some of you may want to see some changes to the skin. We are still improving Vector 2022 and the overall reading experience. If you have a feature request or a bug report, we encourage you to comment here or open a ticket in Phabricator. We will decide on the priority of these requests alongside our regular processes after deployment. Some fixes may be done via gadgets or user scripts, too.

About the skin

Global preferences

We encourage you to try out Vector 2022 by going to the Appearance tab in your preferences and selecting it from the list of skins. Getting used to it may take a few days, and that's the standard for interface changes.

Details about the skin

Vector 2022 is the modernized version of the currently default skin Vector legacy. It is the default on almost all Wikimedia wikis (there are about 10 left now). Most of the active editors use it and do not opt out of the skin at statistically noticeable rates despite easy access to the opt-out link. (Check the source here.)

[Our 2022 answer to why is a change necessary] When the current default skin was created, it reflected the needs of the readers and editors as these were in 2010. Since then, new users have begun using the Internet and Wikimedia projects in different ways. Although there were changes to features the skin supported, the structure, navigation, visual layout, and overall readability of the skin did not change. The old Vector does not meet the current users' needs.

[Objective] The objective for the Vector 2022 skin is to make the interface more welcoming and comfortable for readers and useful for advanced users. It introduces a series of changes that aim to improve problems new and existing readers and editors were having with the old skin. It draws inspiration from previous user requests, the Community Wishlist Surveys, and gadgets and scripts. The work helped our code follow the standards and improve all other skins. We reduced PHP code in the other available skins by 75%. The project has also focused on making it easier to support gadgets and use APIs.

[Changes in a nutshell] The skin introduces changes to the navigation and layout of the site. It adds persistent elements such as a sticky header and table of contents to make frequently-used actions easier to access. It also makes some changes to the overall styling of the page. The analysis of the data collected concluded that these changes improve readability and usability, and save time currently spent in scrolling, searching, and navigating – all of which can be interpreted to create an easier reading experience. The new skin does not remove any functionality currently available on the old Vector skin. On wikis with this skin as the default, there are no negative effects to page views, account creation, or edit rates. On our project pages you will find findings and results in a nutshell.

A summary of findings and results

  • On average, 87% of logged-in users on our early adopter wikis (incl. French Wikipedia) continue to use the new skin once they try it.
  • The sticky header makes it easier to find tools that editors use often. It decreases scrolling to the top of the page by 16%.
  • The new table of contents makes it easier to navigate to different sections. Readers and editors jumped to different sections of the page 50% more than with the old table of contents.
  • The new search bar is easier to find and makes it easier to find the correct search result from the list. This increased the amount of searches started by 30% on the wikis we tested on.
  • The skin does not negatively affect page views, edit rates, or account creation. In fact, there is observational evidence of increases in page views and account creation across partner communities.

How can editors change and customize this skin?

  • We make it possible to configure and personalize our changes. We are happy to work with volunteers with technical skills who would like to create new gadgets and user scripts. So far, many gadgets and user scripts have been built by volunteer developers. These aspects include making the background gray, turning off sticky elements, bringing back the old table of contents, and more. We encourage you to check out our repository for a list of currently available customizations and changes, or to add your own.
  • In Vector 2022, logged-in and logged-out users can change the font size and color scheme based on their individual needs. Dark mode is now available for logged-in users of Vector 2022, and we would like to make it available to logged-out users as soon as most articles are dark-mode friendly.

How will we go through the change

  • Wiki page: we would like to kindly suggest creating a page similar to English Wikipedia's w:WP:V22. It may explain the basics like how to opt-out or customize the skin.
  • CentralNotice banner for logged-in users: before and shortly after deployment, we will display a banner announcing the change. It will be linking to Commons:Vector 2022 if you decide to create such a page. Otherwise, it will be linking to this announcement. This should limit the confusion and the number of repetitive questions about the change.

If you think there are any significant technical issues, let us know – perhaps we've missed something. We're looking forward to your comments and reactions from readers after deployment. Thank you! OVasileva (WMF) and SGrabarczuk (WMF) (talk) 01:06, 24 January; Unarchiving to keep this here SGrabarczuk (WMF) (talk) 19:20, 14 February 2025 (UTC)[reply]

This is great news! I've been using Vector 2022 here for over a year now without issue, and it's important that Commons looks the same to users as the other Wikimedia projects. Thanks. Mike Peel (talk) 19:25, 10 February 2025 (UTC)[reply]
Personally I'm hating it.StarTrekker (talk) 07:06, 11 February 2025 (UTC)[reply]
I think I don't like some things either. However, it takes some time to get used to it and afterwards one likes it more than the prior skin. It would be good to name some things that may be problematic if there are any so it could get improved upon. For example, I think it may make the links to the Welcome and Community portal pages and possibly a few other things like the link to the page information page with the Pageviews link too hard to find. Prototyperspective (talk) 13:18, 11 February 2025 (UTC)[reply]
I think the links to the Wikipedia articles are now too hidden, especially for users not very familiar with the site. I think the Wikipedia article of the language the user has configured with a fallback to the English article if there's no article in that language should be linked well-visibly, for example right before the category description at the top of the page. Prototyperspective (talk) 18:14, 12 February 2025 (UTC)[reply]
It has been around for a quite long time in Wikipedia and other wikis. Software changes are often disruptive at first, but once you get used to them, you don't want to go back. MGeog2022 (talk) 18:30, 12 February 2025 (UTC)[reply]
I use the skin since 2019, so no huge changes at all :D --PantheraLeo1359531 😺 (talk) 14:20, 5 March 2025 (UTC)[reply]
Amazingǃ Comfortable visual consistent across the projects. Thanks. Ong Kai Jin (talk) 13:02, 11 February 2025 (UTC)[reply]
@OVasileva (WMF) @SGrabarczuk (WMF): I think it makes sense as a whole. But there are a couple of things that I don't understand and that I think are relevant to all readers and users. I suppose this has been discussed before.
  • I don't really see how other Wikimedia projects are "Tools." I doubt readers will look for them there. It also doesn't seem ideal to have to scroll in a drop-down menu, in a lot of cases. Why not a separate "In other projects" tab?
  • In the file namespace, perhaps the "Download," "Use this file" etc menu shouldn't be to the right of the previewed filed, since it can overlap awkwardly with the default position of the "Appearance" settings. Or is it an intentional choice that "Appearance" can overlap with other elements?
Sinigh (talk) 14:18, 11 February 2025 (UTC)[reply]
Tracked in MediaWiki talk:Gadget-Stockphoto.js#Vector 2022 vertical support Jon Robson, WMF 20:37, 24 February 2025 (UTC)[reply]

I've seen Appearance panel was overlapped on right side. [1] -- Great Brightstar (talk) 05:39, 16 February 2025 (UTC)[reply]

Now I see the stockphoto layout panel moved to the top of image. This is fixed. -- Great Brightstar (talk) 14:22, 3 March 2025 (UTC)[reply]

February 03

Brunei Darussalam Newsletter

Hello! I came across the Brunei Darussalam Newsletter, where some of the older issues contain a sidebar on the left side of page 2 that states: "Brunei Darussalam Newsletter is published fortnightly by the Department of Information. It reports on government, social and business events in the country. All money values are expressed in Brunei dollars $, unless otherwise stated. Any information in this newsletter may be reproduced; a clipping of the publication would be appreciated. For free subscription (Excluding postage) write to Information Department, Jalan Stoney, Bandar Seri Begawan 2041, Brunei Darussalam." An example would be here. So my question is whether the term "information" in that specific issue could also apply to images.

This has been previously used in "Category:Ministry of Foreign Affairs (Brunei) News Digest issues". — Preceding unsigned comment added by Pangalau (talk • contribs) 13:52, 3 February 2025 (UTC)[reply]

@Pangalau my opinions:
  1. "information" probably only refers to facts, like if there is an article talking about economic projects, it's free to "reproduce the information" (by writing your own article with the same facts), but merely copypasting the entire article would still probably be violation of copyright.
  2. users should be careful and should not construe any vague permission as compatible with com:l.
RoyZuo (talk) 09:52, 7 March 2025 (UTC)[reply]
Noted, and I appreciate your opinionǃ Pangalau (talk) 12:43, 7 March 2025 (UTC)[reply]

February 28

Summaries of the last two Commons Community Conversations now available

Hello all! The summaries from our last two Commons Community Conversations are now available on Commons:

If you have more feedback coming about the topics we discussed, you can do so in the Community calls talk page.

Thank you very much for participating and sharing your feedback! Sannita (WMF) (talk) 15:32, 28 February 2025 (UTC)[reply]

@Sannita (WMF): Thanks! When do you anticipate them being available for the first four converstions?   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 18:12, 28 February 2025 (UTC)[reply]
All four summaries (and the summaries of the two meetings before the conversations) are already available at Commons:WMF_support_for_Commons/Commons_community_calls#Past_discussions. Sannita (WMF) (talk) 17:14, 1 March 2025 (UTC)[reply]
@Sannita (WMF): Thanks! I'm sorry, I must have missed those.   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 17:59, 1 March 2025 (UTC)[reply]
@Jeff G. No problem at all! I also lose track of discussions sometimes, that why I'm happy about notifications and pings :) Sannita (WMF) (talk) 15:19, 3 March 2025 (UTC)[reply]
The textured meshes are hot stuff --PantheraLeo1359531 😺 (talk) 17:20, 5 March 2025 (UTC)[reply]

March 04

"This file did not pass file verification."

Hi all

I've just tried to upload some svg files (individual pages of a booklet I've been working on for a Wikimedia chapter) and I'm getting a weird message with about 20% of the pages, it says "This file did not pass file verification". Two things:

  1. There is no further information about what this means and no link to documentation that explains this. How do I requestion this gets fixed?
  2. Does anyone know if there is documentation on what this error means and how to fix it?

Thanks

John Cummings (talk) 13:10, 4 March 2025 (UTC)[reply]

@John Cummings: Since you don't say the date or file name it's hard to be sure. You say you "just" did this, but the most recent Filter Log entries I can find for you are almost a week back. Those were for trying to add a permission ticket when you aren't a VRT member. Actually, that's what I see for all Filter Log issued for you in the last month or so. - Jmabel ! talk 18:40, 4 March 2025 (UTC)[reply]
Normally it would mean that the file is not an svg or has the wrong extension (this would not show up in the abuse log). It would help if you could upload the file somewhere else and link to it so we can see. Bawolff (talk) 20:11, 4 March 2025 (UTC)[reply]
Looking at logs, it looks like you tried to upload a 12mb file named "12 Case study pages Sudan.svg". Are you sure that wasn't supposed to be a .pdf instead? Case studies aren't usually in SVG format, and the error you got would be the one you would get if you tried to upload a PDF file with a .svg extension. Bawolff (talk) 09:39, 5 March 2025 (UTC)[reply]
Hi Bawolff thanks, its definately an .svg, Jmabel, I don't understand what ticket you mean, am I doing something wrong? If so I'd like to correct it. To be clear, it won't show up in my uploads because it won't accept it as an upload. Here are the files which don't work, you can see from my recent uploads other svg files in the same series I made at the same time work completely fine Category:WikiGap Brochure...
I've started a phab ticket here
Thanks for any suggestions.
John Cummings (talk) 11:11, 5 March 2025 (UTC)[reply]
Hi Jmabel, thanks but I'm completely confused, I didn't try uploading these images with a VRT template, I think I've only ever uploaded anything with the OTRS/VRT pending template.
@John Cummings It looks like those files have very large embedded JPEGs in them. Commons does not allow raster images embedded in SVGs to be larger than 10mb (after base64 conversion). I think this is the issue you are having. Bawolff (talk) 03:53, 6 March 2025 (UTC)[reply]
Hi Bawolff, thank you very much for explaining, is this documented anywhere? John Cummings (talk) 09:07, 6 March 2025 (UTC)[reply]
I added it to https://commons.wikimedia.org/w/index.php?title=Help:SVG&diff=prev&oldid=912120003 last time this came up. As far as i can tell, its not an intentional change but a change because one of the programs mediawiki uses (libxml) changed its default. So all that would need to be done is for mediawiki to set the LIBXML_PARSEHUGE option to restore the old behaviour. Perhaps @Sannita (WMF) could convince the multimedia team to look into it. Bawolff (talk) 09:21, 6 March 2025 (UTC)[reply]

March 05

Is there a reason Commons doesnt allow us to convert MP4 files to WEBM when uploading?

Having to search out external software and websites just to even being allowed to upload videos in the first place is a huge annoyance which only helps discouraging users from uploading content here. --Trade (talk) 23:49, 5 March 2025 (UTC)[reply]

@Trade: Yes, "Commons does not support the more commonly used patent-encumbered video formats such as H.264 and H.265 that are used in MP4 and MOV files, since their use could require royalty payments" per COM:Video#Video formats.   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 01:55, 6 March 2025 (UTC)[reply]
That's the whole point of converting the videos Trade (talk) 03:25, 6 March 2025 (UTC)[reply]
@Trade, this was a feature request in 2023: Commons:Requests for comment/Technical needs survey/Video conversion support. That discussion mentions video2commons which may help somewhat. See Help:Converting video. Commander Keane (talk) 03:21, 6 March 2025 (UTC)[reply]
The reason is here: Commons:Requests for comment/MP4 Video. Pyb en résidence (talk) 18:52, 6 March 2025 (UTC)[reply]
That RFC was over ten years ago, though. Consensus can change - as can the facts on the ground; did Wikimedia even support video transcoding at the time? Omphalographer (talk) 19:56, 6 March 2025 (UTC)[reply]

March 06

Non-confirmed users still allowed to use Upload Wizard?

I previously discussed how to implement the consensus disallowing any more local cross-wiki uploading into Commons. Somehow, I hadn't seen one reply, so the discussion was then archived without such.

Maybe I should've specified further as I'm doing now. Does Commons still allow non-confirmed users to use Upload Wizard, especially to upload files as "free"? (A previous proposal to restrict non-confirmed users from uploading videos and audio clips didn't go well. I'm starting this discussion cautiously before making any more proposals.) George Ho (talk) 22:06, 6 March 2025 (UTC)[reply]

@George Ho, thanks for continuing to work on what I perceive is the terrible mess of cross-wiki uploads.
I can't work out the answer to your question:
Does Commons still allow non-confirmed users to use Upload Wizard, especially to upload files as "free"?.
Well, as far as I can see (and I am auto-confirmed so maybe non-confirmed can't even open the Wizard) the only way to progress past the release rights stage in the Commons Upload Wizard is to select either:
  • This work was created by me and anyone is free to use it.
  • This work was created by someone else and it is free to share.
Both "free". So your question is can users with an account less than 4 days old (non-confirmed) upload at all? As far as I can tell (if mediawiki:Manual:User_rights "user" corresponds to "Users" in Wikimedia world) this would be the "Users" group in Special:ListGroupRights and it says this group has "Upload" permissions. I have no idea if an edit-filter is being used to override GroupRights, but I think that would be very strange.
After writing all this I have confused myself. But I will post it in hopes that someone knowledgeable can participate. Commander Keane (talk) 21:53, 7 March 2025 (UTC)[reply]

March 07

Respect and non-disturbance for long-term prolific contributor

A user has been contributing to Commons tirelessly for nearly 20 years now. His/her at least 110k photos can be seen at Category:Photographs by Anonymous Hong Kong Photographer 1.

A recent example of his/her prolific contribution can be seen at wikimap stats. S/he uploaded at least 7000 (6435 of them geo-tagged) photos of Okinawa this year (it's been only 2 months) alone. In comparison, https://commons.wikimedia.org/w/index.php?search=deepcategory:%222024_in_Okinawa_prefecture%22 "2024 in Okinawa prefecture" has less than 400 files in total. 7k uploads are already quite a lot for any user, but just a fraction of his/her decade-long commitment. As far as I can tell, s/he has been doing so without much attention since 2006.

However, certain users have been targeting this long-term contributor in recent years because of this contributor's unusual habits. Actions they have demanded include but are not limited to: blocking, banning, locking all accounts; deleting all uploads.

As such, I would like to ask the community to help stop such harassment against the long-term contributor. In my humble opinion, anything, other than reasonable inspection of his/her uploads based on com:l, should be stopped. RoyZuo (talk) 07:30, 7 March 2025 (UTC)[reply]

+1 --Achim55 (talk) 07:34, 7 March 2025 (UTC)[reply]
+1 -- C.Suthorn (@Life_is@no-pony.farm - p7.ee/p) (talk) 12:58, 9 March 2025 (UTC)[reply]
Shouldn't respect and non-disturbance be self-evident for every long-term prolific contributor on Commons? --A.Savin 07:54, 7 March 2025 (UTC)[reply]
@RoyZuo: But there is abuse. LuciferianThomas wrote in this Edit Summary: "Intentional wrong-naming files and incorrectly categorising files is clearly abusive behaviour; in scale it is even clearly vandalism". See also m:Requests for comment/Blatant sockpuppetry in good faith.   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 14:09, 7 March 2025 (UTC)[reply]
I recognize Anonymous HK Photographer 1 made a lot of good contributions here, but the problems extends beyond “unusual habits”, many of their uploads have copyright issues. Although this problem only concerns a small proportion of their overall uploads, but since they upload hundreds of images weekly, the problematic uploads pile up to a lot.
I agree with you that the actions demanded above are not suitable, but at the same time I don’t think it is harassment to demand when there are valid concerns. It would be better if you can suggest examples of which specific actions by specific users you think constitutes as harassment. Tvpuppy (talk) 16:05, 7 March 2025 (UTC)[reply]
I salute the anonymous HK user, this can't have been easy. Everyone can make errors, and there are many other ano- and pseudonymous contributors who can eventually fix them. Where there are valid concerns with some of the uploads, we should of course adress that, but overly punitive reactions seem like overkill imo. --Enyavar (talk) 17:14, 7 March 2025 (UTC)[reply]
Cosigning the original post. We do not need yet another case of prolific users being scapegoated and insulted until all eternity, like has happened several times on enwiki. Gnomingstuff (talk) 05:07, 9 March 2025 (UTC)[reply]

Communicating with other users, and changing problematic behavior (like uploading copvios) when notified, are non-optional parts of participating in Commons. Not only does this user not respond on their talk page, nor in DRs and CfDs, it is not even possible to communicate with them because they are constantly changing accounts. They are also violating multiple account policy by failing to link the accounts: Where a user has multiple accounts it is an expectation that they publicly disclose those accounts, usually on each of the relevant user pages providing links to each other. The use of numerous accounts also makes it extremely difficult to track issues like copyvios and improperly named files; however, it is clear that these amount to a non-insignificant proportion of their uploads, and thus add a great deal of work for the community.

I believe a good first step would be a one-account restriction, enforced by technical means as necessary. If the user cannot abide by that extremely basic standard to enable communication and tracking of their behavior, then they are a net negative and do not belong on Commons. No amount of being prolific justifies a user ignoring basic community norms and uploading significant numbers of copyvios. Pi.1415926535 (talk) 22:24, 7 March 2025 (UTC)[reply]

@Pi.1415926535: I agree.   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 23:02, 7 March 2025 (UTC)[reply]
+1 Longterm users shouldn't get a free pass from following the same standards on here everyone else has to just because of how long they have had their account. Its super easy for newish contributors to be sanctioned or blocked over minor non-issues but there's zero consequences for longterm users who don't follow the rules or act abusively. The same goed for admins. Things like repeatedly uploading COPYVIO should be dealt with accordingly regardless of how long the user has been on here or what privileges they have though. --Adamant1 (talk) 23:27, 7 March 2025 (UTC)[reply]
I do not understand how a blatant long-term violator of the Commons:File naming guidelines (Correct – The name should describe the file's content and convey what the subject is actually called. Inaccurate names for the file subject, although they may be common, should be avoided.) is considered a "long-term contributor" by some users above, so apparently people can just upload tons of images and name them incorrectly just to make a mess of Commons to be called a contributor and not an abuser? The large number of files uploaded actually made a heck of a lot more abuse and disturbance to Commons than any other normal user naming files inappropriately. I am very certain that mass contributions does not allow mass disruption and guidelines-breaking in the same scale.
I agree that the upload images are contributions, but the naming of files to an extent of requiring lots of file renamings is definitely abusive editing behaviour, which shall lead to a damning sanction. If RoyZuo insists on calling this abusive user a "contributor" without considering the harm to Commons and unnecessary work to fix all those issues, then I would say they probably did not care about the negatives the abusive user brings, and does not respect the naming guidelines, to a point that they can flat out intentionally cover the intended accused violations and point fingers at the accusers for accusations that we did not make. LuciferianThomas 23:59, 7 March 2025 (UTC)[reply]
I could (but will not) name quite a number of long-term contributors whose work here routinely falls short in one or another respect. I don't see a reason to single out this one. Yes, technically you can communicate with most of the others, but in practice? If they ignore all comments, or brush them off, the result is the same as if there were no channel of communication. - Jmabel ! talk 00:44, 8 March 2025 (UTC)[reply]
I personally do think we need to be more strict about that sort of editor in general. In this specific case, the use of multiple accounts makes it easier for this editor to avoid scrutiny - it would require a great deal of work to determine how many of their uploads have been deleted, or if they have ever been blocked, because the contributions are spread over dozens of accounts. (If any of the accounts have ever been blocked, then this is block evasion, pure and simple.) It also means that the editor likely has not even seen DR and CfD notices because they abandon accounts after using them once, so they may not be aware of the hundreds of copyvios they have uploaded. Forcing them to use a single account would put them on the same footing as every other editor and allow the community to address their issues with file naming and copyvios. Right now, the community has no ability to even address their behavior because of the account-hopping. Pi.1415926535 (talk) 01:14, 8 March 2025 (UTC)[reply]
It's never the actual issue that's the problem. It's pointing out the issue that's the problem. someone can harass you on here all day and no one will bat an eye about it. But then you can be blocked for intimidation if you dare to point out that's what they are doing. The priorities on here are just screwed and it's always an endless exercise in pandering to seniority. --Adamant1 (talk) 01:12, 8 March 2025 (UTC)[reply]
I would say both are problems as important as the other. The long-term disruption pattern shows the inability of the Commons administration to "see what the problem is" and to enforce the very rules of Commons, and the counter-accusation of harassment or intimidation by those who think such abuser is a contributor shows the inability of such users and the Commons administration to care about the actual issue instead of pointing fingers at those who raise a problem. LuciferianThomas 02:14, 8 March 2025 (UTC)[reply]
You're allowed to call this person something other than an "abuser," you know. It will not kill you to treat them like a human being. Gnomingstuff (talk) 03:25, 10 March 2025 (UTC)[reply]
You can keep on ignoring the abuse. It's clearly within my right to call this anonymous user an abuser for his blatant violation described below. LuciferianThomas 11:00, 11 March 2025 (UTC)[reply]
And in return, "it will not kill you to actually care about what is actually happening and not just blaming the one who points out a real issue, whether you like it or not." LuciferianThomas 11:08, 11 March 2025 (UTC)[reply]
Link to evidence of "blatant long-term violator of the Commons:File naming guidelines".
Otherwise, I consider the accusation as invalid and personal attack against the long term anonymous contributor. RoyZuo (talk) 21:54, 10 March 2025 (UTC)[reply]
For the fact that I had only gone through 5 of 98 MTR stations in Hong Kong to move over 50 instances of incorrectly named files and incorrect categorisation for MTR stations? At this rate, there's probably thousands of files misnamed and miscategorised from this user just for the files uploaded for MTR. This is blatant violations and circumventing anti-abuse. LuciferianThomas 10:59, 11 March 2025 (UTC)[reply]
"the fact that I... move over 50 instances"
  1. https://commons.wikimedia.org/w/index.php?title=Special:Log&type=move&user=LuciferianThomas&wpFormIdentifier=logeventslist&wpfilters%5B0%5D=newusers 22 move logs.
  2. https://commons.wikimedia.org/w/index.php?title=Special%3AContributions&target=LuciferianThomas&namespace=all&tagfilter=RenameLink&limit=50 7 edits
As of 17:08, 11 March 2025 (UTC), you have a total of 22+7=29 edits related to renaming any files by the long term contributor.
Is 29 even close to 50?
So you are making up "fact" and misleading the entire Commons community with exaggerated accusation against the long term contributor. It should be noted that you have repeatedly exaggerated this accusation since early 2024. In your own words, such repeated misleading actions are abusive and should lead to blocking of your account.
And this is only 1 single problem of your many similar accusations. RoyZuo (talk) 17:08, 11 March 2025 (UTC)[reply]
I definitely said "incorrect files and incorrect categorisation", but I guess you are just blindsided to the side of the fact you believe in. I might have miscounted moved files, but I have definitely removed hundreds of miscategorised images – pictures of shops (within the station) in the focus, or even their products, instead of the actual station. You tell me this is an image of Po Lam Station? Yes the picture might be taken in Po Lam Station, but it's absolutely nonsense to say it's a picture of Po Lam Station.
Heck, even 29 misnamed instances of say 600 images is a 5% mistake rate, not to mention all the other images that are miscategorised to the level of nonsense. If any editor makes so much mistakes in their editing, how is that not even disruptive? I won't call 22 images of cakes, Mrs Fields cookie products, convenience store products to be "contribution to a station category" – it tells nothing about the actual station.
Your repeated negligence to the actual happenings of the case, making up what I say when you just didn't read, and making up "facts" to mislead the entire Commons community with exaggerated accusation of harassment without caring for the actual disruption is clearly abusive behaviour and should lead to the blocking of your account here on Commons, just like you have been in three other wikis. LuciferianThomas 00:31, 12 March 2025 (UTC)[reply]
Oh btw, the linked image is geotagged in LOHAS Park station. Guess that's an extra count of misnaming images, heh? LuciferianThomas 00:33, 12 March 2025 (UTC)[reply]
"At this rate, there's probably thousands of files misnamed and miscategorised from this user just for the files uploaded for MTR"
there are roughly 3600 files related to MTR https://commons.wikimedia.org/w/index.php?sort=create_timestamp_desc&search=MTR+incategory%3A%22Photographs+by+Anonymous+Hong+Kong+Photographer+1%22 .
Either you can prove your extrapolation, or it should be considered as nothing more than just another exaggeration and personal attack. RoyZuo (talk) 01:16, 12 March 2025 (UTC)[reply]
And you now admitted that you had removed photos taken in a train station from a category under that train station: that is definitely violation of policy Commons:Categories#Types_of_reflected_relations.
Here is 1 such violation of policy by LuciferianThomas https://commons.wikimedia.org/w/index.php?diff=952770572&oldid=715233481 which removed the file from anywhere under Category:LOHAS Park Station, its location of creation (P1071).
Then you made the false accusation of incorrect categorisation against the original uploader and also exaggerated your accusation. RoyZuo (talk) 02:18, 12 March 2025 (UTC)[reply]
And also Commons:Village_pump/Archive/2024/01#Problematic_file_names_and_irrelevant_categorization_by_sockpuppet_group, issue has been detailed before. You can keep pretending that this has not been talked about before, and dismiss my accusations against the abuse, but you will not change the fact that there is indeed abuse, and that the abuse causing widespread inaccuracies in Commons. Heck, you can even keep promoting this behaviour as contribution or "not a serious problem", but this will only show that you don't really care about the truth. LuciferianThomas 11:05, 11 March 2025 (UTC)[reply]
And whether you like it or not, sockpuppetry is clearly a violation anywhere on Wikimedia. From the start, you are supporting sockpuppetry, and it doesn't really matter who was abusing socks. I personally never asked for files to be deleted, I would only ask for a block on sockpuppetry to prevent further disruption, and if they are willing to contribute by the rules (especially for content accuracy and sockpuppetry), I'm more than happy to see further contributions from the user. However before then, sockpuppetry and disruption by inaccuracy is a big fat no from my stance. LuciferianThomas 11:13, 11 March 2025 (UTC)[reply]
Ah, one supports like. Not to paint a bad picture on RoyZuo, but being blocked in two wikis for uncivil behaviour and IDHT respectively doesn't seem to have stopped them from failing to actually get the point yet again. I won't dismiss what they say by their past history, but I will dismiss it for the fact that it is negligent the truth and accusative against the ones who actually care about accuracy and compliance. LuciferianThomas 11:23, 11 March 2025 (UTC)[reply]
Commons:Administrators'_noticeboard/User_problems/Archive_110#RZuo, and it clearly isn't this user's first time defending the disruptive anonymous photographer with actions that do not comply to rules. Why would they now be caring about the truth? They won't. LuciferianThomas 12:00, 11 March 2025 (UTC)[reply]
Just quickly skimming through Category:Yau Tong Station: I have already spotted 3 more files that are mislabeled, and are in fact taken in Tiu Keng Leng station. I guess here's your evidence? LuciferianThomas 11:57, 11 March 2025 (UTC)[reply]
If anyone tries to argue that Yau Tong and Tiu Keng Leng stations are easily mistaken for their similar livery, this is one example of the anonymous photographer labeling things completely and impossibly wrong. LuciferianThomas 12:03, 11 March 2025 (UTC)[reply]
+1 I don't think this contributor is a "net negative" for the project, but the issues he's causing are difficult to track because they are spread over literally hundreds of different (non-disclosed) accounts, and he is impossible to communicate with, and those are both problems. Enforcing a one-account policy restriction (with small carve-outs for things like disclosed alts or pseudonyms maintained for safety reasons) seems more than reasonable to me. ReneeWrites (talk) 10:13, 9 March 2025 (UTC)[reply]
I do not understand at all why RoyZuo brought up this issue as an alleged supporter of the anonymous photographer. This was debated almost everywhere because someone was really busy to get the anonymous photographer blocked or globally locked for socking by whatever means possible. There were two unsuccessful attempts on Commons to have the photographer blocked. The latest ate issue was also ported to Meta, meta:Requests for comment/Blatant sockpuppetry in good faith, where the request was recently denied. I really think that this should stop now, unless someone thinks that yet another attempt at Commons:Administrators' noticeboard/User problems might have a different outcome. --Robert Flogaus-Faust (talk) 11:19, 10 March 2025 (UTC)[reply]
@Robert Flogaus-Faust the hostile actions against the user are succeeding and files are blindly massively deleted Commons:Requests for checkuser/Case/Anonymous Hong Kong Photographer 1.
It takes 1 sysop to give in to the relentless harassment and delete all the files, but it will take many more users' collective effort to fend for the contributor and their contribution, because they never dispute the attempts at deletion or defend themselves.--RoyZuo (talk) 22:03, 10 March 2025 (UTC)[reply]
Then so be it. It is obvious that the anonymous photographer's socking without disclosure of the other accounts is not according to the rules, even though this had been tolerated for some time. The reason for the mass deletion is that there are FoP issues with many of the files. --Robert Flogaus-Faust (talk) 11:47, 11 March 2025 (UTC)[reply]
@Pi.1415926535 "They are also violating multiple account policy..."
that's not a policy, but merely an article, a write-up https://meta.wikimedia.org/w/index.php?title=Sock_puppetry&action=history .
all the policies (on meta) are here meta:Category:Policies. that page you quote is not part of them. RoyZuo (talk) 19:30, 11 March 2025 (UTC)[reply]

Those alledged issues with "massive uploading of copyvios" etc seem to be massively overstated. First of all, these issues are not "these photos have been stolen from some photo agency and are falsely claimed own work" as it appears to being framed, but only FOP, where the uploading does not violate any copyright laws, only Commons policy which does not allow restrictions on commercial use. Then, the people who regularly nominate massive amounts of images uploaded by this person seem to be unwilling to use VFC for their mass nominations, which makes proper review of those DRs an incredible pain. Just a week ago I spend over AN HOUR copy-pasting keep under over 250 DRs, where the nominator apparently carelessly misinterpreted some FOP law (while reviewing them even longer before, and this is a pain when the files are in 200 seperate DRs instead of one or a handful). Those +250 (!!!) DRs have all been kept. The people witchhunting this anonymous guy keep creating massive numbers of questionable DRs, where commenters are unable to keep up with - most of the DRs have no comments as it is de facto impossible to properly review and comment on all of them. Also, many of the "issues" claimed at Commons:Requests for checkuser/Case/Anonymous Hong Kong Photographer 1 like "Using strange names in accounts.", "User pages only created as galleries." or "Indirect disclosure of personal information." are such non-issues to the point that they are laughable. Points such as a single instance of "Intentionally removing sockpuppetry tags." where it is zero indication that this was intentional, or "Systematic, but inconsistent categorization." with zero source, feels like "I just don't like that" instead of being based on any policy whatsoever. ~TheImaCow (talk) 00:46, 11 March 2025 (UTC)[reply]

@User:Krd has aparrently just casually deleted thousands of files uploaded by this anonymous person with the reason "created by abuser", without any consideration for anything. Where exactly is this mentioned as a valid reason at Commons:Deletion policy and how isn't this an act of massive vandalism? ~TheImaCow (talk) 00:58, 11 March 2025 (UTC)[reply]
I browsed through a good percentage of their files laat night and a lot of them had FOP issues. Its pretty clear that isn't something they know or care or about. Regardless, its super unrealistic to expect other users to sift through and nominate their uploads for deletion. Especially given the sheer amount of socks. That's on them for using so many alts and not following the guidelines on a basic level. --Adamant1 (talk) 01:14, 11 March 2025 (UTC)[reply]
okay, and I just browsed to some random of their galleries at User:Gindcheoutarkoadf_OK, User:GISTZIS rAhsueLLS pxwomc, User:GEEHAWUMENKIN 106, User:GAUAI Shfj 992833 --- +1000 images, maybe five where I'd say "not FOP compatible", ~15 redlinked images, none of the DR's I checked had any comments. Perfectly acceptable rate. ~TheImaCow (talk) 02:04, 11 March 2025 (UTC)[reply]
I'd keep the images of food myself. All the ones of store signs, packaging and the like are probably copyrighted though. Not to mention there's SCOPE issues with a lot of their photographs. I really don't see how most of the images don't go against the whole "must be realistically useful for an educational purpose" thing.
I forget where it is right now, but one of the policies says something about someone's personal vacation photos not being educational. That's essentially what these photographs are. 25 random, mundane shots of a hotel room the guy was staying at. Realistically how many photographs of a slept in hotel bed do we need on here? They are just using Commons as a personal file hosting site at that point. It would be a super pedantic time waster to separately nominate all of those images for deletion. --Adamant1 (talk) 02:19, 11 March 2025 (UTC)[reply]
I mean, there are also a ton of photos of items in shops in MTR stations. I have absolutely no idea what the photos are even trying to express for some of them, not to mention the other disruptive bad naming and categorisations. LuciferianThomas 13:30, 11 March 2025 (UTC)[reply]

Larger version is 180° rotated

When I click on File:Exterior del Museo.png to see the enlarged version the image has been rotated by 180°. How to solve that? Wouter (talk) 12:37, 7 March 2025 (UTC)[reply]

@Wouterhagens: Rotate it again locally. https://upload.wikimedia.org/wikipedia/commons/6/60/Exterior_del_Museo.png looks fine to me on the latest Chrome and Windows 10.   — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 14:12, 7 March 2025 (UTC)[reply]
@User:Jeff G.: Thanks. I experienced the problem with Firefox and to my surprise not in Safari. Wouter (talk) 18:54, 7 March 2025 (UTC)[reply]
This general happens when there is conflicting rotational information in the metadata of the files. One type of metadata says one thing, and the other metadata says the other thing. —TheDJ (talk • contribs) 12:51, 10 March 2025 (UTC)[reply]

Decade by category navbox

This needs editting so things like Category:Cross-country skiing in the 1900s go into a subcategory, not into Category:1900s Rathfelder (talk) 13:35, 7 March 2025 (UTC)[reply]

I changed the template so it is now in the “Sports in the XXXXs” category instead. Tvpuppy (talk) 13:47, 7 March 2025 (UTC)[reply]
Thank you. There are a lot of similar issues. Is this the place to ask them to be fixed? Rathfelder (talk) 09:56, 8 March 2025 (UTC)[reply]
Yes, usually for most you can do it here. If the page is using a template, you can go to the template discussion page instead. Tvpuppy (talk) 13:07, 8 March 2025 (UTC)[reply]

Please can someone look at the templates for Category:1910s political cartoons of the United States, Category:Microphones in the 1910s, Category:Science fiction in the 1910s, and Category:Home kitchens in the 1910s and take them out of Category:1910s? Rathfelder (talk) 10:01, 8 March 2025 (UTC)[reply]

Overcategorization like that is a pretty common issue for these types of templates unfortunately. At least IMO categories should just be added manually without the pointless navbox or there should at least be an approval process. By date templates are more trouble then they are worth at this point though. --Adamant1 (talk) 10:05, 8 March 2025 (UTC)[reply]
I’m looking into it. Will try to fix each of them. Tvpuppy (talk) 13:07, 8 March 2025 (UTC)[reply]
@Rathfelder Now they should be all fixed. Let me know if I have missed anything. Tvpuppy (talk) 15:54, 8 March 2025 (UTC)[reply]
I think that's it - for now, at least. Thank you very much.
One other question: English wikipedia has a very useful template {{Navseasoncats}}, but it doesnt work here. Is there an equivalent, or could one be made? Rathfelder (talk) 16:04, 8 March 2025 (UTC)[reply]
It would be very useful here, but to my knowledge, there isn’t an equivalent. One could be made, but that’s outside of my technical abilities. Tvpuppy (talk) 19:13, 8 March 2025 (UTC)[reply]

Universal Code of Conduct annual review: proposed changes are available for comment

Please help translate to your language.

I am writing to you to let you know that proposed changes to the Universal Code of Conduct (UCoC) Enforcement Guidelines and Universal Code of Conduct Coordinating Committee (U4C) Charter are open for review. You can provide feedback on suggested changes through the end of day on Tuesday, 18 March 2025. This is the second step in the annual review process, the final step will be community voting on the proposed changes. Read more information and find relevant links about the process on the UCoC annual review page on Meta.

The Universal Code of Conduct Coordinating Committee (U4C) is a global group dedicated to providing an equitable and consistent implementation of the UCoC. This annual review was planned and implemented by the U4C. For more information and the responsibilities of the U4C, you may review the U4C Charter.

Please share this information with other members in your community wherever else might be appropriate.

-- In cooperation with the U4C, Keegan (WMF) 18:50, 7 March 2025 (UTC)[reply]

March 08

Clothing by date

Category:Clothing in 1957 - and later dates are this way round. Category:1899 clothing and earlier dates are the other way round. Wouldnt it be nice if they were all the same way round? Rathfelder (talk) 22:39, 8 March 2025 (UTC)[reply]

The proper name should be “Clothing in XXXX”, so I have renamed the categories for 1899 and before. Tvpuppy (talk) 23:44, 8 March 2025 (UTC)[reply]

March 10

Theatre by year

Could anyone make some new templates for other countries like the one for Spain? Category:Theatre of Spain by year? Rathfelder (talk) 13:46, 10 March 2025 (UTC)[reply]

I will try to see if I can make one. Do you mean a template for “Category:Theatre of X by year” itself or its subcats i.e. “Category:YYYY in theatre of X”? Tvpuppy (talk) 15:27, 10 March 2025 (UTC)[reply]
I created a template for “Category:YYYY in theatre of X”, see {{Theatre of country by year}}. In theory, it should work for any country and any year, without adding any parameters. See Category:1936 in theatre of Spain for example. Tvpuppy (talk) 16:59, 10 March 2025 (UTC)[reply]
That's great! Thank you. Rathfelder (talk) 19:17, 10 March 2025 (UTC)[reply]
@Rathfelder I also finished making {{Theatre of country by decade}} for the decade categories “Category:Theatre of X in YYYYs”. It should also work without parameters, see example at Category:Theatre of the United States in 1910s. Tvpuppy (talk) 17:59, 11 March 2025 (UTC)[reply]
Just what I need! Rathfelder (talk) 18:01, 11 March 2025 (UTC)[reply]
@Rathfelder I have just finished {{Theatre of country by century}} for the century-categories. It works the same as well. Tvpuppy (talk) 19:22, 11 March 2025 (UTC)[reply]
That is really helpful. Speeds things up no end - and I dont have to worry about miss clicking! Thank you very much. Rathfelder (talk) 20:25, 11 March 2025 (UTC)[reply]

Wishlist for new features on Commons

Hi!

I invite you to join the wishlist of proposals for new functions on Commons. The focus lays on the support of colored meshes, which is highly requested and elemental for future media, and the support for DNG files to be archived. Several additions have also positive influence on sister projects like Wikipedia. We're happy to see you there :) --PantheraLeo1359531 😺 (talk) 16:26, 10 March 2025 (UTC)[reply]

"AutoCats" script for automatic categories

Please check out the new user script AutoCats - it attempts to provide a solution for what I think has long been a sticking point in Commons: the lack of translation for category names. Any feedback is welcome! Yaron Koren (talk) 16:32, 10 March 2025 (UTC)[reply]

March 11

Possible mass upload of Trump-sensitive photos

Hi! In Denmark there are news reporting that Trump is trying to eliminate lots of photos that contain "sensitive" words. So Gay, Trans and Equity for example.

The story in Denmark is that it also affect Category:Enola Gay because of the word "Gay". And story also tells that people try to avoid words that include "trans" so for example "transaction" and "Equity" even if the meaning is w:Equity (finance).

I do not know if it is actually true but if it is true then I wonder if someone can do some magic and mass upload files to prevent them from being deleted. MGA73 (talk) 11:00, 11 March 2025 (UTC)[reply]

Presumably you refer to works of the US Federal government. Such works are commonly bulk-uploaded here anyway; have you found any sets that are not? Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 18:00, 11 March 2025 (UTC)[reply]
Correct works of US Federal government. No, I have not found any good sets. I just thougt it would be good if "everyone" helped out. --MGA73 (talk) 18:03, 11 March 2025 (UTC)[reply]
Commons have un million files from Department of Defense (DoD): 300 000 from Fæ, 300 000 from OptimusPrimeBot (which is still uploading new files) and 400 000 from different uploaders. DVIDS, the wikicommons of DoD contains 5 millions pictures.
I've created a cat to identify files deleted by DoD: Category:Images removed from DVIDS. Pyb en résidence (talk) 19:08, 11 March 2025 (UTC)[reply]
Pyb en résidence's new category also includes a list of deleted files from the AP's recently published database of deleted DVIDS files -- is anybody working on bulk uploading those links from that database that do work? Is there anything other Wikipedians can do to help? -- Gaurav (talk) 23:38, 11 March 2025 (UTC)[reply]
I'm using Openrefine to categorize uploads by Fæ based on the AP database. Don-vip is categorizing OptimusPrimeBot uploads with a deadlink to DVIDS. It's not perfect because some files might be delete for another reasons than anti-DEI. Pyb en résidence (talk) 08:25, 12 March 2025 (UTC)[reply]

Categories under Category:FoP-Switzerland

The categorizations of many categories here are problematic. Supposedly, {{FoP-Switzerland}} should not be used in categories of specific artworks and buildings, as country-specific templates are meant for file namespace only. Moreover, the categories of several artists were slapped with this template, making the categories ending up categorized under this category. It isn't correct to tag the artists' categories with this template, as the artists may have made artworks located in countries with no liberal panorama exceptions. I suggest using {{FoP-category}} for categories of Swiss works themselves, and removing the FoP tag from the categories of artists ({{NoUploads}} suffices). Since there are 700+ categories under Category:FoP-Switzerland, manual fixing of the categories is impractical. I hope there's "VisualCategoryChange" that can custom replace some content of multiple categories at once. JWilz12345 (Talk|Contributions) 12:33, 11 March 2025 (UTC)[reply]

  •  Support I've never really been a huge fan of people adding licensing templates to categories myself. They should really only be used on files. Feel free to ping me when (or if) this is approved and maybe I can help clean some of it up. --Adamant1 (talk) 08:55, 12 March 2025 (UTC)[reply]

March 12

"Winners of [Award]" vs "[Award] winners" categories

Which formatting should be used for these categories? I noticed that Blackcat has moved many of these categories from "[Award] winners" to "Winners of [Award]" over the years. Category:BAFTA Award winners to Category:Winners of the BAFTA Award, for example. — Preceding unsigned comment added by Οἶδα (talk • contribs)

Retrieved from "https://commons.wikimedia.org/w/index.php?title=Commons:Village_pump&oldid=1008720611"