This page is an archive of past discussions. Do not edit the contents of this page. If you wish to start a new discussion or revive an old one, please do so on the current talk page.
The second round of the competition has now closed, with just under 100 points being required to qualify for round 3. YellowEvan just scraped into the next round with 98 points but we have to say goodbye to the thirty or so competitors who didn't achieve this threshold; thank you for the useful contributions you have made to the Cup and Wikipedia. Our top scorers in round 2 were:
Cas Liber, led the field with five featured articles, four on birds and one on astronomy, and a total score of 2049, half of which came from bonus points.
1989 was in second place with 826 points, 466 of which were bonus points. 1989 has claimed points mostly relating to anime and Japanese-related articles.
Peacemaker67 took third place with two FAs, one GA and seven GARs, mostly on naval vessels or military personnel, scoring 543 points.
Other contestants who scored over 400 points were Freikorp, Carbrera, and Czar. Of course all these points are now wiped out and the 32 remaining contestants start again from zero in round 3.
Vivvt submitted the largest number of DYKs (30), and MBlaze Lightning achieved 13 articles at ITN. Carbrera claimed for 11 GAs and Argento Surfer performed the most GARs, having reviewed 11. So far we have achieved 38 featured articles and a splendid 132 good articles. Commendably, 279 GARs have been achieved so far, more than double the number of GAs.
So, on to the third round. Remember that any content promoted after the end of round 2 but before the start of round 3 can be claimed in round 3. Remember too that you must claim your points within 10 days of "earning" them. Invitations for collaborative writing efforts or any other discussion of potentially interesting work is always welcome on the WikiCup talk page. Remember, if two or more WikiCup competitors have done significant work on an article, all can claim points equally.
If you are concerned that your nomination—whether it is at good article nominations, a featured process, or anywhere else—will not receive the necessary reviews, please list it on Wikipedia:WikiCup/Reviews. If you want to help out with the WikiCup, please do your bit to help keep down the review backlogs! Questions are welcome on Wikipedia talk:WikiCup, and the judges are reachable on their talk pages or by email. Good luck! If you wish to start or stop receiving this newsletter, please feel free to add or remove yourself from Wikipedia:WikiCup/Newsletter/Send. Godot13, Sturmvogel 66 and Cwmhiraeth13:16, 1 May 2017 (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.
Scripts using very old deprecated wikibits functions show errors. These functions have not worked since 2013. You should fix or disable broken scripts. You can see examples of how to upgrade scripts. This is the same thing as Tech News wrote about in issue 2017/16. You need to addmw.loader.using( 'mediawiki.util' ) block for your scripts also, or add mediawiki.util dependency in gadget ResourceLoader section in MediaWiki:Gadgets-definition. [2][3]
Problems
Because of a data centre test you will be able to read but not edit the wikis for 20 to 30 minutes on 3 May. This will start at 14:00 (UTC). You might lose edits if you try to save during this time. You can read more about this.
Changes this week
There is no new MediaWiki version this week. This is because of the data centre test.
Meetings
You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 2 May at 19:00 (UTC). See how to join.
Future changes
All Wikimedia wikis will have cookie blocks from May 8. This is an extension to the autoblock system so when a user is blocked, the next time they visit the wiki a cookie will be set. This means that even if the user switches accounts and to a new IP address the cookie will block them again. [4]
The Publish changes, Show preview and Show changes buttons will look slightly different. This is to fit with the OOUI look. Users can test scripts, gadgets and so on to see if they work with the new interface by adding &ooui=1 to the URL. [5]
An RfC has clarified that user categories should be emptied upon deletion, but redlinked user categories should not be removed if re-added by the user.
Discussions are ongoing regarding proposed changes to the COI policy. Changes so far have included clarification that adding a link on a Wikipedia forum to a job posting is not a violation of the harassment policy.
There is a new tool for adding archives to dead links. Administrators are able to restrict other user's ability to use the tool, and have additional permissions when changing URL and domain data.
Following an RfC, the editing restrictions page is now split into a list of active restrictions and an archive of those that are old or on inactive accounts. Make sure to check both pages if searching for a restriction.
Latest tech news from the Wikimedia technical community. Please tell other users about these changes. Not all changes will affect you. Translations are available.
Problems
Some users have a problem with the watchlist. Some changes in categories make the watchlist a blank page. The developers are working on this. Until this is fixed you can try some things that have helped other editors if you have this problem. You can turn on Hide categorization of pages in your watchlist preferences. You can turn off Expand watchlist to show all changes, not just the most recent in your watchlist preferences. You can remove problematic categories from Special:EditWatchlist/raw. [6]
There was a problem with the visual editor for several days. You could not save edits that triggered a CAPTCHA. This would for example be when a new user added external links in references. This was fixed on 2 May. [7]
Changes this week
When you edit you can switch between the visual editor and the wikitext editor. This works if the wiki you edit has the visual editor. The menu will now say Visual editing and Source editing instead of Switch to visual editing and Switch to code editing. This is because it was confusing when the menu said you could switch to the editor you were already using. [8]
The new version of MediaWiki will be on test wikis and MediaWiki.org from 9 May. It will be on non-Wikipedia wikis and some Wikipedias from 10 May. It will be on all wikis from 11 May (calendar).
Meetings
You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 9 May at 19:00 (UTC). See how to join.
Future changes
You will be able to get a notification when a page you created is connected to a Wikidata item. This will come to Wikivoyage on 9 May. If there are no problems it will come to most Wikipedias on 30 May. It will come to other projects and English, French and German Wikipedia later in the summer. It will be opt-in for existing users and opt-out for new users. [9][10]
Markup that looks like code for language variants might need to be fixed. If -{ is used in transclusions or web addresses it has to be escaped appropriately. You can use -<nowiki/>{ for transclusions and %2D{ in web addresses. A transclusion could for example be when you use -{ in a template: {{1x| sad :-{ face }}. This is because of some code fixes to the preprocessor and affects all wikis. [11][12]
Did you know that you can review your changes visually?
When you are finished editing the page, type your edit summary and then choose "Review your changes".
In visual mode, you will see additions, removals, new links, and formatting highlighted. Other changes, such as changing the size of an image, are described in notes on the side.
Click the toggle button to switch between visual and wikitext diffs.
The wikitext diff is the same diff tool that is used in the wikitext editors and in the page history.
You can read and help translate the user guide, which has more information about how to use the visual editor.
A new wikitext editing mode is available as a Beta Feature on desktop devices. The 2017 wikitext editor has the same toolbar as the visual editor and can use the citoid service and other modern tools. Go to Special:Preferences#mw-prefsection-betafeatures to enable the ⧼Visualeditor-preference-newwikitexteditor-label⧽.
A new visual diff tool is available in VisualEditor's visual mode. You can toggle between wikitext and visual diffs. More features will be added to this later. In the future, this tool may be integrated into other MediaWiki components. [13]
You can now use your web browser's function to switch typing direction in the new wikitext mode. This is particularly helpful for RTL language users like Urdu or Hebrew who have to write JavaScript or CSS. You can use Command+Shift+X or Control+Shift+X to trigger this. [15]
The way to switch between the visual editing mode and the wikitext editing mode is now consistent. There is a drop-down menu that shows the two options. This is now the same in desktop and mobile web editing, and inside things that embed editing, such as Flow. [16]
The Categories item has been moved to the top of the Page options menu (from clicking on the icon) for quicker access. [17] There is also now a "Templates used on this page" feature there. [18]
You can now create <chem> tags (sometimes used as <ce>) for chemical formulas inside the visual editor. [19]
Tables can be set as collapsed or un-collapsed. [20]
The Special character menu now includes characters for Canadian Aboriginal Syllabics and angle quotation marks (‹› and ⟨⟩) . The team thanks the volunteer developer, Tpt. [21]
A bug caused some section edit conflicts to blank the rest of the page. This has been fixed. The team are sorry for the disruption. [22]
There is a new keyboard shortcut for citations: Control+Shift+K on a PC, or Command+Shift+K on a Mac. It is based on the keyboard shortcut for making links, which is Control+K on a PC or Command+K on a Mac. [23]
Future changes
The VisualEditor team is working with the Community Tech team on a syntax highlighting tool. It will highlight matching pairs of <ref> tags and other types of wikitext syntax. You will be able to turn it on and off. It will first become available in VisualEditor's built-in wikitext mode, maybe late in 2017. [24]
The kind of button used to Show preview, Show changes, and finish an edit will change in all WMF-supported wikitext editors. The new buttons will use OOjs UI. The buttons will be larger, brighter, and easier to read. The labels will remain the same. You can test the new button by editing a page and adding &ooui=1 to the end of the URL, like this: https://www.mediawiki.org/wiki/Project:Sandbox?action=edit&ooui=1 The old appearance will no longer be possible, even with local CSS changes. [25]
A friendly FYI, that Premathoo reverted you with more obvious LTA sock trolling from someone you just blocked. It appears that my AIV report is being declined. Entirely up to you if you want to do anything. Thanks.
@Murph9000: Sure thing. One thing I noticed: the user has frequently been using File:Windingroad.jpg recently. According to the description page, every time the file is used on the English Wikipedia, except for the user page of Jake Wartenberg, it is used on the user page of a sockpuppet. Mz7 (talk) 04:29, 10 May 2017 (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.
Recent changes
You can now use ISBNs to automatically generate citations in the visual editor. This works on wikis that have enabled Citoid. [27]
The mediawiki.util library does not load automatically any more. Your Special:MyPage/common.js may use it. If you have technical problems that started a couple of weeks ago you can try adding mw.loader.using('mediawiki.util').done(function(){ as the first line in the file and }); as a last one. Tech News wrote about this in the 2017/18 issue. [29]
Changes this week
The RevisionSlider extension will be a default feature on all wikis. RevisionSlider is an easier way to move between changes in the page history. It has been a default feature on German, Arabic and Hebrew Wikipedia and a beta feature on all wikis. You will be able to turn it off in your preferences. [30]
There is no new MediaWiki version this week.
Future changes
Administrators will soon be able to search through deleted pages. [31][32]
Markup that looks like code for language variants might need to be fixed. Tech News wrote about this last week. If -{ is used in transclusions or web addresses it has to be escaped appropriately. You can use -<nowiki/>{ for transclusions and %2D{ in web addresses. This is because of some code fixes to the preprocessor and affects all wikis. You can now see the full list of wikis with this problem and help fix them to avoid that things break later this month. You might find false positives. You can read more about what to fix. [33][34]
Older unreported changes
Your Meta user page is shown on all wikis where you don't have a local user page. You can now add the magic word __NOGLOBAL__ to your Meta user page to stop this. [35][36]
“New Filters for Edit Review” beta released: As of May 9, the New Filters for Edit Review beta has been released to all wikis. The beta lets users review edits on Recent Changes using an easier and more powerful interface and many new tools, including user-defined highlighting and, on some wikis, predictive filters powered by ORES, a machine-learning program. You must opt in to the beta to try it out.
Tell us your ideas—but don’t wait: The team is focused right now in making changes to the New Filters beta. But in a few months, we’ll be moving on to other projects. So now is the time to give the new tools a try and then tell us what you think. What works well? What could make things better for you?
In the medium-term: By the end of summer, we plan to complete a suite of improvements that will, among other things: incorporate all the remaining Recent Changes tools into the new filtering interface; create new ways for reviewers to move back and forth through the filter queue; implement a “Reverted” filter; and, finally, bring the New Filters UI and tools to Watchlist.
Have time for a talk? We're looking for people we can interview about their experiences with the new beta. If you’re a regular user of Recent Changes and have tried the new features—and if you can spare an hour to chat in English with our design researcher—please email dchenwikimedia.org with the subject line “user interview.” Let us know how to get in touch with you and what time zone (city, country...) you’re in.
Wish you had ORES on your wiki? Some of the more interesting New Filters for Edit Review features are dependent on the machine-learning service ORES, which is available only on a small but growing list of wikis. For ORES to work on a wiki, volunteers from that wiki must train it by scoring some thousands of sample edits. Here’s a link that explains how the process works and how you can get it started on your wiki.
On wikis where Flagged Revisions are used, an edit highlighted as bad by ORES will not be highlighted anymore when the edit is reviewed by someone. [37]
You can highlight pages that are in your Watchlist in Recent Changes. 3 different filters are available: in watchlist, not in watchlist, new changes in watchlist. [38]
Wikidata, Dutch, Czech, Hebrew, Estonian and Finnish Wikipedia now have the new filters available as a Beta feature, and ORES is enabled by default on those wikis. [39]
All wikis now have the Recent changes Filters as a Beta feature. [40]
Users are invited to opt in to the Recent changes Filters beta when they visit the Recent Changes page. [41]
On wikis that have ORES predictions enabled by default, it is now possible to choose how to display the predictions in watchlist and recent changes pages. [42]
Future changes
It will be possible soon to save and retreive your favorite filters combinations. [43]
We are working on adding filter groups for last revisions, edits from Wikidata and reverted edits. [44][45][46]
When an article you have created is linked to a Wikidata item, you can receive a notification. Wikidata and all the Wikivoyages have it since May 9th, other wikis will follow. [47]
Special:Notifications tabs is now set to "Unread" if there are any unread messages. [48]
Why did you revert this edit? It is clearly a blatant attack on White People, and is therefore racist.
If anyone made a series called "dear Black People" there would be mass outrage. I disagree with your revert as I think
it is perfectly reasonable and not in any way "politically motivated".
Something that aims to demonize white people is racist. There is nothing political about it, it is the definition of racist.
(edit conflict) Wikipedia reports on information, but it does not take sides. Instead, Wikipedia articles should seek to explain the different sides. This is called having a neutral point of view, and it's one of Wikipedia's core policies. To explicitly label something as racist would be to take a side. Note, for example, that the Ku Klux Klan article does not say "The Ku Klux Klan is a racist movement"; it explains what the group does, but does not decide for the reader whether or not such actions are racist. To say that "Some people find the film to be racist", along with reliable sources backing the statement up, is appropriate; to go "Some people find this film to be racist, so it must be racist" is not having a neutral point of view, and is not appropriate here. —k6ka🍁 (Talk · Contributions) 17:37, 17 May 2017 (UTC)[reply]
Also, this IP which i wrongly thought as static (first contribution other than those by me) is the one from which i edit in my place of work, and i also have this one (https://en.wikipedia.org/wiki/Special:Contributions/85.242.133.151) from my home. At 16:56, the IP started with 193 performed that vandalic action, and at that time i was not even at home, of course i cannot offer any evidence to the contrary, you'll just have to believe me :)
I'm about to email you about a rename over 50k that needs to be processed. If you have time please coordinate with a developer (does this require a phab ticket now?). You can use "[[Special:Diff/nnn|user request]]" as the reason for renaming, referring back to this diff. Thanks, –xenotalk17:21, 21 May 2017 (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.
Changes this week
The new version of MediaWiki will be on test wikis and MediaWiki.org from 23 May. It will be on non-Wikipedia wikis and some Wikipedias from 24 May. It will be on all wikis from 25 May (calendar).
There will be a <div> tag around HTML from the MediaWiki wikitext parser. Gadgets with code that does not follow recommendations could have problems with this. You can report new problems you think are related to this. [52]
Hello, You blocked this user here earlier today. I believe this user may be the same editor from a different IP. Similar edits to the same user TPs today and both locate to the same area. Is there a range block in force? Thanks. Regards, Eagleash (talk) 14:12, 24 May 2017 (UTC)[reply]
@Eagleash: I suspect they're the same user as well. From what I can see there's no rangeblock set (yet). I'm not too good with rangeblocks, though; might be better to ask another administrator that's proficient in that area. —k6ka🍁 (Talk · Contributions) 14:18, 24 May 2017 (UTC)[reply]
I went to another Admin.'s page and previewed my post there for correctly working links only to discover a block on the second IP in the last few minutes! Eagleash (talk) 14:31, 24 May 2017 (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.
Problems
Last week’s MediaWiki version was rolled back from some wikis because of a problem. This means planned changes did not happen. [53]
Meetings
You can join the next meeting with the VisualEditor team. During the meeting, you can tell developers which bugs you think are the most important. The meeting will be on 30 May at 19:00 (UTC). See how to join.
_-_Google_Art_Project.jpg)
