February 2017 - tor-project - lists.torproject.org

Notes from February 9 2017 Vegas team meeting
by Karsten Loesing 13 Feb '17

13 Feb '17

Notes for February 9 2017 meeting: Kate: 1) Coordinating OONI media for ooniprobe phone app release 2) Talking to reporters about uptick in Tor use and downloads 3) Social media Isabela: 1) MOSS #2 invoice/report out - finishing reports for sponsor4 2) Comms Dir interviews - jitsi + irc 3) Working with Linda on user test of Orfox Security Slider - Linda is working with Elio on making sure we have imgs+logos files resources, which eventually can be used by anyone who needs them, but we will apply it at first on our website to bring it in parity with our style guidelines (not change design just make sure we have one type of onion image on the site not 5) - She is also doing a great job on recruiting volunteers to our UX team! She has a list with 4 or 5 different folks who are already with a task and helping out o/ 4) Hiro is working with Metrics team as well as installing schleuder (for using trac via email) - we are planning on hosting an open meeting next week to discuss features for the script she created where you can query trac tickets and do stuff - we are looking at network team wish list as inspiration, just need to triage things a little and define better the 'feature requests' 5) working on sponsorS final report Mike: 1) Working on Sponsor2 traffic analysis resistance. I have most of the system written how I want it; now comes testing. 2) We have a blog URL to test, but Kevin is still slowly fixing remaining issues. I found a few myself and asked him about them. I should just send the URL around to see if others have more. Alison: 1) I'm going to put the social contract up to a formal vote sometime next week (since atagar doesn't want anything grandfathered in. 2) After that, will get back on the membership docs. 3) Phoul and I will meet with Linda next week to discuss the support portal design. 4) Global South outreach continues apace. One of our trainers had a successful workshop in Karachi, and now we're planning the next one with another trainer in Nairobi. Once we've had a few go well, I will write a blog post. 5) I'm reviewing the Tor Meeting agenda feedback emails this weekend. Georg: 1) We made progress on our Sponsor4 items Arturo: 1) Launched ooniprobe mobile app, yay! See: https://ooni.torproject.org/post/ooni-mobile-app/ 2) Made a release candidate for the new ooniprobe web UI. See a live demo of it here: http://demo.probe.ooni.io/ Nick: 1) Wrapping things up with 0.3.0 2) Stabilizing older release series again 3) Trying to finish core-dev hire.

1 0

Notes from February 2 2017 Vegas team meeting
by Karsten Loesing 12 Feb '17

12 Feb '17

Notes for February 2 2017 meeting: Georg: 1) We concentrated our work on Sponsor4 items and on fixing regressions in Tor Browser 6.5 2) Where are we with our applications team? <- we'll discuss things further in Amsterdam + plan to have a meeting there 3) Helped a bit with the Tor Browser related Metrics blog post Nick: 1) Hiring still going on. Lessons learned. 2) I'm going to be semi-afk 2/20 through 2/24. Email will be fine. 3) I think this is the week where we fix the remaining open 030 issues. Another alpha next week probably. Then Sponsor4 prelim work, piles of design proposals, and stable backports? 4) ahf-onboarding seems to be going okay so far (day 2). Shari: 1) Interviewing candidates for Communications Director position. 2) Working on Tor meeting details. 3) Approaching funders. 4) Catching up on stuff from being out of the office last week. Kate: 1) Answering press queries, posting on social media, will be working with OONI on press push next week. Mike: 1) Kevin ran into two issues with the blog that he is still resolving (tag imports have issues, and there is a deployment issue). Sorry for the false alarm last week :/. 2) Working on implementing Adaptive Padding generalization for tor-core (Sponsor2); coordinating with Matt Wright, Marc Juarez, and SecureDrop folks. Alison: 1) Collecting responses for the Tor meeting agenda until tomorrow. Will send a summary to this group before next week's meeting. Continuing to do other meeting planning stuff with Shari and Gunner. 2) Global South outreach: will write a blog post once we've got a few trainings scheduled 3) LFP events upcoming: Pratt Institute, Drexel University, Sacred Heart Church, Temple University 4) Working with Shari, Isa, and Erin on comms director interviews Karsten: 1) Blogged about Tor Metrics' new graph on Tor Browser downloads and updates: https://blog.torproject.org/blog/tor-browser-numbers 2) Planning to add another graph on Tor Browser downloads by operating system. 3) Put out a new Onionoo release and closed about a dozen Atlas tickets towards making Atlas more user-friendly, scheduled blog post for end of February when next Onionoo protocol version 4.0 gets released. 4) Preparing for in-person meeting in Berlin next Friday. Arturo: 1) Fires related to ooni infrastructure all resolved. Data has been reprocessed new database has been populated, by the end of today ooni-explorer will roll-over to the new database and everything will be back to normal. 2) The first stage of the re-engineered data processing pipeline is finished. We are now able to generate "canned" reports that are compressed and result in much reduced storage and faster re-processing times. 3) The ooniprobe mobile release is on track. We expect to upload an app for review by apple today or tomorrow. 4) Addressed all items in the feedback provided by Linda to the new ooniprobe web UI. Live demo available here: http://37.218.242.109/ Isabela: 1) SponsorU stuff is all done and invoice is being processed 2) Sponsor5 Milestone 2 was finished and reported to sponsor 3) SponsorS final quarterly report will be submitted today 4) New DRL proposal - had the call, waiting for follow up steps 5) Need to work on: Task Force proposal - OKRs example - User Growth Strategy update report - sponsor4 reports 6) Interviewing candidates for Comms Dir position

1 0

We're bricking up #nottor; keep your eyes open
by Roger Dingledine 11 Feb '17

11 Feb '17

Hi folks, After another round of irc crazy, we're moving forward with the plan of bricking up the #nottor irc channel: https://trac.torproject.org/projects/tor/wiki/org/meetings/2016WinterDevMee… velope is going to do the actual bricking in the next few days, once he's tied up some loose ends. (Maybe I'll be the one to run the actual commands, so it's got my name on it and it's more clear what's going on.) So, be on the lookout for more misbehavior than usual in the coming days. If you want to help but you don't know how to, let one of us know on irc and we'll try to help you help. Also, if we wanted to do some of the other transitions on that page, like more work on making the mailing lists better, now could be a good time. :) --Roger

1 0

EFF is looking for border search stories
by Shari Steele 08 Feb '17

08 Feb '17

Hey all. EFF is looking for stories of border searches of electronic devices while trying to enter the United States. Pass this along to anyone you know who might fit the criteria: https://www.eff.org/deeplinks/2017/02/invasive-digital-border-searches-tell… <https://www.eff.org/deeplinks/2017/02/invasive-digital-border-searches-tell…> Shari

1 0

New Tor Metrics graph: Tor Browser downloads and updates
by Karsten Loesing 02 Feb '17

02 Feb '17

Hi everyone, we just put a new graph on Tor Metrics called "Tor Browser downloads and updates": https://metrics.torproject.org/webstats-tb.html This graph is the result of a joint effort of the metrics team (with a lot of input on the underlying code from iwakeh) together with Sebastian (who co-authored the original database schema and who operates the web log sanitizer), gk and boklm (who analyze an earlier graph and provided insights about Tor Browser internals), and others who discussed the graph and earlier prototypes. Please take a look at this graph, play a bit with the two inputs (start and end date), and give us feedback by raising questions about the data or giving answers to previously raised questions. The goal would be to write a blog post about this graph together with an early analysis. Currently open questions are: - gk asks on the ticket (https://trac.torproject.org/projects/tor/ticket/21236#comment:11) "The results still confuse me (like: We have 100,000 new downloads each day but that does not show up in the update pings which basically stay the same? We still have more than 120,000 update requests every day, even after almost 6 weeks after the last release?). But that is probably another story. :)" - hellais asked at yesterday's Vegas meeting: "how many times does a normal tor browser do an update ping every day?" which was answered by mikeperry and gk with "twice" "and on every start". This is probably something we should clarify in the graph description. - yawning asks on the ticket (https://trac.torproject.org/projects/tor/ticket/21236#comment:25) "Does it matter that the Linux sandbox behavior is totally different from everyone else, because it uses a different implementation to download, update check, and update? I suspect the user base isn't that big right now, but I'd hate to throw stats off..." Note that we're mostly hoping for feedback on the data, not on the presentation. We know that there's room for making the graph prettier or for providing more inputs to customize it. But we already spent way more time on this graph than we had planned, so we'd save any feedback on the presentation (except for typos or trivial tweaks) for later in the year. Thanks! All the best, Karsten

6 15