November 2019 - tor-project - lists.torproject.org

OONI Monthly Report: October 2019
by Maria Xynou 15 Nov '19

15 Nov '19

Hello, In October 2019, the OONI team completed its 1-year contract with the OTF (which started on 1st November 2018). We thank the OTF for its generous support, which has helped the OONI-verse grow and allowed us to build new and exciting tools for the internet freedom community! ## Stable release of OONI Probe Desktop App for Windows and macOS We released the stable version of the OONI Probe desktop app for Windows and macOS: https://github.com/ooni/probe-desktop/releases/tag/v3.0.0-rc.3 From version 3.0.0-rc.2 onwards, auto-update support is enabled and working on macOS and Windows. Users of the older beta versions may have to do a hard reset of OONI Probe from the About screen page. The new OONI Probe desktop app supports running the Websites, Instant Messaging, Performance, and Middlebox tests, as well as configuring the maximum number of tested URLs for the Websites test (which defaults to the full test list). We aim to publicly launch the new OONI Probe desktop app over the next weeks, once we have received more feedback from community members and have done more extensive testing of the app on more platforms. ## Stable release of OONI Probe Command Line Interface (CLI) We released the stable version of the OONI Probe Command Line Interface (CLI): https://github.com/ooni/probe-cli/releases/tag/v3.0.0-rc.3 Prior to this, we also made other releases during October 2019: https://github.com/ooni/probe-cli/releases/ ## Stable release of OONI Probe engine To enable the integration of tests and to otherwise improve OONI Probe sustainability, we have been re-writing the OONI Probe measurement engine (the software that implements OONI Probe nettests) from C++ to golang. The new OONI Probe measurement engine is available via the following repository: https://github.com/ooni/probe-engine During October 2019, we made several releases: https://github.com/ooni/probe-engine/releases The latest release of the OONI Probe engine is stable: https://github.com/ooni/probe-engine/releases/tag/v0.2.0 ## Release of OONI Probe Mobile 2.2.0 We released the 2.2.0 version of the OONI Probe mobile app. Android: https://github.com/ooni/probe-android/releases/tag/v2.2.0 iOS: https://github.com/ooni/probe-ios/releases/tag/v2.2.0 The latest 2.2.0 version: * Uses less storage by automatically deleting old measurements and fetching them from OONI Explorer * Enables users to copy and share OONI Explorer links based on their testing results ## Seamless integration between mobile and desktop apps To have a more seemless integration between the OONI Probe mobile and desktop apps, we integrated react-native (https://facebook.github.io/react-native/) into the probe-android and probe-ios apps. This allows us to maximize code sharing between the OONI Probe desktop and the mobile apps, as well as making it possible for us to use our in-house React expertise for OONI Probe Mobile development as well -- hence reducing the ongoing maintenance effort. We used the About screen as an example to understand the possible limitations to this approach and implemented it as a react-native screen: https://github.com/ooni/probe-react-native/blob/master/views/About.js Some research was done into converting all of the ooni-components part of our design system (https://github.com/ooni/design-system) to react-native and we have understood that we will have to make some changes to how we use the styled-components module. Specifically, we have understood that we will have to refactor our code to use the react-native specific styled-components wrapped when importing modules into the react-native views. We also spent some time researching the performance impact and application size overhead associated with using react-native. See: https://github.com/ooni/probe/issues/868#issuecomment-547720048 Based on all of this research, we have decided to postpone shipping the react-native integration until we have more views implemented and we have assessed the impact that the increased app size will have on our user-base. We do still think this is something we should be doing, as it opens up opportunities for us to start sharing code between desktop and mobile apps for specific components, such as charts and tables. This will also help ensure that the UX and design is more similar and familiar across platforms. Relevant code: https://github.com/ooni/probe-react-native https://github.com/ooni/probe-ios/pull/313 https://github.com/ooni/probe-android/pull/266 https://github.com/ooni/probe/issues/868 ## Made OONI Probe testing more resilient to network outages To make OONI Probe testing more resilient to network outages, we: * used jafar to stress test netx and implemented retransmission of DNS to improve DNS robustness * made the “nervous resolver” fallback to DoH using Cloudflare, which is also a way to increase robustness The automatic fallback to DNS over HTTPS / DNS over TLS has been designed in such a way that it will be triggered (without touching the scoreboard) also in the event that the master DNS fails. This will be useful to improve reliability when the master DNS used by the device is either down or overloaded. We experienced this kind of transient outage both in Cuba and in Italy, during a six-hour incident where Vodafone Italy DNS infrastructure was down. We also ensured that the new Go code has timeout settings in line with the Go standard library and browsers like Firefox, thus further increasing OONI Probe reliability. A detailed explanation of what this work entailed (including relevant code repositories) is available here: https://github.com/ooni/probe-engine/issues/88#issuecomment-548895700 ## Implemented new OONI Probe nettests To improve and expand upon OONI Probe measurement methodologies, we implemented the following new nettests: * Update to the latest ndt7: https://github.com/ooni/probe-engine/issues/70 * DASH rewrite that uses HTTPS: https://github.com/ooni/probe-engine/issues/51 * Telegram re-write using github.com/ooni/netx: https://github.com/ooni/probe-engine/issues/54 We have also integrated automatic follow-up measurements for: * DNS over TLS / DNS over HTTPS fallbacks: https://github.com/ooni/netx/pull/108 * SNI blocking detection: https://github.com/ooni/netx/pull/109 The DNS over TLS / DNS over HTTPS fallback is performed anytime we resolve a domain name and we get a bogon IP (i.e. an IP that should not be public, such as, for example 10.0.0.1 or 127.0.0.1). In such cases, we record into a scoreboard structure that we were served a bogon IP and fallback to DNS over TLS or DNS over HTTPS. SNI blocking detection is performed after a URL measurement; whenever we see a TLS handshake failure that leads us to think that there may be SNI injection, we run an additional follow-up test with a test helper (example.com:443 in the current experimental code) with the SNI we suspect being blocked and we also record the result into the scoreboard. This design for follow-up experiments is also based on conversations with Vinicius Fortuna (Jigsaw) regarding how to improve the OONI testing methodology. This work intersects with the "Improve basic on device data analysis" work. We chose a design where these new nettests are follow-ups, because this enables us to collect richer measurements without the need to prompt users to manually run follow-ups. The above work was tracked through this master ticket: https://github.com/ooni/probe-engine/issues/86 We implemented these new nettests in probe-engine and we plan to ship them as part of the OONI Probe apps over the next months. ## Ingested new metadata produced by new set of tests Previously, the OONI data processing pipeline only ingested metadata from OONI's Web Connectivity test. We have now added support for ingesting and analyzing the metadata produced by most OONI Probe tests: * Facebook Messenger test * Telegram test * WhatsApp test * HTTP header field manipulation test (for middlebox detection) * Vanilla Tor connectivity test * TCP connect test * DASH test * Meek test We have also implemented basic handling (without scoring) of the following OONI Probe tests: * Psiphon test * NDT test This work was implemented as part of the fast-path pipeline in the following pull request: https://github.com/ooni/pipeline/pull/242 ## Improved basic on-device data analysis To improve basic on-device data analysis (as mentioned above in "Implementing new OONI probe nettests") we added support for the following: * OONI Probe can detect bogus DNS replies and fallback to DNS over HTTPS / DNS over TLS * OONI Probe flags the event where the TLS handshake failed with connection reset and runs follow-up tests to determine whether it's a case of SNI-based filtering This work was tracked through the following ticket: https://github.com/ooni/probe-engine/issues/87 We also built Jafar (https://github.com/ooni/jafar ) -- a tool that simulates a censored environment -- to ensure that our methods work as expected. ## Reduced the latency of publication of uploaded measurements to less than daily To analyze and publish OONI measurements from around the world faster, we built a fast-path pipeline: https://github.com/ooni/pipeline/pull/213 To reduce the latency of publication of uploaded measurements to less than daily, we implemented fast-path support in the OONI API. This work is available through the following pull request: https://github.com/ooni/api/pull/115 The database tables for the fast-path (which publish measurements daily) are already getting populated and published. The OONI API related changes (which will expose the most recent measurements in OONI Explorer) are going to be shipped in production sometime next week, as we are trying to avoid deploying too many services at once. ## Added data processing pipeline heuristics for flagging relevant blocking events for the RSS feed To flag relevant blocking events and expose them via the RSS feed, we added data processing pipeline heuristics to the fast-path pipeline and ingested the metadata of most OONI Probe tests. Our work on adding an event detector and RSS feed generation to the fast-path pipeline is available via the following pull request: https://github.com/ooni/pipeline/pull/228 Based on this, we have an internal web app that generates charts based on blocking events. The event detector is currently running. ## Exposed blocking events in RSS feed hosted on OONI Explorer Based on the event detector that we added to the fast-path pipeline (https://github.com/ooni/pipeline/pull/228) we created an RSS feed for exposing blocking events on OONI Explorer. OONI Explorer now provides links to RSS feeds on events detected by the fast-path pipeline event detector. The following feeds are to be made available on OONI Explorer: * Global feed (added to all pages) * Country-specific feed (added to relevant country pages) So far, we have deployed the global RSS feed which shows events on a global scale and is available here: https://explorer.ooni.org/rss/global.xml Soon thereafter, we are going to be adding the country-specific feed on the OONI Explorer country pages. This work was implemented through the following pull request: https://github.com/ooni/explorer/pull/342 For the time being, we are not going to be promoting the RSS feed feature of OONI Explorer extensively as we need to use it more ourselves and get feedback from trusted community members to avoid mis-interpretation of the data. ## Ensured all our infrastructure is re-deployable We worked on ensuring that all our infrastructure is re-deployable, making it possible for us to recover from a disaster (a machine being terminated) with minimal amount of downtime and be able to migrate to up-to-date versions of Operating Systems to keep our infrastructure secure. All of our work on ensuring that our infrastructure is re-deployable was completed in October 2019 and tracked via this ticket: https://github.com/ooni/sysadmin/issues/356 As part of this work, we also coordinated with Greenhost to ensure the redeployed hosts are using the eclips.is platform in the most resource-conscious way possible. For example, several unnecessary hosts have been terminated and some that did not require to be located in Hong Kong or Amsterdam have been migrated to the Miami location which has more availability of resources. ## Improved the availability of our infrastructure We improved the availability of our infrastructure via the "oonification of probe services". The oonified bouncer, collector and orchestra backend are deployed and serving clients. The pipeline is using the new collector and we rolled-over all the collectors to the new probe-services oonified host. Our work on oonifying the probe services is available via this pull request: https://github.com/ooni/sysadmin/pull/361 All of our work on improving the availability of our infrastructure was tracked through the following ticket: https://github.com/ooni/sysadmin/issues/359 ## Published report on the blocking of abortion rights websites In collaboration with Coding Rights (Brazilian partner) and Women on Waves / Women on Web, we published a report that examines the blocking of abortion rights websites womenonwaves.org and womenonweb.org around the world. The report is available on the following sites: * OONI: https://ooni.org/post/2019-blocking-abortion-rights-websites-women-on-waves… * Coding Rights: https://medium.com/codingrights/on-the-blocking-of-pro-choice-websites-wome… VPNCompare wrote an article about our report: https://www.vpncompare.co.uk/block-abortion-websites/ In this report, we share OONI data confirming the blocking of womenonwaves.org in Brazil, as well as in Iran and Turkey. We also share OONI data on the blocking of womeononweb.org in South Korea, Turkey, and Saudi Arabia. We corroborated OONI findings by looking at Censored Planet data (https://censoredplanet.org/) as well, shared in the report. ## Created community resources To strengthen existing partnerships and better support OONI community engagement efforts, we created several new resources, listed below. ### Created OONI Frequently Asked Questions (FAQ) section To better support the OONI community, we created a Frequently Asked Questions (FAQ) section: https://github.com/TheTorProject/ooni-web/pull/301 The OONI FAQ can also be viewed here: https://deploy-preview-301--ooni.netlify.com/about/faq/ The new OONI FAQ includes answers to 67 questions that fall under the following themes: * About OONI * OONI Probe * Testing websites * OONI data * OONI Explorer We included the questions that we have most frequently been asked over the last years, as well as questions that have been raised by community members during meetings, hackathons, workshops, usability studies, and during other community interactions. The new FAQ (along with all other content on the OONI website) is published on github, and we welcome feedback and community contributions. We aim to publish the FAQ on the OONI website and promote it over the next few weeks. As OONI tools and methodologies evolve, we will continue to update the FAQ on an ongoing basis. ### Created OONI Glossary To empower broader community participation in censorship measurement research, we created a glossary which explains the terms used in the OONI apps, methodologies, and research reports. The new OONI Glossary is available on github (and we encourage review, feedback, and community contributions): https://github.com/TheTorProject/ooni-web/pull/298 The glossary can also be viewed here: https://deploy-preview-298--ooni.netlify.com/about/glossary/ We aim to publish the glossary on the OONI website over the next few weeks and we will promote it through our partner networks. ### Published OONI workshop slides To enable our partners and the broader community to teach OONI Probe and engage their local communities with censorship measurement research and advocacy, we created and published OONI workshop slides: https://docs.google.com/presentation/d/1UAxGeF1NhCXc8pT7cfWTp0NPdkWB5LInBkG… These workshop slides cover the basics with regards to: * OONI Probe test methodologies * Running OONI Probe * Potential risks associated with running OONI Probe * How to reduce potential risk associated with running OONI Probe * Contributing to test lists * Customized website testing * OONI Run: Coordinating custom OONI Probe testing * Using OONI Explorer * OONI API * Interpreting OONI data * Using OONI data * How to get involved with the OONI community We have published these OONI workshop slides on Google Slides so that community members can: * download the slides in the format of their choice * edit and customize the slides (so that they're more relevant to their local context and to the needs of the communities they teach) Our edits to the OONI website to accommodate the publication of the OONI workshop slides are available here: https://github.com/TheTorProject/ooni-web/pull/302 The OONI workshop slides can be found through the Get Involved section of the OONI website: https://ooni.org/get-involved/ ### Published document for OONI Probe community engagement Our partners have expressed the need for a document that they can share to introduce new people to the use of OONI Probe. To this end, we created a PDF document that summarizes key information for getting started with running OONI Probe and engaging your community with censorship measurement research: https://ooni.org/documents/Getting%20started%20with%20OONI%20Probe.pdf Specifically, this document covers: * About OONI Probe * Running OONI Probe * Testing websites * Testing specific websites of your choice * Testing a custom list of websites The above information is shared through instructions, synthesized information, and links for further reading. Our edits to the OONI website to accommodate the publication of this document are available here: https://github.com/TheTorProject/ooni-web/pull/302/commits/6f61b9e9b672443e… This document can be found through the Get Involved section of the OONI website: https://ooni.org/get-involved/ ### Updated OONI Run button page Often when censorship events emerge (leading up to or during political events, such as protests or elections), social media, news media, and VPN sites are commonly blocked. To enable the testing of specific types of websites and to support rapid response to emergent censorship events, we set up a page which includes OONI testing buttons: https://ooni.org/get-involved/run/ These buttons enable the OONI Probe testing of: * Social media websites * News media websites * VPN sites * Wikipedia sites * Human rights sites * Environmental sites * LGBTQI sites Rather than having to identify which social media websites (for example) to test during an urgent censorship event, the OONI community can refer to the buttons on this page for targeted testing. Apart from supporting efforts related to rapid response, these OONI Run buttons can also support research and advocacy efforts related to the customized testing of the above categories of sites over time. ## Community use of OONI data ### Investigating the blocking of sci-hub and libgen in France Community members hosted an OONI workshop in France to engage locals with the use of OONI Probe in order to test the blocking of sci-hub and libgen across different networks. They shared their OONI Probe methodologies and findings through a series of tweets: https://twitter.com/tenacioustek/status/1183715300283502592 They also shared the script they wrote to query results directly from the OONI API: https://github.com/Te-k/analyst-scripts/blob/master/ooni/get_ooni_website_s… ## Community activities ### HacktoberFest 2019 OONI participated in HacktoberFest (https://hacktoberfest.digitalocean.com/) https://twitter.com/OpenObservatory/status/1179033711557263361 The OONI github issues that were part of HacktoberFest are available here: https://github.com/search?q=org%3Aooni+label%3Ahacktoberfest We received valuable contributions from HacktoberFest participants! Across projects, we received 6 pull requests. Notably, the newly launched OONI Explorer received 4 pull requests, one of which was a major refactoring exercise: https://github.com/ooni/explorer/pull/336 ### OONI workshop in Taiwan Our Taiwanese partners, the Open Culture Foundation (OCF), hosted an OONI workshop in Taipei on 17th October 2019. Information about their workshop is available here: https://ocftw.kktix.cc/events/iffcc201910 ### Manual for OONI Probe rapid response in Chile Our Chilean partners, Derechos Digitales, created and published a manual (in Spanish) which explains how to use OONI Probe: https://www.derechosdigitales.org/13931/manual-rapido-de-ooni-probe-para-mo… The use of OONI Probe was heavily promoted by Derechos Digitales during the protests in Chile: https://twitter.com/derechosdigital/status/1187101399001260032 ### Blog post about OONI Probe The Civilsphere Project (dedicated to supporting NGOs, journalists, and human rights defenders) published a blog post (also in Spanish) where they explain OONI and how to use OONI Probe (likely in response to the protests in Chile): https://www.civilsphereproject.org/blog/2019/10/22/que-es-ooni-y-como-usarlo In their blog post, Civilsphere discuss why it's important to measure internet censorship, what OONI Probe can measure, how to run OONI Probe (and associated potential risks), how to configure OONI Probe settings, and how to find OONI data. ## Press coverage CNET published an article about OONI (titled: "These watchdogs track secret online censorship across the globe"): https://www.cnet.com/features/the-watchdogs-tracking-secret-online-censorsh… OONI Probe was also listed as a tool to fight authoritarianism in the following article: https://toolsandnotions.comprehensophy.org/technologies-that-counter-author… ## Userbase In October 2019, OONI Probe was run 485,623 times from 5,561 different vantage points in 214 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

Notes from Vegas Meeting NOVEMBER 14 2019
by Erin Wyatt 15 Nov '19

15 Nov '19

Vegas Team Meeting Notes NOVEMBER 14 2019 NEW BUSINESS - The network team uses "network-team" as a way to highlight us all on IRC. Do other teams have official things like that? Do they want one? [nickm] * Resolution: every team should pick up a string like this and set it up to highlight for themselves. Any team that doesn't want to, doesn't have to. Let people know what string you've picked; The Tor Browser team has "tbb-team”. - Announcement in case any of you want to apply or you want to bring it to the teams. From MOSS program managers: "Finally, a friend and colleague of MOSS, Kara de la Marck, is launching a peer mentorship program for open source maintainers in early 2020. It will be a six-week program that covers topics like sustainability, governance and diversity and inclusion. To learn more about the program or to sign up to become a participant or mentor, please visit https://posse.community." [gaba] - Getting started on the new email service project, review the "Goals" section here: https://help.torproject.org/tsa/howto/submission/ [anarcat] * Discussion: friendly reminder that vegas team ppl agreed to help with documentation and support for email service; need someone to help design a handbook to answer the "so how do i configure my email client to use that thing anyways?”; anarcat will put help needed on a pad when he’s ready; people who are losing their tor project email should file trac tickets. - How are we coordinating the invitation process to our dev meeting for, say, tor core members and external stakeholders (if we wanted to save money we should get to it as fast as possible) [GeKo] * Answer: we will start this process when Isa gets back; we will also discuss if/how many open days we’ll have. GENERAL NOTES + Philipp • Philipp and Roger attended OTF summit in Taiwan • Cecylia and Roger attended RACE PI meeting in San Jose • Reached out to more people for private obfs4 bridge distribution • GetTor, BridgeDB, and Snowflake maintenance + Gaba • Starting S31 report • Nextcloud migration • Roadmaps • Trac up to date • Grants proposals • Will give a talk at SeaGL tomorrow. + Nick • The network team uses "network-team" as a way to highlight us all on IRC. Do other teams have official things like that? Do they want one? • New RC coming out in next few days; stable backport releases aimed for early December when we are less hosed. • Wrapping up sponsor 31. Lots to do there. + Sarah • Campaign continues to do well. We've raised $20K more than we raised last year at this point, even though we started the campaign 5 days earlier in 2018. + Steph • EOY Campaign, running promotions, wrote a blog post on surveillance • Rating outreachy applicants and making a decision. We had 16 applicants for the communications spot. • Talking to Alison about LFI comms plans • Will be applying for the OTF Learning Lab -- will talk over at grants meeting next week + Anarcat • getting started on the new email service project, review the "Goals" section here: https://help.torproject.org/tsa/howto/submission/ [anarcat] • new caching service tweaks, now 88% hit ratio, will hopefully go down to 300$/mth costs in november! shiny graphs at https://grafana.torproject.org/d/p21-cvJWk/cache-health • dealt with an unusual amount of email • cymru might get unstuck, stay tuned • updated my harvest timesheets, i had forgotten for two months (!) • held a sysadmin meeting last month which has my last month/next month tasks https://help.torproject.org/tsa/meeting/2019-11-04/ + Alex: • Went to Freedom not Fear together with Gus. Met a lot of European internet activists and learned a bit there. • Catching up on my backlog with all the CVs for the Shadow Developer hire. • Network team retrospective went well. The team seems to be doing well. • Starting to think a bit about our roadmapping in December. + Gus • Went to Freedom not Fear with Alex. We joined three Tor activities (Tor Meetup, Onion Services and Censorship circumvention). I suggest to our european friends to add this event to their annual agenda. • Organizing Tor activities with our italian friends: • https://blog.torproject.org/events/tor-workshop-strike-spa-roma • https://blog.torproject.org/events/non-e-la-silicon-valley-ma-si-mangia-meg… • Reviewing Outreachies final application. • Finish to update Tor training slides with the latest TB release and sending to our training partners in Global South. • Doing other communities things • Syncing with Pili about Sponsor9 phase 2 report. + Pili • S9 Phase 2 report • S44 report • Doing a bit of trac triaging for browser team • S27 meeting • Tor Browser release meeting + Erin • Shadow dev screening • Misc. HR/org ops stuff • Gaba coming to Seattle! We plan to livestream her State of the Onion talk at SeaGL on Instagram. Kinda late for most people - 16:15 PDT (00:15 UTC), but hopefully we can save/share the vid. + Karsten • Put out several releases as part of extending CollecTor's index.json to contain descriptor types and publication times as well as SHA-256 file digests. • Rewrote exit scanner part that does the scanning without writing properly formatted exit lists in Python.

1 0

Anti-censorship meeting notes, 14 Nov 2019
by Philipp Winter 15 Nov '19

15 Nov '19

Here is our meeting log: http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-11-14-18.00.html And here is our meeting pad: Anti-censorship work meeting pad -------------------------------- Next meeting: Thursday November 14th 18:00 UTC Weekly meetings, every Thursday at 18:00 UTC, in #tor-meeting at OFTC (channel is logged while meetings are in progress). == Goal of this meeting == Weekly checkin about the status of anti-censorship work at Tor. Coordinate collaboration between people/teams on anti-censorship at Tor. == Links to Useful documents == * Our anti-censorship roadmap: https://dip.torproject.org/torproject/anti-censorship/roadmap/boards * Our roadmap consists of a subset of trac tickets. * The anti-censorship team's wiki page: https://trac.torproject.org/projects/tor/wiki/org/teams/AntiCensorshipTeam * GetTor's roadmap: https://dip.torproject.org/groups/torproject/anti-censorship/gettor-project… * Tickets that need reviews: https://trac.torproject.org/projects/tor/query?status=needs_review&componen… * Projects from sponsors we are working on: * https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor30 * https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor28 --------------------------- --- 14th November 2019 --- --------------------------- == Announcements == * Remember we are moving to https://nc.torproject.net for nextcloud. If you have anything else in nc.riseup.net or storm.torproject.org please move it == Discussion == * Gettor update * Survival guide here: https://dip.torproject.org/torproject/anti-censorship/gettor-project/gettor… * Let's agree on an IRC "team handle" that we configure highlights for. This will allow both team-internal and team-external people to reach our team. * There already is "network-team" and "tb-team" * "ac-team" and "anti-censorship-team" * Kicked out old snowflake proxies with #29207 update * It will take a while for metrics to come in, but it looks like we still have plenty. * Cupcake hadn't been updated at all since the original import of Snowflake * dcf is ready to migrate the Snowflake broker to the IPv6 host (#29258). He can update the snowflake-broker.bamsoftware.com address from which snowflake-broker.freehaven.net will follow. Tor Metrics should automatically start following the new broker after that. * Just want to be sure people are around to react in case something goes wrong. * I'd like to copy over the metrics log, but otherwise i'm ready --cohosh * Sponsor 30: we are skipping the November meeting as Hellais and Phw already met during summit. Work Plan for November: https://nc.torproject.net/s/7MYXRmTgirqKKyk * Create an evaluation framework for bridge distribution and selection methods. (anti-censorship team) #31274 * Improve documentation on how to set up a bridge server and different pluggable transport bridge servers. (anti-censorship team) #31280 * Create scripts and configuration code for setting up a bridge on cloud providers to make it easier for operators to launch a new bridge. (anti-censorship team) #31281 * Any update to the roadmap? https://dip.torproject.org/torproject/anti-censorship/roadmap/-/boards == Actions == * Please add your October'19 highlights to our (very late) monthly report: https://pad.riseup.net/p/Z7EjorhnnuNLVnA7Tdda == Interesting links == * Geneva: Evolving Censorship Evasion Strategies: https://censorbib.nymity.ch/pdf/Bock2019a.pdf * They're using genetic algorithms to derive evasion strategies == Updates == FORMAT! Name: This week: - What you worked on this week. Next week: - What you are planning to work on next week (related to anti-censorship work). Help with: - Something you may need help with. Hiro: Started restoring Twitter Responder. When retrieving tweets I need to check for new tweets only otherwise Gettor will end up responding to old back log and already answered messages. <-- is this #27330 ? Next Week: - Work on gettor specs <-- Is this #3781? - More with review of strings and website content and translation phw: This week (2019-11-14): * Attended OTF summit. * Had a chat with Arturo about sponsor 30 * Talked to people about private obfs4 bridge distribution * Lots of censorship-related information sharing * Thought about information sharing list for projects that ship obfs4. * Attended OTF advisory council meeting. * Filed #32276 to help BridgeDB see client IP addresses of moat requests. * Merged two new obfs4 bridge setup guides (thanks to egypcio). * Revised and merged #32203 (no BridgeDB metrics for vanilla bridges); released BridgeDB v0.9.1. * Updated BridgeDB dependencies because of security issue in pillow. * More root cause analysis of #15404 (BridgeDB's email responses aren't localised). * Closed #19839 (untranslated title strings in BridgeDB) because we seem to have fixed it already. * Reviewed #31310 and #29207. * Made progress on #31834 (improve Docker container). * Reviewed status-check script for BridgeDB (will help test our email autoresponder). Next week: * Help with: * Gaba: (updated October 30th) Last week (): * sponsor 30 This week (planned): * more sponsors ahf Last week: - Worked on #28930 This week: - Finished refactoring parts of #28930. Trying to figure out if we should begin the discussion on how PT's can report back on bootstrap info. - Continued to work on a tool to convert Trac tickets into Gitlab tickets. cecylia (cohosh): last updated 2019-11-14 Last week: - reviewed #31028 (websocket library change) - ran some tests for #31971 (windows slowness) and couldn't reproduce it - finished proxy-go tests (#30867) - sponsor 28 PI meeting (travelled to California) - reviewed gettor survival guide - took a look at #32393 (gettor github links broken) and filed #32457 (to get access to gettor machine) - review of gettor PR - did a review of work so far on #31874 - deployed 29207 and #30867 at the broker, proxy-go instances, and for web extensions - started looking at github API for gettor releases (#32480) This week: - continue on writing snowflake tests (#29259) - more work on #29206 and #25723 - more grant writing - have proxies report what kind they are to broker #31157 (related to #29207) - gettor code reviews - add more STUN servers to snowflake (#30579) - come up with a concrete way to measure snowflake network health catalyst: week of 09/19 (planned): - reviews - sponsor31 planning - coding style discussion - comment on draft network team review guidelines - #30984 week of 09/19 (actual): - reviews - sponsor31 planning - talking with people about proposed network team review processes week of 09/26 (planned): - reviews - sponsor31 doc coordination - checking in on Season of Docs work - #30984 arlolra: 2019-11-14 Last week: - finished off / merged #31028 Next week: - add a build step / documentation for code reuse in cupcake - read up on turbo tunnel Help with: - dcf: 2019-11-14 Last week: - reviewed Gorilla WebSocket patch (#31028) - reviewed proxy-go tests (#30867) Next week: - switch to new IPv6 broker (#29258) - prototyping KCP and QUIC in meek - revise ticket about Cupcake patch (#31497) Help with: - need meek-azure to redeploy meek-server for #31890

1 0

Metrics Meeting Notes, November 12th 2019 [includes last week releases]
by Gaba 12 Nov '19

12 Nov '19

Next meeting: *Thursday*, November 21st , 15 UTC Hi! We had our meeting on Tuesday November 12th (it had to be rescheduled this week). New pad for the meeting: https://nc.torproject.net/s/4zQKoype2wbB3tx Meeting Log: http://meetbot.debian.net/tor-meeting2/2019/tor-meeting2.2019-11-12-15.01.l… Agenda and Notes: Nextcloud migration (karsten) gaba creates a new pad on nc.torproject.net and copies all content from here there, then tells us how to find it Onionoo upgrade to 7.0-1.21.1 (karsten) Exit scanner (irl) Irl rewrote the exit scanner (just the scanner portion) in python. It will be ready for review this week. Roadmap - how are we doing? (gaba) https://trello.com/b/Mu5fYg53/tor-metrics-roadmap Releases last week: #32353: Release metrics-lib 2.9.0 #32441: Release CollecTor 1.13.0 #32442: Release metrics-lib 2.9.1 #32443: Release Onionoo 7.0-1.21.1 #32444: Release ExoneraTor 4.2.0 #32445: Release metrics-web 1.3.0 #32452: Release CollecTor 1.13.1 cheers, gaba -- Project Manager: Network, Anti-Censorship and Metrics teams gaba at torproject.org she/her are my pronouns GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19

1 0

Tails report for October 2019
by sajolida 12 Nov '19

12 Nov '19

Releases ======== * Tails 4.0 was released on October 22 (major release). https://tails.boum.org/news/version_4.0/ * Tails 4.1 is scheduled for December 3. The following changes were introduced in Tails 4.0: - Replace *KeePassX* with *KeePassXC*, which is more actively developed. - Remove *Scribus*. - Usability improvements to *Tails Greeter* - Tails 4.0 starts 20% faster. - Tails 4.0 requires about 250 MB less of RAM. - Tails 4.0 is 47 MB smaller to download than Tails 3.16, despite all these changes. - Add support for *Thunderbolt* devices. - ... and a lot more! Code ==== * We finished integrating _Tor Browser_ 9.0 into Tails. (#16356). * Rafael Bonifaz from the Centro de Autonomía Digital published some scripts to run a Mumble server and Mumble clients from Tails. https://autonomia.digital/es/tails/mumble/anonymity/2019/10/09/tails-mumble… Documentation and website ========================= - We improved our documentation on verifying Tails using OpenPGP. (#16175 and #15697) https://tails.boum.org/install/download#openpgp - We improved a lot our manual upgrade documentation, which all users have to follow to upgrade to Tails 4.0: - We merged /upgrade and /doc/upgrade. - We wrote full scenarios to do manual upgrades from: - Windows: https://tails.boum.org/upgrade/win-overview/ - macOS: https://tails.boum.org/upgrade/mac-overview/ - Linux: https://tails.boum.org/upgrade/linux-overview/ Hot topics on our help desk =========================== 1. A lot of people reported having issues installing Tails with Etcher on MacOS. (#17185) 1. We got also numerous reports from people having trouble to import PGP keys with Seahorse. (#17183) 1. And some users are facing a graphic issue on computers with two GPU caused by MAC spoofing running udevadm trigger. (#17199) Infrastructure ============== * We have published the technical design documentation that describes the setup of our translation platform. https://tails.boum.org/contribute/design/translation_platform/ * We upgraded the SMTP relay behind _WhisperBack_ to a v3 Onion service. * We made progress towards upgrading _Chutney_ for our test sui. (#16792) Funding ======= - We launched our end-of-year donation campaign: - We blogged about why supporting Tails is more important than ever and our achievements in 2019. https://tails.boum.org/news/2019-fundraiser/ https://tails.boum.org/news/achievements_in_2019/ - We received a very generous anonymous donation of 300 Moneros (around 15 000€)! Outreach ======== Past events ----------- * Tails was presented in Thessaloniki during 2 days for radical technologies: https://anopoli.espivblogs.net/2019/10/03/2-days-for-radical-technologies/ * intrigeri attended the Mozilla Festival on October 26-27 in London (UK). We held a booth there, talked with lots of people including a number of Tails users, and ran a "Discover Tails and translate it into your own language" session. https://www.mozillafestival.org/ * There were a Tails workshop and a talk about the last 10 years of Tails at the privacyweek in Vienna. https://privacyweek.at/ On-going discussions ==================== * We've started discussing how we will adapt to the fact Firefox will now be released every 4 weeks. Press and testimonials ====================== * 2019-10-24: ris announced the release of Tails 4.0 in Linux Weekly News. https://lwn.net/Articles/802876/ * 2019-10-23: heise.de published a review of Tails 4.0. https://www.heise.de/security/meldung/Tails-4-0-mit-neuem-Linux-und-aktuals… Translations ============ * We have issued a call for translations. https://tails.boum.org/news/call-for-translations/ * We have published a documentation for translators who want to use our new web based translation platform. https://tails.boum.org/contribute/how/translate/with_translation_platform/ ## All the website - fr: 89% (5318) strings translated, 2% strings fuzzy - es: 51% (3067) strings translated, 5% strings fuzzy - de: 35% (2128) strings translated, 11% strings fuzzy - it: 31% (1837) strings translated, 8% strings fuzzy - fa: 28% (1694) strings translated, 11% strings fuzzy - pt: 23% (1364) strings translated, 9% strings fuzzy ## Core pages of the website - fr: 93% (1667) strings translated, 4% strings fuzzy - es: 85% (1523) strings translated, 6% strings fuzzy - de: 64% (1139) strings translated, 16% strings fuzzy - it: 60% (1071) strings translated, 18% strings fuzzy - pt: 44% (793) strings translated, 14% strings fuzzy - fa: 33% (598) strings translated, 14% strings fuzzy Metrics ======= * Tails has been started more than 794 831 times this month. This makes 25 640 boots a day on average. -- sajolida Tails — https://tails.boum.org/ UX · Fundraising · Technical Writing

1 0

No Community Team meeting today - 11th November 2019
by Pili Guerra 11 Nov '19

11 Nov '19

Hi everyone, There’ll be no community team meeting today. Thanks! Pili — Project Manager: Tor Browser, UX and Community teams pili at torproject dot org gpg 3E7F A89E 2459 B6CC A62F 56B8 C6CB 772E F096 9C45

1 0

Tor Browser Release meeting: Wednesday 13th November @ 19UTC
by Pili Guerra 11 Nov '19

11 Nov '19

Hi everyone, Please join us for the Tor Browser release meeting this week. We’ve shifted the time to 19UTC now that the clocks have changed everywhere (that I’m aware of) to keep the usual time for everyone. Thanks! Pili — Project Manager: Tor Browser, UX and Community teams pili at torproject dot org gpg 3E7F A89E 2459 B6CC A62F 56B8 C6CB 772E F096 9C45

1 0

S27: Onion Services meeting this week - Tuesday @ 15UTC
by Pili Guerra 11 Nov '19

11 Nov '19

Hi everyone, We’re now back on our fortnightly schedule for these meetings so here’s your usual reminder about this happening this week. I look forward to hearing your progress and any discussions on the work ahead. Thanks! Pili — Project Manager: Tor Browser, UX and Community teams pili at torproject dot org gpg 3E7F A89E 2459 B6CC A62F 56B8 C6CB 772E F096 9C45

1 0

Network Team Meeting Notes, 6 November 2019
by Alexander Færøy 08 Nov '19

08 Nov '19

Hello, Here is a short summary of the network team meeting from Wednesday: 1) We started out by looking at the 0.4.2 status page on Trac to see how we are doing there. First RC is coming out next week. Ticket #32103 was postponed to 0.4.3. 2) We went over our Kanban board. 3) We went over our review queue. 4) People were reminded about submitting hours via Harvest 5) We were asked by the vegas team to find a volunteer to help the Git team at Tor. Alex signed up for that. 6) We discussed C coding style for the S31 work with "code cleanup". We decided to do the discussion async on the network-team list to see if we can find a style that most people like. Catalyst will lead this. 7) Gaba announced that she will begin working on the planning for our roadmapping work in December. 8) We discussed ticket #32191 about how to help downstream projects better. 9) We discussed next week and public US holidays. Next meeting is 24h later than usual, so the network-team meeting will happen Tuesday the 12th at 18 UTC instead of Monday. Retrospective will happen Tuesday the 12th at 20 UTC. 10) We discussed if we want to do some updates to our stable releases. We decided to look into that at the end of November/early December when some of our sponsors ends and the 0.4.2 work is "over". 11) We shortly discussed how our metapolicy handles the case where not everybody had voted on a policy and the deadline was reached. 12) We talked about ticket #32399 which seems flaky in CI. 13) Nobody else had anything to discuss :-) --- end of summary --- You can read today's network team meeting log at: http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-11-06-22.59.html Below are the contents of our meeting pad: gaba: (updated on october 30th) Last week (actual): check on sponsors This week (planned): nextcloud migration sponsors grant proposals Help with: teor: (online first week of the month, offline at the usual meeting time) Week of 21 and 28 October (planned): Take Time for: - team policies: - commit bit - backports Roadmap: - Sponsor 31 modularisation: disable relay mode when compiling - Disable major relay and dirauth options, when those modules are disabled - Add tor controller trace logging to diagnose stem hangs (#30901) - continue work Other: - Keep on revising monotime coarse stamp bug fix Week of 21 October (actual): Urgent: - CI issues #32177 - resolved by Travis, mitigated by deleting build jobs Take Time for: - team policies: - commit bit - voting! - backports & backport deciding 0.4.2 bugs: - Made progress on Avoid possible overflow when converting between coarse stamp to approx ms #31482 - (Prioritised Sponsor 31 over some fixes, due to deadlines) Roadmap: - Sponsor 31 modularisation: disable relay mode when compiling - Made progress on Disable major relay and dirauth options, when those modules are disabled #32213 - Merged Sponsor 31: coccinelle tooling and CI checks (#31919) - Reviews and merged for Nick's Sponsor 31 work Other: - Fixes on merge_ready and merged code (#31684, #31762, others) - Bug fixes, ticket triage, and extra reviews - Helping with cross-compiling issues Week of 28 October (actual): Urgent: Take Time for: 0.4.2 bugs: Roadmap: - Sponsor 31 modularisation: disable relay mode when compiling - Reviews and merges for Nick's Sponsor 31 work - Config bug fix #32352 Other: - git-setup-dir.sh improvements #32347 - Bug fixes, ticket triage, and extra reviews - Helping with Android issues Week of 4 November (planned): Take Time for: - team policies: - commit bit - backports Roadmap: - Sponsor 31 modularisation: disable relay mode when compiling - Disable major relay and dirauth options, when those modules are disabled #32213 Other: - If there is time, keep on revising monotime coarse stamp bug fix / stem trace Week of 4 November (actual): Take Time for: - team policies: - commit bit - backports Roadmap: - Sponsor 31 modularisation: - Merged Disable major relay and dirauth options, when those modules are disabled #32213 - Merged associated bug fixes #32368 #32370 #32371 - Fixed more bugs #32410 - Add NSS (and lzma and zstd) support to test_parseconf.sh #32397 - Associated bug fixes - Code reviews and merges Other: - Helping with Android issues - Bug fixes, ticket triage, and quick reviews - Helped out at a local Aaron Swartz Day CryptoBar - gave away some Tor stickers Nick: Week of 28 October (planned): - Event at Wendy's - 042-should TBD - Finish all support code for 29211. - Start revisions on paper with Ian & Chelsea? - Documentation work - Help with relay modularization (31851) - Discuss C style survey results. Week of 28 October (actual): - Event at Wendy's - 042-should TBD - More work and testing for config modularization. - Documentation work: doxygen is looking _much_ nicer. - C style survey results, sent out commentary on responses, and draft formatted code. Week of 4 November (planned): - S31 meeting - Doxygen work, tor-guts work. (#29214) - Write a lot of documentation for #29215 - More #30866 work; try to get it merged - Start revisions on paper with Ian & Chelsea? - Plan for upcoming stable releases. Mike: Week of 10/28 (planned): - Write a circpad doc section on formalization of machine computation and why we chose state machines - Look into circpad bugs asn filed last month that I missed (#30992, #32040, #32140) <-- (gaba: should it makes sense to assign those tickets to you if you are working on them? - #32140 is on asn's plate - you also had #28804) - Look into circpad bugs RIT folks found - Sync with Tobias wrt simulator changes - Maybe write blog post on fingerprinting research paper? Week of 10/28 (actual): - Re-read fingeprinting formalization papers and automata theory (in attemptto formalize/describe state machine strucutres; came up with some intuitions but still struggling on formalization) - Continued work on Tobias's simulator - Struggling to prioritize final circpad items - Attempted to reframe fingeprinting paper blog post; it needs to be focused on mitigations + defenses Week of 11/06 (planned): - Finish cleaning up circpad simulator - Read asn's research feedback - Get DNS recommendations for exit operators for fingerprinting blog post - Update + triage circpad bugs Need help with/at risk of dropping this month: - Deep-thought-required research project followup - (Google masque, BGP, ECN, Rob's bw experiments, Dennis's Mozilla video, etc etc...) catalyst: week of 10/21 (2019-W43) (planned): - reviews - more GSoD stuff week of 10/21 (2019-W43) (actual): - more GSoD stuff - split swati's work into multiple commits for easier reviewing and merging - sponsor31 meeting - created child tickets to #29215 (document new architecture) and assigned some - did extra review of #31919 (coccinelle check-local target and git hooks) week of 10/28 (2019-W44) (planned): - reviews - sponsor31 tickets (children of #29215, etc) - GSoD stuff as neeeded week or 10/28 (2019-W44) (actual): - got more of swati's work merged - more feedback on C style stuff - cleaned up #30984 for early review - sponsor31 architecture doc stuff (#29215) week of 11/04 (2019-W45) (planned): - reviews - more sponsor31 architecture doc stuff (#29215) - maybe finish up #30984 - GSoD stuff as needed help with: - would like extra review on #32399 (test-stem) because i still can't get test-stem to work reliably asn: [Currently in Tim's timezone so not able to attend meeting] Week of 21/10 (planned): - Vacations until Friday Week of 21/10 (actual): - Vacations until Friday - Replied to C style survey - Caught up with emails + ongoing netteam proposals - Replied to a few trac tickets that were pending feedback Week of 28/10 (planned): - Continue catching up with (S27) things that happened the past two weeks. - Continue work on stem encoding of HSv3 descriptors. - Traveling to OTF summit on Thursday. - (Also 28th of October is Greek national holiday, but decided to work so that I start catching up on things. I might take a day off at some point this or next week.) Help with: - David, can you do the little-t-tor side of the S27 October report? This will also help me catch up with your side of things. ahf: Week of 28 October (planned): - Will be talking about Tor at Swiss Web Security Day on the 30/10 and at Driving IT the 1/11. - Expect longer response times from me this week because of traveling. Use email over IRC maybe. - Get #28930 rebased into shape for merging. - If I have time look into our Windows Jenkins problems that Weasel reported on IRC (#32320) Week of 28 October (actually): - Went to the Swiss Web Security Day and Driving IT and talked about Tor. People seemed happy. - Continued to hack on #28930. - Didn't have time to look at #32320 yet. - Look into some WLS issues for Swati. Week of 4 November (planned): - Travel with Gus to Freedom Not Fear in Brussels. - Hack on #28930 and #32320. - Continue to see if we can get the asciidoc situation solved for Swati. dgoulet: Week of 21/10 (actual): - Almost done with #30382. I have to talk to asn about the missing two error codes that are a bit complicated to get. - S27 triage and fixes on: #32094, #31958, #28970 - 3/4 there on implementing cmux tests: #32196. - Help arma/nickm on reviewing and testing #32108. - Reviews and Merges. - Network health needed attention. Week of 28/10 (planned): - Get asn up to date on the latest s27 situation. - Have #32196 in needs_review. - I hope I can finalize #30382 with asn's feedback. - s27 report. - Network health situation is still very active. - Continue my s27 quest on fixing all bugs. <-- (gaba: we need to look into the roadmap after december) - Reviews and merges as usual All the best, Alex. -- Alexander Færøy

1 0

Notes from Vegas Meeting NOVEMBER 7 2019
by Erin Wyatt 08 Nov '19

08 Nov '19

Vegas Team Meeting Notes NOVEMBER 7 2019 + OLD BUSINESS - isabela: Blog temporary resolution - no new information. - isabela: working on trademark faq update - isabela: writing letter to developer who was going to fix css on drupal + NEW BUSINESS - [anarcat,gaba] New nextcloud server is online at https://nc.torproject.net and will replace storm by february, so we should move [shared docs] there (eventually?) * gaba will come up with a draft about information storage and policy for documents in nextcloud and elsewhere... there's already #32273 for SVN that could be expanded * ewyatt will migrate shared pads and AFK calendar ASAP - [Sarah] Need more people to make thank you videos in different languages. We have English, Portuguese, and Spanish. * Maybe we can get it in French next? Any other translators who want to help us? Email sstevenson@. * [Sarah] Need help brainstorming any/all privacy and internet freedom “victories”; deadline for submission November 15th. Email your stories to comms@. * [geko] Should we move to 1700 UTC for the vegas team meeting? - Yes, probably. ewyatt moved the discussion to email. + GENERAL NOTES Gus: 1. Answering the last questions from the Outreachies. The last day to record the contribution was November 5th. We have excellent candidates and until the middle of November to select one of them. 2. Reaching out our Tor community in Firenze and Bologna this week. 3. Traveling this Friday to Freedom Not Fear, and also joining the Tor Meetup in Brussels. 4. Catching up email backlog. 5. Reaching out our training partners in Global South to sync about partnership agreement, training dates and training materials. 6. Still updating our documentation - Tor Browser 9 release. 7. Answering Frontdesk tickets. Some emails about letterboxing, missing windows dlls and Linux/torbrowser-launcher apparmor bug. Georg: 1. Finished release prep for fundraising banner (9.0.1/9.5a2) 2. Work on OTF proposal 3. Caught up on pre 9.0 email backlog 4. Went over remaining browser team lead transition items 5. Started thinking more about future network-health work 6. Should we move to 1700 UTC for the vegas team meeting? Nick: 1. Per usual, not enough time :) 2. 0.4.2 seems to be stabilizing; should be in RC soon. 3. 0.4.3 work in progress; looks neat. Make sure that 4. Have you seen https://src-ref.docs.torproject.org/tor/index.html ? 5. Annotated C style poll results: http://people.torproject.org/~nickm/netteam-survey-results-with-commentary.… antoine: 1. retired three old ARM build boxes that were not powerful enough and "special snowflakes", weasel looking for replacements with linaro 2. helped with: New nextcloud server is online at https://nc.torproject.net and will replace storm by february, so we should move these notes there (eventually?) 3. launched new caching service! we should see cost reductions at pantheon next month and service can be used for other slow services, will convert existing varnish instances eventually Antonela < is in Taipei timezone < I'll try to be awake at 00AM but I'm not sure, anw notes are here :) 1. I've been at the OTF summit 2. I met with Georgia and Eileen from Simply Secure to touch base about the Metrics grants 3. I met with Babatunde, our OTF researcher, to coordinate the next steps on his research. 4. I run a workshop about Participatory Design with OKThanks' Tiffany. 5. We met OTF's Learning Lab manager to talk about the next steps on our Onion Services grant and how we can communicate our future releases with the broad community. We told him that we are going to apply for a formal help and I'll put Steph in contact too. 6. We met Sarah, OTF's Red Team (Security Team) Manager to learn more about large onion services deployments (BBC). 7. We met Fiona to check in about our Onion Services grant. She will ping Pili to have a meeting in December to follow up and coordinate on the status of stuff. 8. Reviewed GR's implementation for the EY Campaign, following the latest changes. Sarah 1. EOY campaign - we are averaging over $1,000 per day more than last year and have 51 new monthly donors (we had 100 people sign up to be monthly donors in the entire 2018 campaign.) 2. Need more people to make thank you videos in different languages. We have English, Portuguese, and Spanish. 3. Need help with privacy victories 4. Prep for postal letter to go out in the next week or two to small foundations and major donors. 5. Sourcing and trying to connect with new foundations. 6. afk periodically, but available the 8-15th. Pili 1. November Roadmapping and general month start gardening 2. Started triaging trac for Tor Browser tickets 3. OTF Proposal 4. S9 Phase 2 report 5. Hope to start S44 report soon... 6. Following up with contacts from MozFest Alex: 1. Working on S28 tasks. 2. Going to "Freedom not Fear" in Brussels from Friday to Monday (both inclusive) together with Gus. 3. Talks in Zurich and Copenhagen last week went well. 4. Gitlab "soft deadlines" for medio November seems to be still plausible. 5. Going to send out Network Team report for October this week. Gaba 1. Nextcloud migration 2. Trac & roadmapping 3. Proposals 4. S31 meetings Erin 1. Personnel stuff 2. General HR/corp admin stuff 3. Shadow dev recruiting

1 0