Wikipedia:Wikipedia Signpost/2018-06-29/Technology report

Add links
From Wikipedia, the free encyclopedia
The Signpost
← Back to Contents
View Latest Issue


Technology report

Improvements piled on more improvements

Contribute  —  
Share this
By Evad37
New AI-assisted filters for review edits, which will become a standard feature of the Watchlist interface

AI-assisted filters on Watchlist coming out of beta

Collaboration team is announcing plans to graduate the New Filters for Edit Review out of beta on Watchlist by late June or early July. After launch, this suite of improved edit-search tools will be standard on all wikis. Individuals who prefer the existing Watchlist interface will be able to opt out by means of a new preference.

The New Filters introduce an easier yet more powerful user interface to Watchlist as well as a whole list of filters and other tools that make reviewing edits more efficient, including live page updating, user-defined highlighting, the ability to create special-purpose filter sets and save them for re-use and (on wikis with ORES enabled) predictive filters powered by machine learning. If you’re not familiar with the New Filters, please give them a try on Watchlist by activating the New Filters beta feature. In particular, it would be very helpful if you can test the new functionality with your local gadgets and configurations. The documentation pages provide guidance on how to use the many new tools you’ll discover.

Over 70,000 people have activated the New Filters beta, which has been in testing on Watchlist for more than eight months. We feel confident that the features are stable and effective, but if you have thoughts about these tools or the beta graduation, please let us know on the project talk page. In particular, tell us if you know of a special incompatibility or other issue that makes the New Filters problematic on your wiki. We’ll examine the blocker and may delay release on your wiki until the issue can be addressed. — Kaartic correct me, if i'm wrong (adapted from VPT post)

Responsive MonoBook skin for mobile users

Responsive Monobook demonstration at the Wikimedia Hackathon 2018.

Thanks to a volunteer-driven initiative, the MonoBook skin is now responsive, meaning it will have a mobile-optimized view for smaller devices (similar to the new Timeless skin). This is primarily targeted more towards the needs of third-party MediaWiki users, but is also available for users of Wikipedia and other Wikimedia Foundation wikis.

The initial deployment was made on 31 May with little notice, and had an overwhelmingly negative response at the Village Pump discussion. This was mostly due to the opt-out method not working, and accessibility problems for screen readers. The change was reverted on 2 June, and redeployed the next week after fixing those immediate concerns, and lowering the threshold (viewport width) for devices being considered mobile.

If you use the MonoBook skin, you can try the responsive layout out on a desktop device by shrinking your browser window. If you don't like the new layout, you can go to the Appearance tab in your preferences, uncheck "use responsive MonoBook design", and it will revert to the normal desktop styles.

Feedback, bugs, and suggestions can be reported on the Phabricator task.

(Adapted from VPT discussion)

Update on page issues on mobile web

Proposed display of a page notice on the mobile website.

Hi everyone. The Readers web team has recently begun working on exposing issue templates on the mobile website. Currently, details about issues with page content are generally hidden on the mobile website. This leaves readers unaware of the reliability of the pages they are reading. The goal of this project is to improve awareness of particular issues within an article on the mobile web. We will do this by changing the visual styling of page issues.

So far, we have drafted a proposal on the design and implementation of the project. We were also able to run user testing on the proposed designs. The tests so far have positive results. Here is a quick summary of what we learned:

  • The new treatment increases awareness of page issues among participants. This is true particularly when they are in a more evaluative/critical mode.
  • Page issues make sense to readers and they understand how they work
  • Readers care about page issues and consider them important
  • Readers had overwhelmingly positive sentiments towards Wikipedia associated with learning about page issues

Our next step would be to start implementing these changes. We wanted to reach out to you for any concerns, thoughts, and suggestions you might have before beginning development. Please visit the project page where we have more information and mockups of how this may look. Please leave feedback on the talk page. —CKoerner (WMF) (talk) (adapted from VPT post)

Potentially untagged misspellings report

Potentially untagged misspellings (configuration) is a newish database report that lists potentially untagged misspellings. For example, Angolan War of Independance is currently not tagged with {{R from misspelling}} and it should be.

Any and all help evaluating and tagging these potential misspellings is welcome. Once these redirects are appropriately identified and categorized, other database reports such as Linked misspellings (configuration) can then highlight instances where we are currently linking to these misspellings, so that the misspellings can be fixed.

This report has some false positives and the list of misspelling pairs needs a lot of expansion. If you have additional pairs that we should be scanning for or you have other feedback about this report, that is also welcome. — MZMcBride (talk) (adapted from VPT post)

In brief

Read-only for 30 minutes on July 18

Because of maintenance work, English Wikipedia will be read-only for up to 30 minutes on 18 July, at 06:00 UTC. Everyone will be able to read it, but you can’t edit. This is just to give you an early warning. If everything goes well, this should just take a few minutes, but prepare for 30 minutes to be on the safe side. You can read more in the tasks linked to from phab:T197134. — /Johan (WMF) (talk) (adapted from VPT post)

New user scripts to customise your Wikipedia experience

Bot tasks

Recently approved tasks
Current requests for approval

Latest tech news

Latest tech news from the Wikimedia technical community: 2018 #22, #23, #24, #25, & #26. Please tell other users about these changes. Not all changes will affect you. Translations are available on Meta.

Recent changes
  • You can now use global preferences on most wikis. This means you can set preferences for all wikis at the same time. Before this you had to change them on each individual wiki. Global preferences will come to the Wikipedias later this week. [1][2]
  • It is now easier for blocked mobile users to see why they were blocked. [3]
  • Wikidata now supports lexicographical data. This helps describe words.
  • There is now a checkbox on Special:ListUsers to let you see only users in temporary user groups. [4]
  • Some rare invisible Unicode characters have recently been banned from page titles. This includes soft hyphens (U+00AD) and left-to-right (U+2066) and right-to-left (U+2067) isolate markers. Existing pages with these characters will soon be moved by a script. [5]
  • Advanced item There's a new Wikimedia Foundation team to support the Wikimedia technical communities. It's called the Technical Engagement team. Most of the team members did similar work in other teams before this. More details in this issue's News and notes. [6]
  • There will be a new special page named PasswordPolicies. This page gives information about the password rules for each user group on that wiki. [7]
  • A new way to see moved paragraphs in diffs is coming to most wikis. This is to make it easier to find the moved paragraphs and the changes in them. [8]
  • Advanced item Wikis can enable Citoid to provide automatic reference look-up in the visual editor and the 2017 wikitext editor. This is complex. The tool will now disable itself if the configuration isn't correct. It has warned about this in the JavaScript console since February. Check that your wiki is configured correctly. You can ask for help if you need it. [9]
  • Planet Wikimedia collects blogs about Wikimedia. It will now use the Rawdog feed aggregator to do this instead of Planet. [10][11]
  • Redirect links in Special:WhatLinksHere now link to the original page and not the target page. This was done earlier and changed the used messages on some pages. This was a problem for wikis that customized the message. A new change fixed this by using the old messages with one more parameter for customization. Wikis that already changed their customized messages will have to move the customization back again. [12]
  • In the Wikipedia app for Android or iOS users can create reading lists. The reading lists can be seen on different devices if you are logged in to your account. There is now a browser extension so you can add pages to your reading list from a web browser. At the moment it works with Firefox and Chrome. [13]
  • Advanced item There is a new version of Pywikibot. Pywikibot is a tool to automate tasks on MediaWiki wikis. [14]
  • Advanced item PAWS, our JupyterHub system, got an upgrade and a logo. Several bugs should be fixed.
Problems
  • Some translatable pages are showing old translations instead of latest ones. The cause of this issue has been fixed. We will update all pages automatically to show the latest translations. [15]
  • When a link text was in italics or had other formatting you could sometimes not edit it in the visual editor. This has now been fixed. [16][17]
Future changes
  • It could become easier to reference different pages of a book in an article. [18]
  • Content Translation drafts which have not been updated in over a year will be removed. This allows other users to translate those articles. [19]
  • A survey is collecting information on what users think about how Wikimedia wiki pages are loaded. This information could be used in future development. [20]
  • Advanced item Wikis will switch to use the Remex parsing library. This is to replace Tidy. Wikis with fewer than 100 linter issues in the main namespace in all high-priority linter categories were switched on 30 May and 13 June. This included Wikidata. Tidy will probably be removed on all wikis in the first week of July. [21][22]
  • You will be able to move local wiki files to Commons and keep their original data intact. This is planned to come to the first wikis in June. The legacy tools should still work, as long as they are maintained (three of five are actually deprecated already). The new built-in feature will probably become the preferred method since it will keep the page history and file history intact, including the move to Commons (and who moved it).
  • Content translation users who use the translation dashboard to translate between any two of Arabic, English, French, Japanese and Russian will be asked to be part of a research project. This is to create better tools for translating articles. [23]
Meetings
  • Recurrent item Advanced item You can join the technical advice meeting on IRC. During the meeting, volunteer developers can ask for advice. The meeting takes place every Wednesday from 3 to 4 pm UTC. See how to join.

Installation code

Further information: Wikipedia:User scripts § How to install user scripts
  1. ^ Copy the following code, click here, then paste:
    importScript( 'User:Anomie/unsignedhelper.js' ); // Backlink: User:Anomie/unsignedhelper.js
  2. ^ Copy the following code, click here, then paste:
    importScript( 'User:Bellezzasolo/Scripts/arb.js' ); // Backlink: User:Bellezzasolo/Scripts/arb.js
  3. ^ Copy the following code, click here, then paste:
    importScript( 'User:Bellezzasolo/Scripts/ajaxrollsum.js' ); // Backlink: User:Bellezzasolo/Scripts/ajaxrollsum.js
  4. ^ Copy the following code, click here, then paste:
    importScript( 'User:Sam Sailor/Scripts/WRStitle.js' ); // Backlink: User:Sam Sailor/Scripts/WRStitle.js
  5. ^ Copy the following code, click here, then paste:
    importScript( 'User:Amorymeltzer/easyblock-modern.js' ); // Backlink: User:Amorymeltzer/easyblock-modern.js
  6. ^ Copy the following code, click here, then paste:
    importScript( 'User:Amorymeltzer/crathighlighter.js' ); // Backlink: User:Amorymeltzer/crathighlighter.js
  7. ^ Copy the following code, click here, then paste:
    importScript( 'User:Amorymeltzer/oldafd.js' ); // Backlink: User:Amorymeltzer/oldafd.js
← Previous "Technology report"
Next "Technology report" →
+ Add a comment

Discuss this story

These comments are automatically transcluded from this article's talk page. To follow comments, add the page to your watchlist. If your comment has not appeared here, you can try purging the cache.

When will we get responsive Vector? Lojbanist remove cattle from stage 20:01, 14 July 2018 (UTC)[reply]

Make sure we cover what matters to you — leave a suggestion.
Retrieved from "https://en.wikipedia.org/w/index.php?title=Wikipedia:Wikipedia_Signpost/2018-06-29/Technology_report&oldid=1193877725"