Wikisource:Scriptorium

Important project pages: What is Wikisource? • Wikisource and Wikibooks • Votes • Copyright • Possible copyright violations • Proposed deletions • Wikisource:Protection requests • Cataloging • Wikisource and Project Gutenberg

Languages: Language policy • Language domain requests • Language domain requests/Rules for voting • List of Wikisource Languages

Coordination: Statistics • ProofreadPage Statistics • Subdomain coordination • News

---

Archives • Pre-launch discussions • November 2003 to January 2004 • Feb–Jun 2004 • Jul–Oct 2004 • Oct 2004 – Feb 2005 • Feb–Apr 2005 • Apr–Aug 2005 • Aug–Sep 2005 (until the move to language subdomains) • Sep–Dec 2005 (after the move to language subdomains) • 2006 • 2007 • 2008 • 2009 • 2010 • 2011 • 2012 • 2013 • 2014 • 2015 • 2016 • 2017 • 2018 • 2019 • 2020 • 2021 • 2022 • 2023 • 2024 • 2025 • 2026 The whole history is here.

Welkom · أهلا و سهلا · Xoş gəlmişsiniz · Вiтаем · Добре дошъл · স্বাগতম · Degemer mat · Dobrodošli · Benvinguts · Ⲛⲟϥⲣⲓ · Croeso · Velkommen · Willkommen · Sıma xeyr Amey · Κκαλώς ήρθες · Welcome · Bonvenon · Bienvenidos · Tere tulemast · Ongietorri · خوش آمدید · Tervetuloa · Tervettulemaa · Bienvenue · Wolkom · Fáilte · भळु-औणु · સુસ્વાગત · ברוכים הבאים · स्वागतम · Dobro došli · Isten hozott · Aloha · Բարի գալուստ · Benvenite · Selamat datang · Nno̱ · Bonveno · Velkommin · Benvenuti · ᐊᕆᐅᙵᐃᐹ · ようこそ · fi'i · Sugeng rawuh · კეთილი იყოს შენი მობრძანება · Tikilluarit · 환영합니다 · Salve · Wil sha · Bonveni · Wilkóm · Laipni lūdzam · ဘာသာမန် · സ്വാഗതം · स्वागत आ · Merħba · မြန်မာဘာသာ · Velkommen · Welkom · Velkommen · Bonvenio · Planvengut · ਜੀ ਆਇਆਂ ਨੂੰ · Witajcie · Bem-vindo · Allinmi hamusqaykichik · Bun venit · Добро пожаловать · स्वागतम् · Buresboahtin · ආයුබෝවන් · Vitajte · Pozdravljeni · Pyereestpuáttim · Soo dhowow · Mirëserdhët · Добро дошли · Wilujeng sumping · Välkommen · Karibu · ꠀꠃꠇ꠆ꠇꠣ · స్వాగతం · Хуш омадед · ยินดีต้อนรับ · yI'el · Mabuhay · kama pona · Hoş geldiniz · Räxim itegez · Maeva · Benvenescu · Гажаса ӧтиськом · خۇش كەپسىز · خوش آمديد · Chào mừng đến · Benokömö · კუჩხი ბედინერი ჸოფედას თქვანი მოზოჯუა · װילקום · Angqcoux · 欢迎 · 歡迎 · (edit)

---

ar: هذا الموقع الرئيسي لنقاش ويكي مصدر ومكان طلب المساعدة. استخدم اللغات التي تعرف، وترجم ما ترغب.
bn: এটি উইকিসংকলনের বিষয়বস্তু ও সমস্যা নিয়ে আলোচনা করার একটি কেন্দ্রীয় আলোচনার স্থান। প্রয়োজন হলে সাহায্য চাইতে পারেন। আপনি যে ভাষা জানেন তাই ব্যবহার করতে পারেন ও অনুবাদ করতে পারেন।
de: Dies ist eine zentrale Stelle, um alle Themen um Wikisource zu diskutieren, und ein Platz, um nach Hilfe zu fragen. Benutzen Sie die Sprache(n), die Sie beherrschen, und übersetzen Sie, was Ihnen gefällt.
diq: No wikiçıme heta merselan war ardış u mınaqeşe kerdış i heta cay peşti waştışiyo.Zıwanê ke şıma zanê ê zımani dı iştıraq bıkerê u açarnayış seni beno bıumısê.
el: Αυτή είναι η κεντρική τοποθεσία για να συζητήσετε θέματα για τη Βικιθήκη, αλλά και το μέρος για να ζητήσετε βοήθεια. Χρησιμοποιήστε τη γλώσσα (ή τις γλώσσες) που γνωρίζετε και μεταφράστε αυτά που θέλετε.
fa: این مکان مرکزی برای بحث در مورد مسائل درباره ویکی‌نبشته و مکانی برای درخواست کمک است. از زبان (هایی) که می‌شناسید استفاده کنید و آنچه را دوست دارید ترجمه کنید.
en: This is the central location for discussing issues with Wikisource, and the place to ask for help. Use the language(s) you know, and translate what you like.
eo: Ĉi tio estas la centra loko por diskuti problemojn pri Vikifontaro, kaj la loko por serĉi helpon. Uzu la lingvo(j)n kiu(j)n vi konas, kaj traduku kion vi volas.
es: Este es el lugar central para discutir cualquier asunto de Wikisource y es el lugar para pedir ayuda. Use los idiomas que conozca, y traduzca lo que crea necesario que otros sepan.
fr: Ceci est la page principale pour discuter de ce qui a trait à Wikisource, et pour demander de l’aide. Utilisez la (ou les) langue(s) que vous connaissez, et traduisez ce qui vous plaît.
ga: Seo an lárnionad chun téamaí a bhaineann le Vicífhoinse a phlé, agus an áit inar féidir leat cabhair a iarraidh. Bain usáid as teanga ar bith dá bhfuil agat agus aistrigh cibé rud is mian leat.
gbm: इ च मझळु अड्डा विकीसोतु दगड़ मुद्दा बारा म छुंई लगाणु खुणी, अर ठाणु मदद मंगण खुणी. इस्तेमाल कारा उ भाखा ज्व तुमु बिंगुदौ, अर बदलाखरा जू च पसंद​।
he: זה הדף המיועד לדיונים העוסקים בוויקיטקסט, והמקום לפנות לעזרה. כתבו בשפות שתכירו, ותרגמו מה שתרצו.
hy: Սա Վիքիդարանի հետ կապված հարցերի քննարկման կենտրոնական վայրն է, որտեղ դուք կարող եք նաև դիմել հարցերով։ Օգտագործեք ձեր իմացած լեզուն(երը) և թարգմանե՛ք ի՜նչ կամենում եք։
io: Ita esas la centrala loko por diskutar problemi pri Wikifonto, e la loko por serchar helpo. Uzez la linguo/i quan vu parolas, e tradukar quon/in vu volas.
it: Questo è il luogo principale dove discutere di Wikisource, e il posto dove chiedere aiuto.Scrivi nella lingua che vuoi, puoi anche tradurre quello che vuoi.
ja: ここはプロジェクトについて議論したり、質問がある時に尋ねたりするための場所です。お望みの言語を使って書き込んで下さい。他の人の書き込みを翻訳して下さる方も歓迎です。
ko: 이곳은 위키문헌과 관련한 논의를 하는 주된 곳이자 도움을 구할 수 있는 곳입니다. 구사할 수 있는 언어를 사용하여 다른 내용을 마음껏 번역해 주시길 바랍니다.
my: ဤနေရာသည် ဝီကီရင်းမြစ်နှင့် ပတ်သက်သော ကိစ္စအဝဝအား ဆွေးနွေးရန်နှင့် အကူအညီများအတွက် မေးမြန်းရန် နေရာဖြစ်သည်။ သင်ကျွမ်းကျင်သော ဘာသာစကားကို အသုံးပြုနိုင်ပြီး သင်အလိုရှိရာကို ဘာသာပြန်နိုင်သည်။
nl: Dit is de centrale plek om elk onderwerp in Wikisource te bediscussiëren en de plaats om hulp te vragen. Gebruik de taal die je kent en vertaal wat en wanneer je wilt.
nn: Dette er den sentrale staden å diskutere saker som gjeld Wikisource, og staden for å be om hjelp. Bruk dei språka du kan, og set om det du vil.
pa: ਇਹ ਵਿਕੀਸਰੋਤ ਨਾਲ ਮੁੱਦਿਆਂ 'ਤੇ ਚਰਚਾ ਕਰਨ ਲਈ ਕੇਂਦਰੀ ਸਥਾਨ ਹੈ, ਅਤੇ ਮਦਦ ਮੰਗਣ ਦੀ ਜਗ੍ਹਾ ਹੈ। ਉਹ ਭਾਸ਼ਾ(ਵਾਂ) ਵਰਤੋ ਜੋ ਤੁਸੀਂ ਜਾਣਦੇ ਹੋ, ਅਤੇ ਆਪਣੀ ਪਸੰਦ ਦਾ ਅਨੁਵਾਦ ਕਰੋ।
pt: Esta é a página principal para discutir tudo o que se relaciona com o Wikisource e também o lugar para procurar ajuda. Faça uso da(s) língua(s) que conhece, e traduza os textos que quiser.
ru: Это центральное место для обсуждений, связанных с Викитекой в целом, а также место, где можно спросить о помощи. Используйте язык, который вы знаете и переводите что и когда вам нравится.
sl: To je osrednje mesto za razpravo o zadevah Wikivira in kraj, kjer lahko zaprosite za pomoč. Uporabljajte jezik(e), ki ga (jih) poznate, in prevedite, kar vam je všeč.
su: Ieu mangrupa loka pikeun nyawalakeun hal-hal ngeunaan Wikisource, sarta tempat pikeun ménta pitulung. Pigunakeun basa nu ku anjeun dipikawanoh, tarjamahkeun nu dipikaresep.
sv: Detta är den huvudsakliga platsen där alla typer av frågor rörande Wikisource diskuteras och där nya frågor kan ställas. Använd de språk som du kan och översätt när och vad du vill av andra.
syl: ꠁꠈꠣꠘ ꠃꠁꠇꠤꠒꠣꠇꠞ ꠛꠤꠡꠄꠀꠡꠄ ꠀꠞ ꠖꠄꠖꠞꠛꠣꠞ ꠟꠂꠀ ꠝꠣꠔꠣꠞ ꠄꠉꠥ ꠝꠥꠟ ꠎꠦꠉꠣ ⁕ ꠁꠘꠅ ꠖꠄ ꠖꠞꠇꠣꠞꠦ ꠡꠣꠄ ꠡꠣꠁꠎ꠆ꠎꠅ ꠌꠣꠁꠔꠣ ꠙꠣꠞꠂꠘ ⁕ ꠀꠙꠘꠦ ꠎꠦ ꠜꠣꠡꠣ ꠎꠣꠘꠂꠘ ꠅꠐꠣꠃ ꠛꠦꠛꠀꠞ ꠇꠞ꠆ꠔꠣ ꠙꠣꠞꠂꠘ ꠀꠞ ꠅꠘꠥꠛꠣꠖ ꠇꠞ꠆ꠔꠣ ꠙꠣꠞꠂꠘ ⁕
th: ที่แห่งนี้เป็นศูนย์กลางสำหรับการพูดคุยปัญหาต่าง ๆ เกี่ยวกับวิกิซอร์ซ และเป็นที่สำหรับขอความช่วยเหลือ คุณสามารถใช้ภาษาที่รู้จักและแปลสิ่งที่คุณต้องการ
tl: Ito ang sentrong lokasyon para pag-usupan ang mga isyu kasama ng Wikisource, at ang lugar upang humingi ng tulong. Gamitin ang (mga) wika na alam mo, at isalin ang anong gusto mo.
vi: Đây là trung tâm để thảo luận các vấn đề liên quan đến Wikisource. Bạn sử dụng các ngôn ngữ bạn biết, và dịch những gì bạn thích.
vo: Atos binon top cifik, kö mögos ad bespikön valikosi dö Vükifonät, e kö kanoy i begön yufi. Gebolös pükis, kelis sevol, e tradutolös utosi, kelosi vilol.
yue: 呢度係主要討論維基文庫相關問題嘅版面。你可以用你識得嘅語言留言，亦都可以幫手翻譯其他人嘅留言。
zh-hant: 這裡是討論與維基文庫有關話題和尋求幫助的頁面。使用您所了解的語言留言。您也可以在任何時候把他人的留言翻譯成您熟悉的語言。
zh-hans: 这里是讨论与维基文库有关话题和寻求帮助的页面。使用您所了解的语言留言。您也可以在任何时候把他人的留言翻译成您熟悉的语言。
(edit)

Thank You for Last Year – Join Wiki Loves Ramadan 2026

Dear Wikimedia communities,

We hope you are doing well, and we wish you a happy New Year.

Last year, we captured light. This year, we’ll capture legacy.

In 2025, communities around the world shared the glow of Ramadan nights and the warmth of collective iftars. In 2026, Wiki Loves Ramadan is expanding, bringing more stories, more cultures, and deeper global connections across Wikimedia projects.

We invite you to explore the Wiki Loves Ramadan 2026 Meta page to learn how you can participate and sign up your community.

📷 Photo campaign on Wikimedia Commons

If you have questions about the project, please refer to the FAQs:

• Meta-Wiki
• Wikimedia Commons

Early registration for updates is now open via the Event page

Stay connected and receive updates:

• Telegram channel
• Mailing list

We look forward to collaborating with you and your community.

The Wiki Loves Ramadan 2026 Organizing Team 19:45, 16 January 2026 (UTC)

Support for Bodo Wikisource (Ws/brx) on Wikimedia Incubator

Hello,

I am working on setting up Bodo Wikisource (language code: brx) on Wikimedia Incubator. I would like guidance on ProofreadPage, Index creation, and language approval process.

Bodo is an officially recognized language of India and is written in Devanagari script.

Thank you. Bkbrahma1 (talk) 07:37, 21 January 2026 (UTC)

Page language

It is possible to change page language from default to Lingua Franca Nova (lfn for Main Page/Lingua Franca Nova, La Prea a Senior and Jura de Hipocrate? Thanks in advance. Evelino Ucelo (talk) 17:10, 5 February 2026 (UTC)

Best place to translate meta-works about the capture of knowledge?

There are some interesting freely licensed works about librarianship, archiving, and the like. E.g. this recent paper on Content Authenticity and Provenance -- which are often in just one language and not well indexed, but bear preserving and translating. Is there a good WS project or collection for such things? Does it make sense to have a language-neutral wikiproject for collecting this type of knowledge across the field? Sj (talk) 18:52, 11 February 2026 (UTC)

• English: My initial thought is that it makes the most sense to transcribe the original text on en: (or whatever the source language is) and then allow the other languages' projects to pursue their own translations in accordance with their own policies. Perhaps coordination could be done via a multilingual wikiproject, like Wiksource:WikiProject Translations or similar. I've just started looking around the multilingual wikisource myself so I'm not sure if we have any more infrastructure than the mere possibility of organizing such a thing. -- Mathmitch7 (talk) 22:43, 2 March 2026 (UTC)

Did some Author category cleanup, thinking about next steps

• English: Good morning all, I recently moved around a bunch of categories in Category:Authors. Notable additions include Category:Authors by language, Category:Authors by profession. I also updated WS:LANG to include a column for language-specific Author categories, which are also (generally) collected in Category:Authors by language. There is presently no consistent organization for the language author categories, which I think is fine, but I'd be interested in making some kind of consistency which we can use going forward.

My thinking is that we could create categories like Category:eng authors or Category:zho authors for all of the languages represented here on multi-language wikisource with ISO-639 codes. Then, either redirect those pages to their respective language-specific Author categories (when they exist); or use them as their own category which would then be categorized into both the language's category and Category:Authors by language. For example, Category:lv authors would redirect to the Latvian-language Category:Autori, while Category:tpn authors would serve as the equivalent Tupi-language category. This would help provide some useful infrastructure to support new languages works and authors in the future.

Thoughts? I'm open to suggestions. Don't want to be overly English-oriented, or create too much administrative burden for new users and language content. -- Mathmitch7 (talk) 18:26, 3 March 2026 (UTC)

• English: An additional thought: I think it would be helpful if we created category pages for each ISO 639-1 code, possibly -2 or -3 as well for at least the languages included on multilingual wikisource and on their own subdomains. These would generally redirect to the language categories. For example, Category:en would redirect to Category:English, Category:lv would redirect to Category:Ladin, Category:Ru would redirect to Category:Русский. This would just be helpful for quickly categorizing works without having to find the specific "correct" category. Again, let me know what you think. Mathmitch7 (talk) 23:34, 3 March 2026 (UTC)

Update to this, I think I really like the solution tried on Category:Pt Português (Portuguese), a combination of ISO-639, emic/native language name, and language name in English. I would propose that we move all language categories (ie in Category:Languages) to this scheme. Recognizing of course that it can be tricky to mix rtl and ltr systems, as well as across different scripts. Even so, this seems a fair and usable solution. For example:

• Category:English -> Category:En English (English)
• Category:Ancient Greek -> Category:Grc Ἀρχαία ἑλληνική (Ancient Greek)
• Category:Polski -> Category:Pl Polski (Polish)
• Category:Русский -> Category:Ru Русский (Russian)
• Category:Mingrelian -> Category:Xmf მარგალური (Mingrelian)
• Category:سِنڌِي -> Category:Sd سِنڌِي (Sindhi)

Again, let me know what you think. Obviously changing category names can be a huge pain but I think long-term this is as good a plan as any.

Mathmitch7 (talk) 18:23, 14 April 2026 (UTC)

@Mathmitch7: That's indeed a point in which I stumbled and wanted to act upon. I have no opposition to your change. :) Anything that brings a strand of consistency in this mess is welcome.

For the record -- and this is not meant to hinder your action, just putting ideas out there, -- I was thinking of making category names something much more mechanical, like Category:Works:ru and Category:Authors:ru (or equivalent, as you initially suggested), and then have a gadget that could come by on the client-side and alter the displayed category name depending on the selected language of the user, e.g. if one selects Spanish, those would appear as "Obras (ruso)" and "Autores (ruso)" respectively. This has the advantage of fully implementing the internationalisation ideals of this project, a Spanish speaker should be ideally be able to have the entire project's structural text (i.e. any text that isn't a work transcription) in Spanish. Furthermore, while "native name (english name)" may look perfectly fine for things like Polish, as soon as you get to extinct langauges, or minority languages without a standard orthography, things get problematic. For example, taking from your list, "Ἀρχαία ἑλληνική", does not really mean "Ancient Greek" as ancient Greeks would call it, but rather it's the modern name in ancient spelling (again, it would still be the best option available, so feel free to go with your change), and when it comes to languages like Sumerian, Ugaritic or Ancient Egyptian, what do we put in the native name? In many cases there will be something, but who would that be useful for, except mummies coming back from the dead? This ultimately boils down to an important division that was not well taken into consideration in the Wikisource movement in general: the distinction between content languages (the language in which the transcribe works are into) and the working languages (in which the UI appears, a site operates and a community communicates). This is also why, in my opinion, splitting Wikisources into subdomains was a particularly near-sighted move, why does should reading a Latin text come at the price of having Latin UI? Why should there be an entirely separated set of infrastructure (modules, templates) just on the criterion of the language the transcribed work transcribing is in? The split, driven by technical limitations that we had at the time which can easily be fixed in other ways now (like right-to-left text, which prompted the first subdomain, Hebrew Wikisource, which had this catastrophic domino effect) is showing its failure in almost every aspect, both moral and technical, and those paying the price are the minority languages, whose editors are forced to work in this graveyard of incoherent and unmaintained infrastructure, with the hope of getting their own subdomain, only to be then further alienated from the rest of the community once achieved, helpless to infrastructural bugs and vandalism.

Enough rambling, back to the issue at hand, the proposed gadget idea. Making one is not something impossible, as we have something similar in English Wiktionary, wikt:en:MediaWiki:Gadget-categoryTreeLanguageNames.js, by the excellent coder @Surjection, where for example if you are on wikt:en:Category:Cats, the subcategory Category:ru:Cats will display as "Category:ru:Cats [Russian]". A while ago, I tried implementing a similar thing here, but I remember running in a number of technical difficulties. A difference in implementation was that on enwikt the scope is much more limited -- the only needed display language is English, -- and since that project employs some non-ISO language codes, the most sensible idea was to have a project-specific JSON to house all the code-to-language correspondences, wikt:en:Module:languages/code to canonical name.json, meanwhile here we need to have the name for every language in every language, with all the fallback rules, which is why we are better off relying on the central Wikimedia database that contains all of that. I cannot remember what ultimately stopped me from finishing this gadget, I think the implementation was getting too hacky.

TLDR: There are some ultimate issues that you will encounter trying to implement this for every language, but anything would be better than what we have now, so feel free to do it. :) Catonif (talk) 13:44, 15 April 2026 (UTC)

All these points are well-met (Maybe someday we can re-unite the wikisources :') ). I think that ultimately organizing the kind of gadget you describe is a good plan, and my proposal is an adequate in-between step. I'd maybe like to hear at least one other editor's thoughts on the matter before going ahead with that big of a change, though.

Maybe analogous categories would be Category:En English Authors and Category:Co Autori in corsu (Corsican authors). I don't know, nothing is perfect.

Do you happen to know if there's a good way to change a category's name other than just moving its page, finding everything that links there, and changing them individually? Do other wikis just use bots?

— Mathmitch7 (talk) 18:50, 15 April 2026 (UTC)

You are thinking about commons:Help:Gadget-Cat-a-lot Ignacio Rodríguez (talk) 03:48, 16 April 2026 (UTC)

TEI (Text Encoding Initiative) gadget

@Pecha-pema, Abhignkr47, Saaifa, Mathmitch7: and anyone interested. Greetings, pleasure to meet you and sorry to disturb. Apologies for writing in English. You appear to be the most active on Multilingual Wikisource of the latest days. I'm sorry for whoever interested I did not alert, I did not want to send out too many unwanted pings.

In short, I have written a gadget that can render TEI XML-format texts as HTML. (You can turn it on in your preferences and check how it handles TEI:Fare i ri ëvetar shqip. A brief explanation is at Wikisource:TEI Gadget.) It is a format used for a more scholarly kind of transcription, mainly used for palaeography, manuscripts or thorough critical digital editions. This is not meant as a replacement of the current situation but a way to better digitalise the cases which are not well-handled by Wikitext.

For technical reasons, mostly about security, the solution requires a new namespace (i.e. the thing that comes the colon in a page title, like Page: or Talk:), so I have to file a technical request for the namespace TEI:. As regrettably scatterful as this project is, I assume that such a change would not be carried through without an attempt at a discussion with other editors. For this reason, I ask here whether any of you would oppose such a change.

Thank you for your love of writing, and the work you do to record it. :) Catonif (talk) 16:23, 13 March 2026 (UTC)

• English: Personally I'm fine with having a TEI: namespace or something similar. Support for this kind of document format would be very helpful and putting TEI documents into their own namespace seems like a good way to integrate it with our existing workflow, using a TEI: page as a source and then transcluding it to a normal "work" namespace using a template/Lua module.

However, I would like to see us think about how we could use TEI or TEI markup alongside the existing Page transcription and transclusion workflow. I think one of the best things about Wikisource is that pages in the mainspace are generally linked back to their source scan in an easily verifiable, traceable, and auditable way. Although TEI is great for transcriptions, I don’t yet see an analogue for that particular type of "backing" to a scan. The example document you link has source information, but some work would need to be done to get to something as granular as what we already have for scan verification and to support proofreading efforts.

That all being said, if the gadget works and TEI-XML is as robust as it appears to be, I’m fine with doing what must be done to implement support for it. If that includes a special namespace, at least here on multilingual ws, I support. Cheers! -- Mathmitch7 (talk) 19:45, 13 March 2026 (UTC)

Hello, thanks for your thoughts and your support! :) I agree that scan-backed transcription is the strongest point of boast for Wikisource. The thing is that the transformers are very versatile, which isn't well visible by the example I gave, which only shows two almost-identical transformer schemes, with the only difference being script (if it can help get the idea, the green-boxed header is also generated by a transformer of the same structure.) With this in mind, my thought was to have "Original scan" as one of the selectable transformers (i.e. a column), which is fairly easily doable, just requires for the transformer to ignore all tags, except for ("page break"), which would show the images.

I was going to implement this, I didn't because there is an unrelated ongoing bug which makes the pages of DJVU files not display. See for example Page:Veqilharxhi - Ëvetar (1845).djvu/1 (the same work already in wikitext). The page image used to work a while ago. So for now it would have looked like a bunch of error messages in mainspace. But it's definitely doable once the bug is fixed. :)

This to me is also a way to make the scans more immediately accessible to the reader. I find them to be very valuable, especially in cases of manuscripts and other kind of texts in which TEI in particular shines, and having scans into a separate namespace always felt a bit like hiding them to me. The idea of having them user-toggleable seemed quite neat.

Admittedly, it is true that it will never be as easy. TEI is inevitable much more cumbersome, difficult to learn and master, and in many cases harder to read from the source. The main workspace of editors using will most likely never be the Wikisource editor box, but rather VS Code with the "Scholarly XML" extension (AFAIK, most accessible widely used TEI environment), or similar software. For these reason, I emphasise that that TEI is meant for those who particularly have a lot of time and dedication at their disposal, and are willing to go through the hardships that are required to get something of academic quality. The vast majority of texts will be kept in wikitext. Catonif (talk) 20:32, 13 March 2026 (UTC)

What are the security concerns of having such a namespace enabled and how would you deal with them? Recently there was a mass deletion of random articles in multiple wikis because of a personal JS script gone rogue. PS: (I am well in favor of offering the wide community a sufficiently good for them standard for transcribing. Also I guess there is plenty of text already transcribed this way we could incorporate.) Ignacio Rodríguez (talk) 11:36, 1 April 2026 (UTC)

@Ignacio Rodríguez: Sorry for the late reply, I didn't see your message, and thank you for your support. Since my post here I have come to a solution, which is to handle the TEI-to-HTML transformation within Lua, and let the gadget only handle the columns display. This has a number of disadvantages: JavaScript is much better at handling XML (it was infact built for that purpose), now a separate Lua XML parser is required and we are likely to hit Lua's memory limit with files too large, while a pure JS implementation was much easier to maintain and had no limitations. However we cannot let just any editor write JavaScript that runs on other people's browsers, as the event you mention exemplifies, so the script pages would have needed to be protected under some specific right. But being able to edit and write these scripts is such a central thing for my intended versatile implementation of TEI that I would rather hit the memory limit rather than only allowing very few people to benefit from the infrastructure. As such, the security justification should be gone once I fully implement the Lua solution, and the namespace will be requested only for conceptual reasons. Catonif (talk) 20:24, 12 April 2026 (UTC)

@Catonif maybe it would be better in the long run to build a TEI MediaWiki extension. The gadget is fine by now, but memory limits are concerning. I am no coder but I can cheer you up. For the record I support the creation of the TEI Namespace. Ignacio Rodríguez (talk) 22:44, 12 April 2026 (UTC)

@Ignacio Rodríguez: Absolutely agreed. There exist, in fact, mw:Extension:TEI and mw:Extension:CETEIcean, which I tried testing around, on my own installing of MediaWiki. These are not very well documented projects and it was quite difficult to untangle something out of the code, but to me these seem overly complicated systems with a much more limited outcome, lacking the versatility that TEI was built with in mind, hence not very fit for a project like Wikisource. Furthermore, Extension:TEI, from a quick glance, does not appear to be fully TEI-compliant, allowing for questionable tag names (see here), as instead of , while CETEIcean is not HTML-compliant, as you can see from your inspector on this example, with tag names like in the HTML fed straight to the browser. I had even tried making my own extension, only to realise that it is much beyond my capabilities, and eventually settled for an awkward Lua implementation. Then I got the idea of a much cleaner JavaScript system, only to come back to Lua in the end for the reasons described. My hope is that my implementation is merely a proof of concept for someone more knowledgeable to notice and make better. Catonif (talk) 22:42, 13 April 2026 (UTC)

I see. I was hoping it was within your capabilities. You seem to be very skilled as both those implementations are neat. Maybe you should import some more works in that format, so we grow the need and visibility of the project. If I ever stumble upon some interesting TEI-proofread Spanish works, I might give this a try Ignacio Rodríguez (talk) 12:50, 14 April 2026 (UTC)

Images for "toki soweli tan jan Beatrix Potter" are broken because of an incorrect thumbnail size

When trying to edit toki soweli tan jan Beatrix Potter, all of the page images are broken. (Example: Page 938, obtained from the "Image" tab at the top of Page:Toki soweli tan jan Beatrix Potter.pdf/938)

It looks like this is because the images are using 872px as the thumbnail size. Setting the size of the thumbnail manually in the URL to 960px (or any of the other sizes listed here) fixes the issue (fixed URL for page 938).

Is there a way for the default thumbnail size be changed to something other than 872px so the images show up properly in the editor?

Thanks in advance.

Tymewalk (talk) 03:47, 19 March 2026 (UTC)

• English: This strikes me as a weird quirk or possible bug in ProofreadPage. I can confirm that I get the same kind of broken page image, using Firefox 148.0.2 for Windows, and the Monobook skin. I’ll see if I can force a fix by just purging some pages here and on commons, as sometimes that fixes issues with PDFHandler. Otherwise, we can try posting over to mw:Project:Village Pump and see if anybody knows if it’s related to a known and tracked issue, or if it needs a new issue reported. -- Mathmitch7 (talk) 18:23, 23 March 2026 (UTC)

Proposed changes to Main Page

I think we should:

1. Move it to Wikisource:Main Page and
2. Include some text introducing that this is a stand-alone wiki, not just a portal. I think we should explain that this wiki hosts:
   • Multilingual works
   • Works in a language with too small a corpus
   • Works that are incubating to a subdomain
   • Works that are made up of non-linguistic content
   • Works with languages that have subdomains but that won't accept a particular work for whatever reason

Thoughts on these changes? —Justin (koavf)❤T☮C☺M☯ 06:20, 25 March 2026 (UTC)

• English: I think about this a lot, and I don’t have a great answer. Honestly, my ideal would be to split multi-lingual WS into mul.wikisource.org, and organize it as its own project, and make this main wikisource.org just a portal to those other sites, similar to how Wikipedia works (and by default redirecting all traffic to specific pages to the page on mul.ws). I think that would be clearer to people, including editors. However, that’s a pretty big change, and I wouldn’t move forward with it without substantial discussion both here and at individual language subdomains.

In the meantime, I think your proposal’s points are reasonable. I don’t see a particular reason to move the main page to Wikisource:Main Page, but everything else seems fine. I would also add that the main page should specifically say "Welcome to Multilingual Wikisource." -- Mathmitch7 (talk) 13:01, 30 March 2026 (UTC)

I agree with Mathmitch7. Moving to mul.wikisource.org seems like a good idea. Like Wikidata and Wikispecies, we should have a centralized and organized Main Page for each language using Extension:Translate --Namoroka (talk) 09:27, 4 April 2026 (UTC)

I support revising our Main Page. Yet to split multi-lingual WS into mul.wikisource.org sounds excessive for now.--TunnelESON (talk) 03:56, 6 April 2026 (UTC)

That's fair enough. Even so, multilingual WS has over 61,000 pages in the main namespace, about double the size of Portuguese Wikisource. Just saying that splitting it off may be a good idea. But again, it's a bigger discussion. -- Mathmitch7 (talk) 18:18, 6 April 2026 (UTC)

Here’s some proposed wording in English. Let me know if that seems adequate:

Welcome to Wikisource, the free library that anyone can improve.

This is Multilingual Wikisource, a site for works in all languages, and for connecting different language-specific Wikisource projects. Works on this site include:

• Works in multiple languages
• Works in languages that do not have their own language subdomain (for example, languages with a small corpus)
• Works made up of non-linguistic content
• Works in languages that have language subdomains, but cannot be hosted on those sites due to their site-specific policies

--Mathmitch7 (talk) 19:39, 6 April 2026 (UTC)

That's a nice shot and it finally makes clear on the homepage what this site is. —Justin (koavf)❤T☮C☺M☯ 02:33, 7 April 2026 (UTC)

This has been open for a couple of months and I feel like there's sufficient opportunity to complain if someone doesn't like the changes. ―Justin (koavf)❤T☮C☺M☯ 07:12, 5 June 2026 (UTC)

 Support.--TunnelESON (talk) 03:54, 6 August 2026 (UTC)

Upcoming Wikimedia Café meetup regarding the the 2026-2027 Wikimedia Foundation Annual Plan

Pine (talk) 05:18, 29 March 2026 (UTC)

Action Required: Update templates/modules for electoral maps (Migrating from P1846 to P14226)

Hello everyone,

This is a notice regarding an ongoing data migration on Wikidata that may affect your election-related templates and Lua modules (such as Module:Itemgroup/list).

The Change:
Currently, many templates pull electoral maps from Wikidata using the property P1846, combined with the qualifier P180: Q19571328.

We are migrating this data (across roughly 4,000 items) to a newly created, dedicated property: P14226.

What You Need To Do:
To ensure your templates and infoboxes do not break or lose their maps, please update your local code to fetch data from P14226 instead of the old P1846 + P180 structure. A list of pages was generated using Wikimedia Global Search.

Deadline:
We are temporarily retaining the old data on P1846 to allow for a smooth transition. However, to complete the data cleanup on Wikidata, the old P1846 statements will be removed after May 1, 2026. Please update your modules and templates before this date to prevent any disruption to your wiki's election articles.

Let us know if you have any questions or need assistance with the query logic. Thank you for your help! ZI Jony using MediaWiki message delivery (talk) 17:11, 3 April 2026 (UTC)

Hi all, as far as I can tell, multilingual Wikisource is not affected by this change at all. Let me know if you think otherwise. -- Mathmitch7 (talk) 17:45, 6 April 2026 (UTC)

Tech News: 2026-15

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 CampaignEvents extension now includes a new group goal-setting feature, enabling organizers to set and track event goals such as the number of articles created and participating contributors in real time. Similarly, participants can work toward shared targets and see their collective impact as the event unfolds. The feature is now available on all Wikimedia wikis. Learn more in the documentation.
• The new watchlist labels feature (announced in Tech News 2026-07) is now available via VisualEditor, the source editor, and the 'watchstar' (or watch link, for skins that don't have a star icon). Previously it was only possible to assign labels via EditWatchlist. In all three places it is a new field following the expiry field.
• View all 23 community-submitted tasks that were resolved last week. For example, the issue where talk pages on mobile with Parsoid are unusable after empty section headers, has now been fixed. [1]

Updates for technical contributors

• The sub-referencing feature, which lets editors add details to an existing reference without duplicating it, will be gradually rolled out to more wikis later this year. Wikis using the Reference Tooltips gadget are encouraged to update their version (typically at MediaWiki:Gadget-ReferenceTooltips.js as shown here) to ensure compatibility. Other reference-related gadgets may also be affected. [2]
• All Wikinews editions will be closed and switched to read-only mode on 4 May 2026. Content will remain accessible, but no new edits or articles can be added. This closure was approved by the Board of Trustees of the Wikimedia Foundation following extended discussions. Read more.
• The Action API has had several formats for requested output. One of them, format=php, is being removed soon. Please ensure your scripts or bots use the JSON format. This removal should affect very few scripts and bots. [3]
• The Special:NamespaceInfo page now includes namespace aliases. For example "WP" for the "Project" ("Wikipedia") namespace on the German Wikipedia. [4]
• 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 16:19, 6 April 2026 (UTC)

Bot Flag Request for User:SchlurcherBot

Appologies for posting in English. Also, I could not locate a dedicated page for bot request in English Wikisource, so I am posting here. Please direct me to the correct page if one exists. Thank you.

• Bot name: User:SchlurcherBot
• Bot operator: commons:User:Schlurcher
• Bot task: Automatically convert links from http:// to https:// (secure protocol migration)
• Technical details: Please see meta:User:SchlurcherBot for full details, including the expected number of affected URLs on English Wikisource.
• Bot flags on other projects: Global bot status granted. Also flagged on English Wikipedia, German Wikipedia, French Wikipedia, Italian Wikipedia, Polish Wikipedia, Portuguese Wikipedia, and Commons. For a full list, see: sulutil:SchlurcherBot
• Comment: The bot is globally approved and active on the top 10 Wikipedia projects. As this wiki has opted out of the global bot policy, I am requesting permission to perform these link updates on English Wikisource as well. Please let me know if a local bot flag can be granted or if you have any questions. Thank you. --Schlurcher (talk) 07:59, 7 April 2026 (UTC)

Hi, you can submit this request over to the en.wikisource Scriptorium under the "Bot Requests" section, and it will get more targeted en.ws attention. If you'd also like to submit your request to Multilingual Wikisource (this site), let us know. -- Mathmitch7 (talk) 12:47, 7 April 2026 (UTC)

@Mathmitch7: This request was made for the project sourceswiki so the multilingual wikisource (this site). I also plan to request each individual language like enwikisource, dewikisource eventually as well. Hope this helps. --Schlurcher (talk) 08:11, 8 April 2026 (UTC)

My apologies, I misunderstood! I support approving this bot. Mathmitch7 (talk) 12:26, 8 April 2026 (UTC)

@-jkb-, @Koavf, @Ooswesthoesbes, @TunnelESON. Please let me know if Bot status can be granted. --Schlurcher (talk) 06:52, 17 April 2026 (UTC)

@User:Schlurcher: Looks goed, so granted. --Ooswesthoesbes (talk) 08:07, 17 April 2026 (UTC)

Tech News: 2026-16

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

• Experienced editors are invited to test the Article guidance feature, designed to help less-experienced editors create well-structured, policy-compliant Wikipedia articles. Testing instructions are available. Also, after reviewing the outlines, please provide feedback on the project talk page. Based on your input, the feature will be refined and transferred to the pilot Wikipedias to translate and adapt. Check out the video explaining the feature.

Updates for editors

• On most wikis, all autoconfirmed users can now use Special:ChangeContentModel page to create new pages with custom content models, such as mass message lists, making custom page formats more accessible. Check Special:ListGroupRights for the status of your wiki. [5]
• The Growth team has launched an account creation experiment to evaluate whether adding an account creation button to the mobile web header increases new account registrations and encourages more mobile users to contribute to the wikis. The experiment is currently live on Hindi, Indonesian, Bengali, Thai, and Hebrew Wikipedia, and targets 10% of logged-out mobile web users.
• View all 30 community-submitted tasks that were resolved last week. For example, an issue where VisualEditor could get stuck loading on Windows devices with animations turned off, has now been fixed. [6]

Updates for technical contributors

• Starting later this week, Abuse filter editors who have the ⧼codemirror-beta-feature-title⧽ beta feature enabled will have CodeMirror instead of CodeEditor as the editor at Special:AbuseFilter. This is part of the broader effort to make the user experience more consistent across all editors. [7][8]
• Tools and bots that access the Notifications API (action=query&meta=notifications) will need to update their OAuth or BotPassword grants to also include access to private notifications. [9]
• Due to a library upgrade, listings on category pages may be displayed out of order starting on Monday, 20th April. A migration script will be run to correct this, and will take hours to days depending on the size of the wiki (up to a week for English Wikipedia). [10]
• 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 15:19, 13 April 2026 (UTC)

Tech News: 2026-17

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

• After two years of development, ⧼codemirror-beta-feature-title⧽, also known as CodeMirror 6, is to be promoted out of beta on Tuesday, April 21. It brings better code and wikitext readability, reduction in typing errors, and other benefits to all users of the standard syntax highlighter. A huge thank you to volunteer Bhsd who developed many of the new features, including code folding, autocompletion, and linting. [11]
• A major update to the Wikipedia app for iOS is now rolling out, redesigning the interface to align with Apple's latest "Liquid Glass" visual design. Download the latest version and explore the update.

Updates for editors

• Reading lists is a feature which allows readers to save articles to a list for reading later. This feature is now in beta on Arabic, French, Indonesian, Vietnamese, and Chinese Wikipedias and by default for all new accounts on all Wikipedias.
• An experiment which explores extending Page Previews to mobile web will be launched in the week of April 20 on Arabic, English, French, Italian, Polish, and Vietnamese Wikipedias. Page Previews are pop-ups that display a thumbnail, lead paragraph, and a link to open the full article of a blue link, thereby improving content discovery. The feature is already available on desktop and in the apps. Read more about this experiment and others.
• On several wikis, logged-in editors who haven't confirmed their email addresses can now see a banner encouraging them to do so. Having the email address confirmed allows a user to restore access to the account if they lose it. Learn more. [12]
• View all 15 community-submitted tasks that were resolved last week. For example, an issue where editing very large wiki pages in the 2017 wikitext editor caused slow loading, preview and scrolling lag, and performance issues when selecting, cutting, or pasting content, has now been fixed. [13]

Updates for technical contributors

• As part of the promotion of CodeMirror from a beta feature, all users will use CodeMirror instead of CodeEditor for syntax highlighting when editing JavaScript, CSS, JSON, Vue and Lua content pages. [14]
• The mirrors.wikimedia.org service for Debian and Ubuntu users will sunset and stop working on May 15. The resources for the service will be replaced with new and better options. Some users may need to switch to a different server which should take about a minute. You can read more. [15]
• The image and oldimage table will be removed from wikireplicas. If your tools or queries access image or oldimage directly, please update them to use the file and filerevision table before 28 May. [16]
• Following the recent implementation of global API rate limits on unidentified traffic, the Wikimedia Foundation will continue efforts to ensure fair use of infrastructure by applying global limits to identified API traffic beginning the last week of April. These limits are intentionally set as high as possible to minimise impact on the community. Bots running in Toolforge/WMCS or with the bot user right on any wiki should not be affected for now. However, all developers are advised to follow updated best practices. For more information, see Wikimedia APIs/Rate limits and Frequently Asked Questions.
• The Attribution API is now available as a beta. The API fetches information for crediting Wikimedia articles and media files wherever they are used. Reference documentation is available through the REST Sandbox special page available on all Wikimedia wikis (such as the REST sandbox on English Wikipedia). Share your feedback on the project talk page.
• There is no new MediaWiki version this week.

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

MediaWiki message delivery 15:00, 20 April 2026 (UTC)

Request for comment (global AI policy)

A request for comment is currently being held to decide on a global AI policy. Thank you! MediaWiki message delivery (talk) 00:58, 26 April 2026 (UTC)

Tech News: 2026-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

• There is a change in how new users are autoconfirmed that will improve anti-vandalism protection. Currently, users who have had an account for a few days and made a few edits are automatically added to the Autoconfirmed users group. This configuration tends to be exploited by some vandals, who create accounts and start to use them only after some time. To mitigate this, the configuration will be updated next week so that – for the purpose of becoming autoconfirmed – the account age will be counted from their first edit, instead of registration date. The numeric value of the age threshold will remain the same. This change will be deployed only to wikis which require at least one edit as part of the autoconfirmation conditions. [17]
• All Wikipedia users with new accounts and those who activated the "automatically enable most beta features" option in their preference can now use the reading lists beta feature to save articles for later reading. This helps organize reading interests in one place for convenient access.
• View all 30 community-submitted tasks that were resolved last week. For example, the issue where infobox images have huge padding in Firefox, has been fixed. [18]

Updates for technical contributors

• As a reminder, the global API rate limits will be applied this week to identified API traffic. This is to help ensure fair use of infrastructure. Bots running in Toolforge/WMCS or with the bot user right on any wiki should not be affected for now. However, all developers are advised to follow updated best practices. For more information, including the actual rate limits, see Wikimedia APIs/Rate limits and Frequently Asked Questions.
• 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:06, 27 April 2026 (UTC)

Tech News: 2026-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 Article guidance team invites experienced editors of pilot Wikipedias—Arabic, Bangla, Japanese, Portuguese, Persian, Turkish, Simple English, Spanish, and French—to help translate and adapt sample outlines. These outlines will guide editors in creating clear, well-structured, and policy-compliant articles when using the feature once it is launched in May 2026. Simple instructions on how to translate and adapt the outlines are available.

Updates for editors

• The Product and Technology Advisory Council has published draft recommendations on a model that affiliates can follow when contributing to the technical space. Community members are invited to provide feedback on the recommendation until May 8th on the talk page.
• The number of available thumbnail size preferences in MediaWiki is being reduced to three standardized options—Small (180px), Regular (250px), and Large (400px), as part of ongoing efforts to improve performance and reduce strain on thumbnail services. As a result, existing preferences will be mapped to the nearest new size (for example, smaller selections like 120px or 150px will render at 180px, while larger ones like 300px or 360px will render at 400px). The preferences interface will soon be updated to reflect these changes, and users who wish to opt out or provide feedback can do so. [19]
• From now on, even when a permission expires automatically, users will receive an Echo notification similar to the standard notification for permission changes. There is a difference between this and Global reminder bot in that the latter reminds users a week before the rights are due to expire, so that they can renew the rights.
• View all 32 community-submitted tasks that were resolved last week. For example, the problem where the ULS language selector in Special:Translate would scroll vertically when it shouldn't, has been resolved. Previously, when users opened the "Translate to English" dropdown and typed certain inputs, the dialog would scroll vertically by a few pixels even when there was enough space to display all results. The dropdown no longer shifts unnecessarily when filtering languages. [20]
• The Global Watchlist, which lets you view your watchlists from multiple wikis on a single page, continues to improve. For example, watchlists for Wikibase sites such as Wikidata now support EntitySchema elements for better tracking. The Live Updates mode now refreshes the special page every 60 seconds to comply with the updated global API rate limits for improved real-time responsiveness. Additionally, a directionality bug that displayed links as "changes 3" instead of "3 changes" in mixed-direction lists has been fixed. [21][22][23]

Updates for technical contributors

• The second phase of global API rate limits has been rolled out to reduce the impact of AI crawlers and ensure fair, sustainable access to Wikimedia resources, prioritising human and mission-aligned traffic. Limits have been shifted from per-hour to per-minute, producing smoother traffic patterns and more predictable API load. Community users are not expected to be affected, and no action is required. Early indications show some User-Agent-based requestors are adjusting behaviour, and around 64% of automated API traffic has been identified. Monitoring continues, and Wikimedia Enterprise remains available for commercial support.
• 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 20:43, 4 May 2026 (UTC)

Tech News: 2026-20

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

• Community Tech has published new guidance explaining how wishes on Community Wishlist are triaged and prioritized. The documentation is intended to help contributors write stronger proposals by clarifying the factors that influence prioritization decisions. Beyond vote counts, the guidance highlights considerations such as potential impact on the community when determining which wishes move forward.

Updates for editors

• The Reader Growth team is launching an experiment to test a new Share Card feature that allows readers to create visually engaging cards from Wikipedia articles or selected article sections and share them online, with each card linking back to the original article to help expand readership and article discovery. The mobile-only A/B test will be available to a portion of readers on Arabic, Chinese, French, Vietnamese, and English Wikipedia to better understand reading and sharing habits, and is scheduled to begin the week of May 18 and run for four weeks.
• The Android and iOS Wikipedia apps recently released the 25-day reading challenge into Beta, as part of efforts to drive reader engagement by encouraging users to complete reading milestones. To track their reading streak during the challenge, App users can add a widget featuring Baby Globe to their home screen. The challenge officially begins May 11.
• View all 17 community-submitted tasks that were resolved last week. For example, an issue where the global preference for enabling syntax highlighting in wikitext could unexpectedly disable itself after being turned on, has now been fixed. [24]

Updates for technical contributors

• The ResourceLoader module mediawiki.ui.input, deprecated since September 2023, will be removed this week. There is a guide for migrating from MediaWiki UI to Codex for any tools that use it. [25]
• 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 19:20, 11 May 2026 (UTC)

Tech News: 2026-21

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 Abstract Wikipedia team has identified five potential pilot wikis to assess their interest in adopting abstract articles on their wikis. The pilots are Malayalam, Bengali, Dagbani, Arabic, and Indonesian Wikipedia. The feedback period will be open until May 22. If your community is interested in becoming a pilot, let us know on Meta.

Updates for editors

• An experiment to show Reading Lists to logged-out readers on mobile web will launch on May 18 across German, Spanish, Italian, Portuguese, Polish, Dutch, Turkish, and Urdu Wikipedias, and will run for one month. The effort supports broader goals of helping readers save and organize articles for later reading, while encouraging habits that could lead to future Wikipedia contributions.
• To support a bookmark button in the Reading List beta feature, the "Tools > Action" menu has been updated to display icons, including the watch star indicator that helps editors identify temporarily watched articles. The icons now also match those used on mobile, improving consistency across platforms. The change is currently limited to the actions menu and mainly affects editors with privileged user rights. [26]
• Suggestion Mode was released as an A/B test for newcomer editors on the mobile website at ~15 Wikipedias. The experiment will measure the impact that Suggestion Mode has on the proportion of newcomer mobile web edit sessions that result in constructive (un-reverted) article edits. The experiment will also evaluate the feature's impact on editor retention, and monitor changes in revert and block rates.
• View all 27 community-submitted tasks that were resolved last week. For example, an issue in the Wikipedia Android app where images could sometimes fail to load after opening a recommended reading list notification, has now been fixed. [27]

Updates for technical contributors

• The Wikidata Platform team has published its backend replacement recommendation and accompanying technical architecture for the migration of the Wikidata Query Service (WDQS) away from Blazegraph. Feedback is invited until May 25th 2026, especially on potential gaps and impacts on advanced use cases. Wikidata community members and WDQS users are also encouraged to help identify high-impact tools and workflows that may need attention on this page. Feedback can be shared on the Migration talk page or during the next office hour. See the WDP team newsletter for more details.
• Detailed code updates later this week: MediaWiki

In depth

• On English, French, Japanese, and a few other Wikipedias, there was a trial of hCaptcha, a third-party bot detection service. The trial showed that hCaptcha effectively detects and deters some bad-faith automated activity, on its own and by giving checkusers and stewards signals to look into. Because the results were positive, hCaptcha will be rolled out across all wikis over the next few weeks. See the hCaptcha project page for technical information about the implementation and privacy protections. Learn more.
• The latest Community Tech update is now available, with progress across several Community Wishlist initiatives, including Reading Lists expansion from the mobile app to the website, new language support for "Who Wrote That" and the Personal Dashboard, improvements to 3D rendering and Charts, and upcoming work on talk page sorting, audio playback, and editing workflows. The update also shares current priorities, wishlist status trends, and opportunities for community feedback on future focus areas and the Wikimedia Foundation’s 2026–2027 Annual Plan. Read the full newsletter for details.

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

MediaWiki message delivery 20:21, 18 May 2026 (UTC)

May 2026 Wikimedia Café meetups regarding the Wikimedia Foundation Annual Plan

Hello! There will be two Wikimedia Café discussion opportunities during the last weekend of May. Both sessions will focus on the the 2026-2027 Wikimedia Foundation Annual Plan. Participants may attend either or both sessions.

1. Saturday, 30 May 2026 at 15:00 UTC (timestamp converter), at a time friendly to the Americas, Africa, and Europe
2. Sunday, 31 May 2026 at 05:00 UTC (timestamp converter), at a time friendly to Asia and the Pacific

Café participants are highly encouraged to read in advance at least this summary of the plan. Optionally, Café participants are encouraged to read portions of the plan that interest them and ask questions or provide feedback on the Annual Plan talk page.

Please see the Café page for more information, including tables of timestamp conversions for both sessions, the agenda, and how to register!

Pine (talk) 19:53, 21 May 2026 (UTC)

Tech News: 2026-22

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

• Following a successful account creation experiment, an improved logged-out edit warning message will be deployed to all Wikimedia wikis in the first week of June. The change will only affect logged-out users on mobile web who open an editing session. The updated experience is designed to encourage account creation more clearly, while still allowing users to edit with temporary accounts. Results from the experiment showed a significant increase in account creation, with a 27% relative lift among users shown the updated message. As expected, as more people funnel into account creation, temporary accounts decreased by a relative 16%. The experiment did not show any significant changes in constructive edit rates or other monitored contributor metrics. [28]

Updates for editors

• For security reasons, members of certain user groups are required to have two-factor authentication (2FA) enabled. Members of these groups will be unable to disable the last 2FA method on their account, and it will be impossible to add users without 2FA to these groups. Users will still be able to add new authentication methods or remove them, as long as at least one method is continuously enabled. In the next few weeks, users without 2FA will be removed from these groups. Notably, this applies to bureaucrats. See the linked tasks for deployment schedules. [29][30]
• WMDE Technical Wishes will run an A/B test on 10 wikis, testing potential improvements for Reference Previews. The experiment will run for ~2 weeks at the end of May / beginning of June and will affect 10% of desktop readers on the participating wikis.
• After two successful experiments, the Reader Growth team is rolling out an Image Browsing beta feature for all Wikipedias on mobile on May 25. This means that anyone who has all beta features on by default will start to see this feature, and others can check the box to turn it on in their preferences. The beta feature will include a carousel of all an article's images at the top of the article, with controls for editors to exclude images from the article's carousel or to exclude an article from the feature entirely.
• View all 30 community-submitted tasks that were resolved last week. For example, three dimensional STL files were being rendered incorrectly by the media viewer 3D extension which is now fixed. [31]

Updates for technical contributors

• The legacy CSS classes tleft and tright have been replaced with floatleft and floatright as the former do not work consistently across all MediaWiki platforms, notably mobile web and mobile apps. Projects relying on these classes are encouraged to review related usage and plan for migration. Please note that floatleft and floatright may also be deprecated in future, although there are currently no plans to do so. Read 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 21:52, 25 May 2026 (UTC)

Vote now in the 2026 U4C election

Eligible voters are asked to participate in the 2026 Universal Code of Conduct Coordinating Committee election. More information–including an eligibility check, voting process information, candidate information, and a link to the vote–are available on Meta at the 2026 Election information page. The vote closes on 2 June 2026 at 00:00 UTC.

Please vote if your account is eligible. Results will be available by 14 June 2026. -- In cooperation with the U4C,

Keegan (WMF) (talk) 17:15, 27 May 2026 (UTC)

Tech News: 2026-23

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 is conducting an experiment to show the reading lists feature, which is still in development, to logged-out mobile readers to test whether it encourages account creation at a higher rate compared to the watchstar button. The experiment was launched on May 18th on German, Spanish, Italian, Portuguese, Polish, Dutch, Turkish, and Urdu wikis, and it will run for a month.
• The Wikimedia Apps team released Phase 1 of the redesigned Home Feed to the Android Beta app. The new Home Feed includes a refreshed "Community" tab and a personalized "For You" tab featuring daily updated reading recommendations. The redesign is part of a broader effort to improve content discovery and create more engaging learning experiences in the Wikipedia apps.
• View all 18 community-submitted tasks that were resolved last week. For example, an issue where images could fail to load for some suggested edits on Special:Homepage, leaving the thumbnail stuck in a loading state, has now been fixed. [32]

Updates for technical contributors

• 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 21:08, 1 June 2026 (UTC)

Unable to publish because of hCaptcha failure + IP block (new user)

Hello, I am a new user and I am completely unable to publish any edits on Wikisource. I am facing two compounding issues:

hCaptcha does not load on my network. The publish button stays permanently greyed out with an endless loading spinner. I have tried multiple browsers (Firefox, Chrome, Edge), multiple networks including mobile data, and DNS changes to 8.8.8.8 and 1.1.1.1. The browser console shows:

Content-Security-Policy: The page’s settings blocked the loading of a resource (frame-ancestors) at because it violates the following directive: “frame-ancestors 'self' https://*.wikipedia.org https://*.wikimedia.org https://*.wikibooks.org https://*.wikinews.org https://*.wikiquote.org https://*.wikisource.org https://*.wikiversity.org https://*.wikivoyage.org https://*.wikidata.org https://*.wikimediafoundation.org https://*.wikiworkshop.org https://*.wikifunctions.org https://*.wiktionary.org https://*.mediawiki.org https://*.wmfusercontent.org https://*.w.wiki”

When I use Cloudflare WARP to bypass the hCaptcha issue, my IP is blocked.

I am stuck between both issues and cannot publish anything at all. I am a student trying to complete a task assigned by my instructor.

Thank you. Vivian Alexander L Nonglait (talk) 13:06, 8 June 2026 (UTC)

This has been fixed in https://phabricator.wikimedia.org/T428539. 内存溢出的猫 (talk) 22:52, 3 July 2026 (UTC)

Thank you for the update. Vivian Alexander L Nonglait (talk) 05:34, 5 July 2026 (UTC)

Tech News: 2026-24

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

• Wikimedia Enterprise has increased the free usage limits for its API offerings. The monthly request limit for the On-demand API has increased from 5,000 to 50,000 requests, while the Snapshot API limit has increased from 15 to 30 requests per month. In addition, Structured Contents snapshots are now available for free accounts. These changes expand access to Wikimedia Enterprise data for developers, researchers, and organizations using Wikimedia content. [33]

Updates for editors

• The refreshed Explore Feed, now called the Home Feed, is rolling out to 50% of users of the Wikipedia Android app. The Home Feed helps readers discover relevant content through two new tabs: Community and For You. The Community tab provides a scrollable feed of curated content and updates from the broader Wikimedia community and movement, while the For You tab offers a full-screen, swipeable experience that shows content tailored to a user's interests. The redesign is part of a broader effort to improve discovery and enhance the learning experience in the Wikipedia app.
• The Which came first? daily trivia game is now available in the beta version of the Wikipedia iOS app in English, German, French, Portuguese, Russian, Spanish, Arabic, Chinese, and Turkish. The game uses historical events from Wikipedia's "On This Day" content and challenges readers to guess which of two events happened first. The game was previously released on Android. Communities interested in making the game available in their languages can read the instructions and requirements.
• Sub-referencing, a new MediaWiki feature that allows editors to reuse references with different details, will begin rolling out to Wikimedia wikis following a successful pilot phase. Deployment will start on 8 June for most Group 1 wikis and French Wikipedia, with additional Wikipedia language editions receiving the feature over the coming months. Communities are encouraged to prepare by checking for untranslated Cite extension messages in their language and reviewing any use of Reference Tooltips, which may require updates to support the new functionality. Wikis using Reference Previews do not need to take any action. Communities may also wish to create the cite-tracking-category-ref-details tracking category as a hidden category using __HIDDENCAT__ (or a dedicated template), and connect it to the corresponding Wikidata item d:Q129764848. [34]
• The Page Previews experiment on mobile web has concluded. The team decided not to roll out the feature after the results showed no statistically significant impact on reader retention, as the primary success metric was retention improvement. Page Previews, which are already available on desktop and in the apps, display a thumbnail, lead paragraph, and link to the full article when readers tap a blue link. The experiment tested this experience on mobile web across six Wikipedias.
• The user interface icon library will be updated later this week or next week. Most of the ~300 icons have been slightly refined and ~30 new icons have been added. These changes improve the icons to make them more consistent and comprehensible, and provide more visual balance when they are used in groups.
• The Universal Language Selector (ULS) interface in MediaWiki, which helps users select content in other languages, has been updated. The new version improves speed and accessibility, and users of Wikimedia projects can now pin languages for quicker language switching. The deployment to Wikimedia sites will happen gradually in the coming weeks. You can test it now as a beta feature by selecting beta features in your profile preferences and share your feedback on the project page.
• View all 21 community-submitted tasks that were resolved last week. For example, an issue where the Pageviews Analysis dashboard on pageviews.wmcloud.org stopped updating graph data in May 2026, affecting all users, has been fixed. [35]

Updates for technical contributors

• The function signature for mw.util.addPortletLink() has been simplified. Developers can now pass a configuration object instead of a list of positional parameters when creating portlet links. The previous function signature remains supported for backwards compatibility. For example, instead of: mw.util.addPortletLink('p-cactions', '#', 'Stub', 'ca-stubtag', 'Add a stub tag to this page'); use mw.util.addPortletLink('p-cactions', { href: '#', text: 'Stub', id: 'ca-stubtag', tooltip: 'Add a stub tag to this page' });. Script maintainers are encouraged to review existing uses of addPortletLink() and update them where appropriate. This change will be available on all wikis from 11 June. Thanks to community volunteer Gerges for contributing this improvement. [36]
• Community Wishlist discussion: Product & Technology introduced changes meant to increase the number and complexity of wishes fulfilled, including the disbanding of the Community Tech team. They are engaging in discussions about a proposed direction for the wishlist from community members. Includes ways to structure annual voting, better tracking of wishes, removing focus areas, and staffing updates.
• 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 21:30, 8 June 2026 (UTC)

External book links?

Totally new here and trying to find ways to help! How do I add an external link to a book on an author page? I’ve seen it done a few different ways and I want to check if there’s a preferred way to do it. Thanks so much for any tips! (I can use all the help I can get lol!) Stampdragon (talk) 18:12, 10 June 2026 (UTC)

You do it in the form of [https://example.example/ Text to read], which results in Text to read. You can read more at mw:Help:Links. ―Justin (koavf)❤T☮C☺M☯ 15:02, 14 June 2026 (UTC)

June 2026 Wikimedia Café meetups regarding the English Wikipedia Editor Reflections project

Hello! There will be two Wikimedia Café discussion opportunities during the last weekend of June. Both sessions will focus on the English Wikipedia Editor Reflections project. The featured guest in the Café will be User:Clovermoss. Participants may attend either or both sessions.

1. 27 June 2026 15:00 UTC (timestamp converter), at a time friendly to the Americas, Africa, and Europe
2. 28 June 2026 03:00 UTC (timestamp converter), at a time friendly to Asia and the Pacific

Please see the Café page for more information, including how to register!

Pine (talk) 03:57, 15 June 2026 (UTC)

Tech News: 2026-25

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 Reader Growth team has launched an Image Browsing beta feature on the mobile web version of all Wikipedias. The feature shows an image carousel at the top of articles with 3 or more images. Editors can configure this feature with the following controls: to hide a specific image from a page, either use class=notpageimage excluding it from thumbnail previews, or class=noviewer excluding it from MediaViewer. The carousel can also be disabled from a page entirely, with the magic word __NOMEDIAVIEWERCAROUSEL__. To submit feedback or flag bugs, please visit the project page.
• Wikitables can now be sorted in descending order on the first click by adding data-sort-order="desc" to the header cell. Previously, by default, clicking a column header for the first time sorts it in ascending order. This addition to a Wikitable gives it more control and flexibility, while the default behavior for subsequent clicks remains unchanged. [37]

Updates for editors

• The Article guidance feature is currently being tested with some editors creating new articles on the Simple English, French, and Turkish Wikipedias. The experiment will soon begin on the Arabic and Bangla Wikipedias as well. This feature gives editors community-curated guidance to help them create articles that follow community standards. Experienced editors can continue creating or adapting outlines for specific article types that are commonly created by less experienced contributors. The outlines guide less experienced editors in creating high-quality articles. A quick guide to markups used in outlines can be found on this page. Example outlines that can be adapted and instructions for how to adapt them are on this section of the project page.
• Wikis that wish to replace the "indefinitely" button in Special:Block for temporary accounts (for example, wikis that block temporary users only until account expiration) will be able to do so by creating MediaWiki:ipb-indefinite-expiry-temporary-account with the block duration they want. [38]
• View all 41 community-submitted tasks that were resolved last week.

Updates for technical contributors

• By the end of June, a valid user-agent string will be required for automated dumps downloads from the dumps.wikimedia.org website. Automated requests that provide a generic or empty user-agent will be blocked. This extends enforcement of the long standing user-agent policy. Access to dumps through Wikimedia Cloud Services will not change.
• The roll out of global API rate limits is now complete, with limits enforced across all APIs and at the documented levels for all groups. Bots running in Toolforge/WMCS or with the bot user right on any wiki remain exempt. All bots should continue to follow the documented best practices to avoid being rate limited.
• The API Portal wiki will be read only starting this week (June 15-18). The following week (June 22-25), all API Portal wiki URLs will redirect to Wikimedia APIs on mediawiki.org. Learn more on the project page.
• Detailed code updates later this week: MediaWiki

Meetings and events

• On June 17th at 6pm UTC the WMF will be holding Discord call focused on a code review. We've heard through the Developer Satisfaction Survey that volunteers are struggling with code review and we'd like to discuss these experiences with the goal of surfacing workable solutions. You can join the call via the Wikimedia Community Discord server.
• The Latin American Wikimedia Conference will host a regional hackathon that will bring together the Wikimedia movement’s technical community including developers, system administrators, data scientists, and users with extended rights. Interested technical contributors can apply for a scholarship to participate until June 21 at midnight (Bolivia time, UTC-4).
• Sign up for Wikimania Team Challenges to join this special event. The Team challenges will take place online and in person from July 21 to 22, before Wikimania conference. Everyone is welcome, regardless of skills or Wikimania registration. Teams will work on 10 important challenges supporting the Wikimedia community. For details, visit the Team Challenges page and register there. Registration closes on June 20th at 11pm UTC.

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

MediaWiki message delivery 16:48, 15 June 2026 (UTC)

Tech News: 2026-26

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

• Growth features are now available at Wikidata. This update enables access to Mentorship (if configured), Impact module, the Help Panel, and a simplified Newcomer Homepage (without Suggested Edits). Wikidata administrators are still configuring the features through Community Configuration.

Updates for editors

• The special page Special:RangeCalculator has been created. It allows users to find an IP range without needing to rely on external tools. Until now, this tool was only available to CheckUsers. [39]
• Sub-referencing is a new MediaWiki feature that allows editors to reuse references with different details. It will be deployed to most small and medium-sized Wikipedia language versions on June 23. The FAQ lists possible actions to take on your wiki to support the deployment. Check the rollout plan for the next deployment steps. [40]
• Starting next week, users will get a notification when they are blocked or unblocked from editing, or if this block changes. [41]
• View all 32 community-submitted tasks that were resolved last week.

Updates for technical contributors

• Starting next week, abuse filters that are set to "require CAPTCHA verification" will begin to also affect users with the skipcaptcha right, which includes most autoconfirmed users. Bots are exempted. This change only affects edits that trigger an abuse filter. The skipcaptcha right will continue to exempt users from having to solve CAPTCHAs in the ordinary course of using the wikis. [42]
• Reference documentation for the Lift Wing API has moved from the API Portal to the interactive REST Sandbox.
• The API Portal wiki is now closed. For API documentation, see Wikimedia APIs on mediawiki.org. All API Portal wiki URLs (https://api.wikimedia.org/wiki/) will redirect to the mediawiki.org page starting June 22. [43]
• Detailed code updates later this week: MediaWiki

Meetings and events

• Join an online call on 25 June at 2:30pm UTC to meet the current Wikimedia interns for Google Summer of Code and Outreachy. Interns will provide an overview of their projects and a brief demo of their work so far. Attendees are encouraged to share ideas and connections in their community.

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

MediaWiki message delivery 13:05, 23 June 2026 (UTC)

RFC about AI-generated content in Wikimedia Commons

You are invited to participate in a request for comment on Wikimedia Commons about a policy update for AI content. This may affect files that are uploaded to Wikimedia Commons for use on this project. Thank you. Codename Noreste (talk) 17:12, 23 June 2026 (UTC)

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

Legal & Safety Contacts

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 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.

-- User:Sannita (WMF) (talk) 13:30, 25 June 2026 (UTC)

Tech News: 2026-27

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

• As part of the Account Creation Experiments, the Growth team tested adding a user account icon in the mobile web header for logged-out users, providing direct access to "Create account" and "Log in" actions. The experiment increased account creation by about 20% without negatively affecting edit quality or constructive edit rates. The feature will now be rolled out to all Wikimedia Foundation wikis on mobile web in the first week of July. [44]
• After a successful experiment, logged-in users who did not confirm their email address when their account was created see a new banner asking them to complete that process. This helps reduce the risk that users get locked out of their account, and makes account email addresses overall more reliable. This is part of the Account Security project. [45]
• An update to Search is refining how the -prefix: behaves when used to exclude results. Previously, using -prefix: with negation could unintentionally broaden search results by adding the namespaces included in the search scope, leading to confusing behavior for users expecting a straightforward exclusion filter. With the update, -prefix: will now strictly exclude matching page titles as intended and may display a warning if the relevant namespace has not been explicitly selected. The behavior of prefix: without negation however remains unchanged. [46]
• View all 33 community-submitted tasks that were resolved last week. For example, an issue where reviewers using the Page Curation toolbar were not automatically subscribed to talk page discussions they started has now been fixed. Reviewers will now receive notifications when someone replies to those discussions. [47]

Updates for technical contributors

• Starting June 29th, automated downloads from the dumps.wikimedia.org website will be subject to the user-agent policy. Automated requests that provide a generic or empty user-agent will be blocked. Access to dumps through Wikimedia Cloud Services remains unaffected. This is a follow up to the announcement made in the 2026/25 issue of Tech News.
• 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 11:48, 29 June 2026 (UTC)

Can't write a page!

I think the automatic moderation doesn't like me in particular. I was writing a page at Wikichanzo:Commedia ya Kimungu/Jahannamu/Surah I but I can't do anything. If I click publish I get "This action has been automatically identified as harmful, and therefore disallowed. If you believe your action was constructive, please inform an administrator of what you were trying to do. A brief description of the abuse rule which your action matched is: Antispam". Please, can anybody help me? Dixy52 (talk) 00:05, 3 July 2026 (UTC)

@Dixy52: see my comment below, I changed a bit the filter, it should fix your problem. Cheers, VIGNERON (talk) 21:38, 4 July 2026 (UTC)

This action has been automatically identified as harmful, and therefore disallowed

When creating page FAENH GANGJMINGZ GVENDAENGZ 《AEN GIETDINGH CUNGHGUNG CUNGHYANGH GVENDAENGZ CAIQ CIENZMIENH GYALAEG GAIJGWZ、 DOIHAEUJ GIJ YENDAIVA YIENGH CUNGGUEK》:

This action has been automatically identified as harmful, and therefore disallowed. If you believe your action was constructive, please inform an administrator of what you were trying to do. A brief description of the abuse rule which your action matched is: Antispam

Under Article 5 of the Copyright Law of the People's Republic of China, laws, regulations, resolutions, decisions, judicial decisions, and official translations are excluded from copyright and are instantly in the public domain. The content is an official Zhuang language (Vahcuengh) translation of the original (available on Chinese Wikisource).

@-jkb- @Ankry @Catonif @Draco flavus @Jon Harald Søby @Koavf @Mahagaja @Ooswesthoesbes @Satdeep Gill @Ternera @TunnelESON @VIGNERON @ꠢꠣꠍꠘ ꠞꠣꠎꠣ:

There are several reports above regarding that new pages can't be created, but it seems they haven't received any attention. The previous hCaptcha bug was only resolved after I submitted a Phabricator ticket myself. Don't know why editing a page is so difficult. I'm hoping I've reached the right people for this; thank you for your time. 内存溢出的猫 (talk) 20:31, 4 July 2026 (UTC)

Thanks for letting us now. You (and other people) triggered the antispam filter (Special:AbuseFilter/6, nothing to see with copyright it's just a list of banned words so probably just a w:Scunthorpe problem) but I’m not 100% sure what triggered it. I change what I think was the cause of the problem, could you try again and tell me if it works now? Cheers, VIGNERON (talk) 21:34, 4 July 2026 (UTC)

PS: on Wikisource you are not supposed to put text in the main namespace, hence why the filter is a bit aggressive.

ISO 639-1 codes the Zhuang languages za. Please be sure that the text will be properly titled and licensed.--TunnelESON (talk) 22:31, 4 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. [48]

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:57, 6 July 2026 (UTC)

July 2026 Wikimedia Café meetups regarding Wikimedia governance and options for reform

Hello! There will be two Wikimedia Café discussion opportunities in July. Both sessions will focus on Wikimedia governance, including possible follow-ups to the Movement Charter and options for reform. Participants may attend either or both Café sessions.

This month, to deconflict the Café meetups from Wikimania, the meetups will be held one day later than usual.

1. 26 July 2026 15:00 UTC (timestamp converter), at a time friendly to the Americas, Africa, and Europe
2. 27 July 2026 03:00 UTC (timestamp converter), at a time friendly to Asia and the Pacific

Please see the Café page for more information, including how to register!

↠Pine (✉) 03:39, 13 July 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. [49]

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. [50]
• 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. [51]
• 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:11, 13 July 2026 (UTC)

Hello

How can languages graduate from Multilingual Wikisource? ङघिञ (talk) 12:41, 17 July 2026 (UTC)

Great question. You can see the process at our sister site Meta: m:LangCom. ―Justin (koavf)❤T☮C☺M☯ 21:11, 19 July 2026 (UTC)

Request for bot flag

Hi. I'd like to request a bot flag for my bot, which would fix Linter errors on this wiki. Tenshi Hinanawi (talk) 17:44, 17 July 2026 (UTC)

I'd be happy to grant it and I see that it works on other wikis. How about I temporarily grant it for a week and we see how it looks just to be on the safe side and then you can ping me afterward to see if we can extend it? ―Justin (koavf)❤T☮C☺M☯ 21:12, 19 July 2026 (UTC)

Sure, let me know when you have flagged it temporarily. Tenshi Hinanawi (talk) 22:02, 19 July 2026 (UTC)

Done ―Justin (koavf)❤T☮C☺M☯ 00:00, 20 July 2026 (UTC)

@Koavf: It's been a week, what do you think? Tenshi Hinanawi (talk) 18:30, 26 July 2026 (UTC)

Sounds good to me per Wikisource:Bots. ―Justin (koavf)❤T☮C☺M☯ 18:40, 26 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:46, 21 July 2026 (UTC)

Request for comment (the future of Abstract Wikipedia)

You are invited to voice your opinions in a request for comment about the future of Abstract Wikipedia. Thank you! Kowal2701 (talk) 12:25, 24 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. [52]
• 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. [53]
• 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. [54]

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. [55]
• 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. [56]
• 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:49, 27 July 2026 (UTC)

Migration to Parsoid

Read this in another language

Hello everyone! I am glad to inform you that as the next step in the Parser Unification project, Parsoid will soon be turned on as the default article renderer on your wiki. We are gradually increasing the number of wikis using Parsoid, with the intention of making it the default wikitext parser for MediaWiki's next long-term support release. This will make our wikis more reliable and consistent for editors, readers, and tools to use, as well as making the development of future wikitext features easier.

If this disrupts your workflow, don’t worry! You can still opt out through a user preference or turn Parsoid off on the current page using the Tools submenu, as described in the Extension:ParserMigration documentation.

There is more information about our roll-out strategy available, including the testing done before we turn on Parsoid for a new wiki.

To report bugs and issues, please look at our known issues documentation and if you found a new bug please create a phab ticket and tag the Content Transform Team in Phabricator.

Content Transform Team 16:31, 3 August 2026 (UTC)

Tech News: 2026-32

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 developed a patch demo that wraps the page toolbar onto two lines when there is not enough horizontal space for all the buttons. This aims to reduce crowding in the Vector 2022 toolbar, which can occur on some language Wikipedias at certain screen widths. [57]
• The Reader Experience team is planning to launch Reading Lists, a Community Wishlist item, which is currently available to try in beta, as a full feature in September. Before then, volunteer translator help is needed for string translations into a number of languages. The feature supports reading and learning goals on Wikipedia.
• Next week, the table of contents on Wikimedia Commons file pages will be improved by consolidating the file page table of contents with the page table of contents. This will make it easier to understand a file page’s structure, navigate to specific sections, and share links to individual sections. [58]
• View all 24 community-submitted tasks that were resolved last week. For example, an issue where some TIFF images failed to load after clicking their thumbnail, causing a broken image to be displayed instead of the full-size image, has now been fixed. [59]

Updates for technical contributors

• The variable and function selector in AbuseFilter has been updated to support search and autocomplete. It will allow filter maintainers to find the desired variable or function more quickly. [60]
• The MJPEG and VP8 formats are removed from the video player. The MP4 format (MPEG-4 Part 2) is added instead, which provides higher quality videos to older iPhone devices. It may take a few weeks to retroactively update all existing videos. The default format for modern devices stays the same (VP9/WebM). [61]
• 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 19:46, 3 August 2026 (UTC)

Tech News: 2026-33

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

• A new ChartWizard is now available on Wikimedia Commons for users interested in creating charts from their own data. The wizard makes the Chart extension more beginner-friendly by allowing editors to create charts, such as bar and pie charts, without needing to use JSON. Users can still switch to the JSON editor if they prefer. Feedback on the new tool is welcome on the wish talk page.
• View all 19 community-submitted tasks that were resolved last week. For example, an issue where the Wikipedia iOS app’s Picture of the Day widget displayed the same image every day instead of updating daily, has now been fixed. [62]

Updates for technical contributors

• Math formula SVG images will soon be generated in the browser instead of on the server. MathML continues to be generated on the server and renders in the browser without JavaScript. Wikibooks will see this change on 12 August, Wikisource on 19 August and Wikipedia from 20-27 August. You can try this by selecting "MathML with SVG image (client side MathJax rendering)" in your preferences. This change is part of deprecating RESTBase and deprecating Mathoid. [63]
• Category pages will soon support sorting entries by the time they are added to a category. This will make it easier to find recently or long-standing categorized pages. It will also improve workflows for maintenance categories such as deletion backlogs and other time-based review tasks. You can use cldsort=timestamp URL argument in category view to sort the entries. [64]
• Gadgets and user scripts on Wikimedia wikis may now use ES2018 features and ES2019 features in JavaScript code. Previously, the platform only allowed up to ES2017. MediaWiki validates the source code to protect functionality from syntax errors and to ensure scripts are valid in all supported browsers. [65]
• 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 20:45, 10 August 2026 (UTC)

Tech News: 2026-34

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 Worklist feature for the Event Registration tool is now live on all Wikimedia wikis. With Worklist, event organizers can add the articles their event will focus on directly to the event page. The Worklist also powers Event Pathways which notifies other editors of the upcoming or ongoing event when they edit an article featured in the event's Worklist. This is the minimum viable version (MVP), and feedback is welcome. Organizers are encouraged to try the feature. A hands-on Worklist Setup Workshop will take place on 18 August at 16:00 UTC and 19 August at 11:00 UTC.

Updates for editors

• Special:ShortPages displays short pages by their size, but in many cases it gets filled with disambiguations and soft redirects, making it harder to find the short articles themselves. Starting this weekend, you will be able to choose not to include an article in the special page by adding the magic word __EXPECTSHORTPAGE__. [66]
• One new wiki has been created: a Wikipedia in Bole (w:bol:) [67]
• Starting the week of August 17, the page toolbar will wrap onto two lines when there is not enough horizontal space for all the buttons. This is a fully merged patch from the Reader Experience team which aims to reduce crowding in the Vector 2022 toolbar, that may occur on some language Wikipedias at certain screen widths.
• View all 16 community-submitted tasks that were resolved last week. For example, uploading large files to Wikimedia Commons has become more stable and less prone to failure following some fixes related to the “Could not acquire lock” upload error. [68]

Updates for technical contributors

• Debian Bullseye will reach the end of its Long Term Support on 31 August 2026. Some Cloud VPS projects still have instances running Debian Bullseye. Maintainers of those projects are encouraged to migrate to Debian Bookworm or Debian Trixie. A migration guide is available to help with the process, and users may also want to consider whether their workload is better suited to Toolforge. If you need help or cannot complete the migration by 31 August, please contact the Cloud VPS admins as soon as possible. Read 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 21:03, 17 August 2026 (UTC)

Tech News: 2026-35

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 Special:CreateAccount page has been simplified as part of ongoing work to modernize the account creation experience. The panel showing project statistics no longer appears next to the form on desktop and mobile web. Multiple account creation experiments show that a simpler form helps newcomers complete registration. [69]
• In order to improve page performance, images now load when they are viewed. This means images lower down an article will not load if a reader never scrolls to that part of the page, which may affect some image-related metrics. [70]

• View all 42 community-submitted tasks that were resolved last week. For example, an issue where image thumbnails in Abstract Wikipedia could fail to display after the corresponding file was moved on Wikimedia Commons, has now been fixed. Thumbnails will now update correctly when files are moved. [71]

Updates for technical contributors

• User Info card is a feature that helps patrollers see information about user accounts. So far, it has been available only in places such as page history, logs and recent changes. Now, it's possible to place it in the page content as well, using the {{#uic:}} parser function. It can be particularly useful in templates like {{Userlinks}} (or their specialized variants), as it will make it easier to see the context about a user on various noticeboard pages. The card will be displayed only to users who have it enabled in their preferences. [72]
• Due to user security and privacy risks, we have disabled access to Special:MyPage URLs when specifically using action=raw. If you are impacted by this, consider whether you can use an alternative approach. Special:MyPage URLs can still be accessed and used without action=raw. Specified user page URLs (e.g. User:Myusername) can still be used with action=raw. [73]
• Due to an update, the thumbnailing software has been improved. This includes upgrading librsvg to 2.60 and ImageMagick to 7, as well as resolving a number of long-standing thumbnailing bugs like rendering errors. [74]

• 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 20:45, 24 August 2026 (UTC)

Tech News: 2026-36

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

• A new format for the Community Wishlist is open for feedback. You can read the proposed ideas on Meta. This new process plans to improve how wishes are triaged, voted on, and prioritized in a way that is transparent and balanced across project families and language editions. This consultation is open for two weeks.

Updates for editors

• The latest release of the Wikipedia Android app includes updates to the Saved feature, bringing the app’s saving experience closer to iOS and Web. The update redesigns the Saved tab with an “All articles” view, removes the default “Saved” reading list, renames reading lists to “Collections,” and modernizes the article-saving experience. [75]
• The Reading Lists feature was enabled for all logged-in users on Bengali, Chinese, Czech and Vietnamese Wikipedias on August 25, after several months as a beta feature. Reading Lists will be available to all logged-in users on Arabic, French and Indonesian Wikipedias on September 1, followed by English Wikipedia on September 14, and all other Wikipedia wikis on September 28.
• At the end of the month, some logged-out readers on Bengali, Czech, Persian, English, and Polish Wikipedias using the Minerva skin on mobile will see an updated navigation bar in an A/B test. The test will compare the current navigation bar with a new version designed to make it easier to find information more quickly. The goal is to determine whether these changes encourage readers to return more often. This experiment will not change the experience for logged-in readers and/or editors.
• Editors who maintain redirects, templates, and categories used on redirect pages now have improved ways for finding and curating redirects. Previously, redirects pages could not be searched. Two new search keywords, onlyredirects: and withredirects:, now allow redirects to be searched directly and can be combined with existing keywords such as incategory:, intitle:, and insource:. [76]
• The ISBN lookup tools for generating citations were recently not working because of external service problems. Developers are working on solutions. [77]
• View all 30 community-submitted tasks that were resolved last week. For example, an issue where searching for pages by category using deepcat could return no results or unrelated results has now been fixed. [78]

Updates for technical contributors

• The domain of URLs for thumbnails is changing from upload.wikimedia.org to thumb.wikimedia.org. The old URLs will continue to work for the foreseeable future but MediaWiki will advertise the new domain instead. URLs to other types of media such as original files, videos and transcodes will still be served from upload.wikimedia.org. [79]
• The Wikimedia Math API is now deprecated. These endpoints will be fully sunset by the end of September 2026. Developers who call these endpoints should transition to alternative math rendering solutions, such as the native MathML or MathJax. Third-party MediaWiki installations that utilize the Math extension for formula rendering are required to upgrade to v1.43+ to avoid disruption of service.

• Detailed code updates later this week: MediaWiki

In depth

• Read more about TextMatch in a Diff post titled, Custom edit suggestions for every wiki: How communities are shaping Suggestion Mode with TextMatch.

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

MediaWiki message delivery 20:53, 31 August 2026 (UTC)

Wishlist 2027, invitation to share feedback

Hi, I’m Sonja and I lead some of the teams at the Foundation who will be responsible for picking up wish work under the new wishlist process.

As you may know, the Community Wishlist started out as an annual process through which Wikimedia contributors submit and vote on technical improvements they would like the Wikimedia Foundation to work on. The main goal of it is and has been to improve the editing experience by making changes and features the community asks for specifically.

In recent years, the process behind the wishlist has changed, and we’ve heard from many of you that it no longer meets many community members’ needs. So now, the Foundation is designing a new process with the community to improve how wishes are triaged, voted on, and prioritized in a way that is transparent, balanced across project families and language editions, and takes into account what the Foundation can deliver.

I would like to get community input specifically on these three stages of the Wishlist process:

• The triage stage, meaning how wishes are fleshed out, organized and filtered prior to voting
  • We recommend to have a working group, including volunteers from various wikis and Wikimedia Foundation staff to work through this together
• The voting stage, including who may vote and how votes are structured
• The post-vote stage, including how to bring equity into what work is prioritized
  • One way to do this is to rank wishes within 3 categories: Large Wikipedias or covering all wikis, small and medium-sized Wikipedias, and sister projects, so that top-voted wishes from smaller projects also get attention

This message is an abstract of the full proposed process. As you read the proposed ideas on Meta (available in your language), please speak up about whether you think this will work well or if there are ways to make it stronger.

Regarding the timeline, this consultation is open for two weeks. You can post your feedback on Meta (in your preferred language) or in response below.

For this year’s cycle, we plan to have the wish submission period in late October/early November and the triage process completed by late November. To respect the end-of-year holiday season, voting would happen in early to mid January. This first voting cycle is meant as a first step to try out a new process, and there will be more opportunities to provide feedback along the way, so that we can figure out the best process for future years together.

SPerry-WMF, delivered by Trizek (WMF) (talk) 13:51, 1 September 2026 (UTC)

Thank you to everyone who engaged in the discussion around the proposal from August 26. We've processed your feedback and made changes accordingly. Note that we weren’t able to implement all of it for this cycle, mostly for logistical reasons, but this is merely meant to be a first step and we will continue to improve this process with you all before we run through the next cycle. We plan to use this updated version for the Wishlist 2027, and we look forward to hearing from you all during the submission and voting periods.

SPerry-WMF, delivered by Trizek (WMF) (talk) 14:50, 17 September 2026 (UTC)

Tech News: 2026-37

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

• Add a Link has been upgraded for English Wikipedia users with improved detection of links that have different capitalization. This will help reduce ambiguous suggestions caused by differences in capitalization in article titles, including articles about cultural goods. A second phase of improvements is planned, which will also prepare the feature for release in other languages. [80] [81]
• The Article guidance feature will be enabled by default for junior editors on Simple English and Turkish Wikipedia starting 10 September 2026 following an experiment. Junior editors with 0 to 99 edits will automatically see the feature when they click a red link or use the "Madde oluşturto" option on Turkish Wikipedia to create a new article. The change is intended to help junior editors create higher-quality articles that meet each Wikipedia’s standards. Additional improvements will continue based on the experiment results and community feedback.
• The Pageviews Analysis tool which allows users to compare pageviews across multiple pages, turns 10 years old this year and several new features have been added. They include WikiNav which provides insights into how readers of Wikipedia explore the content, editing stats in Siteviews, the ability to lookup articles belonging to a WikiProject, and support for dark mode. [82]
• A visually simplified Minerva navigation bar is being tested for logged-out readers using mobile web on the Bengali, Czech, English, Farsi, and Polish Wikipedias. The experiment aims to determine whether simplifying the navigation improves reader retention. The test will run from August 31 to September 28, and no action is required from users.
• WMDE Technical Wishes is working on improving auto-generated reference names in VisualEditor. Editors will only notice a slight change starting this week. When adding automatic reference names the numbering will start at :1 instead of :0. Read more on the project page. [83]
• All wikis will be read-only for a few minutes on September 23. This is planned at 14:00 UTC. More information will be published in Tech News and will also be posted on individual wikis in the coming weeks. [84]
• View all 25 community-submitted tasks that were resolved last week. For example, an issue where Parsoid could mishandle nested nowiki tags, causing content to be lost and displaying unwanted text has now been fixed. [85]

Updates for technical contributors

• Interface administrators can configure gadgets from MediaWiki:Gadgets-definition. The definition format has been updated and no longer requires the ResourceLoader option, as gadgets are always loaded through ResourceLoader. This simplifies gadget configuration by removing an option that is no longer necessary, making gadget definitions easier for administrators. [86]
• 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:44, 7 September 2026 (UTC)

Tech News: 2026-38

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 Future Audiences team has started a discussion on English Wikipedia about a proposed new experiment to show a temporary notice about the new Google Preferred Sources feature to Wikipedia readers coming from Google. The experiment is to test whether this notice makes visitors come back to Wikipedia more often. Preferred Sources feature lets users choose websites they trust so Google can highlight content from those sources more prominently in Search and AI experiences. We are interested in testing this on other languages that Google supports and would welcome assistance with starting conversations on other wikis. If interested, please reach out to Future Audiences on the talk page.

Updates for editors

• The chat platform Discord is releasing a new self-service framework that websites can use to specify how their links should look when shared on Discord. The Future Audiences team is planning to start using this new framework to improve how Wikipedia links look when shared on Discord, giving better attribution and credit to contributors. The link appearance and behavior won't change in the first phase of this project as we want to first collect some baseline data to assess the impact of future changes. However, if community members who are active on Discord spot any issues, they can reach out on Phabricator or Metawiki.
• The Reader Growth team will be running an experiment to test whether compacting article lead sections on mobiles with the addition of a "read more" button improves reader retention. The test will begin on September 17 on Arabic, Spanish, French, Indonesian, Italian, Japanese, Portuguese, Vietnamese, and Chinese Wikipedias and will run for four weeks.
• All wikis will be read-only for a few minutes on September 23. This is planned at 14:00 UTC. More information will be published in Tech News and will also be posted on individual wikis in the coming week. [87]
• View all 28 community-submitted tasks that were resolved last week. For example, an issue where Wikistats for Wikipedias was returning an HTTP 500 error and could not be reached, has now been fixed. [88]

Updates for technical contributors

• Developers who maintain a tool that queries the Wikimedia Commons links tables need to update their code to connect to the new x4 database cluster. The links tables have been moved from the s4 cluster to x4, and will no longer receive updates on s4. The page and redirect tables remain available on both clusters. A wiki replica for the x4 cluster will be set up afterwards. The change is being made because the s4 cluster has grown too large to operate efficiently. You can read 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 15:31, 14 September 2026 (UTC)

Server switch - Your wiki will be read-only for a short time soon

Read this message in another language • Please help translate to your language

The Wikimedia Foundation will switch the traffic between its data centers. This will make sure that Wikipedia and the other Wikimedia wikis can stay online even after a disaster.

All traffic will switch on 23 September. The switch will start at 14:00 UTC.

Unfortunately, because of some limitations in MediaWiki, all editing must stop while the switch is made. We apologize for this disruption, and we are working to minimize it in the future.

A banner will be displayed on all wikis 30 minutes before this operation happens. This banner will remain visible until the end of the operation. You can contribute to the translation or proofreading of this banner text.

You will be able to read, but not edit, all wikis for a short period of time.

• You will not be able to edit for up to an hour on Wednesday 23 September 2026.
• If you try to edit or save during these times, you will see an error message. We hope that no edits will be lost during these minutes, but we can't guarantee it. If you see the error message, then please wait until everything is back to normal. Then you should be able to save your edit. But, we recommend that you make a copy of your changes first, just in case.

Other effects:

• Background jobs will be slower and some may be dropped. Red links might not be updated as quickly as normal. If you create an article that is already linked somewhere else, the link will stay red longer than usual. Some long-running scripts will have to be stopped.
• We expect the code deployments to happen as any other week. However, some case-by-case code freezes could punctually happen if the operation require them afterwards.
• GitLab will be unavailable for about 90 minutes.

This project may be postponed if necessary. You can read the schedule at wikitech.wikimedia.org. Any changes will be announced in the schedule.

Please share this information with your community.

Trizek (WMF) 12:58, 15 September 2026 (UTC)

Your feedback wanted: Remove (Language link added:) and similar edits from Special:RecentChanges

(Apologies for posting in English. You can help by translating it)

Hello, I’m Danny from Wikimedia Deutschland’s Wikidata For Wikimedia Projects team.
We have been investigating and examining how Wikidata’s use in the Special:RecentChanges and Special:Watchlist pages can be made to be more useful, or less ‘noisy’ (fewer edits that have little value to the reader).

We are currently exploring to make a change in the volume and the type of Wikidata edits that appear in these pages, and we need your feedback to help us ensure this is a positive change for the Wikis and won’t disrupt your workflows.
Language links are also known as sitelinks or interlanguage links and describe when a Wikidata item is connected to a Wiki, adding it to the language dropdown tool for other connected Wikis.

A variety of "Language Link" edits as seen in the Recent Changes feed

The request for feedback is whether you support the removal of these language link edits from the Recent Changes and Watchlist feed, or would you oppose such a change and if so, why? Please share you thoughts on the dedicated metawiki Talk page.

Further information about this change: m:Wikidata_For_Wikimedia_Projects/Hide_Language_Link_edits

Thank you for any participation or feedback you give, -- User:Danny Benjafield (WMDE) 12:18, 25 September 2026 (UTC)

Tech News: 2026-39

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

• All wikis will be read-only for a few minutes on Wednesday, 23 September 2026 at 14:00 UTC. This is for the datacenter server switchover backup tests, which happen twice a year. During the switchover, all Wikimedia website traffic is shifted from one primary data center to the backup data center to test availability and prevent service disruption even in emergencies. [89]

Updates for editors

• The Growth team tested a new post-edit notice designed to encourage Temporary Account holders to register for a permanent account. The new notice replaced multiple dialogs and a simultaneous welcome notification with a single message highlighting the benefits of creating an account. The experiment increased permanent account creation from 1.94% to 3.66%, an 87% relative increase. The change will now be released to all wikis. [90]
• For Wikipedia editors using the "Suggestion mode" Beta Feature, there is a new opt-in user preference for showing "experimental" edit checks and suggestions. These types are listed at Special:EditChecks, and are intended for early developer-testing and for gathering feedback from experienced users. Administrators can change the configuration details for each suggestion as usual. Administrators can also use this feature to help test their community's ideas for locally created checks and suggestions. Experimental types will have a more distinct visual style later this week. Feedback is welcome.
• The CEE Technical Village Pump has been launched as a space for technical discussions and collaboration among Wikimedia communities in Central and Eastern Europe.
• A new tool, Starter Kit, is now available for new and small language Wikipedia communities. It brings together guided tasks, tools, and resources to help communities get started, monitor their progress, and collaborate with the broader Wikimedia community. Starter Kit is hosted on Wikimedia Toolforge and is designed for Wikipedias with fewer than 50,000 articles. Learn more about how Starter Kit works and how communities have been using it in this Diff blog post.
• The Reader Growth team is launching a retest of the image carousel experiment. The retest will use three new versions of the design, updated based on community feedback. The team will assess results and determine with communities whether or not to proceed with the feature. The experiment will begin the week of September 28 and will run on Arabic, Bengali, Chinese, Czech, English, Farsi, French, German, Indonesian, Japanese, Polish, Portuguese, Spanish, Swedish, and Vietnamese Wikipedias.
• After successful rollouts to Arabic, Bengali, Chinese, Czech, English, French, Indonesian, and Vietnamese Wikipedias, the Reading Lists feature from the Reader Experience team will be available to all logged-in users on all Wikipedia wikis starting September 28.
• View all 28 community-submitted tasks that were resolved last week. For example, an issue where the mentor status script repeatedly updated mentors’ status even when nothing had changed, creating unnecessary Recent Changes entries, has now been fixed. [91]

Updates for technical contributors

• The abusefilters list query API, used to retrieve specific details about active or historical abuse filters configured on a wiki, has been updated to support the formatversion=2 configuration parameter, thereby leading to breaking changes to the API response. All users who maintain user-scripts or other code need to check if they use the abusefilters list query API, and respond to any breaking changes. [92]
• 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 11:56, 27 September 2026 (UTC)

Tech News: 2026-40

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

• Users of default skins on desktop and mobile web (Vector 2022 and Minerva respectively) will now be informed if the search suggestions displayed as they type into Search come from page redirects. Previously, users could get confused when the top search suggestions did not match exactly what they had typed. The new redirect notice clarifies that these suggestions are not random, but related to the search. The suggested pages may be redirects to the most relevant destination articles being searched for. [93]
• Logged-out Wikipedia users on mobile web will begin to see a bookmark button for saving articles to their reading lists instead of the current Watchstar button. When clicked, the bookmark button prompts users to log in or create an account to save an article for later. An earlier experiment found that the bookmark icon was four times more likely than the Watchstar button to encourage logged-out users to create an account. This change is part of efforts to encourage more readers to become account holders and use features that help them save and return to content. [94]
• An experiment will begin on September 29 on Spanish, Arabic, English, and French Wikipedias to simplify the experience users encounter immediately after account creation. The test will explore whether removing friction from the current Welcome Survey helps new users understand what to do next more easily. The experiment will run through the end of October. [95]

• The Product and Technology Advisory Council has put out a call for the community to suggest topics that it should consider and discuss with the Wikimedia Foundation. Editors and technical contributors are invited to add topics to the council's talk page.
• Later this week, it will be possible for communities to configure Edit Checks and Suggestions so that they are shown within additional namespaces, such as a Draft: namespace. Feedback is welcome.
• A bug in the Global Watchlist is causing the page to fail to load for users that have unseen changes on Wikimedia Commons. Developers are working on a fix. Until then, affected users can follow the workarounds described in the relevant help section.
• New magic words {{CATEGORYSORT:TIMESTAMP}} and {{CATEGORYSORT:RTIMESTAMP}} are now available for use. They are able to change the default sorting of categories to be based on timestamp of categorization. [96]
• View all 20 community-submitted tasks that were resolved last week. For example, the issue where Wikistats for Wikipedias was not reachable has now been fixed. [97]

Updates for technical contributors

• The datacenter switchover, scheduled on September 23, has been postponed. The equinox exercise revealed capacity issues, preventing the switch of all services to the other datacenter. The process has been paused, prioritizing investigating that issue, to ensure that we continue to be able to serve our users reliably. A new exercise will be scheduled. Meanwhile, all traffic and edits continue to work as usual.
• On September 23, a power loss briefly affected all wikis, creating intermittent issues on both reading and editing modes. This also affected Gerrit. This is unrelated to the datacenter switchover postponement. [98]
• Produnto has been deployed to mediawiki.org and some Indic language wikis. We want to hear your feedback on this experimental product. Produnto allows users to use Lua modules hosted in Wikimedia's GitLab. It simplifies the sharing of Lua code between wikis. Instead of copying each individual Lua module from one wiki to another, users will be able to easily share packages across all wikis.
• Detailed code updates later this week: MediaWiki

Meetings and events

• A Cross-wiki code collaboration workshop will be held online on October 2 at 12:30 UTC, bringing together South Asian technical contributors to learn about Produnto and begin piloting it on Hindi, Punjabi, Odia, Telugu, and Malayalam Wikipedias. Produnto is a package manager for deploying Lua modules hosted on GitLab to Wikimedia wikis, and was recently deployed on some pilot wikis.

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

MediaWiki message delivery 10:49, 28 September 2026 (UTC)

Expanding my own user page

Hello. I am Ravi Kumar Daparthi (I also edit Wikidata as Daparthiravi; both accounts are mine). I have prepared an expanded biography for my user page, User:Ravi Kumar Daparthi, drawn from my own website and LinkedIn profile, but every attempt to publish it is disallowed by the Antispam filter, even a version with no external links at all. My account has very few edits here, which I assume is the reason. The content is my own biography and the links point only to my own website and public profiles (my Wikidata item is Q141517141). Could an administrator tell me what the filter objects to, or add the text on my behalf? I am also happy to contribute to Wikisource. Thank you. Ravi Kumar Daparthi (talk) 07:20, 29 September 2026 (UTC)

Why are you posting a resume here? A brief biography is fine but the goal of a user page is to give someone context on who you are, what your editing philosophy is, what competence you have related to the work of this site, etc., not to act as a vanity page for a job or to provide free hosting. ―Justin (koavf)❤T☮C☺M☯ 10:29, 29 September 2026 (UTC)

Thank you, Justin, that is fair, and the résumé is gone. I have rewritten my user page as a contributor introduction: who I am in a few lines, the languages I work in, what I can help with here (Indian legal texts, Telugu and English proofreading, some tooling), the public-domain material I plan to work on, how I approach editing, and a disclosure that I work in commercial legal software. There are no awards, no media coverage and no external links; the only cross-references are to my Wikidata account and item. The text is copied below so it can be checked in one place. Two questions: once the account has some history, would a single link to my personal website be acceptable on the page, and is there a good starting point you would suggest for Indian legal or bilingual government texts on this site? I will start with proofreading in the meantime.

Ravi Kumar Daparthi (also written Ravi Daparthi) is a technology entrepreneur based in Hyderabad, India. I edit Wikidata as Daparthiravi; my Wikidata item is Q141517141. (Babel: English 4, Telugu native, Hindi 2.)

Background. I have spent more than twenty years building software: first in enterprise delivery at Publicis Sapient, then in HR and recruitment technology at CEIPAL and at Oorwin, which I co-founded, and now as co-founder and CEO of LawVyn, a case management platform for Indian advocates and law firms. I also co-founded Signitives, an AI product engineering firm. I trained as an electronics engineer, studied project management at the Indian Institute of Science and IIM Bangalore, and I am doing doctoral research at the Swiss School of Business and Management, Geneva, on how large organisations adopt AI.

Mentoring and community. Outside the companies, I give time to people who are starting out. I have been a startup mentor at T-Hub, Hyderabad since 2023, working with early-stage founders on product, go-to-market, customer acquisition and fundraising and opening doors to investors and customers. Through the International Startup Foundation's Junicorn100K initiative I mentor rural youth across India, helping them turn ideas into working prototypes and connect with global markets, in line with the Bharat 2047 vision. I also mentor at E-Cell IIT Bombay's Eureka! business-model competition, and I speak to students on campuses when invited, including IIM Sambalpur and Amrita Vishwa Vidyapeetham, Chennai, on the road from engineering to entrepreneurship. I volunteer with The Akshaya Patra Foundation, and the causes I care about are children, education, the environment and access to science and technology. Free access to knowledge is part of the same commitment, and it is what brings me to Wikisource.

What I can help with.

• Indian legal documents: I work with advocates every day and know how Indian legislation, judgments and gazette notifications are structured and published.
• Proofreading in Telugu and English, and reading Hindi.
• Tooling: OCR, text clean-up and scripting for document work.
• Structured data: linking works and authors to Wikidata.

What I plan to work on.

• Indian legislation, court judgments and official gazette notifications, which Indian copyright law allows to be reproduced freely.
• Bilingual Indian government publications (Hindi and English, Telugu and English), which suit Multilingual Wikisource.
• Public-domain Telugu works on Telugu Wikisource.

How I edit. Scan-backed, faithful transcription with no modernising of the text; a copyright check before anything is uploaded; small edits first and questions on talk pages before any bulk work. Disclosure: I run a commercial legal software company. I do not use Wikisource to promote it and I keep my contributions to public-domain material.

Messages are welcome on my talk page.

Ravi Kumar Daparthi (talk) 11:17, 29 September 2026 (UTC)

Thanks for asking. I personally have no objection to linking to your own webpage and that's a common thing to happen on a user page: if you want to direct someone to a different part of the Web to learn more about you, I think that's fine. As for when you can add links, I can never remember the specifics, but it's after x days and y edits. The exact numbers are small and they vary from wiki to wiki, so that's why it's difficult for me to remember on any given one. I recommend that you just make constructive edits for a bit and then you'll notice that the change will happen spontaneously. As for your second question, I am not terribly familiar with Indian government documents, so nothing immediately comes to mind. You could try asking editors are more active sites that have material in Indian languages, e.g. at hi: or maybe even those who participated in m:Indic Wikisource Proofreadthon 2020? Looking at c:Category:Multilingual text, I see that File:ਪਰਮ-ਅਖਰੀ ਕਿ ਪੈਂਤੀ ਅਖਰੀ.pdf is an English/Punjabi text that you could add here, but it is not related to Indian law and politics. I wish I had better leads. ―Justin (koavf)❤T☮C☺M☯ 12:40, 29 September 2026 (UTC)

Allow global sysops?

Considering the recent vandalism from Special:Contributions/~2026-52647-82, I would like to propose opting Wikisource (this project) into the global sysop wikiset (m:Special:WikiSets/7). Allowing global sysops to operate here would allow them to block vandals and spammers quickly when no local administrators are online, but note that they will only deal with straightforward cases and uncontroversial maintenance. They will not intervene in content matters from this project. Thoughts? Codename Noreste (talk) 13:37, 29 September 2026 (UTC)

I am fine with it. ―Justin (koavf)❤T☮C☺M☯ 14:27, 4 October 2026 (UTC)