안녕하세요! 위키미디어 퓨처스 랩에서 우리는 주변의 변화에 발맞추기 위해 위키미디어가 무엇을 해야 할지 논의했습니다. 우리는 실험에 대한 아이디어를 제시해 달라는 요청을 받았는데, 이는 각 커뮤니티가 참여하기 쉬운 소규모의 안전한 변화를 시도하고, 그 결과를 바탕으로 모든 커뮤니티가 배울 수 있는 방안을 찾을 수 있었습니다.
그 자리에서 논의된 아이디어 중 하나는 일부 커뮤니티에 위키미디어 재단의 실험적 기능을 간소화된 방식으로 배포하는 데 동의하는 것이었습니다. 해당 기능은 발표된 후, 각 기능에 대해 커뮤니티 토론을 거치지 않고 일부 사용자만을 대상으로 테스트(A/B 테스트)됩니다. 그리고 만약 효과가 없거나 문제가 발생한다면, 별다른 논의 없이 신속하게 원상복구될 것입니다.
이를 통해 더 현대적이고 강력한 사용자 경험을 제공할 수 있을 것입니다. 재단과 우리는 우리가 어떻게 새로운 기능을 활용하고, 이것이 다른 위키들이 새로운 기능을 도입하는 데 어떻게 선구자 역할을 하는지 공개적으로 이야기할 수 있게 될 것입니다. 재단이 최근 실험해 온 몇 가지 사례를 보려면 이 페이지를 확인해 보세요.
우리는 사전 논의 과정을 줄이고 이곳에서 더 자주 실험을 진행하는 데 동의할 수 있을까요? 공동체의 의견을 기다리겠니다. *Youngjin (토론) 2026년 4월 16일 (목) 15:07 (KST)[답변]
慈居입니다. 그간 저로 인해 상처 받으신 모든 분들게 깊은 사과를 표합니다. 폄하의 의도는 없었지만 저는 공동체 구성원들을 주제 넘게 책망했고, 저의 여러 실언은 소모적인 논쟁으로 이어졌습니다. 일찍이 양심의 가책을 느꼈으나 항상 감정만이 앞섰습니다. 모두 제가 부족한 탓입니다. 앞으로 모든 논의에 있어서 더 책임감 있게 임하겠습니다. 감사합니다. 慈居 (토론) 2026년 4월 22일 (수) 01:53 (KST)[답변]
| 보호 정책 | 분쟁 해결 |
|---|---|
|
|
보호 정책은 “내용에 관한 논쟁이 있는 문서를 보호할 때, 문서 훼손이나 저작권 침해, 생존 인물에 대한 명예 훼손 등의 정책에 반하는 경우가 아니라면 관리자는 현재의 내용 상태를 보호합니다.”라고 정하고 있으며, 분쟁 해결 정책은 “토론을 시작하기에 앞서 문서의 내용은 편집 분쟁이 발생하기 이전의 판으로 유지시킨 채 토론을 시작해야 합니다.” 라고 정하고 있는데, 분쟁 시 관리자가 보호 정책을 우선 적용하여 “보호 시점의 현재판”을 기준으로 보호한 건에 대하여 분쟁 해결을 준용하여 편집 분쟁 이전의 판으로 복구해야 한다는 요구가 왕왕 있는 편입니다. (예시: 2025년 11월 문서 관리 요청, 사용자토론:앵무#위키백과:분쟁 해결 정책 위반 등)
보호 정책은 “현재의 내용 상태를 보호”하며 보호 정책에 따라 “편집 분쟁의 결과를 반영하고 있다면 편집 분쟁이 일어나기 전 상태로 되돌릴 수 있다”는 관리자의 편집 분쟁 전 문서로 복구할 지 여부에 대한 재량을 인정하고 있는 데 반해, 분쟁 해결 정책은 “편집 분쟁 이전의 판으로 유지하여 토론을 시작해야 한”다고 규정하고 있어 관리자의 재량을 인정하지 않고 기속적으로 분쟁 이전의 판으로 문서를 유지할 것을 요구하고 있습니다. 이 때 관리자가 어느 규정을 우선적으로 집행할 지는 현재 관리자가 개별적으로 결정하고 있는데, 어느 정책이 우위에 있는지에 대한 결정을 내려야 할 시점이 된 것이 아닌가 하는 생각이 있습니다.
(참고를 위한 제시: 영어 위키백과의 경우 보호 정책에서는 “관리자는 문서의 내용이 문서 훼손, 생존 인물, 저작권 등 정책을 위반하지 않는 판 상태를 복원해야 함”이라고 명시하고 있을 뿐 편집 분쟁 이전의 판으로 복구할 지 여부는 관리자의 재량으로 맡겨두고 있습니다. (관리자가 편집 분쟁 전 판으로 문서를 되돌리는지에 대한 재량권 행사를 편집 분쟁에 연관된 것으로 해석하지 않으며, “관리자의 보호 시 편집 분쟁 이전 판으로의 복구 여부는 관리자의 재량 사항이며, 정책에 따라 요구되는 사항이 아님”) 분쟁 해결 정책에서는 문서의 내용이 편집 분쟁 전의 내용으로 유지되어야 한다는 내용 또한 영어 위키백과에는 존재하지 않습니다.) — regards, Revi 2026년 4월 23일 (목) 09:57 (KST)[답변]
- 개인적으로는 관리자는 보호 정책에 따라 문서를 보호하는 것이므로 보호 정책을 우선 적용해야 한다는 생각을 가지고 있고, 그동안 그렇게 처리해왔습니다. — regards, Revi 2026년 4월 23일 (목) 10:02 (KST)[답변]
- 전 위키백과 가입 때부터 분쟁 상태 이전의 판으로 되돌린다고 배웠고 지금까지도 그렇게 알고 있었습니다. 문서 보호는 잘 안하는 편인지라 보호 정책 자체를 그리 유심히 살펴본 기억이 없네요. 재량껏 유연히 적용하는게 당연히 좋긴 하겠는데, 기본적으로 복구하고 이외의 경우를 재량으로 뒀으면 좋겠습니다. 경험상 이렇게해야 나중에 문제될 일이 줄어들어요.
𝓰𝓲𝓷𝓪𝓪𝓷 (T/C/CA) 2026년 4월 25일 (토) 19:57 (KST)[답변]- 경험상이라고 하시지만 저는 오히려 한쪽 편 든다고 난리치는 경우를 너무 많이 경험해서 아예 보호 시점의 최신판 이외의 판으로 조정하는 것을 꺼리는 것도 있습니다… — regards, Revi 2026년 4월 25일 (토) 20:44 (KST)[답변]
- 원래부터 있던 내용보다 누군가가 고친 내용이 이상한 경우가 훨씬 많다는 저만의 빅데이터(레비님의 데이터베이스에 비하면 극스몰데이터)라서요. 물론 전 제가 가입하기 이전에 무슨 전설적인 난리들이 있었는지 잘 알지는 못합니다.
𝓰𝓲𝓷𝓪𝓪𝓷 (T/C/CA) 2026년 4월 25일 (토) 23:28 (KST)[답변]
의견 저는 문서 내용을 두고 분쟁이 발생할 경우 해당 내용이 어떠한 내용인지, 그리고 그 내용이 본문에 기록할 만한 내용인지를 확인하여 되돌릴 것인지, 아니면 그대로 둘 것인지 판단하고 있습니다. 극히 일부 경우를 제외하면 분쟁이 발생하는 내용은 출처, 본문에 오해, 문제가 되는 내용이 들어가거나 백:중립과 같은 부분을 어기는 내용들이기 때문에 저는 이러한 내용이 들어가면 부분에서 문제가 생기면 내용을 되돌리고 있습니다. 다만 출처, 본문에 문제가 없는 경우에는 본문을 무조건 되돌리지는 않고 대신 문서나 관련 분야의 토론 공간에서 해당 내용에 관해 이야기를 나누라고 안내를 하고 있습니다. --YellowTurtle9 (토론) 2026년 4월 25일 (토) 23:40 (KST)[답변]
- 원래부터 있던 내용보다 누군가가 고친 내용이 이상한 경우가 훨씬 많다는 저만의 빅데이터(레비님의 데이터베이스에 비하면 극스몰데이터)라서요. 물론 전 제가 가입하기 이전에 무슨 전설적인 난리들이 있었는지 잘 알지는 못합니다.
- 경험상이라고 하시지만 저는 오히려 한쪽 편 든다고 난리치는 경우를 너무 많이 경험해서 아예 보호 시점의 최신판 이외의 판으로 조정하는 것을 꺼리는 것도 있습니다… — regards, Revi 2026년 4월 25일 (토) 20:44 (KST)[답변]
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
- Wikipedia 25 Birthday mode is now live on Betawi, Breton, Chinese, Czech, Dutch, English, French, Gorontalo, Indonesian, Italian, Luxembourgish, Madurese, Sicilian, Spanish, Thai, and Vietnamese Wikipedias! This limited-time campaign feature celebrates 25 years of Wikipedia with a birthday mascot, Baby Globe. When turned on, Baby Globe is shown on ~2,500 articles, waiting to be discovered by readers. Communities can choose to turn Birthday mode on by getting consensus from their community and asking an admin to enable the feature and customize it via community configuration on the local wiki.
Updates for editors
- Sub-referencing, a new feature to re-use references with different details has been released to Swedish Wikipedia, Polish Wikipedia and a couple of other wikis. You can try the feature on these projects or on testwiki and betawiki. Learnings from the first pilot wiki German Wikipedia have been published in a report. Reach out to the Wikimedia Deutschland team if you are interested in becoming a pilot wiki.
- Paste Check will become available at all Wikipedias this week. The feature prompts newcomers who are pasting text they are not likely to have written into VisualEditor to consider whether doing so risks a copyright violation. Paste Check tags all edits where it is shown for potential review. Local administrators can configure various aspects of the feature via 특수:EditChecks. Research across 22 wikis found that Paste Check resulted in an 18% decrease in relative reverted-edits compared to the control group. Translators can help to localize this and related features.
- The Reader Experience team will be standardizing the user menu in the top right for all mobile users so that it is closer to the desktop experience. Currently this user menu is only visible to users with Advanced Mobile Controls (AMC) turned on. The only change is that a couple buttons previously in the left-side menu will move to the top right for users who do not have AMC turned on. This change is expected to go out March 9 and seeks to improve the user interface.
- Starting in the week of March 2, the emails sent out when an email address was added, removed, or changed for an account will switch to a substantially nicer and clearer HTML email from the prior plaintext one.
- Notifications are currently limited to 2,000 historic entries per user, and extend back to 2013 when the feature was released. This is going to be changed to only store Notifications from the last 5 years, but up to 10,000 of them. This will help with long-term infrastructure health and help to prevent more recent notifications from disappearing too soon.
- The Global Watchlist which lets you view your watchlists from multiple wikis on a single page continues to see improvements. The latest update improves label usage experience. The extension now allows activating the language fallback system for Wikidata items without labels in the viewed language, and showing those labels in the user’s preferred Wikidata language if no
uselang=URL parameter is provided. - The Wikipedia Android team has started a beta test of hybrid search on Greek Wikipedia. Hybrid search capabilities can handle both semantic and keyword queries enabling readers to find what they’re looking for directly on Wikipedia more easily.
- For security reasons, members of certain user groups are required to have two-factor authentication (2FA) enabled. Currently, 2FA is required to use the group, but not to be a member of it. Given that this model still has some vulnerabilities, the situation will gradually change in March. Members of these groups will be unable to disable 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 second half of March, users without 2FA will be removed from these groups. This applies to: CentralNotice administrators, checkusers, interface administrators, suppressors, Wikidata staff, Wikifunctions staff, WMF Office IT and WMF Trust & Safety. Nothing will change for other users. See the linked task for deployment schedule.
View all 27 community-submitted tasks that were resolved last week. For example, the issue preventing users from creating an instance in Wikibase.cloud has now been fixed.
Updates for technical contributors
- To help ensure fair use of infrastructure, over the next month the Wikimedia Foundation will implement global API rate limits across our APIs. In early March, stricter limits will be applied to unidentified requests from outside Toolforge/WMCS and API requests that are made from web browsers. In April, higher limits will be applied to identified traffic. 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.
- The Wikidata Query Service Linked Data Fragment (LDF) endpoint will be decommissioned in February. This endpoint served limited traffic, which was successfully migrated to other data access methods that were better suited to support existing use cases. The hardware used to support the LDF endpoint will be reallocated to support the ongoing backend migration efforts.
- The new Parsoid parser continues to be deployed to additional wikis, improving platform sustainability and making it easier to introduce new reading and editing features. Parsoid is now the default parser on 488 WMF wikis (268 Wikipedias), now covering more than 10% of all Wikipedia page views.
- The process and criteria for requesting exceptional access to the high volume feed of the Wikimedia Enterprise APIs (at no cost for mission-aligned usecases), have now been published. This is to provide more thorough and clearer documentation for users.
- Tech Blog, the blog dedicated to the Wikimedia technical community will be migrating to Diff, the community news and event blog. The migration should be complete in April 2026, after which new posts will be accepted for publishing. Readers will be able to access posts – old and new – on the landing page at https://diff.wikimedia.org/techblog.
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 2026년 3월 3일 (화) 02:51 (KST)[답변]
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, 25 March 2026 at 15: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.
- Last week, all wikis had 2 hours of read-only time, and extended unavailability for user-scripts and gadgets. This was due to a security incident which has since been resolved. Work is ongoing to prevent re-occurrences. For current information please see the post on the Stewards' noticeboard (translations).
Updates for editors
- Users facing multiple blocks on mobile will now see the reasons for each block separately, instead of a generic message. This helps them understand why they are blocked and what steps they can take to resolve the issue. For example, users affected for using common VPNs (such as iCloud Private Relay) will receive clearer guidance on what they need to do to start editing again.
- Later this week, Suggestion Mode will become available as a beta feature within the visual editor at all Wikipedias. This feature proactively suggests various types of actions that people can consider taking to improve Wikipedia articles, and learn about related guidelines. The feature is locally configurable, and can also be locally expanded with custom Suggestions. Current settings can be seen at Special:EditChecks and there are instructions for how administrators can customize the links to point to local guidelines. The feature is connected to Edit check which suggests improvements while someone is writing new content. In the future, the Editing team plans to evaluate the feature's impact with newcomers through a controlled experiment.
View all 23 community-submitted tasks that were resolved last week. For example, the issue where the cursor became misaligned during the use of CodeMirror’s syntax highlighting, which makes wikitext and code easier to read, has now been fixed. This problem specifically affected users who defined a font rule in a custom stylesheet while creating a new topic with DiscussionTools.
Updates for technical contributors
- API rate limiting update: To help ensure fair use of infrastructure, global API rate limits will be applied this week to requests without a compliant User-Agent that originate from outside Toolforge/WMCS and to unauthenticated requests made from web browsers. Higher limits will be applied to identified traffic in April. 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.
- The new GraphQL API has been released. The API was developed as a flexible alternative to select features of the Wikidata Query Service (WDQS), to improve developer experience and foster adaptability, and efficient data access. Try it out and give feedback. You can also sign up for usability tests.
- The PTAC Unsupported Tools Working Group continued improvements to Video2Commons in February, with fixes addressing authentication errors, large-file handling, task queue visibility, and clearer upload behavior. Work is still ongoing in some areas, including changes related to deprecated server-side uploads. Read this update to learn more.
Detailed code updates later this week: MediaWiki
In depth
- The Article Guidance team invites experienced Wikipedia editors from selected pilot wikis and interested contributors from other Wikipedias to fill out this questionnaire which is available in English, Arabic, Bengali, Japanese, Portuguese, Persian, and Turkish. Your answers will help the team customize guidance for less experienced editors and help them learn community policies and practices while creating an article. Learn more on the project page.
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
MediaWiki message delivery 2026년 3월 10일 (화) 03:52 (KST)[답변]
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 개선된 구문 강조 beta feature, also known as CodeMirror 6, has been used for wikitext syntax highlighting since November 2024. It will be promoted out of beta by May 2026 in order to bring improvements and new features to all editors who use the standard syntax highlighter. If you have any questions or concerns about promoting the feature out of beta, please share.
- Some changes to local user groups are performed by stewards on Meta-Wiki and logged there only. Now, interwiki rights changes will be logged both on Meta-Wiki and the wiki of the target user to make it easier to access a full record of user's rights changes on a local wiki. Past log entries for such changes will be backfilled in the coming weeks.
- On wikis using Flagged Revisions, the number of pending changes shown on 특수:보류중바뀜 previously counted pages which were no longer pending review, because they have been removed from the system without being reviewed, e.g. due to being deleted, moved to a different namespace, or due to wiki configuration changes. The count will be correct now. On some wikis the number shown will be much smaller than before. There should be no change to the list of pages itself.
- Wikifunctions composition language has been rewritten, resulting in a new version of the language. This change aims to increase service stability by reducing the orchestrator's memory consumption. This rewrite also enables substantial latency reduction, code simplification, and better abstractions, which will open the door to later feature additions. Read more about the changes.
- Users can now sort search results alphabetically by page title. The update gives an additional option to finding pages more easily and quickly. Previously, results could be sorted by Edit date, Creation date, or Relevance. To use the new option, open 'Advanced Search' on the search results page and select 'Alphabetically' under 'Sorting Order'.
View all 28 community-submitted tasks that were resolved last week. For example, the bug that prevented UploadWizard on Wikimedia Commons from importing files from Flickr has now been fixed.
Updates for technical contributors
- A new special page, 특수:LintTemplateErrors, has been created to list transcluded pages that are flagged as containing lint errors to help users discover them easily. The list is sorted by the number of transclusions with errors. For example: 특수:LintTemplateErrors/night-mode-unaware-background-color.
- Users of the 개선된 구문 강조 beta feature have been using CodeMirror instead of CodeEditor for syntax highlighting when editing JavaScript, CSS, JSON, Vue and Lua content pages, for some time now. Along with promoting CodeMirror 6 out of beta, the plan is to replace CodeEditor as the standard editor for these content models by May 2026. Feedback or concerns are welcome.
- The CodeMirror JavaScript modules will soon be upgraded to CodeMirror 6. Leading up to the upgrade, loading the
ext.CodeMirrororext.CodeMirror.libmodules from gadgets and user scripts was deprecated in July 2025. The use of theext.CodeMirror.switchhook was also deprecated in March 2025. Contributors can now make their scripts or gadgets compatible with CodeMirror 6. See the migration guide for more information. - The MediaWiki Interfaces team is expanding coverage of REST API module definitions to include extension APIs. REST API modules are groups of related endpoints that can be independently managed and versioned. Modules now exist for GrowthExperiments and Wikifunctions APIs. As we migrate extension APIs to this structure, documentation will move out of the main MediaWiki OpenAPI spec and REST Sandbox view, and will instead be accessible via module-specific options in the dropdown on the REST Sandbox (i.e., 특수:Rest연습장, available on all wiki projects).
- The Scribunto extension provides different pieces of information about the wiki where the module is being used via the mw.site library. Starting last week, the library also provides a way of accessing the wiki ID that can be used to facilitate cross-wiki module maintenance.
Detailed code updates later this week: MediaWiki
In depth
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
MediaWiki message delivery 2026년 3월 17일 (화) 04:35 (KST)[답변]
Hi, I’m Johannes from Wikimedia Deutschland’s Technical Wishes team. Apologies for writing in English. 당신의 언어로 번역해 주세요! We are considering to work on Community Wishlist/W17: Improve VE references' automatic names and reuse. This has been a long-term issue for wikitext editors (see e.g. en:WP:VisualEditor/Named references) which has been among the top-voted wishes in several Community Wishlist Surveys, e.g. 2017, 2019, 2022 or 2023.
We would like your input on the solutions proposed on our project page: m:WMDE Technical Wishes/References/VisualEditor automatic reference names. We are considering several options, which can be combined if desired by the community.
- Changing the default pattern for automatically generated reference names (currently
":n", e.g.":0",":1"...) to use the reference type instead (e.g."book_reference-1"). - Providing a simple mechanism for communities to configure a different default name.
- Generating automatic reference names based on the domain name (if it’s a web citation).
- Generating automatic reference names based on template parameters (e.g. "title" or "last"+"first") – defined by the community.
Visit our project page to read about our proposal in detail and share your thoughts on metawiki.
Please note: We will only implement a solution if there’s clear consensus among the global community. Our intention is not to build the perfect solution, but to find a simple and lean one that alleviates the pain caused by auto generated names. We are aware that some experienced VisualEditor users might prefer an option to manually change reference names in VisualEditor, but such a UX intervention is difficult to achieve across reference types and thus out of scope for our team, we can only improve the auto-naming mechanism. We are happy about suggestions for improving certain details of the proposed solutions. Any other feedback and alternative proposals are also welcome – even though it’s out of scope for us, it might still be relevant for future work on this topic.
Please support us interpreting consensus by clearly indicating your opinion (e.g. by using support/neutral/oppose templates). We are aware of en:WP:NOTVOTE, but given that we are facilitating this discussion with users from different wikis, potentially commenting in their native language, clearly indicating your position helps us avoid misunderstandings.
Thank you for participating!Johannes Richter (WMDE) (토론) 2026년 3월 19일 (목) 20:15 (KST)[답변]
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 site users can now log in without a password using passkeys. This is a secure method supported by fingerprint, facial recognition, or PIN. With this change, all users who opt for passwordless login will find it easier, faster, and more secure to log in to their accounts using any device. The new passkey login option currently appears as an autofill suggestion in the username field. An additional "Log in with passkey" button will soon be available for users who have already registered a passkey. This update will improve security and user experience. The screen recording demonstrates the passwordless login process step by step.
- All wikis will be read-only for a few minutes on Wednesday, 25 March 2026 at 15: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.
Updates for editors
- Wikimedia site users can now export their notifications older than 5 years using a new Toolforge tool. This will ensure that users retain their important notifications and avoid them being lost based on the planned change to delete notifications older than 5 years, as previously announced.
- Wikipedia editors in Indonesian, Thai, Turkish, and Simple English now have access to Special:PersonalDashboard. This is an early version of an experience that introduces newer editors to patrolling workflows, making it easier for them to move from making edits to participating in more advanced moderation work on their project.
- The Special:Block now has two minor interface changes. Administrators can now easily perform indefinite blocks through a dedicated radio button in the expiry section. Also, choosing an indefinite expiry provides a different set of common reasons to select from, which can be changed at: MediaWiki:Ipbreason-indef-dropdown.
- Mobile editors at several wikis can now see an improved logged-out edit warning, thanks to the recent updates from the Growth team. These changes released last week are part of ongoing efforts and tests to enhance account creation experience on mobile and then increase participation.
View all 36 community-submitted tasks that were resolved last week. For example, the bug that prevented mobile web users from seeing the block information when affected by multiple blocks has been fixed. They can now see messages of all the blocks currently affecting them when they access Wikipedia.
Updates for technical contributors
- Images built using Toolforge will soon get the upgraded buildpacks version, bringing support for newer language versions and other upstream improvements and fixes. If you use Toolforge Build Service, review the recent cloud-announce email and update your build configuration as necessary to ensure your tools are compatible.
- The API Portal documentation wiki will shut down in June 2026. API keys created on the API Portal will continue to work normally. api.wikimedia.org endpoints will be deprecated gradually starting in July 2026. Documentation on the API Portal is moving to mediawiki.org. Learn more on the project page.
Detailed code updates later this week: MediaWiki
In depth
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
MediaWiki message delivery 2026년 3월 24일 (화) 01:50 (KST)[답변]
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 Beta version of Abstract Wikipedia a new Wikimedia project which is language-independent, was launched last week. The project allows communities to build Wikipedia articles in their native language, which can be readily accessed by other users in their own languages. The wiki is powered by instructions from Wikifunctions and also based on structured content from Wikidata. Read more.
Updates for editors
- The Growth team is running an A/B test to evaluate a clearer, more user-friendly message that promotes account creation on wikis. Currently when logged-out mobile users begin editing, they see a jarring warning message that can feel abrupt and discouraging. This also presents temporary account editing as the default rather than encouraging account creation. The test is running on ten Wikipedias, including Arabic, French, Spanish and German. Read more.
- The Wikimedia Apps team is inviting feedback on how editing should work on the Wikipedia mobile apps. The discussion focuses on improving how users access editing tools when they tap "Edit". This is part of a broader effort to convert readers who develop an interest in editing, to access a more user-friendly pathway to start contributing.
View all 45 community-submitted tasks that were resolved last week. For example, an issue where citation fetching from the large newspaper archive Newspapers.com was no longer working, due to a block in Citoid requests, has now been fixed.
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 2026년 3월 31일 (화) 04:25 (KST)[답변]
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 (토론) 2026년 4월 4일 (토) 02:09 (KST)[답변]
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.
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.
- 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. - The Special:NamespaceInfo page now includes namespace aliases. For example "WP" for the "Project" ("Wikipedia") namespace on the German Wikipedia.
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 2026년 4월 7일 (화) 01:18 (KST)[답변]
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.
- 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.
Updates for technical contributors
- Starting later this week, 편집 필터 편집자 who have the 개선된 구문 강조 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.
- 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. - 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).
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 2026년 4월 14일 (화) 00:18 (KST)[답변]
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, 개선된 구문 강조, 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.
- 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.
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.
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.
- The
mirrors.wikimedia.orgservice 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. - The
imageandoldimagetable will be removed from wikireplicas. If your tools or queries accessimageoroldimagedirectly, please update them to use thefileandfilerevisiontable before 28 May. - 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 2026년 4월 20일 (월) 23:59 (KST)[답변]

제안 모드는 시각 편집기의 새로운 기능입니다. 이 기능은 “인용 추가”, “어조 개선” 또는 “모호한 링크 수정”과 같이 위키백과 문서를 개선하기 위한 조치를 능동적으로 제안합니다. 이 기능은 프로젝트별로 설정할 수 있으며(참조: 특수:EditChecks), 지역별로 사용자 정의할 수 있고 또 그렇게 해야 합니다(참조: mw:도움말:제안 모드#관리자를 위한 – 지역별 사용자 정의). 이 기능은 3월 초부터 모든 위키백과에서 베타 기능으로, 2월 초부터는 영어 위키백과에서 사용할 수 있었습니다.
2개월간의 피드백 결과 전 세계 위키백과에서 수천 건의 편집이 이루어지고, 기능 개선이 지속적으로 진행됨에 따라, 이제 이 기능이 여러분(자원봉사자)과 저희(운영진)가 함께 짧은 통제 실험을 통해 그 효과를 평가해 볼 준비가 거의 되었다고 생각합니다. 이 실험은 4주간 진행되며, 약 20개 위키에서 신규 사용자(해당 위키에서 편집 횟수가 100회 미만인 계정)의 50%에게 이 기능을 제공할 예정입니다.
시험이 시작되기 전에, 우리는 당신의 도움이 필요합니다. 아래의 "지원 및 피드백 요청" 부분에서 해당 기능이 위키의 선호도에 맞는 번역 및 구성되어 있는지 확인해 주실수 있으신가요?
왜 제안 모드를 도입하나요?
제안 모드는 다음 두 가지 대상에게 도움이 되도록 고안되었습니다:
- 편집에 열의를 가지고 있지만 어떻게 건설적으로 시작해야 할지 막막해하는 신규 사용자들이 정책과 지침을 살펴볼 수 있도록 독려해 줍니다.
- 참고: 매일 15만~20만 건의 모바일 웹 편집 세션이, 사용자가 아무런 변경도 하지 않은 채 최소 2초 동안 화면을 둘러본 후 편집을 중단하고 종료합니다.
- 수정해야 할 부분을 더 쉽게 파악하고, 조치를 취할지 여부와 그 방법을 결정하는 데 필요한 맥락을 정리할 수 있는 방법을 모색하는 숙련된 편집자들에게 도움을 줍니다.
도움 및 의견 요청
귀하의 위키에서 로컬 MediaWiki:Editcheck-config.json 파일을 생성하거나 업데이트하고, 인터페이스 번역의 85%를 완료한 것이 확인되며, 중대한 문제가 없는 경우, 다음 주부터 실험을 시작할 계획입니다. 이번 실험은 '제안 모드'가 신규 모바일 웹 사용자의 편집 중 건설적인(되돌림되지 않은) 문서 편집으로 이어지는 비율에 미치는 영향을 측정할 것입니다. 또한 이 기능이 편집자 유지율에 미치는 영향을 평가하고, 되돌림 및 차단 비율의 변화를 모니터링할 예정입니다.
감사합니다! User:Quiddity (WMF) 2026년 4월 22일 (수) 05:03 (KST)[답변]