October 2018 - tor-project - lists.torproject.org

Notes from October 18 2018 Vegas team meeting
by Karsten Loesing 21 Oct '18

21 Oct '18

Notes for October 18 2018 meeting: Roger: 1) Sue: does our grant forecaster have valid solutions for making the numbers work out now that Sponsor19 is underway? 2) I might be missing next two vegas mtgs due to Taipei trip 3) I'm talking to Isa / George / Steph about Tor getting an NYU affiliation 4) ahf points out that for any teams that need a mini meeting before the next major meeting, in Brussels right before FOSDEM is a great choice. Georg: 1) Release preparations for Tor Browser 8.0.3, 8.5a4, and 1.0a3 for Android Alison: 1) Sent Tor Meeting date ideas to tor-internal. Gathering data about possible locations for next time -- Lisbon, Athens, Tbilisi. Anyone have initial thoughts about any of those locations? 2) Working on new Library Freedom website content, LFI application, recruitment, and curriculum for the next round, plus finishing up the last few weeks of the first LFI cohort. 3) Meeting with community and UX teams about sponsor9 travel today. 4) Sent an email to Isa, Shari, and Pili about possible community and UX summit at IFF next year. 5) The Glass Room Experience starts at a number of US libraries this week! 6) Next week we'll follow up with the organizers of Tormenta (feminist meetup in Mexico City). 7) Submitting IFF CFP early next week. 8) Finished up sponsor19 task 9 with Maggie, Arthur, and Pili 9) Working on community portal content. Missing the notes from the community portal mapping session from the meeting. Did you take those notes Pili? 10) Going to DRL implementers meeting next week to talk to them about all of our great usability and community stuff. If there are particularly great things you want me to focus on, let me know! 11) Maggie wants to talk to this group about the volunteer coordination efforts. What's the best method? Mailing list or coming to our next IRC meeting? [email the list i think isa] Sarah: 1) YE campaign launches next Tuesday! Tor Browser banners, social media, blog post, and an email to certain email segments. 2) Planning next phases of the campaign. 3) Updating Sponsor list on the website. Do we want to keep the threshold at $10,000? Do we want to allow individuals to be listed, if that is something they would like? 4) Al working on anti-censorship grant proposal with 11/9 deadline and a modularization proposal to be submitted this month. 5) We are compiling a list of small/family foundations and will send a postal mail letter about our work in the coming weeks. We'll also include past donors for whom we do not have email addresses. Pass along suggestions of foundations that should be included. 6) Attending DRL Implementers meeting next week. Nick: 1) 0.3.5.3-alpha released; 0.3.6 merge window is open. Team is tracking down bugs and going through the merge backlog. 2) Gettor meeting went well; hoping network team can still contribute. Steph: 1) preparing for EOY campaign launch on Tuesday 2) preparing LibrePlanet submission. Alison, Isa, Nathan, Nick, and I are in for a panel. 3) putting together copy on Tor’s history for the website 4) working with The Berkeley Group on our brand perception study 5) submitting a FOSDEM stand for us Anto: 1) EOY campaign - I made banners for TB, reviewed the implementation and localization. I made Banners for tpo.org, working on the implementation with hiro. Made swag options, everything was delivered. Worked with Giant Rabbit on donate.tpo. Made banners for social media. 2) Did OONI Probe app design review, fun as always. 3) Reported for S19 with Arthur and Matt. 4) Helped with OTF onions review. 5) Put together data for pili to report S17 Q1. 6) Reviewing research.tpo.org which irl put together in staging - https://research-staging.torproject.org/ 7) Trying to get tpo.org and tpo.org/about content frizzed so we can move to development. Arturo: 1) Wrapping up OONI Probe mobile design and getting ready for development handoff 2) Writing specification for several new OONI tests and network measurement techniques isabela: 1) Sent onion services proposal to OTF (What is this? ~ Arturo - hahahaha not ooni but onion! LOL. Ok :P) 2) Two important meetings for Tor are now in place, 1) Fundraising/Grants status weeky syncs and 2) Tor Browser release bi-weekly syncs 3) Changed my trip next week - instead of going to Taiwan OTF Summit I am doing DRL Implementers meeting in DC 4) Finishing reports so I can be done with PMs things remaining from the era prior gaba+pili era so I can be done with handing things off to PMs and complete the transition 5) Met with Julius (he was in NYC!) One of the things we discussed was Mozilla All hands and Tor's presence 6) Will meet w/ Shari on Monday (she will be in NYC) Karsten: 1) Drafted a job description for the new metrics developer we want to hire. 2) Released CollecTor 1.8.0 with some minor fixes and improved logging to hopefully track down an issue where we were missing server descriptors two weeks earlier. 3) Added a new graph to Tor Metrics that compares total consensus weights across bandwidth authorities (#25459). Mike: 1) Sponsor2 things 2) Nick - How is the datagram paper coming along? Mozilla people want to meet with us at their all hands in early December, and it is relevant (what is the best place/time to discuss it?). Gaba: 1) in Taipei next week for OSF summit 2) will prepare and be on time for next meeting :)

1 0

August and September community team highlights
by Alison Macrina 17 Oct '18

17 Oct '18

August and September 2018 Community Team highlights Meeting notes ================================================================== https://trac.torproject.org/projects/tor/wiki/org/teams/CommunityTeam#Curre… Tor Meeting ================================================================= In August, we began continued organizing events for the Mexico City Tor Meeting, and started holding biweekly meetings to organize the open days with the help of local folks. These meetings helped to finalize the open days agenda and create the promotional blog post. We worked with other local people to plan and promote the Tormenta feminist meetup for immediately after the Tor Meeting. We also started planning State of the Onion plenary and sent the invite-only agenda out to meeting attendees. In September, we did a final check of all of our MX meeting todo and then we headed to Mexico for the meeting! Documentation ================================================================== Gus and emmapeel worked on content corrections and content updates in the Support Portal. Gus, Jaruga and Phoul updated the Tor Browser Manual with TB 8 release. Gus updated the Tor Relay Guide PT-BR version with the main updates. Localization ================================================================== In August emma did a call for translations for the support portal and started organizing a Localization Lab AMA. Library Freedom Institute ================================================================== In August, Alison held the LFI held our in-person meeting in NYC where she taught the cohort about Tor, Tails, and running effective workshops. Steph came by to teach about media literacy, and sysrqb helped out with the Tor training. The rest of August was LFI weeks 10-13. In September, LFP started planning the Glass Room Experience in North American libraries and museums. LFI completed weeks 14-17 of our curriculum. Tor talks and outreach ================================================================== Gus organized and held Tor trainings at the University of Campinas (Unicamp) August 23rd, in Mombasa and Nairobi, Kenya from August 28th to September 9th, then Oaxaca, Mexico, and Ciudad de Mexico Meetup in Rancho Electronico right before the Tor Meeting at the end of September [1]. Gus also spoke at "IX Semana de Privacidade do CGI" about privacy by design and Tor Project. Steph did a Tor talk for HS students in NYC August 15th. Gman999 held a Tor Meetup at NYU/Poly on August 2nd, and began planning the next NYC meetup for October. Relay advocacy ================================================================== In August Colin started organizing the relay operator meetup for Mexico City. He also created a system to keep track of new relay operators joining the network, and sent a monthly "welcome" email to these operators with similar information as the introduction emails. ================================================================== [1] https://blog.torproject.org/events/tor-meetup-ciudad-de-mexico [2] https://blog.torproject.org/events/ix-seminario-de-protecao-privacidade-e-a…

1 0

Note from the Tor Browser meeting, Oct 15 2018
by Georg Koppen 17 Oct '18

17 Oct '18

Hi all! On Monday we had another weekly Tor Browser meeting. The chat log can be found on http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-10-15-18.00.log… and below are the notes from our meeting pad: Monday October 15, 2018 Discussion: -sponsor 19 reporting -roadmap "finalization": https://pad.riseup.net/p/tbb-roadmap-2018-19 (GeKo: we stick with what we have right now and adapt as we are moving forward) mcs and brade: Last week - Filed and fixed #27994 (Use new logo in Tor Launcher). - Commented in #28002 (The precomplete file in en-US Windows installer is incorrect). - Spent a lot of time on #26263 (browser app icon positioned incorrectly in macOS DMG installer window). This week: - #26263 (browser app icon positioned incorrectly in macOS DMG installer window). - #27828 ("Check for Tor Browser update" doesn't seem to do anything). - Review the team roadmap, especially our tasks. GeKo: Last week: -worked on #26475 (Stylo related reproducibility issues); it seems I have a patch but still need to dig deeper to understand what's exactly going on) -wrote a patch to update our release process document (#25030) -reviews -helped with sponsor8 reporting (sysrqb, igt0: please have a look at https://storm.torproject.org/shared/LDu1Qye1TxTmY8xfTar1vjJ7ix4HOrvJe7Za5MR… and make sure I did not miss anything we could add for the past three months) -helped with the onion services proposal -helped with the anticensorship dev applications -started to update the Tor Browser spec (#25021) This week: -release prep -more reviews -look closer at #28039 to make sure we don't backport that bug -landing patches for #26475 -more work on Tor Browser spec update -start investigating the single-locale language repacks (#27466) -esr60 wrap-up (mcs/brade: Could you finish #22074 for that? How much is left?) from mcs: We will have to take a look at our notes but there might be some low priority tickets that we should file. pospeselr: Last week; - worked on #3600 (disable redirect cookies) - released tbblogger (cleaned up version of logger built to diagnose that windows race condition, should be helpful for similar issues in the future) https://github.com/pospeselr/tbblogger This week - con flue is back for round #2 (have a cold) - finish up #3600 - take a look at Arthur's suggestion for #26540 (pdfjs range-requests going out on system circuit) sysrqb: Last week: email backlog began sponsor 19 report Worked on #27616 (rust audit) Took over BridgeDB This week: Finish #27616 Finish sponsor 19 report (with help from anyone) Sponsor 8 report update Begin working on #28051 (Orbot integration) Bug fix #28051 igt0: Last week: - Worked on #25013 (Desktop is working, now doing small tweaks to make it work on mobile) - Started to write a torbutton proposal. (I am still digesting a bit the meeting we had in mexico, to make sure the proposal is not missing anything) - Read few web/android fingerprinting papers (Session Fingerprinting in Android via Web-to-App Intercommunication) This week: - Finish #25013 - Send torbutton proposal pili: Last week: - organising meetings - re-grouping after Mexico This week: - Tor Browser release meeting - every other week on Wednesdays at 18:00 UTC - starting this Wednesday 17th October - gettor: hiro has volunteered to take it forward, but should this be within this team? - meeting to discuss its future - Wednesday 17th at 16:30 UTC ilv can't make it at that time, watch this space... (GeKo: I think applications team is fine for now) - Sponsor19 reports: Task 7 and Task 9b - - Sponsor8 Q3 report pad: https://storm.torproject.org/grain/7W8G8jxiWRS6BdWEbHAMiN/ - Orfox issues from Fabiola (Guardian Project): How do we want to deal with these going forward? Let's talk about it next week... too much on this week boklm: Last week: - made patch for #27218 (generating multiple bundles in parrallel). On my build machine it seems to be 3.5 times faster than before. - fixed #28002 (fix the precomplete file in the en-US installer) - reviewed patch for #25030 (Update release process document) This week: - work on testsuite - check if more updates are needed for #25030 - help with building new releases arthuredelstein Last week: - Worked more on https://bugzilla.mozilla.org/show_bug.cgi?id=1330467 (FPI permissions, getting closer!) - Started work on donation banner code - Reviewed #26540 (pdfjs range requests not respecting FPI) - Worked on S19 report sections This week: - Finish donation banner - Add some locales for TBB - https://trac.torproject.org/projects/tor/ticket/27200 (hide Firefox favicon from about:tor - Try to post patches for FPI permission on bugzilla - Help with finishing S19 report sections sisbell: Last week: - Setup location to host android dependency tarball (we will move host later as part of integration) - #27440 - using android ndk prebuilt gcc and llvm - #27443: No more downloads of android dependencies during (uses tarball of dependencies). Project aligned with all changes in android-toolchain - Investigated deeper in why apk not reproducible (have defined some possible causes) - Summary: we have a complete build that doesn’t depend on network This Week: - Investigate differences in apk - start integration of changes - testing of #27441 traumschule: Last week: - #25475 (TB Credits): wrote a simple bash script to collect committers of several repos and need input how to go from there (the created output has ~6k lines with many duplicates), also wrt to non-code contributions. This week: - collected several TB 8.0.2 log errors and try to reproduce them, need to investigate why noscript disappeared Georg

1 0

Notes from network team meeting, 15 Oct
by Nick Mathewson 17 Oct '18

17 Oct '18

Hi! Meeting logs at http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-10-15-16.58.html Meeting notes below: = Network team meeting pad! = Welcome to our meeting! Mondays at 1700 UTC on #tor-meeting on OFTC. (This channel is logged while meetings are in progress.) Want to participate? Awesome! Here's what to do: 1. If you have updates, enter them below, under your name. 2. If you see anything you want to talk about in your updates, put them in boldface! 3. Show up to the IRC meeting and say hi! Note the meeting location: #tor-meeting on OFTC! (See https://lists.torproject.org/pipermail/tor-project/2017-September/001459.ht… for background.) After each week's meetings, the contents of this pad will be sent to tor-project @ lists.torproject.org. After that is done, the pad can be used for the next week. == Previous notes == (Search the list archive for older notes.) 10 Sep: https://lists.torproject.org/pipermail/tor-project/2018-September/001972.ht… 17 Sep: https://lists.torproject.org/pipermail/tor-project/2018-September/001982.ht… 24 Sep: https://lists.torproject.org/pipermail/tor-project/2018-September/001996.ht… 1 Oct: No online meeting; in-person meeting in Mexico City. 9 Oct: https://lists.torproject.org/pipermail/tor-project/2018-October/002005.html == Stuff to do every week = * Let's check and update the roadmap. What's done, and what's coming up? url to roadmap: https://docs.google.com/spreadsheets/d/1Ufrun1khEo5Cwd6OwngERn829wU3W3eskdr… * Check reviewer assignments at https://docs.google.com/spreadsheets/d/1Ufrun1khEo5Cwd6OwngERn829wU3W3eskdr… * Also, let's check for things we need update on our spreadsheet! Are there important documents we should link to? Things we should archive? * Check rotations at https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/TeamRot… * Community guides, it's time to hand off to the next guide! * Let's look at proposed tickets! [but see discussion] https://trac.torproject.org/projects/tor/query?status=accepted&status=assig… == Reminders == * Remember to "/me status: foo" at least once daily. * Remember that our current code reviews should be done by end-of-week. * Make sure you are in touch with everybody with whom you are doing work for the next releases * Remember to fill up actual point when you finish a task (as well as "fix" the estimate when starting the issue). * Add planned PTO to the calendar https://storm.torproject.org/shared/X4hcTHZ9_Nw14FzTi3kabO6E8etGYHwLvshGv_C… ------------------------------- ---- 15 October 2018 ------------------------------- == Announcements == - Please work on reviews - Please work on 0.3.5 items Please don't bulk-delete all the old entries from this pad any more. Instead, delete the "planned" and "actual" for the previous week, but leave the "planned" for this week in place. == Discussion == Is there anything assigned in 0.3.5 that you won't be able to finish up RSN? These tickets in 0.3.5 are not assigned and seem important to fix: https://trac.torproject.org/projects/tor/query?priority=Immediate&priority=… Let's figure out how that will happen. Roadmap: status. Anything else we didn't add, should be in the roadmap? asn: me and dgoulet assigned reviews for this week. we had tons of tickets because merge window just opened. if people can't fit it in one week given all the other stuff, we think that's ok. Proposal to change first week meeting of each month weekly meeting to Tuesday 23:00 UTC (the time of the patch party: https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam#Meeting…) > confirmed the change of the 1st week monthly meeting to Tuesday 11pm UTC. Anybody blocked that needs input on anything? == Recommended links == Have a look at Catherine West's rustconf 2018 closing keynote. Lots of neat architectural thinking. https://kyren.github.io/2018/09/14/rustconf-talk.html == Updates == NOTE NEW FORMAT! Name: Week of XYZ (planned): - What you planned for last week. Week of XYZ (actual): - What you did last week. Week of ABC (planned): - What you're planning to do this week. Help with: - Something you may need help with. PLEASE DO NOT BULK-DELETE THE OLD ENTRIES! Leave the "Planned" parts! Nick: Week of 10/8 (planned): - Talking about decentralization at Berkman on Thursday - Post-process meeeting notes into a usable form - Work with gaba et al to finalize roadmap - Review and merge - Work on continuous integration issues - Find a better solution on #27971 (having to force security level 1 for TLS backward compat) - Try to fix bugs in 0.3.5 - Finish whitepaper? ✘ - Work on sketch for subsystem API - Work on sketch for communication API Week of 10/8 (actual): - Got appveyor passing again - Led a discussion about decentralization at berkman - worked on meeting notes a little. - updated roadmap tickets, making sure they were accurate - Tried to work on a solution to #27971, but got bogged down in tricky testing issues. I think we might be able to hammer something sensible out here, but we might need to step back and take stock. - Assigned a bunch of high-priority items in 0.3.5. - Reviewed fix for #27808 - Review and merge - Signed up for Mozilla all-hands in Orlando - Tried to fix NetBSD compilation - Iterated on subsystem API - Iterated on communications/messaging/publish-subscribe API Week of 10/15 (planned): - Any roadmapping tasks Gaba asks me to help with. :) - More review and merge - Finish new-API design proposals, ask for review - Meet to discuss Gettor plans - Talk with Teor about ideal meeting schedule (ie, which meeting to move to a more convenient time) - Talk with Teor about stable maintenance? - Talk with Catalyst and Ahf about bootstrap reporting subtasks and plans - Talk with Gaba about hackweek planning - Release an 0.3.5 alpha - Open merge window for 0.3.6. Help with: - Mikeperry, can you find/create the tickets for the WTF-Pad roadmap entries? Mike (sick, may not be online during meeting): Week of 10/8 (planned): - OMG so much followup - Create tor-researchers list - Figure out Mozilla all Hands - wtf-pad mails Week of 10/8 (actual): - Stayed sick - Fixed up wtf-pad code issues and organized TODO based on code review - Sent mails about wtf-pad Week of 10/15 (planned): - Get farther into wtf-pad updates; update roadmap - Gather other wtf-pad implementations and data ahf: Week of 10/8 (planned): Sponsor 8: - Figure out which tasks I'm on from the roadmap session and begin there. Sponsor 19: - Work on PT document for Kat. Misc: - Backlog of Trac + IRC + Mail - Look into sysadmin candidate + participate in interviews. - Catch up on hiring process for anti-censorship team role. - Go over my meeting notes from the Tor meeting to see if we need to fill out any tickets. Week of 10/8 (actual): - Participated in two interviews for sysadmin candidate. - Lots of CV reviews for next round of sysadmin interviews. - Got CV's for anti-censorship candidate. - Went over (my own) meeting notes from Mexico for ticket creation. - Reviewed tickets #27772, #27194, #27943 - S19 PT info collection. - S8 reporting for Gaba and Isa. Week of 10/15 (planned): Sponsor 8: - Back to using timer based event loop handling for PT's on Windows as per discussion in Mexico. (#25502) - Look into which initial messages we should submit from the PT. Sponsor 19: - Finish document section on PT's for Kat's S19 report. Misc: - Anti-censorship + sysadmin job interview tasks. - Lots of reviews(?) with merge window opening? asn: [Will be on a flight back home during the meeting. Might be able to attend the first part of the meeting depending on takeoff time.] Week of 10/8 (planned): - Catch up with intense amounts of email, backlogs and minor tasks that have accumulated during the meeting. - Do a presentation on "state of Tor" in FOSSCOMM (the Greek open source conference) on Saturday. - Maybe try to read some more WTF-PAD code if I get the time. Week of 10/8 (actual): - Tried to finish up backlog but lots still remains. - Worked on onion services proposal. - Did talk and workshop on FOSSCOMM (the greek open source conf). - Did reviews (#27709, #27928). Week of 10/15 (planned): - Mike: we need to make tickets for all the WTF-PAD roadmap stuff. - Finish up backlog. - Check the censorship dev job applications. - Do all the reviews (many!) - Read WTF-PAD backlog. Not sure if I will have time to start the big review yet, given how much other stuff I have to review. dgoulet: Week of 10/8 (planned): - Write Sponsor19 report. - Figure out where I am in the Roadmap and start on that. - Prioritizing 035 tickets before merge window opens next week. Week of 10/8 (actual): Week of 10/15 (planned): gaba: Week of 10/8 (planned): - roadmap - cleaning on notes - schedule 1 on 1s Week of 10/8 (actual): - some 1 on 1s - fundraising stuff - roadmap Week of 10/15 (planned): - weekly 1:1s - meet to discuss gettor plans and responsabilities - start planning hack-week - anti-censorship dev position - fundraising catalyst: week of 10/8 (2018-W41) (planned): - update existing Mexico City session notes from my handwritten notes - travel accounting - reviews - talk more about hiring process stuff with ahf and komlo? - design meetings rotation Week of 10/8 (2018-W41) (actual): - reviewed Mexico City session notes; nothing really needs updating from my written notes - travel accounting - reviews - worked on getting test-network to run in Travis CI. it seems tricky and unlikely to happen in the 0.3.5 timeframe. - worked on the mystery core file in Travis that happens on some builds (distcheck with Rust?) implemented more diagnostics to help us track it down (#28024) Week of 10/15 (2018-W42) (planned): - reviews - other high-priority 0.3.5 work as needed - open some tickets with observations to help get Chutney reliable enough to run from CI - review anticensorship job applications? teor: Week of 8 Oct (planned): - (I was returning from the meeting, and on leave.) Week of 8 Oct (actual): - (I was returning from the meeting, and on leave.) - Offered to do a Tor talk at a local Internet Freedom Hack - Asked Jon to send stickers etc. Week of 15 Oct (planned): - Post-travel admin - Blog post on PrivCount research - Work on PrivCount in Tor prototype: module design, merge privcount_shamir, stub other modules - Code reviews - Meeting about Tor talk - Make the fallback script ignore addresses in the whitelist - Inbox zero? Week of 15 Oct (actual): - Deal with (most of) my email backlog - gave advice on #28042 (sbws doesn't have enough results), reviewed fix in #28062 - reviewed IPv4/IPv6 autoselection patch #27490 - reviewed bug triage process, and added links to useful queries Feedback: Reviewing all modified tickets is really hard. (I want a timeline view that just has Core Tor tickets, but that seems impossible) - software updates Help with: - nickm, can you help me triage the remaining children of #25669 (privcount shamir)? - I can do most of them, but I don't know how to deal with i128 miscompilations (#26945) Can we declare all platforms that miscompile Rust i128 as unsupported? Or do we need to add code to check for errors? Help with: (next week) - gaba, I don't want to be the only person helping wih sbws. Please assign someone else to sbws on the roadmap. <<not sure which issue you are refering to --gaba >> juga: [afk during meeting, back online from 19:00 UTC] Week of 10/8 (planned): X reorganize onbasca docs X publish onbasca docs used for bwauth session in tor meeting X fix sbws minor bugs X sbws release 0.8.0 X update sbws deb package to 0.8.0-1 X mail other bwauths with the info about new sbws package/release X setup new bw scanner box to send results to dirauth X try shadow - sbws 0.8.0 stretch-backports Week of 10/15 (actual): - all that does not have "X" above^ Week of 10/15 (planned): - what to do with small bandwidth files (#28042) - 2 new minor bugs in sbws - upload sbws deb release when stem deb release 1.7 - sbws 0.8.0 stretch-backports, when ^ - check torflow in shadow, worth implementing sbws in shadow? - write in human language about the current problem with bandwidth scaling - update bandwidth file specification Help with: - teor: - #28042 (teor says: done!) - anyone: - should dirauth start taking results from sbws when we decide/fix #28042 (the dirauth/sbws is ready to do it) (teor says: yes, one dirauth is safe. Please open a task so we can track issues. Let's monitor network performance and consensus weight before and after. mikeperry, is there anything else we should watch?)

1 0

Tor Browser Release meeting
by Pili Guerra 16 Oct '18

16 Oct '18

Hi everyone, As some of you may know already, we want to start doing a regular Tor Browser release meeting so that: - any Tor Browser stakeholders can be informed about what is currently planned for a given release - the Tor Browser team can discuss any dependencies they have with other teams/stakeholders for a given release Everyone is welcome to attend and, if we would like you to attend a particular instance of the meeting, we will invite you personally also :) To avoid meeting fatigue, we'll do this every other week for now and review whether we need to increase the frequency as we go along. I'd like to propose 15:00 UTC on Wednesdays, starting this Wednesday (17th October 2018), at #tor-meeting on IRC for this meeting. We can reserve the whole hour, but hopefully we will only need 30 minutes for it. Next Tor Browser release is due on the 23rd October 2018 and you can find our current roadmap here[1]. I look forward to seeing you there. Thanks! Pili [1] https://pad.riseup.net/p/tbb-roadmap-2018-19 — Project Manager: Tor Browser, UX and Community teams pili at torproject dot org gpg 3E7F A89E 2459 B6CC A62F 56B8 C6CB 772E F096 9C45

4 5

September Communications Report
by Stephanie A. Whited 15 Oct '18

15 Oct '18

Hello Tor, In September, comms: * continued to support Sarah with the EOY fundraising campaign, and we are now finalizing some final pieces before the launch * worked with several teams to write copy for and promote the TBA alpha launch * started working with The Berkeley Group on a brand perception study, the results of which could help us shape our future messaging * started collecting stories on how using Tor has helped people to include in upcoming campaigns and materials * promoted events including the Open Hack Days, Toronto Public Library Digital Privacy Expo, and others * planned for 2019 campaigns September comms in links and stats: New blog posts https://blog.torproject.org/how-has-tor-helped-you-we-need-your-stories https://blog.torproject.org/new-alpha-release-tor-browser-android https://blog.torproject.org/hack-us-mexico-city-hackea-con-tor-en-mexico Twitter avg 3 tweets/day New followers: 3,829 Top tweets: https://twitter.com/torproject/status/1043210153384919046 https://twitter.com/torproject/status/1037397236257366017 https://twitter.com/torproject/status/1042805068507086850 Facebook at least 1 post/weekday New followers: 233 Mastodon at least 1 post/week New followers: 420 Instagram at least 1 post/month New followers: 42 LinkedIn at least 1 post/week New followers: 55 Newsletter 1/month https://newsletter.torproject.org/archive/2018-09-27-tor-browser-android-we… Thanks to anto and hiro for the fresh look of newsletter.torproject.org! Notable press https://techcrunch.com/2018/09/07/tor-project-launches-official-mobile-brow… https://www.lifehacker.com.au/2018/09/what-is-the-tor-browser/ https://www.popsci.com/alternative-phone-browsers -comms -- Stephanie A. Whited Communications Director The Tor Project IRC: stephw PGP Key ID: 39A876AD <https://pgp.mit.edu/pks/lookup?op=get&search=0x6D6B72C339A876AD>

1 0

online environment blurb
by George 15 Oct '18

15 Oct '18

I know there's occasional issues regarding how some people interact on IRC and mailing lists, and I also know there's no magic bullets to ensure a friendly environment. But I jotted down this as a draft for the content of some solution or another. I don't know the form it would take, but at least it's a start at the substance. **** Tor Project channels such as mailing lists and IRC are primarily populated by diverse, uncompensated volunteers and privacy enthusiasts, with a wide range of native languages and computer experience, dwelling in an array of real-life conditions. The average online participant is motivated to assist others or seek help in circumventing censorship and mitigating surveillance. On that note, we implore everyone to maintain a friendly and collegial tone. You are unlikely to personally know other online dwellers, so realize their own physical circumstances may be very different from your perceptions. Online Tor channel participants might not be fluent in the most commonly used languages, in particular English. Interpretations and tones are easily deceptive, even among speakers of English variants. Conducting oneself with patience and understanding is vital in keeping online discourse collaborative and productive. In other cases, online Tor participants may not be expert computer users. Clearly phrasing technical questions isn't an innate ability, and more experienced users should look to ask simple, non-patronizing questions to help them articulate issues they face. Finally and maybe most importantly, online participants may be in high-pressure environments, from dodging the watchful eyes of management or more starkly, evading an oppressive government. Possible repercussions for engaging in the Tor online community could mean loss of employment, harassment or worse. Keep that in mind when engaging in online Tor channels. Patience and understanding, in addition to a imaginative empathy, allows us to make our community stronger and more capable of assisting each other. -- 34A6 0A1F F8EF B465 866F F0C5 5D92 1FD1 ECF6 1682

5 6

September 2018 report and October 2018 plans for the metrics team
by Karsten Loesing 15 Oct '18

15 Oct '18

Hello Tor, hello world! Below you'll find the highlights of Tor metrics team work done in September 2018. Note that, starting this month, we extended the format to also give a few expected highlights for the current month, October 2018. On behalf of the Tor metrics team, Karsten September 2018: Fully integrated the recently added Reproducible Metrics page [1] and the updated Statistics page [2] on all graph pages by adding the sentence: "Learn more about the CSV data format (Statistics page link) or how to reproduce (Reproducible Metrics page link) the graph data." [1] https://metrics.torproject.org/reproducible-metrics.html [2] https://metrics.torproject.org/stats.html Made some more progress on Sponsor 13 [3] objective 1 by drafting a structure for the technical report and picking a plausible candidate for evaluating a batch processing framework. [3] https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor13 Released ExoneraTor 4.0.0 [4] that reduces the overall database from 243G to 63G and mean response time from 18.9 to 2.3 seconds. [4] https://lists.torproject.org/pipermail/tor-relays/2018-September/016209.html Released Onionoo 7.0-1.18.1 [5] that extends the "version" parameter to support lists and ranges, removes redundant "1_week" and "1_month" graphs from clients documents, changes "3_months" graphs to "6_months" graphs in all documents containing history objects, removes the "fingerprint" parameter, and removes the previously deprecated "as_number" field from details documents. [5] https://lists.torproject.org/pipermail/tor-dev/2018-September/013431.html Released Tor Metrics Library 2.5.0 and Tor Metrics Website 1.2.0 [6] for the primary reason that libraries contained in the tarball should match the ones needed to build current master. [6] https://lists.torproject.org/pipermail/tor-dev/2018-September/013459.html Attended the Tor meeting in Mexico City where we presented our work as part of State of the Onion [7] and in a session called Tor Metrics Ecosystem: Data Collection, Archive, Analysis, and Visualisation [8]. [7] https://people.torproject.org/~irl/2018-09-mexicocity-metrics-soto.pdf [8] https://people.torproject.org/~irl/2018-10-mexicocity-ecosystem.pdf October 2018: Extend the existing graphs on Tor Browser downloads by platform [9] and Tor Browser downloads by locale [10] to "Tor Browser downloads and updates by platform" and "Tor Browser downloads and updates by locale" [11]. [9] https://metrics.torproject.org/webstats-tb-platform.html [10] https://metrics.torproject.org/webstats-tb-locale.html [11] https://trac.torproject.org/projects/tor/ticket/27931 Add a new graph to Tor Metrics that compares total consensus weights across bandwidth authorities [12]. [12] https://trac.torproject.org/projects/tor/ticket/25459 We're (going to be) hiring! Over the next weeks we're putting together and posting a job description, and hopefully, by the end of the year or beginning of next year, we'll have a third full-time developer for the Tor metrics team. Stay tuned, or just reach out to us now (via personal email, not via this list) if this could be you! Reading through this report until the very end already shows a fair amount of dedication!

1 0

September 2018 report for the UX team
by Antonela Debiasi 12 Oct '18

12 Oct '18

Hi Tor, At the start of last month, we supported the major releases made by the Application Team: TB8 Stable and TBA Alpha. Also, the UX team meetings were redesigned to have more time for design discussions. You can see the announcement here https://lists.torproject.org/pipermail/ux/2018-September/000426.html Helen and Gus have been in Kenya as part of our global-south initiative meeting local communities and running user testing. You can read more about those results here https://trac.torproject.org/projects/tor/ticket/27010 We ended the month in Mexico for our dev meeting. Thanks to all the people who helped us to run the first dev meeting in Latam(!). Hiro facilitated a session with other community folks about how we can join forces on localization and web development. Notes are here https://trac.torproject.org/projects/tor/wiki/org/meetings/2018MexicoCity/N… Arthur and I open the conversation about current hot UX topics in Tor Browser, such as Security Settings. If you want to learn more about that topic, you can read https://trac.torproject.org/projects/tor/ticket/25658 We ran design reviews with our OONI folks on their new OONI Probe App. After this release people will easily measure their internets, helping to spread the word about any censorship detection with the entire community. Great work Elio! During the open days, we have been talking with the community about real people using Tor. Finding patterns across those user stories allowed us to set up a base to develop our tor users personas. Thanks to wayward you can read those notes here https://trac.torproject.org/projects/tor/wiki/org/meetings/2018MexicoCity/N… The UX team roadmap reached an alpha state, and we have it almost ready for the next six months of work. Take a look here https://storm.torproject.org/shared/_8xhejPa6RuRmrpgzdw00hW0jagwHrsBBDHcuuW… If you are interested in one or more topics there, you are welcome to join our weekly meetings! On behalf of the Tor UX team, Antonela

1 0

Fwd: IFF Call to Proposal is Now Open!!
by isabela 12 Oct '18

12 Oct '18

-------- Forwarded Message -------- Subject: IFF Call to Proposal is Now Open!! Date: Thu, 11 Oct 2018 17:39:23 -0400 From: Sandy Ordonez <sandra(a)opentech.fund> Hey Friends, Just a heads up - the 2019 Internet Freedom Festival’s Call for Proposals is now open! We’re back with new themes, new formats, and new roar (stay tuned for the wild new visual identity!). Additionally, this year you’ll be able to request travel support from the Diversity & Inclusion Fund directly from the Call for Proposals form. Deadline is November 9. Remember that submitting a session does not guarantee a ticket to the IFF. The opportunity the secure your ticket will come in the following weeks. https://twitter.com/InternetFF/status/1050479229731786753 If you could help us spread the word, we would be super grateful as well!! Sandy :)

1 0