A request for comment is open to discuss whether admins should be advised to warn users rather than issue no-warning blocks to those who have posted promotional content outside of article space.
Technical news
The Nuke feature also now provides links to the userpage of the user whose pages were deleted, and to the pages which were not selected for deletion, after page deletions are queued. This enables easier follow-up admin-actions.
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.
Happy New Year
It is time to wish all members of the project a Happy New Year and many thanks for all of the work done on articles relating to Yorkshire over the past year.
WikiProject Yorkshire Collaboration of the Month Project
The January 2025 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.
Thanks
A very big Thank you to all the editors who labour away quietly and help make this WikiProject what it is; no edit goes unnoticed.
To members who have added suggestions to the ToDo list at Yorkshire Portal.
To the football and rugby editors who have done sterling work in keeping abreast of the top clubs.
To all the WikiProject Yorkshire editors who have been busy on vandal patrol at watchlist.
Great!
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 January 2025 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:54, 7 January 2025 (UTC)
Tech News: 2025-03
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
The Single User Login system is being updated over the next few months. This is the system which allows users to fill out the login form on one Wikimedia site and get logged in on all others at the same time. It needs to be updated because of the ways that browsers are increasingly restricting cross-domain cookies. To accommodate these restrictions, login and account creation pages will move to a central domain, but it will still appear to the user as if they are on the originating wiki. The updated code will be enabled this week for users on test wikis. This change is planned to roll out to all users during February and March. See the SUL3 project page for more details and a timeline.
Updates for editors
On wikis with PageAssessments installed, you can now filter search results to pages in a given WikiProject by using the inproject: keyword. (These wikis: Arabic Wikipedia, English Wikipedia, English Wikivoyage, French Wikipedia, Hungarian Wikipedia, Nepali Wikipedia, Turkish Wikipedia, Chinese Wikipedia) [1]
One new wiki has been created: a Wikipedia in Tigre (w:tig:) [2]
View all 35 community-submitted tasks that were resolved last week. For example, there was a bug with updating a user's edit-count after making a rollback edit, which is now fixed. [3]
Updates for technical contributors
Wikimedia REST API users, such as bot operators and tool maintainers, may be affected by ongoing upgrades. Starting the week of January 13, we will begin rerouting some page content endpoints from RESTbase to the newer MediaWiki REST API endpoints for all wiki projects. This change was previously available on testwiki and should not affect existing functionality, but active users of the impacted endpoints may raise issues directly to the MediaWiki Interfaces Team in Phabricator if they arise.
Toolforge tool maintainers can now share their feedback on Toolforge UI, an initiative to provide a web platform that allows creating and managing Toolforge tools through a graphic interface, in addition to existing command-line workflows. This project aims to streamline active maintainers’ tasks, as well as make registration and deployment processes more accessible for new tool creators. The initiative is still at a very early stage, and the Cloud Services team is in the process of collecting feedback from the Toolforge community to help shape the solution to their needs. Read more and share your thoughts about Toolforge UI.
For tool and library developers who use the OAuth system: The identity endpoint used for OAuth 1 and OAuth 2 returned a JSON object with an integer in its sub field, which was incorrect (the field must always be a string). This has been fixed; the fix will be deployed to Wikimedia wikis on the week of January 13. [4]
Many wikis currently use Cite CSS to render custom footnote markers in Parsoid output. Starting January 20 these rules will be disabled, but the developers ask you to not clean up your MediaWiki:Common.css until February 20 to avoid issues during the migration. Your wikis might experience some small changes to footnote markers in Visual Editor and when using experimental Parsoid read mode, but if there are changes these are expected to bring the rendering in line with the legacy parser output. [5]
@Phikia. London2025 is confirmed to Parkrun1606 and not to Sutton1989. I’m mildly surprised given London2025 edits followed Sutton1989 threats to repeatedly insert allegations on the BLP for the next 50 years but Parkrun1606 was edit warring the content before Sutton1989 and London2025. A checkuser has suppressed London2025's edits and the others. — Malcolmxl5 (talk) 20:35, 15 January 2025 (UTC)[reply]
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
Administrators can mass-delete multiple pages created by a user or IP address using Extension:Nuke. It previously only allowed deletion of pages created in the last 30 days. It can now delete pages from the last 90 days, provided it is targeting a specific user or IP address. [6]
On wikis that use the Patrolled edits feature, when the rollback feature is used to revert an unpatrolled page revision, that revision will now be marked as "manually patrolled" instead of "autopatrolled", which is more accurate. Some editors that use filters on Recent Changes may need to update their filter settings. [7]
View all 31 community-submitted tasks that were resolved last week. For example, the Visual Editor's "Insert link" feature did not always suggest existing pages properly when an editor started typing, which has now been fixed.
Updates for technical contributors
The Structured Discussion extension (also known as Flow) is being progressively removed from the wikis. This extension is unmaintained and causes issues. It will be replaced by DiscussionTools, which is used on any regular talk page. The last group of wikis (Catalan Wikiquote, Wikimedia Finland, Goan Konkani Wikipedia, Kabyle Wikipedia, Portuguese Wikibooks, Wikimedia Sweden) will soon be contacted. If you have questions about this process, please ping Trizek (WMF) at your wiki. [8]
The latest quarterly Technical Community Newsletter is now available. This edition includes: updates about services from the Data Platform Engineering teams, information about Codex from the Design System team, 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
Patrollers and admins - what information or context about edits or users could help you to make patroller or admin decisions more quickly or easily? The Wikimedia Foundation wants to hear from you to help guide its upcoming annual plan. Please consider sharing your thoughts on this and 13 other questions to shape the technical direction for next year.
Updates for editors
iOS Wikipedia App users worldwide can now access a personalized Year in Review feature, which provides insights based on their reading and editing history on Wikipedia. This project is part of a broader effort to help welcome new readers as they discover and interact with encyclopedic content.
Edit patrollers now have a new feature available that can highlight potentially problematic new pages. When a page is created with the same title as a page which was previously deleted, a tag ('Recreated') will now be added, which users can filter for in Special:RecentChanges and Special:NewPages. [9]
Later this week, there will be a new warning for editors if they attempt to create a redirect that links to another redirect (a double redirect). The feature will recommend that they link directly to the second redirect's target page. Thanks to the user SomeRandomDeveloper for this improvement. [10]
Wikimedia wikis allow WebAuthn-based second factor checks (such as hardware tokens) during login, but the feature is fragile and has very few users. The MediaWiki Platform team is temporarily disabling adding new WebAuthn keys, to avoid interfering with the rollout of SUL3 (single user login version 3). Existing keys are unaffected. [11]
For developers that use the MediaWiki History dumps: The Data Platform Engineering team has added a couple of new fields to these dumps, to support the Temporary Accounts initiative. If you maintain software that reads those dumps, please review your code and the updated documentation, since the order of the fields in the row will change. There will also be one field rename: in the mediawiki_user_history dump, the anonymous field will be renamed to is_anonymous. The changes will take effect with the next release of the dumps in February. [12]
