16:11:08 <hellais> #startmeeting OONI meeting 2017-04-17
16:11:08 <MeetBot> Meeting started Mon Apr 17 16:11:08 2017 UTC.  The chair is hellais. Information about MeetBot at http://wiki.debian.org/MeetBot.
16:11:08 <MeetBot> Useful Commands: #action #agreed #help #info #idea #link #topic.
16:11:15 <hellais> link to pad: https://pad.riseup.net/p/ooni-irc-pad
16:11:30 <hellais> is somebody here for the meeting that had some things they would like to discuss?
16:11:49 <onon> I mainly have a question concerning transifex, if there's a way to get context / see where the string are being mapped to
16:12:28 <onon> especially for some strings that are just single words often times several translations can apply
16:14:05 <hellais> onon: Generally the best thing to do is to "open an issue" (i.e. leave a comment in the comment section for the string) and me or somebody else will reply to you
16:14:42 <onon> ok good that's what I've done so far
16:15:19 <hellais> if you want to digg into it yourself you can do that in the web UI by grepping in the source code for the string labelled as "key" in the "context tab"
16:15:26 <hellais> https://github.com/TheTorProject/ooni-wui
16:15:57 <hellais> for android and iOS it's also similar, but maybe slightly harder to infer the context without loading it in xcode or android studio: https://github.com/TheTorProject/ooniprobe-android
16:16:47 <onon> ok I'll try those and use the comment section in case it's unconclusive
16:17:45 <onon> other than that, I saw the documentation could use some updates (e.g. ooniresources / decks locations on homebrew installs), is that already assigned to someone?
16:17:50 <hellais> onon: be sure to flag the comments as "issue" (I think you do that by clicking on "open an issue" instead of "comment" in the transifex UI)
16:18:03 <onon> oh then I did it wrong
16:18:28 <onon> I see, thanks
16:18:31 <hellais> onon: no I don't think there is anybody assigned to that and this would be something super useful
16:18:57 <hellais> yeah the problem is that if you don't mark it as issue it's super hard for me to find the comments that require attention and the UI of transifex is _horrible_
16:19:13 <onon> let me see if I can change the status after the fact
16:19:48 <onon> hm no but I can resubmit
16:20:28 <onon> as for the documentation maybe it would make sense to compile a list of needed changes since I mainly have on my list what I've noticed using ooniprobe myself
16:22:19 <hellais> onon: yeah that would be great. That should probably go in an issue either on ooni-probe or in ooni-web
16:23:28 <onon> maybe ooni-probe since the docs are in the repo there?
16:23:48 <hellais> yeah, that makes sense
16:25:28 <onon> ok I will open one there
16:26:29 <hellais> excellent!
16:26:40 <hellais> is anybody else here for the weekly gathering?
16:26:52 <hellais> Are there any other topics you would like to discuss, bring up?
16:27:25 <onon> I'm good for now
16:27:55 <slacktopus> <agrabeli> hi
16:28:08 <onon> hi agrabeli
16:29:18 <willscott> the metrics for how many reports have been coming in since the mobile launch are really impressive!
16:30:11 <slacktopus> <agrabeli> @willscott yep! It would be good to also have Windows and macOS applications to enable more stable measurements and more types of tests run
16:32:51 <willscott> it looks like diversity / usage is back to about 50% from initial launch. is there work on triggering periodic reminders to re-run the mobile measurements?
16:33:02 <hellais> yeah
16:33:38 <hellais> willscott: I think in the next or the one after, we will be adding push notification support to both android and iOS apps
16:34:22 <hellais> The long term plan is to have orchestration so we will be able to actually trigger the apps to run the measurements directly (if the user has opted in), but as a crutch we would also be able to trigger push notifications to all our users to run the app if we notice they haven't run it in a while
16:34:54 <willscott> well, also the background capabilities for ios at least may be limited to that
16:34:57 <hellais> progress on probe orchestration can be found here: https://github.com/hellais/proteus
16:35:26 <hellais> actually with iOS we can do something like running a measurement when responding to a silent push notification
16:36:17 <willscott> cool
16:36:43 <willscott> is there a count of unique clients that can be on those measurement statistics?
16:37:12 <hellais> feedback is especially welcome on the scheduling semantics, for the moment I went for something fairly simple
16:37:26 <hellais> willscott: not currently, we don't store unique client IDs
16:37:57 <hellais> however as part of orchestration we are considering adding unique IDs to be stripped during sanitisation as we have to store unique IDs anyways to be able to send push notifications
16:38:22 <hellais> for the mobile app deployment we use crashlytics which also gives us accurate user-base metrics
16:38:40 <willscott> right now it's a bit hard to understand how "evenly" those 150k measurements are distributed across the 3k networks
16:39:10 <hellais> yeah I see what you mean
16:39:32 <willscott> presumably a lot of people downloaded it, ran it once, and forgot about it, and then there are a few people who have been diligently running it daily
16:39:53 <slacktopus> <agrabeli> yeah
16:40:09 <hellais> for the last 30 days we have had on Android 18k active users (i.e. people that openned the app)
16:40:22 <hellais> on iOS ~3k
16:40:40 <willscott> that's great
16:42:57 <hellais> yeah I think though most users don't run it that often
16:43:20 <hellais> we do have some people though that are fairly committed, like the stats show that we have about a couple dozen users that use the app every day
16:43:48 <hellais> several hundreds (200-300) that use it 3-5 days per week
16:44:03 <hellais> and thousands that use it 1-2 times per week
16:56:12 <hellais> are there more topics to discuss?
17:02:55 <hellais> I guess not, thanks for attending!
17:02:57 <hellais> #endmeeting