Hi! Avishai11 (talk) 17:38, 19 November 2020 (UTC)
- click this button if you need any help first, it's great, and has lots of links!
Archives (Index) |
This page is archived by ClueBot III.
|
Requesting immediate archiving...
Tech News: 2024-45
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
- Stewards can now make global account blocks cause global autoblocks. This will assist stewards in preventing abuse from users who have been globally blocked. This includes preventing globally blocked temporary accounts from exiting their session or switching browsers to make subsequent edits for 24 hours. Previously, temporary accounts could exit their current session or switch browsers to continue editing. This is an anti-abuse tool improvement for the Temporary Accounts project. You can read more about the progress on key features for temporary accounts. [1]
- Wikis that have the CampaignEvents extension enabled can now use the Collaboration List feature. This list provides a new, easy way for contributors to learn about WikiProjects on their wikis. Thanks to the Campaign team for this work that is part of the 2024/25 annual plan. If you are interested in bringing the CampaignEvents extension to your wiki, you can follow these steps or you can reach out to User:Udehb-WMF for help.
- The text color for red links will be slightly changed later this week to improve their contrast in light mode. [2]
- View all 32 community-submitted tasks that were resolved last week. For example, on multilingual wikis, users can now hide translations from the WhatLinksHere special page.
Updates for technical contributors
- XML data dumps have been temporarily paused whilst a bug is investigated. [3]
In depth
- Temporary Accounts have been deployed to six wikis; thanks to the Trust and Safety Product team for this work, you can read about the deployment plans. Beginning next week, Temporary Accounts will also be enabled on seven other projects. If you are active on these wikis and need help migrating your tools, please reach out to User:Udehb-WMF for assistance.
- The latest quarterly Language and Internationalization newsletter is available. It includes: New languages supported in translatewiki or in MediaWiki; New keyboard input methods for some languages; details about recent and upcoming meetings, and more.
Meetings and events
- MediaWiki Users and Developers Conference Fall 2024 is happening in Vienna, Austria and online from 4 to 6 November 2024. The conference will feature discussions around the usage of MediaWiki software by and within companies in different industries and will inspire and onboard new users.
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
MediaWiki message delivery 20:47, 4 November 2024 (UTC)
Pending changes reviewer granted
Hello. Your account has been granted the "pending changes reviewer" userright, allowing you to review other users' edits on pages protected by pending changes. The list of articles awaiting review is located at Special:PendingChanges, while the list of articles that have pending changes protection turned on is located at Special:StablePages.
Being granted reviewer rights neither grants you status nor changes how you can edit articles. If you do not want this user right, you may ask any administrator to remove it for you at any time.
See also:
- Wikipedia:Reviewing pending changes, the guideline on reviewing
- Wikipedia:Reviewing pending changes#Requirements to accept an edit, when to accept an edit
Dr vulpes (Talk) 05:49, 6 November 2024 (UTC)
The Signpost: 6 November 2024
- From the editors: Editing Wikipedia should not be a crime
- In the media: An old scrimmage, politics and purported libel
- Special report: Wikipedia editors face litigation, censorship
- Traffic report: Twisted tricks or tempting treats?
Tech News: 2024-46
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
- On wikis with the Translate extension enabled, users will notice that the FuzzyBot will now automatically create translated versions of categories used on translated pages. [4]
- View all 29 community-submitted tasks that were resolved last week. For example, the submitted task to use the SecurePoll extension for English Wikipedia's special administrator election was resolved on time. [5]
Updates for technical contributors
- In
1.44.0-wmf-2
, the logic of Wikibase functiongetAllStatements
changed to behave likegetBestStatements
. Invoking the function now returns a copy of values which are immutable. [6] - Wikimedia REST API users, such as bot operators and tool maintainers, may be affected by ongoing upgrades. The API will be rerouting some page content endpoints from RESTbase to the newer MediaWiki REST API endpoints. The impacted endpoints include getting page/revision metadata and rendered HTML content. These changes will be available on testwiki later this week, with other projects to follow. This change should not affect existing functionality, but active users of the impacted endpoints should verify behavior on testwiki, and raise any concerns on the related Phabricator ticket.
In depth
- Admins and users of the Wikimedia projects where Automoderator is enabled can now monitor and evaluate important metrics related to Automoderator's actions. This Superset dashboard calculates and aggregates metrics about Automoderator's behaviour on the projects in which it is deployed. Thanks to the Moderator Tools team for this Dashboard; you can visit the documentation page for more information about this work. [7]
Meetings and events
- 21 November 2024 (8:00 UTC & 16:00 UTC) - Community call with Wikimedia Commons volunteers and stakeholders to help prioritize support efforts for 2025-2026 Fiscal Year. The theme of this call is how content should be organised on Wikimedia Commons.
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
MediaWiki message delivery 00:04, 12 November 2024 (UTC)
Thanks
Thank you for the barnstar. Iljhgtn (talk) 23:14, 14 November 2024 (UTC)
- @Iljhgtn you are very welcome - you totally deserve it!!! Avishai - @Avishai11 Avishai11 (talk) 23:18, 14 November 2024 (UTC)
- May I ask how you noticed? Iljhgtn (talk) 00:08, 15 November 2024 (UTC)
- @Iljhgtn I saw your profile on the Teahouse, and I clicked on it, and I clicked on Contributions! Great work! @Avishai11 Avishai11 (talk) 03:06, 15 November 2024 (UTC)
- May I ask how you noticed? Iljhgtn (talk) 00:08, 15 November 2024 (UTC)
Editing the Checkuser policy
Please do not edit the policy directly; take any proposed changes to the talk page. I will be removing your new shortcuts; they are not needed, and can be confusing. Risker (talk) 23:25, 14 November 2024 (UTC)
- [NOTE: Sorry for the super long message!]
- Hi @Risker,
- It's a pleasure meeting you. I hope you are doing great! I hope not to come off as rude, but did you actually read my edits? All of them were not policy changes. Check the history. The only other way you could mean "do not edit the policy directly" would be saying that I can't/shouldn't edit the policy, no matter what (even minor edits), without approval. That's not Wikipedia policy (which you should be very familiar with, sitting on the Arb Committee). There are so many other policies that statement would violate if so. For starters, a classic WP:OWNERSHIP, discouraging Wikipedia:BOLD, and not doing WP:GF. Plus, if we weren't allowed to make minor edits to policies, it would have a super high protection level. It doesn't; it has autoconfirmed.
- For "take any proposed changes to the talk page", we all know (and it literally says it when you edit the page): minor edits or non-policy changes (which I did) do NOT require consensus or "approval". Do you disagree?
- On "I will be removing your new shortcuts": this is a helpful edit that you decided, unilaterally, scrolling through Wikipedia, decided to revert, not thinking about for probably more than 2 minutes, decided to do, but it was very rude. I added helpful shortcuts! And there is room in the box. We have so many strange or "confusing" shortcuts, like Wikipedia:CHAR/A, that's very confusing. We have H:SPCHAR (which goes to WP:SEARCH). There was no reason for your removals.
- About "they are not needed": respectfully, that's actually not for you to decide. Sorry, but it isn't. Please actually cite ANY applicable policy. ANY. None, right?
- Regarding "and can be confusing": Do you call WP:CHE for WP:CHECKUSER CONFUSING? How is that confusing? Most editors would probably agree: it's not. If you need help understanding why it isn't confusing: the first 3 letters of CheckUser are: CHE. Hence WP:CHE. And you call WP:CHK NOT CONFUSING? What? WP:CHK is very confusing, much more than WP:CHE.
- Also, "shortcut not needed" is not a valid reason for deletion (as I would have expected you to know) per WP:SPEEDY. Your deletion was against all of Wikipedia's deletion policies. Let's go through CSD codes as well as the general and redirects deletion codes:
- "G1. Patent nonsense
- This applies to pages consisting entirely of incoherent text or gibberish with no meaningful content or history. It does not cover poor writing, partisan screeds, obscene remarks, implausible theories, vandalism, hoaxes, fictional material, coherent non-English material, or poorly translated material. In short, if it is understandable, G1 does not apply. It also does not apply to pages in the user namespace." There's no way this could be seen as that. The text was completely coherent and understandable.
- "G2. Test pages
- This applies to pages created to test editing or other Wikipedia functions. It applies to subpages of the Wikipedia Sandbox created as tests, but does not apply to the Sandbox itself, pages in the user namespace, or valid but unused or duplicate templates." These redirects were definitely NOT "tests".
- "G3. Pure vandalism and blatant hoaxes
- Further information: Wikipedia:Vandalism and Wikipedia:Do not create hoaxes
- This applies to pages that are blatant and obvious misinformation, blatant hoaxes (including files intended to misinform), and redirects created by cleanup from page-move vandalism. Articles about notable hoaxes are acceptable if it is clear that they are describing a hoax." Not possible.
- "G4. Recreation of a page that was deleted per a deletion discussion
- This applies to sufficiently identical copies, having any title, of a page deleted via its most recent deletion discussion. It excludes pages that are not substantially identical to the deleted version, and pages to which the reason for the deletion no longer applies. It excludes pages in userspace and draftspace where the content was converted to a draft for explicit improvement (but not simply to circumvent Wikipedia's deletion policy). This criterion also does not cover content undeleted via a deletion review, or that was only deleted via proposed deletion (including deletion discussions closed as "soft delete") or speedy deletion." Not possible.
- "G5. Creations by banned or blocked users, or in violation of general sanctions
- This applies to pages created by banned or blocked users in violation of their ban or block, as well as pages created in violation of general sanctions, and that have no substantial edits by others not subject to the ban or sanctions." I wasn't blocked or banned, was I?
- "G6. Technical deletions
- This is for uncontroversial maintenance, including:
- Deleting redirects or other pages which prevent page moves. Administrators should be aware of the proper procedures where a redirect or page holding up a page move has a non-trivial page history. An administrator who deletes a page that is blocking a move should ensure that the move is completed after deleting it." [Note: There was more criteria, but that would be much longer.] There was NO WAY this counts as "uncontroversial". No one would agree with that assessment.
- "G7. Author requests deletion
- If requested in good faith and provided that the only substantial content of the page was added by its author. For redirects created as a result of a page move, the mover must also have been the only substantive contributor to the pages before the move. If the sole author blanks a page other than a userspace page, a category page, or any type of talk page, this can be taken as a deletion request. If an author requests deletion of a page currently undergoing a deletion discussion, the closing admin may interpret that request as agreement with the deletion rationale." Question: Did I request deletion? Answer: No, I didn't.
- "G8. Pages dependent on a non-existent or deleted page
- Examples include, but are not limited to:
- Talk pages with no corresponding subject page
- Subpages with no parent page
- TimedText pages without a corresponding file (or when the file has been moved to Commons)
- Redirects to target pages that never existed or were deleted
- Editnotices of non-existent or unsalted deleted pages" Does WP:CHECKUSER still exist? Please, tell me.
- "G9. Office actions
- Main page: Wikipedia:Office actions
- In exceptional circumstances, the Wikimedia Foundation office reserves the right to speedy-delete a page. Deletions of this type must not be reversed without permission from the Foundation." Are you a WMF staff member? I don't believe so.
- "G10. Pages that disparage, threaten, intimidate, or harass their subject or some other entity, and serve no other purpose
- Examples of "attack pages" may include: libel, legal threats, material intended purely to harass or intimidate a person, or biographical material about a living person that is entirely negative in tone and unsourced. These pages should be speedily deleted when there is no neutral version in the page history to revert to. Both the page title and page content may be taken into account in assessing an attack. Articles about living people deleted under this criterion should not be restored or recreated by any editor until the biographical article standards are met. Other pages violating the Biographies of living persons policy might be eligible for deletion under the conditions stipulated at Wikipedia:Biographies of living persons § Summary deletion, creation prevention, and courtesy blanking, although in most cases a deletion discussion should be initiated instead.
- Redirects from plausible search terms are not eligible under this criterion. For example, a term used on the target page to refer to its subject is often a plausible redirect – see Wikipedia:RNEUTRAL." Definitely not an attack page, or an intimidation page. Also, see the very last sentence. Perfect for this situation, isn't it?
- "G11. Unambiguous advertising or promotion
- Main page: Wikipedia:Spam
- This applies to pages that are exclusively promotional and would need to be fundamentally rewritten to serve as encyclopedia articles, rather than advertisements. If a subject is notable and the content could plausibly be replaced with text written from a neutral point of view, this is preferable to deletion. Note: Any article that describes its subject from a neutral point of view does not qualify for this criterion. However, "promotion" does not necessarily mean commercial promotion: anything can be promoted, including a person, a non-commercial organization, a point of view, etc." Please answer: was the redirect advertising something? Or promoting something? NO.
- "G12. Unambiguous copyright infringement
- Main page:
- Wikipedia:Copyright violations
- This applies to text pages that contain copyrighted material with no credible assertion of public domain, fair use, or a compatible free license, where there is no non-infringing content on the page worth saving. Only if the history is unsalvageably corrupted should it be deleted in its entirety; earlier versions without infringement should be retained. For equivocal cases that do not meet speedy deletion criteria (such as where there is a dubious assertion of permission, where free-content edits overlie the infringement, or where there is only partial infringement or close paraphrasing), the article or the appropriate section should be blanked with {{subst:Copyvio|url=insert URL here}}, and the page should be listed at Wikipedia:Copyright problems. Please consult Wikipedia:Copyright violations for other instructions." Not applicable!
- "G13. Abandoned drafts and Articles for creation submissions
- Further information: Wikipedia:Articles for creation
- This applies to any pages that have not been edited by a human in six months found in:
- Draft namespace,
- Userspace with an {{AFC submission}} template
- Userspace with no content except the article wizard placeholder text." Was it in the draftspace?
- "G14. Unnecessary disambiguation pages
- This applies to the following disambiguation pages and redirects:
- Disambiguation pages that have titles ending in "(disambiguation)" but disambiguate only one extant Wikipedia page.
- Regardless of title, disambiguation pages that disambiguate zero extant Wikipedia pages.
- A redirect that ends in "(disambiguation)" but does not redirect to a disambiguation page or a page that performs a disambiguation-like function (such as set index articles or lists)." Not a disambiguation.
- SO, I've proved that there was absolutely no policy allowing the SPEEDY deletion of those redirects.
- Now, I'm going to prove that there was no reason for deletion even under the non-CSD criteria:
- "The redirect page makes it unreasonably difficult for users to locate similarly named articles via the search engine. For example, if the user searches for "New Articles", and is redirected to a disambiguation page for "Articles", it would take much longer to get to the newly added articles on Wikipedia." Not applicable.
- "The redirect might cause confusion. For example, if "Adam B. Smith" was redirected to "Andrew B. Smith", because Andrew was accidentally called Adam in one source, this could cause confusion with the article on Adam Smith, so the redirect should be deleted." Nope.
- "The redirect is offensive or abusive, such as redirecting "Joe Bloggs is a Loser" to "Joe Bloggs" (unless "Joe Bloggs is a Loser" is legitimately discussed in the article), or "Joe Bloggs" to "Loser". (Speedy deletion criterion G10 and G3 may apply.) See also § Neutrality of redirects." Were the redirects offensive to you? Or to anyone?
- "The redirect constitutes self-promotion or spam. (Speedy deletion criterion G11 may apply.)" NO.
- "The redirect makes no sense, such as redirecting "Apple" to "Orange". (Speedy deletion criterion G1 may apply.)" I'm pretty sure "CHE" to "CHECKUSER" makes perfect sense.
- "It is a cross-namespace redirect out of article space, such as one pointing into the User or Wikipedia namespace. The major exception to this rule are the pseudo-namespace shortcut redirects, which technically are in the main article space. Some long-standing cross-namespace redirects are also kept because of their long-standing history and potential usefulness. "MOS:" redirects, for example, were an exception to this rule until they became their own namespace in 2024." Were the redirects pointing to the article space?
- "If the redirect is broken, meaning it redirects to an article that does not exist, it can be immediately deleted under speedy deletion criterion G8. You should check that there is not an alternative place it could be appropriately redirected to first and that it has not become broken through vandalism." I don't remember the direct being broken, do you?
- "If the redirect is a novel or very obscure synonym for an article name that is not mentioned in the target, it is unlikely to be useful. In particular, redirects in a language other than English to a page whose subject is unrelated to that language (or a culture that speaks that language) should generally not be created. (Implausible typos or misnomers are candidates for speedy deletion criterion R3, if recently created.)" Not a synonym. Or in another language. Or an impossible typo!
- "If the target article needs to be moved to the redirect title, but the redirect has been edited before and has a history of its own, then the title needs to be freed up to make way for the move. If the move is uncontroversial, tag the redirect for G6 speedy deletion, or alternatively (with the
suppressredirect
user right; available to page movers and admins), perform a round-robin move. If not, take the article to Requested moves." Not applicable. - "If the redirect could plausibly be expanded into an article, and the target article contains virtually no information on the subject." Could it have been?
- Now, we've determined you had no right to delete the redirects, remove them from the list of shortcuts, and to use the edit summary(s) so improperly.
- I sincerely hope we can find a solution together before something else happens. I really don't want to get anyone else involved in this. I actually don't, that wasn't a threat, I swear. But I will if this isn't solved soon, we may need to see a third-party(s). I look forward to your reading your response soon. I hope you have a great rest of your day!
- Warm regards,
- Avishai
- @Avishai11
- Avishai11 (talk) 21:46, 15 November 2024 (UTC)
I am sure you mean well, Avishai11. The bottom line is that you are not in a position to understand the policies you are trying to edit. That is okay, you simply haven't been here long enough to know that the CheckUser policy has been carefully crafted over almost 20 years to read the way that it is. The policy doesn't really apply to you, except in that you could request that a checkuser look at a suspected sockpuppet that you've come across. Over that nearly 20 years of the policy's existence, many editors who are not checkusers or do not have sufficient experience have tried to "improve" it, only to be promptly reverted because their seemingly minor changes have definitely impacted the content and effect of the policy. This is actually common to a lot of other policies, as well. It is perfectly reasonable to suggest even minor modifications to a policy on the talk page of the policy. What some people consider minor edits turn out to be massively changing to the meaning of a policy. It is expected by the community that only very experienced editors who work with a particular policy regularly will make even minor changes, and often even experienced editors will discuss minor changes on the talk page of the policy. An editor with 600 live edits is not the best person to be editing policy.
The shortcuts and redirects you are suggesting on various pages are not particularly plausible, and in some cases are quite problematic due to historical reasons of which you are not aware. Deleting the redirect pages is housekeeping (G6); the shortcuts aren't appropriate for use in the places to which you have redirected, so the redirect pages are no longer needed and could potentially prevent someone else from using that redirect for something more plausible.
I suggest you spend the next year editing content and applying the existing policies before you start trying to reword policies to your preferred form. Try to get your percentage of edits to content higher than your percentage of edits to any other namespace; the way to understand Wikipedia is to edit its content. Perhaps you might want to subscribe to SuggestBot to get ideas on articles you can edit. Risker (talk) 22:17, 15 November 2024 (UTC)
- @Risker: Thank you for your faith in me. That might not sound right, sorry - I genuinely am thankful that you aren't a mean person! Thanks! I am also so sorry for making you read all of that. However, I still have many issues with your message. "The bottom line is that you are not in a position to understand the policies you are trying to edit." First of all, I fully understand the CheckUser policy and most other Wikipedia policies (that aren't extremely technical, such as specifically the steps to delete pages or how to build and publish bots, nor do I need to) don't try to gaslight me (respectfully). Secondly, I wasn't editing the policy's CONTENT. However, if I'm missing the point, I'm sorry. I've been here, learning, for over 4 1/2 years. There's still things for me to learn; everyone can learn new things. I did know that the CheckUser policy was created in 2005, around 19 years ago. I could say that off of the top of my head. You are correct in that the CheckUser policy does NOT currently apply to me (except that I could request a CheckUser to investigate a suspected sockpuppet). Also, if you look at what the CheckUser policy looked like in 2005, or even 2008, or 2011, or even in 2020 (there were still HUGE changes from 2020). I consider myself a semi-experienced editor (not as much as you, of course!), and I used to be (until around 20 hours ago) a mentor in Wikipedia's Mentorship Program. I was qualified then, and I promptly (except when I had a family issue and needed to take a 2 week break this summer) answered all of their questions, and helped them. Some of my (former) mentors even have 400, 500, and even 700 edits! Even more than me! They have created many new articles with my help. Do you think I should be a mentor? Back to the main point, as of right now, my main issues aren't with your reverts of the shortcuts, my problem is with your deletion of the shortcuts. I actually was writing a message to answer a question at the Help Desk when I got the notice that it was deleted from my watchlist. I USE it, and I think it would be helpful for some people, at least. So, I was wondering if you could "revive" the shortcuts. I also just want to say that I really, truly appreciate you taking the time to explain your side to me. Also, I am unaware of your "historical reasons". What does that even mean? From what I saw, nothing was created on those pages. If I'm wrong, please explain. Plus, if someone DID want to create something with that redirect, they would be welcome to do so. I would like to use the redirects for something useful, too. And how exactly aren't they appropriate? Please, explain. Now onto your last paragraph. I have spent many years editing and learning. 4 1/2 years, to be exact. You've definitely had a LOT more experience than me, but I have a strong amount (not enough to do an RFA, but I don't want that right now, I know I need to learn more myself). Also, I actually enjoy working "behind the scenes" as well as on the "front-end". It just so happens I prefer helping other people edit. That's ok; many admins and editors prefer this as well. I like keeping Wikipedia "tidy and organized". I look forward to your reply. @Avishai11 Avishai11 (talk) 01:17, 17 November 2024 (UTC)
- @Risker: Just checking in, did you read this? Best, @Avishai11 Avishai11 (talk) 01:47, 19 November 2024 (UTC)
- Yes, I saw it, Avishai11. I am kind of at a loss that someone who had 42 edits over 4 months in 2020-21, then two years without a single edit, then 564 edits this year (which included a two month break) really wants to claim 4-1/2 years' experience editing. I just don't know what to say to that at all. What I do know is that when I look at Pinhoe railway station, you deliberately ignored the hatnote that says "use dd/mm/yy dates", which is the usual standard for articles involving British topics, and completely changed the dating protocol to "mm/dd/yy" which is the usual standard for American topics. It would be nice if you returned that to the correct format. Incidentally, "station master" is the normal usage; "stationmaster" is a secondary way of spelling things. In looking through your contributions, I can see that you have tried your hand at a lot of things: categorization, article deficiency tagging, some PRODs, and of course a few other things, with mixed feedback or results. It's normal that it takes a while for an editor to find their niche. But you're doing a lot of what we could call "maintenance work" without doing much content improvement. No, I don't expect you to be writing fully-fledged articles; I admire your restraint in that. But I'd expect to see you doing some of the tasks that are recommended by the Growth Team as good tasks for low-experience editors. I think you would be familiar with them, as you had previously volunteered as a Growth Team mentor. The irony is that I still do several of those very tasks even now, almost 20 years after I created my account. It is a good way to keep in touch with the real purpose of Wikipedia, which is its content. I really urge you to try out some of those tasks, because it will get you better rooted into what we really do here. (At less than 700 edits, you are a low experience editor, no matter when you created your account. It's not a slight. The majority of Wikipedia accounts have fewer than 100 edits, often spread out over a decade or more.)
I won't be reviving the shortcuts; it's very bad when every user feels empowered to add their own favourite ways of getting to a page, because then we'd have hundreds, if not thousands, of shortcuts to every Wikipedia-space page. Instead, make your case for the shortcut on the talk page of the page to which you want to attach it. This is a place where others in the community can also chime in, and a consensus can be reached. Lots of people have a subpage in their userspace with links to pages they find useful, or alternately they just keep them on their userpage.
I know it may sound a bit rich that I'm urging you to work on content when I've done so little in recent times. I was, however, "seconded" to a global committee for 2.5 years, and have only come "home" to English Wikipedia in the last couple of months. My first priority was taking care of a very large backlog in the checkuser/administrator area. I'm just now really starting to sink my teeth back into content. I'm starting the way that I often recommend to new editors: just keep hitting "random article", reading each one, and making minor improvements if needed. Eventually, we stumble into an article that needs more serious work, whether copy-editing or improving references or rewriting entirely. I encourage you to keep working on the encyclopedia. Risker (talk) 04:49, 19 November 2024 (UTC)
- Yes, I saw it, Avishai11. I am kind of at a loss that someone who had 42 edits over 4 months in 2020-21, then two years without a single edit, then 564 edits this year (which included a two month break) really wants to claim 4-1/2 years' experience editing. I just don't know what to say to that at all. What I do know is that when I look at Pinhoe railway station, you deliberately ignored the hatnote that says "use dd/mm/yy dates", which is the usual standard for articles involving British topics, and completely changed the dating protocol to "mm/dd/yy" which is the usual standard for American topics. It would be nice if you returned that to the correct format. Incidentally, "station master" is the normal usage; "stationmaster" is a secondary way of spelling things. In looking through your contributions, I can see that you have tried your hand at a lot of things: categorization, article deficiency tagging, some PRODs, and of course a few other things, with mixed feedback or results. It's normal that it takes a while for an editor to find their niche. But you're doing a lot of what we could call "maintenance work" without doing much content improvement. No, I don't expect you to be writing fully-fledged articles; I admire your restraint in that. But I'd expect to see you doing some of the tasks that are recommended by the Growth Team as good tasks for low-experience editors. I think you would be familiar with them, as you had previously volunteered as a Growth Team mentor. The irony is that I still do several of those very tasks even now, almost 20 years after I created my account. It is a good way to keep in touch with the real purpose of Wikipedia, which is its content. I really urge you to try out some of those tasks, because it will get you better rooted into what we really do here. (At less than 700 edits, you are a low experience editor, no matter when you created your account. It's not a slight. The majority of Wikipedia accounts have fewer than 100 edits, often spread out over a decade or more.)
- @Risker: Just checking in, did you read this? Best, @Avishai11 Avishai11 (talk) 01:47, 19 November 2024 (UTC)
Speedy deletion nomination of Wikipedia:!!!
A tag has been placed on Wikipedia:!!! requesting that it be speedily deleted from Wikipedia. This has been done under section R3 of the criteria for speedy deletion, because it is a recently created redirect from an implausible typo or misnomer, or other unlikely search term.
If you think this page should not be deleted for this reason, you may contest the nomination by visiting the page and clicking the button labelled "Contest this speedy deletion". This will give you the opportunity to explain why you believe the page should not be deleted. However, be aware that once a page is tagged for speedy deletion, it may be deleted without delay. Please do not remove the speedy deletion tag from the page yourself, but do not hesitate to add information in line with Wikipedia's policies and guidelines. Bbb23 (talk) 22:19, 15 November 2024 (UTC)
Mentor
I've removed you from the list of mentors. You are insufficiently experienced to be a mentor, and you do not meet the criteria.--Bbb23 (talk) 22:42, 15 November 2024 (UTC)
Speedy deletion nomination of Wikipedia:BUTTON
A tag has been placed on Wikipedia:BUTTON requesting that it be speedily deleted from Wikipedia. This has been done under section R3 of the criteria for speedy deletion, because it is a recently created redirect from an implausible typo or misnomer, or other unlikely search term.
If you think this page should not be deleted for this reason, you may contest the nomination by visiting the page and clicking the button labelled "Contest this speedy deletion". This will give you the opportunity to explain why you believe the page should not be deleted. However, be aware that once a page is tagged for speedy deletion, it may be deleted without delay. Please do not remove the speedy deletion tag from the page yourself, but do not hesitate to add information in line with Wikipedia's policies and guidelines. Bbb23 (talk) 22:43, 15 November 2024 (UTC)
- You're making things worse for yourself. I just deleted the MfD you created. If you wish to contest the speedy deletion, nominating it for deletion and then opposing your own nomination is disruptive.--Bbb23 (talk) 23:41, 15 November 2024 (UTC)
Speedy deletion nomination of Wikipedia:HEBU
A tag has been placed on Wikipedia:HEBU requesting that it be speedily deleted from Wikipedia. This has been done under section R3 of the criteria for speedy deletion, because it is a recently created redirect from an implausible typo or misnomer, or other unlikely search term.
If you think this page should not be deleted for this reason, you may contest the nomination by visiting the page and clicking the button labelled "Contest this speedy deletion". This will give you the opportunity to explain why you believe the page should not be deleted. However, be aware that once a page is tagged for speedy deletion, it may be deleted without delay. Please do not remove the speedy deletion tag from the page yourself, but do not hesitate to add information in line with Wikipedia's policies and guidelines. Bbb23 (talk) 22:44, 15 November 2024 (UTC)
The Signpost: 18 November 2024
ArbCom 2024 Elections voter message
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.
If you wish to participate in the 2024 election, please review the candidates and submit your choices on the voting page. If you no longer wish to receive these messages, you may add {{NoACEMM}}
to your user talk page. MediaWiki message delivery (talk) 00:46, 19 November 2024 (UTC)
Tech News: 2024-47
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. [8]
- 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. [9]
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. [10][11]
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.
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
MediaWiki message delivery 01:57, 19 November 2024 (UTC)
Wikipedia translation of the week: 2024-48
Please be bold and help translate this article!
Wang Su-bok was a singer from North Korea, who was the most popular singer in Japanese-occupied Korea in 1935. She was credited as a ground-breaking female artist, whose work led the way for the modern K-pop phenomenon.
(Please update the interwiki links on Wikidata of your language version of the article after each week's translation is finished so that all languages are linked to each other.)
About · Nominate/Review · Subscribe/Unsubscribe · Global message delivery
--MediaWiki message delivery (talk) 01:57, 25 November 2024 (UTC)
Tech News: 2024-48
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 andCtrl
+I
for italics. A full list of all six shortcuts is available. Thanks to SD0001 for this improvement. [12] - 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).
- View all 25 community-submitted tasks that were resolved last week. For example, a user creating a new AbuseFilter can now only set the filter to "protected" if it includes a protected variable.
Updates for technical contributors
- 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. [13]
- 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. [14]
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.
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, 25 November 2024 (UTC)
Wikipedia translation of the week: 2024-49
Please be bold and help translate this article!
Storm Filomena was an extratropical cyclone in early January 2021 that was most notable for bringing unusually heavy snowfall to parts of Spain, with Madrid recording its heaviest snowfall in over a century, and with Portugal being hit less severely. The eighth named storm of the 2020–21 European windstorm season, Filomena formed over the Atlantic Ocean close to the Canary Islands on 7 January, subsequently taking a slow track north-eastwards towards the Iberian Peninsula and then eastwards across the Mediterranean Sea.
(Please update the interwiki links on Wikidata of your language version of the article after each week's translation is finished so that all languages are linked to each other.)
About · Nominate/Review · Subscribe/Unsubscribe · Global message delivery
--MediaWiki message delivery (talk) 02:48, 2 December 2024 (UTC)
Tech News: 2024-49
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
- Two new parser functions were added this week. The
{{#interwikilink}}
function adds an interwiki link and the{{#interlanguagelink}}
function adds an interlanguage link. These parser functions are useful on wikis where namespaces conflict with interwiki prefixes. For example, links beginning withMOS:
on English Wikipedia conflict with themos
language code prefix of Mooré Wikipedia. - 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. [15]
- 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). [16]
- 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. [17]
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.
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
MediaWiki message delivery 22:20, 2 December 2024 (UTC)
Administrators' newsletter – December 2024
News and updates for administrators from the past month (November 2024).
Interface administrator changes
- 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.
- 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 arbitration case Yasuke (formerly titled Backlash to diversity and inclusion) has been closed.
- An arbitration case titled Palestine-Israel articles 5 has been opened. Evidence submissions in this case will close on 14 December.
Wikipedia translation of the week: 2024-50
Please be bold and help translate this article!
Syrian literature is modern fiction written or orally performed in Arabic by writers from Syria since the independence of the Syrian Arab Republic in 1946. It is part of the historically and geographically wider Arabic literature. The modern states of Syria, Lebanon, Jordan, Israel as well as the Palestinian autonomous areas only came into being in the mid-20th century. Therefore, Syrian literature has since been referred to by literary scholarship as the national literature of the Syrian Arab Republic, as well as the works created in Arabic by Syrian writers in the diaspora. This literature has been influenced by the country's political history, the literature of other Arabic-speaking countries and, especially in its early days, by French literature.
(Please update the interwiki links on Wikidata of your language version of the article after each week's translation is finished so that all languages are linked to each other.)
About · Nominate/Review · Subscribe/Unsubscribe · Global message delivery
--MediaWiki message delivery (talk) 01:59, 9 December 2024 (UTC)
Tech News: 2024-50
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
- 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. [18] - 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. [19]
- 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
andarchiveDate
, 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. [20] - One new wiki has been created: a Wikivoyage in Indonesian (
voy:id:
) [21] - 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. [22]
- 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. [23][24]
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. [25]
- 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.
- There is no new MediaWiki version this week. [26]
Meetings and events
- The next meeting in the series of Wikimedia Foundation discussions with the Wikimedia Commons community will take place on December 12 at 8:00 UTC and at 16:00 UTC. The topic of this call is new media and new contributors. Contributors from all wikis are welcome to attend.
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
MediaWiki message delivery 22:13, 9 December 2024 (UTC)
The Signpost: 12 December 2024
- News and notes: Arbitrator election concludes
- Arbitration report: Palestine-Israel articles 5
- Disinformation report: Sex, power, and money revisited
- Op-ed: On the backrooms by Tamzin
- In the media: Like the BBC, often useful but not impartial
- Traffic report: Something Wicked for almost everybody
Wikipedia translation of the week: 2024-51
Please be bold and help translate this article!
The Mars ocean theory states that nearly a third of the surface of Mars was covered by an ocean of liquid water early in the planet's geologic history. This primordial ocean, dubbed Paleo-Ocean or Oceanus Borealis (/oʊˈsiːənəs ˌbɒriˈælɪs/ oh-SEE-ə-nəs BORR-ee-AL-iss), would have filled the basin Vastitas Borealis in the northern hemisphere, a region that lies 4–5 km (2.5–3 miles) below the mean planetary elevation, at a time period of approximately 4.1–3.8 billion years ago. Evidence for this ocean includes geographic features resembling ancient shorelines, and the chemical properties of the Martian soil and atmosphere
(Please update the interwiki links on Wikidata of your language version of the article after each week's translation is finished so that all languages are linked to each other.)
About · Nominate/Review · Subscribe/Unsubscribe · Global message delivery
--MediaWiki message delivery (talk) 01:45, 16 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. [27]
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
MediaWiki message delivery 22:22, 16 December 2024 (UTC)
New pages patrol January 2025 Backlog drive
January 2025 Backlog Drive | New pages patrol | |
| |
You're receiving this message because you are a new page patroller. To opt-out of future mailings, please remove yourself here. |
MediaWiki message delivery (talk) 01:52, 18 December 2024 (UTC)
Wikipedia translation of the week: 2024-52
Please be bold and help translate this article!
In August 2023, major floods occurred in large part of Slovenia and neighbouring areas of Austria and Croatia due to heavy rain. Amongst others, the level of rivers Sava, Mur and Drava was exceptionally high. Several settlements and transport links in Slovene Littoral, Upper Carniola and Slovenian Carinthia were flooded. Due to the amount of rain, the streams in Idrija, Cerkno and Škofja Loka Hills overflowed.
(Please update the interwiki links on Wikidata of your language version of the article after each week's translation is finished so that all languages are linked to each other.)
About · Nominate/Review · Subscribe/Unsubscribe · Global message delivery
MediaWiki message delivery (talk) 02:55, 23 December 2024 (UTC)
The Signpost: 24 December 2024
- From the archives: Where to draw the line in reporting?
- Recent research: "Wikipedia editors are quite prosocial", but those motivated by "social image" may put quantity over quality
- Gallery: A feast of holidays and carols
- Traffic report: Was a long and dark December
Upcoming expiry of your reviewer right
Hi, this is an automated reminder as part of Global reminder bot to let you know that your permission "reviewer" (Pending changes reviewers) will expire on 00:00, 4 January 2025 (UTC). For most rights, you will need to renew at WP:PERM, unless you have been told otherwise when your right was approved. To opt out of user right expiry notifications, add yourself to m:Global reminder bot/Exclusion. Leaderbot (talk) 19:42, 28 December 2024 (UTC)
Wikipedia translation of the week: 2025-01
Please be bold and help translate this article!
The Uganda Railways Corporation (URC) is the parastatal railway of Uganda. It was formed after the breakup of the East African Railways Corporation (EARC) in 1977 when it took over the Ugandan part of the East African railways.
(Please update the interwiki links on Wikidata of your language version of the article after each week's translation is finished so that all languages are linked to each other.)
About · Nominate/Review · Subscribe/Unsubscribe · Global message delivery
MediaWiki message delivery (talk) 02:37, 30 December 2024 (UTC)
Welcome to the 2025 WikiCup!
Happy New Year and Happy New WikiCup! The 2025 competition has just begun and all article creators, expanders, improvers and reviewers are welcome to take part. Even if you are a novice editor, we hope the WikiCup will give you a chance to improve your editing skills as you go. If you have already signed up, your submissions page can be found here. If you have not yet signed up, you can add your name here and the judges will set up your submissions page ready for you to take part. Any questions on the scoring, rules or anything else should be directed to one of the judges, or posted to the WikiCup talk page.
For the 2025 WikiCup, we've implemented several changes to the scoring system. The highest-ranking contestants will now receive tournament points at the end of each round, and final rankings are decided by the number of tournament points each contestant has. If you're busy and can't sign up in January, don't worry: Signups are now open throughout the year. To make things fairer for latecomers, the lowest-scoring contestants will no longer be eliminated at the end of each round.
The first round will end on 26 February. The judges for the WikiCup this year are: Cwmhiraeth (talk · contribs · email), Epicgenius (talk · contribs · email), Frostly (talk · contribs · email), Guerillero (talk · contribs · email) and Lee Vilenski (talk · contribs · email). Good luck! If you wish to start or stop receiving this newsletter, please feel free to add or remove your name from Wikipedia:WikiCup/Newsletter/Send. MediaWiki message delivery (talk) 00:13, 1 January 2025 (UTC)
Administrators' newsletter – January 2025
News and updates for administrators from the past month (December 2024).
- Following an RFC, Wikipedia:Notability (species) was adopted as a subject-specific notability guideline.
- 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.
- 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.
- Following the 2024 Arbitration Committee elections, the following editors have been elected to the Arbitration Committee: CaptainEek, Daniel, Elli, KrakatoaKatie, Liz, Primefac, ScottishFinnishRadish, Theleekycauldron, Worm That Turned.
- A New Pages Patrol backlog drive is happening in January 2025 to reduce the number of unreviewed articles and redirects in the new pages feed. Sign up here to participate!
Wikipedia translation of the week: 2025-02
Please be bold and help translate this article!
From 1942 to 1949, Canada forcibly relocated and incarcerated over 22,000 Japanese Canadians—comprising over 90% of the total Japanese Canadian population—from British Columbia in the name of "national security". The majority were Canadian citizens by birth and were targeted based on their ancestry. This decision followed the events of the Japanese Empire's war in the Pacific against the Western Allies, such as the invasion of Hong Kong, the attack on Pearl Harbor in Hawaii, and the Fall of Singapore which led to the Canadian declaration of war on Japan during World War II. Similar to the actions taken against Japanese Americans in neighbouring United States, this forced relocation subjected many Japanese Canadians to government-enforced curfews and interrogations, job and property losses, and forced repatriation to Japan
(Please update the interwiki links on Wikidata of your language version of the article after each week's translation is finished so that all languages are linked to each other.)
About · Nominate/Review · Subscribe/Unsubscribe · Global message delivery
--MediaWiki message delivery (talk) 03:56, 6 January 2025 (UTC)
Wikipedia translation of the week: 2025-03
Please be bold and help translate this article!
Christmas seals are adhesive labels that are similar in appearance to postage stamps that are sold then affixed to mail during the Christmas season to raise funds and awareness for charitable programs. Christmas seals have become particularly associated with lung diseases such as tuberculosis, and with child welfare in general. They were first issued in Denmark beginning in 1904, with Sweden and Iceland following with issues that same year. Thereafter the use of Christmas seals proved to be popular and spread quickly around the world, with 130 countries producing their own issues.
(Please update the interwiki links on Wikidata of your language version of the article after each week's translation is finished so that all languages are linked to each other.)
About · Nominate/Review · Subscribe/Unsubscribe · Global message delivery
--MediaWiki message delivery (talk) 02:24, 13 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) [28] - One new wiki has been created: a Wikipedia in Tigre (
w:tig:
) [29] - 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. [30]
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. [31] - 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. [32]
Meetings and events
- The next meeting in the series of Wikimedia Foundation Community Conversations with the Wikimedia Commons community will take place on January 15 at 8:00 UTC and at 16:00 UTC. The topic of this call is defining the priorities in tool investment for Commons. Contributors from all wikis, especially users who are maintaining tools for Commons, are welcome to attend.
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
MediaWiki message delivery 01:39, 14 January 2025 (UTC)
The Signpost: 15 January 2025
- From the editors: Looking back, looking forward
- Traffic report: The most viewed articles of 2024
- In the media: Will you be targeted?
- Technology report: New Calculator template brings interactivity at last
- Opinion: Reflections one score hence
- Serendipity: What we've left behind, and where we want to go next
- Arbitration report: Analyzing commonalities of some contentious topics
- Humour: How to make friends on Wikipedia
Wikipedia translation of the week: 2025-04
(it:Scontri del Nagorno Karabakh del 2010) (tr:2010 Dağlık Karabağ çatışmaları)
Please be bold and help translate this article!
The 2010 Nahorno karabakh war were a series of exchanges of gunfire that took place on February 18 on the line of contact dividing Azerbaijani and the Karabakh Armenian military forces. Azerbaijan accused the Armenian forces of firing on the Azerbaijani positions near Tap Qaraqoyunlu, Qızıloba, Qapanlı, Yusifcanlı and Cavahirli villages, as well as in uplands of Agdam Rayon with small arms fire including snipers. As a result, three Azerbaijani soldiers were killed and one wounded.
(Please update the interwiki links on Wikidata of your language version of the article after each week's translation is finished so that all languages are linked to each other.)
About · Nominate/Review · Subscribe/Unsubscribe · Global message delivery
--MediaWiki message delivery (talk) 01:20, 20 January 2025 (UTC)
Tech News: 2025-04
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. [33]
- 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. [34]
- 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. [35]
- 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.
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
MediaWiki message delivery 01:34, 21 January 2025 (UTC)
Wikipedia translation of the week: 2025-05
Please be bold and help translate this article!
Jinnah's Birthday, officially Quaid-e-Azam Day and sometimes known as Quaid Day, is a public holiday in Pakistan observed annually on 25 December to celebrate the birthday of the founder of Pakistan, Muhammad Ali Jinnah, known as Quaid-i-Azam ("Great Leader"). A major holiday, commemorations for Jinnah began during his lifetime in 1942, and have continued ever since. The event is primarily observed by the government and the citizens of the country where the national flag is hoisted at major architectural structures such as private and public buildings, particularly at the top of Quaid-e-Azam House in Karachi.
(Please update the interwiki links on Wikidata of your language version of the article after each week's translation is finished so that all languages are linked to each other.)
About · Nominate/Review · Subscribe/Unsubscribe · Global message delivery
--MediaWiki message delivery (talk) 01:30, 27 January 2025 (UTC)
Tech News: 2025-05
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. [36]
- 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. [37]
- 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. [38]
- View all 30 community-submitted tasks that were resolved last week.
Updates for technical contributors
- 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, theanonymous
field will be renamed tois_anonymous
. The changes will take effect with the next release of the dumps in February. [39]
Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.
MediaWiki message delivery 22:12, 27 January 2025 (UTC)
Wikipedia translation of the week: 2025-06
Please be bold and help translate this article!
The French conquest of Corsica was a successful expedition by French forces of the Kingdom of France under Comte de Vaux, against Corsican forces under Pasquale Paoli of the Corsican Republic. The expedition was launched in May 1768, in the aftermath of the Seven Years' War.
(Please update the interwiki links on Wikidata of your language version of the article after each week's translation is finished so that all languages are linked to each other.)
About · Nominate/Review · Subscribe/Unsubscribe · Global message delivery
--MediaWiki message delivery (talk) 12:20, 3 February 2025 (UTC)