Hey everybody,
TL;DR: I wanted to let you know about an upcoming experimental Reddit AMA
("ask me anything") chat we have planned. It will focus on artificial
intelligence on Wikipedia and how we're working to counteract vandalism
while also making life better for newcomers.
We plan to hold this chat on June 1st at 21:00 UTC/14:00 PST in the /r/iAMA
subreddit[1]. I'd love to answer any questions you have about these topics
questions, and I'll send a follow-up email to this thread shortly before
the AMA begins.
----
For those who don't know who I am, I create artificial intelligences[2]
that support the volunteers who edit Wikipedia[3]. I've been fascinated by
the ways that crowds of volunteers build massive, high quality information
resources like Wikipedia for over ten years.
For more background, I research and then design technologies that make it
easier to spot vandalism in Wikipedia—which helps support the hundreds of
thousands of editors who make productive contributions. I also think a lot
about the dynamics between communities and new users—and ways to make
communities inviting and welcoming to both long-time community members and
newcomers who may not be aware of community norms. For a quick sampling of
my work, check out my most impactful research paper about Wikipedia[3],
some recent coverage of my work from *Wired*[4], or check out the master
list of my projects on my WMF staff user page[5], the documentation for the
technology team I run[9], or the home page for Wikimedia Research[8].
This AMA, which I'm doing with with the Foundation's Communications
department, is somewhat of an experiment. The intended audience for this
chat is people who might not currently be a part of our community but have
questions about the way we work—as well as potential research collaborators
who might want to work with our data or tools. Many may be familiar with
Wikipedia but not the work we do as a community behind the scenes.
I'll be talking about the work I'm doing with the ethics of AI and how we
think about artificial intelligence on Wikipedia, and ways we’re working to
counteract vandalism on the world’s largest crowdsourced source of
knowledge—like the ORES extension[6], which you may have seen highlighting
possibly problematic edits on your watchlist and in RecentChanges.
I’d love for you to join this chat and ask questions. If you do not or
prefer not to use Reddit, we will also be taking questions on ORES'
MediaWiki talk page[7] and posting answers to both threads.
1. https://www.reddit.com/r/IAmA/
2. https://en.wikipedia.org/wiki/Artificial_intelligence
2. https://www.mediawiki.org/wiki/ORES
3.
http://www-users.cs.umn.edu/~halfak/publications/The_Rise_and_Decline/halfa…
4.
https://www.wired.com/2015/12/wikipedia-is-using-ai-to-expand-the-ranks-of-…
5. https://en.wikipedia.org/wiki/User:Halfak_(WMF)
6. https://www.mediawiki.org/wiki/Extension:ORES
7. https://www.mediawiki.org/wiki/Talk:ORES
8. https://www.mediawiki.org/wiki/Wikimedia_Research
9. https://www.mediawiki.org/wiki/Wikimedia_Scoring_Platform_team
-Aaron
Principal Research Scientist @ WMF
User:EpochFail / User:Halfak (WMF)
Hello,
Welcome to the first in a reoccurring monthly update from the Reading
department at the Wikimedia foundation. Here we'll provide a quick summary
of things that are currently being worked on. An archive of past activity
can be found on Mediawiki.org. Feedback and questions are welcome.
== Web ==
=== New print styles for the mobile web ===
Based on the findings of the New Readers team, we learned that users are
increasingly getting information online, and then sharing or consuming it
offline. In terms of mobile devices, this often means taking screenshots of
useful information, or saving the article as a PDF to read later on their
phones. Our older print styles did not account for reading on mobile
devices - they focused on paper printing. We will update our print styles
for mobile devices to account for offline consumption, making them easier
to read and navigate, as well as accounting for missing crucial information
such as article title and branding.[0]
=== Moving the lead section before the infobox on the mobile web ===
Over the past few quarters, we've been focusing on the top of the article
experience on the mobile website. One of the identified issues was that,
for articles which contained an infobox, users were exposed to the infobox
content prior to having an overview of the subject of the article itself.
To improve on this issue, we've moved the lead section of each article so
that it appears before the infobox on mobile, allowing readers to have
access to the main content of the page earlier. This change is now live on
all projects. Before, [0] After [1]
=== Completing related pages deployment ===
Since March 30, 2017, we have been running a test on enwiki on the related
pages feature. Over the past month, we collected data and analyzed the
performance of the feature.[2] Based on the results, we completed the
deployment of the feature on mobile English Wikipedia.
== New Readers ==
* The New Readers team is deep in beginning pilots to address the barriers
that were identified as highest priority through deep research in 2016.[3]
You can see deeper, cross-team updates at m:New Readers/Updates. [4]
* For Reading, we're supporting the Android and Web teams in developing
deeper support for readers who have internet sometimes, but want access to
some content when they're offline or don't want to spend the data to read.
To see a summary of that work, check out m:New Readers/Offline.[5]
== Multimedia ==
* In addition to bugfixes and maintenance, the team has been evaluating the
pre-release version of 3D model file support and collecting feedback via
the Commons Village Pump.[6] During the forthcoming month the team will be
prioritizing and working on 3D tasks in anticipation of a future launch.[7]
== Other Noteworthy Stuff ==
* Following April's Q3 quarterly check-in, we examined core readership
metrics for the same timespan in a followup presentation.[8] [9]
[0]
https://www.mediawiki.org/wiki/Reading/Web/Projects/Print_Styles#Mobile_Pri…
[1]
https://www.mediawiki.org/wiki/File:Mobile_website,_older_version_of_infobo…
[2]
https://www.mediawiki.org/wiki/File:Lead_paragraph_before_infobox_example_-…
[3]
https://www.mediawiki.org/wiki/Reading/Web/Projects/Related_pages#Metrics_a…
[4] https://meta.wikimedia.org/wiki/New_Readers/Findings
[5] https://meta.wikimedia.org/wiki/New_Readers/Updates
[6] https://meta.wikimedia.org/wiki/New_Readers/Offline
[7]
https://commons.wikimedia.org/wiki/Commons:Village_pump/Archive/2017/05#Pre…
[8] https://phabricator.wikimedia.org/tag/3d/
[9]
https://www.mediawiki.org/wiki/File:Reading,_Comm_Tech_%26_TPG_Quarterly_Ch…
[10]
https://commons.wikimedia.org/wiki/File:Wikimedia_Foundation_Reading_metric…
---
The archive of all past updates can be found on MediaWiki.org:
https://www.mediawiki.org/wiki/Reading/Status_updates
Yours,
Chris Koerner
Community Liaison - Discovery
Wikimedia Foundation
https://www.mediawiki.org/wiki/Scrum_of_scrums/2017-05-31
*= 2017-05-31 =*
contact: https://www.mediawiki.org/wiki/Wikimedia_Engineering
== Call outs:==
* Security: status of TemplateStyles security review? (—from Reading eng.)
**its almost done. will be done end of this week at latest --bawolff
* Analytics: EventLogging purging script will be deployed before end of Q4.
Reminder: Default purging strategy for new schemas since July 2016 is
full purge after 90 days.
If you want new schemas sinc that date not to be fully purged after 90
days, please contact Analytics as soon as possible.
* RelEng: If you've committed something recently that may affect
performance, you maybe did affect performance: please check :) -
https://phabricator.wikimedia.org/T166345
=== Reading ===
==== iOS ====
* Last week
** 5.5 - https://phabricator.wikimedia.org/project/view/2602/
*** Places search updates: https://phabricator.wikimedia.org/T159733
*** Update `Top Read` feed design: https://phabricator.wikimedia.org/T165510
*** Places accessibility: https://phabricator.wikimedia.org/T159733
*** Other bug fixes & enhancements
* This week
** 5.5 - https://phabricator.wikimedia.org/project/view/2602/
*** Feature freeze, finish any remaining bug fixes & design tweaks
*** Regression testing
==== Android ====
* Bug identified last week causing stale content on the German WP main
page. Thanks to Arlo and the Parsoid crew for the quick fix.
* Beta release planned for late this week (for real). Finishing up final
tasks now.
* Next release will finalize the UI components for readling list syncing.
* New engineer hiring process is underway. (The new eng will replace
Stephen who is moving to Reading Web.)
* Current release board:
https://phabricator.wikimedia.org/project/view/2352/
* Next release board: https://phabricator.wikimedia.org/project/view/2763/
==== Multimedia ====
* Ongoing: Media Viewer improvements, bringing it in line with standards
that didn't exist when it was written
* Soon: 3D extension prioritization and fixes
* Current work is largely stalled due to hiring process
==== Web ====
* Commencing work on Electron PDF. (cc Ops)
* Clearing out backlog - with a focus on #wikimedia-log-errors (cc RelEngs)
==== Reading Infrastructure ====
* compiling Page Content Service Data Inventory for HTML endpoint
==== Wikidata ====
* attended Wikicite (after the hackathon)
* Wikidata build is broken due to CI - it runs composer update. need
someone to review jenkins-config change to add the ability to do composer
install instead:
** https://gerrit.wikimedia.org/r/#/c/354522/
* discussed at hackathon to move away from having the Wikidata build
entirely and put our libraries into mediawiki-vendor
==== Services ====
* Blockers: none
* Updates:
** Getting ready to test automatic RESTBase blacklisting
==== Security ====
* Reviews:
** psy/psysh use on WMF servers
** Verification of whitelisted.yaml / graylisted.yaml
=== Editing ===
==== Language ====
* No blockers. Not blocking.
* CX new change in wmf3: User can now choose article publish destination in
a better manner.
==== Parsing ====
* Waiting on the wmf2 train to roll out fully for some followup work /
updates.
* Linter patch to cache linter counts is still in review, but close to
being merged. Once that gets in, and it rolls out, we will be able to
re-enable linter on large wikis
* https://gerrit.wikimedia.org/r/#/c/72053/ introduces a piglatin language
variant for easier testing of language variant code. Needs reviews. Bartosz
might already be on it.
==== Collaboration ====
* Continued work on namespace and tag filters for RCFilters
* Followup and bug fixes on the new notification blacklist feature (now in
Beta Cluster)
* Working on tag validation for AbuseFilter
==== Analytics ====
* We found the issue in global unique devices count per top domain (*.
wikipedia.org),
fixed it and data looks good after vetting, will be productionized in
short.
* Ongoing: Webrequest Tagging (portal, pageviewAPI, etc.)
* Making progress on Wikistats2 front-end (stats.wikimedia.org replacement)
* CRing and testing EL purging script, we plan to deploy it before the end
of the quarter.
Reminder: Default purging strategy for new schemas since July 2016 is
full purge after 90 days.
==== UI Standardization ====
* This week:
** Preparing urgent v0.23.0 with OOjs v2.1.0 dependency, bug fixes and
further improvements around Promise-methods feat WindowManager
** Continuos work on style guide build process, semi-automated SVG export
* Updates:
** OOjs UI:
*** v0.22.0 released with 2 accessibility and several other (UI)
improvements, among those
**** Rename the 'MediaWiki' theme to 'WikimediaUI' for clarity on
development focus
**** WindowManager: Add `WindowInstance` - a Promise-based lifecycle object
(Timo Tijhof) and follow
**** Frameless button sizing equal framed ones is in
**** Passing ARIA tests from 13 up to 18
**** OOjs UI demos now with strengthened mobile experience, clearer
sectioning and in-demo widget code for copy & paster
=== Discovery ===
Meeting conflict, probably can't attend.
* No blockers, continuing the work from previous one
=== Fundraising Tech ===
* Civi / mailhouse integration
* Dead session debugging
* Fraud filter fixes
* Moving all DonationInterface queue code into library
* Preparing to move DonationInterface configuration code into library
* CentralNotice new features ready to deploy
=== RelEng ===
* Blocked
** MW 1.29 Release blocked on the tasks in:
https://phabricator.wikimedia.org/project/view/2400/
*** Lots to do with JobQueue and the Database
* Updates
** WARNING: Ops will be removing Salt near the end of next quarter, that
means no more Trebuchet as well. See
https://phabricator.wikimedia.org/T129290#3245438 for a list of things
still needing migration to scap3.
** wmf.2 train issues, if you've committed something recently that may
affect performance, you maybe did affect performance: please check :) -
https://phabricator.wikimedia.org/T166345
This is a reminder of today's RFC discussion about MediaWiki's database schema
for PostgreSQL. Tim proposes to make it more similar to our MySQL schema, to
reduce maintenance overhead and breakage
<https://phabricator.wikimedia.org/T164898>.
Rationale: The inconsistencies between the MySQL and PostgreSQL schemas cause a
constant maintenance burden. PostgreSQL support is frequently broken in master.
The PostgreSQL schema is certainly better than the MySQL one, if analyzed in
isolation, but the advantages to PostgreSQL users of having an improved schema
are more than outweighed by the disadvantages of inconsistency with the
remainder of the installed MediaWiki user base.
The discussion will take place on the #wikimedia-office channel on Freenode, at
21:00 UTC (2pm PDT, 23:00 CEST).
--
Daniel Kinzler
Principal Platform Engineer
Wikimedia Deutschland
Gesellschaft zur Förderung Freien Wissens e.V.
Extension:Math removed client side MathJax support after MW 1.25. This
makes setup of the Math extension considerably more difficult. Mathoid was
fairly straightforward, but RESTBase seems like it is much more
complicated. Is RESTBase a hard requirement? Is there any way to connect to
Mathoid directly, the way VE can connect to Parsoid directly?
Thank you,
James
Hey,
I'm excited to announce the new feature in wikilabels that allows people to
check progress of campaigns they are labeling.
Wikilabels [1] is a platform to gather human-labeled data so it can be used
on ORES [2]. You can find its home page in https://labels.wmflabs.org.
These data can be used in different AI models varying from fighting
vandalism to quality of items in Wikidata to anti-harassment models.
Until now, it was hard to get number of labels that is being made in each
campaign or understand how much work is left. But from now on by accessing
https://labels.wmflabs.org/stats and then going to your wiki you can have
these data. For example, go to https://labels.wmflabs.org/stats/enwiki/ and
it shows you progress of each campaign and how many labels are left to
consider it done or number of unique volunteers who are labeling.
Note that we are overhauling current paths of wikilabels to something
completely new because current paths are a little bit confusing and jump
around between GUI and API. So this URLs might change in the future [3] but
we will announce that properly beforehand and also make sure there is
redirect left from the old ones.
Any feedback about this feature would be greatly welcome. Feel free to
reach out to us in #wikimedia-ai at irc://irc.freenode.net or AI mailing
list. [4]
[1]: https://meta.wikimedia.org/wiki/Wiki_labels
[2]: https://www.mediawiki.org/wiki/ORES
[3]: https://phabricator.wikimedia.org/T165046
[4]: https://lists.wikimedia.org/mailman/listinfo/ai
Best
--
Amir Sarabadani Tafreshi, on behalf of Scoring platform team
Software Engineer (contractor)
-------------------------------------
Wikimedia Deutschland e.V. | Tempelhofer Ufer 23-24 | 10963 Berlin
http://wikimedia.de
Wikimedia Deutschland - Gesellschaft zur Förderung Freien Wissens e.V.
Eingetragen im Vereinsregister des Amtsgerichts Berlin-Charlottenburg unter
der Nummer 23855 B. Als gemeinnützig anerkannt durch das Finanzamt für
Körperschaften I Berlin, Steuernummer 27/681/51985.
I'd like to highlight two videos (some people may have already seen these)
that demo upcoming changes to edit review / RC patrol that take advantage
of ORES. I feel that that the changes look promising, and I hope that RC
patrollers, Teahouse hosts, newbie adopters, and others will find that the
changes make their work easier. I also hope for improved retention of
good-faith contributors.
0. A succinct overview by Joe Matazzoni (WMF):
https://commons.wikimedia.org/w/index.php?title=File%3ANew-feature_demo%E2%…
1. A more extensive overview, also by Joe, including valuable context, from
the WMF Metrics Meeting for May 2017:
https://www.youtube.com/watch?v=rAGwQdLyFb4 between 15:00 and 28:15.
Pine
