This page has archives. Sections older than 30 days may be automatically archived by Lowercase sigmabot III when more than 4 sections are present.
Has this user made a silly mistake? Click on the trout to notify them!
••••🎄Merry Christmas🎄••••
"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 ..warm greetings.. for Christmas and New Year 2021."
JACKINTHEBOX • TALK is wishing you a MerryChristmas! This greeting (and season) promotes WikiLove and hopefully this note has made your day a little better. Spread the WikiLove by wishing another user a Merry Christmas, whether it be someone you have had disagreements with in the past, a good friend, or just some random person. Happy New Year!
Spread the cheer by adding {{subst:Xmas2}} to their talk page with a friendly message.
Don't take this too seriously. Someone just wants to let you know that you did something silly.
You have been trouted for: muddling locations with a shared name.
Your error was understandable, given that there are three places named Lukyanivka in Kyiv Oblast alone, and only one has an English Wikipedia article. There are two ways to avoid making this kind of mistake when editing Module:Russo-Ukrainian War detailed map:
See whether a Ukrainian version of the disambiguation page is available. If there isn't one linked at the side, machine-translate the name of the settlement and search for its disambiguation page on Ukrainian Wikipedia. By doing this, you would have found uk:Лук'янівка, which lists three locations in Kyiv Oblast.
More simply, you could have spotted a discrepancy in the location: the coordinates for Lukyanivka (neighborhood) are inside Kyiv, while the source said the village in question was tens of kilometers east of Brovary.
Hi again! I see you had some trouble with some of the locations in the ISW's most recent update. Personally, the way I try to avoid errors is to
Search on Google Maps for locations of the same name near the area being discussed;
By comparing the locations of search results against the location of the front lines on Template:Russo-Ukrainian War detailed map, it may be possible to determine which settlement is being talked about. Still, at this stage, it is best not to assume.
Copy Google's Ukrainian transliteration of the settlement's name from the bar on the left;
This should appear if you click on a settlement with the right name.
If the page is for a settlement, see if there is a disambiguation link at the top. (In-browser machine translation is useful here. Unfortunately, I do not believe Preferences>Gadgets>Appearance>Display links to disambiguation pages in orange is available on Ukrainian Wikipedia, but if a link is clicked, it should be clear whether its destination is a disambiguation page from the format.) If there is no link, you can be confident you have the right settlement; if there is a link, click it.
Filter out most settlements by looking only at those in the oblasts you are interested in;
Disambiguation pages generally group articles by their oblast.
Again, machine translation is useful here; alternatively, you can learn to recognise the Ukrainian Cyrillic for "Donetsk", "Luhansk", "Kherson" etc.
Out of the settlements which remain, use the maps/coordinates on their respective pages to judge whether they are in the correct location.
Incidentally, another thing to note is that in HTML, <ref name="foo"/> is shorthand for <ref name="foo"></ref>, so you can save yourself some typing there. Once again, thanks for your help! —AlphaMikeOmega (talk)16:56, 28 April 2022 (UTC)[reply]
I'd just like to bring up your recent edits regarding Blahodatne, and why I largely reverted them, without being constrained to an edit summary. Here's how I believe the claim got to the ISW's map:
7 June: Twitter user Ukraine War Map posts this, which says that Blahodatne was reported retaken, but does not cite a source;
8 June: This is picked up and relayed by Ukrainian military journalist Roman Bochkala here. He does not cite a source, but uses the same map image;
8 June: The ISW does not mention Blahodatne in its text, but to draw its map (which can only ever be approximate due to the fog of war), the ISW cites Bochkala's Telegram post (see here).
So overall, it doesn't appear well-sourced (unless perhaps we can find Twitter user Ukraine War Map's source). It's probably because of cases like this that the contributors who worked on the Syrian Civil War maps decided not to copy others' maps – a policy carried over to equivalent pages on the Russo-Ukrainian War. That said, the ISW's maps are still useful: it's just probably best to chase down the maps' claims to see if you can find the original source. —AlphaMikeOmega (talk)23:33, 10 June 2022 (UTC)[reply]
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) [1]
One new wiki has been created: a Wikipedia in Tigre (w:tig:) [2]
View all 35 community-submitted tasks that were resolved last week. For example, there was a bug with updating a user's edit-count after making a rollback edit, which is now fixed. [3]
Updates for technical contributors
Wikimedia REST API users, such as bot operators and tool maintainers, may be affected by ongoing upgrades. Starting the week of January 13, we will begin rerouting some page content endpoints from RESTbase to the newer MediaWiki REST API endpoints for all wiki projects. This change was previously available on testwiki and should not affect existing functionality, but active users of the impacted endpoints may raise issues directly to the MediaWiki Interfaces Team in Phabricator if they arise.
Toolforge tool maintainers can now share their feedback on Toolforge UI, an initiative to provide a web platform that allows creating and managing Toolforge tools through a graphic interface, in addition to existing command-line workflows. This project aims to streamline active maintainers’ tasks, as well as make registration and deployment processes more accessible for new tool creators. The initiative is still at a very early stage, and the Cloud Services team is in the process of collecting feedback from the Toolforge community to help shape the solution to their needs. Read more and share your thoughts about Toolforge UI.
For tool and library developers who use the OAuth system: The identity endpoint used for OAuth 1 and OAuth 2 returned a JSON object with an integer in its sub field, which was incorrect (the field must always be a string). This has been fixed; the fix will be deployed to Wikimedia wikis on the week of January 13. [4]
Many wikis currently use Cite CSS to render custom footnote markers in Parsoid output. Starting January 20 these rules will be disabled, but the developers ask you to not clean up your MediaWiki:Common.css until February 20 to avoid issues during the migration. Your wikis might experience some small changes to footnote markers in Visual Editor and when using experimental Parsoid read mode, but if there are changes these are expected to bring the rendering in line with the legacy parser output. [5]
You have accused me on being in an edit war even though I placed (extensively sourced) information where it should be. I have noticed the other editor has not received such a warning? He is the one that removed my edit, all while failing to provide a legitimate reason (he repeatedly accused me of citing social media, when I had cited the LA Times). So... if I revert somebody's edits for no reason, I'm edit warring. If somebody else reverts my edits, I'm edit warring? You wanna help me out with this logic? 141.154.49.21 (talk) 18:16, 19 January 2025 (UTC)[reply]
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Updates for editors
Administrators can mass-delete multiple pages created by a user or IP address using Extension:Nuke. It previously only allowed deletion of pages created in the last 30 days. It can now delete pages from the last 90 days, provided it is targeting a specific user or IP address. [6]
On wikis that use the Patrolled edits feature, when the rollback feature is used to revert an unpatrolled page revision, that revision will now be marked as "manually patrolled" instead of "autopatrolled", which is more accurate. Some editors that use filters on Recent Changes may need to update their filter settings. [7]
View all 31 community-submitted tasks that were resolved last week. For example, the Visual Editor's "Insert link" feature did not always suggest existing pages properly when an editor started typing, which has now been fixed.
Updates for technical contributors
The Structured Discussion extension (also known as Flow) is being progressively removed from the wikis. This extension is unmaintained and causes issues. It will be replaced by DiscussionTools, which is used on any regular talk page. The last group of wikis (Catalan Wikiquote, Wikimedia Finland, Goan Konkani Wikipedia, Kabyle Wikipedia, Portuguese Wikibooks, Wikimedia Sweden) will soon be contacted. If you have questions about this process, please ping Trizek (WMF) at your wiki. [8]
The latest quarterly Technical Community Newsletter is now available. This edition includes: updates about services from the Data Platform Engineering teams, information about Codex from the Design System team, and more.
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Weekly highlight
Patrollers and admins - what information or context about edits or users could help you to make patroller or admin decisions more quickly or easily? The Wikimedia Foundation wants to hear from you to help guide its upcoming annual plan. Please consider sharing your thoughts on this and 13 other questions to shape the technical direction for next year.
Updates for editors
iOS Wikipedia App users worldwide can now access a personalized Year in Review feature, which provides insights based on their reading and editing history on Wikipedia. This project is part of a broader effort to help welcome new readers as they discover and interact with encyclopedic content.
Edit patrollers now have a new feature available that can highlight potentially problematic new pages. When a page is created with the same title as a page which was previously deleted, a tag ('Recreated') will now be added, which users can filter for in Special:RecentChanges and Special:NewPages. [9]
Later this week, there will be a new warning for editors if they attempt to create a redirect that links to another redirect (a double redirect). The feature will recommend that they link directly to the second redirect's target page. Thanks to the user SomeRandomDeveloper for this improvement. [10]
Wikimedia wikis allow WebAuthn-based second factor checks (such as hardware tokens) during login, but the feature is fragile and has very few users. The MediaWiki Platform team is temporarily disabling adding new WebAuthn keys, to avoid interfering with the rollout of SUL3 (single user login version 3). Existing keys are unaffected. [11]
For developers that use the MediaWiki History dumps: The Data Platform Engineering team has added a couple of new fields to these dumps, to support the Temporary Accounts initiative. If you maintain software that reads those dumps, please review your code and the updated documentation, since the order of the fields in the row will change. There will also be one field rename: in the mediawiki_user_history dump, the anonymous field will be renamed to is_anonymous. The changes will take effect with the next release of the dumps in February. [12]
