June 2013 - ooni-dev - lists.torproject.org

Team Meeting: 2003-07-01 0900 PDT
by Tom Lowenthal 01 Jul '13

01 Jul '13

Greetings people of Earth! On Monday, in keeping with the ancient customs of our ancestors, we will meet to pay reverence to the Dreaded Ooni. Sacrifices are welcome. Here's my proposal for an agenda. It may look familiar. If you wish to wrangle it, please get in touch by email before 1700 PDT on 2013-06-28. If you wish to get in touch after that time, or wish to propose an alternate time for the meeting, please do not rely on email, but telephone me instead. 0900 Convene: how are folks feeling, how's it going? 0905 Report: core team, what did you do this week, and what are you planning? 0920 Assess: how close are we to our nearest deliverable, what does each of us have to do to get there? 0935 Dependencies: Is there anything that you {will|do} need from someone else? 0955 Prospective: What Ooni-stuff will be done this week? 1010 Adjourn See you Monday, -Tom

3 2

Notes from meeting today
by Meredith Whittaker 28 Jun '13

28 Jun '13

CCing all those who's emails I have, and the list. This is what I jotted down from the meeting today. I'm not sure if there's a place these should go, or if there's a better way. For now, add things I missed and correct things I got wrong. I'm assuming we're back on for the regular time, Monday, 12:00pm, EDT, featuring Tom :) Cheers, M Art 'n Aaron have merged the user interface, worked on the backend collector policy (how to allow collectors to set their own policies, etc.), and worked on code to handle downloading and caching. This work will continue into next week. There were some questions about M-Lab NS. Meredith (hi) will CC Art and Aaron on an email with the M-Lab NS developers. Nathan has been working on the threat model, now updated and expanded in the wiki: https://github.com/TheTorProject/ooni-probe/wiki/Threat-Model In a week or two, Nathan estimates he and Daira will be ready to present an overview to the team, either during the regular meeting or some other time. Once the threat model is complete, it will be the responsibility of the broader team to update and revamp as decisions are made and things change. If anyone would like to follow progress in real time, pay attention to the wiki changes. Aaron pointed out that we'll want to clearly educate the end-user about the privacy protections (etc.) they can expect from OONI. Nathan noted that he's working on a doc that describes each role (probe runner, OONIB maintainer, data analyst, etc.), and what assumptions they can make about OONI. This can be a start for clearer user-facing documentation. Review of progress toward "Fully Specified" milestone: - URL input processors: done - Triage test inclusion: done, but Meredith to update item with list of tests accepted by M-Lab Steering Committee - Backend specification: Need to add all items that need to be completed for this to be done (Art) - Test helper versioning spec: Not complete. Need to link to document (assuming it exists) that notes current specification (Art) - Threat model: In progress. ETA ~2 weeks. - Design specs: In progress, need to add all items needed to the list (not clear that everything is accounted for currently). - Spec OONI backend HTTP API: Need to review what exists currently, audit what's missing, and add all that are necessary as separate tickets. - Spec how OONI handles OONIB collector policy: Aaron currently working on this -- Meredith Whittaker Program Manager, Google Research Google NYC

3 3

Team Meeting: 2003-06-24 0900 PDT [be in #ooni 10 mins early]
by Tom Lowenthal 27 Jun '13

27 Jun '13

Hello fine folks, On Monday, we will once again meet in a hangout at 0900 to discuss the future of network measurement, and our contribution thereto. Especially if you had any difficulty joining last week, I entreat you to be in #ooni at 0850 so that we can try to get up to code and properly grounded before 0900. Here's my proposal for an agenda. If you have suggestions for additions or subtractions let's wrangle by email, but not not at 0830 on Monday. 0900 Convene: how are folks feeling, how's it going. 0910 Report: core team, what did you do this week, and what are you planning? 0940 Assess: how close are we to our nearest deliverable, what does each of us have to do to get there? 1000 Adjourn No homework this week. Enjoy your weekend! -Tom

7 9

Re: [ooni-dev] Team Meeting: 2003-06-24 (reschedule to 2013-06-26) 0900 PDT [be in #ooni 10 mins early]
by Arturo Filastò 24 Jun '13

24 Jun '13

On Jun 24, 2013, at 6:06 PM, Tom Lowenthal <me(a)tomlowenthal.com> wrote: > Arturo, > > In future, please do not try to reschedule the project meeting less > than three hours before it starts, and especially not because of a > private conversation. There is a reason that I invite schedule > wrangling in advance: it puts everyone on equal footing, and avoids > surprises. If someone would like to move the meeting, they can either > reply to the meeting-notice email on ooni-dev or -- if that's not > possible -- contact me well in advance. > > Please reply so that I know that you understand what I'm asking. Dude, seriously? On Saturday (the 22nd) I got on IRC and told that Aaron and I had an issue with the schedule. Since we did not get a reply there I then sent an email to you and all the other people in the call that we had an issue with the call and got no reply. Aaron also sent an email about this on ooni-dev (https://lists.torproject.org/pipermail/ooni-dev/2013-June/000021.html) and he also got no reply. Since more than 48 hours had passed and nobody expressed their opinion on rescheduling so I decided to reschedule it. I realize it is a bit late to reschedule, but that was the soonest I was able to get online and send an email (from the airport wifi in Dusseldorf). Next time if you have concerns please express them in time and not after we have tried to warn you of our problems with attending the meeting. Thanks! ~ Art.

1 0

ooni translations
by isis agora lovecruft 23 Jun '13

23 Jun '13

Our code, from what I understand, though I have never worked with Transifex or any of these other translation services, is not particularly well-suited to translation. First question, at what point/release is OONI going to aim for for having translations available? Going with the "usual" route of having a strings.py seems like it wouldn't work for OONI, do to the number of merge conflicts it would create (i.e. if I work on a nettest, and Aaron does some work on the director, and we both change strings.py, then the merge might not work cleanly). Are there any other opinions or ideas on the cleanest way to get ready for translations? We could have an ooni.strings submodule, and stick per file things in there, like director_str.py, etc. Thoughts? -- ♥Ⓐ isis agora lovecruft _________________________________________________________ GPG: 4096R/A3ADB67A2CDB8B35 Current Keys: https://blog.patternsinthevoid.net/isis.txt

3 3

Communication & Meetings [action needed]
by Tom Lowenthal 23 Jun '13

23 Jun '13

I've written a initial wiki page with our meeting schedule and communication norms at <https://github.com/TheTorProject/ooni-probe/wiki/Communication>. Other notes: * All ooni-related mail should either go to the ooni-dev list or CC me. If you're sending something to the list and there's a specific ask for me, you can also CC me to get my attention. * All M-Lab-related mail should CC Meredith. * It's expected that an email directed to one of us with a specific ask will be answered within 24 hours on week-days. * Email expecting a response or action should indicate this in the subject line. # Next Actions * Subscribe to the ooni-dev mailing list at: <https://lists.torproject.org/cgi-bin/mailman/listinfo/ooni-dev>. * Edit that wiki page to add your public contact info, including an email address and your Github handle. If you have other communication preferences or foibles, this is a good place for them too. # Optional Actions * Look through the issues, and assign them to yourself if needed. * File new issues for things you think aren't covered. * Write wiki pages documenting other agreements or knowledge captured this week. Thanks, -Tom

2 1

Use of Chromebot Top Million URLs Instead of Alexa?
by Collin Anderson 22 Jun '13

22 Jun '13

Hello OONI, The source tree for Chromebot contains a list of "top million URLs" for stability testing [1]. The Chromebot list might present an interesting complement to Alexa for the HTTP tests, since it would be more likely resemble real-world conditions through triggering URL-specific responses from censors -- rather than exclusively measuring filtering based on hostname. [1] http://src.chromium.org/svn/trunk/tools/chromebot/top-million Cordially, Collin -- *Collin David Anderson* averysmallbird.com | @cda | Washington, D.C.

1 0

Re: [ooni-dev] Dimming the Internet: Detecting Throttling as a Mechanism of Censorship in Iran
by isis agora lovecruft 21 Jun '13

21 Jun '13

Collin Anderson transcribed 5.7K bytes: > Today, my latest paper “Dimming the Internet: Detecting Throttling as a > Mechanism of Censorship in Iran,” a documentation on three years of the use > of bandwidth throttling as a means of political censorship in Iran, was > posted on the publishing site arXiv. Congratulations, Colin! You are awesome. I put this up on the censorship wiki for Iran: https://trac.torproject.org/projects/tor/wiki/doc/OONI/censorshipwiki/Censo… -- ♥Ⓐ isis agora lovecruft _________________________________________________________ GPG: 4096R/A3ADB67A2CDB8B35 Current Keys: https://blog.patternsinthevoid.net/isis.txt

1 0

Fwd: Dimming the Internet: Detecting Throttling as a Mechanism of Censorship in Iran
by isis agora lovecruft 21 Jun '13

21 Jun '13

----- Forwarded message from Collin Anderson <collina(a)gmail.com> ----- > From: Collin Anderson <collina(a)gmail.com> > Subject: Dimming the Internet: Detecting Throttling as a Mechanism of Censorship in Iran > Date: Thu, 20 Jun 2013 17:48:05 +0100 > Message-ID: <CA+CWxj+Xc-xa_Tr3sM4MEqtMR4Rv-rjv5hNPetG4wEG==DQEZA(a)mail.gmail.com> > To: Collin Anderson <collina(a)gmail.com> > > *I hate to do the mass BCC thing, but wanted to brag to you specifically > and hopefully get your attention for a **bit. I promise June and July will > be an interesting month of research, so please forgive my vanity. - Collin* > > Today, my latest paper “Dimming the Internet: Detecting Throttling as a > Mechanism of Censorship in Iran,” a documentation on three years of the use > of bandwidth throttling as a means of political censorship in Iran, was > posted on the publishing site arXiv. > > Blogpost (with Election data): > http://cgcsblog.asc.upenn.edu/2013/06/20/dimming-the-internet-detecting-thr… > Paper (arXiv): http://arxiv.org/abs/1306.4361 > > “Dimming the Internet" uses a three-year dataset of network measurements as > a monitoring service for political throttling, then applies the methodology > to shed light on the recent history of censorship in Iran, and finds that > Iran’s Internet has experienced prolonged and significant disruptions timed > annually near the anniversary of the Islamic Revolution and 25 Bahman, the > first anniversary of the contested elections, and protests over the > depreciation of the value of the Iranian Rial. Through the Measurement Lab > (M-Lab) platform, anti-censorship researchers gain a diverse and > non-partisan perspective on a network that is often opaque and difficult to > access from outside. The results described not only shed light on instances > of censorship, but also the manner in which public networks are subjected > to a greater degree of disruption than those of business, universities and > governments. > > Iran is not alone in this behavior, with Syria, Bahrain, Myanmar and > Vietnam reportedly utilizing similar tactics. As stories of connection > throttling timed with political instability grow and access to > international communications platforms remains a necessary means for > expression otherwise denied, “Dimming the Internet” provides a framework > for accountability on a trend that thus far has been opaque. In the coming > months, the Center for Global Communication Research at the Annenberg > School for Communication will expand on this methodology as a means to > account for historical cases and monitor this phenomenon on an ongoing > basis globally. > > *“Dimming the Internet” was supported by the Center for Global > Communication Studies at the University of Pennsylvania and Google > Research. They are awesome.* > -- > *Collin David Anderson* > averysmallbird.com | @cda | Washington, D.C. ----- End forwarded message ----- -- ♥Ⓐ isis agora lovecruft _________________________________________________________ GPG: 4096R/A3ADB67A2CDB8B35 Current Keys: https://blog.patternsinthevoid.net/isis.txt

1 0

Team Meeting: 2003-06-17 0900 PDT [be in #ooni 10 mins early]
by Tom Lowenthal 19 Jun '13

19 Jun '13

Hello hello hello fantastic Ooni folks. Get ready for a precociously productive meeting on Monday. # Time This Monday is our first team meeting since the Berlin intensive face-to-face. It's at 9am on the West coast, 10am in the mountains, noon on the East coast, 5pm in the UK, and 6pm in Europe central. If you're planning on coming and I haven't listed your time zone, let me know to include it in future reminders. The meeting is open to all who wish to observe or listen productively. # Venue I intend to meet in the pixellated video realm that is Google Hangouts. My gmail address is flamsmark(a)gmail.com, and you're totally welcome (and encouraged) to try getting in touch with me and testing your video capabilities before the call. If Hangouts will *not* work for you on Monday, reply to this email, and I'll promulgate an alternative meeting venue, likely Uberconference. I anticipate that there may be a few technical hiccups with this new and uncharted technology, so please be in #ooni on OFTC *ten minutes* before we start so that we can set up before the meeting and start on time. # Schedule My proposed tentative schedule for this meeting goes a little like this. I invite you to help me wrangle it by email, but not right before we start on Monday. 0900: Check in: how's everyone doing? 0910: Berlin takeaways: what's on your plate that isn't captured on Github? 0940: Triage upstream: collaboratively move items from Trac to Github. 1010: Week in profile: what things are you planning to get done this week? 1025: Parting thoughts. 1030: Adjourn. # Tasks In order to have a useful and productive session, here are some things that everyone should do before 9am on Monday: 1. Decompress. Travel is tough; come out of the weekend refreshed. 2. Read the agenda. Reply if you have suggestions. 3. Prepare your Hangouts. Make sure we can actually connect on Monday. 4. Review the Ooni tickets on Trac. They're all listed at <http://j.mp/153kpDN>. * * * * * That's all for now. I'll see all your gorgeous smiling faces on Monday. -Tom

3 2