User talk:Jarekt

Archives

2007	2008	2009	2010	2011
2012	2013	2014	2015	2016
2017	2018	2019	2020	2021
2022	2023	2024	2025

Tech News: 2025-18

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Updates for editors

Event organizers who host collaborative activities on multiple wikis, including Bengali, Japanese, and Korean Wikipedias, will have access to the CampaignEvents extension this week. Also, admins in the Wikipedia where the extension is enabled will automatically be granted the event organizer right soon. They won't have to manually grant themselves the right before they can manage events as requested by a community.
View all 19 community-submitted tasks that were resolved last week.

Updates for technical contributors

The release of the next major version of Codex, the design system for Wikimedia, is scheduled for 29 April 2025. Technical editors will have access to the release by the week of 5 May 2025. This update will include a number of breaking changes and minor visual changes. Instructions on handling the breaking and visual changes are documented on this page. Pre-release testing is reported in T386298, with post-release issues tracked in T392379 and T392390.
Users of Wiki Replicas will notice that the database views of ipblocks, ipblocks_ipindex, and ipblocks_compat are now deprecated. Users can query the block and block_target new views that mirror the new tables in the production database instead. The deprecated views will be removed entirely from Wiki Replicas in June, 2025.
Detailed code updates later this week: MediaWiki

In depth

The latest quarterly Language and Internationalization Newsletter is now available. This edition includes an overview of the improved Content Translation Dashboard Tool, support for new languages, highlights from the Wiki Loves Ramadan campaign, results from the Language Onboarding Experiment, an analysis of topic diversity in articles, and information on upcoming community meetings and events.

Meetings and events

The Let's Connect Learning Clinic will take place on April 29 at 14:30 UTC. This edition will focus on "Understanding and Navigating Conflict in Wikimedia Projects". You can register now to attend.
The 2025 Wikimedia Hackathon, which brings the global technical community together to connect, brainstorm, and hack existing projects, will take place from May 2 to 4th, 2025, at Istanbul, Turkey.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 19:28, 28 April 2025 (UTC)[reply]

Deletetion of Q133456425

Hi, Jarekt! I didn't quite unterstand why you've deleted the wikidata qualifier Q133456425 in [file:Holy Family at the table.png]? Greetz! Bukk (talk) 07:57, 29 April 2025 (UTC)[reply]

Bukk, Yesterday I was working on files using {{Artwork}} template which are connected to deleted Wikidata items. I detected about 30 of them and I think all were added by you. I do not know the sequence of events, but it looks like you are adding an Wikidata item to the files, which link to items with no statements, which are then deleted by User:MisterSynergy. From what I understand it is impossible to detect for Wikidata users which Wikidata items are "used" on other projects. Files on Commons connected to deleted items, break stuff on Commons, and can not be easily fixed. My current approach is to reverse the edits adding deleted items. Are you creating those items on Wikidata? If so, why no statements? List of deleted Items:

--Jarekt (talk) 12:07, 29 April 2025 (UTC)[reply]

Hi, Jarekt! I create the wikidata items with the Quick Statements tool. Based on the data of the Commons date file the wikidata statments are created. Usally I do some editing manually such as "genre" or "collection". Then I copy the wikidata item and paste it into the Commons data file. This procedere doesn't produce any empty wikidata files without any statments. But perhaps I make a mistake in between. I shall check your list of wikidata items later. Greetz! Bukk (talk) 10:50, 30 April 2025 (UTC)[reply]

Template:Art_Photo - no_qs

Good morning Jarekt, thank you for your change. Just one comprehension question: What is the meaning of “|no_qs=1”. I could not find the parameter here (Is there a lack of quality assurance here?). Best regards Molgreen (talk) 04:24, 1 May 2025 (UTC)[reply]

@Molgreen: It is kind of a long story. All templates based on Module:Artwork share input parameters. They are also designed to create QuickStatement ("QS") commands if they have information which is missing on Wikidata. The QuickStatement commands can be used to copy the data to Wikidata by clicking on

icon. See any file in Category:Artworks with Wikidata item: quick statements. This whole system works best for images of artworks using {{Artwork}} or books using {{Book}} template. If a photo of a building is using {{Artwork}} or {{Art photo}} template, it is not wrong, but the QuickStatement commands can become nonsensical. The parameter "no_qs=1" is an easy way to turn off broadcasting QuickStatement commands and remove the file from Category:Artworks with Wikidata item: quick statements, so that no one presses the button to send wrong data to Wikidata. I agree with you that the parameter should be documented better, but it is hard to explain it's use without an essay. --Jarekt (talk) 12:21, 1 May 2025 (UTC)[reply]

Good morning Jarekt, thanks for the explanation. Would it be a good idea to suggest on the discussion page that the parameter is mentioned (explained) and refer to this discussion here? Best regards Molgreen (talk) 05:05, 2 May 2025 (UTC)[reply]

Commons talk:Photo challenge/themes

Hi there. At Commons talk:Photo challenge/themes, the bot keeps archiving "parking lots", but it's still an active discussion. Would you be able to help? Thanks! Magnolia677 (talk) 10:29, 2 May 2025 (UTC)[reply]

@Magnolia677: I restored the section, looked through all the settings documented at Template:Autoarchive resolved section and I do not see any obvious reason why the bot would be archiving this section. User:Euku runs User:SpBot maybe he can help. --Jarekt (talk) 12:47, 2 May 2025 (UTC)[reply]

Hi all! Thanks for reporting that! The bot merged the previous "Camelidae" section with the "Parking lots". It seems for the last 18 years nobody reported any issue with a headline like == {{Q-|Q6501349|capitalization=ucfirst}} == . There were two traps for the bot. The first is the = within the headline text. The second problem was the comment after the last ==. Both was not expected, but MediaWiki still eats it. This is fixed now. Euku:^⇄ 18:16, 4 May 2025 (UTC)[reply]

Tech News: 2025-19

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Weekly highlight

The Wikimedia Foundation has shared the latest draft update to their annual plan for next year (July 2025–June 2026). This includes an executive summary (also on Diff), details about the three main goals (Infrastructure, Volunteer Support, and Effectiveness), global trends, and the budget and financial model. Feedback and questions are welcome on the talk page until the end of May.

Updates for editors

For wikis that have the CampaignEvents extension enabled, two new feature improvements have been released:
- Admins can now choose which namespaces are permitted for Event Registration via Community Configuration (documentation). The default setup is for event registration to be permitted in the Event namespace, but other namespaces (such as the project namespace or WikiProject namespace) can now be added. With this change, communities like WikiProjects can now more easily use Event Registration for their collaborative activities.
- Editors can now transclude the Collaboration List on a wiki page (documentation). The Collaboration List is an automated list of events and WikiProjects on the wikis, accessed via Special:AllEvents (example). Now, the Collaboration List can be added to all sorts of wiki pages, such as: a wiki mainpage, a WikiProject page, an affiliate page, an event page, or even a user page.
View all 27 community-submitted tasks that were resolved last week.

Updates for technical contributors

Developers who use the moment library in gadgets and user scripts should revise their code to use alternatives like the Intl library or the new mediawiki.DateFormatter library. The moment library has been deprecated and will begin to log messages in the developer console. You can see a global search for current uses, and ask related questions in this Phabricator task.
Developers who maintain a tool that queries the Wikidata term store tables (wbt_*) need to update their code to connect to a separate database cluster. These tables are being split into a separate database cluster. Tools that query those tables via the wiki replicas must be adapted to connect to the new cluster instead. Documentation and related links are available. [1]
Detailed code updates later this week: MediaWiki

In depth

The latest Chart Project newsletter is available. It includes updates on preparing to expand the deployment to additional wikis as soon as this week (starting May 6) and scaling up over the following weeks, plus exploring filtering and transforming source data.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 00:11, 6 May 2025 (UTC)[reply]

Igenc Tech News

Hi Jarekt,
I've finally solved the issue mentioned here (at 'This coat of arms was created with Inkscape…important by xxx'), the “important” option creates a link that leads to a section of the manual with the aim of informing the user that his file is not optimized; the option is generated by the code “im”, its counterpart is the code “iz”, that informs the user that the file is indeed optimized, it's still visible on this file, just click on “optimized” to get to the help in question. It's likely that this attention wasn't correctly perceived by users, as the link wasn't visible, and I think I'll deprecate it when I get to the related extension ; also, the code “iz” is defined elsewhere than in Module:IgenCoa, probably at the top level, i.e. Template:Image_generation that the module depends on.
Which brings to the next point: Managing users in IgenCoa does indeed make it hard to maintain - I'm gradually reducing the number of ids, per each user's files managed in, also the categorization can also be done directly in the file by adjusting the options ; the advantage of user-categorization by igen code (directly in the file page) is to avoid categorization in a user's category of another user's files, when categories entered normally are copy-pasted from one file to another without verification, which happens frequently…
The next point, then, is that IgenCoa is just a part of Template:Image_generation, which doesn't only define CoAs but also logos, diagrams, flags, icons, seals, emblems, symbols, which is great, but the main issue is that it also defines tools and there are too many of them, some of which are barely used, example: this category handles many subcategories for a too-limited amount of files, then it might be relevant to merge the categorization of barely used tools (other than Adobe, inkscape, Corel, Txt, etc.) with Other tools, while retaining the icon on the file description
I'm not there yet. BR,--Kontributor 2K (talk) 10:23, 11 May 2025 (UTC)[reply]