Commons:Village pump/Technical/Archive/2026/07

"Show changes" not working correctly

When I edit a file page, "Show changes" is giving me the same view as "Show preview". There appears to be no way to examine what I've changed without saving. This is recent (almost certainly within the last 48 hours or so). - Jmabel ! talk 19:38, 2 July 2026 (UTC)

Seems to be working for me, but maybe it only happens for certain wikitext editors or gadgets. Bawolff (talk) 14:33, 3 July 2026 (UTC)

And it's back to working for me. Who knows... - Jmabel ! talk 22:21, 3 July 2026 (UTC)

This section was archived on a request by: Jmabel ! talk 22:21, 3 July 2026 (UTC)

Get list of files uploaded by user

Can I get a list of current filenames of files uploaded by $user from the API?
I tried https://commons.wikimedia.org/w/api.php?action=help&modules=query%2Blogevents but this returns filenames as they were when uploaded, so results include redirects. Does this have to be done in two steps? - Alexis Jazz ^{ping plz} 05:06, 4 July 2026 (UTC)

you can also use list=allimages https://commons.wikimedia.org/w/api.php?action=query&list=allimages&aisort=timestamp&aiuser=Bawolff . If you want to use logevents, did you consider using it as a generator? Bawolff (talk) 07:40, 4 July 2026 (UTC)

Bawolff, thx, list=allimages worked!
I didn't want to use logevents, I just looked at how COM:VFC accomplished it. I don't know what "use as a generator" means. - Alexis Jazz ^{ping plz} 10:33, 4 July 2026 (UTC)

Its kind of a moot point, as i didn't realize, but logevents cannot be used as a generator. In general though, the generator parameter of the api lets you feed the results of a list module into one of prop modules. Bawolff (talk) 17:30, 4 July 2026 (UTC)

Is it possible to significantly change an SVG source code without changing the visual output visibly?

I mean the output would be identical or visually imperceptible to most. I just want to know if this is possible. Candidyeoman55 (talk) 09:42, 4 July 2026 (UTC)

Candidyeoman55, yes.
Why? - Alexis Jazz ^{ping plz} 10:34, 4 July 2026 (UTC)

There were a few discussions regarding some high profile logos which I ended up in on English Wikipedia (the NBA logo and the Chicago Bulls logo). These logos are now labeled as fair use, but the discussion was about whether those logos (American logos published before 1978) had a copyright notice or not, therefore making them public domain in the US.

However, three users (999real, Based5290 and Howardcorn33 - which I think may be sockpuppets or co-ordinating in another way) pushed the discussion into uncomfortable territory for me: Whether SVG codes could be possibly "copyrighted". I mentioned this page to them to see if this would convince them, as my argument is that we should use the official vectorizations (if properly done and available) for logos (due to my concerns inspired by the case of when Tesla tried to get their logos removed from Wikimedia Commons), but these three users insisted. I can see the damage they can do to Wikimedia projects: If they get their way, rasters and improper SVGs (such as autotraced) could end up being used in high profile pages instead of the official properly done one, and that to me is unacceptable. I hope any damage they do or might do to the projects is reverted quickly.

We should use the precedent we have for paintings in my opinion. Candidyeoman55 (talk) 11:15, 4 July 2026 (UTC)

And one even uploaded an auto-traced version to Commons, which was done, according to him, on vectorizer.ai, which is a paid service of AI autotracing, which is not consistent to me. I'll nominate the file for deletion. Also, two of these users now have "retired" as their label on their user pages and the other doesn't have a user page. Candidyeoman55 (talk) 11:19, 4 July 2026 (UTC)

Actually the Tesla image WMF deleted was on the grounds of it being the exact same as with the copyright office, so keeping those does not seem smart. See Commons:Office actions/DMCA notices/2025#c-Jrogers (WMF)-20250603140300-Odder-20250530171800. You could try to make a claim about derivitive work on a redrawn logo, but that argument will not work on the original. Writing that and knowing how AI is coded and trained, I would not dream of calling any of it´s works derivitive.

Also note that Coats of arms are free because they are drawn from descriptions of the coat of arms. The original is not free. Snævar (talk) 15:59, 4 July 2026 (UTC)

Delinker log not working?

The delinker log has not been working for me over the last week at least (here is an example). Has anyone else been having a problem with it? IronGargoyle (talk) 15:54, 4 July 2026 (UTC)

IronGargoyle, CommonsDelinker hasn't edited anything since 26 June 2026. See User talk:CommonsDelinker#Where art thou? - Alexis Jazz ^{ping plz} 01:52, 5 July 2026 (UTC)

@Alexis Jazz: Are things getting delinked by another bot? Is there a log somewhere for this? IronGargoyle (talk) 02:39, 5 July 2026 (UTC)

IronGargoyle, on most projects nothing is getting delinked. File:Marguerite Moreau 2001..png and File:Stuart Townsend 2001..png were uploaded at 11:14 and 11:15 yesterday, nearly 18 hours ago. Watch w:es:Before I'm Dead for bot activity.
There's w:en:Special:Contributions/Filedelinkerbot which is still operational and active on enwiki, hewiki, kowiki and metawiki. - Alexis Jazz ^{ping plz} 03:02, 5 July 2026 (UTC)

That's really unfortunate that delinking isn't happening either. I hope the log can be retrieved at some point. Filedelinkerbot is fine for delinking stuff, but it didn't play well with the (now non-functional) delinker log. IronGargoyle (talk) 03:10, 5 July 2026 (UTC)

IronGargoyle, it has its own log: https://krdbot.toolforge.org/cgi-bin/Delinkerlog.php - Alexis Jazz ^{ping plz} 03:56, 5 July 2026 (UTC)

File:Rothschild Extinct Birds.djvu does not render thumbnails

For some reason the File:Rothschild Extinct Birds.djvu fails to render thumbnails both here in Commons and in Wikisource. As a result it cannot be transcluded to the mainspace, see s:Extinct Birds. In other similar cases it usually helps when the cache of the file's page is purged, but here it does not help either. Any idea what is happening and how to solve it? -- Jan Kameníček (talk) 19:35, 5 July 2026 (UTC)

Note that in the past it must have worked well, otherwise its indivudual pages could not have been proofread. See e. g. here where the page's thumbnail on the right is not rendered now, but it must have been rendered in the past as there is the transcribed and validated text on the left. --Jan Kameníček (talk) 19:58, 5 July 2026 (UTC)

Works fine for me. - Jmabel ! talk 01:51, 6 July 2026 (UTC)

Yeah, I have just noticed at another discussion that M-le-mot-dit reuploaded the file, and then it started working again. -- Jan Kameníček (talk) 17:48, 6 July 2026 (UTC)

Tech News: 2026-28

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

• View all 34 community-submitted tasks that were resolved last week. For example, an issue where the search bar results on Wikidata, showed English results instead of using the correct language fallback for users of language variants, has now been fixed. Search suggestions will now follow the expected language fallback chain. [1]

Updates for technical contributors

• In preparation for Celebrate Women campaign planned for March 2027, the Wikimedia Foundation’s Content Enablement team has launched a 22-question survey to better understand technical contributions by women+ (anyone who identifies as a woman) across Wikimedia projects. The survey takes approximately 15–20 minutes to complete and will remain open until 20 July 2026. The questions are also available on-wiki for review in advance.
• The Score extension now supports rendering music scores as SVG images in addition to PNG, addressing a long-standing feature request and resolving historical image quality issues. Both formats are now provided to clients, with PNG in the src attribute and SVG in the srcset attribute.
• The new Parsoid parser continues to be deployed to additional wikis, making it easier to introduce new reading and editing features. It was enabled on French Wikipedia, bringing total progress to covering 78.9% of Wikipedia page views. Rollout to English Wikipedia desktop will progress through this week.
• Detailed code updates later this week: MediaWiki

In depth

• The Wikimedia Hackathon 2026 recap blog post is now live. It highlights the projects, sessions, and social activities from this year’s event, and shares initial plans for the 2027 Wikimedia Hackathon.

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

MediaWiki message delivery 13:54, 6 July 2026 (UTC)

Media of the day missing from front page

See Commons_talk:Media_of_the_day#July_8,_2026_missing. TheFeds 03:02, 8 July 2026 (UTC)

PNG preview is creating WEBP

For some reason png preview, for example File:Flag of the United Kingdom (1-2).svg, is creating webp files. LoneShadow42 (talk) 19:34, 7 July 2026 (UTC)

@LoneShadow42 Yes, WMF recently changed the thumbnail logic to always use webp thumbnails for SVGs when possible. https://gerrit.wikimedia.org/r/c/operations/puppet/+/1306395 AntiCompositeNumber (they/them) (talk) 03:14, 8 July 2026 (UTC)

Thank you. I'm not sure where to report it, but, it still says "Size of this PNG preview of this SVG file:" below the image. LoneShadow42 (talk) 03:41, 8 July 2026 (UTC)

@LoneShadow42: I've opened phab:T431559 to track that. It's probably a short term situation, because ideally MediaWiki would always know what file type is being served. SWilson (WMF) (talk) 10:48, 8 July 2026 (UTC)

Radio buttons missing from History pages

For the past couple of days, on every History page I’ve visited the radio buttons that allow selection of the first & last edits to compare are missing—each line showing just a blank space between the “(cur | prev)” links and the timestamp. This prevents the display of any diff between non-consecutive edits. I have not changed my preferences, scripts or styles recently. Any ideas what might have happened or, more practically, how I can get these buttons to show again?—Odysseus1479 (talk) 22:49, 8 July 2026 (UTC)

What browser are you using, on what OS? Have you looked at all with the browser debugger tools to see whether they are hidden by styles or actually missing from the HTML? - Jmabel ! talk 00:53, 9 July 2026 (UTC)

Safari v17.6 on MacOS 14. Sorry, I wouldn’t know what to look for in the page source or resources. I did try switching from my usual Vector 2010, for which I have custom CSS, to the default 2022 (and back) but it made no difference.—Odysseus1479 (talk) 02:02, 9 July 2026 (UTC)

@Odysseus1479: In the page source, you'd be looking for a section that begins with <ul class="mw-contributions-list"> and ends with </ul>. I happen to know that File:Capital in Cuxa Cloister (MET 25.120.617) 01.jpg, which I uploaded, is a page without too much history (6 versions). If you could reproduce the mw-contributions-list section of its history page here, we might learn something, or at least eliminate some possibilities. (As you can imagine, really hard to try to debug via a conversation like this.)

Or maybe someone else with a similar environment to yours might have some insight? - Jmabel ! talk 04:54, 9 July 2026 (UTC)

Thanks. I’m hesitant to dump all that in here—the tags in question cover almost all the ‘guts’ of the page. There are three such sections: the first comprises 69 lines of code (inclusive of the opening & closing) and corresponds to the most recent edit; the second, of 64 lines, is for the next most recent; and the third covers all four earlier edits in 191 lines. Perhaps most of interest, though, are the pairs of lines that look like this:

<input type="radio" value="1169030053" disabled="" name="oldid" id="mw-oldid-null">
<input type="radio" value="1169030053" checked="" name="diff" id="mw-diff-1169030053">

from the first section,

<input type="radio" value="1167684487" checked="" name="oldid" id="mw-oldid-1167684487">
<input type="radio" value="1167684487" name="diff" id="mw-diff-1167684487">

from the second, or

<input type="radio" value="1135352884" name="oldid" id="mw-oldid-1135352884">
<input type="radio" value="1135352884" name="diff" id="mw-diff-1135352884">

from the third. (As might be expected, the third section contains three more such pairs; they look just like the last example except for the diff IDs.) Does that tell you anything, or do you need more context?—Odysseus1479 (talk) 20:25, 9 July 2026 (UTC)

It tells me the problem is not in the HTML as such which, in this respect, is identical to what I see on my machine.

Most likely, if you can't see those buttons there is a stylesheet problem of some sort, but if no one else can replicate it and you are not comfortable using a browser debugger and don't have access to someone else who can, there is little hope of working out what the problem might be.

Less likely, but not impossible, is that your particular browser is somehow misinterpreting a stylesheet. That would be a serious browser bug. Is there someone else reading this who has Safari v17.6 on MacOS 14 and can either say that they do or don't have the same problem? - Jmabel ! talk 04:54, 10 July 2026 (UTC)

Thanks again. I’m pretty sure now something has broken in my browser’s UI resources: I had occasion to visit a government registry’s search page today, one I’ve used many times before, and the form did not display any of the checkboxes that are usually there (and do show in Firefox). OTOH the minor-edit and watch-page checkboxes in this edit window show normally, and I think they ought to be the same kind of control, which is puzzling. At any rate it seems unlikely to be MW-related, especially considering nobody else has reported similar problems AFAICT.—Odysseus1479 (talk) 20:18, 10 July 2026 (UTC)

hCaptcha problem; more widely, privacy and surveillance

drawing more attention to Commons:Help_desk#c-~2026-37045-87-20260627102400-hCaptcha_system_broken.

i share @MGeog2022's concerns.

wiki is ostensibly protective of users' privacy (for example, revealing users' names is considered outing). but it records users' ip addresses, devices' fingerprinting data, etc.; and prevents most users from using vpn. also recently, it started requiring email for registration. and also these captcha systems.

here's my personal opinion. i have zero trust in all anonymous or pseudonymous users who hold sysop+ rights. i have zero trust in wmf either. the system as it is currently set up only serves to protect the small group of people in power from criticism and regulation, i.e. it is not far from bureaucratic dictatorship or tyranny, if it is not already one. RoyZuo (talk) 09:20, 5 July 2026 (UTC)

This link works. Yann (talk) 09:29, 5 July 2026 (UTC)

Whats the question you are asking? —TheDJ (talk • contribs) 15:49, 5 July 2026 (UTC)

cc @EMill-WMF. Nemoralis (talk) 14:23, 9 July 2026 (UTC)

There's a lot going on at once in these comments. For the record, email is not required for registration. For accounts with no email address, there are conditions under which we'll load in the captcha system on login.

Some conditions under which that might happen are very similar to those that, for accounts with an email attached, will cause an email to be sent with a code to paste in to continue logging in. That email-based check is dramatically more effective at protecting an account from takeover than a captcha, but a captcha is one of the few things we can do for no-email accounts.

For both email checks and captchas, they can affect regular account owners as well, especially if the account owner changes IPs and clears cookies frequently. This can sometimes cause issues, but they are still meant to allow the account owner to login. EMill-WMF (talk) 03:03, 10 July 2026 (UTC)

thx for answering.

@MGeog2022. RoyZuo (talk) 15:09, 10 July 2026 (UTC)

As I've said before, I'm not against captchas at all: in fact, I feel my account far more protected from possible bot attacks, so I'm really happy with them. The big problem was when the captchas stopped working and didn't allow me to log in: it seems it was unintended and it is fixed by now, but I think the error was really serious and it took too much time to be addressed. MGeog2022 (talk) 11:16, 11 July 2026 (UTC)

Post-processing professional photos?

I do a lot of fixing up of poor photos used in enwiki articles, most commonly just plain badly exposed images with deep shadows. Then I look at something like File:Supreme Court US 2009.jpg and I'm not sure what to do. My first thought is to just shove the shadow slider all the way to the right and be happy that I'm recovered the detail in the justice's robes. But this is an official photo taken by a professional photographer under studio conditions. Do I really want to mess with that? Maybe the underexposure of the robes is a deliberate artistic statement, not to be bludgeoned by a random slider-pusher? Thoughts? — Preceding unsigned comment added by RoySmith (talk • contribs) 15:43, 11 July 2026 (UTC)

Don't do? Not because of assumed artistic statements, but on technical grounds. I most likely wouldn't try to recover shadows from a JPEG, it's dynamic range is too limited. And are those robes truly plain black (RGB 00 00 00) or are they only dark (didn't check the pixels or the histogram)? Regards, Grand-Duc (talk) 16:14, 11 July 2026 (UTC)

RoySmith, there's nothing wrong with that photo? - Alexis Jazz ^{ping plz} 03:13, 12 July 2026 (UTC)

RoySmith: File:Raikaia Salmon.JPG was taken too far. File:Alice Tangerini.jpg also. File:Frank Lloyd Wright - Barton House.jpg was not an improvement. You generally lean towards overbrightening. - Alexis Jazz ^{ping plz} 03:25, 12 July 2026 (UTC)

Android motion photos

When uploading photos that contain video data ("motion photos" on Android), would I be required to remove the video portion from the image if it is in a non-free format?

Android motion photos are simply JPEG files with MP4 video appended to the end. According to the specification, the video track may be encoded in AVC (H.264), HEVC (H.265), or AV1 - my phone encodes them in HEVC - and the video can also contain an audio track in AAC. Since these are non-free formats, strictly speaking the video portion should not be allowed under Commons:File types. But there's nothing technically stopping me from uploading the motion photo because it's in an allowed file type (JPEG). MediaWiki might just treat it as an ordinary JPEG file and ignore the MP4 data.

With iOS live photos, the device saves the photo and video as two separate files, so this doesn't seem to be an issue. Qzekrom (talk) 02:25, 13 July 2026 (UTC)

Problems with Template:Citation

The Template:Citation seems to have been changed recently. This har resulted in lines of white space being inserted between the citations used in references in an artwork template, as seen here File:Martinus Rørbye, Arrestbygningen ved råd- og domhuset, 1831, KMS206, Statens Museum for Kunst.jpg. I have not seen this behavior of the template before and have no idea of how to correct it. Cheers Rsteen (talk) 12:45, 13 July 2026 (UTC)

Pinging @ForeverFlying who made the edit in question. – Howardcorn33 (💬) 16:58, 5 August 2026 (UTC)

@Rsteen I have removed the extra white spaces, so the template should be displaying properly now. Thanks. Tvpuppy (talk) 17:31, 5 August 2026 (UTC)

My apologies for messing up the line-spacing! @Tvpuppy Thank you for the fix! And thank you @Rsteen for bringing up the issue. ForeverFlying (talk) 17:40, 5 August 2026 (UTC)

This section is resolved and can be archived. If you disagree, replace this template with your comment. --Tvpuppy (talk) 21:22, 10 August 2026 (UTC)

Blank space on top of categories with navboxes

Some navboxen appear to be having mysterious blank spaces on top of the categories (in MonoBook on Firefox latest version, at least). See for instance Category:Snow in Florida, which has a significant gap between the navbox and the category title on top of the page. Compare to Category:Rain in Florida, which has the same navbox, but does not have the mysterious space. What gives? - The Bushranger (talk) 05:07, 27 July 2026 (UTC)

@The Bushranger: The first character of the page is an invisible en:Byte order mark. I removed it from Category:Snow in Florida. --Achim55 (talk) 07:11, 27 July 2026 (UTC)

Huh, wonder how that happened. Thanks for clearing it up! - The Bushranger (talk) 01:53, 28 July 2026 (UTC)

This section is resolved and can be archived. If you disagree, replace this template with your comment. --Tvpuppy (talk) 21:21, 10 August 2026 (UTC)

Tech News: 2026-29

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

• Revise Tone helps newcomers identify passages in Wikipedia articles that may contain non-encyclopedic language and encourages them to consider revising the tone. The feature was A/B tested on the Arabic, English, French, and Portuguese Wikipedias, where newcomer task completion rates increased by 38.7% compared to the default Copyedit task, with no decrease in edit quality. The test ended on July 9, and the feature is now available for everyone on these wikis, configurable via Community Configuration. The plan is to release Revise Tone to more wikis.
• The community configuration that allows automatic removal of inactive mentors based on configurable criteria will be enabled on Thursday 16, on some wikis to keep mentor lists up to date. Mentors are experienced contributors who opt in to help new users on-wiki through the Growth Features. Administrators can now prepare the settings via Special:CommunityConfiguration/Mentorship; they will take effect starting Thursday.
• View all 38 community-submitted tasks that were resolved last week. For example, an issue where some users of the Wikipedia Android app were logged out immediately after signing in, preventing them from staying logged in and editing pages, has now been fixed. [2]

Updates for technical contributors

• Editing a page via user scripts or gadgets was causing watchlist labels that the user had assigned to that page to reset. This has now been fixed. [3]
• To work around a Safari bug (see phab:T425211), on Parsoid-enabled wikis, wikilink hrefs now use absolute urls instead of protocol-relative urls. REST API output remains unchanged and continue to use protocol-relative urls. Gadgets, user scripts, bots, and CSS might need to be adapted if they relied on the presence of protocol-relative urls in wikilink hrefs. [4]
• Detailed code updates later this week: MediaWiki

In depth

• The Wikimedia Foundation’s Experiment Platform Team has published a blog post reflecting on its first year of structured experimentation. It highlights successful experiments such as Paste Check, Reference Check, and Tone Check, which improved editing outcomes and have been rolled out to more users, as well as experiments that did not lead to product changes. Read more.

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

MediaWiki message delivery 16:08, 13 July 2026 (UTC)

Inappropriate rejection of a file name

Initial report and section title (the latter now modified) appear to have been wrong, but there is still apparently a problem here. - Jmabel ! talk 06:49, 19 July 2026 (UTC)
Santiago Brra. reports that he tried to upload a file with the name "Sala de la colección principal de la Biblioteca Popular Solidaridad Social, Rosario, Argentina. Julio de 2026.jpg" and got the obviously inappropriate message "Please write a more informative title". Anyone have any idea why this would happen? - Jmabel ! talk 22:29, 18 July 2026 (UTC)

OK, it was an inaccurate report on his part, though there is still an issue. The message he received was entirely different, and in Spanish. It was "Algo salió mal: El nombre de archivo que estabas intentando subir ha sido incluido en la lista negra..." So it was saying something in this file name was blacklisted. Offhand, I have no idea what is wrong with that filename. Nothing in the filter log at all for that account. Reading what he later wrote at Commons:Help desk#Título para imagen de Wikimedia, I'm pretty sure it was a cross-wiki upload from es-wiki, if that helps. - Jmabel ! talk 06:49, 19 July 2026 (UTC)

Tech News: 2026-30

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

• The Reader Experience team has incorporated community feedback around the placement of watchstar and watchlist buttons for the Reading Lists beta feature, which would allow for saving articles for later reading – a wishlist item to bring the functionality to web. Editors are invited to enable the beta feature to test it out and share their thoughts.
• Suggestion Mode offers edit suggestions within the VisualEditor for improving Wikipedia articles. All suggestions are community-configurable. The TextMatch feature is a way for volunteers to create custom local suggestions. The feature searches in articles for strings of text, and now includes support for regular expressions. This gives volunteers greater precision and flexibility over the kinds of local suggestions they can create. Note: Suggestions can be targeted based on the edit count of the person editing as well as other aspects of the page. You can find examples from other communities for inspiration, including TextMatches that detect: typos, grammar-errors, potential advertisements, clichés, incorrect dash or hyphen usage, non-specific time keywords, outdated names, and more. Any feedback is appreciated.
• View all 27 community-submitted tasks that were resolved last week. For example, an issue where the SVG Translate tool could use an outdated version of a file, causing existing translations to be overwritten when new ones were uploaded, has now been fixed. Overall, in the last quarter from April – June 2026 about 337 community tasks were resolved by the Wikimedia Foundation.

Updates for technical contributors

• On Parsoid-enabled wikis, Parsoid now renders a maximum of 1,250 images per page. A new tracking category, "media-limit-reached", will be soon made available to identify pages where this limit is reached, making it easier to find content whose media output may have been restricted during rendering. See phab:T430854 for more information and to provide feedback.
• Detailed code updates later this week: MediaWiki

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

MediaWiki message delivery 05:44, 21 July 2026 (UTC)

Outdated pictures of the day

I've been seeing reports that the picture of the day is sometimes showing POTDs from previous days. Are the caches for the Main Page not always getting updated? Clarinetguy097 (talk) 16:47, 21 July 2026 (UTC)

• Here is an example where both POTD and MOTD are affected: the POTD and MOTD for 11th July are repeated in archive.org from 11-15th July: 11th, 12th, 13th, 14th, 15th July. Only on 16th July did POTD and MOTD get updated. --Tagooty (talk) 15:42, 22 July 2026 (UTC)

  i vaguely remember that @Schlurcher's bot purges the main page every day after midnight. sorry if wrong mention.

  2 potential problems:

  1. not sure when exactly the purge happens. might it help if it's done a few minutes after 00:00 instead of exactly midnight?
  2. still, i have a vague impression that pages quite often look different to logged in and logged out users, probably due to how the website is cached and delivered by wmf.

  RoyZuo (talk) 13:16, 23 July 2026 (UTC)

  @Clarinetguy097, @RoyZuo, @Tagooty: RoyZuo remembers correctly SchlurcherBot purges all the different language versions of the main page every day, around 1am. However, SchlurcherBot was down during time period noted. I did not see this before, but it seems this is a faily critical task to do, so maybe we need a second bot, that does the same or another backup solution. --Schlurcher (talk) 15:08, 23 July 2026 (UTC)

  thx a lot.

  i agree that having a 2nd bot to double tap is essential.

  but, maybe wmf should also purge the highest traffic pages? for pages that are frequently visited, or contain important info (such as legal stuff or time-sensitive stuff), maybe wmf should purge them so they make sure pages delivered to users are up to date?

  maybe a page should be automatically purged whenever it hits a certain view count? purged every 100k-th visit. or purged daily/hourly when a page accumulates 100k visits over 24h/3d/7d...? just some random ideas. RoyZuo (talk) 16:45, 23 July 2026 (UTC)

  Thanks for the explanations. Given the time-sensitive nature, I think the best solution is for the bot that updates POTD and MOTD at midnight UTC to purge immediately. Leaving the task to another bot that usually, but not always, runs 1 hour later is risky and imprecise. Tagooty (talk) 04:02, 25 July 2026 (UTC)

  Tracked in Phabricator
  Task T433164
  

  see if the problem gets worked on. RoyZuo (talk) 11:12, 25 July 2026 (UTC)

Tech News: 2026-31

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

• Content Translation now supports dark mode, fulfilling a Community Wishlist request. This brings the tool in line with the accessibility features available in the Vector 2022 and Minerva skins, helping reduce visual fatigue for users translating content. [5]
• DiscussionTools' source mode and the 2017 wikitext editor will now offer autocomplete for links ([[), templates ({{), HTML and parser tags (<), and magic words (__), making it quicker and easier to insert links, templates, and other wiki markup while editing. [6]
• The Readers Growth team has concluded its experiment with mobile page previews and will not roll out the feature. Page Previews are a pop-up bottom sheet that appears when readers tap a blue link, showing a thumbnail, lead paragraph, and an option to open the article. The experiment showed flat retention and negative indicator metrics, suggesting that mobile web readers preferred navigating directly to linked articles rather than using page previews.
• The Reader Experience team has seen encouraging early results from the Reading Lists feature, with 93% of participating users reporting that it was useful. Reading Lists help active readers save articles for future reading and support their learning goals on Wikimedia projects. The team plans further improvements before expanding the feature to more users.
• The Explore Feed Refresh initiative was tested with new and casual Wikipedia app readers. The refreshed feed helps readers discover new and relevant content. After a 10.5% increase in engagement with the feed, Wikimedia Apps team has decided to scale the Home Feed redesign to iOS with the learnings from the Android release applied.
• View all 23 community-submitted tasks that were resolved last week. For example, an issue where subject names in the Article Guidance feature were displayed with incorrect capitalization on French Wikipedia, has now been fixed. Subject names will now follow the correct capitalization rules for the language. [7]

Updates for technical contributors

• After running several Account Creation Experiments to improve registration completion rates, a new version of the username field on Create Account has been rolled out. It includes a popover summarizing the username policy to provide clearer guidance during account creation. As part of this change, the messages createacct-helpusername and createacct-username-help that several communities have configured will no longer be used. If communities want to customize the guidance shown in the new popover, they can instead edit the following messages: createacct-username-policy-popover-bullet1, createacct-username-policy-popover-bullet2, and createacct-username-policy-popover-bullet3. [8]
• Later this week, the CodeMirror syntax highlighter will offer themes. The themes can be picked from a dropdown menu in the full CodeMirror preferences dialog. For wikitext, available themes are default, colorblind-friendly (previously the colorblind preference option on Special:Preferences#mw-prefsection-editing) and no-highlighting. For code languages (i.e., CSS/JavaScript/JSON/Vue/Lua), there are several themes available. These same themes will eventually be available for wikitext, too. [9]
• From now on, wikis can restrict editing in the "User" namespace to only the page owner and certain user groups. Read the configuration documentation to learn more.
• Detailed code updates later this week: MediaWiki

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

MediaWiki message delivery 18:46, 27 July 2026 (UTC)

Batch uploading audio files – bot or not?

Hello! I want to upload a large amount of audio files, approximately 33 000, to Commons (pronunciations of Estonian words, if you're interested). For the sake of my mental and physical health, I don't really want to click the Upload Wizard 33 000 times to upload each file individually. There's gotta be a more efficient way to do that, perhaps it's a job that a bot can do? I know there are tools other than the Upload Wizard, which can be used to upload many files at once, but there's a few additional catches which lead me to think it's a job better left to a bot or a user more experienced here than me, who would know how to tackle these issues and not end up in a mental hospital in the process.

Firstly, the files need to be renamed. Currently they are just numbered, for example psv_08693.wav. Their names need to be reformatted to Et-{{{term}}}.ogg. Fortunately, there is, at least for one portion of the audio files, a .txt file which connects every one of those numbers to the corresponding terms. I imagine that a bot wouldn't have a problem with reading that and renaming the audio files accordingly. The other portion of the audio files also have an additional file, but it's in the .ndx format, which I can't open, so I'm not sure if it can be used in the same way, hopefully it can. The fun doesn't end there though – not only do the file names need to be converted from a numeric value to a text value as per the .txt file, but these text values in turn need even more changing. Nothing too extreme though, mostly just converting some symbols, like ` to *, with some exceptions, such as the symbol being removed altogether for words of 4 or less letters (it's more complicated than that but I will not go into it). The reason being that these audio files are intended to be used on Wiktionary, and the template that converts Estonian text to IPA uses different symbols when respelling, and the audio files should, ideally, be equal to the respelling in the first parameter of the pronunciation template. But it will also allow manual input of the audio files, so if you deem making this shortcut possible to be too complicated and time-consuming, then it's not the end of the world either. A couple of examples: psv_08693.wav → t`el'k → Et-tel'k.ogg, psv_01396.wav → hilja → Et-hilja.ogg (no changes needed), psv_00855.wav → el`ekter → Et-el*ekter.ogg, psv_00447.wav → `asf`alt → Et-*asf*alt.ogg, psvalg_1721.mp3 → k`un'stn`ik → Et-k*un'stnik.ogg (here, again ideally, delete the symbol if the term ends in -ik, but as I said, no problem if that's too complicated, and there are a million exceptions to this anyway), psvalg_2109.mp3 → organisatsi`oon → Et-organisatsi*oon.ogg, psv_00931.wav → enآ´ergiline → Et-en"ergiline.ogg (´ becomes "), psv_00028.wav → abi+elu → Et-abi-elu.ogg (+ becomes -, compound words), psv_07746.wav → sini+m`ust+v`alge → Et-sini-must-v*alge.ogg (components of a compound word are treated individually, so the rule of removing ` from 2-4 letter words applies). Every other symbol other than letters, spaces, and those symbols mentioned, should be removed. A final note: some forms are exactly the same and have the same pronunciation, therefore they have only one file for all of the forms in question, but the .txt file lists them multiple times, although with the same file name, just on different lines.

The second issue is one of categorization. The files need to be categorized as [[Category:Estonian pronunciation|<first letter of the term>]] or [[Category:Estonian pronunciation|<term>]] (I think it's the same). This can probably be solved with some non-back-breaking code, but it should still be done by someone who knows what they're doing.

Thirdly, the files are either in .wav or .mp3 format. They need to be converted to .ogg. This doesn't seem like a nightmare on its own, I could probably do that by myself, but combined with all these other things it doesn't bring me much optimism.

So in conclusion, I'm looking for somebody who is willing to and able to help me with uploading these files. It would be fantastic if somebody could do it for me, and if not, then could at least explain to me the necessary steps, as I genuinely have no clue. I understand if this seems like a lot to ask, we can do compromises on the file naming part, if necessary, but I really hope somebody here has the necessary skills and readiness to take on this task in some format, either with a bot or not with a bot. Joonas07 (talk) 09:37, 12 July 2026 (UTC)

 Comment MP3 is now accepted. - Jmabel ! talk 18:02, 12 July 2026 (UTC)

Does require having the autopatrol right, which you will need to request (for you or a bot) —TheDJ (talk • contribs) 18:59, 12 July 2026 (UTC)

Great, that's one problem less. But I'm still looking for someone who would generally know what they're doing, especially if some kind of autopatrol rights have to be requested, it's better to have a user who has some kind of prior experience. Seeing as nobody has answered me here yet, could you maybe suggest some users that I could contact directly and ask if they are ready to do it? Apologies if I'm being intrusive, but I really need help here. Joonas07 (talk) 09:36, 15 July 2026 (UTC)

Are the files other than the actual audio small enough that you can pack them all into an archive (eg. a zip file) and upload them to somewhere we can look at? I think seeing the real data would help us prepare for this task.

It intimidates me that we'll have to derive the upload filenames according to conventions of dictionary in a foreign language that I'm not familiar with. So you'll probably have to explain these transformation rules and proofread the derived filenames, possibly in multiple passes until we get all the names right.

Also please tell us about the legal parts, as in licenses for copyright and database rights. I know this can be annoying, but I think anyone who wants to help will want to be really sure about them before uploading tens of thousands of audio files. Though of course we won't upload all of them at the same time, instead we'd upload a smaller selection first and then allow users some time to tell us what we did wrong. – b_jonas 03:45, 22 July 2026 (UTC)

Sorry for not replying, fortunately, I found a user already who can help me, but thanks for offering! Joonas07 (talk) 16:19, 28 July 2026 (UTC)

But I'll keep you in mind, in case it won't work out with that other user after all. There's the issue of bot permissions and when it comes to converting the names, I'm not sure if it can just be done with find and replace. So I might still contact you at some point, if you are okay with that. Joonas07 (talk) 16:30, 28 July 2026 (UTC)

For the record, all the files including the index are packed into three zip files, and the files are CC-BY-4.0, so we can use them for educational purposes. Joonas07 (talk) 16:37, 28 July 2026 (UTC)

Wait, “psv_00931.wav → enآ´ergiline → Et-en"ergiline.ogg”? There's a letter from arabic script in the middle of that one! I hope there's a semi-reasonable explanation for this one, like it's an old database from back when Unicode wasn't as prevalent as now and some characters got replaced by inappropriate ones during the conversion. – b_jonas 05:07, 22 July 2026 (UTC)

Yes, I noticed that too, but I don't know where it came from. Seems like it appears only before the symbol ´, so probably some Unicode stuff like you said. Joonas07 (talk) 16:28, 28 July 2026 (UTC)

TSE-Dados-Abertos

Hello,

I'd like to know if it would be possible to update the TSE-Dados-Abertos to improve the categorization. As it stands now, the main category have 18,915 files, with the categories by party and by year having to be added manually.

To empty the main category, could it be possible for the template to work like {{TSE-Dados-Abertos|party=(party acronym; example: MDB, PT, PDT...)|year=(electoral year)}}, with an warning message displayed if any or both options are missing? It would also be interesting if the template could link to the divulgacandcontas.tse.jus.br (as the source of the political party), as we can see here, for 2022. This could also help if this batch upload proposal ever happens. Erick Soares3 (talk) 16:22, 28 July 2026 (UTC)

Automatic categories for Template:Translate

Scribunto now can return a list of languages translated in an SVG file (T259018), and so it's possible to automate the addition of files to Category:SVG by language (as requested in T407647). I'm not quite sure where the best place would be for this feature (maybe in Module:FileMedia, although that doesn't really deal with categories; then called from {{Translate}}), but something like the following should be possible:

    local langs = mw.title.new( 'File:Tulunadu.svg' ).file.languages
    local cats = ''
    for _,langCode in pairs( langs ) do
        local langName = mw.language.fetchLanguageName( langCode, 'en' )
        cats = cats .. '[[Category:' .. langName .. '-language SVG]]\n'
    end
    return cats

Pinging @Booksmurf who's working on related stuff.
— Sam Wilson 02:07, 22 July 2026 (UTC)

I have created this module and its doc in relation to:

https://meta.wikimedia.org/wiki/Community_Wishlist/W528 @docjames

https://commons.wikimedia.org/wiki/Module:Translate

As per Sam's comment, I do not know where would be the place place for this, so if any admin could help figuring out the next step or giving recommendations, it would be greatly appreciated!

Thank you Booksmurf (talk) 09:27, 1 August 2026 (UTC)