User talk:Firestar464
|
||||||
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🎄••••
[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]This section is pinned and will not be automatically archived. |
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:
- 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.
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
- 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.
- 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.
- 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.
- Search on Google Maps for locations of the same name near the area being discussed;
- 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)
- 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
Control of Cities: Blahodatne
[edit]This section is pinned and will not be automatically archived. |
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: 2024-46
[edit]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. [1]
- 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. [2]
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. [3] - 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. [4]
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)
The Signpost: 18 November 2024
[edit]ArbCom 2024 Elections voter message
[edit]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:45, 19 November 2024 (UTC)
Tech News: 2024-47
[edit]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. [5]
- 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. [6]
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. [7][8]
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)
Tech News: 2024-48
[edit]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. [9] - 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. [10]
- 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. [11]
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)
Hello!
[edit]Hello! I see you've visited Japan before, right? Well, I wanna go to Japan too! Bella. (talk) 00:59, 26 November 2024 (UTC)
Contentious topic notice: Syrian Civil War
[edit]This is a standard message to notify contributors about an administrative ruling in effect. It does not imply that there are any issues with your contributions to date.
You have shown interest in the Syrian Civil War and ISIL. Due to past disruption in this topic area, the community has authorised uninvolved administrators to impose contentious topics restrictions—such as editing restrictions, bans, or blocks—on editors who do not strictly follow Wikipedia's policies, expected standards of behaviour, or the page-specific restrictions, when making edits related to the topic. For additional information, please see the guidance on these sanctions. If you have any questions, or any doubts regarding what edits are appropriate, you are welcome to discuss them with me or any other editor. |
AntiCompositeNumber (talk) 00:42, 1 December 2024 (UTC)
Tech News: 2024-49
[edit]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. [12]
- 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). [13]
- 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. [14]
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)
Syria map
[edit]Just clarifying, is the only time the map can be edited when a well-known reliable source states "party X has taken control of villages A, B, C, D...", and not if the reliable source claims "party X claims to have taken control of villages A, B, C, D and most of blue province. Party Y launched a counterattack"? Because if the latter is allowed to be used to change control of villages in a province, I will happily revert all edits I made. If a widely respected source says "Party X took control over large parts of Aleppo and the surrounding towns", how is that supposed to be used to change control of villages? Can it be used to "confirm" Party X's claims? This needs to be clarified. TheNavigatrr (talk) 00:20, 3 December 2024 (UTC)
- You already answered the above question on a different page, but if a news outlet such as the New York Times were to claim "the rebels now control all of Idlib Province and most of Aleppo Province", would that be grounds to change previously government-held villages around Nubl/Zahraa, Deir Hafir, as-Safira and immediately south of Aleppo city to rebel-held? TheNavigatrr (talk) 00:05, 5 December 2024 (UTC)
- In regards to Aleppo Province, those changes would be WP:OR based on the NYT article alone. However, I found a source for as-Safira. Firestar464 (talk) 01:24, 5 December 2024 (UTC)
December 2024
[edit]Hello, Firestar464. I noticed that your recent edit to Module:Syrian Civil War overview map added a link to an image on an external website or on your computer, or to a file name that does not exist on Wikipedia's server. For technical and policy reasons it is not possible to use images from external sources on Wikipedia. Most images you find on the internet are copyrighted and cannot be used on Wikipedia, or their use is subject to certain restrictions. If the image meets Wikipedia's image use policy, consider uploading it to Wikipedia yourself or request that someone else upload it. See the image tutorial to learn about wiki syntax used for images. Thank you. Sumanuil. (talk to me) 01:01, 8 December 2024 (UTC)
Tech News: 2024-50
[edit]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. [15] - 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. [16]
- 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. [17] - One new wiki has been created: a Wikivoyage in Indonesian (
voy:id:
) [18] - 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. [19]
- 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. [20][21]
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. [22]
- 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. [23]
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.