This is an archive of past discussions with User:SilverLocust. 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.
Hello! Voting in the 2024 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 2 December 2024. All eligible users are allowed to vote. Users with alternate accounts may only vote once.
The Arbitration Committee is the panel of editors responsible for conducting the Wikipedia arbitration process. It has the authority to impose binding solutions to disputes between editors, primarily for serious conduct disputes the community has been unable to resolve. This includes the authority to impose site bans, topic bans, editing restrictions, and other measures needed to maintain our editing environment. The arbitration policy describes the Committee's roles and responsibilities in greater detail.
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
Users of Wikimedia sites will now be warned when they create a redirect to a page that doesn't exist. This will reduce the number of broken redirects to red links in our projects. [1]
View all 42 community-submitted tasks that were resolved last week. For example, Pywikibot, which automates work on MediaWiki sites, was upgraded to 9.5.0 on Toolforge. [2]
Updates for technical contributors
On wikis that use the FlaggedRevs extension, pages created or moved by users with the appropriate permissions are marked as flagged automatically. This feature has not been working recently, and changes fixing it should be deployed this week. Thanks to Daniel and Wargo for working on this. [3][4]
In depth
There is a new Diff post about Temporary Accounts, available in more than 15 languages. Read it to learn about what Temporary Accounts are, their impact on different groups of users, and the plan to introduce the change on all wikis.
Meetings and events
Technical volunteers can now register for the 2025 Wikimedia Hackathon, which will take place in Istanbul, Turkey. Application for travel and accommodation scholarships is open from November 12 to December 10 2024. The registration for the event will close in mid-April 2025. The Wikimedia Hackathon is an annual gathering that unites the global technical community to collaborate on existing projects and explore new ideas.
Join the Wikimedia Commons community calls this week to help prioritize support for Commons which will be planned for 2025–2026. The theme will be how content should be organised on Wikimedia Commons. This is an opportunity for volunteers who work on different things to come together and talk about what matters for the future of the project. The calls will take place November 21, 2024, 8:00 UTC and 16:00 UTC.
A Language community meeting will take place November 29, 16:00 UTC to discuss updates and technical problem-solving.
On my first (non-WP:ROUNDROBIN) redirect suppression
I'm the person you granted temporary page mover rights yesterday, and I wanted to ask if this move, where "Viceskeeni2" was the username of the page author, was a correct application of that criterion. JJPMaster (she/they) 02:48, 23 November 2024 (UTC)
I can only speak for myself on that, and I wouldn't say it's unreasonable to conclude that the criterion applied.
Either way, redirects are WP:CHEAP, and redirects in draftspace are particularly harmless (perhaps with some exceptions), so it would be fine here to just leave a redirect.
When you do suppress a redirect (other than in a round-robin swap), you should check for incoming links. (From the granting message: "Please remember to [...] make link corrections where necessary, including broken double-redirects when suppressredirect is used. This can be done using Special:WhatLinksHere.") In this instance, User:Viceskeeni2/Selimiye Mosque (Deggendorf) was a redirect to Draft:Viceskeeni2/Selimiye Mosque (Deggendorf) but broke after the draft was moved without leaving a redirect. So the broken redirect was deleted per WP:G8 (incorrectly, since G8 notes that "Redirects that were broken as a result of a page move or retargeting [...] should instead be retargeted to their target's new name"). Also, by moving the draft without leaving a redirect, it redlinked the link at the creator's userpage, User:Viceskeeni2. SilverLocust💬07:07, 23 November 2024 (UTC)
I think the reason I suppressed that redirect was because I thought that the continued inclusion of the username and forward slash indicated that they accidentally forgot to delete the part of the title that made it clear the page was in userspace (inspired by this move I took before being granted page mover access). However, my use of {{db-error}} might have made it a bit unclear—I think that what is more clear than that Draft:Selimiye Mosque (Deggendorf) was intended was that Draft:Viceskeeni2/Selimiye Mosque (Deggendorf) was not intended. I was also considering moving the page back to User:Viceskeeni2/Selimiye Mosque (Deggendorf) over redirect, but decided that that was unlikely to be the intended title, since it had just been moved therefrom. JJPMaster (she/they) 16:24, 23 November 2024 (UTC)
Hello, SilverLocust. This is a bot-delivered message letting you know that Draft:Equity power of United States courts, a page you created, has not been edited in at least 5 months. Drafts that have not been edited for six months may be deleted, so if you wish to retain the page, please edit it again or request that it be moved to your userspace.
If the page has already been deleted, you can request it be undeleted so you can continue working on it.
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
A new version of the standard wikitext editor-mode syntax highlighter will be available as a beta feature later this week. This brings many new features and bug fixes, including right-to-left support, template folding, autocompletion, and an improved search panel. You can learn more on the help page.
The 2010 wikitext editor now supports common keyboard shortcuts such Ctrl+B for bold and Ctrl+I for italics. A full list of all six shortcuts is available. Thanks to SD0001 for this improvement. [5]
Starting November 28, Flow/Structured Discussions pages will be automatically archived and set to read-only at the following wikis: bswiki, elwiki, euwiki, fawiki, fiwiki, frwikiquote, frwikisource, frwikiversity, frwikivoyage, idwiki, lvwiki, plwiki, ptwiki, urwiki, viwikisource, zhwikisource. This is done as part of StructuredDiscussions deprecation work. If you need any assistance to archive your page in advance, please contact Trizek (WMF).
The CodeEditor, which can be used in JavaScript, CSS, JSON, and Lua pages, now offers live autocompletion. Thanks to SD0001 for this improvement. The feature can be temporarily disabled on a page by pressing Ctrl+, and un-selecting "Live Autocompletion".
Tool-maintainers who use the Graphite system for tracking metrics, need to migrate to the newer Prometheus system. They can check this dashboard and the list in the Description of the task T350592 to see if their tools are listed, and they should claim metrics and dashboards connected to their tools. They can then disable or migrate all existing metrics by following the instructions in the task. The Graphite service will become read-only in April. [6]
The New PreProcessor parser performance report has been fixed to give an accurate count for the number of Wikibase entities accessed. It had previously been resetting after 400 entities. [7]
Meetings and events
A Language community meeting will take place November 29 at 16:00 UTC. There will be presentations on topics like developing language keyboards, the creation of the Mooré Wikipedia, the language support track at Wiki Indaba, and a report from the Wayuunaiki community on their experiences with the Incubator and as a new community over the last 3 years. This meeting will be in English and will also have Spanish interpretation.
Hi, thank you for acting as closer in this discussion. Note that Category:Hip hop, several articles within, and related subcategories, will need to be moved to be consistent with the hyphenated spelling. 162 etc. (talk) 08:21, 2 December 2024 (UTC)
your Editnotices help
Again thanks for trying to help, but just as a future heads-up, even though I consider myself fairly conversant in technology, I don't have the faintest clue why I would be helped by you offering me to start up draft articles, nor why I am benefited from your choice of two. They are (as far as I can see) completely blank: the boilerplate code claims there are drafts but there's nothing there. Furthermore when I expand each thing, I'm greeted with more boilerplate for "You are editing Wikipedia right now!" and obviously false claims these drafts are " today's featured article." The boilerplate goes on and on, for a reason that completely escapes me.
I'm not writing this to ask you what all of this means; I have abandoned my hope my request will get implemented in the short-term. Instead I am humbly asking that you reconsider before trying to help another editor the same way. Bluntly speaking, your "help" is likely just as incomprehensible to them as it is to me. Maybe add a short explanatory note so the editor understands what you are offering, or something. I genuinely don't know what's missing other than you gave me something I have zero clue how to use, and I'm thinking of the next editor you want to help.
Anyway, have a nice day, and again, I am not expecting or asking for any response on your part. Thank you for wanting to help out, even if I am clearly not competent enough to appreciate it. Regards, CapnZapp (talk) 10:53, 2 December 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.
Starting this week, Wikimedia wikis no longer support connections using old RSA-based HTTPS certificates, specifically rsa-2048. This change is to improve security for all users. Some older, unsupported browser or smartphone devices will be unable to connect; Instead, they will display a connectivity error. See the HTTPS Browser Recommendations page for more-detailed information. All modern operating systems and browsers are always able to reach Wikimedia projects. [8]
Starting December 16, Flow/Structured Discussions pages will be automatically archived and set to read-only at the following wikis: arwiki, cawiki, frwiki, mediawikiwiki, orwiki, wawiki, wawiktionary, wikidatawiki, zhwiki. This is done as part of StructuredDiscussions deprecation work. If you need any assistance to archive your page in advance, please contact Trizek (WMF). [9]
This month the Chart extension was deployed to production and is now available on Commons and Testwiki. With the security review complete, pilot wiki deployment is expected to start in the first week of December. You can see a working version on Testwiki and read the November project update for more details.
View all 23 community-submitted tasks that were resolved last week. For example, a bug with the "Download as PDF" system was fixed. [10]
Updates for technical contributors
In late February, temporary accounts will be rolled out on at least 10 large wikis. This deployment will have a significant effect on the community-maintained code. This is about Toolforge tools, bots, gadgets, and user scripts that use IP address data or that are available for logged-out users. The Trust and Safety Product team wants to identify this code, monitor it, and assist in updating it ahead of the deployment to minimize disruption to workflows. The team asks technical editors and volunteer developers to help identify such tools by adding them to this list. In addition, review the updated documentation to learn how to adjust the tools. Join the discussions on the project talk page or in the dedicated thread on the Wikimedia Community Discord server (in English) for support and to share feedback.
Following an RFC, the policy on restoration of adminship has been updated. All former administrators may now only regain the tools following a request at the Wikipedia:Bureaucrats' noticeboard within 5 years of their most recent admin action. Previously this applied only to administrators deysopped for inactivity.
Following a request for comment, a new speedy deletion criterion, T5, has been enacted. This applies to template subpages that are no longer used.
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
Technical documentation contributors can find updated resources, and new ways to connect with each other and the Wikimedia Technical Documentation Team, at the Documentation hub on MediaWiki.org. This page links to: resources for writing and improving documentation, a new #wikimedia-techdocs IRC channel on libera.chat, a listing of past and upcoming documentation events, and ways to request a documentation consultation or review. If you have any feedback or ideas for improvements to the documentation ecosystem, please contact the Technical Documentation Team.
Updates for editors
Layout change for the Edit Check feature
Later this week, Edit Check will be relocated to a sidebar on desktop. Edit check is the feature for new editors to help them follow policies and guidelines. This layout change creates space to present people with new Checks that appear while they are typing. The initial results show newcomers encountering Edit Check are 2.2 times more likely to publish a new content edit that includes a reference and is not reverted.
The Chart extension, which enables editors to create data visualizations, was successfully made available on MediaWiki.org and three pilot wikis (Italian, Swedish, and Hebrew Wikipedias). You can see a working examples on Testwiki and read the November project update for more details.
Translators in wikis where the mobile experience of Content Translation is available, can now discover articles in Wikiproject campaigns of their interest from the "All collection" category in the articles suggestion feature. Wikiproject Campaign organizers can use this feature, to help translators to discover articles of interest, by adding the <page-collection> </page-collection> tag to their campaign article list page on Meta-wiki. This will make those articles discoverable in the Content Translation tool. For more detailed information on how to use the tool and tag, please refer to the step-by-step guide. [11]
The Nuke feature, which enables administrators to mass delete pages, now has a multiselect filter for namespace selection. This enables users to select multiple specific namespaces, instead of only one or all, when fetching pages for deletion.
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. Thanks to Chlod and the Moderator Tools team for both of these improvements. [12]
The Editing Team is working on making it easier to populate citations from archive.org using the Citoid tool, the auto-filled citation generator. They are asking communities to add two parameters preemptively, archiveUrl and archiveDate, within the TemplateData for each citation template using Citoid. You can see an example of a change in a template, and a list of all relevant templates. [13]
Last week, all wikis had problems serving pages to logged-in users and some logged-out users for 30–45 minutes. This was caused by a database problem, and investigation is ongoing. [15]
View all 19 community-submitted tasks that were resolved last week. For example, a bug in the Add Link feature has been fixed. Previously, the list of sections which are excluded from Add Link was partially ignored in certain cases. [16][17]
Updates for technical contributors
Codex, the design system for Wikimedia, now has an early-stage implementation in PHP. It is available for general use in MediaWiki extensions and Toolforge apps through Composer, with use in MediaWiki core coming soon. More information is available in the documentation. Thanks to Doğu for the inspiration and many contributions to the library. [18]
Wikimedia REST API users, such as bot operators and tool maintainers, may be affected by ongoing upgrades. On December 4, the MediaWiki Interfaces team began rerouting page/revision metadata and rendered HTML content endpoints on testwiki from RESTbase to comparable MediaWiki REST API endpoints. The team encourages active users of these endpoints to verify their tool's behavior on testwiki and raise any concerns on the related Phabricator ticket before the end of the year, as they intend to roll out the same change across all Wikimedia projects in early January. These changes are part of the work to replace the outdated RESTBase system.
The 2024 Developer Satisfaction Survey is seeking the opinions of the Wikimedia developer community. Please take the survey if you have any role in developing software for the Wikimedia ecosystem. The survey is open until 3 January 2025, and has an associated privacy statement.
Is there a reason you went with raw html (ending the div early, font, etc.) rather than '''{{big|{{xtn|Arbitrators-elect (taking office 1 January 2025)}}}}''' as has been done in the past? I ask because the page has to be parsed by AmoryBot for the user highlighting pages. If there's gonna be a new format, nbd, I can update the bot script, but otherwise it tries to be strict. ~ Amory(u • t • c)11:51, 12 December 2024 (UTC)
@Amorymeltzer: That was just what was used in the example diff from 2014 that was linked on the clerk procedures page (which I'll update to a current example). Though I should have noticed that the html tags were mismatched. I've fixed my edit per your suggestion; please change it further if it's still wrong. SilverLocust💬12:08, 12 December 2024 (UTC)
file:FHM1.jpg: Based on the uploader's edits, their other uploads, and the filename, I concluded that the image was most likely taken from an issue of FHM magazine: in other words, that "{{self|GFDL|cc-by-sa-2.5,2.0,1.0}}" was blatantly false. That the license was bad. I observed that the image was not in use, and there was therefore no point in devising an FUR. Lastly, I noted that the uploader was last active in 2007, and was thus unlikely to respond to a request for further details.
File:LakeWade.JPG: This image was uploaded in 2008, to illustrate an article about a high school sports team that was speedy'd two days after creation. It's some kids standing on a sports field, taken from a weird angle. In the background you can see some adults, and some other kids sitting on a bench. Also there are trees. I transfer a lot of images to Commons. I assessed that this one would not be considered within scope on Commons, and that if it were imported to Commons, it would eventually be deleted from there as well, pursuant to a formal deletion request.
File:Muralb.jpg: "Photo of a mural in Illinois, where freedom of panorama does not apply to murals." Because the person who uploaded the image of the mural did so in order to add it to an article about a neighborhood in Chicago, which is in Illinois, I reasonably inferred that the mural was in Illinois. This means that it is subject to American law. Do you understand "freedom of panorama"? Barring significant changes to American law, this photo of a 2-dimensional artwork on public display in the United States was not, and could not be, properly licensed (unless any one of a variety of highly specific conditions, such as "the mural first went on display prior to 1 January 1929", or "the muralist died over 70 years ago", is true; however, as no provenance was supplied for the mural, we must assume that none of those conditions are true and that therefore, barring more information, the mural is still under copyright). As the photo is a derivative work of a nonfree artwork, it could only remain on enwiki with a proper Fair Use Rationale. Its purpose in the article from which I removed it was "being part of a gallery that illustrates various examples of Puerto Rican culture in a particular Chicago neighborhood". I assessed that it was not possible to create a valid FUR to enable the image to be kept on enwiki.
Kelly Xu: as best I recall, someone came on live help chat and wanted to know why that recently-created article was allowed to exist. I assessed the article and determined that, although it did cite several sources for its assertions of notability, none of those sources were at all reliable. As you can see from the edit summary in the deletion log, I explained why each source was not useful, and emphasized that once all these not-useful sources were eliminated, there was nothing left on which to base an article: notability was not asserted. There was no indication of importance. If you feel that using cryptic diglyphs in deletion logs is preferable to using detailed human-readable explanations, you are entitled to that opinion.
File:Dh logod.jpg: this was described as the logo of deathcore band Arsonists Get All the Girls. The uploader stated that it was "own work"; however, based on their edits, I feel it is unlikely that they are a member of AGAtG, and that instead, the statement is only valid insofar as the uploader was the one who extracted the image from the cover of the AGAtG album "The Game of Life". It is a derived work of a nonfree album cover (and is on the wrong side of the threshold of originality, as well). Thus, I concluded that the license was invalid and the image was nonfree. Furthermore, as best I can tell, only one of AGAtG's six albums used this image (it's not on their Facebook page, it's not on their Bandcamp page, it's not on the licensed t-shirts), which I assume is why the image isn't actually in use in the AGAtG article and hasn't been in years: I don't think it's actually their logo. Therefore, I concluded that there was no point in devising an FUR.
File:Esham1.jpg : a very small, low-resolution photo of rapper Esham Attica Smith, which has not been used in our article on Mr. Smith in well over a decade and a half. Edit summary on the upload indicated that it was taken from Mr. Smith's official website in 2006, which led me to conclude that it was highly unlikely to have been the uploader's own work, and thus that the licensing was equally unlikely to be valid. However, when compiling this reply to your question, I noticed that the uploader's username was that of the recording company founded by Mr. Smith and his brother. This new information has led me to conclude that we can reasonably assume the photo to be either the uploader's own work, or a work for hire produced by an employee or contractor of the uploader. Mea culpa, mea maxima culpa. As such, if you wish to restore that (very small, low-resolution, unused) image and then import it to Commons, I will have no objections, although I do ask that you first make sure to fill in proper metadata on the image and also rename it so that its name is at least 10 characters long (perhaps "Esham Smith ca 2006"?).
If you feel that it is important for you to restore any of the other images, or the article, so that you can then implement a full-length formal deletion discussion for each of them, rather than accepting the validity of my rationales for each of those deletions, then by all means, I urge you to do so.
If you have further questions about any of my deletions, please ask; part of the ethos of the Wikimedia movement is sharing our knowledge. DS (talk) 19:01, 16 December 2024 (UTC)
If "Dragonfly does not use the deletion rationales that I want him to" upsets you, I'm sorry to hear that. You can, as I said, restore any or all of the images and put them through full deletion debates. I will even participate in those debates if you notify me that you have begun them. I am always willing to explain my actions, and I am always willing to admit when I made a mistake (e.g., the photo of Mr. Smith); if you wish to audit my deletion log, go ahead. However, WP:IAR is still a guiding principle of this project: "If a rule prevents you from improving or maintaining Wikipedia, ignore it."
Are there any of the images which you feel should not have been deleted at all? If your answer is "no", then your situation resolves to "you have deleted images that I agree should have been deleted, but I do not approve of the reasons you provided in the edit summary". If your answer is "yes", I look forward to reading your explanation as to why.
Remember: process is important, but it is not all-important. Our overall goal, the one you and I share, is to make Wikipedia better. DS (talk) 16:20, 17 December 2024 (UTC)
Tech News: 2024-51
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
Interested in improving event management on your home wiki? The CampaignEvents extension offers organizers features like event registration management, event/wikiproject promotion, finding potential participants, and more - all directly on-wiki. If you are an organizer or think your community would benefit from this extension, start a discussion to enable it on your wiki today. To learn more about how to enable this extension on your wiki, visit the deployment status page.
Updates for editors
Users of the iOS Wikipedia App in Italy and Mexico on the Italian, Spanish, and English Wikipedias, can see a personalized Year in Review with insights based on their reading and editing history.
Users of the Android Wikipedia App in Sub-Saharan Africa and South Asia can see the new Rabbit Holes feature. This feature shows a suggested search term in the Search bar based on the current article being viewed, and a suggested reading list generated from the user’s last two visited articles.
The global reminder bot is now active and running on nearly 800 wikis. This service reminds most users holding temporary rights when they are about to expire, so that they can renew should they want to. See the technical details page for more information.
The next issue of Tech News will be sent out on 13 January 2025 because of the end of year holidays. Thank you to all of the translators, and people who submitted content or feedback, this year.
View all 27 community-submitted tasks that were resolved last week. For example, a bug was fixed in the Android Wikipedia App which had caused translatable SVG images to show the wrong language when they were tapped.
Updates for technical contributors
There is no new MediaWiki version next week. The next deployments will start on 14 January. [20]
SilverLocust, everything I said in my EFA nomination was true, and it is still holds. In accepting your nomination, you said you greatly admire me, and I want to put on the record that I greatly admire you. Your dedication to this experiment we call Wikipedia is admirable, but rivaled by the skill you bring to the task, and achieving the highest support percentage at EFA speaks for itself. You have been a great friend these past six months, and I look forward to continuing to clerk in the new year. At some point we should work on a SCOTUS article together (definitely after the current thing on our plate is in the rear-view mirror). Best to you and yours in the new year, and happy holidays! HouseBlaster (talk • he/they) 04:24, 22 December 2024 (UTC)
Happy Holidays
Merry Christmas and a Prosperous 2025!
Hello SilverLocust, may you be surrounded by peace, success and happiness on this seasonal occasion. Spread the WikiLove by wishing another user a Merry Christmas and a Happy New Year, whether it be someone you have had disagreements with in the past, a good friend, or just some random person. Sending you heartfelt and warm greetings for Christmas and New Year 2025. Happy editing, Abishe (talk) 22:26, 24 December 2024 (UTC)
Hello everyone, and welcome to the 26th issue of the Wikipedia Scripts++ Newsletter, covering all our favorite new and updated user scripts since 1 August 2024. At press time, over 94% of the world has legally fallen prey to the merry celebrations of "Christmas", and so shall you soon. It's been a quiet 4 months, and we hope to see you with way more new scripts next year. Happy holidays! Aaron Liu (talk) 05:06, 25 December 2024 (UTC)
Got anything good? Tell us about your new, improved, old, or messed-up script here!
Featured script
Very useful for changelist patrollers, DiffUndo, by Nardog, is this edition's featured script. Taking inspiration from WP:AutoWikiBrowser's double-click-to-undo feature, it adds an undo button to every line of every diff from "show changes", optimizing partial reverts with your favorite magic spell and nearly fulfilling m:Community Wishlist/Wishes/Partial revert undo.
Miscellaneous
Doğu/Adiutor, a recent WP:Twinkle/WP:RedWarn-like userscript that follows modern WMF UI design, is now an extension. However, its sole maintainer has left the project, which still awaits WMF mw:code stewardship (among some audits) to be installed on your favorite WMF wikis.
DannyS712, our former chief editor, has ascended to MediaWiki and the greener purpley pastures of PHP with commits creating Special:NamespaceInfo and the __EXPECTUNUSEDTEMPLATE__ magic word to exclude a template from Special:UnusedTemplates! I wonder if Wikipedia has a templaters' newsletter...
BilledMammal/Move+ needs updating to order list of pages handle lists of pages to move correctly regardless of the discussion's page, so that we may avoid repeating fiasco history.
Andrybak/Unsigned helper forks Anomie/unsignedhelper to add support for binary search, automatic edit summaries after generating the {{unsigned}} template, support for {{undated}}, and support for generating while syntax highlighting is on.
Polygnotus/Move+ updates BilledMammal's classic Move+ to add automattic watchlisting of all pages—except the target page(s)—changed while processing a move.
Just a reminder, when you delete an article or draft, please remember to check and delete the talk page as well. I just found three talk pages that were part of page deletions you recently did but you neglected to delete the talk pages. I've found it easiest to use Twinkle to delete pages as Twinkle will only delete talk pages of articles and drafts but also any redirects that exist. This makes things very easy. Thank you and have a great weekend. LizRead!Talk!04:08, 29 December 2024 (UTC)
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.
Christopher, evading a block is not allowed. As you noted, you are using a proxy to evade a block. To reiterate, posting contentious assertions about living people (two named, one unnamed) based on court filings or other primary, unpublished, self-published, or unreliable sources is a BLP policy violation. And please stop sending me messages in particular. SilverLocust💬19:13, 10 January 2025 (UTC)
Tech News: 2025-03
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) [21]
One new wiki has been created: a Wikipedia in Tigre (w:tig:) [22]
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. [23]
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. [24]
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. [25]
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. [26]
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. [27]
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. [28]
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.
This is an archive of past discussions with User:SilverLocust. 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.