This is an archive of past discussions with User:Malcolmxl5. 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.
Following an RfC, there is a new criterion for speedy deletion: C4, which applies to unused maintenance categories, such as empty dated maintenance categories for dates in the past.
The arbitration case Historical Elections is currently open. Proposed decision is expected by 3 September 2024 for this case.
Miscellaneous
Editors can now enter into good article review circles, an alternative for informal quid pro quo arrangements, to have a GAN reviewed in return for reviewing a different editor's nomination.
The number has been kept deliberately low to give us a fighting chance of improving them to at least GA status, also so we can concentrate our efforts on these first.
Wiki Loves Monuments
We failed on keeping York as a good article as it was down graded as the previous newsletter was being published. This month is the annual Wiki Loves Monuments, may be we can do better this month and get some relevant photographs in the Yorkshire area that are listed buildings without photographs.
WikiProject Yorkshire Collaboration of the Month Project
The September 2024 articles selected below are an editor choice as there were no nominations on the project talk page.
The project is subscribed to a clean-up listing which lists articles tagged with various clean-up tags that need attention. The listing is refreshed by a bot on a regular basis.
Monitoring is essential Use the watchlist to keep an eye on changes to the project's articles so that vandalism and spamming can be removed as quickly as possible.
Moves Please be careful when performing articles moves and ensure that you also move all the talk sub-pages and update any image fair use rational. Otherwise the archives, to-do lists, assessment comments and GA reviews get lost and the image may be deleted as it has an incorrect FUR. You will also have to check that the Commons link is set correctly.
Comments, questions and suggestions about this, or any, issue of the newsletter are always welcome and can be made by pressing the feedback button below...
Would you like to write the next newsletter for WP:YORKS? Please nominate yourself at WT:YORKS! New editors are always welcome!
Delivered September 2024 by MediaWiki message delivery.
If you do not wish to receive the newsletter, please add an N to the column against your username on the Project Mainpage.
21:27, 2 September 2024 (UTC)
Tech News: 2024-36
Extended content
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
Editors and volunteer developers interested in data visualisation can now test the new software for charts. Its early version is available on beta Commons and beta Wikipedia. This is an important milestone before making charts available on regular wikis. You can read more about this project update and help to test the charts.
Feature news
Editors who use the Special:UnusedTemplates page can now filter out pages which are expected to be there permanently, such as sandboxes, test-cases, and templates that are always substituted. Editors can add the new magic word __EXPECTUNUSEDTEMPLATE__ to a template page to hide it from the listing. Thanks to Sophivorus and DannyS712 for these improvements. [1]
Editors who use the New Topic tool on discussion pages, will now be reminded to add a section header, which should help reduce the quantity of newcomers who add sections without a header. You can read more about that, and 28 other community-submitted tasks that were resolved last week.
Last week, some Toolforge tools had occasional connection problems. The cause is still being investigated, but the problems have been resolved for now. [2]
Translation administrators at multilingual wikis, when editing multiple translation units, can now easily mark which changes require updates to the translation. This is possible with the new dropdown menu.
Project updates
A new draft text of a policy discussing the use of Wikimedia's APIs has been published on Meta-Wiki. The draft text does not reflect a change in policy around the APIs; instead, it is an attempt to codify existing API rules. Comments, questions, and suggestions are welcome on the proposed update’s talk page until September 13 or until those discussions have concluded.
Learn more
To learn more about the technology behind the Wikimedia projects, you can now watch sessions from the technology track at Wikimania 2024 on Commons. This week, check out:
Hello, back in 2016 you indefinitely blocked this page from being created. As an admin, I've been asked to unblock the page, but I'm uncomfortable doing so for fear of a possible conflict of interest without first seeking broader opinion. For context, I was recently interviewed by the Times of Israel, and the author of that article asked me to unblock the article (she knows the subject well). As the admin who blocked the article, what do you think? Has enough time passed? The subject might be notable, as there are a few RS articles on him, which she passed on to me. Cheers. -- Earl Andrew - talk14:13, 3 September 2024 (UTC)
Hi Earl. I see I salted the page as it was an article about a (then) non-notable individual that was being repeatedly created. That was a long time ago, I think enough time has passed and I have unprotected the page. -- Malcolmxl5 (talk) 14:36, 3 September 2024 (UTC)
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Feature news
Starting this week, the standard syntax highlighter will receive new colors that make them compatible in dark mode. This is the first of many changes to come as part of a major upgrade to syntax highlighting. You can learn more about what's to come on the help page. [4][5]
Editors of wikis using Wikidata will now be notified of only relevant Wikidata changes in their watchlist. This is because the Lua functions entity:getSitelink() and mw.wikibase.getSitelink(qid) will have their logic unified for tracking different aspects of sitelinks to reduce junk notifications from inconsistent sitelinks tracking. [6]
Project updates
Users of all Wikis will have access to Wikimedia sites as read-only for a few minutes on September 25, starting at 15:00 UTC. This is a planned datacenter switchover for maintenance purposes. More information will be published in Tech News and will also be posted on individual wikis in the coming weeks. [7]
Contributors of 11 Wikipedias, including English will have a new MOS namespace added to their Wikipedias. This improvement ensures that links beginning with MOS: (usually shortcuts to the Manual of Style) are not broken by Mooré Wikipedia (language code mos). [8]
Hey there, thanks for checking on the proxy status of the user I brought to the OP project. When these folks go on a spree again, would it be safe to block the IPs as proxies as soon as I see them? Or should I bring them to y'all to check? Or something else? Joyous!Noise!02:48, 9 September 2024 (UTC)
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Improvements and Maintenance
Editors interested in templates can help by reading the latest Wishlist focus area, Template recall and discovery, and share your feedback on the talkpage. This input helps the Community Tech team to decide the right technical approach to build. Everyone is also encouraged to continue adding new wishes.
The new automated Special:NamespaceInfo page helps editors understand which namespaces exist on each wiki, and some details about how they are configured. Thanks to DannyS712 for these improvements. [9]
References Check is a feature that encourages editors to add a citation when they add a new paragraph to a Wikipedia article. For a short time, the corresponding tag "Edit Check (references) activated" was erroneously being applied to some edits outside of the main namespace. This has been fixed. [10]
It is now possible for a wiki community to change the order in which a page’s categories are displayed on their wiki. By default, categories are displayed in the order they appear in the wikitext. Now, wikis with a consensus to do so can request a configuration change to display them in alphabetical order. [11]
Tool authors can now access ToolsDB's public databases from both Quarry and Superset. Those databases have always been accessible to every Toolforge user, but they are now more broadly accessible, as Quarry can be accessed by anyone with a Wikimedia account. In addition, Quarry's internal database can now be queried from Quarry itself. This database contains information about all queries that are being run and starred by users in Quarry. This information was already public through the web interface, but you can now query it using SQL. You can read more about that, and 20 other community-submitted tasks that were resolved last week.
Any pages or tools that still use the very old CSS classes mw-message-box need to be updated. These old classes will be removed next week or soon afterwards. Editors can use a global-search to determine what needs to be changed. It is possible to use the newer cdx-message group of classes as a replacement (see the relevant Codex documentation, and an example update), but using locally defined onwiki classes would be best. [12]
Technical project updates
Next week, all Wikimedia wikis will be read-only for a few minutes. This will start on September 25 at 15:00 UTC. This is a planned datacenter switchover for maintenance purposes. This maintenance process also targets other services. The previous switchover took 3 minutes, and the Site Reliability Engineering teams use many tools to make sure that this essential maintenance work happens as quickly as possible. [13]
Tech in depth
The latest monthly MediaWiki Product Insights newsletter is available. This edition includes details about: research about hook handlers to help simplify development, research about performance improvements, work to improve the REST API for end-users, and more.
To learn more about the technology behind the Wikimedia projects, you can now watch sessions from the technology track at Wikimania 2024 on Commons. This week, check out:
Hackathon Showcase (45 mins) - 19 short presentations by some of the Hackathon participants, describing some of the projects they worked on, such as automated testing of maintenance scripts, a video-cutting command line tool, and interface improvements for various tools. There are more details and links available in the Phabricator task.
Co-Creating a Sustainable Future for the Toolforge Ecosystem (40 mins) - a roundtable discussion for tool-maintainers, users, and supporters of Toolforge about how to make the platform sustainable and how to evaluate the tools available there.
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 September 25 at 15:00 UTC. Reading the wikis will not be interrupted, but editing will be paused. These twice-yearly processes allow WMF's site reliability engineering teams to remain prepared to keep the wikis functioning even in the event of a major interruption to one of our data centers.
Updates for editors
A screenshot of the interface for the Alt Text suggested-edit feature
Editors who use the iOS Wikipedia app in Spanish, Portuguese, French, or Chinese, may see the Alt Text suggested-edit experiment after editing an article, or completing a suggested edit using "Add an image". Alt-text helps people with visual impairments to read Wikipedia articles. The team aims to learn if adding alt-text to images is a task that editors can be successful with. Please share any feedback on the discussion page.
The Codex color palette has been updated with new and revised colors for the MediaWiki user interfaces. The most noticeable changes for editors include updates for: dark mode colors for Links and for quiet Buttons (progressive and destructive), visited Link colors for both light and dark modes, and background colors for system-messages in both light and dark modes.
It is now possible to include clickable wikilinks and external links inside code blocks. This includes links that are used within <syntaxhighlight> tags and on code pages (JavaScript, CSS, Scribunto and Sanitized CSS). Uses of template syntax {{…}} are also linked to the template page. Thanks to SD0001 for these improvements. [14]
Two bugs were fixed in the GlobalVanishRequest system by improving the logging and by removing an incorrect placeholder message. [15][16]
The API now enables 5,000 on-demand API requests per month and twice-monthly HTML snapshots freely (gratis and libre). More information on the updates and also improvements to the software development kits (SDK) are explained on the project's blog post. While Wikimedia Enterprise APIs are designed for high-volume commercial reusers, this change enables many more community use-cases to be built on the service too.
The Snapshot API (html dumps) have added beta Structured Contents endpoints (blog post on that) as well as released two beta datasets (English and French Wikipedia) from that endpoint to Hugging Face for public use and feedback (blog post on that). These pre-parsed data sets enable new options for researchers, developers, and data scientists to use and study the content.
In depth
The Wikidata Query Service (WDQS) is used to get answers to questions using the Wikidata data set. As Wikidata grows, we had to make a major architectural change so that WDQS could remain performant. As part of the WDQS Graph Split project, we have new SPARQL endpoints available for serving the "scholarly" and "main" subgraphs of Wikidata. The query.wikidata.org endpoint will continue to serve the full Wikidata graph until March 2025. After this date, it will only serve the main graph. For more information, please see the announcement on Wikidata.
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
Readers of 42 more wikis can now use Dark Mode. If the option is not yet available for logged-out users of your wiki, this is likely because many templates do not yet display well in Dark Mode. Please use the night-mode-checker tool if you are interested in helping to reduce the number of issues. The recommendations page provides guidance on this. Dark Mode is enabled on additional wikis once per month.
Editors using the 2010 wikitext editor as their default can access features from the 2017 wikitext editor by adding ?veaction=editsource to the URL. If you would like to enable the 2017 wikitext editor as your default, it can be set in your preferences. [17]
For logged-out readers using the Vector 2022 skin, the "donate" link has been moved from a collapsible menu next to the content area into a more prominent top menu, next to "Create an account". This restores the link to the level of prominence it had in the Vector 2010 skin. Learn more about the changes related to donor experiences. [18]
The CampaignEvents extension provides tools for organizers to more easily manage events, communicate with participants, and promote their events on the wikis. The extension has been enabled on Arabic Wikipedia, Igbo Wikipedia, Swahili Wikipedia, and Meta-Wiki. Chinese Wikipedia has decided to enable the extension, and discussions on the extension are in progress on Spanish Wikipedia and on Wikidata. To learn how to enable the extension on your wiki, you can visit the CampaignEvents page on Meta-Wiki.
Developers with an account on Wikitech-wiki should check if any action is required for their accounts. The wiki is being changed to use the single-user-login (SUL) system, and other configuration changes. This change will help reduce the overall complexity for the weekly software updates across all our wikis.
In depth
The server switch was completed successfully last week with a read-only time of only 2 minutes 46 seconds. This periodic process makes sure that engineers can switch data centers and keep all of the wikis available for readers, even if there are major technical issues. It also gives engineers a chance to do maintenance and upgrades on systems that normally run 24 hours a day, and often helps to reveal weaknesses in the infrastructure. The process involves dozens of software services and hundreds of hardware servers, and requires multiple teams working together. Work over the past few years has reduced the time from 17 minutes down to 2–3 minutes. [19]
The number has been kept deliberately low to give us a fighting chance of improving them to at least GA status, also so we can concentrate our efforts on these first.
Wiki Loves Monuments
Thanks for all those who took part in the annual Wiki Loves Monuments, assuming that there is Yorkshire in the image detail, we achieved 566 new images. Most of these were from North Yorkshire with 560 of those images indicating thay are from there. The other 6 are from elsewhere in Yorkshire.
WikiProject Yorkshire Collaboration of the Month Project
The October 2024 articles selected below are an editor choice as there were no nominations on the project talk page.
The project is subscribed to a clean-up listing which lists articles tagged with various clean-up tags that need attention. The listing is refreshed by a bot on a regular basis.
Monitoring is essential Use the watchlist to keep an eye on changes to the project's articles so that vandalism and spamming can be removed as quickly as possible.
Moves Please be careful when performing articles moves and ensure that you also move all the talk sub-pages and update any image fair use rational. Otherwise the archives, to-do lists, assessment comments and GA reviews get lost and the image may be deleted as it has an incorrect FUR. You will also have to check that the Commons link is set correctly.
Comments, questions and suggestions about this, or any, issue of the newsletter are always welcome and can be made by pressing the feedback button below...
Would you like to write the next newsletter for WP:YORKS? Please nominate yourself at WT:YORKS! New editors are always welcome!
Delivered October 2024 by MediaWiki message delivery.
If you do not wish to receive the newsletter, please add an N to the column against your username on the Project Mainpage.
Following a discussion, the speedy deletion reason "File pages without a corresponding file" has been moved from criterion G8 to F2. This does not change what can be speedily deleted.
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
Communities can now request installation of Automoderator on their wiki. Automoderator is an automated anti-vandalism tool that reverts bad edits based on scores from the new "Revert Risk" machine learning model. You can read details about the necessary steps for installation and configuration. [20]
Updates for editors
Translators in wikis where the mobile experience of Content Translation is available, can now customize their articles suggestion list from 41 filtering options when using the tool. This topic-based article suggestion feature makes it easy for translators to self-discover relevant articles based on their area of interest and translate them. You can try it with your mobile device. [21]
It is now possible for <syntaxhighlight> code blocks to offer readers a "Copy" button if the copy=1 attribute is set on the tag. Thanks to SD0001 for these improvements. [22]
Customized copyright footer messages on all wikis will be updated. The new versions will use wikitext markup instead of requiring editing raw HTML. [23]
Later this month, temporary accounts will be rolled out on several pilot wikis. The final list of the wikis will be published in the second half of the month. If you maintain any tools, bots, or gadgets on these 11 wikis, and your software is using data about IP addresses or is available for logged-out users, please check if it needs to be updated to work with temporary accounts. Guidance on how to update the code is available.
Rate limiting has been enabled for the code review tools Gerrit and GitLab to address ongoing issues caused by malicious traffic and scraping. Clients that open too many concurrent connections will be restricted for a few minutes. This rate limiting is managed through nftables firewall rules. For more details, see Wikitech's pages on Firewall, GitLab limits and Gerrit operations.
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 Structured Discussion extension (also known as Flow) is starting to be removed. This extension is unmaintained and causes issues. It will be replaced by DiscussionTools, which is used on any regular talk page. A first set of wikis are being contacted. These wikis are invited to stop using Flow, and to move all Flow boards to sub-pages, as archives. At these wikis, a script will move all Flow pages that aren't a sub-page to a sub-page automatically, starting on 22 October 2024. On 28 October 2024, all Flow boards at these wikis will be set in read-only mode. [29][30]
WMF's Search Platform team is working on making it easier for readers to perform text searches in their language. A change last week on over 30 languages makes it easier to find words with accents and other diacritics. This applies to both full-text search and to types of advanced search such as the hastemplate and incategory keywords. More technical details (including a few other minor search upgrades) are available. [31]
View all 20 community-submitted tasks that were resolved last week. For example, EditCheck was installed at Russian Wikipedia, and fixes were made for some missing user interface styles.
Updates for technical contributors
Editors who use the Toolforge tool Earwig's Copyright Violation Detector will now be required to log in with their Wikimedia account before running checks using the "search engine" option. This change is needed to help prevent external bots from misusing the system. Thanks to Chlod for these improvements. [32]
Some HTML elements in the interface are now wrapped with a <bdi> element, to make our HTML output more aligned with Web standards. More changes like this will be coming in future weeks. This change might break some tools that rely on the previous HTML structure of the interface. Note that relying on the HTML structure of the interface is not recommended and might break at any time. [34]
In depth
The latest monthly MediaWiki Product Insights newsletter is available. This edition includes: updates on Wikimedia's authentication system, research to simplify feature development in the MediaWiki platform, updates on Parser Unification and MathML rollout, and more.
The latest quarterly Technical Community Newsletter is now available. This edition include: research about improving topic suggestions related to countries, improvements to PHPUnit tests, and more.
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 Mobile Apps team has released an update to the iOS app's navigation, and it is now available in the latest App store version. The team added a new Profile menu that allows for easy access to editor features like Notifications and Watchlist from the Article view, and brings the "Donate" button into a more accessible place for users who are reading an article. This is the first phase of a larger planned navigation refresh to help the iOS app transition from a primarily reader-focused app, to an app that fully supports reading and editing. The Wikimedia Foundation has added more editing features and support for on-wiki communication based on volunteer requests in recent years.
iOS Wikipedia App's profile menu and contents
Updates for editors
Wikipedia readers can now download a browser extension to experiment with some early ideas on potential features that recommend articles for further reading, automatically summarize articles, and improve search functionality. For more details and to stay updated, check out the Web team's Content Discovery Experiments page and subscribe to their newsletter.
Later this month, logged-out editors of these 12 wikis will start to have temporary accounts created. The list may slightly change - some wikis may be removed but none will be added. Temporary account is a new type of user account. It enhances the logged-out editors' privacy and makes it easier for community members to communicate with them. If you maintain any tools, bots, or gadgets on these 12 wikis, and your software is using data about IP addresses or is available for logged-out users, please check if it needs to be updated to work with temporary accounts. Guidance on how to update the code is available. Read more about the deployment plan across all wikis.
It is now possible to create functions on Wikifunctions using Wikidata lexemes, through the new Wikidata lexeme type launched last week. When you go to one of these functions, the user interface provides a lexeme selector that helps you pick a lexeme from Wikidata that matches the word you type. After hitting run, your selected lexeme is retrieved from Wikidata, transformed into a Wikidata lexeme type, and passed into the selected function. Read more about this in the latest Wikifunctions newsletter.
Updates for technical contributors
Users of the Wikimedia sites can now format dates more easily in different languages with the new {{#timef:…}} parser function. For example, {{#timef:now|date|en}} will show as "24 November 2024". Previously, {{#time:…}} could be used to format dates, but this required knowledge of the order of the time and date components and their intervening punctuation. #timef (or #timefl for local time) provides access to the standard date formats that MediaWiki uses in its user interface. This may help to simplify some templates on multi-lingual wikis like Commons and Meta. [40][41]
Commons and Meta users can now efficiently retrieve the user's language using {{USERLANGUAGE}} instead of using {{int:lang}}. [42]
The Product and Tech Advisory Council (PTAC) now has its pilot members with representation across Africa, Asia, Europe, North America and South America. They will work to address the Movement Strategy's Technology Council initiative of having a co-defined and more resilient technological platform. [43]
In depth
The latest quarterly Growth newsletter is available. It includes: an upcoming Newcomer Homepage Community Updates module, new Community Configuration options, and details on new projects.
The Wikimedia Foundation is now an official partner of the CVE program, which is an international effort to catalog publicly disclosed cybersecurity vulnerabilities. This partnership will allow the Security Team to instantly publish common vulnerabilities and exposures (CVE) records that are affecting MediaWiki core, extensions, and skins, along with any other code the Foundation is a steward of.
The Community Wishlist is now testing machine translations for Wishlist content. Volunteers can now read machine-translated versions of wishes and dive into discussions even before translators arrive to translate content.
20–22 December 2024 - Indic Wikimedia Hackathon Bhubaneswar 2024 in Odisha, India. A hackathon for community members, including developers, designers and content editors, to build technical solutions that improve contributors' experiences.
The Wikimedia Foundation is conducting a survey of Wikipedians to better understand what draws administrators to contribute to Wikipedia, and what affects administrator retention. We will use this research to improve experiences for Wikipedians, and address common problems and needs. We have identified you as a good candidate for this research, and would greatly appreciate your participation in this anonymous survey.
You do not have to be an Administrator to participate.
The survey should take around 10-15 minutes to complete. You may read more about the study on its Meta page and view its privacy statement .
Please find our contact on the project Meta page if you have any questions or concerns.
