- tor-project - lists.torproject.org

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

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

12 Oct '18

Notes for October 11 2018 meeting: Georg: 1) Anti-censorship team hiring plan/progress? Alison: 1) I think the meeting was awesome. Gus in particular did an incredible job getting lots of locals involved. I like the method of starting with a Tor training before the meeting. I have some ideas for how things could have gone better but overall I'm happy with it. Going to shoot out an email today or tomorrow for meeting feedback, with a reminder to people to put their notes on the wiki. I will also start a round of thank-yous to some locals, and try to do a debrief with the folks who were at the feminist meetup (which was amazing). Immediate feedback from this group? 2) Thoughts about the next Tor Meeting -- Stockholm doesn't seem to work for many people, other ideas given were Athens or Lisbon closer to our regular meeting time. I was thinking I'd make a survey after the meeting group gets back to me with possible costs etc. 3) Working on a Library Freedom website makeover and rebrand. 4) Finishing up LFI curriculum for the pilot, starting work on the next one. 5) Finishing up the community team roadmap. We have a lot of travel coming up. 6) Next week I'm starting to prep for LFI recruitment, which will begin in December or so. 7) Library Freedom starts the Glass Room Experience in North American libraries next week! Arturo: 1) We have released a beta of the OONI Probe desktop app for Windows and macOS: https://github.com/ooni/probe-desktop/releases/tag/v3.0.0-beta.1 2) We have released a beta of the OONI Probe CLI for macOS, windows and linux: https://github.com/ooni/probe-cli/releases/tag/v3.0.0-beta.1 3) The OONI meeting in Mexico went very well, we now have a tentative roadmap for the next 12 months 4) We have started collaborating closer with the Tor UX team, yay! 5) Working toward the upcoming OONI Probe mobile launch. 6) Updated test lists: https://github.com/citizenlab/test-lists/pull/398 & https://github.com/citizenlab/test-lists/pull/399 7) Submitted September report: https://lists.torproject.org/pipermail/tor-project/2018-October/002006.html Nick: 1) Back to software. Half my team is sick or taking a break, so stuff's a bit slow. 2) Talking at Berkman about decentralization this afternoon. 3) Discussions happening about gettor and who should own it. Sponsor19 timing leaves us in a weird place wrt coordination. Karsten: 1) Started working on 1 new graph and 2 updated graphs as a result of talking to people in Mexico City. 2) About to release CollecTor 1.8.0 with a couple smaller fixes, also in response to missing out server descriptor descriptors over the weekend. Sarah: 1) YE campaign planning. Today will add more ideas to the social media components. 2) Wrote a blog about my first Tor meeting. 3) Getting Al ramped up. 4) Still trying to work out best way to accept cryptocurrency. Roger: 1) Fosdem talk submission 2) Started the sponsor19 list and threads - i wonder if everybody with a task has confirmed seeing the mail? 3) Many anti-censorship dev applications still coming in 4) Should add new Penn funding to sponsors page. Anything else to add? Yes: Handshake. 5) We have another sysadmin interview right after this meeting Steph: 1) working with the berkeley group on our brand study. reviewing their survey and making sure they have relevant info 2) preparing for EOY fundraising campaign. taglines done, reviewing artwork 3) responding to inquiries 4) planning comms strategy for next year, met with Isa to discuss isabela: 1) organizing and having 1:1s with a lot of people (weekly) Gaba, Erin, Steph, Sarah, Pili, Sue 2) synced with all Fundraising/Grants working group (we will have a weekly sync to keep track of all fundraising and grants work) 3) finishing sponsor17 final reports 4) getting onion proposal updated with OTF feedback 5) Vegas team will get bigger soon :) 6) October is the last month of transition - will be in Seattle during the week of Nov 12 where we will finalize it Mike: 1) One of the outcomes of the research.torproject.org meeting was to create a public tor-researchers mailinglist, but with subscribe approval. Is this possible? Who do I ask? [yes it is possible, see https://trac.torproject.org/projects/tor/wiki/doc/emailLists#HowdoIaskforan… -RD]

1 0

September Fundraising Report
by sstevenson＠torproject.org 10 Oct '18

10 Oct '18

I hope everyone who was in Mexico has recovered from the various illnesses that seemed to affect many of us! Here is what was up in Tor Fundraising World in September: Began sketching out the year-end giving campaign that will have the theme, “Strength in Numbers.” The campaign launches October 23rd and will feature a match from Mozilla and additional match opportunities from another donor. Helped get the newsletter banner up in Tor Browser. So far this effort has resulted in significant email list growth. It is currently up to 12,454 names when on 9/6, it had 7,840. Wrote to donors who had not given in several years about Tor Browser 8 and Tor for Android and asked them to consider giving again. Several donated - even up to $1,000 - after not giving since 2015. Sorted through the status of all current grants with the team in Seattle and made a grant roadmap covering the next few months. Researched possible private foundation funding that can be pursued at the beginning of next year. Began working with a consultant to ensure Tor is registered for fundraising in all states. The process is on hold until the 990 is complete. Began updating Tor’s Guidestar profile. Met in person with one of our grant managers. Worked with OONI on a proposal that will now be included as part of a larger anti-censorship proposal that is due in early November. Welcomed Al whose first day at Tor was in Mexico City! I hope you will all help with the year-end campaign by sharing messages on social media and talking with your networks about the amazing work being done at Tor. Sarah Sarah Stevenson Fundraising Director The Tor Project sstevenson(a)torproject.org Public Key: 93B3 AC08 4257 FA3D D4BB 8E95 CC08 5DBA C015 612A

1 0

OONI Monthly Report: September 2018
by Maria Xynou 10 Oct '18

10 Oct '18

Hello Tor world, In September 2018, the OONI team released a beta of the OONI Probe desktop apps for Windows and macOS, established a new partnership with Paraguay's TEDIC and updated a number of test lists. ## Beta of OONI Probe desktop app We have released a beta of the OONI Probe desktop apps for Windows and macOS: https://github.com/ooni/probe-desktop/releases/tag/v3.0.0-beta.1 The aim of this beta release is mostly to sort out stability issues related with shipping measurement-kit and the new OONI Probe CLI on macOS and Linux. We are therefore currently limiting the testing to more tech-savvy users. As the UI of the desktop app has yet to be finalized, the most useful feedback currently pertains to the functionality of the app and any bugs (rather than the UI). That said, the application is feature complete and supports the same functionality shipped as part of the mobile apps. Namely it supports: * Running the websites, instant messagging, middleboxes and performance tests * Viewing the test results for all the above tests * An onboarding wizard with our informed consent procedure * Changing some of the most basic app settings Help in testing the apps is greatly appreciated! If you run into any issues, please report them to bugs(a)openobservatory.org. You should also use the "Hard reset" button in the About of the app before installing the stable version of the app. If you run into any issues, that button may be a viable workaround (note: it will delete all your measurements and settings). ## Established new partnership We are excited to have formally established a new partnership with Paraguay's TEDIC! As part of our new partnership, we aim to collaborate on the study of internet censorship in Paraguay through the collection and analysis of OONI Probe network measurements. Social media announcement: https://twitter.com/OpenObservatory/status/1042760192197373952 ## Updated test lists We carried out research to update the following test lists: 1. Nigeria: https://github.com/citizenlab/test-lists/pull/387 2. Jordan: https://github.com/citizenlab/test-lists/pull/388 3. Argentina: https://github.com/citizenlab/test-lists/pull/390 4. Colombia: https://github.com/citizenlab/test-lists/pull/393 In previous months, we also updated the South Sudan test list: https://github.com/citizenlab/test-lists/pull/366 We also updated the Ugandan and global test lists (https://github.com/citizenlab/test-lists/pull/391) and created new test lists for Cameroon (https://github.com/citizenlab/test-lists/pull/392) and Greece (https://github.com/citizenlab/test-lists/pull/394) ## Community use of OONI data ### Berkman report on Telegram blocking in Iran The Berkman Centre for Internet and Society published a research report examining the blocking of Telegram in Iran: https://thenetmonitor.org/bulletins/censorship-and-collateral-damage-analyz… OONI data on the blocking of Telegram was used as part of this research. ### Digital Security Lab Ukraine reports Through the use of OONI Probe, Digital Security Lab Ukraine has been investigating internet censorship in occupied territories of Ukraine. In September 2018, they published two research reports based on OONI data: 1. Blocking of websites in Crimea (that aren't included in the Russian blocklist): https://medium.com/@cyberlabukraine/crimea-has-a-website-ban-list-additiona… Digital Security Lab Ukraine uncovered the blocking of at least eight Ukrainian websites in Crimea that aren't included in Russia's official blocklist. This research was covered by RosKomSvoboda (a public organization aimed at countering internet censorship): https://roskomsvoboda.org/41726/ 2. Blocking of at least 56 Ukrainian websites in Luhansk: https://medium.com/@cyberlabukraine/at-least-56-ukrainian-websites-are-bloc… Digital Security Lab Ukraine uncovered the blocking of at least 56 Ukrainian websites in Luhansk, many of which include media websites and human rights sites. It's worth noting though that they did not find evidence of internet censorship in Donetsk. ## Community activities ### Community meeting We held a community meeting on Slack (https://slack.openobservatory.org/) on Tuesday, 25th September 2018. As part of our September community meeting, we discussed updating test lists and digging through OONI data. ### OONI presentation at CryptoInstallFest OONI's Leonid gave a presentation in Moscow at CryptoInstallFest on his findings regarding recent internet censorship events in Russia. * Slides: https://slides.ooni.io/2018/CIF * Summary of new findings: https://usher2.club/articles/mt-free-pre-block/ * Information about the event: https://cryptofest.ru/agenda Relevant media coverage: * (en) https://en.crimerussia.com/gromkie-dela/wi-fi-in-moscow-underground-used-fo… * https://www.the-village.ru/village/city/news-city/326087-maxima-vs-telegram * https://www.the-village.ru/village/city/news-city/326091-maxima-vs-telegram… * https://roem.ru/28-09-2018/273997/fil-kulin-opisal-mehanizm-dobavleniya-v-n… * https://tjournal.ru/77024-ekspert-maksimatelekom-pomogaet-roskomnadzoru-blo… ### Tor Meeting & OONI Team Meeting The OONI team traveled to Mexico City to participate in the bi-annual Tor Meeting between 29th September 2018 to 3rd October 2018: https://trac.torproject.org/projects/tor/wiki/org/meetings/2018MexicoCity As part of the invite-only days of the Tor Meeting, OONI facilitated the following sessions: * Censorship Rapid Response: Brainstorming on collaboration between OONI and Tor and determining next steps * Future and next steps for BridgeDB * OONI data format pain management * Tor anti-censorship strategy brainstorming and next steps As part of the public days, we facilitated an OONI session that aimed to introduce locals to OONI Probe and engage them with censorship measurement research. We also had a UX review of the revamped OONI Probe for Android mockups with the Tor UX Team, where we gathered valuable feedback. You can see the mockups here: http://design.ooni.io/mockups/probe-android Following the Tor Meeting, the OONI team hosted its internal team meeting in Mexico City on 4th & 5th October 2018. As part of our 2-day internal meeting, we had the following sessions: * Roadmap for the next 12 months (with more detailed roadmapping for the next 6 months) * Revamping OONI Probe mobile apps: Determining next steps towards stable release * Revamping OONI Explorer: Detailed roadmap & discussion of issues and next steps * OONI Probe desktop apps: Next steps * Brainstorming on new nettests * Probe Orchestration: Next Steps * OONI Partnership Program & community needs * Improving OONI Run & enabling automatic daily testing (until probe orchestration is rolled out) * Measurement-Kit: Future directions * Brainstorming on automating test list methodologies * Fundraising ## Userbase In September 2018, OONI Probe was run 257,139 times from 4,661 different vantage points in 211 countries around the world. This information can also be found through our stats: https://api.ooni.io/stats ~ The OONI team. -- Maria Xynou Research & Partnerships Director Open Observatory of Network Interference (OONI) https://ooni.torproject.org/ PGP Key Fingerprint: 2DC8 AFB6 CA11 B552 1081 FBDE 2131 B3BE 70CA 417E

1 0

Network team meeting notes, 9 Oct 2018
by Nick Mathewson 09 Oct '18

09 Oct '18

Hi, all! We had our meeting today. The logs and decisions are at http://meetbot.debian.net/tor-meeting/2018/tor-meeting.2018-10-09-16.59.html . Below are the contents of our meeting pad... = 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.) 4 Sep: https://lists.torproject.org/pipermail/tor-project/2018-September/001965.ht… 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. == 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 == *ok, 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 ------------------------------- ---- 9 October 2018 ------------------------------- == Announcements == Tor 0.3.2 is now unsupported. https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTor… Tor Calendar: we have a shiny new one for adding time off https://storm.torproject.org/grain/H6dQejgGAizq6MYMawwPzq/ Tor employees, please do timesheets each week, or in the worst case by the end of the month. The new schema (all network team work goes in "Network Team") should make this much faster. == Discussion == * We must assign bug and CI tickets in 0.3.5; they should get fixed ASAP. - nickm * What do we need to do to "finish up" our roadmap? I know it's a living document, but how far are we from something we can work from? -nickm Reminder for this discussion: sponsor 8 issues are priority as it is finishing at the end of the year -gaba There are a few things in the UX roadmap related to network team. Let's check that we have it on our roadmap -gaba (https://storm.torproject.org/grain/2uvMtMh7xKDubdC5np68tN/) * Finish & validate new "minimal rotations" plan from meeting? (Idea was to define minimial versions of each rotation, and possibly drop the ones that don't actually make sense) -nickm Plan and comments: https://pad.riseup.net/p/team_rotation * Reminder: Capacity estimation: adding actual points in the big beautiful spreadsheet from the roadmap -gaba * Proposal to change the meeting only once every 4 weeks to a time that teor can attend. Patch party time? -gaba == 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): - Leave blank for now, since we didn't make plans for last week Week of XYZ (actual): - What you did last week Week of ABC (planned): - What you're planning to do this week. Mike (sick, may not be online during meeting): Week of 10/1 (actual): - OMG so many meetings Week of 10/8 (planned): - OMG so much followup - Create tor-researchers list - Figure out Mozilla all Hands - wtf-pad mails Nick: Week of 10/1 (actual): - Wrap up meeting stuff, take a couple of days mostly-off 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 ahf: Week of 10/1 (actual): - Tor meeting. - Wrote a scraper for Trac in Python, so we might be able to move on with some of the ideas that came up in our CI session! Needs some cleanup though. 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. asn: [will be on a flight back to gr during meeting): Week of 10/1 (actual): - Tor meeting. - Mike I pushed a branch with the WTF code reading we did together `adaptive_padding_comments`. 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. dgoulet: Week of 10/1 (actual): - A bit uneventful. Few tickets reviewed and a little bit of triage. - Followed the meeting as much as I could using the Wiki notes, some IRC insights and emails. 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. gaba: Week of 10/1 (actual) - Tor meeting Week of 10/8 (planned): - roadmap - cleaning on notes - schedule 1 on 1s catalyst (sick, might be offline for actual meeting): week of 10/1 (2018-W40) (actual): - Mexico City and all the meetings 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

1 0

September 2018 report for the Tor Browser team
by Georg Koppen 09 Oct '18

09 Oct '18

Hi! September was the month of the releases for the Tor Browser team. As said in our previous monthly report we got our Tor Browser 8.0[1], Tor Browser 8.5a1[2], and Tor Browser for Android 1.0a1[3] out. However, then we needed to pick up 2 security releases done by Mozilla which resulted in Tor Browser 8.0.1[4], Tor Browser 8.0.2[5], Tor Browser 8.5a2[6], and Tor Browser 8.5a3[7]. Apart from closing security holes in Firefox, with the release of Tor Browser 8.0.1 and 8.5a2 we took the opportunity to fix the most pressing issues encountered during our Tor Browser 8.0 rollout. Those included a crash during start-up on older macOS systems (10.9.x)[8] and a suboptimal solution to our user agent treatment[9]. Remaining issues are still tracked with the `tbb-8.0-issues` keyword.[10] Tor Browser 8.0.2 and 8.5a3 only closed Firefox security holes.[11] This was the first time we needed to do security releases during a dev meeting which was... exciting. Many thanks to boklm who did the heavy-lifting here. Besides working on those releases we nailed down our future plans towards a stable Tor Browser for Android[12], prepared our dev meeting and met face to face in Mexico. The full list of tickets closed by the Tor Browser team in September is accessible using the `TorBrowserTeam201809` keyword in our bug tracker.[13] For October we plan to finish our roadmap for the coming 6 months[14] and try to make solid progress towards our second alpha release for Tor Browser for Android, which is plan in early November. At the end of October another round of desktop releases is planned to pick up the latest batch of Firefox security patches and more fixes for Tor Browser 8 related issues. All tickets on our radar for this month can be seen with the `TorBrowserTeam201810` keyword in our bug tracker.[15] Georg [1] https://blog.torproject.org/new-release-tor-browser-80 [2] https://blog.torproject.org/new-release-tor-browser-85a1 [3] https://blog.torproject.org/new-alpha-release-tor-browser-android [4] https://blog.torproject.org/new-release-tor-browser-801 [5] https://blog.torproject.org/new-release-tor-browser-802 [6] https://blog.torproject.org/new-release-tor-browser-85a2 [7] https://blog.torproject.org/new-release-tor-browser-85a3 [8] https://trac.torproject.org/projects/tor/ticket/27482 [9] https://trac.torproject.org/projects/tor/ticket/26146 [10] https://trac.torproject.org/projects/tor/query?status=accepted&status=assig… [11] https://www.mozilla.org/en-US/security/advisories/mfsa2018-24/ [12] https://lists.torproject.org/pipermail/tbb-dev/2018-September/000910.html [13] https://trac.torproject.org/projects/tor/query?status=closed&keywords=~TorB… [14] https://lists.torproject.org/pipermail/tbb-dev/2018-October/000916.html [15] https://trac.torproject.org/projects/tor/query?status=accepted&status=assig…

1 0