[00:07:54] awjr: http://commons.wikimedia.org/wiki/File:Sasaasassa.jpg < can you delete this [00:07:59] accidentally uploaded from test wiki [01:10:51] jdlrobson: looks like someone beat me to it [04:21:44] New patchset: Siebrand; "Maintenance for MobileFrontend." [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/24261 [04:51:25] New review: Jdlrobson; "Cheers for this Siebrand. A few comments." [mediawiki/extensions/MobileFrontend] (master) C: -1; - https://gerrit.wikimedia.org/r/24261 [06:53:25] New review: Siebrand; "Different people have different opinions, apparently. I've had multiple other "code owners" request ..." [mediawiki/extensions/MobileFrontend] (master); V: 0 C: 0; - https://gerrit.wikimedia.org/r/24261 [06:53:46] New patchset: Siebrand; "Maintenance for MobileFrontend." [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/24261 [16:52:25] MaxSem: is "did you mean?" the same as spelling corrections? https://bugzilla.wikimedia.org/show_bug.cgi?id=36712 ie. is this done? [16:53:02] I mean https://en.wikipedia.org/w/index.php?title=Special%3ASearch&search=rusia&fulltext=Search [16:53:35] ahh ok cool [16:53:39] I'll add a story then :) [16:55:00] in the terminology of action=query&list=search, it's a "suggestion" [16:55:51] sure [16:59:40] MaxSem: https://plus.google.com/hangouts/_/431f87ccc1687de7f6fb35c4dd6958d919e6b81b?ssc=eyJCIjpbbnVsbCxudWxsLG51bGwsbnVsbCxudWxsLG51bGwsbnVsbCxudWxsLG51bGwsbnVsbCxudWxsLG51bGwsbnVsbCxudWxsLG51bGwsbnVsbCxudWxsLG51bGwsW11dLCJPIjpbbnVsbCxudWxsLG51bGwsbnVsbCxudWxsLFtdLG51bGwsbnVsbCxudWxsLG51bGwsbnVsbCxudWxsLG51bGwsbnVsbCxudWxsLG51bGwsbnVsbCxudWxsLFtdLG51bGxdfQ%3D%3D&authuser=0&hl=en-US [17:00:22] wow, this time the ling is muchmuch longer [17:00:48] hangout link? [17:00:57] https://plus.google.com/hangouts/_/431f87ccc1687de7f6fb35c4dd6958d919e6b81b?ssc=eyJCIjpbbnVsbCxudWxsLG51bGwsbnVsbCxudWxsLG51bGwsbnVsbCxudWxsLG51bGwsbnVsbCxudWxsLG51bGwsbnVsbCxudWxsLG51bGwsbnVsbCxudWxsLG51bGwsW11dLCJPIjpbbnVsbCxudWxsLG51bGwsbnVsbCxudWxsLFtdLG51bGwsbnVsbCxudWxsLG51bGwsbnVsbCxudWxsLG51bGwsbnVsbCxudWxsLG51bGwsbnVsbCxudWxsLFtdLG51bGxdfQ%3D%3D&authuser=0&hl=en-US [17:01:09] damn [17:01:11] that is long [17:05:52] [WLMMobile] brion pushed 2 new commits to master: http://git.io/kHg5BQ [17:05:52] [WLMMobile/master] don't add desktop upload category to every upload - jdlrobson [17:05:52] [WLMMobile/master] Merge pull request #261 from jdlrobson/uploadproblem - Brion Vibber [17:06:04] Project WLMMobile - Nightly builds build #235: SUCCESS in 8.1 sec: https://integration.mediawiki.org/ci/job/WLMMobile%20-%20Nightly%20builds/235/ [17:18:49] [WLMMobile] brion pushed 2 new commits to master: http://git.io/7eEQWA [17:18:49] [WLMMobile/master] dynamically load latest messages from github - jdlrobson [17:18:49] [WLMMobile/master] Merge pull request #260 from jdlrobson/dynamic-i18n - Brion Vibber [17:18:56] Project WLMMobile - Nightly builds build #236: SUCCESS in 6.3 sec: https://integration.mediawiki.org/ci/job/WLMMobile%20-%20Nightly%20builds/236/ [17:18:57] jdlrobson: dynamically load latest messages from github [17:36:32] brion: so the WLM error is pretty straight forward [17:36:57] the app is using the using the Android default API for stream decoding [17:37:25] so you can easily get an OutOfMemory exceptions while loading big image files [17:37:57] *nod* [17:38:10] it looks like there is a patch to decode image size without loading all data into memory [17:38:24] I don't know it's status or how old it is but http://mail-archives.apache.org/mod_mbox/incubator-callback-dev/201205.mbox/%3C2112207549.53830.1336728714149.JavaMail.tomcat@hel.zones.apache.org%3E [17:38:56] well, we end up loading the image into an so if that first load is going to crash it... [17:39:07] it's based on https://issues.apache.org/jira/browse/CB-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13273136 [17:41:38] brion: does the app use DATA_URI ? [17:41:45] no, we use FILE_URI [17:58:57] brion, MaxSem: https://plus.google.com/hangouts/_/2e43aba64f2c3557ae225d6e1965e5aa08e1929c?pqs=1&authuser=0&hl=en [18:00:41] MaxSem, brion, jdlrobson, philinje: http://etherpad.wikimedia.org/wlm-project-retro [18:01:29] jdlrobson: grab tomasz if you see him on your way up to r66 [18:02:00] ahh upstairs [18:10:24] MaxSem, jdlrobson, brion: http://etherpad.wikimedia.org/wlm-project-retro [18:14:27] tfinc: http://etherpad.wikimedia.org/wlm-project-retro [19:51:56] brion: i've been thinking about responsive images for non-javascript users and that initial load [19:52:04] yeah? [19:52:12] what if we served images as links… where the href is the image and the text of the a tag is the alt text [19:52:19] then in javascript substituted those [19:52:29] hmmm [19:52:42] obvious problem with that is api clients that aren't expecting this [19:52:46] they'll get no images [19:53:06] you mean in MF not API right? [19:53:06] api clients? [19:53:10] yeh in MF [19:53:23] hmm [19:53:24] responsive images stuff you've been doing.. [19:53:48] that way the images are accessible and if someone has disabled javascript it's probably to do with reducing page load and wanting to emphasize on text any how.. [19:54:27] the text could even be a generic photo placeholder with alt text wrapped in a link [19:54:34] just thinking how we can do that, expose the same information to api clients, and not break api clients that don't know about it [19:54:36] at least that way it's clearer there is suppose to be an image there [19:56:35] i was also thinking of adding a mobile option for high-res images so you can switch it off and see the low-res images [19:56:57] brion that sounds like step 3 (the one before profit ;-)) [19:57:04] :D [19:57:49] can we also disable cleanup templates… pleeeeaase? :) [19:58:09] sure, just clean them up and delete the templates >:) [19:58:24] Or since we have Mobile.css now (I think?) we can hide them there :D [19:58:50] personally i think those are important parts of how we communicate that wikipedia is a living document [19:58:56] but that seems to be a minority opinion ;) [19:58:58] they're just so huge on mobile. might as well be a sopa blackout screen, except it's bright colors and looks scary and broken [19:59:06] hehe [19:59:17] i think the idea of them is good, but the way they're currently executed is… not so much [19:59:20] perhaps some styling middle ground can be sought [19:59:29] why does https://en.wikipedia.org/wiki/MediaWiki_talk:Mobile.css show me talk for common.css? [19:59:49] yuvipanda: (Redirected from MediaWiki talk:Mobile.css) [20:00:01] yeah, I wonder why that's a redirect [20:00:17] probably to keep all the discussion in one place, avoid fragmentation and forgotten questions [20:00:25] Maryana: I'll write you a story for them [20:00:40] jdlrobson: you are the master storywriter [20:01:09] jdlrobson: all these transformations would be easier if we had stuff in DOM all the time instead of HTML strings. :P [20:01:28] btw, i spend a ridiculous amount of time last night trying to find a dalek macro onto which i could insert the phrase "PRODUCT SHALL REMAIN SILENT!" [20:01:31] … i failed. [20:01:42] :)) [20:01:56] oh btw, iOS and mac os x updates out now. updates yer machines wheeeeeee [20:02:07] and a billion app updates for iOS 6 or iPhone 5 compatibility. yay [20:03:16] brion: you should check the wikipedia app on it :) [20:03:27] From past experience that's probably the wrong smiley to use there [20:03:51] yuvipanda: runs fine on ios6 so far, but on iPhone 5 it'll be letterboxed until we release a fix [20:03:58] fix is in pulls :) [20:04:17] oh great, i have to update Xcode. that's gonna be a fast download [20:04:42] ah, sweet [20:04:51] now I must really sleep if I want to cycle 15km at 7am [20:05:21] Xcode download's bigger than the mac os x update :P [20:06:43] ok… already updated the iPod touch. updating the iPad 3 now… iPad 1 won't get the update, and iPhone 3gs is being kept at 4.3 for compat testing. whee [20:07:33] and my galaxy tab 10.1 FINALLY got its android 4.0.4 update! [20:08:04] brion: have a question for you about the WLM app? [20:08:11] Yay for quick Xoom updates ;) [20:08:13] ask away [20:08:29] can you tell me the URLs we access? [20:08:35] ah the most important app to update: robot unicorn attack now compatible with android 4 [20:08:50] philinje: lemme pull up the list [20:09:09] all the base urls should be in: https://github.com/wikimedia/WLMMobile/blob/master/assets/www/js/config.js [20:09:26] we have our monument API, we access Wikipedia, and Commons, and map quest, right? [20:09:32] ok cool [20:09:37] BLOCKING_POLICY and SIGNUP_PAGE are just links [20:09:51] and…. looks like we don't have the map quest tile url in that list but yes that's one additional [20:09:56] Orange is thinking about zero-rating the app in Europe [20:10:09] brion: no! nyancat lost in space! :-P [20:10:51] hmm, what about Mapquest? [20:11:01] phlemme pull up the base url for it [20:11:20] var tiles = new L.TileLayer('http://otile{s}.mqcdn.com/tiles/1.0.0/osm/{z}/{x}/{y}.png', { [20:11:40] so otile1.mqcdn.com, otile2.mqcdn.com, otile3.mqcdn.com, otile4.mqcdn.com [20:11:40] ok, the curly brackets are variables? [20:11:45] yeah [20:12:01] super, thanks [20:12:46] and the Wikipedia access is for the article links? [20:14:28] yeah… we do go to https://*.wikipedia.org/w/api.php for article existence checks [20:14:47] oh -- and where you see test.wikipedia.org, we use commons.wikimedia.org in the real app :) [20:15:37] ok, what is this for: WIKIPEDIA: 'https://$1.wikipedia.org' [20:16:26] philinje: looks like that's just a link to Wikipedia on the about page [20:17:15] ok, so in reality we only go to WIkipedia for the API to check article existence? [20:17:21] looks like yeah [20:18:13] awesome [20:18:18] jdlrobson: that reminds me we need to think about opera mini [20:18:27] rumor is it's reasonably widely used, especially for asian languages [20:18:27] brion: opera mini? [20:18:46] currently we blacklist it from javascript support i think since it's a bit flaky (weird server-side handling) [20:18:53] we probably don't want to break images on it... [20:19:03] wonder if we need to do separate rendering for it vs jquery-capable browsers [20:21:31] though it may have improved over time… it might actually be able to handle stuff now. i wonder... [20:22:25] brion: sorry, does WIKI_API: 'https://test.wikipedia.org/w/api.php' [20:22:42] become COMMONS_API: 'https://commons.wikimedia.org/w/api.php' [20:22:49] yeah [20:23:04] and what about this: WIKI_BASE: 'https://test.wikipedia.org/wiki/' [20:23:17] same, but that's just used for links [20:23:35] oh, and of course we load images from https://upload.wikimedia.org/... [20:23:46] ah, right [20:25:50] sorry, by links do you mean we get them from the Commons API? [20:26:34] WIKI_BASE is where we append the page name to get a link, like to existing images [20:26:56] "Xcode failed to download" bah [20:28:03] aha, if i just move in the copy i already downloaded it's happy with that [20:28:10] gotta reboot for updates, brb [20:32:37] while that's going, luckily i have a million computers [20:41:50] brion: if you have a sec, you might want to check the email I just sent AMit [20:42:42] philinje: looks good [20:50:14] off to update more devices [20:50:23] will peek in later & update stuff on the retina patches [23:48:41] New patchset: Siebrand; "Maintenance for MobileFrontend." [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/24261