[00:08:01] philinje: for the contact-browser would you want to break them up by projects ? [00:08:11] or keep it high level [00:08:44] New patchset: Jdlrobson; "allow user to switch site-wide language from the settings page" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/10452 [00:09:07] tfinc: good point [00:10:16] i guess there won't be much technical variation between project sites, so they could be treated with one address [00:13:29] New patchset: Jdlrobson; "allow user to switch site-wide language from the settings page" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/10452 [00:19:35] philinje: we won't know if there is until we do the commons migration [00:19:40] so its tough to say [00:19:49] i find it interesting that most mobile sites on the net do not collect feedback [00:19:58] philinje: what sites have you seen that collect feedback ? [00:23:42] tfinc: seems like an under-used option, but that is true on the web and in every kind of product [00:30:14] New patchset: Jdlrobson; "only serve contact-us.css on Special:MobileFeedback (bug 37716)" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/13102 [00:32:59] philinje: i made some changes on http://www.mediawiki.org/wiki/Mobile/Feedback#Next_steps .. most people seem to avoid case distinctions with their contact address. [00:34:11] i decided to get rid of the proposed otrs list and suggested moving it to mobile-feedback-l [00:34:38] and redirecting anything anything coming in for mobile@wikipedia -> mobile-feedback-l [00:34:41] thats one less list then [00:36:11] New patchset: Jdlrobson; "more prominent configuration message" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/13104 [00:36:12] ok [08:08:05] finally! [08:08:08] * yuvipanda goes to check logs [08:40:43] Project WikipediaMobile - Nightly builds build #353: SUCCESS in 28 sec: https://integration.mediawiki.org/ci/job/WikipediaMobile%20-%20Nightly%20builds/353/ [08:40:44] * tommy: Clean up ReadItLater plugin attribution comments [08:40:44] * yuvipanda: Removed stray entry in plugins.xml [08:40:45] * yuvipanda: Make default language for search be the system's default locale [08:40:45] * yuvipanda: Added migration code for PhoneGap database issues [08:40:46] * yuvipanda: Updated CHANGELOG and bumped version number [08:40:46] * yuvipanda: Added comments clarifiying data migration [08:40:47] * yuvipanda: Added clarification on language fix [08:40:47] * yuvipanda: Move WebKit settings to proper location. [08:40:48] * yuvipanda: Bumped version number for iOS [08:40:48] * jdlrobson: Fixed #35431 [08:40:49] * jdlrobson: Fixed sections bug [08:40:49] * jdlrobson: Some style fix according with styling guidelines [08:40:50] * niklas.laxstrom: Translation updates from translatewiki.net [08:40:50] * brion: bug 35710 - about page links now open in external browser [08:40:51] * brion: Bug 35734 - Update iOS splash screen images [08:40:51] * brion: Bug 35741 - iOS save/share menu should offer to open page in Safari [08:40:52] * piotrowski: Format README.md to make it pretty (no content changes) [08:41:03] * yuvipanda: Make Language Links work via the API [08:41:03] * yuvipanda: Fixes to make loading read-in not painful [08:41:04] * yuvipanda: Add tracking code to use clicktracking for saved pages [08:41:04] * yuvipanda: Selectively make iOS 4.2 use HTTP [08:41:05] * yuvipanda: Hide keyboard once search item has been clicked [08:41:05] * yuvipanda: UIWebView doesn't like upper case HTTP. Needs lower case [08:41:06] * yuvipanda: Fix issue with scrolling past bottom on iOS 4.x [08:41:06] * yuvipanda: Move to iScroll-lite [08:41:07] * yuvipanda: Reset scroll to top on opening new pages [08:41:07] * yuvipanda: Reduce timeout in doFocusHack [08:41:08] * yuvipanda: Search doesn't start autocompleting until you stop typing [08:41:08] * yuvipanda: Do not crash when using twitter on pre 5.0 devices [08:41:09] * yuvipanda: Hide navbar when in overlays [08:41:09] * yuvipanda: Show feedback when saving pages on iOS [08:41:10] * yuvipanda: Stop lines from being cut off at bottom of content [08:41:10] * yuvipanda: Bug 35741 - iOS save/share menu should offer to open page in Safari [08:41:11] * yuvipanda: Decrease search typeahead timeout [08:41:11] * yuvipanda: Fix content being cut off on iPad [08:41:23] * yuvipanda: No more zepto. [08:41:23] * yuvipanda: Fix 'things disappear when scrolling' bug (#35779) [08:41:24] * yuvipanda: Enable 'Read in' for iOS [08:41:24] * yuvipanda: More workarounds for bug #35779 [08:41:25] * yuvipanda: Use typeof as an operator rather than as a function [08:41:25] * yuvipanda: Stop using .attr, use .data instead [08:41:26] * yuvipanda: Updated README [08:41:26] * yuvipanda: Rewrote search.js to not use network.js [08:41:27] * yuvipanda: Removed reference to network.js [08:41:27] * yuvipanda: Get rid of `make remotes` since we're now using a submodule [08:41:28] * yuvipanda: Cleanup + scope fixes for prior search fixes [08:41:28] * yuvipanda: Add the hacks css to the app [08:41:29] * yuvipanda: Show title at start of page [08:41:29] * yuvipanda: Remove extra network.js call in android platform [08:41:30] * yuvipanda: Get rid of some completely unnecessary console.logs [08:41:30] * yuvipanda: Removed MobileFrontend patch files (no longer needed) [08:41:31] * yuvipanda: update README file for development in browser [08:41:31] * yuvipanda: fix toggling to also add class to sections [08:41:43] * niklas.laxstrom: Localisation updates from http://translatewiki.net. [08:41:43] * yuvipanda: Don't reset scroll when not needed [08:41:44] * yuvipanda: Removed unneccessary .empty() calls [08:41:44] * yuvipanda: Fix Page actions not showing up on iOS [08:41:45] * brion: Tweak to index.html [08:41:45] * brion: Update WinPhone to cordova 1.6.1 [08:41:46] * brion: fix styles, scrolling, show/hide section icons for WinPhone [08:41:46] * brion: Fix message, sitematrix load on winphone [08:41:47] * brion: Update Windows Phone tile & icon [08:41:47] * brion: Add solid color fallbacks to gradients for Windows Phone [08:41:48] * brion: bug 36256: handle back button on Windows Phone 7 [08:41:48] * yuvipanda: Updated to latest version of MobileFrontend [08:41:49] * yuvipanda: Remove extra button in section headers [08:41:49] * jdlrobson: when toggling add openSection class to button [08:41:50] * yuvipanda: Fastclick for all menu items [08:41:50] * yuvipanda: Replace doFocusHack with more descriptive setupFastClick [08:41:51] * yuvipanda: Make search focus properly [08:41:51] * yuvipanda: suggested amendments to STYLE_GUIDELINES [08:42:03] * jdlrobson: Clean up langlinks to use app.navigateTo [08:42:03] * jdlrobson: Notify when saving is done [08:42:04] * yuvipanda: Made headings in CHANGELOG consistent [08:42:04] * yuvipanda: Updated version numbers and added CHANGELOG [08:42:05] * yuvipanda: Make pages work for other languages, rather than just default [08:42:05] * yuvipanda: Rename beta_common.css to common.css [08:42:06] * yuvipanda: Separate RTLness for UI language and content language [08:42:06] * yuvipanda: Sort languages in settings in Unicode order [08:42:07] * yuvipanda: Sort langlinks by unicode order & set proper direction [08:42:07] * yuvipanda: Do not display aricle title in 'Read In' overlay [08:42:08] * yuvipanda: Remove stray global assignment (was used for debugging) [08:42:08] * s.mazeland: Localisation updates from http://translatewiki.net. [08:42:09] * s.mazeland: Localisation updates from http://translatewiki.net. [08:42:09] * jdlrobson: Fix reference display not dismissing when user taps outside it [08:42:10] * jdlrobson: Fix scrolling in search results, history and lang links on iOS4.x [08:42:10] * jdlrobson: Disable Animation for Reference Reveal [08:42:11] * jdlrobson: No transitions when toggling [08:42:11] * jdlrobson: Hide citation backlinks [08:42:23] * yuvipanda: Handle links in reference reveal display properly [08:42:23] * brion: remove old Windows 8 Metro project [08:42:24] * brion: Add stub Windows 8 Metro app [08:42:24] * brion: Stub localization support for Windows 8 Metro app [08:42:25] * brion: mark some js files with UTF-8 BOM to pass Windows 8 validation [08:42:25] * s.mazeland: Localisation updates from http://translatewiki.net. [08:42:26] * brion: win8: fix l10n regression [08:42:26] * brion: Win8: fixes for snapped mode [08:42:27] * yuvipanda: Removed Share to Read It Later from iOS App [08:42:27] * brion: Win8: snapped mode fixes, listview fixes [08:42:28] * brion: win8: basic offline detection [08:42:28] * brion: win8: adjust padding in snapped view [08:42:29] * brion: Stub promotional images for win8 store [08:42:29] * yuvipanda: Perform migration for outdated saved pages on app launch [08:42:30] * yuvipanda: URLEncode the title when it is part of the API Url [08:42:30] * yuvipanda: Added an option to suppress success message on page save [08:42:31] * yuvipanda: Hide migration overlay only after main page has loaded [08:42:31] * yuvipanda: Handle failure of updating saved pages on startup [08:42:43] * pfhayes: Localisation updates from http://translatewiki.net. [08:42:43] * pfhayes: Localisation updates from http://translatewiki.net. [08:42:44] * pfhayes: Localisation updates from http://translatewiki.net. [08:42:44] * pfhayes: Bumping version numbers [08:42:45] * pfhayes: Fixing url intents [08:42:45] * pfhayes: Allows opening main page [08:42:46] * pfhayes: Links on license. Fixes #34030 [08:42:46] * pfhayes: Localisation updates from http://translatewiki.net. [08:42:47] * pfhayes: Localisation updates from http://translatewiki.net. [08:42:47] * pfhayes: Localisation updates from http://translatewiki.net. [08:42:48] * pfhayes: Localisation updates from http://translatewiki.net. [08:42:48] * pfhayes: Bumping version numbers [14:20:02] New review: MaxSem; "(no comment)" [mediawiki/extensions/MobileFrontend] (master); V: 0 C: -1; - https://gerrit.wikimedia.org/r/10452 [14:35:59] New review: MaxSem; "(no comment)" [mediawiki/extensions/MobileFrontend] (master); V: 1 C: 2; - https://gerrit.wikimedia.org/r/13104 [14:36:01] Change merged: MaxSem; [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/13104 [15:03:50] New review: MaxSem; "This change would create client-side cache fragmentation: people will have to reload all the modules..." [mediawiki/extensions/MobileFrontend] (master); V: 0 C: -2; - https://gerrit.wikimedia.org/r/13102 [15:35:44] hello jrobson [15:35:48] how goes house hunting? [15:36:59] I don't know why but every morning I now see you on irc this plays in my head > http://www.youtube.com/watch?v=nwd9W6VwIu4 [15:37:17] I found a house \o/ just need to accept the right one [15:43:51] yuvipanda: I'm heading to the office… hope I haven't made you seizure [16:35:02] jrobson: that was... nice :) [16:36:02] yuvipanda: a seizure? [16:36:20] it's the original miyazaki http://en.wikipedia.org/wiki/Panda!_Go,_Panda! [16:36:42] a bizarre story of how an orphaned girl gets a panda dad and adopts his panda son who has no mum [16:36:48] and they meet an escaped tiger from the circus [16:37:16] Only for die hard miyazaki geeks [16:37:26] jrobson: sounds like something I should try watching [16:39:10] it's interesting as there are loads of parallels between his other works [16:42:17] so yuvipanda we need to start planning our washington dc nights [16:49:07] jrobson: plan? :P [16:49:43] jrobson: but yes, I think planning might be superior to my way of just 'stagger around, get lost and find something cool(hopefully)' [16:50:55] I was thinking of poking the couch surfing community there to find a drinking guide [16:53:14] jrobson: aaah, already in touch with that community? [16:55:03] yup [16:55:20] hangout is up https://plus.google.com/hangouts/_/dfdb2542ea02c558c49a03d39d9f8db572417005?hl=en [16:55:26] * tfinc grabs a power adaptor before his laptop dies [16:59:29] yuvipanda: MaxSem https://plus.google.com/hangouts/_/dfdb2542ea02c558c49a03d39d9f8db572417005?hl=en [17:08:56] yuvipanda: which graphics are the ones we should have for the demo? [17:13:45] * tfinc hates how long apple reviews take [17:14:17] tfinc, speaking of .m. domains: we still have https://bugzilla.wikimedia.org/show_bug.cgi?id=34788 unfixed which will make us look less than pretty is we will start redirecting people to mobile domains en masse [17:14:48] philinje: i added only one more graphic [17:14:51] philinje: the 16x16 can wait [17:14:57] MaxSem: and thats pending https://rt.wikimedia.org/Ticket/Display.html?id=2136 [17:15:02] which is the ops request for it [17:15:13] we can live without https at first [17:15:20] I still can't read those [17:17:48] yuvipanda: do you mean the second item here: https://www.mediawiki.org/wiki/Wiki_Loves_Monuments_mobile_application/ToDo#TBD: [17:18:00] * tfinc hates that rt isn't open like a passion [17:20:43] so the nexus tablet is real [17:21:20] philinje: a combined WLM Logo + 'up affordance' icon? (see https://developer.android.com/design/media/action_bar_pattern_up_app_icon.png) [17:21:23] yes [17:21:35] ok [17:22:44] tfinc: I hope it starts shipping soon so I can buy one at washington [17:23:07] New patchset: MaxSem; "Bug 36182 - Switching between desktop and mobile view should redirect to canonical URLs" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/13185 [17:26:12] does anyone has idea why http://mobile-geo.wmflabs.org/ is not accessible? [17:26:58] MaxSem: I've got no idea [17:28:09] is labs that broken? [17:28:43] there has been some disruption in our cluster a little while ago [17:29:29] labs is not part of it [17:31:31] SO MaxSem : "site language" is the UI language which can be different fro content language. This switch is about switching between *sites* in different languages. [17:31:37] When is UI language different from content language? [17:32:40] jrobson: in the apps a decision was made to separate UI language and content language, which we will reverse with the new UI [17:33:16] philinje: MaxSem is referring to the mobile website [17:33:19] go to Special:Preferences, see the "Language" selector. it switches UI language so you can browse enwiki with Chinese UI. we can't have a selector on mobile options which is named the same but does absolutely different thing [17:33:24] yuvipanda: it ships mid july [17:33:46] tfinc: damn [17:34:19] but MaxSem this doesn't do that... [17:34:24] 18 new input languages. Let's hope indic ones made it [17:34:32] It just redirects you to the homepage of that language [17:35:11] jrobson, exactly. so it has to be called differently to avoid confusion [17:35:31] mobile and desktop sites must use uniform terminology [17:35:35] but it's just called "Language" on the Special:Preferences page [17:35:41] on our page we call it "Site Language" [17:37:13] MaxSem: just grabbing philinje into the conversation [17:37:41] it's unclear [17:38:21] Yes agreed. philinje is telling me that apparently the desktop version is also likely to change [17:38:30] Personally I think mixing languages is a bad idea [17:39:02] no, UniversalLanguageSelector doesn't touch Special:Preferences, it just adds a convenient UI language switch [17:39:25] the desktop site is confusing, but there are times when language of the UI chrome can be needed [17:39:37] having UI language independent from content language is a fundamental MW feature [17:40:09] yes, but the typical usage is to switch the chrome when browsing a different language version [17:40:33] so what is my concern there is that users must understand clearly that they're not switching UI language, insted they're going to a ddifferent site [17:41:09] currently, most people familiar with Special:Preferences will think it's a UI switch [17:41:28] (also because of its position) [17:42:05] i think we need to get Lindsey and Pau into this discussion, but for now, let's go with Lindsey's current proposal [17:42:16] MaxSem: how many people are familiar with Special:Preferences ? - (I wasn't for example) [17:42:27] MaxSem: do you think a lot of people rely on Special:Preferences? [17:42:32] I'd be keen to get some real data - people complaining for example that the language setting is confusing [17:42:38] you're not a WP regular, unlike thousands of people [17:42:44] or demanding that language on the settings page should change the UI chrome rather than redirect to the homepage [17:43:10] I know MaxSem but I'd say WP regulars with an account are a minority in the X billion mobile page views [17:43:24] tfinc: "Nexus 7 built to bring you the best of Google — it's a fantastic device, so starting today it's available at $199." [17:43:29] jrobson, that's not a reason to piss them off [17:43:52] Well it might not piss them off.. that's what I'm saying [17:44:01] I'd rather we got something out there and people told us it was wrong and we fixed it [17:44:06] to resolve this, let me reach out to Pau and Lindsey [17:44:14] rather than worry about pissing people off and not get anything out [17:44:25] the leeway we have in mobile is considerable [17:44:41] I completely agree the difference is confusing - but I'm not sure which is the expected one [17:44:56] yuvipanda: nice prince point [17:45:03] philinje: maybe we could do some user testing around this in the beta? [17:45:04] tfinc: says 'starting today' :D [17:45:13] Brooke, your opinion^^? :P [17:45:23] yuvipanda: orders start today. device ships mid july [17:45:29] but for sure the way the apps currently work is confusing, and that is similar to the Special:Preferences approach [17:45:51] jrobson: yes, we could do some user testing, but the problem is we may not address the core WP users [17:46:13] tfinc: aaah, daymn. [17:47:52] philinje: app users are, likely, a different group than the 'core' WP users, and should be addressed/supported as such. [17:53:05] Amgine: good point [17:53:33] that is partly why we have so much leeway in mobile [17:53:58] Amgine: hey, how did it go with the Wiktionary Village Pumps, in terms of mentioning the app? [17:54:22] heh. Wait until the great schism - *then* you're going to have more serious market divergence. [17:55:34] philinje: I mentioned either in lists or on Beer parlors (the Wiktionary equivalent) of 10 or so, but only 4 of the top 10. [17:55:51] Greek is really excited about it. [17:56:18] only 4 of the top 10 … [17:56:35] came back with comments? [17:56:46] Working on it yet. They aren't languages I have much luck with. [17:56:49] yuvipanda: i saw this and wondered if arthur was at google i/o http://www.blogcdn.com/www.engadget.com/media/2012/06/googleio20124197.jpg [17:56:59] hahaha [17:56:59] [17:57:28] preilly: lets chat about the dolphin presentation that your doing tomorrow later today [17:57:30] oh, tfinc: the de.WT folk were mystified as to how you edited the main page... I laughed. [17:57:39] Amgine: what did they say? [17:57:55] Just questions like "Is he some kind of steward?" [17:58:02] lolz [17:58:13] Amgine: what did you tell them? [17:58:23] "No, a bit higher than that." [17:58:28] :D [17:58:32] glad you could explain it [17:58:38] [18:01:30] Amgine: curious about the term, "the great schism" - is that your own invention? [18:01:53] Yes. The great schism will occur when mobile can edit. [18:02:24] Then the app market will be identified as Catholic (read-only) and Protestant (read&write) [18:02:30] tfinc: okay sounds good [18:02:39] PReilly: \Mike> As for the mobile site, if id="mf-foo" makes it show up in mobile view, is there any id to make it show up only in mobile view and not in standard? [18:03:20] Amgine: no [18:03:33] Amgine: people are doing that already on tablets - with the desktop site, and maybe a tablet app would be the read/write version [18:03:49] kk. Any idea how someone might edit css to *make* an id which does not display on non-mf? [18:04:28] philinje: cool! I didn't know there was an app with edit yet. [18:04:39] not yet, just thinking about it [18:04:56] edit css to make an id? not sure I understand what you mean.. [18:05:53] philinje just explained… let me think [18:06:17] jrobson: how would a wiktionary create an id which does not display on the main page, but does display on MF main page. [18:06:19] It would require a change to common.css I think [18:06:31] Yes, that's what I figured. [18:06:52] jrobson, where did dl go?:P [18:07:19] dl MaxSem ? [18:07:28] from your nick [18:08:20] Ohhh [18:08:32] It's because I'm still in laptop limbo now I have my new machine [18:09:09] So Amgine the sensible approach would be to add a definition .mobileonly { display: none; } to MediaWiki:Common.css [18:09:39] Cool, \Mike is going to try that out, I suspect. [18:10:23] It might be worth starting a discussion around that. I think .printonly already exists [18:10:44] <\Mike> If I figure out exactly how to do it, yeah :p (/me's css skills consists of copy&paste) [18:11:08] Well that could be copy and pasted :) [18:11:13] .mobileonly { display: none; } [18:11:36] Currently MobileFrontend is not effected by MediaWiki:Common.css [18:12:02] <\Mike> Okay, where do you want me to paste it, then? [18:12:09] but to future proof you also want to copy and paste [18:12:14] You can just copy/paste that line into MediaWiki:Common.css [18:12:19] .mobile .mobileonly { display: inline; } [18:12:32] actually [18:12:34] .mobile .mobileonly { display: block; } [18:12:36] probably better [18:12:52] (MFE includes a mobile class on the body tag so you can target things better at mobile) [18:14:15] although of cause that will restrict all elements with a class to nomobile to be block elements rather than the default [18:15:39] <\Mike> Sorry to be a noob now, but will I then in the main page add a ... id="mobile [18:15:41] <\Mike> ? [18:15:56] <\Mike> *mobileonly? [18:16:20] Nope.. so then what you to need to do is add a class attribute [18:16:33] so [18:16:33] class='mobile only' [18:16:41] To add something which only appears on the mobile home page,

Things you want to show on mobile

[18:16:46] add that after id='yourid' [18:16:52] exactly Amgine [18:16:57] jrobson, class='mobileonly' [18:17:13] argg my pc keeps autocorrecting my spelling [18:17:24] * jrobson fixes [18:18:21] wow .. parachutes, bike stunts, and repelling all at google i/o … now i wish that i had been there [18:18:22] jrobson, is that a macos feature? [18:18:35] tfinc: indeed, I've a very nice excuse for not being there. You don't seem to :P [18:18:50] yuvipanda: its just funny cause their just two blocks down from us [18:18:57] I guess so [18:19:19] jrobson, can we close https://bugzilla.wikimedia.org/show_bug.cgi?id=36379 ? [18:19:51] Probably MaxSem - there are still a few outstanding issues with the names of classes and id's but I don't think those matter so much [18:19:59] They probably need a more specific ticket anyway [18:20:04] Just close it :) [18:20:36] tfinc: yes, when I was in SF I think I got lost and found that a few times [18:21:18] MaxSem: philinje hows is the blog post coming along ? [18:21:48] preilly: we still need to respond to open path about article history and translations [18:21:56] <\Mike> Ok, that seems to work. Thank you! [18:22:21] oh wait [18:22:22] nm [18:22:30] preilly: just saw your mail from last night [18:22:31] with teeth screeching [18:23:10] sloooowww internet [18:23:16] awesome \Mike [18:24:27] watching live streams from Google I/O eh? [18:24:38] :) [18:24:44] they are talking about the glasses. omg. neeed [18:24:50] i'm catching the live blog [18:26:22] <\Mike> Just a second question: the string "Type your search term above and matching articles..." has to be translated somewhere, but I can't seem to find it among the system messages. Do you know where it is located? [18:26:54] Philinje: one interesting comment on fr.WT, well, sort of interesting - shows the user did not actually understand the app is different from MobileFrontend: http://fr.wiktionary.org/wiki/Wiktionnaire:Wikid%C3%A9mie#Official_App_Wiktionnaire_Mobile_pour_Android_publi.C3.A9 [18:27:31] https://developers.google.com/events/io/?utm_source=io-site&utm_medium=emb-io&utm_campaign=io-site [18:27:42] So MaxSem philinje what should we do about the language switching? I'm keen to get this out into the beta so we can improve on it. I'd rather have some real data that we are doing it wrong then speculate that it's confusing. [18:27:43] need glasses with wikipedia app .. need [18:28:02] mutante: i need to remember to bring them the next time i jump out of a plane [18:28:13] jrobson: let's go with it for now, it's a beta [18:28:26] MaxSem: is that okay with you? [18:28:33] jrobson & philinje, imho just tweak the message and move it to the bottom to make it look less like UI lang switcher [18:28:33] if so could you revert your -1 ? [18:28:44] But tweak it how.. [18:29:10] We could have 'Site and Content Language' but that is too wordy [18:29:31] to make it very clear that we're goint to a different site, not changing some "site language" [18:30:49] How about just "Site" then ? [18:30:55] yuvipanda, can you share a couple of points on how our mobile app benefited from switching to API? just your personal likes [18:31:02] I just feel losing the word language is confusing [18:31:26] <\Mike> ok, found it. [18:31:41] Also MaxSem if someone is having issues with the mobile site sticking - how do they smash their cookies? [18:31:51] I remember there was a query string for that [18:32:02] jrobson, depends on browser [18:32:06] iphone [18:32:13] I don't remeber anything like thaty [18:32:22] it was like cookie-age or something [18:35:17] MaxSem: sure! email? [18:36:21] mutante: ouch $1500 [18:36:25] tfinc: 1500 dollars, just live at the conference, developer pre-order though! audience claps, like a minute ago :) [18:36:33] heh, in sync [18:36:45] yuvipanda, just a couple sentences - on this channel is fine [18:36:58] thats going to have to come down in price as i'll break a pair within weeks of using it [18:37:11] but its meant to be a dev unit [18:38:33] MaxSem: 1. we didn't have to worry about unrelated changes to the mobile site breaking the app [18:38:44] jrobson: how about "All languages" ? [18:38:54] MaxSem: 2. Since the data was a bit more structured, we were easily able to do things like load images only when their section is expanded [18:39:37] MaxSem: 3. It helps responsiveness a lot by just doing section-wise loading [18:39:54] Amgine: thanks for that [18:40:06] tfinc: lets write a mail to have a couple donated to WP? [18:40:09] MaxSem: 4. Speed and bandwidth helped because we're getting just the data we want, without extra cruft (, nav elements, etc [18:40:13] you are welcome. I'm working on translations now. [18:40:24] yuvipanda, thanks! [18:40:50] MaxSem: http://en.wikipedia.org/wiki/Wikipedia:Emv that was what I was looking for [18:41:09] mutante: sure. we have lots of friends at google [18:41:22] tfinc: then they can say Glasses is also "optimized" for WP:) [18:42:39] jrobson, mobileRedirect.php is here for b/c, we don't really care about it when changing our cookie system so I won't be surprised if it already doesn't work properly [18:44:36] Well I got back to the guy and asked him to try it - so he can test it for us ;-) [18:47:03] mutante: i'd be eager to think about how their interfacing with us already. its a great data source for glass [18:47:15] Amgine: did you see the comments about the default switchover higher up on the same page? [18:48:22] Yes, but let me re-read. [18:50:56] i think the comments are about editing on mobile [18:52:03] My French sucks. [18:53:45] Ah! They are talking about the text JackPotte added to the mobile main page about contributing; they decided it should be removed. [18:53:55] tfinc: indeed! also see this and the drawing there on how to edit: http://gizmodo.com/5919605/google-scores-a-patent-on-google-glasses-technology [18:54:14] They also really really hate the web-browser based editing on a mobile. [18:55:21] Philinje: they would like a form-style "there's a problem here" button. [18:56:41] "trackpad probably means that the Project Glass system will be controlled with your fingers and not just your voice or eyesight." . eyesight = next step i guess [18:57:00] but integrated into the frame of the glasses [18:59:27] * yuvipanda is sure people will make borg styled versions of this [19:01:56] ah, of course. My country of 1 billion people doesn't quite exist, does it? [19:01:59] 'Sorry! Devices on Google Play is not available in your country yet. [19:02:01] ' [19:05:06] preilly: how much lead time do you need before we can set a time for switching over the next batch of sibling projects ? [19:06:43] yuvipanda: i'll be ready to chat in about 5min [19:07:01] tfinc: okay! skype? [19:07:05] yes [19:07:36] http://m.mediawiki.org/ doesn't show me what i would expect [19:07:40] tfinc: ok [19:10:12] preilly: is mediawiki.org special in any way for lvs? http://m.mediawiki.org/ is showing the wrong page [19:10:42] New patchset: MaxSem; "Add logging of format=json usage for WMF." [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/13203 [19:13:16] preilly: problem is v [19:13:17] mwMobileFrontendConfig.settings.useFormatCookieDomain [19:18:35] MaxSem: did you ever get my latest inline styles email? I am worried it might have been dropped in the outage [19:18:54] jrobson, don't recall it [19:19:22] I've just bumped it so hopefully that will answer :) [19:19:29] jrobson, now read the bump [19:19:40] but not the one before? [19:19:52] That's reassuring - I thought no one cared about it :P [19:20:13] jrobson, I actually wanted to play a different style-related experiment on you, but labs is kinda down [19:26:27] New review: MaxSem; "Also needs https://gerrit.wikimedia.org/r/#/c/13207/" [mediawiki/extensions/MobileFrontend] (master); V: 0 C: 0; - https://gerrit.wikimedia.org/r/13203 [19:28:40] New patchset: Jdlrobson; "write mobiletoken cookie on the current domain" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/13210 [19:34:58] New patchset: Jdlrobson; "write mobiletoken cookie on the current domain" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/13210 [19:37:48] New patchset: Jdlrobson; "drop unnecessary prefix" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/13213 [19:38:34] New review: preilly; "(no comment)" [mediawiki/extensions/MobileFrontend] (master); V: 1 C: 2; - https://gerrit.wikimedia.org/r/13210 [19:38:37]