[12:38:42] whee, iOS 4.x test device! [13:13:21] join #chennai-hackers [13:13:27] gah [13:18:21] augh, 4.x test device doesn't seem to think my wifi works [13:18:21] sigh [13:31:07] MaxSem: https://bugzilla.wikimedia.org/show_bug.cgi?id=36720 [13:31:57] yeah, continue poikng:) [13:32:30] s/poiking//poking Patrick/ [13:32:32] I'm guessing it must be that [13:32:41] preilly is hard to poke from this side of the atlantic [13:54:48] This is frustrating [13:54:49] gah [13:54:56] * yuvipanda contineus wifi tinkering on iPhone [14:26:42] Lithuanian spam just arrive to the Mobile Feedback mailing list. [14:26:48] *arrived [14:27:22] I know a bit of Lithuanian. I hope to reply... [14:27:39] *hoped. I don't like the past tense today. [15:09:25] aharoni: was it spam spam or just spam-because-we-usually-do-not-know-the-language spam? [15:11:58] New patchset: Jdlrobson; "enable full text search (bug 36679)" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/7172 [15:11:59] New patchset: Jdlrobson; "override MediaWiki:Common.css search styling rules" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/7173 [15:14:21] MaxSem: you there? [15:14:29] yup [15:14:39] switching from action=opensearch to action=query&list=search - is there any reason not to? [15:14:43] how does it compare performance wise? [15:15:37] full-text is certainly slower [15:16:10] so https://gerrit.wikimedia.org/r/7172 should be fine ? [15:16:24] e.g. clicking search goes to search results page, otherwise do the prefix search [15:17:30] New patchset: Jdlrobson; "style warning boxes better for mobile (bug 36674)" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/7175 [15:18:36] however now that I've been explained that Special:Search invocation was removed by accident.... [15:19:01] I'm not sure if predictive search should switch to full-text [15:19:24] New patchset: Jdlrobson; "fix for toggling bug 36675 and bug 36673" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/7177 [15:19:28] as it's not only slower but also has problems with searching parts of words [15:26:54] New review: MaxSem; "(no comment)" [mediawiki/extensions/MobileFrontend] (master) C: 1; - https://gerrit.wikimedia.org/r/7172 [15:29:07] yuvipanda: spam spam. [15:31:28] aharoni: ah :) [15:48:18] jdlrobson, I have an idea: a manual for end-users on how to format content for mobile [15:49:22] we should explain in one place how to create mobile main pages, format templates that look sanely on mobile screens, etc [15:50:32] well, something along those lines would be needed if we are to scrub out all inline styles [15:51:14] unrealistic [15:51:23] also, will be quite slow [15:55:22] I think that I just made my first WikipediaMobile pull request. [16:02:54] [WikipediaMobile] yuvipanda pushed 1 new commit to master: http://git.io/AHi5ew [16:02:54] [WikipediaMobile/master] Added more rtl language codes from MediaWiki's Names.php. - Amir E. Aharoni [16:03:36] aharoni: ^ [16:03:37] thanks :) [16:06:06] yuvipanda, tfinc, hi! [16:06:18] hey aharoni [16:06:44] remember that you did the hackathon in India and brought all the needed stuff on a USB drive to make setting up the environment faster? [16:06:48] tfinc: the iOS device is here :) [16:06:54] ah [16:07:56] I am thinking of doing a hackathon some time soon and I may try to add mobile as a topic there. [16:08:20] So I thought about preparing such a USB drive. Is there a list of things that should be there? [16:08:57] aharoni: hmm, we prepped them last time but IIRC we didn't make a list [16:09:26] yuvipanda: can you make one? it would be useful. [16:10:17] philinje: did you see https://bugzilla.wikimedia.org/show_bug.cgi?id=36017? [16:10:29] aharoni: ah, shall do! [16:10:38] cool, thx. [16:15:08] pchang: did you see https://bugzilla.wikimedia.org/show_bug.cgi?id=36017? [16:15:11] hello [16:16:13] yuvipanda: yes, just going into a meeting [16:16:28] i am think of some basic test above the globe [16:16:57] and a smaller globe [16:17:06] should have something today [16:18:04] philinje: cool :) [16:18:06] MaxSem: yeh I just went for a walk actually and was thinking more about inline styles [16:18:20] I'm thinking even more that they should be scrubbed [16:18:26] unless they are marked in a special way [16:18:44] yuvipanda: do we have time to translate a string? [16:18:51] so my proposal was to educate ppl how to avoid breaking stuff:) [16:19:33] philinje: depends on what string it is. If it is 'wikipedia' we already have it [16:19:37] well the easy stuff to fix is in the stuff in stylesheets [16:19:50] I think only in special cases are inline styles useful [16:19:51] e [16:19:58] e.g. those railway templates [16:20:38] would be interesting to turn them off in the beta and see what breaks [16:21:03] jdlrobson: maybe a bit more space between W and "Type your search'? [16:21:40] yuvipanda: would be a new string [16:22:29] yuvipanda: if there isn't time, we can go with Wikipedia under the globe [16:23:07] philinje: it might still be a bit context-less and confusing [16:23:23] philinje: I'd still want to retain the bottom row of 'actions' that the original comp had [16:24:31] philinje - so my feelings on tweaks are that they are not worth it at this stage (unless they are judged to be extremely important) - I'm very concerned that I wasted many hours tweaking the last mockups and now they have been all thrown away as the user testing deemed them to not be usable. If the purpose of this next demo is to judge whether people can find functionality we should only make those changes to spacing if we believe they will e [16:24:32] the results of the a/b testing. I'm happy to make this one tweak to spacing between the W and type your search but I don't want to spend many more hours again for something we are not going to use... thoughts? [16:24:59] arggh I'm being chucked out of my office space now... [16:25:33] philinje: will be one email! [16:25:36] *on [16:26:53] jdlrobson: ok [16:27:37] yuvipanda: can those strings be translated? [16:28:25] yuvipanda: or just go with the same names as we had before - for example, Random instead of Surprise me [16:28:45] Home instead of Featured [16:28:53] again, if not time for translation [16:29:56] philinje: We don't really have 'Random' functionality in the app, so having Random show up would be pointless [16:31:14] philinje: and I think it's fine to add a bit more strings for translation. We can do another release a bit later with just more translations if they miss the first cut [16:34:10] yuvipanda: maybe Home and Contact at the bottom, but depends on when the new Contact is deployed [16:34:31] ah, +1 to Home and Contact [16:34:54] is Arthur here? [16:35:03] philinje: not yet [16:35:16] philinje: why should it depend on new contact us? [16:35:28] the current one is lame [16:35:35] the new one is great [16:36:10] anyway, we could go with Contact and assume the new page will go live soon [16:36:35] Only one text string needs to be added to the new Contact page [16:37:10] 'Contact us' is already translated [16:38:02] i mean a text string in the Contact page itself [16:40:08] philinje: ah ok [16:42:57] yuvipanda: will file a bug today, but the text is on the talk page of Contact [16:43:58] mobile design/Contact [16:46:06] philinje: would still like a comp of it with the globe icon [16:46:21] ok [16:46:24] philinje: thanks :) [16:47:05] yuvipanda: how is the Mainpage API? [16:47:15] works [16:47:54] +1 [16:47:58] philinje: it's been deployed. [16:48:06] and works. [17:07:16] yuvipanda: Jon had another idea upon launch: use a separate spinner for the page [17:07:41] so main page shows up but the spinner is not the one in the search bar [17:09:13] philinje: a blocking spinner? [17:09:48] philinje: the idea is to let people use search as fast as possible philinje. I'm not sure how opening a separate spinner will help. [17:16:14] greetings all [17:16:20] whatsup tfinc [17:16:22] the current spinner doesn't stop you from searching, i don't think we'd want to stop people :) [17:18:54] brion: yes, the idea is to make it more obvious people can search while the page is downloading [17:19:37] hmm [17:19:49] greetings [17:20:10] hey jon good timeing [17:20:30] jon, was trying to explain your idea about the separate spinner [17:21:21] i.e., you think the spinner in the search bar makes it look like part of search, whereas a spinner for the article would make it more obvious it's about the article [17:22:56] plausible [17:23:19] 2hmm, so a big fat spinner in the content area [17:24:03] tfinc MaxSem what do you reckon about the idea of scrubbing inline styles in the beta - it would give us a safe way to explore the damage [17:24:14] philinje: can you throw in an update for http://www.mediawiki.org/wiki/Mobile_design/Wikipedia_navigation [17:24:14] i have a theory it won't damage much [17:24:25] I disagree [17:24:38] why MaxSem [17:24:38] tfinc: ok [17:24:38] would that mean we'll have a beta and non-beta api too? [17:24:48] i believe there are only a few niche places inline styles are actually useful [17:24:52] e.g. https://bugzilla.wikimedia.org/show_bug.cgi?id=34711 [17:24:58] useful/essential [17:25:08] most of the time they just make things prettier and slightly more readable [17:26:05] and yes philinje YuviPanda +1 to a big spinner that is separate from search - that is so broken [17:27:59] jdlrobson, try removing inline styles from a complex template [17:28:09] yuvipanda: worth testing [17:28:32] but MaxSem I hazard a guess they will still be readable.. just ugly - which I believe is better than the current situation where things are just not readable [17:28:45] going forward I could imagine style="/*@noscrubs*/border:solid 1px red" which when used protects inline styles for places where it is important [17:28:54] if nothing else it could help us fix inline styles [17:28:59] (in the beta) [17:29:05] and thus in the main site eventually [17:29:34] jdlrobson, believe me about one thing: crowds VPT will eat you alive [17:29:42] *at VPT [17:30:38] but if its in the beta.. we won't get widespread damage - if anything it will provide an easy way for people to fix inline styling issues with their templates on mobile [17:30:56] (without effecting the public global site) [17:31:00] https://en.m.wikipedia.org/w/index.php?title=Baker_Street_tube_station looks like shit, however the dot still points at the right spot on the map [17:31:17] philinje: Still not sure if I'd want to do it for this release - possibly very late? [17:32:47] MaxSem: I've seen examples where it doesn't point to the right place.. there was a bug recently around this.. [17:35:28] i guess what i'm trying to get at is we need to find an easy way for contributors to check templates are mobile safe - and one way I can imagine us doing that is turning them all off in the beta unless they are prefixed with an annotation e.g. /*@mobilesafe*/ and allowing a timeframe during which they can be checked and fixed up [17:35:48] +1 to jdlrobson [17:36:26] i could imagine 1) email community asking them to help us get the website mobile friendly and getting them to opt into beta [17:36:49] explaining that inline styles need to be checked across templates and prefixed where they are vital and verified to work in mobile [17:37:35] (or stuff put into MediaWiki:Common.css) [17:37:40] after say 1/2 months - whatever's needed we turn this on permanently but even during this 2 month time period we will get much more mobile friendly content [17:38:13] it's also rather future proof in that if people add new inline styles but don't check if they are mobile friendly we do not break the content [17:39:37] jdlrobson: lindsey is modifying the buttons [17:40:59] jdlrobson: any chance you could update just one prototype demo3, with new buttons? [17:41:43] jdlrobson: great idea about the templates [17:43:35] YuviPanda|food: the spinner idea is something we could try later in a test, aka beta site [17:54:42] New review: awjrichards; "(no comment)" [mediawiki/extensions/MobileFrontend] (master); V: 1 C: 2; - https://gerrit.wikimedia.org/r/7177 [17:54:45] Change merged: awjrichards; [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/7177 [17:57:01] email sent to wikitech-l [18:18:56] philinje: yes, if you remember the email i sent yesterday, we'll be getting a 'beta' application in google play shortly :) [18:19:38] awjr: http://www.mediawiki.org/wiki/Wikimedia_Labs/Development_Process tells me that any instance should be able to hookup to a production like db [18:19:49] oo [18:20:11] i'll look closer in a bit, thanks tfic [18:20:14] *tfinc [18:22:13] tfinc: i have the iOS 4.x test device :) [18:24:00] YuviPanda: damn that was fast [18:24:13] does https://www.mediawiki.org/wiki/Extension:MobileFrontend#action.3Dmobileview look ok? [18:24:17] its visited more countries in its voyage then most peopel do in a lifetime [18:24:18] :D [18:24:34] tfinc: it got here before I actually tried tracking it :) [18:24:52] MaxSem: doesn't mention override :D [18:24:58] is there a chance that normal humans will understand it? [18:25:11] YuviPanda, it's undocumented [18:25:20] YuviPanda: no more intercontinental debugging! [18:25:22] thank god ... [18:25:25] tfinc: :D [18:25:39] YuviPanda: is it working ok for you? [18:25:43] tfinc: did you check out the content for the google play beta app description? [18:25:50] tfinc: once we figure that out I'll push it out to market [18:25:53] tfinc: i had been looking at https://ticket.wikimedia.org/otrs/index.pl?Action=AgentTicketZoom&TicketID=6546154&ArticleID=7637255&ZoomExpand=0#7637255 [18:25:55] tfinc: yup! [18:26:01] breifly. looked fine. i'll take another look now [18:26:20] tfinc: my portable wifi thingimangy is causing problems, so I just put my sim in it. Works fine [18:26:25] it's possible that that user was seeing the site when we were having issues after Monday's deployment but before we got them fixed tuesday evening [18:26:37] awjr: possibly. thats why i asked for screenshots [18:26:56] word [18:27:51] YuviPanda: did you any problems signing for it . any customs issues ? [18:27:57] tfinc: none at all [18:28:04] speaking of override... preilly, when it will die? [18:28:08] thats how it should be [18:28:20] indeed [18:29:20] MaxSem: ? [18:29:34] preilly, action=mobileview&override=1 [18:30:52] MaxSem: well when ever we can use the other api in production [18:30:58] MaxSem: which might be now [18:31:26] sehr gut, I'll look at killing it [18:31:46] preilly, you wanted to discuss MF instantiation? [18:32:10] MaxSem: I'm busy right now [18:32:14] MaxSem: probably tomorrow [18:35:25] YuviPanda: i'm pretty happy with the icon :D [18:35:46] it combines everything that we needed to have there [18:36:29] YuviPanda: i made a tiny text fix and cc'd Phil. If he has no problems with it lets publish it [18:37:20] tfinc: agreed [18:38:44] YuviPanda: prep a blog post about it so that we can raise awareness. MaxSem how goes the API blog post with Yuvi ? [18:39:16] tfinc, working on on-wiki documentation, we have to point people somewhere [18:39:25] great [18:39:51] MaxSem : pull in guillaume if you need any help [18:41:55] this is awesome http://www.disneyresearch.com/research/projects/hci_touche_drp.htm [18:45:11] whoa [18:46:54] tfinc: about the beta? Do we want to make that high visibility? [18:47:23] im particularly impressed by the body sensitivity - "it is not inconceivable that one day, mobile devices will have no screens or buttons, and rely exclusively on the body as the input surface" [18:48:48] awjr: yup, i really like their uses cases. minus the cereal which was dumb [18:48:59] hahah yeah the cereal was really dumb [18:49:13] YuviPanda: do you want keep it to mobile-l for now ? [18:49:30] mobile-l + twitter [18:49:35] tfinc: for a week? Then we can push it out wider [18:49:39] sure [18:49:50] lets beta test our beta [18:49:58] * tfinc hurts his brain by saying that [18:51:04] :D [18:56:29] awjr: just filed the bug about the text change on Contact page [18:56:42] 36741 [19:05:35] New patchset: awjrichards; "Removing errant new line" [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/7204 [19:09:58] New review: preilly; "(no comment)" [mediawiki/extensions/MobileFrontend] (master); V: 1 C: 2; - https://gerrit.wikimedia.org/r/7204 [19:10:00] Change merged: preilly; [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/7204 [19:15:56] hi there, I just saw the first proof-of-concept of the PhoneGap app running on Qt in the Nokia N9! http://www.youtube.com/watch?v=U_ay0U5FIts [19:15:59] getting there... [19:17:04] qgil, isn't Maemo DOA? [19:17:05] Following the same path we should get it for Symbian as well... [19:17:21] Qt is alive [19:17:38] Can it be run on any phone that is not the N9? [19:17:43] we are working on Qt support for PhoneGap, taking Wikipedia app as example / test [19:17:46] * YuviPanda has a friend who has one! [19:18:05] qgil: what device are you guys testing it with? [19:18:13] er... the N9 :) [19:18:52] "any phone that is not the N9" is a bit wide concept ;) [19:18:58] :D [19:19:11] * YuviPanda has a friend who has an N9 [19:20:32] as said, we are working on this Qt - PhoneGap support. We are using the N9 but eventually this work should provide also a Symbian package able to run in many more devices [19:20:45] aaah, I had forgotten that S60 also supported qt now [19:22:50] We are talking actually about Symbian Belle, found in the Nokia 808 PureView, N8 and other contemporary products, a user base of 180 million Qt enabled devices [19:23:56] Devices with pretty good cameras btw, how is that feature for easy upload of pictures? ;) [19:25:59] qgil: we're starting work on a WLM app pretty soon [19:26:01] phonegap again [19:26:43] YuviPanda: WLM? [19:29:29] wiki loves maonuments [19:33:28] New review: preilly; "(no comment)" [mediawiki/extensions/MobileFrontend] (master); V: 1 C: 2; - https://gerrit.wikimedia.org/r/7172 [19:33:31] Change merged: preilly; [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/7172 [19:33:50] New review: preilly; "(no comment)" [mediawiki/extensions/MobileFrontend] (master); V: 1 C: 2; - https://gerrit.wikimedia.org/r/7175 [19:33:52] Change merged: preilly; [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/7175 [19:34:18] New review: preilly; "(no comment)" [mediawiki/extensions/MobileFrontend] (master); V: 1 C: 2; - https://gerrit.wikimedia.org/r/7173 [19:34:20] Change merged: preilly; [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/7173 [19:34:38] New review: preilly; "(no comment)" [mediawiki/extensions/MobileFrontend] (master); V: 1 C: 2; - https://gerrit.wikimedia.org/r/7121 [19:34:40] Change merged: preilly; [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/7121 [20:14:34] New patchset: L10n-bot; "Localisation updates from http://translatewiki.net." [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/7220 [20:15:00] New review: preilly; "(no comment)" [mediawiki/extensions/MobileFrontend] (master); V: 1 C: 2; - https://gerrit.wikimedia.org/r/7220 [20:15:04] Change merged: preilly; [mediawiki/extensions/MobileFrontend] (master) - https://gerrit.wikimedia.org/r/7220 [20:52:05] wow our labs instance is a total spam magnet. [20:52:26] anybody have an objection to me locking down the wiki a bit to make it less spam-prone? [20:59:51] preilly: did you originally set up the mobile labs instance? [21:00:20] awjr: yes [21:00:35] preilly out of curiosity did you set it up following this? http://www.mediawiki.org/wiki/Wikimedia_Labs/Development_Process [21:01:09] more specifically, did the data in the db come from the 'create-wiki' command with —data enwiki? [21:01:28] awjr: no [21:01:42] k [21:01:54] thanks [21:01:59] what wiki are you talking about? [21:02:08] mobile-geo [21:02:32] awjr: MaxSem did that one [21:02:43] oic [21:02:45] yeah [21:02:57] everything was done manually [21:03:15] MaxSem ok so you didn't use the 'create-wiki' command (http://www.mediawiki.org/wiki/Wikimedia_Labs/Development_Process)? [21:03:31] nope. docs are good only if you know about them [21:04:11] hehehe true story [21:25:37] tfinc: philinje is the copy for the Google Play beta push fine? [21:27:05] tfinc: did you see this: http://www.zdnet.com/blog/facebook/facebook-announces-the-app-center/12792 [21:28:08] so i can pay for apps that i dont use on facebook now ? [21:28:11] yes ... i saw it [21:28:17] tfinc: ha ha [21:28:43] granted if people can donate through facebook that might be nice for us [21:29:09] 'the server could not process your apk' grr [21:30:06] YuviPanda: will take another look [21:30:08] gaaaah, deleting an APK deletes the entire app. Now I need to fill it in again. [21:30:11] sigh [21:30:48] YuviPanda: what will google place list this under [21:30:52] this == beta app [21:30:56] org.wikipedia. ? [21:31:04] org.wikipedia.beta [21:31:12] YuviPanda: lolz .. i should have warned you about that [21:31:22] * tfinc has been bitten by the same dumb ui quirk [21:31:30] cool [21:32:03] tfinc: fun fact was that I did it yesterday and now did it again today :D [21:32:29] YuviPanda: welcome to the club :D [21:32:36] :D [21:35:41] awjr: did the docs that i linked earlier for labs work to import/connect/suck-in a db ? [21:36:19] YuviPanda: guess it's hard to say, "remember this is a beta in your review" [21:36:42] tfinc: i assume so but am waiting for confirmation about what exactly you get with that db (eg templates, image files, etc) [21:36:56] tfinc: philinje https://play.google.com/store/apps/details?id=org.wikipedia.beta [21:36:59] :) [21:37:54] looks great [21:38:47] tfinc: actually no. that tool doesn't exist yet. [21:38:51] it's a proposed spec. [21:39:16] awjr: lame. could you find anyting about a proposed timeline ? [21:39:33] considering that page was last edited in december... [21:39:35] i'll ask ryan [21:39:38] k [21:39:54] i wanted to do our due diligence reading the docs before asking him [21:40:00] but thats all i coudl find [21:40:26] YuviPanda: nice! /me goes to install [21:41:25] anyone have an abusturdly compliced but non popular page on en wiki ? [21:41:35] i want to respond to this tweet [21:42:00] https://twitter.com/#!/ahmattox/status/200701873685139456 [21:43:11] tfinc: http://en.wikipedia.org/wiki/List_of_American_Civil_War_Generals_(Confederate) [21:43:56] tfinc: List of American Civil War Generals (Confederate) ‎[418,775 bytes] [21:44:03] tfinc: http://en.wikipedia.org/wiki/Special:LongPages [21:45:56] got to love 0.399374961853027 megabyte pages [21:46:10] YuviPanda: all hail not having to uninstall/install just to run the beta [21:46:43] tfinc: the timeline for getting the create-wiki tool done is on the order of months [21:46:51] but is pretty up in the air, atm [21:47:13] so were going to have to import with deep depth levels then until then [21:47:47] YuviPanda: I said, "all hail" [21:48:50] * YuviPanda says 'all hail' in a quiet voice [21:49:10] having IRC clients that don't notify has good/bad things [21:50:58] i'm going to laugh if the beta starts beating other wikipedia apps in the store [21:51:11] ha ha [21:51:14] tfinc pagelink-depth is actually not all that useful - adding templates=true will pick up the necessary templates, but i can't figure out a reasonable way to pick up images [21:51:17] tfinc: that would be hilarious [21:51:34] awjr: auto commons [21:51:38] awjr: why can't images just come from commons ? [21:51:43] as they do in en wiki [21:52:24] uhh YuviPanda [21:52:28] e.g., # InstantCommons allows wiki to use images from http://commons.wikimedia.org [21:52:29] $wgUseInstantCommons = true; [21:52:34] tfinc what is 'auto commons'? [21:52:35] oh [21:52:36] neat [21:52:39] Email Developer => tfinc@wikimedia.org is not the right setting [21:52:40] lemme try that [21:52:40] ;) [21:52:56] YuviPanda: please change that to be mobile-feedback-l@lists.wikimedia.org [21:52:57] mobile-l sent [21:52:58] ah [21:52:59] right [21:53:21] tfinc: been getting mail already? [21:53:35] awjr: i meant that en wiki doesn't store many images. it just pulls them from commons using the remote file repot [21:53:47] changed [21:53:48] tfinc: i'm trying to stop it before i do ;) [21:54:06] talking to yourself is clearly the first step towards making sure you don't get lots of email :) [21:54:28] :D [21:54:52] tfinc: tfinc: i'm trying to stop it before i do <— too meta for me [21:55:28] * YuviPanda submits that to quips [21:56:16] tfinc, YuviPanda have you seen the new user testing videos? [21:56:21] * tfinc wonders how accurate http://yuvi.in/where.html is if yuvi is picking up packages in Chennai [21:56:54] Thehelpfulone: i looked at the new videos that showed new search bar icon placement [21:57:13] not tfinc probably picking up a cached version [21:57:22] tfinc: try again [21:57:24] I've got him at: Location INDIA, ANDHRA PRADESH, HYDERABAD Latitude, Longitude 17.37528, 78.47444 (17°22'31"N 78°28'28"E) [21:57:37] tfinc: ^^ [21:57:37] wrong city, wrong state [21:57:54] i've never even been there! [21:58:09] YuviPanda: are you using your TATA TELESERVICES LTD - TATA INDICOM - CDMA DIVISION usb stick? [21:58:23] I am, indeed, using sais stick [21:58:31] *said [21:58:32] tfinc: ok [21:59:10] hmm, tweeted [22:00:32] YuviPanda: you use irssi? [22:00:56] preilly: yup [22:01:02] YuviPanda: nice [22:01:16] I could set up growl notifications, but I *do* like not having notifications... [22:05:02] YuviPanda: are you near Kendra Bank Rd? [22:05:08] preilly: nope [22:08:39] i still can't get used to these new github icons [22:08:46] tfinc: yeah [22:09:48] * preilly ha ha https://twitter.com/#!/yuvipanda/status/200272118821289984 [22:09:48] preilly: http://g.co/maps/x4q46 is where I live, if you're sending a missile here [22:10:22] preilly: it did yesterday :D I hope it does on friday too, though we don't have jon tomorrow [22:10:35] we should also constitute a formal award for the winner at the end of every standup [22:11:00] YuviPanda: my missile was on the way to 9/21, Old Washermenpet, Chennai 21 [22:12:03] preilly: that numbering is ambigous, it wouldn't know which is the old one and which is the new one [22:12:34] every house has two numbers - an older government started transitioning people to 'new' numbers, then went out of power, so that transition never really happened. So everyone now has two numbers :D [22:14:35] YuviPanda: so if the missile takes out 92, GA Road, Old Washermanpet, Chennai, Tamil Nadu 600021, India I should be covered? [22:15:08] nope, 92 GA road is pretty far off [22:15:09] hmm setting $wgUseInstantCommons = true; on mobile-geo (on w_awjr) does not appear to be having the intended effect [22:15:21] depends on the spread radius of the missile [22:15:31] 30 meters [22:15:37] awjr: what is the URL [22:15:42] YuviPanda: https://twitter.com/#!/billyvinning/status/200710576731729920 ? [22:15:46] preilly: you could alternatively take away my internet and have the sam eeffect of a nuke hitting me on the face [22:16:05] preilly a simple test is here: http://mobile-geo.wmflabs.org/w_awjr/index.php/Blah but what i really want is for the images to work on the san francisco article [22:16:07] YuviPanda: ha ha [22:16:14] tfinc: responding. Not sure what's up [22:17:10] as i understand it, with $wgUseInstantCommons=true; allows you to embed images from commons but as if you were embedding them locally [22:17:38] so if i want to use http://commons.wikimedia.org/wiki/File:Kiril_Lazarov_06.jpg locall, all i need to do is [[File:Kiril_Lazarov_06.jpg]] [22:17:40] but no worky :( [22:18:03] awjr: what is the instance name? [22:18:31] preilly it's the mobile-geo labs instance [22:19:09] so mobile-enwp [22:19:31] awjr: [[File:Kiril Lazarov 06.jpg|thumb|Kiril Lazarov 06]] [22:20:21]