|
This is the talk page of SHB2000
Click here to message me – I will reply as soon as I can. All replies will be made directly underneath your message on this page. Do be aware though, that I do not use talkback. I do on the other hand, use pings as I've more or less given up on watchlists, but may not always ping you (usually, if the message has gone unanswered for about more than 12-18 hours, then I'd usually give a ping). Threads on this page are archived every 14 days of inactivity, but mass mail messages may get archived earlier, while active threads might get archived later than 14 days of inactivity, but how this page is archived isn't consistent merely because a bot couldn't do its job. |
Checkuser?
[edit]I don't know how people are nominated for local checkuser, but given recent events I think we really need one. You're very active here and already a bureaucrat, so I think it would make sense for you to have the tools. Would you be interested? I don't want to make a nomination without consulting you first. --Comment by Selfie City (talk) (contributions) 20:39, 14 October 2025 (UTC)
- Yes, I would be interested (and thanks for asking!) – I believe it's the same process as starting a nomination on WV:URN, except we need 25 support votes and m:ANPDP needs to be signed. We'd also need a minimum of two checkusers, so maybe would you be happy to put yourself down as the second? //shb (t | c | m) 21:35, 14 October 2025 (UTC)
- Some other thoughts that come to mind:
- it might be very difficult to reach 25 votes organically, so there is a non-zero chance of our nominations failing without any opposes
- it's probs worth revising Wikivoyage:CheckUser to explicitly allow stewards to continue performing checks here even after we obtain local checkusers
- Nonetheless I still think it's worth trying, especially because I've had to ask a fair few CU requests (mostly off-wiki via Discord) this year and it isn't like the amount of abuse has gone down. //shb (t | c | m) 22:06, 14 October 2025 (UTC)
- I would be happy to, but I wouldn't want to stand in the way of any bureaucrats who may be interested. I think it's worth trying a nomination even if finding 25 users is difficult. --Comment by Selfie City (talk) (contributions) 23:50, 14 October 2025 (UTC)
- Definitely; if anything there is nothing saying we can't have 3 CUs either (which would ideally be better than two). //shb (t | c | m) 00:18, 15 October 2025 (UTC)
- @SHB2000, @SelfieCity I think I read your mind and agree with your reasoning. I have raised that question. OhanaUnitedTalk page 15:13, 23 October 2025 (UTC)
- Definitely; if anything there is nothing saying we can't have 3 CUs either (which would ideally be better than two). //shb (t | c | m) 00:18, 15 October 2025 (UTC)
- I would be happy to, but I wouldn't want to stand in the way of any bureaucrats who may be interested. I think it's worth trying a nomination even if finding 25 users is difficult. --Comment by Selfie City (talk) (contributions) 23:50, 14 October 2025 (UTC)
- Some other thoughts that come to mind:
Tech News: 2025-43
[edit]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
- To optimize how user data is stored in our databases, the saved preferences of users who haven't logged in for over five years and have fewer than 100 edits will be cleared. When those users return, default settings will apply. [1]
View all 20 community-submitted tasks that were resolved last week. For example, there was a broken link from the GlobalContributions interface message to the XTools GlobalContributions page which has now been fixed. [2]
Updates for technical contributors
- The work to reroute all traffic to API endpoints under the
rest.phproute through a common API gateway is now complete. If any issues are observed, please file a phabricator ticket to the Service Ops team board. - Edits to Wikidata references or qualifiers will now be shown in RecentChanges and Watchlist entries on other wikis less often, reducing unnecessary notifications. This will reduce the overall quantity of 'noisy' entries. Wikidata's own pages remain unchanged. [3]
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:37, 20 October 2025 (UTC)
The Signpost: 20 October 2025
[edit]- News and notes: Board shuffles, LLM blocks increase, IPs are going away
- Special report: The election that isn't
- Interview: The BoT bump
- In the media: An incident at WikiConference North America; WMF reports AI-related traffic drop and explains Wikipedia to US conservatives
- Traffic report: One click after another
- Humour: Wikipedia pay rates
Growth News #35
[edit]
A quarterly update from the Growth team on our work to improve the new editor experience.
New releases
[edit]English Wikipedia gets "Add a Link" Structured Task
[edit]We released the "Add a Link" Structured Task to 100% of accounts at English Wikipedia on Tuesday, September 2nd (before then it was available to 20% of accounts).
Growth features for Wikidata
[edit]After examining if the Growth features and Mentorship could be adapted to Wikidata, we activated the Growth features on Beta Wikidata to allow for testing and discussion (T400937). Although some features, like Suggested Edits, are Wikipedia-specific, the Growth team designed most features to be more wiki-agnostic.
Work in progress
[edit]Revise Tone Structured Task
[edit]The Growth team is making progress on the technical architecture, onboarding design, and early user testing. We are targeting an A/B test before the end of this year, with constructive edits by newcomers as the primary success metric.
Add a link to more wikis
[edit]The machine learning team has been working on a new model that can suggest links to more languages, including Urdu, Chinese, and Japanese Wikipedias. We are starting to release the “Add a Link” feature to Wikipedias that weren’t supported by the previous model.
Add a link, which can be configured by the community locally, increases the chance that a new contributor will make their first edit and then continue to participate in Wikipedia.
Research
[edit]The Growth team is involved in several research initiatives to help guide our future work:
Progression System – We have published initial findings from interviews with 10 English and French Wikipedia newcomers. The research examined motivations, challenges, and feedback on a prototype system intended to help editors build confidence, develop skills, and contribute more constructively over time.
Mobile Web Editing Research – This project combines quantitative and qualitative data, community feedback, and user journey analysis to identify possible ways to enhance the mobile editing experience.
Newcomers Survey – This project surveys successful newcomers on English Wikipedia to understand their early editing experiences, tool use, and community interactions.
Community events
[edit]The Growth team participated in several community events to listen, share, and collaborate on improving newcomer experiences across Wikimedia projects.
Wikimania - Organizers as key partners to support newcomers' growth in our movement
This session invited organizers to share how they introduce newcomers to Growth features and the challenges they encounter. The discussion focused on common newcomer questions and opportunities to strengthen collaboration in supporting new editors.
Wikimania - Lightning Talk: Structured Tasks
This talk demonstrated how Structured Tasks help newcomers take their first successful steps on Wikipedia. It shared impact data, community configurations, and a demo of “Add a Link,” illustrating how these tasks make editing more accessible and sustainable, particularly for mobile contributors.
Wikimania - Building a Sustainable Future for Wikimedia Contributors
With active editor numbers declining, the Contributors Strategy aims to create a clearer, more engaging path for participation. This session, led by the WMF Contributors group with involvement from the Editing, Growth, Moderator Tools, and Connection (formerly Campaigns) teams, highlighted efforts to streamline contributor experiences, offer structured and mobile-friendly workflows, and foster meaningful engagement. Participants learned about ongoing initiatives and shared feedback to help shape a more inclusive and sustainable future for Wikimedia contributors.
CEE Meeting - Retaining beginners and improving content moderation: an inclusive and sustainable future for Wikipedia contributors
Many communities face a decline in volunteer engagement. Newcomers often leave soon after joining, while experienced editors struggle to manage increasingly complex workflows and overwhelming backlogs. We presented the Contributors Strategy and the different features and workflows that can help communities to address these challenges. We listened to the specific needs of the CEE communities to help guide the Contributors teams' work.
Growth team's newsletter prepared by the Growth team and posted by bot • Give feedback • Subscribe or unsubscribe.
10:23, 22 October 2025 (UTC)
Tech News: 2025-44
[edit]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 Wikipedia iOS app has launched an A/B/C test of improvements made to the tabbed browsing feature for select regions and languages. The test, named “More dynamic tabs”, explores new tab experiences and includes “Did you know” and “Because you read” article recommendations. You can read more on the project page.
- Autoconfirmed users on small and medium wikis with the CampaignEvents extension can now use Event Registration without the Event Organizer right. This feature lets organizers enable registration, manage participants, and lets users register with one click instead of signing event pages.
View all 31 community-submitted tasks that were resolved last week. For example, the issue of flashing colors when holding or pressing the arrow keys under the dark mode settings in Vector 2022 has been fixed. [4]
Updates for technical contributors
- The CampaignEvents extension will be deployed to all remaining wikis during the week of 17 November 2025. The extension currently includes three features: Event Registration, Collaboration List, and Invitation List. For this rollout, Invitation List will not be enabled on Wikifunctions and MediaWiki unless requested by those communities. Visit the deployment page to learn more.
- The SwaggerUI-based REST sandbox experience is now live on all wiki projects. The sandbox can be accessed through the Special:RestSandbox page. Please report any issues to the MediaWiki Interfaces team board, or join the discussion on the project launch page. [5]
- Transform endpoints with a trailing slash path in the MediaWiki REST API are now marked as deprecated. They will remain functional during this time, but removal is expected by the end of January 2026. All API users currently calling them are encouraged to transition to the non-trailing slash versions. Both endpoint variations can be found and tested using the REST Sandbox. See the MediaWiki REST API Deprecation page for more detailed information about the API deprecation policies and procedures.
- A dedicated changelog now exists for the MediaWiki REST API. The changelog provides an overview of these changes, making it easier for developers to keep track of improvements and iterations. Announcements will also continue to flow through the standard communication channels, including Tech News and email distribution lists, but can now be more easily referenced from a central location. If you have feedback about the style, structure, or content of this changelog, please join the discussion.
- Administrators can delete the tracking category which was previously added by the JsonConfig extension, as it is no longer used. See the categories linked from Q130635582. It is OK if there are still pages listed in the category as that is just a caching issue, and they will be automatically cleared out the next time each page is edited. [6]
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.
