"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[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[reply]
New year, new scripts. Welcome to the 23rd issue of the Wikipedia Scripts++ Newsletter, covering around 39% of our favorite new and updated user scripts since 24 December 2021. That’s right, we haven’t published in two years! Can you believe it? Did you miss us?
Got anything good? Tell us about your new, improved, old, or messed-up script here!
User:Alexander Davronov/HistoryHelper has now become stable with some bugfixes and features such as automatically highlighting potentially uncivil edit summaries and automatically pinging all the users selected.
To a lesser extent, the same goes for User:PrimeHunter/Search sort.js. I wish someone would integrate the sorts into the sort menu instead of adding 11 portlet links.
Aaron Liu: Watchlyst Greybar Unsin is a rewrite of Ais's Watchlist Notifier with modern APIs and several new features such as not displaying watchlist items marked as seen (hence the name), not bolding diffs of unseen watchlist elements which doesn’t work properly anyways, displaying the rendered edit summary, proper display of log and creation actions and more links.
Alexis Jazz: Factotum is a spiritual successor to reply-link with a host of extra features like section adding, link rewriting, regular expressions and more.
User:Aveaoz/AutoMobileRedirect: This script will automatically redirect MobileFrontend (en.m.wikipedia) to normal Wikipedia. Unlike existing scripts, this one will actually check if your browser is mobile or not through its secret agent string, so you can stay logged in on mobile! Hooray screen estate!
Deputy is a first-of-its-kind copyright cleanup toolkit. It overrides the interface for Wikipedia:Contributor copyright investigations for easy case processing. It also includes the functionality of the following (also new) scripts:
User:Elominius/gadget/diff arrow keys allows navigation between diffs with the arrow keys. It also has a version that requires holding Ctrl with the arrow key.
Frequently link to Wikipedia on your websites yet find generating CC-BY credits to be such a hassle? Say no more! User:Luke10.27/attribute will automatically do it for ya and copy the credit to yer clipboard.
User:MPGuy2824/MoveToDraft, a spiritual successor (i.e. fork) to Evad37's script, with a few bugs solved, and a host of extra features like check-boxes for choosing draftification reasons, multi-contributor notification, and appropriate warnings based on last edit time.
/CopyCodeBlock: one of the most important operations for any scripter and script-user is to copy and paste. This script adds a copy button in the top right of every code block (not to be confused with <code>) that will, well, copy it to your clipboard!
m:User:NguoiDungKhongDinhDanh/AceForLuaDebugConsole.js adds the Ace editor (a.k.a. the editor you see when editing JS, CSS and Lua on Wikimedia wikis) to the Lua debug console. "In my opinion, whoever designed it to be a plain <textarea> needs to seriously reconsider their decision."
GANReviewTool quickly and easily closes good article nominations.
ReviewStatus displays whether or not a mainspace page is marked as reviewed.
SpeciesHelper tries to add the correct speciesbox, category, taxonbar, and stub template to species articles.
User:Opencooper/svgReplace and Tol's fork replaces all rasterized SVGs with their original SVG codes for your loading pleasures. Tell us which one is better!
ArticleInfo displays page information at the top of the page, directly below the title.
/HeaderIcons takes away the Vector 2022 user dropdown and replaces it with all of the icons within, top level, right next to the Watchlist. One less click away! There's also an alternate version that uses text links instead of icons.
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Recent changes
mediawiki2latex is a tool that converts wiki content into the formats of LaTeX, PDF, ODT, and EPUB. The code now runs many times faster due to recent improvements. There is also an optional Docker container you can install on your local machine.
The way that Random pages are selected has been updated. This will slowly reduce the problem of some pages having a lower chance of appearing. [1]
Changes later this week
The new version of MediaWiki will be on test wikis and MediaWiki.org from 9 January. It will be on non-Wikipedia wikis and some Wikipedias from 10 January. It will be on all wikis from 11 January (calendar). [2][3]
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Recent changes
Pages that use the JSON contentmodel will now use tabs instead of spaces for auto-indentation. This will significantly reduce the page size. [4]
Gadgets and personal user scripts may now use JavaScript syntax introduced in ES6 (also known as "ES2015") and ES7 ("ES2016"). MediaWiki validates the source code to protect other site functionality from syntax errors, and to ensure scripts are valid in all supported browsers. Previously, Gadgets could use the requiresES6 option. This option is no longer needed and will be removed in the future. [5]
An update on the status of the Community Wishlist Survey for 2024 has been published. Please read and give your feedback.
Changes later this week
The new version of MediaWiki will be on test wikis and MediaWiki.org from 16 January. It will be on non-Wikipedia wikis and some Wikipedias from 17 January. It will be on all wikis from 18 January (calendar). [8][9]
Starting on January 17, it will not be possible to login to Wikimedia wikis from some specific old versions of the Chrome browser (versions 51–66, released between 2016 and 2018). Additionally, users of iOS 12, or Safari on Mac OS 10.14, may need to login to each wiki separately. [10]
The jquery.cookie module was deprecated and replaced with the mediawiki.cookie module last year. A script has now been run to replace any remaining uses, and this week the temporary alias will be removed. [11]