The Signpost

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:

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
Problems
Future changes
Meetings

Installation code

  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
S
In this issue
+ Add a comment

Discuss this story

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




       

The Signpost · written by many · served by Sinepost V0.9 · 🄯 CC-BY-SA 4.0