[03:23:08] morning all [05:57:15] matanya: are you just trying to be the first to reach T100000 in Phab? ;) [09:17:22] yo [09:17:27] in lyon at the place [09:17:29] it's wix [09:17:36] working outside listening to the breeze [09:21:38] hey halfak o/ [09:21:54] Hey phuedx o/ [09:22:08] I was just talking to a facebook researcher you were working with WRT planout. [09:22:20] oh neato [09:22:36] halfak: are you going to the hackathon? [09:22:49] also, i'd love to take the planout stuff further [09:22:50] Yup. I'll arrive at 11PMish local time tonight. [09:22:57] awesome [09:23:04] i have brought lots of coffee beans etc [09:23:19] halfak: i've just had an idea about that extension that'll make it easier to work with [09:23:23] * phuedx notes it down [09:24:39] halfak: what did he have to say? [09:26:17] He asked me how to pronounce your username :) [09:26:37] But he said that you guys worked together a bit, but he didn't know what came of it or if he could help more. [09:26:45] I promised to ping you to reach out to him again. [09:27:49] I'm still unclear on whether the PHP planout library is open source. [09:27:54] I know the python port is. [09:31:31] iirc they forked it and now it's diverged somewhat [09:31:35] but it's open afaict [09:31:49] Oh! Gotcha. [09:32:21] Another thing we talked about was multi-armed bandit integration. [09:32:58] Seems like that would be really valuable for fundraising. [09:45:48] halfak: i'm still really interested in the integration -- i just need buy in [09:45:59] working on it in isolation is a pita and not what i'm good at [09:46:21] +1. Did you get a good chance to talk to Andrew Green about what he is working on for Fundraising? [09:47:32] no i didn't -- i sucked at that [09:47:44] i shouldn't whinge about not having buy in [09:47:48] i'm going to reach out to him now [09:47:49] Boo. :P [09:47:56] :) [09:48:21] i'm sorta having a free day as i've been travelling since 4 am [09:48:33] got some work done on the plane though! [09:50:22] Yeah. I'm looking forward to that to. It was hard to not prepare some of my projects for the hackathon on the flight here. Experience suggests one *must* sleep on the flight from North America to Europe. [09:50:42] I've the flight to Lyon today -- gonna make sure I'm fully charged :) [09:51:07] Are you at the hostel now? [09:51:09] phuedx, ^ [09:52:02] halfak: yeah, i'm sitting in the garden of the hotel and brewing coffee from berlin :D [09:52:25] halfak: agreed -- you have to sleep [09:59:23] The coffee they have been giving us at WWW tastes like burnt marshmallows. It seems to lack all flavors that I identify as "coffee". [14:15:26] joakino: yt? [14:20:05] yo [14:20:24] phuedx: just checked in [14:20:39] going for Jon Robson and heading to the hostel soon [14:20:48] yeah man -- head on over and we'll party like it's 2015 [15:01:59] mdholloway: i got back a little earlier from the vet than i supposed. fritz is in good health [15:02:20] niedzielski: glad to hear it! [16:17:46] mdholloway: yeesh, both images on today's english main page are experiencing that link preview template issue [16:20:25] niedzielski: yeah, i noticed at least the top one wasn't working properly while doing something else [16:20:43] niedzielski: i wonder whether dmitry got any response to his complaint on the template page [16:20:49] mdholloway: can't be good for link preview testing [16:21:47] niedzielski: nope [20:29:05] mdholloway|lunch: just saw your email and patch. neat! so, we're currently just piping all our crash reports through email into OTRS? [20:29:22] niedzielski: yep [20:29:37] niedzielski: oh yeah, i'm back from lunch :) [20:30:08] mdholloway|lunch: ok cool. so this patch is really just an effort to get a better dashboard experience? [20:30:11] niedzielski: to OTRS where (hopefully) someone manually looks through them and decides whether we know about them or not [20:30:25] niedzielski: yeah, i think that's a fair description [20:30:25] mdholloway: yeah that's rough [20:31:01] mdholloway: ok neat! were there any other backends besides acralyzer you found? [20:31:45] mdholloway: i wonder if we could send to OTRS + Acralyzer or do A/B testing for a while [20:32:19] niedzielski: i don't know of any others; HockeyApp and Acralyzer were the two I knew might be good candidates [20:33:02] niedzielski: I'm not sure if you've used Crashlytics (I haven't), but that's one option it's already been decided we're not going with due to being (as I understand it) fully proprietary/closed source [20:33:03] mdholloway: wow, look at all the extra data you get when you click on a crash [20:33:32] niedzielski: at least that's what I gathered from talking with Adam B. [20:33:39] mdholloway: i've not used it. i used testflight for a while when android was supported and then hockeyapp [20:35:01] mdholloway: neat, ok it looks like acralyzer is the official backend: https://github.com/ACRA/acra/wiki/Backends [20:36:15] niedzielski: yep. [20:37:22] niedzielski: oops, i think i just accidentally deleted the crash group containing all of my contrived crashes... [20:37:53] niedzielski: ah, never mind [20:38:01] niedzielski: looks like you can mark them solved/unsolved [20:38:34] mdholloway: how hard was it to setup on the backend? [20:39:29] niedzielski: On Cloudant, very simple [20:40:00] niedzielski: I gave up on the DigitalOcean instance I was tinkering with this morning; never could get past the ECONNREFUSED issue [20:40:17] niedzielski: for expediency's sake just so i could get something up and running [20:40:58] niedzielski: looks like there are a number of hosted options if we want to keep it simple and don't care about someone else holding the crash data [20:41:22] niedzielski: or at least are comfortable with them holding it given their privacy policies, etc. [20:43:27] niedzielski: Or we could set up our own server. Then we run back into the issue of where to put it here (apparently it's too sensitive for Labs, though it seems ironic to be more comfortable to have someone else holding onto it; I guess I'm not that familiar with Labs and what it's used for) [20:44:48] mdholloway: hm, yeah, i'd be interested what the path is for self hosting [20:45:41] mdholloway: a bit of a tangent, but i wonder what a crash funnel look like [20:52:38] what do you think of the current email based reporting method? it's kind of a separate issue but another aspect i'm definitely interested in fixing. i'd like it to be fully automated -- i'm sure the percentage of people who bother to send the crash email now is very low. [20:59:54] mdholloway: i like that it's as simple as an email. that's probably where my positive feedback ends [21:00:44] mdholloway: one thing i like about the current design is that the system crash report dialog doesn't seem to be exposed? this means all our crash reports go to one spot [21:01:29] niedzielski: that's true [21:03:44] mdholloway: i guess native crashes and OOMs leak through but i would guess those are much rarer. i see 51 crashes in the play console for the last six months [21:04:35] mdholloway: the alternative is not fun: check play, check amazon, and check custom backend [21:05:12] mdholloway: we had to do that at my last gig and it was burdensome [21:08:06] niedzielski: i would think that wouldn't change with acralyzer, at least, since we're just pointing the crash reports we're currently sending to OTRS to a different backend. [21:08:16] mdholloway: correction on htat number above: 51 crash *groups*, ~150 occurrences total. still pretty small number given the timespan, the version inclusiveness, and the download numbers [21:08:26] niedzielski: was it at your last job you were using HockeyApp? [21:08:39] mdholloway: yeah, i agree with that assessment. hopefully just a much nicer dashboard [21:08:44] mdholloway: that's right [21:08:52] niedzielski: i wonder how many amazon installs we have. I'm not even sure i have the login. [21:09:18] mdholloway: adam hooked me up recently. let me take a peek [21:15:14] mdholloway: hm, our monthly active devices is ~50k with a peak in the least year at around ~65k in mid january [21:15:16] niedzielski: was just playing with your "search wikipedia" patch, btw. cool feature, but it would be nice if we could avoid having to click back through the main page. Not sure if it's possible without a substantial change since (without having looked at the code yet) I suppose you're launching the underlying PageActivity [21:16:04] mdholloway: i think it's an easy change. i have mixed feelings about it because i don't want to kick the user out if they didn't intend to leave the app and vice cersa [21:16:08] versa* [21:16:33] niedzielski: i see. [21:17:11] niedzielski: to me it feels like it "should" go straight back to the browser. but let me play with it a bit more. [21:17:16] mdholloway: feel free to weigh in on the patch one way or another [21:17:39] mdholloway: i don't have strong feelings about it [21:18:10] mdholloway: also try the search widget. the production behavior is to do as you describe [21:18:22] mdholloway: the homescreen search widget that is [21:19:12] niedzielski: i'll give it a whirl [21:22:04] niedzielski: hmm. i'm not crazy about that, either (still seeing the underlying page even though it's immediately dismissed). i guess for these purposes i just wish search were its own activity. [21:22:49] mdholloway: if you try the production or master version of the app, i htink that will be more the behavior you're looking for [21:29:22] niedzielski: even in the production version i'm not 100% thrilled. (as an aside, it looks like the widgets all use the production logo regardless of the version they're coming from -- would be nice to differentiate). [21:30:33] mdholloway: yeah, i'll make a phab for the icon issue. i would like the search widget to accept input on the homescreen but haven't looked into it [21:31:21] niedzielski: agreed.