Wikitech-l September 2015

wikitech-l@lists.wikimedia.org

126 participants
104 discussions

A couple videos: Parsoid with Reading Engineering; Reading Showcase 20150824

by Adam Baso

Hi all, Just wanted to share a couple recent videos. Enjoy! == Parsoid with Reading == https://youtu.be/3WJID_WC7BQ?t=14 C. Scott Ananian and Subbu Sastry from the Wikimedia Foundation provide an overview of Parsoid, a Wikimedia technology that supports HTML to wikitext (and vice versa) translation, supporting rich annotated output markup for translation layers and other clients (e.g., Wikipedia related technology) to more specifically query elements from wiki content. You may have caught some of this material at Wikimania, or maybe this is your first time. In any event, it's good stuff! This was an interactive session with questions from Wikimedia Reading Engineering. == Reading Showcase 20150824 == https://youtu.be/F9ExzUaRI0k About every 4 weeks the Wikimedia Reading department gets together to showcase experiments and works in progress and the like. This is the session from 24-August-2015. -Adam

8 years, 7 months

thumb generation

by wp mirror

0) Context I am currently developing new features for WP-MIRROR (see < https://www.mediawiki.org/wiki/Wp-mirror>). 1) Objective I would like WP-MIRROR to generate all image thumbs during the mirror build process. This is so that mediawiki can render pages quickly using precomputed thumbs. 2) Dump importation maintenance/importDump.php - this computes thumbs during importation, but is too slow. mwxml2sql - loads databases quickly, but does not compute thumbs. 3) Question Is there a way to compute all the thumbs after loading databases quickly with mwxml2sql? Sincerely Yours, Kent

8 years, 7 months

Tools for dealing with citations of withdrawn academic journal articles

by Pine W

Is there any easy way to find all of citations of specified academic articles on Wikipedias in all languages, and the text that is supported by those references, so that the citations of questionable articles can be removed and the article texts can be quickly reviewed for possible changes or removal? See https://www.washingtonpost.com/news/morning-mix/wp/2015/08/18/outbreak-of-f… If we don't have easy ways to deal with this (and I believe that we don't), I'd like to suggest that the Community Tech team work on tools to help when these situations happen. Thanks, Pine

8 years, 7 months

Link: useful article on in-person events

by Frances Hocutt

An excellent article on best practices and pitfalls for in-person technical events: https://modelviewculture.com/pieces/software-in-person This has some ideas and framings that can be useful for planning for the upcoming developer summit. -Frances

8 years, 7 months

Super-charging Mobile: An experiment with ServiceWorkers in MediaWiki

by Jon Robson

Sam asked me to write up my recent adventures with ServiceWorkers and making requests for MediaWiki content super super fast so all our lovely users can access information quicker. Right now we're trying to make the mobile site ridiculously fast by using new shiny standard web technologies. The biggest issue we have on the mobile site right now is we ship a lot of content - HTML and images - since we ship those on desktop. On desktop it's not really a problem from a performance perspective but it may be an issue from a download perspective if you have some kind of data limit on your broadband and you are addicted to Wikipedia. The problem however is that on mobile, the connection speeds are not quite up to desktops standard. To take an example the Barack Obama article contains 102 image tags and 186KB of HTML resulting in about 1MB of HTML. If you're on your mobile phone just to look up his place of birth (which is in the lead section) or to see the County results of the 2004 U.S. Senate race in Illinois [1] that's a lot of unnecessary stuff you are forced to load. You have to load all the images and all the text! Owch! Gilles D said a while back [2] "The Barack Obama article might be a bit of an extreme example due to its length, but in that case the API data needed for section 0's text + the list of sections is almost 30 times smaller than the data needed for all sections's text (5.9kb gzipped versus 173.8kb gzipped)." Somewhat related, some experimenting with webpagetest.org has suggested that disabling images on this page has a serious impact on first paint (which we believe is due to too many simultaneous connections) [3,4] Given that ServiceWorker is here (in Chrome first [5] but hopefully others soon) I wrote a small proof of concept that lazy loads images to expose myself to this promising technology. For those interested I've documented my idea here: https://en.m.wikipedia.org/wiki/User:Jdlrobson/lazyloader but basically what is does is: 1) intercept network requests for HTML 2) Rewrites the src and srcset attributes to data-src and data-srcset attributes 3) Uses JavaScript to lazy load images when they appear in the screen. 4) Without JS the ServiceWorker doesn't run so the web remains unbroken (But as Jake Archibald points out though there are downsides to this approach [6].) It doesn't quite work as a user script due to how scope works in service workers but if we want to use these in production we can use a header [7] to allow use of scope: '/' so if we wanted to do this in production there's no real problem with that, but we will have to ensure we can accurately measure that... [8] A more radical next step for ServiceWorkers would be to intercept network requests for HTML to use an API to serve just the lead section [9]. This won't help first ever loads from our users, but it might be enough to get going quickly. If we want to target that first page load we need to really rethink a lot of our parser architecture.... fun times. Would this be a good topic to bring up in January at the dev summit? [1] https://en.m.wikipedia.org/wiki/Barack_Obama#/media/File:2004_Illinois_Sena… [2] https://phabricator.wikimedia.org/T97570 [3] https://phabricator.wikimedia.org/T110615 [4] https://phabricator.wikimedia.org/T105365#1477762 [5] https://jakearchibald.com/2014/using-serviceworker-today/ [6] https://twitter.com/jaffathecake/status/644168091216310273 [7] https://gerrit.wikimedia.org/r/#/c/219960/8/includes/resourceloader/Resourc… [8] https://phabricator.wikimedia.org/T112588 [9] https://phabricator.wikimedia.org/T100258

8 years, 7 months

Video: updated support for VP9, Opus source media

by Brion Vibber

Thanks to Giuseppe in ops & a bunch of other folks who have helped out, we've got an updated server configuration for the 'video scalers' that generate media transcodes, supporting VP9 video and Opus audio. Initially we have one server updated and in production, and the rest should follow by tomorrow. (Updated servers are also in place on the beta cluster.) This should make it possible for WebM files using VP9 video and/or Opus audio to work as fully first-class citizens in TimedMediaHandler, generating medium- and low-resolution transcodes in Ogg and WebM VP8. It should also fix Ogg audio files using the Opus codec to work consistently. Support for generating VP9 transcodes as well is in the code and just needs to be switched on -- I'll tweak that configuration once we've got the rest of the servers upgraded and have more capacity for batch runs. (I've got a client-side bot which I'll start once that's ready, to force all the files to generate over time.) -- brion

8 years, 7 months

2015-09-16 Scrum of Scrums meeting notes

by Grace Gellerman

https://www.mediawiki.org/wiki/Scrum_of_scrums/2015-09-16

8 years, 7 months

Collapsible content

by Legault, Phillip [ITSUS]

MediaWiki 1.23.8 I'm using collapsible content for a User Guide page, and there are a lot of sections. So I set each section with one heading and collapsed default. I added the following CSS simple works fine. :target { color: red; } I’m trying to do something with JQUERY with pseudo class :target to expand the selected and if I provide a link it will expand the section as well. I have been searching and still haven’t found anything that works. Any help would be appreciated Thanks! Phil

8 years, 7 months

[x-post] Reminder: Language Engineering Office Hour is on September 16, 2015 (today) at 1500 UTC

by Runa Bhattacharjee

Hello, A reminder that the online office hour hosted by the Wikimedia Language Engineering team is scheduled for later today at 1500 UTC. You can join the hangout or watch the session from: https://plus.google.com/u/0/events/c1c0msurhua7enopsu3q8l42j3s Please note, due to the limitation of Google Hangouts there are few seats available. So do let us know before hand if you would like to participate on the hangout. We will also be on the IRC channel #wikimedia-office to take questions. Please see below for the event details, local time and original announcement. Thanks Runa == Details == # Event: Wikimedia Language Engineering office hour session # When: September 16th, 2015 (Wednesday) at 15:00 UTC (check local time http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150916T1500) # Where: https://plus.google.com/u/0/events/c1c0msurhua7enopsu3q8l42j3s and on IRC #wikimedia-office (Freenode) # Agenda: Content Translation updates and Q & A ---------- Forwarded message ---------- From: Runa Bhattacharjee <rbhattacharjee(a)wikimedia.org> Date: Tue, Sep 8, 2015 at 5:21 PM Subject: Language Engineering office hour and online meeting on 16 September 2015 (Wednesday) at 1500 UTC To: Wikimedia developers <wikitech-l(a)lists.wikimedia.org>, MediaWiki internationalisation <mediawiki-i18n(a)lists.wikimedia.org>, "Wikimedia & GLAM collaboration [Public]" <glam(a)lists.wikimedia.org>, Wikimedia Mailing List <wikimedia-l(a)lists.wikimedia.org> [x-posted announcement] Hello, The next office hour of the Wikimedia Language Engineering team is scheduled for next Wednesday, September 16th at 15:00 UTC. Like our last office hour, this time also we are hosting it as an online discussion over Hangout/Youtube with a simultaneous IRC conversation. Due to the limitation of Google Hangouts, only a limited number of slots are available. Hence, do let us know (on the event page <https://plus.google.com/u/0/events/c1c0msurhua7enopsu3q8l42j3s>) if you would like to participate on the Hangout. The IRC channel #wikimedia-office and the Q&A channel for the youtube broadcast will be open for interactions during the session. Our last online round-table session was held in June 2015. You can watch the recording here: https://www.youtube.com/watch?v=vbXyHmpZJGE Please read below for the event details and do let us know if you have any questions. Thank you Runa == Details == # Event: Wikimedia Language Engineering office hour session # When: September 16th, 2015 (Wednesday) at 15:00 UTC (check local time http://www.timeanddate.com/worldclock/fixedtime.html?iso=20150916T1500) # Where: https://plus.google.com/u/0/events/c1c0msurhua7enopsu3q8l42j3s and on IRC #wikimedia-office (Freenode) # Agenda: Content Translation updates and Q & A -- Language Engineering Manager Outreach and QA Coordinator Wikimedia Foundation

8 years, 7 months

Understanding weird behaviour of diffto in API

by Petr Bena

I am trying to understand how this works: https://www.mediawiki.org/wiki/API:Revisions There is a parameter DiffTo which says: Revision ID to diff each revision to. Use "prev", "next" and "cur" for the previous, next and current revision respectively. I suppose that I can give it revision ID instead of that string hint. So let's say we have 4 edits made to the page [[X]], their ID's are: * 520 * 510 * 20 * 1 Now I want to create a diff of last three changes, so that I see what has changed from revision 20 until revision 520 INCLUDING these 2 revisions, that means, I want to see all changes that were made in 20, 510 and 520 up to the current version. I suppose in that case I would set RevID to 520 and DiffTo to 20. That however doesn't seem to work. It shows the diff, but other way, it shows diff from 520 to 20 (and I think it even excludes that revision) not from 20 to 520, including both 20 and 520. How does the whole thing actually work? I might need something like "DiffFrom" when I think of that, but there is no such a thing. Even more weird thing that happens to me, is that when I swap RevID and DiffTo, the results seem to be identical.

8 years, 7 months

← Newer
1
2
3
4
5
6
7
8
9
10
11
Older →

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

Wikitech-l September 2015