Commons:Village pump/Archive/2026/10
| This is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page. |
Vandalism
Sorry, I don't know how to create a vandalism report. Someone added a deletion request at the Picture of the Day: Revision of 1282505058. It's vandalism. Please remove the deletion request. I've asked the same in the German vollage pump. Thank you. -- XRay 💬 05:29, 5 October 2026 (UTC)
- Sorry, I didn't know I could remove the request myself. I thought the write protection applied to me as well. So that's taken care of. Thanks anyway! -- XRay 💬 05:31, 5 October 2026 (UTC)
- This section was archived on a request by: --XRay 💬 06:07, 5 October 2026 (UTC)
Linking scans of Audubon and Gould plates to their Wikidata items
Every plate of Audubon's Birds of America (Havell edition) and of Gould's Birds of Europe, Australia, Asia and Great Britain now has its own Wikidata item (see d:Wikidata:Dataset Imports/Historical bird plates). I'd like to link about 1,050 existing scans on Commons to those items, adding digital representation of (P6243), depicts (P180) and main subject (P921), each pointing to the plate item, following Commons:Structured data/Modeling/Visual artworks. Every match is by BHL page, scan leaf or printed plate number. Crops, facsimiles and uncertain matches are left out. A 20-file pilot is done (batch 285175). I plan to run the rest with QuickStatements in small chunks over a day or two. Objections or suggestions are welcome. Wells.riley (talk) 00:36, 1 October 2026 (UTC)
- For any that already use {{Artwork}} or {{Art photo}}, it would be good to get the Wikidata item number into the appropriate field of the template as well. - Jmabel ! talk 09:45, 1 October 2026 (UTC)
Uploading photos from an Iphone is a pain
Hi there, When trying to upload multiple photos from my Iphone, I get the impression the upload wizard is becoming increasingly flaky. The usual workflow for me has become to select photos that go together with a subject in the Iphone photos app, place them in a (temporary) album, open the Iphones native Safari browser, go to Commons, open the upload wizard and go through the motions there. The first bit works.. OK-ish. I would be very happy if there would be a way to set a preferred language when adding captions, but besides that it is fidgetty is sort of works. However things go wrong when uploading more then a few (<4) images. Either only a few files make it through the publishing, even though all uploads succeeded and got the green check, or actually the upload wizard breaks off altogether, and I need to restart all the work including the file naming, description, wikidata tagging etc. This is a pain. It does not appear there are any up to date apps to do this, but even the basic uploader fails. Any other ideas for workflows? Apps? Milliped (talk) 16:48, 1 October 2026 (UTC)
- There are other tech problems (unrelated to iphones) right now, like displaying negative number of entries in categories - perhaps a sitewide snafu. Retired electrician (talk) 18:54, 1 October 2026 (UTC)
- This is what keeps me loyal as an Android user. Uploading from Android through Upload Wizard is similarly complex, annoying, and unreliable. However, the Android Wikimedia Commons App is the opposite, providing easy forms to fill out, and making reasonable guesses to some of the blanks in the form. If I didn't have that, I would still dodge the Wizard by using WikiShootMe, though that's not anywhere as good as the Android app. Jim.henderson (talk) 19:17, 1 October 2026 (UTC)
Can anyone find it?
I want to create a Category for this newspaper, but can't find an entry in Wikidata to get an infobox: Pass Observer (1960-1963) SN 97069663 1960-[1962]. I thought all newspapers with SN numbers were loaded in the past? Can anyone find it? --RAN (talk) 16:58, 2 October 2026 (UTC)
- I just made Pass Observer (Q141625275) (Pass Observer), didn't seem like it existed already... Arlo James Barnes 19:54, 2 October 2026 (UTC)
- Thanks! --RAN (talk) 01:30, 3 October 2026 (UTC)
Where is the October historical buildings challenge?
There was a banner yesterday about picturing buildings of importance (or something like that) throughout October but I can't find it. Julvsel (talk) 21:43, 2 October 2026 (UTC)
Are the categories in “Pub signs by subject” and “Inn signs by subject” different, or should they be merged?
.jpg/250px-Schwäbisch_Hall_-_Altstadt_-_Weiler_-_Im_Weiler_2_-_Wirtshausausleger_(RQCE7578).jpg?utm_source=commons.wikimedia.org&utm_campaign=parser&utm_content=thumbnail)
Hi there, I just stumbled over two (possibly) overlapping groups of categories: Category:Pub signs by subject and Category:Inn signs by subject, both of them with quite some subcategories. I understand that a pub is not the same as an inn. But looking at the images in these categories I get the impression that users do not really distinguish between pubs and inns when they add such categories, but just use either subcategories of Category:Pub signs by subject or of Category:Inn signs by subject, depending on which group of categories they discovered first.
Therefore my question, especially to native speakers of the English language. Is it necessary to keep these two kinds of categories separate? (Then we would have to sort images carefully into the right subcategory, depending on whether each sign belongs to a pub or to an inn. Not easy: often former inns are just pubs today.) Or do you agree with my impression that these categories are not really different, but that the distinction is rather accidental? Then we should consider to unite these categories. In the latter case I ask native speakers to explain which names are better and should be used for the united categories.
Hint: I have reported this here and not on Commons:Categories for discussion because this is not a category deletion request etc. I just want to open an informal discussion in order to clarify the situation. Only if people agree that we need action a formal category discussion should be opened.
Thank you and all the best, – Aristeas (talk) 14:52, 1 October 2026 (UTC)
- As you allude to, but do not state, an inn, properly speaking, offers beds for the night. If you go back a couple of centuries it didn't even necessarily offer proper rooms, but did offer beds. (The Spanish posada is similar, as is the Romanian han; I couldn't vouch for other languages.) Many historic inns are now pubs, and many of those retain "inn" in their name. Also, some places that were never really inns have "inn" in their name. Nowadays, when used for an actual hostelry, the name can still carry a bit of a rustic connotation, but that's been really undercut by its use in the names of some hotel and motel chains (Holiday Inn, Hilton Garden Inn, Radisson Park In, etc.) so it's gotten really muddy, especially in the last 75 or so years.
- Still, there are definitely places that are well categorized as "inns" that are in no sense pubs: National Park Inn at Longmire, Washington in Mount Rainier National Park; Old Faithful Inn in Yellowstone National Park; Hobo's Inn in Elbe, Washington; Red Lion Inn in Stockbridge, Massachusetts; I'm guessing that is enough to make the point. - Jmabel ! talk 16:51, 1 October 2026 (UTC)
- I did not discuss the difference between inn and pub because I wanted to leave this to native speakers. Thank you very much for explaining it! – However, please note that I do not propose to merge all inn and pub categories; I just refer to the categories about inn signs and pub signs. AFAICS for these signs the difference between pubs and inns is not that important and often difficult to establish – as you say, “[m]any historic inns are now pubs”, etc. So often a sign says “... inn”, but inside you will find a pub. In cases like that one it’s difficult to say to which category a photo of the sign belongs (the sign is about a former inn, but it belongs to a pub, etc.). This is why I think about merging the categories for inn and pub signs. – Aristeas (talk) 11:52, 2 October 2026 (UTC)
- I would support merging these categories, as well as the analogous Category:Inn signs by country and Category:Pub signs by country. The distinction between an inn and a pub is quite slight, and is not at all relevant if all you're looking at is the sign. Omphalographer (talk) 16:51, 1 October 2026 (UTC)
- I don't think they should be merged, though a fair number of signs belong in both, and I think it is harmless if a few end up classified as "inns" as well as pubs on nothing more than their name. Remember, Commons categorization is primarily about helping people find things, not about ontology.
- As for why not merge: a sign for the National Park Inn at Longmire, Washington is in no sense a pub sign and (to keep it in the same region) a sign for the George and Dragon in the Fremont neighborhood of Seattle is in no sense a sign for an inn. - Jmabel ! talk 14:28, 2 October 2026 (UTC)
- Would merging both into Category:Pubs and Inns by subject under Category:Pubs and Inns satisfy everyone? — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 16:03, 2 October 2026 (UTC)
- Maybe I'm in a cranky mood (because why should I have three issues with something so simple?) but:
- Why the capitalization of "Inns" (or was that just an oversight)?
- Normally, we try to avoid union categories. To take examples I gave above, why would File:Fremont, Seattle - The George and Dragon 01.jpg the George and Dragon in Fremont, Seattle (in no sense an "inn") and National Park Inn at Longmire (in no sense a "pub") belong at all in the same conflated category?
- This one might be just me but: I hate those "by subject" cats. It's like "for some reason based on a cat name that you may or may not know, some of the subcats here are buried a level down." I know Commons well enough that I can make good guesses what might be there, but I don't see how we expect that of end users.
- Jmabel ! talk 11:54, 3 October 2026 (UTC)
- Re. part 2: I don't think the category is meant to encompass all signage on pubs/inns, only the specific type described at w:en:Pub sign. Neither of the places you identified has a pub sign, just an ordinary printed sign.
- Re. part 3: in this case, "by subject" means "grouped by the thing depicted on the sign", e.g. Category:Pub signs depicting foxes. As a separate matter, though, some of the geographic/subject cross-categorizations are a bit much, e.g. Category:Pub signs in the West Midlands (county) depicting birds. Omphalographer (talk) 17:26, 3 October 2026 (UTC)
- Maybe I'm in a cranky mood (because why should I have three issues with something so simple?) but:
- Would merging both into Category:Pubs and Inns by subject under Category:Pubs and Inns satisfy everyone? — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 16:03, 2 October 2026 (UTC)
Hi, I thought we have a bot closing the nominations, but there are many waiting to be closed. Yann (talk) 18:41, 3 October 2026 (UTC)
- Hello, I have now manually closed all the nominations that have already ended. Just letting you know, the bot hasn't been working for several years, and FM nominations needs to be closed manually. Also, the previous FMC maintainer stopped maintaining at the beginning of this year. Currently, we still don't have a regular FM maintainer, so the FM closing work were being picked up by several users here and there. That is why the nominations are being closed somewhat irregularly. Thanks. Tvpuppy (talk) 00:40, 4 October 2026 (UTC)
Png background displaying black instead of white
See: Category:Alfred_Naess. Am I just seeing it, or do others? RAN (talk) 19:07, 3 October 2026 (UTC)
- @Richard Arthur Norton (1958- ): is this about File:Alfred Ingvald Naess circa 1900 with removed background.png (which shows black for me) or something else? - Jmabel ! talk 21:59, 3 October 2026 (UTC)
- Yes, I know websites have png clear layer default to either black or white, most default to white. When I look at the png directly it is white, but in the infobox it is defaulting to black. Are you seeing the image at Commons defaulting to black, or only the version in the infobox catgory? I wonder if it was an error in the creation of the thumbnail? I think I would have noticed the problem years ago. --RAN (talk) 22:41, 3 October 2026 (UTC)
- I use dark mode on Commons, so it looks dark grey to me. Arlo James Barnes 19:38, 4 October 2026 (UTC)
- Looks like it is now back to white. --RAN (talk) 22:45, 3 October 2026 (UTC)
I noticed a newly created {{Lolicon}} template that was seemingly created as a content disclaimer. It is worth noting that templates such as {{Pornography}} and {{NSFW-art}} have been deleted due to their vagueness and the fact that the general disclaimer already covers them. However, lolicon media is seemingly more controversial (see discussion), so this template might have some merit. I'm not really a template guy, so I decided to post it here to discuss the template. I previously posted here when discussing the {{NSFW-art}} template, so this seems like the right place for discussion (isn't really a proposal or copyright related).
Pinging template creator @Ahri Boy.
Edit: Some more info: the template is currently used on one file (File:Stability Matrix Inference in action.png), there is also Wikimedia Commons content descriptor (P14416) for flagging explicit content. Dabmasterars [EN/RU] (talk/uploads) 04:12, 5 October 2026 (UTC)
- I saw this posted here and had a question. It seems that this template may only cover around four or five files that are currently hosted on all of Commons.
- My question is, since this template would cover such a low amount, is it even needed? And if it is, could/should it even, also cover general child nudity? Issac I Navarro (talk) 05:20, 5 October 2026 (UTC)
- The template is factually wrong. The law is not defined this way in all these countries. It's very unlikely that making statements about what is "illegal" would be helpful and could be misleading. Fæ (talk) 16:00, 5 October 2026 (UTC)
- FYI the Dabmasterars account was WMF locked on 6th October. Fæ (talk) 10:32, 6 October 2026 (UTC)
Category emptying
- IMO contributors should never move all the files from a category, then call for the deletion of the category they emptied, because it is now empty...
What should contributors do if they encounter a category they think is poorly named, or which contains content they believe belongs elsewhere?
Some people will go through every item in that category, one at a time, removing the category they don't like, replacing it with a new category. And then they make the terrible mistake of placing a speedy deletion tag on the category they just emptied. Yes, a category that NEVER had any contents should be eligible for speedy deletion. A now empty category, that only had contents for a short amount of time, should also be eligible for speedy deletion. But, categories that had contents for a meaningful amount of time should be redirected to the category where their former contents were moved.
We have two choices of procedures for this. The observant contributor can place a {{Move}} tag, in the category, with a brief explanation as to why it should be moved. Or they can click on the button to start a discussion on the category. Both choices leave a heads-up for the person who started the category. Even when no-one weighs in at the discussion they opened, following one of these two choices is extremely importantː
- The discussion establishes a documented trail of what is going on.
- We are all fallible. Providing an opportunity for others to weigh in may show the concerned contributor good reasons why the original categories were the right categories, all along.
- If the administrator who closes the discussion concludes the consensus is to move the files, they initiate a robot to do the move. This saves a lot of human effort, and is not subject to human fallibility.
- A redirect is then automatically left in the now empty category. As above, this redirect is essentialː
- Commons images are served to lots of non-WMF projects. There is no mechanism to know which files and categories are being used under their original names on those non-WMF projects.
- Commons users are pasting the URLs to files and categories in the emails, in their academic papers, on their web pages.
Cheersǃ Geo Swan (talk) 12:09, 5 October 2026 (UTC)
- Absolutely agreed. Andy Dingley (talk) 14:19, 5 October 2026 (UTC)
- I'm fine with (most of) this if any of the relevant work has been done by an established user but:
- To take an extreme case, if some temporary account comes along and creates Category:Sexy, I don't want to have to go through all this to undo it.
- Also, are you saying all of this needs to be done even for obvious typographical errors? VfC is generally quite backlogged.
- When you say the admin must "initiate a robot to do the move": no, that does not save human effort compared to moving the category in the normal manner and then moving the contents with Cat-a-Lot. I see no reason in the world to have to go through Commons Delinker for this: it often has a significant backlog and it has been known to stall out for days.
- Conversely, I've been very unhappy recently with a user I will refrain from naming who in the last month has unilaterally moved over 100 categories I created with absolutely no consultation, and sometimes over my explicit objection (though I don't think he has deleted the cat redirects). - Jmabel ! talk 16:17, 5 October 2026 (UTC)
- What's the average waiting time for a {move} request? A year would be conservatives I'd say. Not a pleasant option. Little wonder that editors are tempted to take shortcuts. The principles outlined are all very high minded, but until realistic resources are behind them, they are just a recipe for sclerosis inaction. Laurel Lodged (talk) 17:01, 5 October 2026 (UTC)
- I think you chose Category:Sexy as an obviously worthless category. Is it?
- Is Category:Sexy full of images uploaded by the same new user who created the category? Are they all questionable images -- out of scope, not properly licensed, or probable or demonstrable copyright violations? Then request the deletion of the category in the discussion where you call for the whole mess of this new user's bad images to be deleted.
- However, if some new user adds a bunch of existing in scope images to a new category, maybe they have a point? Commons has no fixed schema, laid down by a central authority. I think some people get strongly wedded to the organizational sub-tree they and other people who share their interests use. We can get tunnel vision. But all the hierarchies we use are, in the end, conventions, not natural laws.
Story time. decades ago I was the guy at my little food coop, who met our delivery truck, helped the driver unload the shipment, and then updated the rolodex cards we used for inventory. I did this for a couple of years, then I had to go away for a year. I didn't create the system, I merely updated it, and, occasionally added new cards, for new items, adding them into a dozen or so broad categories. When I left the
cerealscategory only held cards for genuine cereals, likewheat, oats, millet, barley. When I returned the coop had started carrying organic equivalents to breakfast cereals, like organic cheerios, and they had been shoehorned into thecerealscategory, and someone who found this confusing had tried to add agrainscategory. When I arrived back both categories contained both kinds of foods. This kind of mess is what happens a database has no one in authority to lay down one rigid set of rules. Commons categories are like that.Maybe the creation of a category that doesn't seem to fit, like Category:Sexy, is a clue that a disambiguation page is necessary?
- Yes, if a category, or set of categories, existed, with an obvious misspelling, for a meaningful amount of time, a redirect is required. You and I participated in Commons:Categories for discussion/2010/11/Category:Ship's bells, which I think is an example of an "obvious error".
- I am not an administrator. Are you saying setting a robot to repetitively perform the actual moves isn't easy? Yes, if the category in question only contains a half dozen or so images, using cat-a-lot only takes a couple of minutes. But individuals can't be relied on to leave meaningful edit summaries. Even a cat-a-lot edit summary is only a clue to the fact someone has decided to empty a category.
An individual recently triggered me to start this thread, when, on their sole judgement, they removed multiple dozens of files from categories I started, then placed speedy tags on those categories, with the justification that the categories he or she had emptied were now empty. Those categories had held meaningful content for nine months. They didn't use any edit summaries, they never use edit summries, and this was all part of a reorgnization that involved editing over 500 files, that took them several days.
When a robot moves it there is a meaningful edit summary.
- Cheersǃ Geo Swan (talk) 19:47, 6 October 2026 (UTC)
- As it happens, at the moment Category:Sexy is not empty. I feel that the images there should be moved; I also feel that if someone were, instead, to create that category, no, we should not have to go through a formal process to get rid of it. I strongly suspect you have no idea how much relatively uncontroversial cleanup of utter crap admins are doing all the time, and how burdensome it would be to have a lot of formal process around it. - Jmabel ! talk 20:25, 6 October 2026 (UTC)
- Yes, that is an obvious error, but it's one you could easily imagine a non-native speaker making. Conversely, if you are saying that when I run across someone having added a category with a name like "Bookshops in Seatattle" we need to have a formal CfD and/or keep that as a redirect to "Bookshops in Seattle" I disagree entirely. - Jmabel ! talk 20:21, 6 October 2026 (UTC)
- I am saying that giving the command to the robot is slightly more more time-consuming than what I am doing with "Move" + Cata-a-Lot, generally results in a less clear summary (certainly never in a clearer summary), and also involves a delay until the robot picks up the task from its queue, usually under an hour but sometimes several days. When done by a non-admin filemover, it is tremendously slower, almost never completing on the same day (because an admin has to approve the bot use) and I've seen such things sit queued for admin review for weeks. - Jmabel ! talk 20:31, 6 October 2026 (UTC)
- I think you chose Category:Sexy as an obviously worthless category. Is it?
- What's the average waiting time for a {move} request? A year would be conservatives I'd say. Not a pleasant option. Little wonder that editors are tempted to take shortcuts. The principles outlined are all very high minded, but until realistic resources are behind them, they are just a recipe for sclerosis inaction. Laurel Lodged (talk) 17:01, 5 October 2026 (UTC)
- While I agree in general, I have to push back a little bit on the last bit (point 4). Commons categories are largely internal to Commons - as far as I am aware, they are not exposed to external projects in the same way that files are. External users linking to categories do so with the implicit understanding that the names or contents of categories may change at any time. Omphalographer (talk) 18:19, 5 October 2026 (UTC)
- They are used in some competitions (like WLM stats). Sometimes might be hardcoded in tools that are more or less external. Also as Tim said Cool URIs don't change ;) (which applies to most old cats) Nux (talk··dyskusja) 18:40, 5 October 2026 (UTC)
- Other projects, non-WMF projects, use Commons files and categories. I think you are mistaken if you believe these are stealth uses. If they were stealth uses they could easily be shut down. I think this is a deliberate policy. I know Justapedia uses them. So, I stand by point 4. You wrote "External users linking to categories do so with the implicit understanding that the names or contents of categories may change at any time." If this were true it would very strongly undermine the use of Commons resources by outsiders. Maybe someone with the WMF could weigh in here, over whether Commons allowing external projects to rely on Commons images is a deliberate choice? Geo Swan (talk) 17:45, 6 October 2026 (UTC)
- the problem of deleting rightful cat pages (including redirects) is obviously the sysop's fault.
- some sysops keep doing this despite being told not to. they should be removed. RoyZuo (talk) 18:36, 5 October 2026 (UTC)
- Should we really say it is the administrator's fault when the category system was not designed with a history mechanism? Is there a reliable way for an administrator, encountering an empty category, to determine if it has always been empty, or whether some ill-advised contributor covertly emptied it? I don't think there is. Short of deprecating categories, and introducing a tool for building hierarchies that does keep a history, I think doing our best to pressure those who want to move all the files in a category to follow best practices and to do so via a {{Move}} tag, or a CrD. Geo Swan (talk) 17:55, 6 October 2026 (UTC)
- There is an category watch method, https://commons.wikimedia.org/wiki/Special:RecentChangesLinked?hidebots=1&translations=filter&hidepageedits=1&hidenewpages=1&hideWikibase=1&hidelog=1&hidenewuserlog=1&target=Commons%3ACategories_for_discussion%2F2026%2F10&limit=100&days=7&urlversion=2 , see also mw:Manual:CategoryMembershipChanges. Probably not as good as you wanted, but probably a step in the right direction. People should always try to talk as a first resort. Snævar (talk) 21:51, 6 October 2026 (UTC)
- Should we really say it is the administrator's fault when the category system was not designed with a history mechanism? Is there a reliable way for an administrator, encountering an empty category, to determine if it has always been empty, or whether some ill-advised contributor covertly emptied it? I don't think there is. Short of deprecating categories, and introducing a tool for building hierarchies that does keep a history, I think doing our best to pressure those who want to move all the files in a category to follow best practices and to do so via a {{Move}} tag, or a CrD. Geo Swan (talk) 17:55, 6 October 2026 (UTC)
- Conditional support but subject to exempted cases. One example was given by Jmabel, for typo errors or names in non-conventional spellings (like "Category:Buildings in Bukawe" and "Category:Buildings in Cabalogan" which a regular user with Cat-a-lot usage right should be able to summarily move the categories to Category:Buildings in Bocaue and Category:Buildings in Catbalogan, respectively. Another thing, even for some established users who tend to create "legalese"-type categories or nonsensical categories, like several made by Judgefloro (talk · contribs) (e.g. Category:Museo ni Baldomero Aguinaldo y Baloy (facade, fences and interior & tombs of Baldomero and Petrona Reyes - Binakayan, Kawit, Cavite) and Category:Manila–Cavite Expressway, 2018), it is fitting to transfer files to a category with reasonable name and either convert the old category to redirect or nominate the old category for deletion (COM:CFD, which is quite backlogged). JWilz12345 (Talk|Contributions) 03:47, 6 October 2026 (UTC)
- WRT your examples "Category:Buildings in Bukawe" and "Category:Buildings in Cabalogan"... I suggest that, when a category had a name that included a typographical error, or was non-conventional, yet it contained meaningful content for a period of time, it should not be deleted. A redirect should be left, because we have no way of knowing how many people bookmarked it under the original imperfect name.
- Cat-a-lot is an imperfect tool, because it does not explain the reasoning. More than a decade ago I uploaded some images related to a river, in Africa. The river's name was in Arabic, which I don't speak, so I created a category for them in English transliteration. A year or two later someone else followed the bad practice of moving the existing images from the category I started, to a brand new category they started using a different transliteration Yeah. Cat-a-lot's edit summary didn't explain their reasoning.
When I contacted them they claimed the name I used was "wrong", because the site where they found an additional image used a different transliteration. Unlike Chinese there is no single reliable way to transliterate Arabic. After I insisted on a CfD I found at least one more way that river's name was transliterated into Engligh. In the long run it wouldn't matter which transliteration we put the base name at, so long we leave redirects at the other transliterations.
FWIW, the government of the country where the river flowed used the transliteration i picked on its government's website. Geo Swan (talk) 20:27, 6 October 2026 (UTC)
- One user in particular, whom I also shall not name, comes to my mind, fitting the introductory description perfectly in an encounter I had a few years ago. Now with filemover rights, it seems moving without redirect also applies to categories, so not even a second pair of eyes is involved anymore to otherwise follow up on a cat. speedy delete request. However, I am in favour of being bold to prevent adding to the infamous CfD backlogs, especially for silly little things. But leaving the old title as redirect is then pretty much essential to easily enable reverting in case of disagreement. --HyperGaruda (talk) 04:12, 6 October 2026 (UTC)
Request for volunteers to lead on COM:CSAM
In a recent high profile deletion discussion (here) we were reminded that Commons:Child protection is at proposed status, originally based on text copied from the English Wikipedia in 2012.
It would take an open mind as reviewing past discussion shows vacillation between wanting publication or withdrawing as no consensus. It may be that Commons does not need a separate policy as our project might default to the WMF policy, but even that default and deciding it's unnecessary to have a Commons specific policy should be based on a consensus, probably with a VPP vote.
Lastly a consensus would be best encouraging viewpoints from regular Commons contributors. Commons is not terribly interested in policies, especially a negative topic, but this is an area that a majority might expect to mostly share the same concerns. Fæ (talk) 21:59, 6 October 2026 (UTC)
- To use ThunderingTyphoons!' changes to the English Wikivoyage's equivalent page as inspiration, perhaps the page should be overall more child-oriented. Right now it's rather technical, which is fine to get into after the most important points are conveyed. Arlo James Barnes 01:24, 8 October 2026 (UTC)
Notification of DMCA takedown demand — Educacao nao se faz de cima para baixo, História no Museu da Pessoa (194872)
In compliance with the provisions of the US Digital Millennium Copyright Act (DMCA), and at the instruction of the Wikimedia Foundation's legal counsel, one or more files have been deleted from Wikimedia projects. Please note that this is an official action of the Wikimedia Foundation office which should not be undone. If you have valid grounds for a counter-claim under the DMCA, please contact me.
The takedown can be read here.
Affected file:
To discuss this DMCA takedown, please go to COM:DMCA#Educacao nao se faz de cima para baixo, História no Museu da Pessoa (194872). Thank you! Joe Sutherland (WMF) (talk) 13:51, 7 October 2026 (UTC)
Protected by Pixsy
I've found images, for example File:Adam Woods - Melodifestivalen 2024, Malmö (Torsdag)-2.jpg, that have "Protected by Pixsy" warning in permissions field. Is this allowed? I feel it's needless intimidation of reusers and promotion of Pixsy services. It also equates copyright violation to theft, which might be legally inaccurate. Template where this comes from: User:Adjoka/Pixsy. --MSDN.WhiteKnight (talk) 10:31, 8 October 2026 (UTC)
- I also think this is problematic. I am also confused if Wikimedia Sweden allows the usage of such services for works where they supported the creation. Other chapters explicitly prohibit automated copyright enforcement in the project funding policy. GPSLeo (talk) 10:41, 8 October 2026 (UTC)
- I won't comment on whether it's "needless intimidation" or "promotion", but that template seems like a very useful warning to help re-users avoid a shakedown by Pixsy. Most people who find things on Commons don't totally understand free license rules and requirements, that's just the way it is. I would definitely sleep better knowing those people have been told as clearly as possible that they risk legal action if they don't follow the rules as described in the license. Better, in my view, to put up with that template than see re-users get bombarded with takedown orders and requests for payment because they didn't understand what was required of them.
- In this specific instance though, I would agree with GPSLeo that it seems odd for Wikimedia Sweden to fund the creation of these images without some sort of contractual clause barring automated enforcement from services like Pixsy. 19h00s (talk) 10:46, 8 October 2026 (UTC)
- I would support deletion of the template and mass deletion of all images that require the template unless the uploader agrees to remove it.
- Wikimedia Commons is not a tool to help literal shakedowns and pseudo legal threats (see Copyright troll). "Technical" arguments to justify official looking threats do not make sense if they are intended to work around free use, these fail COM:L which states in plain English "Wikimedia Commons only accepts free content, that is, images and other media files that are not subject to copyright restrictions which would prevent them being used by anyone, anytime, for any purpose." Courtesy ping @Adjoka: Fæ (talk) 11:57, 8 October 2026 (UTC)
- I don't think that violates COM:L. It warns about mishandling images, but you can still use it anytime, for any purpose, as long as you obey the license. Which is what the existing license templates already say anyway ("you are free to X, Y, Z, under the license conditions"). The Pixsy warning, as I understand it, is just more direct and practical. Nux (talk··dyskusja) 21:14, 8 October 2026 (UTC)
- I do not think this is any sort of "intimidation". Every licence apart from CC0, WTFPL, and the like has a clause warning that violating the terms of licence has consequences. It is normal. As for promotion, it maybe a little bit of a promotion. But in a way so is the termplate that I add to my photos that promotes my camera manufacturer. I would support making this Pixsy template smaller, it takes disproportionate amount of space. ℺ Gone Postal (〠 ✉ • ✍ ⏿) 12:57, 8 October 2026 (UTC)
- Unfortunately "recover compensation" is a legal threat for reusers, especially those that are inexperienced with copyright law and might pay a demand, rather than call their bluff. I'd go a step further and if there are uploaders that are going beyond using take downs to request attribution, but using Commons to copyright troll and successfully get demands for cash paid, we should block them from uploading to the project.
- For those unaware, pixsy takes a 50% commission on settlements. They have a history of aggressive legal action but almost invariably settle out of court. One of their targets has been Cory Doctorow, friend of Wikimedia Commons, who wrote about the experience here in 2022 and described their demands as "baseless legal threats".
- I don't think Wikimedia Commons should support or condone this type of behaviour in any way, including denying the use of templates that promote Pixsy. Fæ (talk) 13:38, 8 October 2026 (UTC)
- After rereading Doctorow's experience with this firm, gone ahead and created Deletion requests/User:Adjoka/Pixsy. Fæ (talk) 14:57, 8 October 2026 (UTC)
- I can understand both sides. The municipality of Trogen used this file without any attribution on their homepage (next to my SVG creation of their COA). I had to write three E-mails with the request to add the attribution to complay with the license conditions. The first E-mails was sent to the direct municipality with no reaction. The second to the upper level administration, they would check that. After almost 3 weeks, no furthe reaction, so I reminded them. Instead of complying with the license conditions, they used another image. So, the problem is, that often the respect for the work isn't there, and a proper "reminder" of the circumstances is not that bad idea, I think --PantheraLeo1359531 😺 (talk) 19:19, 8 October 2026 (UTC)
- PS: For clarification, I did not bring up any legal threats, but it proves that the awareness of attribution for using free media is not always present, even at state administration entities --PantheraLeo1359531 😺 (talk) 19:21, 8 October 2026 (UTC)
- See also Commons:Deletion requests/User:Adjoka/Pixsy: :
Delete both User:Adjoka/Pixsy and User:Josve05a/Pixsy: bad faith copyright trolling, blackmailing for profit, links to malware sites, destructive business model, malicious spying on peope using AS (Artificial Stupidity). If your f**king image is strictly yours and you are so afraid of "theft", then do NOT upload it anywhere, problem solved. Taylor 49 (talk) 01:21, 9 October 2026 (UTC)
- See also Commons:Deletion requests/User:Adjoka/Pixsy: :
nappy.co
Nappy.co is a site that offers CC0 1.0 licensed photos of black and brown people. They have recently announced that they are shutting down. There are a handful of these photos on Commons already. I think it would be useful to include these photos in Commons as many are of high quality and could be useful in an educational context. I unfortunately have neither the skills or time at the moment to do this myself, so I bring it to the VP for others to be aware and consider. Ckoerner (talk) 14:29, 8 October 2026 (UTC)
- Thanks for sharing here. Sad to see it shutting down. I've reached out to them to see if they can provide a dump of all the photos and their data, and have otherwise also started working on a script to download everything from the site (but of course a dump would be best if they can provide one). ~Kevin Payravi (talk) 18:56, 8 October 2026 (UTC)
An Ukrainian Trizub Legal Disclaimer
Since I noticed an imbalance in Wikimedia's disclaimers, I would like to discuss creating a Template:Ukrainian Tryzub symbol template. I don't support anyone—neither Russia nor Ukraine—but if a
| Legal disclaimer This image shows (or resembles) a symbol used by the Russian Federation and its Armed Forces, an organization closely associated to it, or another party advocating or glorifying wars of aggression or aggressive conduct. The use of these insignias may be prohibited by law in the Czech Republic, Germany, Kazakhstan, Kyrgyzstan, Latvia, Lithuania, Moldova, Poland, Ukraine and other countries, depending on context. |
exists, there should be a counterpart to balance it out, like
and
| Legal disclaimer This image shows (or resembles) Palestinian insignia such as flags, coats of arms, etc. Such usage may be subject to official restrictions in Israel if the purpose of the flag is to "identify with a terrorist organization or show sympathy for it, or if it is highly likely this act will lead to a grave disruption of public peace", according to a 2014 statement by the Attorney General. |
So, I’d like to ask for your thoughts on creating a Template:Ukrainian Tryzub symbol—one that wouldn't damage the country's reputation, nor be offensive or delegitimize the State, but would instead serve to warn the average user that printing or publicly distributing a file containing these symbols in Russia could lead to imprisonment or a heavy fine in their own country. — 20Prox 09:25, 9 October 2026 (UTC)
- There's a new thread at VPP about this kind of template. — Arlo James Barnes 18:42, 9 October 2026 (UTC)
- Ah, OK thanks, I didn't know that before 20Prox (talk) 20:00, 9 October 2026 (UTC)
Category does not show up
I go to Category:Number 05001 on stamps and I observe that it is inside Category:Number 05001 on objects, but when I follow the link, I see that the parent category is somehow empty. How can it be? ℺ Gone Postal (〠 ✉ • ✍ ⏿) 18:01, 9 October 2026 (UTC)
- Problem vanished for this cat ... but the BUG undeniably exists. For example this cat contains 13 pages. Yet when going one level up, the number 10 is showed instead. Taylor 49 (talk) 21:06, 9 October 2026 (UTC)
- @Gone Postal and @Taylor 49: Purging the lower cat fixes it's representation in the upper cat by forcing some back-end work. I needed to do that for the cat Taylor 49 wrote about, but that or something like it was already done for the cat Gone Postal wrote about. See COM:PURGE and action=purge. — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 21:44, 9 October 2026 (UTC)
Comment, see discussion for this problem at Commons:Village pump/Technical#Category gallery count shows negative number. It seems the problem is still ongoing, and as Jeff G. mentions above, purging the category page seems to fix it. Thanks. Tvpuppy (talk) 21:54, 9 October 2026 (UTC)
- Purging the SUBcategory page is the operative step here. Null editing it (by prepending {{subst:void}}) may work, too. Then force-refreshing or one of the preceding steps on the parent may work too. — 🇺🇦Jeff G. ツ please ping or talk to me🇺🇦 22:29, 9 October 2026 (UTC)
Another categorization issue (sigh...)
I just initiated Commons:Categories for discussion/2026/10/Category:Births in Tennessee by municipality. There's a bigger-picture issue arising from this category's creation, which would have distracted from that discussion, so I'm bringing it up separately. For the United States, it's been understood that categorizing someone's birth by county is preferable for lesser-populated places, while more specific by-city subcats should be created for, well, cities. There are a number of editors who have chosen to disregard this, apparently believing that we need an unlimited number of one-entry subcats for every little fucking tiny place. This includes places incorporated as towns and villages, CDPs, and even places that aren't enumerated by the Census Bureau! Several years ago, I attempted to redirect these subcats and their content to the by-county subcats. I had to stop when an admin tried to interfere, claiming that I didn't ask permission to do so (what the fuck?), while many of the editors who created these tiny subcats have since undone those efforts. If we're going to permit another free-for-all here, is "by city" the most appropriate naming convention? The cat I CFD'ed was apparently created because its sole subcat relates to a place incorporated as a town, not a city. Allowing that to blossom would create another free-for-all. If it's considered permissible that every little fucking tiny place gets its own tree of tiny subcats instead of a logically-constructed tree, shouldn't we replace "by city" with "by populated place", following the lead of Wikipedia's recent actions? Such a move would be a lot more broad-ranging than the subset of cats I discuss above, since we already mix in cities with CDPs/towns/etc. in a lot of trees. RadioKAOS / Talk to me, Billy / Transmissions 15:31, 9 October 2026 (UTC)
- I would agree that "People born in" categories are pretty useless for place where very few people have been born. They are also often inaccurate: I imagine that the majority of births in Tennessee, at least in the last 75 years, are in maternity wards, and while most people were born in the county where their mother resides, plenty of them were not born in the village/hamlet/etc. where they lived and were raised. I'm a good example of this last, in suburban New York. I suspect someone would be liable to say I was "born and raised in Freeport," but actually I was not born there, because the maternity ward was in Oceanside. - Jmabel ! talk 19:36, 9 October 2026 (UTC)
- I am not sure how any of these "Births in" categories could help a user locate relevant media. "People from" is fairly easy to imagine a use case for (and has a use value that increases with specificity), but having a separate category tree just for people born in a place seems more likely to hinder discovery than to help it. I agree that these categories under discussion don't seem useful at all. If we're going to have "Births in" at all, I think that if anything it should be even more hyperspecific -- "Births at X hospital", "Home births in Y", etc. -- with higher levels in the tree existing solely as container categories. -- Visviva (talk) 01:49, 10 October 2026 (UTC)
- A person's place of birth (P19) is a property which is tracked at Wikidata. If we have categories for this at all, surely they should be autopopulated from Wikidata? Maintaining a system of categories for that locally seems like a lot of duplicated effort with no clear benefit. Omphalographer (talk) 03:04, 11 October 2026 (UTC)
Converting single page jpg into a PDF
Category:Memoiren einer arabischen Prinzessin (Ruete) contains 204 single page jpg files from a book. Is there any protocol for combing them into a PDF? Eievie (talk) 16:46, 9 October 2026 (UTC)
- Well, you can compile these into a pdf, there are several tools to do it. However this was an old scan and there are better around.
- Here's the same jpgs recompiled as one pdf File:Memoiren einer arabischen Prinzessin (Ruete).pdf
- Here's a better scan File:Memoiren einer arabischen Prinzessin , 1886.pdf
- For accessibility, here's an edition in English File:Memoirs of an Arabian princess - an autobiography (IA memoirsofarabian00ruetuoft).pdf
- Unless the jpg scans of text are inuse on wikisource or similar, they should be put up for deletion as being out of scope, see COM:NOT. -- Fæ (talk) 17:14, 9 October 2026 (UTC)
- Using w:ImageMagick and w:PDFtk, it's as easy as downloading the JPGs to a working directory and using
convert *.jpg *.pdfand thenpdftk *.pdf cat output foobar.pdf. — Arlo James Barnes 19:29, 9 October 2026 (UTC)- img2pdf can be preferable to ImageMagick, as it doesn't re-encode the JPEGs. Similar usage but can do it in one step:
img2pdf *.jpg -o foobar.pdfSam Wilson 03:55, 10 October 2026 (UTC)
- img2pdf can be preferable to ImageMagick, as it doesn't re-encode the JPEGs. Similar usage but can do it in one step:
- For img2pdf can you rearrange the pages before output to a pdf? On some I have used, output depends on the order I load them, and cannot be rearranged. --RAN (talk) 04:20, 10 October 2026 (UTC)
- @Richard Arthur Norton (1958- ): The pages are added to the PDF in the order you give them in the output. So if you use a glob like
*.jpgit'll put them in alphabetical order, but if you specify each file like002.jpg 001.jpgit'll put them in whatever order you give. Sam Wilson 01:10, 11 October 2026 (UTC)
- @Richard Arthur Norton (1958- ): The pages are added to the PDF in the order you give them in the output. So if you use a glob like
- Thanks! --RAN (talk) 01:16, 11 October 2026 (UTC)
Simultaneous US publication
Does {{Simultaneous US publication}} accurately describe Commons practice? If so, should that practice also be codified at COM:L?
The incoming links to the template from project space are generally favorable, but are limited to file-specific discussion posts. For something that represents, on the face of it, a major derogation from the general principle that non-freely-licensed files must be in the public domain in at least the United States and in the source country of the work
, it seems like it might be good to have more thorough documentation than what seems to be only a free-floating and recently-created template. For my part, I like the template and the position it represents; it enhances the educational value we can provide by allowing the inclusion of a lot of content that would otherwise be locked away for decades to come. But I'm curious to get a better sense of how broad the consensus is on this topic. -- Visviva (talk) 03:46, 8 October 2026 (UTC)
- I think the short answer is that it only ends up being used where simultaneous U.S. publication would come as a surprise. For example, we wouldn't typically put it on an agency press photo from a war zone, with a citeable PD U.S. publication source within 30 days after the event: we'd just cite that as a source. - Jmabel ! talk 08:13, 8 October 2026 (UTC)
- The template "Simultaneous US publication" is recent, but the associated template {{PD-URAA-Simul}} is much older, having been created in 2008. – Howardcorn33 (💬) 20:04, 8 October 2026 (UTC)
- The point is that according to US law when something has been simultaneously published (within 30 days) in the US it is a US work. It might be dubious that any other country would treat it this way given several factors like the US was not a member of the Bum Convention and didn't comply with their rules. On the other hand the template is correct for files like Pro Wrestling Illustrated which is a US magazine that just happened to be published in the UK and Canada. 999REAL 💬 ⬆ 20:40, 8 October 2026 (UTC)
Thanks to all for the input. I wonder if the following would work as an explanation of why this is OK and not really an exception to the rule? In evaluating the source country of a work for Commons purposes, the Commons community generally follows the scheme established by the Uruguay Round Amendments Act, at 17 U.S. Code § 104A. Accordingly, if a work was first published in a country outside the US but was then published in the US within 30 days, then Commons will consider the work's source country to be the US, and the work only needs to be public domain under US law. -- Visviva (talk) 02:06, 10 October 2026 (UTC)
- Seems correct to me. - Jmabel ! talk 22:20, 12 October 2026 (UTC)
Photo Challenge August 2026 results
| Rank | image | Title | Author | Score |
|---|---|---|---|---|
| Leaving the Seine estuary (Le Havre harbor) into English Sea |
Pedemann | 11 | ||
| Confluence du Rhin et de la Moselle à Coblence en 1988 - Confluence of Rhine and Moselle at Sunshine, Coblence, Germany, 1988 - Zusammenfluß von Rhein und Mosel in Koblenz im 1988 |
Jean-Marie Vugnon (2) | 11 | ||
| The mouth of the Sava into the Danube | Krigore | 9 |
| Rank | image | Title | Author | Score |
|---|---|---|---|---|
| A threaded needle | Krigore | 17 | ||
| Knitting needles | Tn.kuvat | 11 | ||
| IV Needle & Sodium Chloride Water Drops (Black and White) |
Zwiebackgesicht | 8 |
Congratulations to @Pedemann, @Jean-Marie Vugnon (2), @Krigore, @Tn.kuvat and @Zwiebackgesicht. Sekidoki (aka Taiwania Justo) is speaking (Reception Room) 06:23, 12 October 2026 (UTC)
Endangered free media repository
A few days ago, I received an Email that MorphoSource has problems with keeping up the web page. It contains also freely CC licensed 3D models of skulls or CT scans, etc. Pinging also @Fæ: :3. Maybe some users with experience can collect some models? See also Category:Files from MorphoSource --PantheraLeo1359531 😺 (talk) 19:48, 9 October 2026 (UTC)
- Thanks @PantheraLeo1359531 for the notice here. -- Ooligan (talk) 16:33, 13 October 2026 (UTC)
Redundancy among almost identical images from the same source
Usually, I am engaged with copyright issues, so I do not know the community standards on other issues as well as I might. However, when patrolling new PD uploads (mainly to check copyright license tags) I sometimes come across situations like this: File:Mozart - Piano Concerto No. 26 K. 537 - autograph, The Morgan Library & Museum, f. 1r.jpg shows a higher resolution version of the much-used File:Mozart - Piano Concerto No. 26 - Opening Page of the Autograph Manuscript.jpg from the same source, albeit with a slightly different crop of the black framing edges. It seems to me that if the original had been overwritten with the newer version, this would have been in keeping with Commons:Overwriting existing files; however, now that it was uploaded separately, I am not sure what to do with it. If only the better one is to be kept, is the new or the established title to be preferred? Or, if both are kept as they are not exact duplicates, should the links in the various Wikipedias changed manually to use the higher-resolution version? Or should a DR be opened to decide the issue? Any guidance would be welcome! Felix QW (talk) 19:10, 10 October 2026 (UTC)
- There's one thing that can be done without any harm whatsoever: mentioning such finds in each other's "other version" field in the {{Information}}, perhaps with a descriptive image legend ("higher resolution, slight crop difference" would be possible for instance in your Mozart example). So, even if you do not want to open a DR with the rationale "nearly duplicate of XY", your research and finds will stay documented. If you settle for a DR, put that always on the smaller file, if something gets deleted als duplicate, its page becomes a redirect, so no project uses get lost. In fact, duplicates are a valid COM:Speedy deletion rationale, but if something is not an exact duplicate or scaled down, then a standard DR (if a deletion is sensible at all) is certainly better. Regards, Grand-Duc (talk) 20:27, 10 October 2026 (UTC)
- I suggest uploading the original source with its wide border for reference, then keep the best cropped one for general use (by sticking {{duplicate}} on the fairly obviously inferior crop). This removes any doubt about what was cropped and there's no point in keeping multiple crops for the sake of it.
- Ideally the original uncropped version could have been the first version then overwritten, that way it's permanently in the file history if anyone wants to verify it. Fæ (talk) 10:18, 11 October 2026 (UTC)
- Gone ahead and uploaded the original from The Morgan - File:Concerto for piano and orchestra no. 26 in D major, K. 537 (morgan 115397).jpg. Someone should choose the best crop and delete the other.
- The whole manuscript has been scanned, so the rest should be uploaded, at least initially the originals uncropped are all worth having on Commons for reference. --Fæ (talk) 09:15, 14 October 2026 (UTC)
- @Fæ: Thank you very much for your input and your support! I marked the inferior crop as a {{Duplicate}} (linking this discussion) and also marked the remaining crop as {{Extracted from}} the original you uploaded. Felix QW (talk) 13:36, 14 October 2026 (UTC)
- Hello, I am the contributor who originally uploaded File:Mozart - Piano Concerto No. 26 K. 537 - autograph, The Morgan Library & Museum, f. 1r.jpg, and I have only just come across this discussion. I never intended to create a duplicate of the image. My initial goal was to upload a higher-quality version to replace the existing image and I did try to upload it as a new version (using the "Upload a new version of this file" button).
- However, I encountered a permission error. It was refused with "File overwriting not allowed - you currently do not have sufficient permissions". A separate upload was the only route open to me to make the higher-quality image available. I have to say I do not understand that refusal, as my account is autoconfirmed, so I am not sure which restriction it came from. If anyone can tell me, I would be glad to know, since overwriting would obviously have been the cleaner route here.
- Regards, SovalinaWiki (talk) 08:31, 15 October 2026 (UTC)
- Commons:Overwriting existing files/Requests explains that in 2023, a decision has been made to limit overwriting to autopatrolled (rather than autoconfirmed) users. It seems that if you do this kind of upload more frequently, requesting autopatrol rights is the way to go, and that otherwise one could list requests there on a case-by-case basis. Felix QW (talk) 09:26, 15 October 2026 (UTC)
- Also of interest may be Commons:History merging and splitting. But just be careful, in some cases it is obvious that the file is exactly the same except for the resolution they should then be merged (rather than one of them deleted). However, sometimes people feel that files are duplicates, while they are actually just showing something very similar. ℺ Gone Postal (〠 ✉ • ✍ ⏿) 08:50, 15 October 2026 (UTC)
Flags of Palestine
Category:Flags of Palestine, Category:Flags of the State of Palestine and their relation to their respective subcats and content, and relation with Wikidata and (via that) other wikis are a bit of a mess currently. I'm probably not the one to sort it out, but it needs to be sorted. I suspect some subcats are poorly defined as to whether they refer simply to geography or to a Palestinian governmental entity.
Pinging @Поль Крол Злой Диктатор, who has worked in this area recently. - Jmabel ! talk 07:37, 13 October 2026 (UTC)
- Personally, I believe that Category:Flags of Palestine should contain only the flags of the modern Palestine, as that is what people most often mean by the term today. However, I changed the categorization for two reasons: 1) it seems odd to have two categories with nearly identical names within the same (or related) general categories; 2) Category:Flags of Palestine currently includes Category:Flags of Israel which — despite politics and the fact that a number of states do not recognize it — is a UN member and therefore cannot belong in Category:Flags by state with limited recognition (for the same reason that Category:Flags of the People's Republic of China is excluded, even though several countries still recognize Taiwan as the legitimate government of China). In any case, I believe we should settle on the categorization scheme before creating new categories. It might also be worth creating Category:Flags of Palestine (region) to house Category:Flags of Palestine, Category:Flags of Israel, and categories for the flags of entities that existed prior to 1947. Поль Крол Злой Диктатор (talk) 23:55, 13 October 2026 (UTC)
- Putting Flags of Israel as a subcat of Flags of Palestine doesn't seem very sensible to me. That feels like someone engaging in political axe grinding. Bawolff (talk) 01:08, 14 October 2026 (UTC)
- I do think the "region" solution might help. Even with that, the hierarchy in that area is still a mess, and should be sorted out. - Jmabel ! talk 07:21, 14 October 2026 (UTC)
- Putting Flags of Israel as a subcat of Flags of Palestine doesn't seem very sensible to me. That feels like someone engaging in political axe grinding. Bawolff (talk) 01:08, 14 October 2026 (UTC)
Minor mistakes in categories, or careful, but slower job?
I sometimes spend time patrolling overflowing categories. Let's say we're talking about category Sky. The quick way to diffuse category is to search within category for a keyword, for example "Canada", select images looking at thumbnails with Cat-A-Lot, and move them to category Skies over Canada. I avoid making obvious mistakes, like moving images of chickens mistakenly put in category Sky, but there are sometimes imported images (Panoramio etc.) that may have mass imported description like "Our Canada and USA trip". So some of the skies may be over Canada, some may be over the US.
Would you say it's better to quickly diffuse the category anyway, with possible small mistakes, like skies over USA ending up in category "Skies over Canada", and let the deeper category caregivers deal with this (or deal with this myself in 2 months when I end up in deeper category) OR diffuse category slowly and carefully (opening each image found with keyword Canada, and checking whether something in description suggests otherwise), but this way, maintenance of overflowing categories is neverending, and they never get diffused.
I'm leaning towards allowing possibility of minor mistakes.--Tupungato (talk) 12:02, 13 October 2026 (UTC)
- I'd say that if you are making even 1% mistakes on average, then you are definitely doing it wrong. Anything over 0.2% (one in a 500) should be at least a yellow flag. Every mistake you make doing this is likely to take significant time to fix, probably as much time as it takes to add/refine 100+ categories by eyeballing like this. - Jmabel ! talk 18:28, 13 October 2026 (UTC)
- I'd push back a bit on what Jmabel said - you should try to avoid making categories worse, of course, but propagating a minor error that's already been made (like your "skies over Canada" example) isn't the end of the world. It'd certainly be better if you caught it, but it isn't so critical that it should slow down otherwise uncontroversial tasks like diffusal. Omphalographer (talk) 01:50, 14 October 2026 (UTC)
- @Omphalographer: I don't want to make too much of the disagreement here but I do want to point out a non-obvious impact as it has affected me: I have about 100,000 file pages on my watchlist, about 2/3 of them my own uploads and the rest mostly historical images of the Pacific Northwest where I've worked on the description, categories, etc. Recently a user I'd rather leave nameless because I'm not intending to criticize them beyond what I've written to the directly has done a ton of category work, mostly diffusion, in that area. The user in question is certainly at least 97% on the mark, maybe 99% (hard to track closely), but even allowing the 99%, that's a higher error rate than I feel comfortable with on my own uploads or on ones where probably no one else is really watching them so I've taken the responsibility. So it means I've had to review about 8000 of their edits over the last month, to catch somewhere between 80 and 200-odd errors. That's a lot of impact on my time, and while there are probably only a couple of hundred Commons users watching so many files to have that sort of impact on them, the impact would be proportional for anyone else who is trying to make sure that their own content stays correctly categorized.
- Conversely, there are other editors who are so consistently correct that when I see their edits in my watchlist, the only reason I would look at the edit is sheer curiosity. - Jmabel ! talk 07:33, 14 October 2026 (UTC)
- I think that the talk about percentages is a little misleading, there are different mistakes, some are worse than others. Let's say that you move 1 file out of a million into a category that is so deep in the tree that nobody actually looks at it. If this file is not categorised in other ways and its name is not very good, this file can be lost completely for a while. On the other hand if you move 1 file out of 100 within a category where the error is trivial to detect, or when it is a tangential category to the subject matter of this file, then it is not such a big deal. I do not work on diffusion much here, but I have been working a lot on adding infobox to files without them. I concentrate on stamps. Now, while doing that I also categorise them by price. Would a slower process of also categorising by every other aspect (colour, perforation, etc) and finding more information that does not exist in the original description be better? Maybe, but overall I would give up after searching for the exact date of publication of some 1939 stamp for a half an hour without being able to find a correct answer. Is it actually "better"? I know that you have asked a specific question, but my answer is "do what is reasonable for a specific category", and sadly you are the one who needs to define what "reasonable" means, and sometimes deal with somebody whose definition will differ from yours. ℺ Gone Postal (〠 ✉ • ✍ ⏿) 09:33, 15 October 2026 (UTC)
Senate Bill 2424 and House Bill 11566 from the Philippines concerning online safety for children
Resources: Senate Bill 2424 and House Bill 11566.
Both pending bills aim to ensure "safety of children" in the Philippines, away from "harmful" Internet content most especially social media and other high-risk websites and platforms. This is made possible by age verification or age assurance measures.
- Senate Bill 2424 key provisions
- Section 3(h) defines a social media platform as "an electronic service that primarily facilitates online social interaction, enabling two (2) or more users to link, communicate, or interact with each other, or allows them to create, upload, publish, share, or post content accessible to other users."
- Section 3(c) defines a covered social networking function as "a feature of an electronic service that enables users to establish or maintain social connections; communicate or interact with other users beyond communications strictly necessary for the underlying service; participate in public, semi-public, or discoverable communities; maintain friend, follower, subscriber, or similar user connections; or create, upload, publish, stream, share, distribute, access, or view user-generated content, including livestreamed content, made available by other users."
- Section 3(d) defines harmful content as "online content, including livestreamed content, that: (1) constitutes or facilitates sexual abuse, exploitation, or trafficking of children; (2) depicts, promotes, encourages, facilitates, or provides instructions for ongoing or graphic violence, suicide, or self-harm; or (3) directly encourages, facilitates, or provides instructions for conduct presenting an imminent and substantial risk of death or serious physical injury to a child."
- Section 3(e) defines high-risk digital services as "social media platforms and online gaming services with covered social networking functions, such as but not limited to, Meta Platforms, Roblox, and Gorebox."
- Section 6 provides a restricted list of exempted platforms, but with one major caveat. With underlines added by me here as emphasis:
The following digital services and functions shall not be subject to the provisions of this Act:
(a) Electronic mail services;
(b) Private messaging services limited to private or closed communications which do not feature any public, semi-public, or discoverable, community-based, follower-based, or other social networking functions;
(c) Online gaming services, primarily for gameplay whose communication or similar functionalities or features are strictly incidental to such gameplay: Provided, That covered social networking functions offered by such services shall not be excluded from the coverage of this Act: Provided, further, That the functionalities or features including voice or text chat, shall be subject to the age restrictions and age-assurance requirements under this Act: Provided, finally, That child safety measures shall also attach to the gameplay functions when made accessible to children, taking into account their differing and evolving capacities;
(d) Educational platforms used for instruction, learning, assessment, or school administration, where access is limited to students, teachers, school personnel, parents, or other authorized users and user interaction is limited to legitimate educational purposes;
The Department of Education (DepEd), Commission on Higher Education (CHED), and Technical Education and Skills Development (TESDA) shall issue joint guidelines on the standards and procedure for certification. The Department of Information and Communications Technology (DICT) shall maintain and publish on its website, a consolidated list of certified platforms and services, which shall be updated every quarter.
(e) Digital news services; and
(f) Enterprise, workplace, or professional collaboration services where access is limited to members or authorized users of an organization and which do not provide public or discoverable covered social networking functions.
The foregoing exclusions shall apply only to the service or function described herein and shall not exempt any covered social networking function that would otherwise fall within the coverage of this Act.
- Section 5 states:
No child shall be permitted to register, create, access, use, or maintain an account on any high-risk digital service. This prohibition is absolute and shall not be waived by parental or guardian consent, authorization, or supervision, under any circumstance.
In the case of an online gaming service or other electronic service that offers both covered social networking functions and functions not so covered, the minimum age requirement shall apply only to the former and not to the entirety of the platform or service.
- Section 3(b) defines a child as "a person below eighteen (18) years of age."
- House Bill 11566 key provisions
- Section 3(r) defines a social media platform as "any internet-based service, network, application, website, or software whose purpose is to facilitate online social networking or allow the creation, sharing, or dissemination of user-generated content. The term shall not include the following: (1) Electronic mail services; (2) Short messaging services: (3) Private messaging services without public or discoverable social networking functions; (4) Educational platforms and enterprise, workplace, or professional collaboration tools, approved by the Department of Education (DepEd) or other national government agencies concerned; (5) Digital news services; and (6) Government digital services."
- Section 3(s) defines a user-generated content as "any information, material, or content created, uploaded, posted, transmitted, shared, streamed, published, or otherwise made available by a user through a digital service, including text, images, photographs, audio, video, livestreams, software, comments, messages, and other forms of digital expression."
- Section 3(g) defines a functionally equivalent digital service as "a digital service that is not nominally a Social Media Platform but performs core social-networking, content-sharing, communication, user-interaction, livestreaming, or substantially similar functions and presents child online safety risks substantially similar to those addressed under this Act."
- Section 3(h) defines harmful or prohibited content as "content that promotes, glorifies, encourages, facilitates, or provides instructions for violence, self-harm, violent extremism, including nihilistic violent extremism and other emerging forms thereof, sexual abuse and exploitation, or other conduct that constitutes a serious and foreseeable risk to the safety or well-being of children, or contains deepfake or synthetic media that realistically simulate, fabricate, modify, or imitate the appearance, voice, likeness, actions, or statements of a real or fictional person, object, or event for the purpose of misinformation."
- For Coverage (Section 4), with underlines added by me here as emphasis::
This Act shall apply to all Digital Platforms that are accessible, offered, or made available to users in the Philippines, regardless of their place of incorporation, principal place of business, or location of their servers.
For purposes of this Act, an Online Gaming Platform shall be covered only with respect to its social, communication, content-sharing, livestreaming, user-interaction, recommender, or other interactive features and functionalities. Nothing in this Act shall be construed to diminish, exclude, or transfer the existing jurisdiction, regulatory authority, or enforcement powers of Philippine Amusement and Gaming Corporation, the Games and Amusements Board, the Movie and Television Review and Classification Board, or other competent government agencies over matters within their respective mandates, except to the extent expressly provided in this Act with respect to child online safety risks arising from covered social or interactive functionalities.
Coverage under this Act shall be determined by the Office created under Section 8 herein based on the actual functions, features, and risks of a service, rather than solely on its name, stated purpose, business model, or manner of marketing. The said Office may make a written determination of coverage based on such statutory criteria and standards, subject to notice, due process, and applicable remedies in accordance with this Act.
- Section 8 refers to the duties and responsibilities of the to-be created SAFE Kids Office ("Office for Safe and Friendly Environment for Kids in Digital Spaces").
- Section 5 states:
No Social Media Platform, Functionally Equivalent Digital Service, Application Distribution and Operating System Provider, or Online Gaming Platform with respect to its social, communication, content-sharing, livestreaming, user-interaction, or other interactive features and functionalities, shall allow a person below thirteen (13) years of age to create, register, maintain, or use an account or otherwise access such service or features.
Upon determining or becoming aware that an account is being maintained or used by a person below thirteen (13) years of age, the Digital Platforms shall, without undue delay, disable the account and take reasonable, proportionate, and privacy-preserving measures to prevent its continued use or recreation.
- Section 6 allows children and teens (aged 13 to 17) to retain accounts, subject to parental consent, but they are restricted from viewing or utilizing the following features: "(a) Harmful or Prohibited Content; (b) Advertisements; (c) Recommendations; (d) Communications and interactions; (e) Livestreaming; (f) Endless scrolling; (g) Short-form video feeds or “shorts”; (h) Behavioral profiling; (i) Unnecessary collection or sharing of personal information; (j) Purchases; (k) Gambling-like mechanisms; and (l) Other features or practices that may pose reasonably foreseeable and material risks to the safety, health, privacy, development, education, sleep, or well-being of children."
- My informative notes
One can notice the extensive usage of "or" conjunction instead of "and" when defining what website or platform is a social media platform. Using the Senate Bill version as example: "an electronic service that primarily facilitates online social interaction, enabling two (2) or more users to link, communicate, or interact with each other, or allows them to create, upload, publish, share, or post content accessible to other users." This means, even if a website does not have the primary function to facilitate social interaction online, a website or platform that allows 2 or more users to share, create, or publish content that can be read by other users is deemed a social media. The House Bill has a nearly identical definition, utilizing "or" instead of "and" in connecting the two important clauses defining a social media platform. Wikimedia platforms like Wikimedia Commons are likely covered by the specific definitions.
The House Bill provides an additional safeguard in case a platform fails the usual characteristic of a social media platform, in the form of "functionally equivalent digital service." The definition also uses "or," not "and": a digital service that is not nominally a Social Media Platform but performs core social-networking, content-sharing, communication, user-interaction, livestreaming, or substantially similar functions and presents child online safety risks substantially similar to those addressed under this Act.
The Senate bill's definition of a covered social networking function also uses "or" and not "and": "a feature of an electronic service that enables users to establish or maintain social connections; communicate or interact with other users beyond communications strictly necessary for the underlying service; participate in public, semi-public, or discoverable communities; maintain friend, follower, subscriber, or similar user connections; or create, upload, publish, stream, share, distribute, access, or view user-generated content, including livestreamed content, made available by other users."
It remains to be seen if the DICT would be rigid in interpreting "or" or give flexibility to treat "or" as an "and." Flexibility would exempt Wikimedia from age verification mandate under the Senate Bill (but may not be under the House Bill due to "functionally equivalent digital service" term.
From the Senate Bill's Section 6, educational platforms would be given exemptions, but only if those are certified by three government agencies that administer education in all levels (DepEd for pre-school to high school, CHED for tertiary/college, and TESDA for technical-vocational), and the condition is that "access is limited to students, teachers, school personnel, parents, or other authorized users and user interaction is limited to legitimate educational purposes." The list of the certified educational platforms would be updated by the country's information and communications technology agency (DICT) every quarter. Moreover, the concluding paragraph of that section does not exempt the "social networking functions" of the exempted platforms. Again, the Senate bill defines this as "a feature of an electronic service that enables users to establish or maintain social connections; communicate or interact with other users beyond communications strictly necessary for the underlying service; participate in public, semi-public, or discoverable communities; maintain friend, follower, subscriber, or similar user connections; or create, upload, publish, stream, share, distribute, access, or view user-generated content, including livestreamed content, made available by other users."
- Reddit forum
H.B. 11566 - SAFE KIDS ACT encompasses more than Social Media. It includes Banning Children from Using Operating Systems. This also means EVERY WEBSITE (that requires account-creation) will have consistent Age Assurance Checks to prove users are not minors. They also need license to operate in PH. Here are the relevant excerpts from the post by "territorialfantail":
- Functionally Equivalent Digitial Service (idk the definition is VERY VAGUE maybe Twitch, Youtube, and most art and fiction sites, Deviantart, pixiv, photobucket, flickr, etc).
- Basta (in Tagalog, English is: It's just that) anything that has "information, material, content that is created, uploaded, posted, transmitted, shared, streamed, published, or other wise made available by a user through a digital service, including text, images, photographs, audio, video, livestreams and other forms of digital expression" WILL NOT BE ALLOWED TO BE ACCESSED BY CHILDREN.
- One of the questions: How about non-profit websites such as archives and wikis that do not use ads and do not generate revenue? Are they part of this Ban as well? What if they do not have the framework for Age Assurance Checks? How would they able to establish a business license here? Would they ban archives from the PH Web? What about preservation of lost media? What about preservation of history and of stories? Or are we not allowed this also?
Note, Flickr mentioned by territorialfantail as among the possible platforms covered by the definition of "functionally equivalent digital service." As well as DeviantArt and Photobucket. The user also asks if "wikis" and non=profit websites (but allow user accounts and user interactions) are also covered.
- Final informatory note from me
Both Senate Bill 2424 and House Bill 11566 are still pending harmonization. Both have been passed on third and final readings in their respective chambers of Congress. Due to noticeable differences between two versions, they will be harmonized in a bicameral session. Furthermore, both measures still require the DICT to create implementing rules and regulations (IRR) within 90 days from the effectivity of the law (Section 27 of Senate Bill, Section 41 of House Bill) even after the president's signature, with participation from all concerned government and law enforcement agencies, child safety and psychiatric associations, the National Youth Commission, recognized child rights orgs, and other stakeholders.
_ JWilz12345 (Talk|Contributions) 15:50, 16 October 2026 (UTC)

