Wikipedia

Firestar464

Joined 14 January 2020
Latest comment: 2 days ago by MediaWiki message delivery in topic Tech News: 2025-49
Learn more about this page

••••🎄Merry Christmas🎄••••

edit

"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!

edit
 


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

edit
Latest comment: 3 years ago3 comments2 people in discussion
 

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)Reply

slaaaaaap...thanks for the advice Firestar464 (talk) 02:29, 1 April 2022 (UTC)Reply
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, <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

Control of Cities: Blahodatne

edit
Latest comment: 3 years ago1 comment1 person in discussion

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)Reply

The Signpost: 10 November 2025

edit
Latest comment: 23 days ago1 comment1 person in discussion
* Read this Signpost in full * Single-page * Unsubscribe * MediaWiki message delivery (talk) 12:52, 10 November 2025 (UTC)Reply

Tech News: 2025-46

edit
Latest comment: 23 days ago1 comment1 person in discussion

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

 
Example of a talk page with the new design, in French.
  • Starting November 12, users will see a change in the appearance of talk pages on some Wikipedias. Almost all wikis have received this design change; English Wikipedia will get these changes later. You can read more on Diff. Users can opt out of these changes in their user preferences in "Show discussion activity". [1]
  • MediaWiki can now display a page indicator automatically while a page is protected. This feature is disabled by default. It can be enabled by community request. [2]
  • Using the "Show preview" or "Show changes" buttons in the wikitext editor will now carry over certain URL parameters like 'useskin', 'uselang' and 'section'. This update also fixes an issue where, if the browser crashed while previewing an edit to a single section, saving this edit could overwrite the entire page with just that section’s content. [3][4][5]
  • Wikivoyage wikis can use colored map markers in the article text. The text of these markers will now be shown in contrasting black or white color, instead of always being white. Local workarounds for the problem can be removed. [6]
  • The Activity tab in the Wikipedia Android app is now available for all users. The new tab offers personalized insights into reading, editing, and donation activity, while simplifying navigation and making app use more engaging. [7]
  • The Reader Growth team is launching an experiment called "Image browsing" to test how to make it easier for readers to browse and discover images on Wikipedia articles. This experiment, a mobile-only A/B test, will go live on English Wikipedia in the week of November 17 and will run for four weeks, affecting 0.05% of users on English wiki. The test launched on November 3 on Arabic, Chinese, French, Indonesian, and Vietnamese wikis, affecting up to 10% of users on those wikis. [8]
  •   View all 27 community-submitted tasks that were resolved last week. For example the inability to lock accounts on mobile sites has been fixed. [9]

Updates for technical contributors

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

MediaWiki message delivery 20:36, 10 November 2025 (UTC)Reply

Tech News: 2025-47

edit
Latest comment: 16 days ago1 comment1 person in discussion

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

  • The Reader Experience team is experimenting with reading lists on mobile web, allowing logged-in readers with no edits to save private lists of articles for later. The experiment is running on Arabic, Chinese, French, Indonesian, and Vietnamese Wikipedias since the week of 10 November, and will begin on English Wikipedia the week of 17 November.
  • Users who can’t receive their email verification code during login can now get help by submitting a form on a new special page. This update is part of the Account Security initiative. If your account has an email address, please make sure you still have access to it. When logging in from a new device or location without 2FA, you may be asked to enter a 6-digit code sent by email to finish logging in. Learn more.
  • One new wiki has been created: a Wikisource in Minangkabau (s:min:) [16]
  •   View all 23 community-submitted tasks that were resolved last week.

Updates for technical contributors

  • As part of the Parser Unification project, the Content Transform Team rolled out Parsoid as the default parser to many low-traffic Wikipedias and is preparing the next step to high traffic ones. This message is an invitation for you to opt-in to Parsoid, as described in the Extension:ParserMigration documentation, and identify any issues you might encounter with your own workflow using bots, gadgets, or user scripts. Please, let us know through the "Report Visual Bug" link in the Tools sidebar or create a phab ticket and tag the Content Transform Team in Phabricator.
  • Unsupported Tools: Several issues with Video2Commons have been fixed, including filename-related upload failures, black-video imports, and retry handling. AV1 support has also been added. Ongoing work focuses on backend stability, ffmpeg errors, subtitle imports, metadata handling, and playlist uploads. To track specific tasks, check the Phabricator board.
  •   Detailed code updates later this week: MediaWiki

Meetings and events

  • Save the date for the next Wikimedia Hackathon happening in Milan, Italy from May 1–3, 2026. Registration will open in January 2026. Scholarship applications are currently open, and will close on November 28, 2025. If you have any questions, please email hackathon@wikimedia.org.

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

MediaWiki message delivery 17:24, 17 November 2025 (UTC)Reply

ArbCom 2025 Elections voter message

edit
Latest comment: 16 days ago1 comment1 person in discussion
 

Hello! Voting in the 2025 Arbitration Committee elections is now open until 23:59 (UTC) on Monday, 1 December 2025. 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 2025 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, 18 November 2025 (UTC)Reply

Tech News: 2025-48

edit
Latest comment: 9 days ago1 comment1 person in discussion

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

  • Last week, the Wikimedia Search Team recreated the "DWIM" (Do What I Mean) gadget functionality server-side, for Russian and Hebrew Wikipedias. This feature adds cross-keyboard suggestions to the standard search-box suggestions. For example, searching for cxfcnmt on Russian Wikipedia will now add suggestions for счастье ("happiness") that the user probably intended. They plan to enable this feature for other Russian and Hebrew wikis this week. [17]
  • Later this week, users of the "Improved Syntax Highlighting" beta feature will have syntax highlighting available in DiscussionTools. This requires that the "Enable editing tools in source mode" preference be set. [18]
  • Campaign events extension – the set of tools for coordinating events and other on-wiki collaborations has now been deployed to all Wikimedia wikis. A new feature known as Collaborative contribution to help organizers and participants see the impact of activities has also been added. Join the upcoming learning session to see the new feature in action and share your feedback.
  •   View all 24 community-submitted tasks that were resolved last week. For example, the bug which stopped CodeReviewBot from working, has now been fixed. [19]

Updates for technical contributors

  • Users of Wikimedia API can join a usability study to help validate the new design of Wikimedia REST API sandboxes. Interested participants should fill the recruitment survey. [20]
  • The MediaWiki Interfaces team is deprecating XSLT stylesheets within the Action API. Support for format=xml&xlst={stylesheet} will be removed from Wikimedia projects by the end of November, 2025. In addition, it will soon be disabled by default in MediaWiki release versions: v1.43 (LTS), v1.44, and v1.45. Support for XSLT stylesheets will be fully removed from MediaWiki v1.46 (expected to release between April and May 2026). [21]
  • The WDQS legacy endpoint (query-legacy-full.wikidata.org) will be decommissioned at the end of December 2025, and finally closed down on 7th January 2026. After this date, users should expect requests to query.wikidata.org that require the full graph to fail or return invalid results if they are not rewritten to use SPARQL federation. The team encourages users to ensure that tools and workflows use the supported WDQS endpoints (https://query.wikidata.org/ - Main graph or https://query-scholarly.wikidata.org/ - Scholarly graph). For support with migrating use cases, please review the Data Access and Request a Query pages for details and assistance on alternative access methods.
  •   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:54, 24 November 2025 (UTC)Reply

The Signpost: 1 December 2025

edit
Latest comment: 3 days ago1 comment1 person in discussion
  • Comix: Madness
    It could happen to anyone.
* Read this Signpost in full * Single-page * Unsubscribe * MediaWiki message delivery (talk) 00:12, 1 December 2025 (UTC)Reply

Tech News: 2025-49

edit
Latest comment: 2 days ago1 comment1 person in discussion

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

  • The Wikipedia Year in Review 2025 will be available on December 2 for users of iOS and Android Wikipedia apps, featuring new personalized insights, updated reading highlights, and refreshed designs. Learn more on the review's project page.
  • The Growth team is working on improving the text and presentation of the Verification Email sent to new users to make them more welcoming, useful and informative. Some new text have been drafted for A/B testing and you can help by translating them. See Phabricator.
  • Add a link will now be deployed at Japanese, Urdu and Chinese Wikipedias on December 2. Add a link is based on a prediction model that suggests links to be added to articles. While this feature has already been available on most Wikipedias, the prediction model could not support certain languages. A new model has now been developed to handle these languages, and it will be gradually rolled out to other Wikipedias over time. If you would like to know more, please contact Trizek (WMF).
  •   View all 34 community-submitted tasks that were resolved last week. For example, the issue where search boxes on some Commons pages showed no results due to switch from SpecialSearch to MediaSearch, has now been fixed. [22]
  • Two new wikis have been created:

Updates for technical contributors

  •   Detailed code updates later this week: MediaWiki

In depth

  • The Wikimedia Foundation is in the early stages of exploring approaches to Article guidance. The initiative aims to identify interventions that could help new editors easily understand and apply existing Wikipedia practices and policies when creating an article. The project is in the exploration and early experimental design phase. All community members are encouraged to learn more about the project, and share their thoughts on the talk page.

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

MediaWiki message delivery 18:55, 1 December 2025 (UTC)Reply

Add topic
Retrieved from "https://en.wikipedia.org/w/index.php?title=User_talk:Firestar464&oldid=1325574896"