User talk:AmandaNP
From Wikipedia, the free encyclopedia
| This user talk page might be watched by friendly talk page stalkers, which means that someone other than me might reply to your query. Their input is welcome and their help with messages that I cannot reply to quickly is appreciated. |
|
UTRS 3
Amanda, I would like to make some changes to the UI/UX for UTRS 3. Is the Github repo still the same? Are you working off of the master branch or the utrs3-starterfixes3 branch?--v/r - TP 20:01, 3 March 2026 (UTC)
- You've got the right repo. You can branch off of master, everything is submitted through pull requests to master so it's easier to minimize conflicts. I'm only holding the starterfixes branches open for about a week at a time, so don't worry about them. -- Amanda (she/her) 07:24, 4 March 2026 (UTC)
- The reason I ask is because master seemed out of date when I tried to look at the appeal.blade.php file. The HTML didn't resemble what was rendering in my browser. So I looked deeper and found that only the utrs3-starterfixes3 branch had the right formatting. Are you using the master branch on the prod env?--v/r - TP 20:01, 4 March 2026 (UTC)
- Temporarily I am not using, just to get these starter fixes out that came with UTRS 3 right of the bat. Once the last round stabilizes I will go back to master. But yes, that is the branch being used. -- Amanda (she/her) 04:33, 5 March 2026 (UTC)
- Okay, I'll wait until your changes get pushed back to the repo because the changes I want to make aren't reflected in the current master branch.--v/r - TP 19:37, 5 March 2026 (UTC)
- @TParis: I have merged starterfixes3 into master. I'll ensure the branch is officially changed on the server later today, but that should allow you to make changes & do a pull request. -- Amanda (she/her) 13:39, 11 March 2026 (UTC)
- Okay, I'll wait until your changes get pushed back to the repo because the changes I want to make aren't reflected in the current master branch.--v/r - TP 19:37, 5 March 2026 (UTC)
- Temporarily I am not using, just to get these starter fixes out that came with UTRS 3 right of the bat. Once the last round stabilizes I will go back to master. But yes, that is the branch being used. -- Amanda (she/her) 04:33, 5 March 2026 (UTC)
- The reason I ask is because master seemed out of date when I tried to look at the appeal.blade.php file. The HTML didn't resemble what was rendering in my browser. So I looked deeper and found that only the utrs3-starterfixes3 branch had the right formatting. Are you using the master branch on the prod env?--v/r - TP 20:01, 4 March 2026 (UTC)
Tech News: 2026-11
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 18:50, 9 March 2026 (UTC)
Happy Bureaucratship Anniversary!
| Happy bureaucratship anniversary! Hi AmandaNP! On behalf of the Birthday Committee, I'd like to wish you a very happy anniversary of your successful request for bureaucratship. Enjoy this special day! DaniloDaysOfOurLives (talk) 03:11, 13 March 2026 (UTC) |
Tech News: 2026-12
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 Improved Syntax Highlighting 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 Special:PendingChanges 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, Special: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: Special:LintTemplateErrors/night-mode-unaware-background-color.
- Users of the Improved Syntax Highlighting 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., Special:RestSandbox, 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
- The 2026 Coolest Tool Award celebrating outstanding community tools, is now open for nominations! Nominate your favorite tool using the nomination survey form by 23 March 2026. For more information on privacy and data handling, please see the survey privacy statement.
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
MediaWiki message delivery 19:33, 16 March 2026 (UTC)