Commons:Village pump/Archive/2026/06

Wiki Indaba 2026 – Scholarships & Program Call now open | Abidjan, November 13–15

Dear Wikimedians,

The call for applications for scholarships and the program of Wiki Indaba 2026 is now open.

This year, the conference will be held in Abidjan, Côte d’Ivoire, from November 13 to 15, 2026, under the theme “Africa’s Future: Knowledge Equity and Innovation”.

Wiki Indaba is the premier gathering of Wikimedians from the African continent and the diaspora. If you have a project, an experience, or an idea to share with the community, now is the time to submit your proposal.

Two applications are available: • Scholarship application → bit.ly/INDABA26_SCHOLARSHIP • Program proposal → bit.ly/INDABA26_PROGRAM

⏳ Deadline: June 30, 2026 at 11:59 PM GMT (for both)

We look forward to welcoming you to Abidjan! Abiba Pauline (talk) 21:36, 1 June 2026 (UTC)

1 petabyte of freely usable media files

Commons is close to 1 petabyte. Currently, the Special:MediaStatistics reads: "Total file size for all 142,471,025 files: 1,085,665,611,155,968 bytes (987.41 TB)". Congrats. emijrp (talk) 16:52, 1 June 2026 (UTC)

• Let me add a hint: You talk about pebibytes. A pebibyte is equal to 2⁴⁰ bytes or approx. 1.099 petabytes and a petabyte are 1,000 terabytes :) --PantheraLeo1359531 😺 (talk) 17:04, 1 June 2026 (UTC)

  Not really. I meant 1024 TB = 1 PB, thats why I said "is close to". We are not there yet, but will soon. Regards. emijrp (talk) 17:10, 1 June 2026 (UTC)

  That would be 1024 TiB = 1 PiB ;). Prefixes like k, M, G, T and P are SI prefixes with base 1000. The IEC prefixes like ki, Mi, Gi, Ti and Pi are IEC prefixes with base 1024. We cannot confuse the prefixes where a terabyte would be 1024 gigabytes but a teragram would be 1000 gigagram. 🙃 --PantheraLeo1359531 😺 (talk) 18:41, 1 June 2026 (UTC)

  Apparently Special:MediaStatistics has no problem with it, it uses TB, though you can report a bug if you want. emijrp (talk) 18:57, 1 June 2026 (UTC)

It would be great if Arch Mission Foundation could use several of these disks to store that petabyte in this facility, as they did with (the then current content of) English Wikipedia in 2024. Not because I fear a big apocalyptic event happening anytime soon, but as a last safeguard against other things that can (and, sadly, often do) happen. MGeog2022 (talk) 12:05, 3 June 2026 (UTC)

The demands for digital storage will increase fast. So this would be a good thing --PantheraLeo1359531 😺 (talk) 16:04, 4 June 2026 (UTC)

Less than 4000 media needing categories as of 2021

By now, less than 4000 media needing categories as of 2021, but we got stuck at the letter N and still have to categorize some difficult-to-categorise files in foreign languages. Do you want to contribute, to categorize the reminder, please? NearEMPTiness (talk) 05:11, 2 June 2026 (UTC)

The categorisation of the all media needing categories as of 2021 is nearing completion due to the work of @User:Stefan Kühn, @User:Prototyperspective, @User:Gbawden, @User:ProtoplasmaKid, @User:Krok6kola, @User:Jochen Burghardt and many other non-disclosed contributors. Now, we need to team-up once again, to categorize the media described in foreign languages, please. Should we then tackle all media needing categories as of 2022 or take a break? NearEMPTiness (talk) 04:11, 5 June 2026 (UTC)

I think we’re on the right track. If you look at the statistics, we’ve tagged about 120,000 files in four months. So we’ve reduced the large pile of uncategorized files by an average of about 7,000 files per week. If we all keep this up and don’t lose sight of the goal, we should have only a few files left by the summer of 2027. @NearEMPTiness: Thanks for always being so active in promoting this work. --sk (talk) 07:56, 5 June 2026 (UTC)

@NearEMPTiness (ping) --PantheraLeo1359531 😺 (talk) 15:11, 5 June 2026 (UTC)

We slowly reached the letter S. More help is required, please, to keep the ball rolling. NearEMPTiness (talk) 00:51, 6 June 2026 (UTC)

• I just handled a couple of images with Persian names (and Iranian subjects) but that had been held in Uncategorized media with description in Arabic language. There are probably more, because the scripts are nearly indistinguishable to non-readers; just a heads-up to any FA speakers to have a look in that category as well. (And possibly vice versa, not to mention the other languages with similar writing.)—Odysseus1479 (talk) 02:52, 11 June 2026 (UTC)

Resolved: All media of 2021 have been categorized. Thank you very much for your contributions. NearEMPTiness (talk) 05:28, 11 June 2026 (UTC)

This section is resolved and can be archived. If you disagree, replace this template with your comment. NearEMPTiness (talk) 05:28, 11 June 2026 (UTC)

Key for categories of Stolpersteine in Milan, Venice and probably in other cities too

Is it really useful to sort the Stolpersteine by the victim's last name? Because in my opionion it's a mess to leave some stumbling blocks sorted by the victim's last name while others (for example, photos with multiple Stolpersteine) aren't. Andrek02 (talk) 15:21, 6 June 2026 (UTC)

If it can be done consistently, it is presumably useful to bring multiple images of the same stone near each other, and also stones for multiple members of the same family. - Jmabel ! talk 22:28, 6 June 2026 (UTC)

Accidentally overwrote a crop

At File:Lorenzo and Henrietta Music.jpg, I was trying to crop the image and accidentally overwrote instead of uploading the cropped version separately. Can someone please fix this? TenPoundHammer (talk) 15:49, 6 June 2026 (UTC)

@TenPoundHammer: That's not difficult. Simply revert to the starting point (I did this already) and redo the crop. Please mind using the CropTool's Lossless mode to avoid a en:generation loss. Regards, Grand-Duc (talk) 16:23, 6 June 2026 (UTC)

Clarifying the closing time zone for Photo Challenge submissions and voting

I would like to raise a question regarding the closing time zone used for the Photo Challenge.

Recently, while handling the vote counting process, I noticed an inconsistency between the actual submission deadline and the wording currently used in the challenge pages. In practice, the submission period appears to close at 00:00 AoE on the 1st day of each month. However, the written description in recent months has stated the deadline as 00:00 UTC on the 1st day of each month.

There was also previous advice from experienced Wikimedians suggesting that the voting period should preferably end using AoE time, as this gives contributors around the world a more inclusive and predictable deadline. Nevertheless, the wording used in recent months has mainly referred to UTC.

This creates a potential ambiguity: contributors may understand the deadline differently depending on whether they rely on the actual timing, the page wording, or past practice.

I would therefore like to ask the community to clarify which time zone should be used as the standard closing time for the Photo Challenge:

• Option A: Use 00:00 AoE on the 1st day of each month as the standard closing time.
• Option B: Use 00:00 UTC on the 1st day of each month as the standard closing time.

My own view is that whichever option is chosen, the most important point is that the submission and voting pages should use consistent wording, and that the actual closing mechanism should match the stated deadline. This would help avoid confusion for participants and make future vote counting easier to manage.

Comments and suggestions are welcome, especially from users who have previously helped maintain or close the Photo Challenge pages. This is Taiwania Justo speaking (Reception Room) 13:29, 2 June 2026 (UTC)

how about for simplicity sake just set the deadline to UTC 00:00 2nd of each month? so every contest is always open exactly from 00:00 1st day of current month to 00:00 2nd day of next month UTC? RoyZuo (talk) 15:04, 3 June 2026 (UTC)

Thank you, I think this is a reasonable simplification, and it would certainly be easier to describe and implement than using AoE explicitly.

However, I think the effect is not exactly the same as AoE. Setting the deadline to 00:00 UTC on the 2nd would give some regions additional time beyond the end of the 1st in their local time zone, while AoE is specifically intended to close the contest only after the last time zone has passed the deadline.

Therefore, I would still slightly prefer using AoE if the goal is to handle global time zones fairly. That said, if the community prefers a simpler fixed UTC-based rule, then 00:00 UTC on the 2nd could be a workable compromise. The most important point is that the wording and the actual closing mechanism should be consistent. This is Taiwania Justo speaking (Reception Room) 04:08, 5 June 2026 (UTC)

everything utc would be actually fairer since everyone has the exact same period of time (1 month + 1 day) to submit. RoyZuo (talk) 08:11, 5 June 2026 (UTC)

 Support I don't know as I have an especially strong opinion as long as it's clear, but UTC is the de facto Internet Time Zone (and is generally when things on the front page of Wikimedia sites update), and being open from 0:00 UTC on the 1st day to 0:00 UTC on the 2nd day of the following month is unambiguous and easy to understand. — PeterCooperJr (talk) 20:10, 5 June 2026 (UTC)

@Jarekt: Since you have been involved in maintaining the Photo Challenge, I would appreciate your opinion on this issue, especially on the proposed UTC-based compromise. This is Taiwania Justo speaking (Reception Room) 05:59, 6 June 2026 (UTC)

User:Taiwania Justo, I do not have much of an opinion, I only know that original approach of advertising and enforcing 00:00 UTC resulted with a lot of unhappiness from people (mostly in the US) who think that deadline is at midnight but forget that it is midnight in London and they missed the deadline. I was rejecting large number of entries from last minute submitters and they were not happy. Quietly moving the real deadline by 12 hours, removed most late entries. So in Template:Photo challenge rules I would replace UTC with AoE. --Jarekt (talk) 14:47, 6 June 2026 (UTC)

Hmmm, here's my opinion: If the deadline is AoE, the period will be 1 month + 12 hours (current AoE = UTC-12), and 2nd day of the month UTC will be 1 month + 1 day. These options are ok for me. This is Taiwania Justo speaking (Reception Room) 11:18, 7 June 2026 (UTC)

Can Template:NoFoP-non-buildings-category be made?

In Wikimedia Commons, indication of FoP status templates are exist for buildings and public arts categories.

• {{FoP-category}}: For categories of buildings and public arts from a public space in a country that provides Wikimedia Commons-acceptable freedom of panorama
• {{FoP-buildings-category}}: For categories of buildings from a public space in a country that provides Wikimedia Commons-acceptable freedom of panorama for for architectural works only
• {{NoFoP-category}}: For categories of buildings and public arts from a public space in a country that does not provide Wikimedia Commons-acceptable freedom of panorama

After looking at these three templates, I suggest a template, {{NoFoP-non-buildings-category}}.

This is for categories of public arts from a public space in a country that does not provide Wikimedia Commons-acceptable freedom of panorama except for architectural work. (For example, Japan, United States, Finland, etc.)

And, this is intended to integrate {{NoFoP-Japan}}, {{NoFoP-US}}, {{NoFoP-Denmark}}, {{NoFoP-Finland}}, etc.

However, these countries have different criteria for distinguishing between works of arts and buildings.

For example, in Japan, if the exterior of a building, such as the Tower of the Sun, is treated as a work of art, it is treated as such. On the other hand, in the United States, works of art that are included as part of a building and treated as components of the building (e.g., if a column is shaped like a statue) are allowed on Wikimedia Commons.

How about {{NoFoP-non-buildings-category}}? --Ox1997cow (talk) 13:54, 6 June 2026 (UTC)

 Support but rename to something more professional. Suggested {{NoFoP-public art-category}}. Essentially, in all countries that only grant Commons-suitable FoP for images of architecture, almost all kinds of public art are not freely usable in photos, be it sculptures, murals, frescoes, paintings, and graffiti. My suggested wording:

This is a category of a copyrighted artistic work from a public space in a country that only provides Wikimedia Commons-acceptable freedom of panorama to images of architecture and not works of art in public spaces. Please do not upload more photographs or videos of such works, unless their presence is incidental or trivial to the overall image. If the work enters the public domain, please remove this template.

This should also mean redirecting all redundant template headers to this, such as {{NoFoP-US}} and {{NoFoP-Japan}}, and {{NoFoP-Denmark}}.

There is no need to enumerate the names of the countries (I think it's eight) with such FoP rules: Denmark, Finland, Japan, Malawi, Norway, Russia, Taiwan, and the United States. JWilz12345 (Talk|Contributions) 01:27, 7 June 2026 (UTC)

Then, how about {{FoP-buildings-category}} be renamed {{FoP-architecture-category}}? This will resolve the confusion with {{FOP-buildings-category warning}}. Ox1997cow (talk) 03:41, 7 June 2026 (UTC)

No need to rename that. "If it ain't broke, don't fix it," as a popular saying goes. There is no confusion. FoP-buildings-category suits the categories of modern buildings from those eight countries, while the template with warning suits the general categories of countries with no complete FoP (e.g. Azerbaijan and Ukraine, like "Buildings in Baku" or "Churches in Kyiv"). There are no issues in usage of these two as far as I know. JWilz12345 (Talk|Contributions) 04:23, 7 June 2026 (UTC)

Since the names of the templates are similar({{FoP-buildings-category}} and {{FOP-buildings-category warning}}), I thought about changing the name. Anyway, I will make {{NoFoP-public art-category}}. Ox1997cow (talk) 05:02, 7 June 2026 (UTC)

There are other types of architecture than buildings too, like bridges. Nakonana (talk) 13:23, 7 June 2026 (UTC)

@Nakonana@Ox1997cow I'd support the renaming. It appears in Japan, bridges are works of architecture, not just utilitarian engineering works. See this source used on COM:FOP Japan. JWilz12345 (Talk|Contributions) 14:50, 7 June 2026 (UTC)

What is it? Then, what is correct template name and contents of template? Ox1997cow (talk) 16:12, 7 June 2026 (UTC)

Just a simple renaming, to the category name you are proposing. Nothing else. JWilz12345 (Talk|Contributions) 03:18, 8 June 2026 (UTC)

I made {{NoFoP-public art-category}}. Then, When it integrate {{NoFoP-Japan}}, {{NoFoP-US}}, {{NoFoP-Denmark}}, {{NoFoP-Finland}}, etc? Ox1997cow (talk) 11:06, 8 June 2026 (UTC)

akg image

Anyone signed up with akg images? I'd like to add this 17th century PD-Art image to Commons, but you need to be signed up to akg to download the full resolution (2242 × 3364 px; 21.6 MB). Thanks! - MPF (talk) 12:17, 8 June 2026 (UTC)

@MPF: seems like it should be part of Category:Mughal album (muraqqa) (Louvre OA 3619). The Louvre has an alternative scan with a slightly different colour balance at https://collections.louvre.fr/en/ark:/53355/cl010371364 (5th image). --HyperGaruda (talk) 20:53, 8 June 2026 (UTC)

@HyperGaruda excellent, thanks! - MPF (talk) 21:21, 8 June 2026 (UTC)

@HyperGaruda added now as File:Perroquet rouge 1600-1615.jpg, though the Louvre source is much lower resolution than the akg copy (so if anyone wants to upload the akg copy, either on top or as a separate file . . .) - MPF (talk) 23:32, 8 June 2026 (UTC)

Court Order Concerning Commons Image Related to the 2026 Onikişubat School Shooting

Dear Community Members,

We write to you on behalf of the Legal Department of the Wikimedia Foundation regarding certain developments in Turkey relating to an image currently hosted on Wikimedia Commons concerning the 2026 Onikişubat school shooting.

On April 29, 2026, the Wikimedia Foundation was informed of a takedown order by the Muğla 2nd Criminal Judgeship of Peace, via the Turkish Information and Communication Technologies Authority. The Foundation was directed to take down an image titled "İsa Aras Mersinli, perpetrator of the 2026 Onikişubat school shooting", from Wikimedia Commons. The image is a blurred photograph, sourced from X/Twitter, which - according to its uploader - appears to show İsa Aras Mersinli, the perpetrator of a school shooting that occurred in the Onikişubat district of Kahramanmaraş Province on April 15, 2026. We understand that the image was nominated for deletion on April 15, 2026, and on May 8, 2026, the discussion was closed with a decision to retain the image. The user who closed that discussion concluded  that the image was educationally valuable and did not violate any of the community's applicable policies, including the COM:DIGNITY and the Identification guidelines.

The Foundation took note of the deletion discussion, and we also reached out to a member of the Volunteer Response Team for input. On May 12, 2026, the Foundation filed an appeal before the Higher Court Muğla 1st Criminal Judgeship of Peace. That appeal was subsequently rejected.

As we explore our limited legal options at this stage, we are notifying the community of these developments for two reasons:

• First, to keep you informed: we want to ensure that the community is aware of this development, and what has been done so far by the Foundation.
• Second, to prompt further discussions: we know that the deletion discussion received relatively limited participation, divided opinions, and covered issues not related to the Order (such as the intellectual property rights of CCTV owners). Other community members may have been unaware, and now may feel motivated to have their say. Whether the deletion discussion is reopened or not, your views on the importance of this particular file to the projects can inform our own strategy. Note in particular that other media hosted on Commons is not subject to this Order, and Wikipedia was already preferring to use other photographs. You should also consider the possible consequences of noncompliance with such an order; for now, we will not publicly speculate, but we do want you to understand that what is said and done here could have consequences beyond this particular image.

While we appreciate the reasoning reflected in the late April/early May's deletion discussion, there is also some local context and sensitivities surrounding the image that are worth noting. The investigation into the incident remains ongoing. There are reasons to believe that it was a copycat crime inspired by past shootings. Significant amounts of disinformation, shooter-glorification and calls for further school attacks apparently circulated online. Under Turkish law (including Article 24 of the Turkish Civil Code), the display of graphic or traumatic images may raise concerns relating to personal rights, privacy, and dignity, depending on the circumstances.

In that context, the Radio and Television Supreme Council/RTÜK has issued a public statement concerning content related to the Onikişubat school shooting. In that statement, RTÜK advised that traumatic footage and content violating the privacy of victims, students, or their families should not be broadcast. RTÜK further emphasized the importance of relying on official statements to avoid misinformation and urged media outlets and publications to remain mindful of public sensitivities and the psychological well-being of children.

This Village Pump post is not an instruction or direction for any specific editorial action or outcome. The Foundation fully respects the independence of the Wikimedia community in editorial content-governance matters.

That said, the Order is addressed to Wikimedia, so the Foundation must make its own assessment of its legal obligations, litigation risk, and the broader interests of the Wikimedia projects and the community. Community decisions under the community's own content policies are an essential part of how the projects are governed, and help inform the Foundation's legal strategy. However, these determinations, by themselves, are not binding on the Foundation's assessment of the action(s) it may need to take in response to a court order.

Accordingly, depending on the legal options available and the Foundation's assessment of the risks involved, the Foundation may take appropriate action under the Terms of Use, including an Office Action, where necessary to safeguard the projects, the Foundation, and the Wikimedia community more broadly.

We believe that constructive engagement with the community will help reach a resolution that appropriately considers the educational value of the image as provided under, community governance principles, local legal risks, and the long-term interests of the Wikimedia projects. For reference, please also take a look at the Legal Department's earlier note titled "Educational use rationales for controversial content" (here).

Thanks, BChoo (WMF) (talk), on behalf of the Wikimedia Foundation's Legal Department 23:48, 6 June 2026 (UTC)

Sigh, we are really gonna end 2026 with Commons being censored by every major Western country in the world huh? Trade (talk) 04:04, 8 June 2026 (UTC)

@BChoo (WMF): Are you able to share the content of the takedown order, the WMF appeal, and/or the rejection of that appeal? Omphalographer (talk) 05:16, 8 June 2026 (UTC)

We recently had many cases they show, that we need better procedures when dealing with privacy related issues. I think we definitely need a kind of community committee to decide such cases. GPSLeo (talk) 05:52, 8 June 2026 (UTC)

I dont feel our user base is large enough to justify a community committee in the first place, let alone for such a narrow topic. It works on ENWP for obvious reasons Trade (talk) 06:06, 8 June 2026 (UTC)

The DR was reopened for a third time yesterday. Those interested in the legal and privacy related arguments being relayed by WMF Legal can give opinions there. In effect that does make a "kind of community committee".

See Commons:Deletion requests/File:İsa Aras Mersinli, perpetrator of the 2026 Onikişubat school shooting.png --Fæ (talk) 06:17, 8 June 2026 (UTC)

BTW, Category:COM:DIGNITY-related deletion requests seems a useful category to review when discussing privacy related cases, and this DR is in it. Where there is unreasonable invasion of privacy, Commons policies do and should respect these aspects of the law. Fæ (talk) 11:21, 9 June 2026 (UTC)

Maybe one could draw the community's attention to such privacy related DRs by making it a habit to post a thread on VP about the existence of such a DR. Nakonana (talk) 08:07, 8 June 2026 (UTC)

ZoomViewer tool not working

Posted on the talk page for the tool, but reposting here because it says that page isn't monitored much. The ZoomViewer tool has never worked for me on any image, regardless of the browser used. Even the examples on the help page do not work, the page gets stuck on the 'processing image' screen and never loads the image. Do others also have this problem? The tool would be very helpful in viewing large images that browsers are otherwise unable to handle. Surajr7 (talk) 22:17, 8 June 2026 (UTC)

I can confirm it also doesn't work for me either. It looks like the current listed maintainers are User:Tim Starling, User:Tacsipacsi and User:Dschwen. In addition to the main thing being broken, the iff endpoint is also giving an error. [1]. Bawolff (talk) 01:21, 9 June 2026 (UTC)

As I said on the talk page, it's likely that it was broken by administrator intervention on December 24, 2025, as an emergency action related to its enormous disk space usage. There was no log entry, but see this discussion from May-June 2025 for context. If it takes 6 months for someone to notice and report that the tool is fully broken, it's really hard for me to justify spending any more time on it. There are a lot of things I could work on that would be of value to users pretty much every day. Tim Starling (WMF) (talk) 03:05, 9 June 2026 (UTC)

Given Tim's comment, i guess we should remove the link to the tool from {{LargeImage}} Bawolff (talk) 04:36, 9 June 2026 (UTC)

Thank you for the reply Tim Starling (WMF). I agree that trying to fix the ZoomViewer tool is a waste of time, the button is sort of hidden and probably rarely used. With that said, I think a built-in zoom function is badly needed and would see a lot of use. For example, the featured articles en:The Garden of Earthly Delights and en:Las Meninas get about 50k views per month each. The lead images (both featured pictures) are extremely high quality, near giga-pixel images. However, few users will ever be able to appreciate these high quality images. They take forever to load in-browser — if they do at all – and few will want to download an over 200MB image. These thousands of high quality images that have high use across Wikimedia projects essentially sit there unused because they are inaccessible to most users. Thanks, Surajr7 (talk) 06:12, 9 June 2026 (UTC)

Ah, I see a zoom feature is already in development. In my opinion development of the feature should be prioritized since it would see a ton of use and greatly add to the accessibility of images. Thank you for all the work you guys do Surajr7 (talk) 06:15, 9 June 2026 (UTC)

You should not interpret that phab task as indicating that any sort of zoom feature of very large images is currently under active development. Bawolff (talk) 06:20, 9 June 2026 (UTC)

I see, sorry I am not technical person. Is there a way to request that development of the proposed feature become active? I am talking about a general zoom function for all images, not just for very large ones. Surajr7 (talk) 06:42, 9 June 2026 (UTC)

Meta:Community Wishlist i suppose. Bawolff (talk) 11:27, 9 June 2026 (UTC)

New userscript: Cat-WD-Linked

Hi. Just finished writing a userscript that adds a menu item "Category WD links" to the tools menu of category pages on Commons and Wikipedia. Clicking it checks which subcategories are linked to Wikidata and checks if those items have P910 or P301 claims. It can be found at wikidata:User:Infrastruktur/cat-wd-linked.js. If you have any feedback, either use my Wikidata talk page or ping me because I'm not active on Commons. Infrastruktur (talk) 06:46, 9 June 2026 (UTC)

Deployment of Legal and Safety Contacts Link in the Footer of Your Wiki

Hello community,

The Wikimedia Foundation has provided a single legal and safety contact page, to be linked in the footer of your wiki, to ensure access to accurate legal information. This is a regulatory requirement.

We have already rolled out links to English, German, Italian, Spanish Wikipedias and other wikis and we will deploy to your wiki soon.

Please read more on the project page and leave any comments in this thread or on the talk page. –– STei (WMF) (talk) 17:20, 9 June 2026 (UTC)

Good. Those have been terribly hard to find. - Jmabel ! talk 04:38, 11 June 2026 (UTC)

Request for speakers of Indian languages: which language is this video?

File:President Trump Participates in a Bilateral Meeting with the Prime Minister of the Republic of India.webm. Narendra Modi is a Gujarati, but my assumption is that he's speaking Hindi since this is for a broad audience. Can someone please confirm that it's Hindi and delete the HTML comment that I added or replace Category:Videos in Hindi with the correct language? Thanks/धन्यवाद. ―Justin (koavf)❤T☮C☺M☯ 20:02, 17 June 2026 (UTC)

Yes, it is Hindi. ङघिञ (talk) 09:24, 20 June 2026 (UTC)

Lovely. ―Justin (koavf)❤T☮C☺M☯ 10:05, 20 June 2026 (UTC)

This section was archived on a request by: ―Justin (koavf)❤T☮C☺M☯ 10:05, 20 June 2026 (UTC)

Wiktionary logo

I wanted to upload a Wiktionary logo I designed for Norfuk-Pitkern Wiktionary, but it is not letting me upload because 'It is a copy of File:WiktionaryEn.svg' when it is a file derived from it. Thanks, ङघिञ (talk) 09:27, 20 June 2026 (UTC)

Sorry, it uploaded, turns out I mistakenly was going to upload the original file. ङघिञ (talk) 09:40, 20 June 2026 (UTC)

This section was archived on a request by: Andy Mabbett (Pigsonthewing); Talk to Andy; Andy's edits 12:32, 20 June 2026 (UTC)

Is it worth running OCR on full newspaper pages?

Is it worth running OCR on full newspaper pages like: File:"Scenes Taken at Huge $2,000,000 Pier Fire" Evening Vanguard, January 7, 1924.jpg, or just hope someone in the future breaks it down into the individual news articles? The Library of Congress does entire pages but it is of limited usefulness. --RAN (talk) 16:14, 11 June 2026 (UTC)

That's something for Wikisource to care about. Bedivere (talk) 22:37, 12 June 2026 (UTC)

Here's a sample of what an OCR does with it, so probably not worth the effort as the output is so buggy.

ye

MONDAY,    J ANUARY:   1

ief Congratulated for
Coolnezs Under -
* Fire
Officer Mer of the’ Venice police |.
‘ce turmed in the alarm of the |
ean Park fire yesterday at 9:50 |
m. when he phoned.tc Captain {
go.at the station hore, news: of |
spreading disaster.
here was troubje on the police |
@phone atid Officer De Villa, of |
D motor¢ycle corps rushed to the |
@cpartment and got Engine |
. 2-cf Company. No. 1 away in|
16 to be first at the blaze.
oung McCauslang, son of Chief
Police H. H.  McCausland,  who |
at the station, sped cn the |
nds of putting in an emergency. :

for every officer cn the force
turn get.               -.
The first consideration of: the of-
rs and orders given by Captain
go were for the roping off of
» lines ‘to keep the sight secing
blic: out’ of the fighting zones.
vaptain. Lingo drew on his ex-
ience af September 1912, when
was chief of police of the Ven-
force’ to tackle the early
ases of the work at the fire. -

ief of Police H. H. McCaus- |
hd, whd w

If you want to research how it can be done, this was using pytesseract with an "automated page segmentation" setting, more info. Fæ (talk) 20:14, 14 June 2026 (UTC)

• It is imperfect, as is the OCR done by the Library of Congress at Chronicling America. I tend to find better OCR at Newspapers.com. Newspapers.com reran all their OCR recently using newer software. You can pick out a person's name in your example, and that just might be what someone is looking for. Otherwise the few thousand newspaper page images we already host, are just decorations. --RAN (talk) 22:21, 15 June 2026 (UTC)

Who can help to categorise the 22,000 media items from 2022?

In the category All media needing categories as of 2022 are approximatels 22,000 items that need to be categorised. In February 2025, there were still 80,000 – so we are making good progress. Experience shows that the final quarter is particularly difficult and requires not only knowledge of categorisation but also the ability to read foreign characters. Tips on this can be found in the WikiProject Minimum One Category. Who is able and willing to help with this, or has a good idea on how it can be done most effectively? --NearEMPTiness (talk) 07:03, 13 June 2026 (UTC)

While I appreciate the intention, I am not sure I fully agree with some of the results of the previous round. I noticed a lot of files moved from one pile of uncategorized mess to another pile of essentially uncategorized mess (now in two flavours: Category:Unidentified locations and Category:Unidentifiable locations). Fine if it is combined with some generic category to describe the subject, but not as the only category (e.g. File:DSC 0147 (35990764463).jpg could have at least gone into some building category if one does not know it is Category:Osaka Castle). --HyperGaruda (talk) 08:39, 13 June 2026 (UTC)

I agree, looking Category:Unidentifiable locations, I can clearly see some images literally has the locations in their filename. For example:

• File:Darhal Valley.jpg
• File:East Shore Park.jpg
• File:Gate D of banshankari metro.jpg
• File:Lohajung Village with snow in January.jpg

So, not sure why these are "unidentifiable", and not placed in the correct category in the first place. Thanks. Tvpuppy (talk) 09:54, 13 June 2026 (UTC)

Yes, the objective is, to put the files into the most appropriate category, not only into an unidentified category. However, even the latter is useful, for instance, when an expert is needed to identify animals or plants. NearEMPTiness (talk) 12:13, 13 June 2026 (UTC)

• Category:Unidentified men has the same problem, the person may be identified in the caption or the image title, and is just missing a category for a person. --RAN (talk) 22:25, 15 June 2026 (UTC)

Flat lists

Do we have a category that contains all the flat-list categories? RAN (talk) 15:39, 14 June 2026 (UTC)

Sorry if this seems pedantic or rude, but I'm not sure how to word this. Can't you easily answer your own question by going to a flat category (e.g. Category:Surnames (flat list)) and seeing yourself that it is in Category:Flat categories? Is there something that I'm missing? ―Justin (koavf)❤T☮C☺M☯ 15:41, 14 June 2026 (UTC)

• Probably because we call the concept "flat lists" and we call the categories "Category:Flat categories". Solved with a new and simple redirect, Category:Flat lists redirecting to Category:Flat categories. --RAN (talk) 21:00, 15 June 2026 (UTC)

Which license to use by conferences?

I participated to an EPF conference and the organisers make the pictures taken during the conference available free of use.

Quote: SwissTransfer link with pictures taken by our photographers. You are free to use these photographs in any external communication. This link is valid for one month. :End Quote

https://www.epf.eu/wp/epf-confereepf-conference-2026-advancing-sustainable-passenger-mobility-across-europe/

Wich license should I use?

PS: There is Category:European Passengers' Federation (EPF) (my own pictures in past conferences)

Smiley.toerist (talk) 09:31, 10 June 2026 (UTC)

If someone is bold, they could say that this quote authorisation amounts to {{Copyrighted free use}}. But we should apply COM:PRP, which makes that statement from whoever insufficient for our purposes. It would be better if you could get a clear license name, maybe a statement that the media are made available under e.g. the CC-By-SA 4.0. I would actually refrain from a Commons upload for now. Regards, Grand-Duc (talk) 10:50, 10 June 2026 (UTC)

I am a member of the organisation wich organized this conference and know most of organizers personaly, so it would be no problem to confirm the authorisation. At the conference itself the policy about the availibility of the presentation slides and pictures taken was make public. There are lots of pictures of the speakers/presentations. Most of the speaker names are in the conference agenda, but if their is doubt who is in the picture I can ask.Smiley.toerist (talk) 09:39, 11 June 2026 (UTC)

@Smiley.toerist: you will have to make sure that the conference organisers actually have the intellectual property rights that the photographers own at first when making their images. They can be transferred, but that transfer must be documented, in writing. Furthermore, this rights transfer must allow for a free license. Ideally, any conference photographer did transfer "all economic exploitation rights" (or made a rights transfer with a wording of similar or broader meaning) to the conference organisation. That way, it's within the purview of you and your colleagues to grant a license (as the photographers did transfer that right beforehand). Regards, Grand-Duc (talk) 14:34, 11 June 2026 (UTC)

Its not our business to investigate if the internal paperwork of the organisation is correct. The photographers where not professionals, but members who where tasked to take pictures of the event, for use by the organiser. So wil ask the organiser to confirm a cc-by-sa-4.0 license, wich I will be using.Smiley.toerist (talk) 12:14, 12 June 2026 (UTC)

Per C:PCP, it is our business. The conference took place in Maastricht so Dutch copyright law ("auteursrecht") applies and that is pretty straightforward: Rights stay with the author unless it's explicitly transferred. You have to provide proof that's the case if you have the organizers provide the license. Probably better to have the individual photographers provide a license for the photos they took. Multichill (talk) 19:34, 12 June 2026 (UTC)

We do accept the GLAM claims that what they released to us, is public domain. (Unless we have evidence it is not). And if an organisation claims its pictures are free to use, we dont accept it. We are splitting hairs now and being more catholic than the pope.Smiley.toerist (talk) 22:01, 12 June 2026 (UTC)

GLAM institutions are (often) used to deal with intellectual property rights and have (often) some expertise in it. This cannot be reliably surmised for some associations organising conferences (unless it's e.g. a conference by attorneys in IP law). Regards, Grand-Duc (talk) 22:18, 12 June 2026 (UTC)

The law does not apply automaticaly for employees or volonteers working for an organisation. If people having a working relationship (employment) with the organisation get an assignment to take pictures for the organsation, the organisation gets the full authorship rigths, unless otherwise specified.Smiley.toerist (talk) 11:45, 14 June 2026 (UTC)

@Smiley.toerist: for employees or contractors that varies by country, and I'm not offhand aware of any country where volunteering for an organization would automatically assign them your copyrights. It certainly does not in the U.S. - Jmabel ! talk 22:15, 14 June 2026 (UTC)

In practice, volunteers and employees, will be wel advised to mention any restrictions, payments etc on their pictures, before they take the pictures. If there are limitations, the employer wil ask somebody else to do the work. If they demand their legal rigths afterwards, they wil jeopardise their work relationships with their employers. So these rigths are more theoretical. In practice most of these things are done informaly. Professional photographers wil make their conditions clear before any fotosession.Smiley.toerist (talk) 11:01, 16 June 2026 (UTC)

And, in practice, if an organization wishes to obtain copyrights in a situation like this, they would also do well to have contract terms to that effect. I've done a moderate amount of photography (in the U.S.) as a contractor in situations like this. I can't remember ever having to sign over copyrights, though I've certainly signed over very liberal usage rights, even sometimes including that I do not have to be credited on use by the organization itself. - Jmabel ! talk 18:28, 16 June 2026 (UTC)

Dashed lines in GEOJSON pages?

Is it possible to add dashed lines to a GEOJSON map data page? If it is possible, how? If it isn't possible, how could the feature be implemented? —TheGinger68 ↗ 20:38, 14 June 2026 (UTC)

Styling in these maps are defined in the simple style spec, and there’s no provision therein for dashed lines. Opening an issue on that GitHub page might get the right people to start thinking about it, but I’m not the one to be promising anything on that front. BMACS1002 (talk) 04:43, 16 June 2026 (UTC)

It’s been an open feature request for a long time. I wouldn’t be surprised if another existing implementation of the specification implements a dash pattern option unilaterally though. Minh Nguyễn ^💬 04:58, 16 June 2026 (UTC)