User talk:Bamyers99
| This is a Wikipedia user talk page. This is not an encyclopedia article or the talk page for an encyclopedia article. If you find this page on any site other than Wikipedia, you are viewing a mirror site. Be aware that the page may be outdated and that the user whom this page is about may have no personal affiliation with any site other than Wikipedia. The original talk page is located at https://en.wikipedia.org/wiki/User_talk:Bamyers99. |
 Archives (Index) |
|
This page is archived by ClueBot III.
|
Measuring impact on AfroCreatives WikiProject using bambot cleanup tool
[edit]Hi @Bamyers99.
I hope you're well.
I'm curious on how to read the data on the line chart and the table on the cleanup tool history page to determine how many articles that are improved and how many issues that are resolved over a given period of time on AfroCreatives WikiProject.
Any clarification you could provide would be highly appreciated. Ceslause (talk) 10:23, 14 March 2025 (UTC)
- @Ceslause: The "New articles" column indicates articles that had no cleanup issue last week, but have a cleanup issue this week. The "Resolved articles" column indicates articles that had a cleanup issue last week, but have no cleanup issue this week. --Bamyers99 (talk) 21:45, 14 March 2025 (UTC)
- Thank you so much! Ceslause (talk) 20:58, 23 March 2025 (UTC)
Tech News: 2025-12
[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.
Weekly highlight
- Twice a year, around the equinoxes, the Wikimedia Foundation's Site Reliability Engineering (SRE) team performs a datacenter server switchover, redirecting all traffic from one primary server to its backup. This provides reliability in case of a crisis, as we can always fall back on the other datacenter. Thanks to the Listen to Wikipedia tool, you can hear the switchover take place: Before it begins, you'll hear the steady stream of edits; Then, as the system enters a brief read-only phase, the sound stops for a couple of minutes, before resuming after the switchover. You can read more about the background and details of this process on the Diff blog. If you want to keep an ear out for the next server switchover, listen to the wikis on March 19 at 14:00 UTC.
Updates for editors
- The improved Content Translation tool dashboard is now available in 10 Wikipedias and will be available for all Wikipedias soon. With the unified dashboard, desktop users can now: Translate new sections of an article; Discover and access topic-based article suggestion filters (initially available only for mobile device users); Discover and access the Community-defined lists filter, also known as "Collections", from wiki-projects and campaigns.
- On Wikimedia Commons, a new system to select the appropriate file categories has been introduced: if a category has one or more subcategories, users will be able to click on an arrow that will open the subcategories directly within the form, and choose the correct one. The parent category name will always be shown on top, and it will always be possible to come back to it. This should decrease the amount of work for volunteers in fixing/creating new categories. The change is also available on mobile. These changes are part of planned improvements to the UploadWizard.
- The Community Tech team is seeking wikis to join a pilot for the Multiblocks feature and a refreshed Special:Block page in late March. Multiblocks enables administrators to impose multiple different types of blocks on the same user at the same time. If you are an admin or steward and would like us to discuss joining the pilot with your community, please leave a message on the project talk page.
- Starting March 25, the Editing team will test a new feature for Edit Check at 12 Wikipedias: Multi-Check. Half of the newcomers on these wikis will see all Reference Checks during their edit session, while the other half will continue seeing only one. The goal of this test is to see if users are confused or discouraged when shown multiple Reference Checks (when relevant) within a single editing session. At these wikis, the tags used on edits that show References Check will be simplified, as multiple tags could be shown within a single edit. Changes to the tags are documented on Phabricator. [1]
- The Global reminder bot, which is a service for notifying users that their temporary user-rights are about to expire, now supports using the localized name of the user-rights group in the message heading. Translators can see the listing of existing translations and documentation to check if their language needs updating or creation.
- The GlobalPreferences gender setting, which is used for how the software should refer to you in interface messages, now works as expected by overriding the local defaults. [2]
View all 26 community-submitted tasks that were resolved last week. For example, the Wikipedia App for Android had a bug fixed for when a user is browsing and searching in multiple languages. [3]
Updates for technical contributors
- Later this week, the way that Codex styles are loaded will be changing. There is a small risk that this may result in unstyled interface message boxes on certain pages. User generated content (e.g. templates) is not impacted. Gadgets may be impacted. If you see any issues please report them. See the linked task for details, screenshots, and documentation on how to fix any affected gadgets.
- 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 23:45, 17 March 2025 (UTC)
The Signpost: 22 March 2025
[edit]- From the editor: Hanami
- News and notes: Deeper look at takedowns targeting Wikipedia
- In the media: The good, the bad, and the unusual
- Recent research: Explaining the disappointing history of Flagged Revisions; and what's the impact of ChatGPT on Wikipedia so far?
- Traffic report: All the world's a stage, we are merely players...
- Gallery: WikiPortraits rule!
- Essay: Unusual biographical images
- Obituary: Rest in peace
Tech News: 2025-13
[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.
Weekly highlight
- The Wikimedia Foundation is seeking your feedback on the drafts of the objectives and key results that will shape the Foundation's Product and Technology priorities for the next fiscal year (starting in July). The objectives are broad high-level areas, and the key-results are measurable ways to track the success of their objectives. Please share your feedback on the talkpage, in any language, ideally before the end of April.
Updates for editors
- The CampaignEvents extension will be released to multiple wikis (see deployment plan for details) in April 2025, and the team has begun the process of engaging communities on the identified wikis. The extension provides tools to organize, manage, and promote collaborative activities (like events, edit-a-thons, and WikiProjects) on the wikis. The extension has three tools: Event Registration, Collaboration List, and Invitation Lists. It is currently on 13 Wikipedias, including English Wikipedia, French Wikipedia, and Spanish Wikipedia, as well as Wikidata. Questions or requests can be directed to the extension talk page or in Phabricator (with #campaigns-product-team tag).
- Starting the week of March 31st, wikis will be able to set which user groups can view private registrants in Event Registration, as part of the CampaignEvents extension. By default, event organizers and the local wiki admins will be able to see private registrants. This is a change from the current behavior, in which only event organizers can see private registrants. Wikis can change the default setup by requesting a configuration change in Phabricator (and adding the #campaigns-product-team tag). Participants of past events can cancel their registration at any time.
- Administrators at wikis that have a customized MediaWiki:Sidebar should check that it contains an entry for the Special pages listing. If it does not, they should add it using
* specialpages-url|specialpages. Wikis with a default sidebar will see the link moved from the page toolbox into the sidebar menu in April. [4] - The Minerva skin (mobile web) combines both Notice and Alert notifications within the bell icon (
). There was a long-standing bug where an indication for new notifications was only shown if you had unseen Alerts. This bug is now fixed. In the future, Minerva users will notice a counter atop the bell icon when you have 1 or more unseen Notices and/or Alerts. [5] - View all 23 community-submitted tasks that were resolved last week.
Updates for technical contributors
- VisualEditor has introduced a new client-side hook for developers to use when integrating with the VisualEditor target lifecycle. This hook should replace the existing lifecycle-related hooks, and be more consistent between different platforms. In addition, the new hook will apply to uses of VisualEditor outside of just full article editing, allowing gadgets to interact with the editor in DiscussionTools as well. The Editing Team intends to deprecate and eventually remove the old lifecycle hooks, so any use cases that this new hook does not cover would be of interest to them and can be shared in the task.
- Developers who use the
mw.ApiJavaScript library, can now identify the tool using it with theuserAgentparameter:var api = new mw.Api( { userAgent: 'GadgetNameHere/1.0.1' } );. If you maintain a gadget or user script, please set a user agent, because it helps with library and server maintenance and with differentiating between legitimate and illegitimate traffic. [6][7] - 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 22:39, 24 March 2025 (UTC)
Template parameters with talk page archives
[edit]Would it be feasible to exclude archives of talk pages (or all subpages of talk pages, such as archives and GA/FA reviews) from the Template Parameters report? I understand including talk pages in the report was done in order to track parameters in templates that only go on talk pages (WikiProject banners), and archived talk pages do not have WikiProject banners.
It is not clear to me that there is any consensus to edit archived talk pages in order to remove deprecated/non-functional parameters from templates that show up in the report (see recent discussion about editing archived talk pages), and I'd rather not spend my time editing archives. But as it stands now, the Template Parameter report for the templates I am interested in getting clogged with bad parameters that only appear on archived talk pages. Plantdrew (talk) 20:08, 31 March 2025 (UTC)
- @Plantdrew: I have told it to stop looking at templates on pages with /Archive in their name. --Bamyers99 (talk) 22:06, 31 March 2025 (UTC)
Tech News: 2025-14
[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 Editing team is working on a new Edit check: Peacock check. This check's goal is to identify non-neutral terms while a user is editing a wikipage, so that they can be informed that their edit should perhaps be changed before they publish it. This project is at the early stages, and the team is looking for communities' input: in this Phabricator task, they are gathering on-wiki policies, templates used to tag non-neutral articles, and the terms (jargon and keywords) used in edit summaries for the languages they are currently researching. You can participate by editing the table on Phabricator, commenting on the task, or directly messaging Trizek (WMF).
- Single User Login has now been updated on all wikis to move login and account creation to a central domain. This makes user login compatible with browser restrictions on cross-domain cookies, which have prevented users of some browsers from staying logged in.
- View all 35 community-submitted tasks that were resolved last week.
Updates for technical contributors
- Starting on March 31st, the MediaWiki Interfaces team will begin a limited release of generated OpenAPI specs and a SwaggerUI-based sandbox experience for MediaWiki REST APIs. They invite developers from a limited group of non-English Wikipedia communities (Arabic, German, French, Hebrew, Interlingua, Dutch, Chinese) to review the documentation and experiment with the sandbox in their preferred language. In addition to these specific Wikipedia projects, the sandbox and OpenAPI spec will be available on the on the test wiki REST Sandbox special page for developers with English as their preferred language. During the preview period, the MediaWiki Interfaces Team also invites developers to share feedback about your experience. The preview will last for approximately 2 weeks, after which the sandbox and OpenAPI specs will be made available across all wiki projects.
- Detailed code updates later this week: MediaWiki
In depth
- Sometimes a small, one line code change can have great significance: in this case, it means that for the first time in years we're able to run all of the stack serving maps.wikimedia.org - a host dedicated to serving our wikis and their multi-lingual maps needs - from a single core datacenter, something we test every time we perform a datacenter switchover. This is important because it means that in case one of our datacenters is affected by a catastrophe, we'll still be able to serve the site. This change is the result of extensive work by two developers on porting the last component of the maps stack over to kubernetes, where we can allocate resources more efficiently than before, thus we're able to withstand more traffic in a single datacenter. This work involved a lot of complicated steps because this software, and the software libraries it uses, required many long overdue upgrades. This type of work makes the Wikimedia infrastructure more sustainable.
Meetings and events
- MediaWiki Users and Developers Workshop Spring 2025 is happening in Sandusky, USA, and online, from 14–16 May 2025. The workshop will feature discussions around the usage of MediaWiki software by and within companies in different industries and will inspire and onboard new users. Registration and presentation signup is now available at the workshop's website.
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
MediaWiki message delivery 00:02, 1 April 2025 (UTC)
New article list oddity
[edit]Hi Bamyers, as a regular AfD closer I've noticed that Portal:COVID-19/New articles comes up rather frequently - more than I'd expect - among the links to deleted articles in the XfD closer script. A user more technically capable than me found it seems to come from here. Whether it's a problem, I'm not sure - so I thought I'd ask. Best, Vanamonde93 (talk) 00:53, 2 April 2025 (UTC)
- @Vanamonde93: User:InceptionBot does keyword searches on new articles using these keywords: User:AlexNewArtBot/COVID-19. Articles stay on the list for 2 weeks. --Bamyers99 (talk) 01:15, 2 April 2025 (UTC)
Tech News: 2025-15
[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
- From now on, interface admins and centralnotice admins are technically required to enable two-factor authentication before they can use their privileges. In the future this might be expanded to more groups with advanced user-rights. [8]
- View all 20 community-submitted tasks that were resolved last week.
Updates for technical contributors
- The Design System Team is preparing to release the next major version of Codex (v2.0.0) on April 29. Editors and developers who use CSS from Codex should see the 2.0 overview documentation, which includes guidance related to a few of the breaking changes such as
font-size,line-height, andsize-icon. - The results of the Developer Satisfaction Survey (2025) are now available. Thank you to all participants. These results help the Foundation decide what to work on next and to review what they recently worked on.
- Detailed code updates later this week: MediaWiki
Meetings and events
- The 2025 Wikimedia Hackathon will take place in Istanbul, Turkey, between 2–4 May. Registration for attending the in-person event will close on 13 April. Before registering, please note the potential need for a visa or e-visa to enter the country.
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
MediaWiki message delivery 18:49, 7 April 2025 (UTC)
The Signpost: 9 April 2025
[edit]- Opinion: Crawlers, hogs and gorillas
- Debriefing: Giraffer's RfA debriefing
- Obituary: RHaworth, TomCat4680 and PawełMM
- Traffic report: Heigh-Ho, Heigh-Ho, off to report we go...
- News from Diff: Strengthening Wikipedia’s neutral point of view
- Comix: Thirteen
Get a Life
[edit]Get a life Mickeymouse der (talk) 19:19, 11 April 2025 (UTC)
Broken section anchors
[edit]Hi @Bamyers99, I would like to ask if you could provide me with the query used in the "Broken section anchors" database report on Wikipedia. It would be really helpful for me to review the query used to analyze broken or missing section anchors in redirects, as part of our work with Wikipedia's database. Thank you in advance for your help! Best regards. Mohammed Qays (🗣) 12:01, 13 April 2025 (UTC)
- @Mohammed Qays: It takes more than a query to determine if an anchor is missing. The source code is at BrokenSectionAnchors.php (github).
Basic flow:
- Retrieve all redirect target pages rendered contents
- SELECT DISTINCT rd_title FROM redirect WHERE rd_fragment IS NOT NULL AND rd_fragment <> AND rd_namespace = 0
- Cache each target page by retrieving from https://en.wikipedia.org/wiki/{$rd_title}
- Check for existence of each redirect target anchor (fragment) in the cached page
- SELECT rd_title, page_title, rd_fragment FROM redirect, page WHERE rd_fragment IS NOT NULL AND rd_fragment <> AND rd_namespace = 0 AND page_namespace = 0 AND rd_from = page_id
- Scan the page text for rd_fragment php code