User talk:Firestar464

••••🎄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."

Happy editing,
User:245CMR

A Joyous Yuletide to You!

JACKINTHEBOX • ^TALK is wishing you a Merry Christmas! 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.

Trouted

Whack!

You've been whacked with a wet trout.

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:

1. 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.
2. 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.

Regardless, thank you for your contributions. —AlphaMikeOmega (talk) 18:26, 31 March 2022 (UTC)

slaaaaaap...thanks for the advice Firestar464 (talk) 02:29, 1 April 2022 (UTC)

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

1. 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.
2. 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.
3. Go to the Ukrainian Wikipedia article with the same name as was copied;
   • 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.
4. 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.
5. 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, is shorthand for , so you can save yourself some typing there. Once again, thanks for your help! —AlphaMikeOmega (talk) 16:56, 28 April 2022 (UTC)

Control of Cities: Blahodatne

Hi! Thanks again for your contributions to Control of cities during the Russo-Ukrainian War and the related maps. It's good to know you were working on the pages while I was taking a break.

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)

Tech News: 2026-38

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 Future Audiences team has started a discussion on English Wikipedia about a proposed new experiment to show a temporary notice about the new Google Preferred Sources feature to Wikipedia readers coming from Google. The experiment is to test whether this notice makes visitors come back to Wikipedia more often. Preferred Sources feature lets users choose websites they trust so Google can highlight content from those sources more prominently in Search and AI experiences. We are interested in testing this on other languages that Google supports and would welcome assistance with starting conversations on other wikis. If interested, please reach out to Future Audiences on the talk page.

Updates for editors

• The chat platform Discord is releasing a new self-service framework that websites can use to specify how their links should look when shared on Discord. The Future Audiences team is planning to start using this new framework to improve how Wikipedia links look when shared on Discord, giving better attribution and credit to contributors. The link appearance and behavior won't change in the first phase of this project as we want to first collect some baseline data to assess the impact of future changes. However, if community members who are active on Discord spot any issues, they can reach out on Phabricator or Metawiki.
• The Reader Growth team will be running an experiment to test whether compacting article lead sections on mobiles with the addition of a "read more" button improves reader retention. The test will begin on September 17 on Arabic, Spanish, French, Indonesian, Italian, Japanese, Portuguese, Vietnamese, and Chinese Wikipedias and will run for four weeks.
• All wikis will be read-only for a few minutes on September 23. This is planned at 14:00 UTC. More information will be published in Tech News and will also be posted on individual wikis in the coming week.
• View all 28 community-submitted tasks that were resolved last week. For example, an issue where Wikistats for Wikipedias was returning an HTTP 500 error and could not be reached, has now been fixed.

Updates for technical contributors

• Developers who maintain a tool that queries the Wikimedia Commons links tables need to update their code to connect to the new x4 database cluster. The links tables have been moved from the s4 cluster to x4, and will no longer receive updates on s4. The page and redirect tables remain available on both clusters. A wiki replica for the x4 cluster will be set up afterwards. The change is being made because the s4 cluster has grown too large to operate efficiently. You can read more.
• Detailed code updates later this week: MediaWiki

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 15:28, 14 September 2026 (UTC)

The Signpost: 16 September 2026

• News and notes: The Balance of Power
  Wikimedia employees unionize, officer departs, The Signpost gains sister on Wiktionary

• In the media: Shocking photos may be changed on Wikipedia
  The image gallery anyone can edit.

• Disinformation report: Have UN Secretary-General candidates manipulated Wikipedia?
  Speaking diplomatically, not all of them.

• Recent research: Google's AI overviews may have reduced search engine referrals to English Wikipedia by 5%
  And other research findings.

• WikiConference report: The backwater symbiosis – reflections from Wiki Conference India 2026
  The fourth iteration of Wiki Conference India.

• Traffic report: Heaven let your light shine down
  The recently deceased dominate while still leaving room for some entertainment.

• Serendipity: Wikipedia Family Mosh Pit
  A poem by Mollystarkdean.

• Obituary: Passing of Gobonobo, community leader advocating for women and minorities
  Promoter of cultural knowledge and organizer of global cooperation.

• On the bright side: Fantasy video games, hopeful science fiction, and the change of seasons
  The Legend of Zelda, Star Trek, and Vivaldi's The Four Seasons.

• Comix: The Adventure of the Unknown Corpse
  An elementary case for fiction's greatest detective.

* Read this Signpost in full * Single-page * Unsubscribe * MediaWiki message delivery (talk) 02:07, 16 September 2026 (UTC)

Tech News: 2026-39

Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.

Weekly highlight

• All wikis will be read-only for a few minutes on Wednesday, 23 September 2026 at 14:00 UTC. This is for the datacenter server switchover backup tests, which happen twice a year. During the switchover, all Wikimedia website traffic is shifted from one primary data center to the backup data center to test availability and prevent service disruption even in emergencies.

Updates for editors

• The Growth team tested a new post-edit notice designed to encourage Temporary Account holders to register for a permanent account. The new notice replaced multiple dialogs and a simultaneous welcome notification with a single message highlighting the benefits of creating an account. The experiment increased permanent account creation from 1.94% to 3.66%, an 87% relative increase. The change will now be released to all wikis.
• For Wikipedia editors using the "Suggestion mode" Beta Feature, there is a new opt-in user preference for showing "experimental" edit checks and suggestions. These types are listed at Special:EditChecks, and are intended for early developer-testing and for gathering feedback from experienced users. Administrators can change the configuration details for each suggestion as usual. Administrators can also use this feature to help test their community's ideas for locally created checks and suggestions. Experimental types will have a more distinct visual style later this week. Feedback is welcome.
• The CEE Technical Village Pump has been launched as a space for technical discussions and collaboration among Wikimedia communities in Central and Eastern Europe.
• A new tool, Starter Kit, is now available for new and small language Wikipedia communities. It brings together guided tasks, tools, and resources to help communities get started, monitor their progress, and collaborate with the broader Wikimedia community. Starter Kit is hosted on Wikimedia Toolforge and is designed for Wikipedias with fewer than 50,000 articles. Learn more about how Starter Kit works and how communities have been using it in this Diff blog post.
• The Reader Growth team is launching a retest of the image carousel experiment. The retest will use three new versions of the design, updated based on community feedback. The team will assess results and determine with communities whether or not to proceed with the feature. The experiment will begin the week of September 28 and will run on Arabic, Bengali, Chinese, Czech, English, Farsi, French, German, Indonesian, Japanese, Polish, Portuguese, Spanish, Swedish, and Vietnamese Wikipedias.
• After successful rollouts to Arabic, Bengali, Chinese, Czech, English, French, Indonesian, and Vietnamese Wikipedias, the Reading Lists feature from the Reader Experience team will be available to all logged-in users on all Wikipedia wikis starting September 28.
• View all 28 community-submitted tasks that were resolved last week. For example, an issue where the mentor status script repeatedly updated mentors’ status even when nothing had changed, creating unnecessary Recent Changes entries, has now been fixed.

Updates for technical contributors

• The abusefilters list query API, used to retrieve specific details about active or historical abuse filters configured on a wiki, has been updated to support the formatversion=2 configuration parameter, thereby leading to breaking changes to the API response. All users who maintain user-scripts or other code need to check if they use the abusefilters list query API, and respond to any breaking changes.
• Detailed code updates later this week: MediaWiki

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 11:54, 27 September 2026 (UTC)

Tech News: 2026-40

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 default skins on desktop and mobile web (Vector 2022 and Minerva respectively) will now be informed if the search suggestions displayed as they type into Search come from page redirects. Previously, users could get confused when the top search suggestions did not match exactly what they had typed. The new redirect notice clarifies that these suggestions are not random, but related to the search. The suggested pages may be redirects to the most relevant destination articles being searched for.
• Logged-out Wikipedia users on mobile web will begin to see a bookmark button for saving articles to their reading lists instead of the current Watchstar button. When clicked, the bookmark button prompts users to log in or create an account to save an article for later. An earlier experiment found that the bookmark icon was four times more likely than the Watchstar button to encourage logged-out users to create an account. This change is part of efforts to encourage more readers to become account holders and use features that help them save and return to content.
• An experiment will begin on September 29 on Spanish, Arabic, English, and French Wikipedias to simplify the experience users encounter immediately after account creation. The test will explore whether removing friction from the current Welcome Survey helps new users understand what to do next more easily. The experiment will run through the end of October.

• The Product and Technology Advisory Council has put out a call for the community to suggest topics that it should consider and discuss with the Wikimedia Foundation. Editors and technical contributors are invited to add topics to the council's talk page.
• Later this week, it will be possible for communities to configure Edit Checks and Suggestions so that they are shown within additional namespaces, such as a Draft: namespace. Feedback is welcome.
• A bug in the Global Watchlist is causing the page to fail to load for users that have unseen changes on Wikimedia Commons. Developers are working on a fix. Until then, affected users can follow the workarounds described in the relevant help section.
• New magic words {{CATEGORYSORT:TIMESTAMP}} and {{CATEGORYSORT:RTIMESTAMP}} are now available for use. They are able to change the default sorting of categories to be based on timestamp of categorization.
• View all 20 community-submitted tasks that were resolved last week. For example, the issue where Wikistats for Wikipedias was not reachable has now been fixed.

Updates for technical contributors

• The datacenter switchover, scheduled on September 23, has been postponed. The equinox exercise revealed capacity issues, preventing the switch of all services to the other datacenter. The process has been paused, prioritizing investigating that issue, to ensure that we continue to be able to serve our users reliably. A new exercise will be scheduled. Meanwhile, all traffic and edits continue to work as usual.
• On September 23, a power loss briefly affected all wikis, creating intermittent issues on both reading and editing modes. This also affected Gerrit. This is unrelated to the datacenter switchover postponement.
• Produnto has been deployed to mediawiki.org and some Indic language wikis. We want to hear your feedback on this experimental product. Produnto allows users to use Lua modules hosted in Wikimedia's GitLab. It simplifies the sharing of Lua code between wikis. Instead of copying each individual Lua module from one wiki to another, users will be able to easily share packages across all wikis.
• Detailed code updates later this week: MediaWiki

Meetings and events

• A Cross-wiki code collaboration workshop will be held online on October 2 at 12:30 UTC, bringing together South Asian technical contributors to learn about Produnto and begin piloting it on Hindi, Punjabi, Odia, Telugu, and Malayalam Wikipedias. Produnto is a package manager for deploying Lua modules hosted on GitLab to Wikimedia wikis, and was recently deployed on some pilot wikis.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

MediaWiki message delivery 10:47, 28 September 2026 (UTC)

Tech News: 2026-41

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 process for this year’s Community Wishlist has been published, incorporating community feedback. The wish submission process will end on November 8. This year, a working group (open for volunteering) that includes community members familiar with the technical aspect of our wikis alongside Wikimedia Foundation staff, will take care of the triage process. The triage is expected to be completed by late November. Votes for wishes will start in January.

Updates for editors

• Editors using the visual editor will now see a warning when they paste text that is likely to have initially been copied from one of five external generative AI chatbots into Wikipedia. This feature is known as LLM Paste Check. It is a type of Edit Check that is community configurable. The check looks for markers in the copied HTML and is not using content watermark detection. Edits will also be tagged so that patrollers can review them more closely. The feature helps newcomers add content that respects Wikipedia’s policies and makes it easier for experienced editors to identify problematic edits. Communities with local policies about LLM usage can adjust the wording and policy that is linked. The team apologizes that this was rolled out without a delay for translations.
• Editors can now easily access the web visual editor directly from the iOS and Android apps. When opening the editor, users will be given a choice between visual editing and source editing. If they choose visual editing, they will be sent to a mobile web window in their phone's browser. After completing their edit, a banner will give them the option to return to the app. This enables readers to make quick contributions while casually reading.
• Users of the Wikipedia Android and iOS apps will now see a one-time account creation prompt after they have used the app for two consecutive weeks. This prompt explains the benefits of having an account. It is intended to help more casual readers become logged-in users who return to the apps regularly.
• Editors on group1 wikis, including Wikiquote, Wikibooks, Wikiversity, Wikivoyage, and Wikisource, will no longer see notifications on Recent Changes and Watchlist when a link to another language version of a page is added, removed, or changed in its Wikidata item. This change will begin on October 5 at 07:00 UTC as a two-week trial to reduce high-volume, low-value notifications and make important changes easier to identify. Editors who rely on these notifications can read more on the project page and share feedback or concerns on the talk page.
• View all 36 community-submitted tasks that were resolved last week. For example, an issue where mentors who removed themselves from the mentorship program could still have mentees assigned to them and receive questions, has now been fixed. Mentees will now be reassigned when a mentor leaves the program.

Updates for technical contributors

• Wikimedia Brasil has published its Development Best Practices Framework (ABPD). It is a guide for staff, contractors and volunteers building technical tools and projects. It covers the project lifecycle, security, accessibility, personal data protection and responsible AI use, and explains how movement-wide guidelines were adapted to a local context. They encourage other affiliates to reuse it and adapt it. Read more in the Diff post.
• A new, canonical base URL for Wikimedia APIs will soon be introduced. The new canonical route follows a {projectName}/api/ pattern and will act as an alternative path for current REST APIs (for example: {projectName}/w/rest.php/). Both versions will be callable for all existing APIs, but the new structure will be the preferred path for newly created API modules. This change will be non-breaking for most users. The existing pathways will remain available for all existing endpoint requests. However, some endpoints may return URLs following the new pattern in response bodies. Changes will be available on test wiki first, with the rollout expected to cover all wikis by the end of October.
• Detailed code updates later this week: MediaWiki.

Tech news prepared by Tech News writers and posted by bot • Contribute • Translate • Get help • Give feedback • Subscribe or unsubscribe.

18:49, 5 October 2026 (UTC)