This is an archive of past discussions with User:Dbeef. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.
Latest comment: 10 months ago2 comments2 people in discussion
Hey @Dbeef. Your wiki edit anniversary was 2 days ago, marking 5 years of dedicated contributions to this Wikimedia project. Your passion for sharing knowledge and your remarkable contributions have not only enriched the project, but also inspired countless others to contribute. Thank you for your amazing contributions. Wishing you all the best for the year ahead:) -❙❚❚❙❙ GnOeee ❚❙❚❙❙✉07:08, 20 October 2025 (UTC)
Latest comment: 9 months ago1 comment1 person in discussion
BumblB645 has given you batteries! Batteries promote WikiLove (📖💞) and hopefully this one has made your day more powerful. It is the power source best preferred by bots. 🤖 Spread the WikiLove by giving someone else batteries, whether it be someone you have had robot wars with in the past or a good friend.
Latest comment: 9 months ago4 comments3 people in discussion
Editor of the Week
Your ongoing efforts to improve the encyclopedia have not gone unnoticed: You have been selected as Editor of the Week in recognition of your great contributions! (courtesy of the Wikipedia Editor Retention Project)
In trying to write out what dbeef (formerly known as 0xDeadbeef) has done for Wikipedia, I am finding that it would be easier for me to list what they have not accomplished. Many writers work on articles, get the GA badge, and call it a day. Not dbeef; they have been polishing, refining, expanding, and contributing to Rust (programming language) for over three years at this point, resulting in an article which far exceeds the GA criteria. Their RfA with less than 8,000 edits at the time (and I feel silly typing out "less than 8,000" with a negative connotation) pushed the boundaries for what was acceptable at RfA—I firmly believe they paved the way for a slight reduction in WP:EDITCOUNTITIS at RfA. On the technical side, they are an edit filter manager and our newest CheckUser appointee, have finally gotten continuous deployment over the finish line with DeadbeefBotII(talk·contribs·count·logs), and are the current maintainer of WP:DISCORD's WikiAuthBot2 (both are programmed in Rust, of course!). I really don't know how they manage to fit everything into their schedule, but they do—and I am truly grateful for it all. Thank you, beef.:) This nomination was seconded by TechnoSquirrel69, ~delta, QuicoleJR, Perfect4th, Bunnypranav, Hawkeye7, Sohom Datta, Vacant0 and GoldRomean.
You can copy the following text to your user page to display a user box proclaiming your selection as Editor of the Week:
Many editors work on articles, get the GA badge, and call it a day. dbeef has been polishing, refining, expanding, and contributing to Rust (programming language) for over three years. The results are articles which far exceed the GA criteria. Their 2023 RfA pushed the limitations for what edit count was acceptable at an RfA and paved the way for a slight reduction in WP:EDITCOUNTITIS. On the technical side, they are an edit filter manager and our newest CheckUser appointee, have finally gotten continuous deployment over the finish line with DeadbeefBotII(talk·contribs·count·logs), and are the current maintainer of WP:DISCORD's WikiAuthBot2 (both are programmed in Rust, of course!).
Latest comment: 7 months ago2 comments2 people in discussion
Peace is a state of balance and understanding in yourself and between others, where respect is gained by the acceptance of differences, tolerance persists, conflicts are resolved through dialog, peoples rights are respected and their voices are heard, and everyone is at their highest point of serenity without social tension. Happy Holidays to you and yours. Buster Seven Talk (UTC) 20:40, 18 December 2025 (UTC)
Latest comment: 7 months ago2 comments2 people in discussion
Happy holidays and a prosperous 2026!
I don't think I have sufficient command of language to adequately express how deeply I respect you. I'll try, but hopefully this disclaimer is sufficient. Everything I said back at WP:EDDY was true, so I got some of my bases covered. Other things I didn't get to mention or really appreciate include User:Dbeef/One big SPI guide, the care with which you approach U4C work, the kindness you show to everyone, and your amazing sense of humor. Thank you for your support as I navigate the maze that is being a functionary (ack that still feels weird to say). Which is all to say, happy holidays, and the best to you and yours in the new year:)
Latest comment: 7 months ago3 comments2 people in discussion
Hi Dbeef,
Are you still active on the Teahouse? I noticed you are listed on Wikipedia:Teahouse/Host landing under your old username. Your old page redirects to your new, so it's not a broken link, but it might be confusing to newbies that your current posts would not correspond to your /Hosts entry. DMacks (talk) 01:49, 26 December 2025 (UTC)
@DMacks: I have removed myself from there because I don't participate there much anymore. Unfortunate but my WikiWork is too preoccupied by SPIs and other administrative stuff:) dbeef [talk]23:32, 1 January 2026 (UTC)
Latest comment: 7 months ago2 comments1 person in discussion
Hello, Dbeef. Please check your email; you've got mail! The subject is Request for IPBE permission for ShuQizhe on enwp. Message added 03:35, 1 January 2026 (UTC). It may take a few minutes from the time the email is sent for it to show up in your inbox. You can remove this notice at any time by removing the {{You've got mail}} or {{ygm}} template.
Changes to the Access to Temporary Account IP Addresses Policy's disclosure rules include broadening the consecutive-blocks exception to cover all admin actions and removing the requirement to revision-delete permissible disclosures once they become unnecessary (instead requiring only their removal). See WP:TAIVDISCLOSE for more information.
Latest comment: 7 months ago1 comment1 person in discussion
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Weekly highlight
The Wikimedia Foundation has shared some guiding questions for the July 2026–June 2027 Annual Plan on Meta and Diff. These focus on global trends, faster and healthier experimentation, better support for newcomers, strengthening editors and advanced users, improving collaboration across projects, and growing and retaining readership. Feedback and ideas are welcome on the talk page.
Updates for editors
As part of the current work of Community Tech team on the Multiple watchlists project, the display of EditWatchlist will be updated as a first step towards multiple watchlists. Additionally, the pagination on Search will be updated too, as a part of the work on the Revamp pagination / page navigation wish.
The Global Watchlist is a MediaWiki extension that lets you see your watchlists from different wikis on the same page. It was recently updated to look more like the regular Watchlist, such as preparing it for temporary accounts in IP masking (including rerouting user links to contributions pages), making page titles bold, and opening links in edit summaries and tags in new browser tabs.
View all 28 community-submitted tasks that were resolved last week. For example, the issue where global blocks did not have the option to disable sending emails, has now been fixed, and will be available for use in the week of January 13.
Latest comment: 6 months ago1 comment1 person in discussion
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 SRE Team will be performing a cleanup of Wikimedia's Etherpad instance, the web-based editor for real-time collaborative document editing. All pads will be permanently deleted after 30 April, 2026 – if there are still migration projects in progress at that point the team can revisit the date on a case by case basis. Please create local backups of any content you wish to keep, as deleted data cannot be recovered. This cleanup helps reduce database size and minimize infrastructure footprint. Etherpad will continue to support real-time collaboration, but long-term storage should not be expected. Additional cleanups may occur in the future without prior notice.
Updates for editors
The Information Retrieval team will be launching an Android mobile app experiment that tests hybrid search capabilities which can handle both semantic and keyword queries. The improvement of on-platform search will enable readers to find what they’re looking for directly on Wikipedia more easily. The experiment will first be launched on Greek Wikipedia in late February, followed by English, French, and Portuguese in March. Read more on Diff blog.
The Reader Growth team will run an experiment for mobile web users, that adds a table of contents and automatically expands all article sections, to learn more about navigation issues they face. The test will be available on Arabic, Chinese, English, French, Indonesian, and Vietnamese Wikipedias.
Previously, site notices (MediaWiki:Sitenotice and MediaWiki:Anonnotice) would only render on the desktop site. Now, they will render on all platforms. Users on mobile web will now see these notices and be informed. Site administrators should be prepared to test and fix notices on mobile devices to avoid interference with articles. To opt out, interface admins can add #siteNotice { display: none; } to MediaWiki:Minerva.css.
View all 19 community-submitted tasks that were resolved last week. For example, an issue on Special:RecentChanges has been fixed. Previously, clicking hide in the active filters caused the "view new changes since…" button to disappear, though it should have remained visible. The button now behaves as expected.
Updates for technical contributors
New documentation is now available to help editors debug on-site search features. It supports troubleshooting when pages do not appear in results, when ranking seems unexpected, and when you need to inspect what content is being indexed, helping make search behavior easier to understand and analyze. Learn more.
Latest comment: 5 months ago4 comments2 people in discussion
Hi -- it's not really the bot's fault, but this edit caused ChristieBot to crash. I'll fix that on my side, but could you stop the bot from converting to articlehistory if the GA template is invalid in this way? The problem is that when {{GA}} was added the user forgot to add the page, so DeadbeefBot also did not add the page in articlehistory and the resulting GA link fails. Mike Christie (talk - contribs - library) 11:15, 22 February 2026 (UTC)
The problem line is this: |action5link=Talk:Barron Trump/GA. The GA subpages all end with a digit, which is drawn from the page= parameter in {{GA}}, which was blank here because the editor who promoted the GA failed to include it. The result is a link to Talk:Barron Trump/GA, instead of to Talk:Barron Trump/GA2. As it happens it was an invalid review anyway and the article has been put back in the GA nomination queue, so there's nothing for the bot to do now until the next GA review is completed. What I'm requesting is that if the page= parameter is blank, don't convert unless you have some other way to figure out what number to use there. Mike Christie (talk - contribs - library) 11:32, 1 March 2026 (UTC)
Latest comment: 5 months ago3 comments2 people in discussion
Hi,
I temporarily recreated this page as signature links under my old username were broken. For now it redirects to a disambiguation page. Could you please email me a copy of the content so I can refine the redirect? Thanks! TheTechie[she/they]|talk?20:15, 9 March 2026 (UTC)
Latest comment: 5 months ago2 comments2 people in discussion
Hello friend. I went looking for User:DeadbeefBot II today and had trouble finding it. I tried searches starting with Dbeef and 0xDeadbeef and it didn't follow that naming pattern. Anyway, maybe add it to your user page? If not no worries. Thanks! –Novem Linguae (talk) 13:20, 22 March 2026 (UTC)
Latest comment: 5 months ago1 comment1 person in discussion
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.
Latest comment: 4 months ago1 comment1 person in discussion
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.
@JalenBarks: Got it back running. It turns out the original OAuth key did not allow editing protected pages, so when the page got protected the bot couldn't edit it at all. dbeef [talk]22:19, 31 March 2026 (UTC)
Administrators' newsletter – April 2026
Latest comment: 4 months ago1 comment1 person in discussion
Following a motion, the GSCASTE extended-confirmed restriction in the Indian military history case has been narrowed. It now applies to caste-related topics in South Asia, and the preemptive protection remedy has been amended accordingly.
Latest comment: 4 months ago1 comment1 person in discussion
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.
Latest comment: 4 months ago1 comment1 person in discussion
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.
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, Edit filter managers 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.
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).
Latest comment: 4 months ago1 comment1 person in discussion
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.
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.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.
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.
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.
Latest comment: 3 months ago1 comment1 person in discussion
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.
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.
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.
May 2026 Administrator Election – Call for Candidates
Latest comment: 3 months ago1 comment1 person in discussion
The administrator elections process has officially started! Interested editors are encouraged to self-nominate or arrange to be nominated by reviewing the instructions at Wikipedia:Administrator elections/May 2026/Candidates.
Here is the schedule:
April 29 – May 5: Call for candidates
May 8–12: Discussion phase
May 13–19: SecurePoll voting phase
Please note the following:
The requirements to run are identical to RFA—a prospective candidate must be extended confirmed.
The process will have a seven day call for candidates phase, a two day pause, a five day discussion phase, and a seven day private vote using SecurePoll. Discussion and questions are only allowed on the candidate pages during the discussion phase.
The outcome of this process is identical to making a request for adminship. There is no official difference between an administrator appointed through RFA versus administrator elections.
Ask any questions about the process at the talk page. Later, a user talk message will be sent to official candidates with additional information about the process.
If you are interested in the process, please make sure to watchlist the appropriate pages. A watchlist notice will be added when the discussion phase opens, and again when the voting phase opens.
You're receiving this message because you signed up for the mailing list. To opt-out of future mailings, please remove yourself from the list.
Changes to user permissions made from Meta are now included in the local user permissions log (T6055).
The autoconfirmed user group will soon be modified such that the four-day account age requirement begins when an account makes its first edit (T418484).
Arbitration
The arbitration case SchroCat has been opened. Evidence submissions in this case closed on 15 April.
Per a recent motion, appeals of blocks from the conflict-of-interest VRT queue are, by default, appealed on-wiki through the normal unblock process. However, they may be heard by the Committee if COIVRTers disagree on the interpretation of the evidence or believe ArbCom would be better suited to hear the appeal. Administrators are also advised that loosening or lifting such blocks without the consent of someone with access to the queue or ArbCom can be grounds for desysopping.
Per a recent motion, restrictions issued directly by the Committee may now be enforced with blocks which work exactly like contentious topic blocks.
Latest comment: 3 months ago1 comment1 person in discussion
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.
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.
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.
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.
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.