Wikitech-l April 2025

52 participants
42 discussions

Upcoming Codex 2.0 release
by Anne Tomasevich 08 May '25

08 May '25

The Design System Team (DST)[0] is preparing to release the next major version of Codex, the design system for Wikimedia. Codex has evolved significantly since the first major version release in late 2023: expanding the toolkit with a number of new components[1], tokens[2] and icons[3], introducing alternative color modes[4], adding a proper i18n system[5], refactoring components to be compatible with native browser validation[6], supporting the creation of a PHP implementation of the component library[7], refreshing the documentation, and (finally) getting a unique logo. With the upcoming introduction of a revised typography scale and customizable font modes[8] along with a handful of other breaking changes, DST has determined this to be an appropriate time for another major version release. ==== Timeline ==== DST plans to first release a release candidate (rc) of version 2.0.0 that will include all known breaking changes. It is anticipated that only one rc version will be released, but if major issues are discovered, there will be additional rcs until the build is considered stable enough to be the official major version. - v2.0.0-rc.1 will be released on 29 April 2025 and ride the deployment train the week of 5 May 2025 - v2.0.0 will be released on 13 May 2025 and ride the train the week of 19 May 2025 ==== Breaking Changes ==== Codex 2.0 will include a number of breaking changes that need to be addressed in downstream code to avoid compatibility issues. These are detailed in full along with guidance on how to prepare for the release at https://www.mediawiki.org/wiki/Codex/Release_Timeline/2.0#Breaking_changes. If you are using Codex for a feature actively deployed in Wikimedia production, please check to see if the breaking changes apply to your code. DST has already opened Phabricator tasks for known areas that need to be updated based on codesearch but this is likely not comprehensive. Thank you to everyone who has contributed to the development of Codex throughout its 1.0 lifespan! We look forward to seeing its use in Wikimedia projects continue to grow as it further evolves through this next major iteration. Anne Tomasevich, on behalf of the Design System Team [0] https://www.mediawiki.org/wiki/Design_System_Team [1] https://doc.wikimedia.org/codex/latest/components/overview.html [2] https://doc.wikimedia.org/codex/latest/design-tokens/overview.html [3] https://doc.wikimedia.org/codex/latest/icons/overview.html [4] https://doc.wikimedia.org/codex/latest/using-codex/adrs/08-adr-color-modes.… [5] https://doc.wikimedia.org/codex/latest/using-codex/adrs/10-adr-i18n-for-com… [6] https://doc.wikimedia.org/codex/latest/using-codex/adrs/12-adr-native-const… [7] https://doc.wikimedia.org/codex/latest/using-codex/adrs/11-adr-codex-php.ht… [8] https://doc.wikimedia.org/codex/latest/using-codex/adrs/13-adr-font-modes.h… [9] https://codesearch-beta.wmcloud.org/search -- Anne Tomasevich (she/her) Staff Software Engineer, Design System Wikimedia Foundation

3 2

Talk to the Search Platform / Query Service Team—May 7, 2025
by Guillaume Lederrey 07 May '25

07 May '25

Hello all! The Search Platform Team usually holds an open meeting on the first Wednesday of each month. Come talk to us about anything related to Wikimedia search, Wikidata Query Service (WDQS), Wikimedia Commons Query Service (WCQS), etc.! Feel free to add your items to the Etherpad Agenda for the next meeting. Details for our next meeting: Date: Wednesday, May 7, 2025 Time: 15:00-16:00 UTC / 08:00 PST / 11:00 EST / 17:00 CET Etherpad: https://etherpad.wikimedia.org/p/Search_Platform_Office_Hours Google Meet link: https://meet.google.com/vgj-bbeb-uyi Join by phone: https://tel.meet/vgj-bbeb-uyi?pin=8118110806927 Have fun and see you soon! Guillaume -- *Guillaume Lederrey* (he/him) Engineering Manager Wikimedia Foundation <https://wikimediafoundation.org/>

1 1

Maintenance scripts are moving to Kubernetes
by Reuven Lazarus 07 May '25

07 May '25

Hi all, With MediaWiki at the WMF moving to Kubernetes, it's now time to start running manual maintenance scripts there. Any time you would previously SSH to a mwmaint host and run mwscript, follow these steps instead. The old way will continue working for a little while, but it will be going away. What's familiar: Starting a maintenance script looks like this: rzl@deploy2002:~$ mwscript-k8s --comment="T341553" -- Version.php --wiki=enwiki Any options for the mwscript-k8s tool, as described below, go before the --. After the --, the first argument is the script name; everything else is passed to the script. This is the same as you're used to passing to mwscript. What's different: - Run mwscript-k8s on a deployment host, not the maintenance host. Either deployment host will work; your job will automatically run in whichever data center is active, so you no longer need to change hosts when there’s a switchover. - You don't need a tmux. By default the tool launches your maintenance script and exits immediately, without waiting for your job to finish. If you log out of the deployment host, your job keeps running on the Kubernetes cluster. - Kubernetes saves the maintenance script's output for seven days after completion. By default, mwscript-k8s prints a kubectl command that you (or anyone else) can paste and run to monitor the output or save it to a file. - As a convenience, you can pass -f (--follow) to mwscript-k8s to immediately begin tailing the script output. If you like, you can do this inside a tmux and keep the same workflow as before. Either way, you can safely disconnect and your script will continue running on Kubernetes. rzl@deploy2002:~$ mwscript-k8s -f -- Version.php --wiki=testwiki [...] MediaWiki version: 1.43.0-wmf.24 LTS (built: 22:35, 23 September 2024) - For scripts that take input on stdin, you can pass --attach to mwscript-k8s, either interactively or in a pipeline. rzl@deploy2002:~$ mwscript-k8s --attach -- shell.php --wiki=testwiki [...] Psy Shell v0.12.3 (PHP 7.4.33 — cli) by Justin Hileman > $wmgRealm = "production" > rzl@deploy2002:~$ cat example_url.txt | mwscript-k8s --attach -- purgeList.php [...] Purging 1 urls Done! - Your maintenance script runs in a Docker container which will not outlive it, so it can't save persistent files to disk. Ensure your script logs its important output to stdout, or persists it in a database or other remote storage. - The --comment flag sets an optional (but encouraged) descriptive label, such as a task number. - Using standard kubectl commands[1][2], you can check the status, and view the output, of your running jobs or anyone else's. (Example: `kube_env mw-script codfw; kubectl get pod -l username=rzl`) [1]: https://wikitech.wikimedia.org/wiki/Kubernetes/Kubectl [2]: https://kubernetes.io/docs/reference/kubectl/quick-reference/ What's not supported yet: - Maintenance scripts launched automatically on a timer. We're working on migrating them -- for now, this is for one-off scripts launched by hand. - If your job is interrupted (e.g. by hardware problems), Kubernetes can automatically move it to another machine and restart it, babysitting it until it completes. But we only want to do that if your job is safe to restart. So by default, if your job is interrupted, it will stay stopped until you restart it yourself. Soon, we'll add an option to declare "this is idempotent, please restart it as needed" and that design is recommended for new scripts. - No support yet for mwscriptwikiset, foreachwiki, foreachwikiindblist, etc, but we'll add similar functionality as flags to mwscript_k8s. Your feedback: Let me know by email or IRC, or on Phab (T341553 <https://phabricator.wikimedia.org/T341553>). If mwscript-k8s doesn't work for you, for now you can fall back to using the mwmaint hosts as before -- but they will be going away. Please report any problems sooner rather than later, so that we can ensure the new system meets your needs before that happens. Thanks, Reuven, for Service Ops SRE

7 19

Gerrit is down for troubleshooting
by Lukasz Sobanski 01 May '25

01 May '25

Hi, Following the Gerrit switchover from gerrit2002 to gerrit1003 earlier today we noticed missing changes in the Gerrit interface. We shut down Gerrit to prevent further complications and are troubleshooting in T393034 <https://phabricator.wikimedia.org/T393034>. -- Lukasz Sobanski SRE

1 3

Announcement: Wikidata's Strategic Direction for 2025
by Danny Benjafield 30 Apr '25

30 Apr '25

Dear Wikidata Community, As part of Wikimedia Deutschland’s 2030 Strategic Direction and in close collaboration with the Wikimedia Foundation (WMF), the Wikidata team has set its priorities for 2025 around 4 core themes: ensuring Wikidata can continue to grow sustainably, strengthening the diverse community of editors who steward and reuse our data, and refining the underlying platform services that power everything we build together. We chose these focuses because, first, as Wikidata’s size and impact expand, it’s crucial that we build systems and policies that keep our infrastructure healthy and our data dependable. Second, our community remains at the heart of everything we do -- whether someone contributes the first statement to a brand new Item or runs complex queries that power research and apps. Finally, by refining data access methods “as a service” across our ecosystem, we’ll open the door for all our product teams and third-party developers to build meaningful services and applications that create positive impact. Supporting sustainable growth means two things this year. We’ll partner with the Wikibase teams to improve federated SPARQL queries. This would allow you pull data seamlessly from multiple Wikibase instances lowering the barrier to hosting some data in other parts of the Wikibase Ecosystem, ensuring everyone can continue to access and edit data reliably. At the same time, we’ll have conversations about data governance guidelines together with the Cloud and Suite teams and the wider Wikidata community. This way it's always obvious where different kinds of data belong. That clarity helps editors make confident decisions, reduces duplicate work, and lays the foundation for new projects that can flourish alongside Wikidata itself. Strengthening the Wikidata community means making every step of contribution easier and more rewarding. Mobile editing has grown in recent years, yet adding or updating statements on a phone still forces many users into “desktop view.” We’ll roll out a prototype that will make editing statements on mobile phones easier. To help more advanced editors and tool builders, we’ll continue growing the visibility and documentation around EntitySchemas, so that editors everywhere can adopt these powerful templates and can integrate them out of the box. And of course, we’ll bring people together through online and in-person events such as WikidataCon, regional capacity‑building campaigns in Africa, meetups at Wikimania and other conferences, XXX Days events like Data Reuse Days and Lexico Days, and more. By connecting newcomers with experienced mentors, by highlighting local hubs where editors can support each other, and by linking each Item back to its relevant WikiProjects, we’ll nurture more active, diverse, and resilient communities. Our third focus area is Increasing mission-aligned data reuse The Wikidata For Wikimedia Projects <https://meta.wikimedia.org/wiki/Wikidata_For_Wikimedia_Projects> team will improve the editing experience and increase productivity of Wikipedia contributors by making it easier for editors to monitor, understand, and act on changes to their watchlisted articles when the edit comes from Wikidata. Displaying Wikidata edits in Watchlist and Recent Changes pages is an opt-in feature of the user preferences; our aim is to increase awareness, adoption, and utility of this function by summer 2026. In parallel, we will raise awareness and contributors’ understanding of the Wikidata integrations currently being used in the Wikimedia Projects through a community outreach project by hosting an online conference, Wikidata and Sister Projects <https://www.wikidata.org/wiki/Event:Wikidata_and_Sister_Projects>, dedicated to celebrating and informing Wikimedians of the many ways Wikidata currently supports the Wikimedia Projects. Additionally, we are reviewing the available documentation on Wikidata integrations to ensure it is updated, comprehensive, and available in multiple core languages. Refining platform services “as a service” is our fourth focus area. We’ll refine data access methods so Wikidata's data can be reused to build meaningful services and applications. Specifically, we'll build out search capabilities in the REST API so developers can discover and query data more easily. We’ll ensure the Wikidata Query Service (WDQS) is optimized for its core strength of supporting queries that need the graph -- keeping it fast and reliable under complex workloads. Finally, we’ll improve our data dumps to provide more accessible snapshots and subsets of Wikidata’s data. What does this mean for you? If you’re a mobile‑first contributor, editing from your phone will become smooth and straightforward. If you’re a developer or researcher, you’ll gain powerful new search endpoints in the REST API, a finely tuned Wikidata Query Service for graph-centric queries, and cleaner, more timely data dumps to build on. If you organize or participate in events, you’ll find more support and clearer pathways to grow local hubs and share best practices. If you’re leveraging Wikidata’s data to support your workflows and content in other Wikimedia projects, you’ll have access to current use-cases, examples and better documentation to refer to. Ultimately, every update we make in this period is designed to give you more confidence, more choice, and more impact as you add, improve, and reuse the world’s free structured knowledge. We’ll keep you posted on progress throughout the year and as always, welcome your questions and feedback on the talk page <https://www.wikidata.org/wiki/Wikidata_talk:Development_plan/Wikidata_2025-…> . Thank you for your efforts to drive Wikidata forward. Best regards, The Wikidata Team Wikimedia Deutschland -- *Danny Benjafield* Community Communications Manager Wikidata For Wikimedia Projects Wikimedia Deutschland e. V. | Tempelhofer Ufer 23-24 | 10963 Berlin Phone: +49 (0)30-577 11 62-0 https://wikimedia.de Keep up to date! Current news and exciting stories about Wikimedia, Wikipedia and Free Knowledge in our newsletter (in German): Subscribe now. <https://www.wikimedia.de/newsletter/> Imagine a world in which every single human being can freely share in the sum of all knowledge. Help us to achieve our vision! https://spenden.wikimedia.de Wikimedia Deutschland — Gesellschaft zur Förderung Freien Wissens e. V. Eingetragen im Vereinsregister des Amtsgerichts Charlottenburg, VR 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für Körperschaften I Berlin, Steuernummer 27/029/42207. Geschäftsführende Vorstände: Franziska Heine

1 0

LessExceptionCompiler error
by Viktoria Hillerud 30 Apr '25

30 Apr '25

After pulling down the latest changes from MW core, I got some error with my css/less not loading on the page. The issue looks like this: Less_Exception_Compiler: error evaluating function `unit` The first argument to unit must be a number. Have you forgotten parenthesis? index: 69 in stickyHeader.less on line 2, column 1 1| @spacing-search-title-divider: 30px; 2| @font-size-sticky-header-links: unit( 14 / @font-size-browser, em ); // Equals `0.875em`. 3| @import '../skins.vector.styles/variables.less'; 4| 5| .vector-sticky-header-container { 6| position: fixed; I have already run composer update and the relevant maintenance scripts (update.php, etc.), but the issue persists. These are the versions I'm using (same as my colleague, for whom it works fine): MediaWiki 1.44.0-alpha (4c93914) 07:06, 28 April 2025 PHP 8.3.14 (fpm-fcgi) ICU 72.1 MariaDB 11.4.4-MariaDB Any ideas on what could be happening? *Viktoria Hillerud* *Developer* Wikimedia Sverige (WMSE)

3 3

FYI: Edge Uniques
by Brandon Black 29 Apr '25

29 Apr '25

Hi everyone, If you follow any technical Wikimedia news, you might have read about this in Tech News or on Diff already, but in case you missed it: The Wikimedia Foundation is working on a system called Edge Uniques which will enable A/B testing, help mitigate DDoS attacks, and eventually give better visitor metrics. We’re doing this by adding a first-party cookie named "WMF-Uniq" which is handled *only* on our CDN edge servers directly. This cookie contains a randomly-generated unique identifier and a few bits of minimal metadata about site visit history. We've explicitly designed this system such that we do *not* need to or intend to store these cookies or their identifiers in any databases or logs anywhere on our servers, or forward them to any other complex parts of our internal server-side infrastructure where the risks of accidental leakage or storage might be higher. It's a fairly unique system, and one that we've tried to design for maximal privacy preservation and data minimization for Wikimedians while also meeting our needs around both A/B testing of reader-oriented features and helping to control the server load from botnets of various kinds with resource-abusive patterns. The A/B testing portion of this design can record relevant, specific, pre-defined metrics into our analytics databases for those agents selected for testing (e.g. "an agent in Test123/GroupA clicked the new blue button"), but these metrics records use a temporary, per-experiment derivative identifier created by a one-way hash, making them non-reversible back to the original cookie identifiers. You can read more details on Meta: https://meta.wikimedia.org/wiki/Edge_Uniques If you want to talk to us about this, we’re happy to discuss it on the project talk page: https://meta.wikimedia.org/wiki/Talk:Edge_Uniques We’re also hosting an office hours/community call to answer questions or discuss the topic further on April 29, 14:00 UTC. See more info here: https://meta.wikimedia.org/wiki/Edge_Uniques#Next_steps -- Brandon Black Principal Site Reliability Engineer, SRE Traffic Team Wikimedia Foundation

3 2

Tech News 2025, week 18
by Uzoma Ozurumba 29 Apr '25

29 Apr '25

Latest *tech news <https://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/News>* from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations <https://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/News/2025/18> are available. *Updates for editors* - Event organizers who host collaborative activities on multiple wikis <https://meta.wikimedia.org/wiki/Special:MyLanguage/CampaignEvents/Deploymen…>, including Bengali, Japanese, and Korean Wikipedias, will have access to the CampaignEvents extension <https://www.mediawiki.org/wiki/Special:MyLanguage/Extension:CampaignEvents> 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 <https://phabricator.wikimedia.org/T386861>. - [image: Recurrent item] View all 19 community-submitted tasks that were resolved last week <https://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/News/Recently_resol…> . *Updates for technical contributors* - The release of the next major version of Codex <https://www.mediawiki.org/wiki/Special:MyLanguage/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 <https://www.mediawiki.org/wiki/Special:MyLanguage/Codex/Release_Timeline/2.…> and minor visual changes <https://www.mediawiki.org/wiki/Special:MyLanguage/Codex/Release_Timeline/2.…>. Instructions on handling the breaking and visual changes are documented on this page <https://www.mediawiki.org/wiki/Special:MyLanguage/Codex/Release_Timeline/2.0>. Pre-release testing is reported in T386298 <https://phabricator.wikimedia.org/T386298>, with post-release issues tracked in T392379 <https://phabricator.wikimedia.org/T392379> and T392390 <https://phabricator.wikimedia.org/T392390>. - Users of Wiki Replicas <https://wikitech.wikimedia.org/wiki/Special:MyLanguage/Help:Wiki_Replicas> will notice that the database views of ipblocks, ipblocks_ipindex, and ipblocks_compat are now deprecated <https://phabricator.wikimedia.org/T390767>. Users can query the block <https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Block_table> and block_target <https://www.mediawiki.org/wiki/Special:MyLanguage/Manual:Block_target_table> 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. - [image: Recurrent item] Detailed code updates later this week: MediaWiki <https://www.mediawiki.org/wiki/MediaWiki_1.44/wmf.27> *In depth* - The latest quarterly Language and Internationalization Newsletter <https://www.mediawiki.org/wiki/Special:MyLanguage/Wikimedia_Language_and_Pr…> is now available. This edition includes an overview of the improved Content Translation Dashboard Tool <https://test.wikipedia.org/w/index.php?title=Special:ContentTranslation&cam…> , support for new languages <https://www.mediawiki.org/wiki/Special:MyLanguage/Wikimedia_Language_and_Pr…> , highlights from the Wiki Loves Ramadan campaign <https://www.mediawiki.org/wiki/Special:MyLanguage/Wikimedia_Language_and_Pr…> , results from the Language Onboarding Experiment <https://meta.wikimedia.org/wiki/Special:MyLanguage/Research:Languages_Onboa…>, an analysis of topic diversity in articles, and information on upcoming community meetings and events. *Meetings and events* - The Let's Connect Learning Clinic <https://meta.wikimedia.org/wiki/Special:MyLanguage/Grants:Knowledge_Sharing…> will take place on April 29 at 14:30 UTC <https://zonestamp.toolforge.org/1745937000>. This edition will focus on "Understanding and Navigating Conflict in Wikimedia Projects". You can register now <https://meta.wikimedia.org/wiki/Special:MyLanguage/Event:Learning_Clinic_%E…> to attend. - The 2025 Wikimedia Hackathon <https://www.mediawiki.org/wiki/Special:MyLanguage/Wikimedia_Hackathon_2025>, 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. -- Uzoma Ozurumba (She/her) Movement Communications Specialist (Product and Tech) meta.wikimedia.org/wiki/User:UOzurumba_(WMF)

1 0

Re: Tech News 2025, week 17
by Luca Martinelli [Sannita＠WMF] 28 Apr '25

28 Apr '25

On Mon, Apr 28, 2025 at 3:38 PM Gryllida <gryllida(a)fastmail.fm> wrote: > does wikifunctions include any ML functions? such as NLP? say i wanted to process text from external sources and extract some specific information and compare with what is written in wiki page There are text-based functions on Wikifunctions, so yes, you can do some limited experiment about this, also calling Wikidata lexemes with a function. L.

1 0

Tech News 2025, week 17
by Nick Wilson (Quiddity) 28 Apr '25

28 Apr '25

Latest *tech news <https://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/News>* from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations <https://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/News/2025/17> are available. *Updates for editors* - Wikifunctions <https://www.wikifunctions.org/wiki/Special:MyLanguage/Wikifunctions:Main_Pa…> is now integrated with Dagbani Wikipedia <https://en.wikipedia.org/wiki/dag:Sol%C9%94%C9%A3u> since April 15. It is the first project that will be able to call functions from Wikifunctions <https://www.wikifunctions.org/wiki/Special:MyLanguage/Wikifunctions:Introdu…> and integrate them in articles. A function is something that takes one or more inputs and transforms them into a desired output, such as adding up two numbers, converting miles into metres, calculating how much time has passed since an event, or declining a word into a case. Wikifunctions will allow users to do that through a simple call of a stable and global function <https://www.wikifunctions.org/wiki/Special:MyLanguage/Wikifunctions:Catalog…>, rather than via a local template. [1] <https://www.wikifunctions.org/wiki/Special:MyLanguage/Wikifunctions:Status_…> - A new type of lint error has been created: Empty headings <https://meta.wikimedia.org/wiki/Special:LintErrors/empty-heading> ( documentation <https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Lint_errors/empty-he…>). The Linter extension <https://www.mediawiki.org/wiki/Special:MyLanguage/Help:Extension:Linter>'s purpose is to identify wikitext patterns that must or can be fixed in pages and provide some guidance about what the problems are with those patterns and how to fix them. [2] <https://phabricator.wikimedia.org/T368722> - [image: Recurrent item] View all 37 community-submitted tasks that were resolved last week <https://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/News/Recently_resol…> . *Updates for technical contributors* - Following its publication on HuggingFace, the "Structured Contents" dataset, developed by Wikimedia Enterprise, is now also available on Kaggle <https://enterprise.wikimedia.com/blog/kaggle-dataset/>. This Beta initiative is focused on making Wikimedia data more machine-readable for high-volume reusers. They are releasing this beta version in a location that open dataset communities already use, in order to seek feedback, to help improve the product for a future wider release. You can read more about the overall Structured Contents project <https://enterprise.wikimedia.com/blog/structured-contents-snapshot-api/#ope…>, and about the first release that's freely usable <https://enterprise.wikimedia.com/blog/structured-contents-wikipedia-infobox/> . - There is no new MediaWiki version this week. *Meetings and events* - The Editing and Machine Learning Teams invite interested volunteers to a video meeting to discuss Peacock check <https://www.mediawiki.org/wiki/Special:MyLanguage/Edit_check/Peacock_check>, which is the latest Edit check <https://www.mediawiki.org/wiki/Special:MyLanguage/Edit_check> that will detect "peacock" or "overly-promotional" or "non-neutral" language whilst an editor is typing. Editors who work with newcomers, or help to fix this kind of writing, or are interested in how we use artificial intelligence in our projects are encouraged to attend. The meeting will be on April 28, 2025 <https://www.mediawiki.org/wiki/Special:MyLanguage/Editing_team/Community_Co…> at 18:00–19:00 UTC <https://zonestamp.toolforge.org/1745863200> and hosted on Zoom. *Tech news <https://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/News> prepared by Tech News writers <https://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/News/Writers> and posted by bot <https://meta.wikimedia.org/wiki/Special:MyLanguage/User:MediaWiki_message_d…> • Contribute <https://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/News#contribute> • Translate <https://meta.wikimedia.org/wiki/Special:MyLanguage/Tech/News/2025/17> • Get help <https://meta.wikimedia.org/wiki/Tech> • Give feedback <https://meta.wikimedia.org/wiki/Talk:Tech/News> • Subscribe or unsubscribe <https://meta.wikimedia.org/wiki/Global_message_delivery/Targets/Tech_ambass…>.*

6 8

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Wikitech-l April 2025