tor-project July 2021

tor-project@lists.torproject.org

11 participants
22 discussions

OONI Monthly Report: May 2021
by Maria Xynou 15 Jul '21

15 Jul '21

Hello, Hope you're all doing well. These days we're primarily supported by the DRL, which is why we do quarterly reporting. That said, we'd like to share monthly updates from the OONI team with the community, hence our May 2021 report shared below. I'll also follow-up to share our June 2021 report. *# OONI Monthly Report: May 2021* Throughout May 2021, the OONI team worked on the following sprints: * Sprint 38 - Umbrella octopus (1-9 May, 2021) * Sprint 39 - Vaquita (10-23 May, 2021) * Sprint 40 - Manatee (24-31 May, 2021) Our work can be tracked through the various OONI GitHub repositories: https://github.com/ooni Highlights are shared in this report below. *## Released OONI Probe Android 3.0.0 with automated testing, backend proxy support, and new experimental card* We released OONI Probe Android 3.0.0 which is a major release because it includes 3 exciting new features: 1) Automated regular testing: By enabling automated testing in the settings, OONI Probe Android will test websites automatically every hour! 2) New Experimental card: Users can now run our new STUN reachability test. 3) Backend proxy support: Users can enable Psiphon or use a custom proxy through the new OONI backend proxy settings. Further information is provided below. *### Automated testing* Following the beta release in April 2021 ( https://github.com/ooni/probe/issues/1451), we made a public release of OONI Probe Android 3.0.0 with support for automated testing: https://github.com/ooni/probe-android/releases/tag/v3.0.0 Instead of having to remember to manually run OONI Probe, users can now have OONI Probe test websites automatically every hour! All they have to do is enable the "Run tests automatically" option in the new "Automated testing" setting of the OONI Probe Android app. Through these settings, users can choose whether they would prefer to have OONI Probe only run tests while they’re connected to WiFi and their phone is charging (to avoid consuming their data and battery). By enabling "automated testing", the OONI Probe Android app will test websites automatically (in the background) every hour, without requiring users to do anything. We started off with only automated website testing, but we plan to add support for automatically running other tests as well in future releases (similarly to automated testing on OONI Probe Desktop: https://ooni.org/support/ooni-probe-desktop#automated-ooni-probe-testing). To avoid over-cluttering the "Test Results" section of the app with too many test results (from automated runs), they are only made available on the OONI API (https://api.ooni.io/) and OONI Explorer ( https://explorer.ooni.org/), where they are openly published in near real-time. We strongly recommend enabling automated testing, as this will help ensure regular testing (which is crucial for detecting censorship events). *### New Experimental card* As censorship becomes more sophisticated, we need to ship new censorship detection tests faster. To this end, we added a new Experimental card in the OONI Probe Android app, where we plan to release our latest experiments. This card is meant to provide us agility in adding and removing new experiments on an ongoing basis (particularly in response to emergent censorship events). With OONI Probe Android 3.0.0, users can run our new STUN reachability test: https://github.com/ooni/spec/blob/master/nettests/ts-025-stun-reachability.… Our work on adding support for running experimental tests is documented through the following pull request and tickets: https://github.com/ooni/probe-android/pull/429, https://github.com/ooni/probe/issues/1388, https://github.com/ooni/probe/issues/1185, https://github.com/ooni/probe/issues/1473. *### Backend proxy support* In some places, such as Iran, communication to the OONI backend services is being interfered with. We have therefore added support for configuring a circumvention proxy for speaking to OONI backend services. OONI Probe Android 3.0.0 includes new backend proxy settings where users can: * Enable Psiphon (https://psiphon.ca/) * Use a custom proxy This will help with circumventing any accidental or deliberate OONI Probe blocking. Our work on this is documented through the following tickets: https://github.com/ooni/probe/issues/1469, https://github.com/ooni/probe/issues/1470, https://github.com/ooni/probe/issues/1477. *## Published a blog post on making OONI Probe Android more resilient* We published a blog post where we describe what we did to make OONI Probe Android more resilient to deliberate or accidental blocking: https://ooni.org/post/making-ooni-probe-android-more-resilient/ As part of this blog post, we explain why we decided to add backend proxy support to OONI Probe, how and why we changed our Android TLS fingerprint, and we document future improvements. *## Improvements to the code quality of OONI Probe Android* In collaboration with Bloco, we improved the way in which the OONI Probe Android app is being tested by adding UI and domain tests, as documented through the following pull requests: https://github.com/ooni/probe-android/pull/431 and https://github.com/ooni/probe-android/pull/437. We also refactored the app to make use of the dependency injection pattern: https://github.com/ooni/probe-android/pull/430 *## Added RTL support to OONI Probe Desktop* We continued to work on adding support for Right-To-Left (RTL) languages (such as Arabic and Farsi) in OONI Probe Desktop. This allows us to integrate translations (provided by the Localization Lab community) in the OONI Probe desktop app. This work is documented through the following ticket: https://github.com/ooni/probe/issues/1087 *## Prototype of browser-based OONI Probe* Community members have been requesting a browser-based version of OONI Probe that they can run. To this end, we started fleshing out a browser-based OONI Probe which allows for testing the accessibility of websites by loading the favicon of the target websites. This work is documented through the following ticket: https://github.com/ooni/ooni.org/issues/854 *## OONI Probe for Raspberry Pis* We added support for creating builds for armv7 and started publishing them on our Debian repository. This allows Raspberry Pi users to install OONI Probe CLI on their Raspberry pi devices. This is documented through the following ticket: https://github.com/ooni/probe/issues/807 *## OONI Probe Command Line Interface (CLI)* We added support to OONI Probe CLI for exposing the is_uploaded status inside of the result listing. This will allow us to expose an icon at the resulting listing level indicating that a measurement has not been uploaded and eventually support re-uploading them. This is documented through the following ticket: https://github.com/ooni/probe/issues/1457 *## Developing a new OONI Probe test for the Snowflake pluggable transport* We made progress on developing a new OONI Probe test for measuring the Snowflake pluggable transport. Specifically, we researched the feasibility of developing such a test and we started fleshing it out in probe-cli, as documented through the following tickets: https://github.com/ooni/probe-engine/issues/283 and https://github.com/ooni/probe/issues/1565. *## Building a web platform for test list updates and URL prioritization* We made progress on building a web platform that will serve two purposes: * Enabling community contributions to the Citizen Lab test lists (without a GitHub account); * Enabling the OONI team to make adjustments to URL priorities for testing. To avoid unsolicited traffic/activity, we will be issuing OONI accounts to community members so that they can login to this web platform. Once logged in, community members will be able to review the Citizen Lab test lists, add new URLs, propose the deletion or edit of existing URLs, and propose different category codes. All of this will be done through a web platform, without requiring community members to use GitHub. Once they have submitted their contributions through this web platform, pull requests will automatically be opened on the Citizen Lab test list GitHub repository (to ensure that test list contributions continue to go through the usual community review process on GitHub). The same web platform will also be used by the OONI team to adjust the testing prioritization of URLs, based on our URL prioritization policy: https://ooni.org/post/ooni-smart-url-list-system/ In May 2021, we made progress on building the URL priority management interface, the login interface, and the URL submission interface. The URL prioritization management interface is an internal tool which allows members of the OONI team to adjust the priority of URLs or of Citizen Lab category codes for testing (https://github.com/ooni/url-prioritization). Specifically, we added support to the backend and the frontend of the platform that will enable users to login. This login workflow functions by sending a one-time login token to the registered user’s email address. Once the token is presented to the backend, a cookie is registered in the user’s browser, allowing them to login to the URL submission and prioritization backend. Our work on this is documented through the following ticket: https://github.com/ooni/backend/issues/491 *## OONI Measurement Aggregation Toolkit* We made progress on OONI’s new Measurement Aggregation Toolkit ( https://explorer.ooni.org/experimental/mat) which allows us to display measurements in aggregate over any arbitrary axis (for example, measurements over time). In particular, we started adding support for creating multi-dimensional charts which allows us to display all measurements for all inputs over time. Since the charts are very large, we needed to measure the performance of various approaches to plotting them and came up with a solution that allows us to achieve acceptable performance. This performance boost was achieved through the use of a technique called windowing, where only the visible area of the chart is rendered in the browser at a given time. This work is documented through the following pull request: https://github.com/ooni/explorer/pull/579 *## OONI Explorer* We added support to OONI Explorer for displaying the reason for the anomaly (DNS, TCP/IP, HTTP-failure, HTTP-diff) in the search listing. This allows users to quickly look at the different types of anomalies that occur over time for a given search query (enabling the confirmation of censorship events and ruling out false positives). This work is tracked through the following GitHub issue: https://github.com/ooni/explorer/issues/438. We also added support for filtering the WhatsApp IM test results by anomaly (https://github.com/ooni/explorer/pull/589), and we added support for running end-to-end tests of legacy YAML measurements inside of the continuous integration of OONI Explorer ( https://github.com/ooni/explorer/pull/594). *## OONI backend* We added backend support for the scoring (i.e. marking them as anomalies or OK) of Signal experiment measurements: https://github.com/ooni/backend/issues/500 Due to the discontinuation of the Bintray service, we migrated all our internal Debian repositories away from the service and switched to using AWS S3 instead. This is documented through the following tickets: https://github.com/ooni/probe/issues/1440 and https://github.com/ooni/backend/issues/504. *## Academic research paper on internet censorship in Myanmar* In collaboration with CAIDA, Censored Planet, and other researchers, we worked on an academic research paper which investigates internet censorship in Myanmar following the February 2021 military coup. As part of this paper, we analyzed relevant OONI measurements from Myanmar and documented the blocking of websites across AS networks in the country since the coup. In collaboration with Censored Planet, we discovered several cases of collateral damage (as a result of IP blocks), which we document in the paper. Researchers from CAIDA also document the nightly internet outages in Myanmar following the coup, providing detailed analysis and new findings. We completed the writing of this paper by mid-May and submitted it to the FOCI academic journal ( http://conferences.sigcomm.org/sigcomm/2021/workshop-foci.html), where it has been approved for publication. *## Research report on internet censorship in Azerbaijan* In collaboration with Azerbaijan Internet Watch, we worked on writing a joint research report that examines internet censorship in Azerbaijan over the last year. The first step though was to analyze OONI measurements collected from Azerbaijan, and so we performed relevant year-long OONI data analysis (https://github.com/ooni/ooni.org/issues/851 ). Based on this data analysis, we produced multiple charts (communicating key findings) and we wrote the technical findings. *## Improving OONI Run based on community feedback* Last year, we carried out an extensive OONI Run usability study (involving both a survey and interviews with community members) to collect community feedback on how to improve the OONI Run platform (https://run.ooni.io/). Based on this study, we published a detailed report which includes all of the feedback and findings from this study ( https://ooni.org/post/2020-06-09-ooni-run-usability-study-findings/). In May 2021, we had several dedicated team meetings during which we went through all of the community feedback, opened relevant GitHub tickets, and documented the next steps (and a relevant roadmap) for improving the OONI Run platform based on community feedback. This has been quite a lengthy process because we have had to evaluate several interdependencies (with other platforms we’re currently building), as well as the feasibility of implementing many of the community feature requests. This is an ongoing process. *## Community outreach related to the discontinuation of legacy-probe* Throughout May 2021, we continued relevant community outreach efforts in relation to the upcoming discontinuation of the legacy version of ooniprobe, which relies on v2 onion services (which are being discontinued by October 2021). As legacy ooniprobe still accounts for a relatively large percentage of global OONI measurements, we have been trying to reach these users to encourage them to switch over to the OONI Probe Command Line Interface (https://ooni.org/install/cli). To this end, we have been sharing relevant information (including how to switch to OONI Probe CLI) with multiple community mailing lists and on our social media channels. We have also been reaching out to our partners and other community members, in an effort to reach legacy probe users. *## Test list updates* In May 2021, we contributed the following updates to the Citizen Lab test lists: * Israel: https://github.com/citizenlab/test-lists/pull/770 (we added Palestinian news media and human rights websites to check if they’re blocked in Israel) * Colombia: https://github.com/citizenlab/test-lists/pull/775 (we added a site which OONI data indicated was blocked, but which was not already included in the test list) *## Collaboration with Netalitica on test list updates* Netalitica researchers continued to do excellent work in reviewing and updating more Citizen Lab test lists. In May 2021, we opened a pull request based on Netalitica updates to the Malaysian test list (https://github.com/citizenlab/test-lists/pull/772) and we reviewed their updates to the Indian test list, based on which we shared feedback for further possible improvements. We also provided relevant data analysis support to Netalitica ( https://github.com/ooni/ooni.org/issues/887), sharing statistical information on how many new censorship cases were discovered following their updates to the Citizen Lab test lists. *## Created resources for OPTIMA 2.0 training program* We previously (in late 2020) supported Internews’ OPTIMA Network Measurement Training program for advocates by creating relevant OONI resources and facilitating OONI training sessions. Information about this training program is available here: https://internews.org/resource/optima-network-measurement-training/ In support of Internews’ OPTIMA 2.0 program (the continuation of the training program), we created (in May 2021) a new video recording and a relevant OONI quiz for training participants. We also created a resource on network measurement tools for internet shutdown advocacy. *## Organizing the 2 online OONI Partner Training events* In preparation for the 2 online OONI Partner Training events, we continued to do relevant organizational work. In May 2021, we sent out personal invitations to more than 100 prospect participants and we prepared a draft outline of the training sessions. To ensure that participant needs are met during the training events, we created (and shared) a pre-training survey ( https://forms.gle/YU4TW62LrLKmCC7N9) to collect participant feedback. The feedback shared through this survey helped inform the creation of the final training agenda. *## Updated the OONI Partners page* On our website, we feature all of our partners and their important work through our Partners page: https://ooni.org/partners In May 2021, we updated this page to add 2 more of our partners (with whom we’ve been collaborating closely over the last few years): * IODA: https://ooni.org/partners/ioda/ * OutRight Action International: https://ooni.org/partners/outright-action-international/ *## OONI Team Meeting Day: Strategic Planning* On 5th May 2021, we had an (online) OONI Team Meeting Day focused on strategic planning. As part of this day-long meeting, our team had the following 4 sessions: * Session 1: Time for Reflection * Session 2: Communications Strategies * Session 3: What do you want OONI to be? * Session 4: Strategic fundraising As part of these sessions (particularly sessions 2 and 4), we had the opportunity to share knowledge and skills (with the whole OONI team) gained through the Ford Foundation Communications and Financial Resilience training programs we had participated in over the last months. These sessions offered our team an opportunity to take a step back and brainstorm on big-picture strategic decisions and goals moving forward. Over the years, we generally have such team meetings on an annual or bi-annual basis. In preparation for this OONI Team Meeting Day, we prepared relevant slides, resources, and hands-on exercises to ensure that the discussions are as interactive and useful as possible. As an outcome, all of our team members gained new skills and knowledge in relation to communications and fundraising strategies, and based on our brainstorming discussions and exercises, we refined our upcoming milestones. *## Ford Foundation Financial Innovation & Resilience Training* As part of our participation in the Ford Foundation’s Financial Innovation and Resilience training program, we attended a relevant workshop on 12th May 2021, and a relevant webinar on 27th May 2021. We were offered this great opportunity because we are a grantee of the Ford Foundation, who support OONI’s community-related work. The knowledge and skills gained through this training program have helped us rethink and improve OONI’s fundraising strategies. *## Community use of OONI data### 2020 Annual Report on Digital Rights in Venezuela* On 16th May 2021, our Venezuelan partners, IPYS Venezuela ( https://ooni.org/partners/ipys-venezuela/), published their 2020 Annual Report on Digital Rights in Venezuela. As part of this report, they made use of OONI data ( https://twitter.com/VEinteligente/status/1412532307248877570). Their report is available here: https://ipysvenezuela.org/2021/05/16/32196/ *### Report on the blocking of websites in Egypt* On 24th May 2021, our Egyptian partners, Masaar - Technology and Law Community (https://ooni.org/partners/masaar/), published a research report documenting the techniques and laws around the blocking of websites in Egypt. As part of this report, they made use of OONI data. Their report is available here: https://masaar.net/en/blocking-websites-in-egypt-techniques-and-laws/ *## Community activities### Stockholm Internet Forum 2021* On 12th May 2021, OONI’s Maria participated as a speaker on a panel discussion (“#KeepItOn: Governments weaponizing Internet shutdowns”) at the Stockholm Internet Forum 2021 (https://stockholminternetforum.se/). As part of her participation on the panel, Maria presented OONI’s work and discussed how OONI has supported the advocacy efforts of the #KeepItOn campaign (https://www.accessnow.org/keepiton/) in fighting internet shutdowns around the world. *### OONI workshops at TechUp event* On 15th May 2021, OONI’s Maria facilitated 2 online OONI workshops for civil society communities in India and in the Philippines during the TechUp event, organized by the IO Foundation ( https://www.theiofoundation.org/techup/). As part of these 2 workshops, Maria presented OONI’s tools, methodologies, and dataset, and provided live demos explaining how participants can use OONI Explorer (https://explorer.ooni.org/) to track censorship events worldwide in real-time. As part of outreach efforts, we created an OONI e-booth on TechUp’s Airmeet platform. This provided OONI resources and information for civil society communities in Asia. *### Localization Lab Summit 2021* On 21st and 28th May 2021, we attended the Localization Lab Summit 2021 ( https://www.localizationlab.org/localization-summit-2021-sessions), during which we had the opportunity to meet with the Localization Lab community, learn about emerging digital rights threats around the world, and unmet community needs. We also had the opportunity to connect with funders and the developers of other internet freedom tools, and to learn more about localization needs and challenges. Given that the translation and overall localization of the OONI Probe apps is supported by the Localization Lab community, this was a very important opportunity for us to learn more about community needs and challenges, which helps inform the development and improvement of our tools. *### OONI training facilitated by Cameroonian partners* In May 2021, our Cameroonian partner, COMPSUDEV ( https://ooni.org/partners/compsudev/), collaborated with AfroLeadership ( https://afroleadership.org/) on organizing and facilitating a 2-day training event (“Building Evidence for Internet Rights Advocacy”) for civil society groups in Cameroon. As part of this training event, they facilitated OONI workshops with the goal of introducing participants to OONI’s tools, methodologies, and dataset. More specifically, they walked through the OONI Probe apps (explaining how participants can use them to measure internet censorship), demoed OONI Explorer (explaining how they can find and use OONI data as part of advocacy), and collected participant feedback. We are very grateful for these community-initiated OONI workshops! *### OONI feedback collected from civil society in Tanzania* In May 2021, Tanzania’s Zaina Foundation carried out a Feedback Collection project for several open source tools, including OONI. As part of this, they asked community members in Tanzania to share their feedback on OONI Probe and OONI Explorer. Following this project, Zaina Foundation shared with us the feedback they collected from human rights defenders in Tanzania for the improvement of OONI Probe and OONI Explorer. *### OONI guide by Fundación Karisma* Starting on 26th May 2021, OONI measurements collected from Colombia started to show: * Blocking of ghostbin.co: https://explorer.ooni.org/search?until=2021-06-02&since=2021-05-03&domain=g… * Blocking of archive.org: https://explorer.ooni.org/search?until=2021-06-02&since=2021-05-03&domain=a… To encourage further testing, our Colombian partner, Fundación Karisma ( https://ooni.org/partners/karisma-foundation/), wrote and published a short OONI guide (in Spanish): https://web.karisma.org.co/micro-guia-para-el-uso-de-ooni/. They also promoted their OONI guide (and OONI Probe testing) on their social media channels: https://twitter.com/Karisma/status/1398372339918721030 *### OONI Community Meeting* On 25th May 2021, we hosted the monthly OONI Community Meeting on our Slack channel (https://slack.ooni.org/), during which we discussed the following topics: 1. Updates regarding the new web platform for suggesting updates/edits to the Citizen Lab test lists. How shall we deal with dead URLs that still remain blocked in a given country? 2. Pluggable transport implementation in any networking system, and the current state of obfs4 support in OONI Probe. *## Userbase* In May 2021, 10,261,241 OONI Probe measurements were collected from 5,132 AS networks in 191 countries around the world. This information can also be found through our measurement stats on OONI Explorer (see chart on “monthly coverage worldwide”): https://explorer.ooni.org/ ~ OONI team.

1 0

OONI Monthly Report: April 2021
by Maria Xynou 15 Jul '21

15 Jul '21

Hello, Hope you're all doing well. These days we're primarily supported by the DRL, which is why we do quarterly reporting. That said, we'd like to share monthly updates from the OONI team with the community, hence our April 2021 report shared below. I'll also follow-up to share our May and June 2021 reports. *# OONI Monthly Report: April 2021* Throughout April 2021, the OONI team worked on the following sprints: * Sprint 36 - Rhodophyta (1-11 April, 2021) * Sprint 37 - Vampire squid (12-25 April, 2021) * Sprint 38 - Umbrella octopus (26-30 April, 2021) Our work can be tracked through the various OONI GitHub repositories: https://github.com/ooni Highlights are shared in this report below. *## Released new OONI Probe test for Signal Private Messenger App* The OONI Probe apps now feature a brand new test for the Signal Private Messenger app! You can test the Signal app on your network and check if it's blocked. The specification of the OONI Probe Signal test is available here: https://github.com/ooni/spec/blob/master/nettests/ts-029-signal.md We also wrote a Signal test description (for a more general audience), which we published on our website: https://ooni.org/nettest/signal Through the OONI Probe Signal test, users can check if it’s possible to establish a connection to the various backend services used by the Signal app or if Signal is being interfered with on their network. Following the implementation of our Signal test ( https://github.com/ooni/probe-cli/pull/230), we created a UI for displaying the test results inside of the OONI Probe apps. We then worked on integrating the Signal test inside of the OONI Probe mobile and desktop apps in preparation for the new app releases. Our new Signal test was shipped as part of OONI Probe Desktop 3.4.0 ( https://github.com/ooni/probe-desktop/pull/202) and OONI Probe Mobile 2.11.0 (https://github.com/ooni/probe-android/pull/422, https://github.com/ooni/probe/issues/1415). All Signal test results from around the world are openly published in near real-time on OONI Explorer: https://explorer.ooni.org/search?since=2021-03-15&test_name=signal *## Updated the user guides for OONI Probe Mobile and Desktop Apps* In April 2021, we published updated versions of our user guides for the OONI Probe apps: 1) User Guide: OONI Probe Mobile: https://ooni.org/support/ooni-probe-mobile 2) User Guide: OONI Probe Desktop: https://ooni.org/support/ooni-probe-desktop Following relevant OONI Probe mobile and desktop releases, we updated the guides to include new features, settings, step-by-step instructions, and screenshots (https://github.com/ooni/ooni.org/issues/844). *## Beta for automated testing on OONI Probe Android* In April 2021, we released a beta version for automated testing on OONI Probe Android! This means that users can have OONI Probe test websites automatically multiple times per day (without having to remember to run OONI Probe or do anything). We reached out to community members, requesting that they help test the beta and report any issues they encounter. Users could help test the beta version by: 1) Joining the beta program: https://play.google.com/apps/testing/org.openobservatory.ooniprobe 2) Updating (through the Play Store) to OONI Probe 3.0.0-beta.1 (Android) 3) Through the OONI Probe 3.0.0-beta.1 app, tapping Settings -> Automated testing and enabling the "Run tests automatically" setting. The beta included settings for having automated tests run only when users are connected to WiFi and while their phone is charging (though they can configure this in the "Automated testing" settings). To avoid cluttering the UI of the OONI Probe Test Results screen, the test results from automated testing will only be made available on OONI Explorer (published automatically in real-time): https://explorer.ooni.org/ *## Improvements to the testing of OONI Probe Android* We onboarded an external contractor (Bloco) to assist us with the development of integration and unit tests for OONI Probe Android. This has led to improving the overall code quality of the app, as well as ensuring that it’s better tested so that we can have higher confidence in what we ship to end users. This work is documented through the following pull request: https://github.com/ooni/probe-android/pull/426 *## Research on implementing automated testing on iOS* We carried out research to explore the feasibility of adding support to the OONI Probe iOS app to perform background tasks (required for automated testing). We also created a prototype for OONI Probe iOS background tasks: https://github.com/ooni/probe/issues/1459 *## OONI Probe backend proxy support* We worked on adding backend proxy support to the OONI Probe apps in order to make them more resilient to intentional or accidental blocking. More specifically, we added support that will enable OONI Probe users to use Psiphon or a custom proxy to communicate with OONI backend services. In April 2021, we released an alpha version with Psiphon proxy support: https://github.com/ooni/probe-cli/releases/tag/v3.10.0-alpha. We also created a UI for the new OONI backend proxy settings in the OONI Probe apps. All of this work is documented through the following ticket: https://github.com/ooni/probe/issues/985 *## Preview release of OONI Probe Desktop with RTL support* In April 2021, we made a preview release of OONI Probe Desktop with RTL support: https://github.com/ooni/probe-desktop/releases/tag/v3.5.0-rtl.1 This experimental release includes support for languages that use Right-to-Left (RTL) scripts, such as Arabic and Farsi. We shared this preview release with community members to get their feedback on how to improve it before the public release. Based on their feedback, we made a series of improvements. *## OONI Probe Command Line Interface (CLI)* We released OONI Probe CLI 3.9.0 (https://github.com/ooni/probe/issues/1369) which includes a series of improvements and end-to-end testing. We continued to work on redesigning the probeservices package ( https://github.com/ooni/probe/issues/1405) to add circumvention support, making OONI Probe more resilient to censorship. We also completed work related to implementing the check-in API in OONI Probe CLI ( https://github.com/ooni/probe/issues/1299). *## Changes to the OONI Probe Android TLS fingerprint* We noticed that OONI Probe Android was not working properly on some networks in Iran. We therefore investigated the issue and discovered that the block had to do with the fact that a specific ordering of the TLS cipher suites was leading to fingerprinting and blocking on this network. As a result of this, we patched the golang TLS code to maintain the same cipher suite ordering as it does on desktop, which resulted in us managing to unblock the app in Iran. More details about this issue are available through the following ticket: https://github.com/ooni/probe/issues/1444 (and our relevant blog post: https://ooni.org/post/making-ooni-probe-android-more-resilient/#changing-ou…). *## Research on implementing a new Snowflake experiment in OONI Probe* We carried out research (and testing) necessary for evaluating the feasibility of implementing a new Snowflake experiment in the OONI Probe apps and concluded that it is feasible. Our work on this research prototype is documented through the following ticket: https://github.com/ooni/probe-engine/issues/283 *## Data quality improvements* We improved upon the quality of OONI Probe RiseupVPN measurements by fixing a bug to reduce the ratio of false positives. This work is documented through the following ticket: https://github.com/ooni/probe/issues/1354 Based on the RiseupVPN test, RiseupVPN was flagged as “likely blocked” even if a single gateway was blocked, without taking into account the built-in fallback mechanisms. Moreover, the gateways were indicated as “likely blocked” if they were malfunctioning for other reasons (such as misconfiguration, DDoS, reboot on security updates etc.). As a result, this produced a lot of false positives. To address this, we made a series of improvements in order to improve the accuracy of the RiseupVPN test and to reduce the ratio of false positives. *## Improvements to OONI Explorer* We added support for grouping test names by the relative test group under the “Test Name” filter of the OONI Explorer Search page: https://github.com/ooni/explorer/pull/573 We fixed an issue related to how we were displaying the timestamps in the summary text of the OONI Explorer measurement pages: https://github.com/ooni/explorer/issues/541 Thanks to a community contribution, we now have support in the measurement pages for expanding all the measurement data JSON keys: https://github.com/ooni/explorer/pull/567 *## Creating a real-time incident response dashboard* We made considerable progress on the Measurement Aggregation Toolkit, which allows users to plot aggregate charts of measurements in response to ongoing censorship events. In particular, we added support for plotting charts on multiple axes, allowing us to display anomaly counts of measurements over time per URL. This work is documented through the following pull request: https://github.com/ooni/explorer/pull/579 *## Proof of concept for new URL submission web platform* To enable community members to contribute to the Citizen Lab test lists (which include URLs measured by OONI Probe), we are creating a web platform that will enable users to review and contribute to the test lists without using GitHub (contributions from this new web platform will still end up as pull requests on the Citizen Lab test list repository for review). In April 2021, we created a proof of concept backend implementing the full URL submission functionality. We Integrated the URL submission/editing backend into the OONI API: https://github.com/ooni/backend/issues/490. This allows users to contribute URLs to the Citizen Lab test lists without needing to create a GitHub account or knowing how to format a pull request. This work is documented through the following ticket: https://github.com/ooni/backend/issues/487 *## OONI backend* Throughout April 2021, we worked on the following backend activities: * Added support to the OONI API for the new OONI Probe Signal test * Investigated a check-in test list bug (which wasn’t returning entries), added metrics, fixed the bug, and added fallback options: https://github.com/ooni/probe/issues/1328 * Monitored the growth of incoming OONI measurements from unattended runs (to ensure that our infrastructure can handle the increased load and to check if measurement coverage increases as expected) * We started evaluating DuckDB as an alternative database solution by building a test DB and performing a quick benchmark * Server infrastructure improvements related to VPS that we use for running OONI Probe CLI experiments * Worked on switching ooniprobe and backend Debian packages to S3: https://github.com/ooni/probe/issues/1359 * Made progress on the OONI API registration and login, deployed it on our testing infrastructure and performed testing with probes: https://github.com/ooni/backend/issues/491 * Integrated the URL submission/editing backend into the OONI API: https://github.com/ooni/backend/issues/490 * Discussed backend/db requirements for storing new dimensions around OONI Web Connectivity measurements (server IP address, multiple DNS resolvers, blocking taxonomy): https://github.com/ooni/backend/issues/492 *## Dealt with the discontinuation of Bintray* We used to rely on Bintray for hosting the Debian package repositories for probe-cli, as well as several internal tooling used in our infrastructure. Bintray has announced that they are going to discontinue the service ( https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartce…) and as a result of this, we have had to migrate our infrastructure away from Bintray and replace it with an s3 based solution. This work is documented through the following ticket: https://github.com/ooni/probe/issues/1437 We also moved the debian package generation over to github actions so that it’s following the same pattern used in the rest of our repositories. Moreover we added support for signing of packages and added support for the detection of duplicate packages. *## Updated OONI Data Policy* On 13th April 2021, we published an updated version of the OONI Data Policy: https://ooni.org/about/data-policy This updated documentation reflects the changes we made in terms of our use of analytics in the OONI Probe apps ( https://github.com/ooni/ooni.org/pull/838). Following a careful audit of various analytics tools (as reported in March 2021), we removed Firebase analytics and app usage metrics entirely from the OONI Probe mobile app, while ensuring that no analytics are used on OONI Probe F-Droid. Rather, we limited the OONI Probe mobile app to the use of Sentry for crash reports (when users opt-in) and to the use of Countly for sending push notifications on Android. On OONI Probe desktop, we removed Matomo app usage metrics, and limited the app to the use of Sentry for crash reports (when users opt-in). We made these changes as part of our data minimization efforts. *## Academic paper investigating internet censorship in Myanmar* We collaborated with CAIDA, Censored Planet, and other researchers on an academic research paper investigating the censorship events in Myanmar following the military coup (on 1st February 2021). This paper builds upon our previous study on censorship events in Myanmar ( https://ooni.org/post/2021-myanmar-internet-blocks-and-outages/), offering additional data analysis and new insights. In April 2021, we worked on (and completed) OONI data analysis required for this academic paper (https://github.com/ooni/ooni.org/issues/855). Specifically, we analyzed OONI measurements collected from Myanmar with the aim of examining whether and how censorship events changed in the country between January 2021 to April 2021, how censorship varied across AS networks, and we investigated potential cases of collateral damage (as a result of IP blocks). Based on our analysis, we produced multiple charts (communicating key findings) and started working on writing the paper. *## Data analysis for IPYS Venezuela* We provided data analysis support to our Venezuelan partner, IPYS Venezuela (in support of their annual digital rights report). This involved a year-long analysis of OONI measurements collected from Venezuela, primarily aimed at identifying the blocking of websites (and how that varies across AS networks). As a result of this analysis, we produced a relevant chart and CSV file (https://github.com/ooni/ooni.org/issues/823), which we shared with IPYS Venezuela in support of their research. *## Data analysis for Azerbaijan Internet Watch* In support of our partner, Azerbaijan Internet Watch, we analyzed OONI measurements collected from Azerbaijan between 1st January 2021 to 30th April 2021. As part of this analysis, we documented the (ongoing) blocking of independent news media and circumvention tool websites (based on OONI data). Based on our analysis, we produced relevant charts (that summarize key findings) and a report: https://www.az-netwatch.org/wp-content/uploads/2021/04/2021-04-Azerbaijan-I… Azerbaijan Internet Watch also published a summary of our report findings on their site: https://www.az-netwatch.org/news/azerbaijan-keeps-blocking-access-to-key-in… *## Data analysis for the Tor Project* We collaborate with the Tor Project’s anti-censorship team on monitoring Tor blocking around the world. As part of these efforts, we analyzed OONI measurements collected from Belarus over the last year to examine torproject.org reachability. Based on this analysis, we produced and shared relevant CSV files and charts with the Tor Project’s anti-censorship team. *## Test list updates* In April 2021, we updated the Citizen Lab test list for Togo ( https://github.com/citizenlab/test-lists/pull/766) by adding media websites shared by Reporters Without Borders. *## Planning the OONI Partner Training 2021* In April 2021, we started planning the logistics surrounding the organization of an OONI Partner Training. We were initially hoping to host an in-person event for all our partners, but in light of the COVID-19 pandemic (and associated travel restrictions), we decided to facilitate the event entirely online. Given that our partners are located around the world (from Latin America to Asia), we needed to consider training formats that would accommodate different time zones and different community needs. As such, we started organizational work related to hosting online OONI Partner Trainings in April 2021 (the events were scheduled for late June 2021 and early July 2021), and created a Concept Note. *## Ford Foundation Financial Innovation & Resilience Training* As part of our participation in the Ford Foundation’s Financial Innovation and Resilience training program, we attended a relevant workshop on 14th April 2021, and a relevant webinar on 22nd April 2021. We were offered this great opportunity because we are a grantee of the Ford Foundation, who support OONI’s community-related work. The knowledge and skills gained through this training program have helped us rethink and improve OONI’s fundraising strategies. *## Community activities### 87th Nexa Lunch Seminar* On 28th April 2021, OONI’s Simone was a speaker at the Nexa Center for Internet and Society’s (online) 87th Lunch Seminar (titled “The risks of digital sovereignty”). Information about the event is available here: https://nexa.polito.it/lunch-87 *### Research on Twitter throttling in Russia* Censored Planet produced a great research report examining the throttling of Twitter in Russia: https://censoredplanet.org/throttling. OONI’s Simone collaborated with the Censored Planet team and contributed to this research. *### OONI Community Meeting* On 27th April 2021, we hosted the monthly OONI Community Meeting on our Slack channel (https://slack.ooni.org/), during which we discussed the following topics: 1. Updates from the OONI team: (1) New Signal test, (2) Automated testing on OONI Probe Android 3.0.0-beta.1, (3) Switching from legacy ooniprobe to OONI Probe CLI. 2. Updates on internet censorship in Uganda (social media and VPN blocking) and Tanzania (Twitter blocking). 3. Updates on OONI’s new URL submission web platform. 4. The research benefit of potentially including dead/expired URLs in test lists. *## Userbase* In April 2021, 8,539,001 OONI Probe measurements were collected from 5,141 AS networks in 200 countries around the world. This information can also be found through our measurement stats on OONI Explorer (see chart on “monthly coverage worldwide”): https://explorer.ooni.org/ ~ OONI team.

1 0

(Call for Presentations) Tor Demo Day - August 25th 2021
by gus 13 Jul '21

13 Jul '21

Hello, We are going to have the next Demo day in August 25th @ 1600 UTC. You can submit your proposal using this form, and I will get in touch to confirm your presentation: https://nc.torproject.net/apps/forms/Nr3ceMnHsqCBopos cheers, Gus Tor Demo Day - August 25th 2021 =============================== Why? ---- - We want to spice up our remote working routine and also break the silos between teams. - Tor Demo Days are a success and we want to share this experience with the broad Tor community! How? ---- - We are opening the call for presenters. - The agenda will be set before the meeting and will be shared with tor-project. - We want 5 to 10 minutes length presentations. We will handle questions at the end of all presentations. - Slides are allowed, but not mandatory. You may share your screen or a pre-recorded video if that makes you less anxious. - We like the adrenaline of the live presentations, but if they wish, presenters can share pre-recorded videos with us. They should be sent a few hours in advance and will be lined up and shared with assistants during the session. - This is a place where people should feel safe to engage, share their point of view, and participate. Read our Code of Conduct: https://gitweb.torproject.org/community/policies.git/tree/code_of_conduct.t… Who? ---- - Anyone who wants to share what they have been hacking on. It doesn't need to be a finished feature but a work in progress. It can be small like a Tor Browser feature or something you have been hacking around Tor not officially. - Presenters have 5 to 10 minutes. People can ask questions via text for 3 minutes. - Gus will moderate at this time. We need volunteers for other Demo days in 2021. Where? ------ At our BBB instance. A public link will be shared the same day of the Demo. When? ----- Wednesday August 25th at 1600 UTC. How to submit a proposal ------------------------ Just use this form: https://nc.torproject.net/apps/forms/Nr3ceMnHsqCBopos -- The Tor Project Community Team Lead

1 0

UX team monthly meetings notes, July 13th
by Duncan Russell 13 Jul '21

13 Jul '21

1 0

Tails report for June 2021
by sajolida＠pimienta.org 13 Jul '21

13 Jul '21

Tails report for June, 2021 [1] HIGHLIGHTS * We entirely rewrote and redesigned our very old warnings page [2]. The new warnings page [3] is shorter, easier to understand by less technical people, less scary, more helpful, and visually attractive. We also integrated it in our download page [4] so that people can learn more about tails while waiting for their download. Read our articles on: * Protecting your identity [5] * Limiations of Tor [6] * Using untrusted computers [7] * We finished making Tails ready for the deprecation of onion services v2 by upgrading to OnionShare 2.2. * We explained that users can reduce the size of the download [8] of future automatic upgrades by doing a manual upgrade to the latest version. * We published our finances for 2020 [9]. * We documented better MAT and metadata [10]. * We documented how to use Dino in Tails [11]. Dino is being considered as an option to replace Pidgin in Tails. Please report your findings! METRICS * Tails has been started more than 629 659 times this month. This makes 20 989 boots a day on average. How do we know this? [12] Links: ------ [1] https://tails.boum.org/news/report_2021_06/ [2] https://web.archive.org/web/20210531191605/https://tails.boum.org/doc/about… [3] https://tails.boum.org/doc/about/warnings/index.en.html [4] https://tails.boum.org/install/download/index.en.html [5] https://tails.boum.org/doc/about/warnings/identity/index.en.html [6] https://tails.boum.org/doc/about/warnings/tor/index.en.html [7] https://tails.boum.org/doc/about/warnings/computer/index.en.html [8] https://tails.boum.org/doc/upgrade/index.en.html#reduce [9] https://tails.boum.org/doc/about/finances/index.en.html#2020 [10] https://tails.boum.org/doc/sensitive_documents/metadata/index.en.html [11] https://tails.boum.org/doc/advanced_topics/dino/index.en.html [12] https://tails.boum.org/support/faq/index.en.html#boot-statistics

1 0

UX team meeting on July 13th
by Duncan Russell 08 Jul '21

08 Jul '21

Hi everyone! Our next User Experience team meeting will be held on Tuesday July 13th at 1400 UTC in #tor-meeting.* During this meeting we'll share an update on the UX team’s ongoing work across key projects, including the recent release of Tor Browser 10.5. If you'd like to get involved please feel free to add your items to the pad: https://pad.riseup.net/p/1D8sK8Zy74b_0qclC97I-ux-team-monthly-2020-keep <https://pad.riseup.net/p/1D8sK8Zy74b_0qclC97I-ux-team-monthly-2020-keep> Remember, User Experience team meetings are an open space for discussion around ethical user research, user interface design and the user experience of privacy-enhancing products. See you soon! Duncan [*] https://gitlab.torproject.org/tpo/ux/team/-/wikis/home <https://gitlab.torproject.org/tpo/ux/team/-/wikis/home>

1 0

Anti-censorship team monthly report: June 2021
by Cecylia Bocovich 08 Jul '21

08 Jul '21

Hi everyone! This is what we've been up to on the anti-censorship team in June! June 2021 monthly report Snowflake ========= * Fixed a bug that was preventing Snowflake metrics from being counted correctly https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… * Fixed a memory leak in the Snowflake bridge https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… * Fixed some data races in the Snowflake client https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… * Added man pages for snowflake client and proxy commands https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… * Upgraded the hardware resources of the Snowflake bridge BridgeDB ======== * Improve the strings to make it easier for translators https://gitlab.torproject.org/tpo/anti-censorship/bridgedb/-/issues/12957 rdsys ===== * WIP of integration of gettor https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/issues/32 * WIP integration of BridgeDB with rdsys https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/issues/12 https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/issues/38

1 0

Anti-censorship meeting notes, 2021 July 8
by Cecylia Bocovich 08 Jul '21

08 Jul '21

Hi everyone, Here are our meeting logs: http://meetbot.debian.net/tor-meeting/2021/tor-meeting.2021-07-08-16.00.html and our meeting pad: Anti-censorship work meeting pad -------------------------------- Next meeting: Thursday July 8th 16:00 UTC Weekly meetings, every Thursday at 16: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. == Announcements == Tor Browser 10.5 released with Snowflake. https://blog.torproject.org/new-release-tor-browser-105 Peep the charts 👀 https://metrics.torproject.org/rs.html#details/5481936581E23D2D178105D44DB6… https://metrics.torproject.org/userstats-bridge-transport.html?start=2021-0… == Discussion == == Actions == Please add what you were up to in June to the monthly report: https://pad.riseup.net/p/dlSPsaKmgz_zoucqcp_N == Interesting links == snowflake-client.exe in TB 10.5 detected as malware https://lists.torproject.org/pipermail/tor-talk/2021-July/045752.html https://www.reddit.com/r/TOR/comments/of1gu3/windows_defender_latest_tor_br… https://gitlab.torproject.org/tpo/web/support/-/issues/237 == Reading group == We will discuss "" on Questions to ask and goals to have: What aspects of the paper are questionable? Are there immediate actions we can take based on this work? Are there long-term actions we can take based on this work? Is there future work that we want to call out, in hopes that others will pick it up? == Updates == Name: This week: - What you worked on this week. Next week: - What you are planning to work on next week. Help with: - Something you need help with. cecylia (cohosh): last updated 2021-07-08 Last week: - quick fixup for snowflake client torrc (snowflake#40041) - talked to orbot about their default bridge configs - https://github.com/guardianproject/orbot/issues/488 - Updated sample torrc files to encourage use of BridgeDistribution instead of PublishServerDescriptor - core/tor!410 - reviewed bridgestrap!7 (collector metrics for bridgestrap) - reviewed snowflake!46 (have proxies report their client counts) - more work on shim for moat (bridgedb#32276) - wrote up a quick iptproxy patch to have orbot report a different proxy type to the broker - https://github.com/tladesignz/IPtProxy/pull/10 - reviewed snowflake!39 (split broker into components) This week: - followup review for rdsys!11 - finish deploying moat shim (bridgedb#32276) - more work on snowflake documentation (snowflake#40031) - kcp/smux parameters (snowflake#40026) Needs help with: - snowflake-webext!18 (website change) arlolra: 2021-07-08 Last week: - More snowflake!39 Next week: - Maybe get back to snowflake-webext #10 Help with: - dcf: 2021-07-07 (will be absent for 2021-07-08 meeting) Last week: Next week: - AMP cache rendezvous for snowflake https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… Help with: agix:2021-07-08 Last week: -Off till next week due to final exams Next week: -Work on bridgebox for rdsys -More research on httpt #4 Help with: - hanneloresx: 2021-3-4 Last week: - Submitted MR for bridgestrap issue #14 Next week: - Finish bridgestrap #14 - Find new issue to work on Help with: - maxb: 2021-07-28 Last week: - Worked on github.com/max-b/nat-testing for https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… - Have the client actually using the snowflake proxies, but not actually building a bridge/making a connection - Debugging has been difficult/required actually understanding a bit more of the underlying protocols/etc Next week: - Fix proxy connections!! - Make config fixes cohosh suggested - Implement alternative NAT types - Add testing wrapper w/ "pass/fail" conditions meskio: 2021-07-08 Last week: - merge collector metrics in bridgestrap (bridgestrap#15) - merge snowflake assign proxies based on self-reported client load (snowflake#40048) - gettor rdsys integration (rdsys!11 rdsys#32) Next week: - continue work on gettor in rdsys (rdsys!11 rdsys#32) - document our server setup in TPA wiki Help with: -

1 0

User Feedback Report - June 2021
by Kulsoom Zahra 08 Jul '21

08 Jul '21

Greetings, everyone! This is a report of the work done by the Community Team in the past month and general user feedback that we've received across our official support channels. Report Period - May 24 upto July 1 --- Request Tracker --- Tickets resolved in the past month: 212 # New RT templates We gathered data on the most frequent issues faced by Tor users and turned their responses into RT articles/templates. This will help people working on the RT provide better user assistance. The following articles have been created or updated: 1. v2 onion deprecation 2. Will TB keep all my applications safe? Download files off Tor? Can someone access my files while using Tor? Etc. Here is a list of issues which got the most attention (at least 3 tickets on RT): # Tor Browser Breakdown of number of RT tickets received with respect to operating system: Windows (10,8,7 ...all the way upto XP) - 23 MacOS - 6 GNU/Linux - 2 Android - 11 (Note: This includes tickets where the user mentioned the operating system or it was evident from the issue they were running into or enclosed screenshots.) 1. 7 RT tickets - Failure to launch Tor Browser "Tor unexpectedly exited". We point users to the "Seven-point basic troubleshooting" article (template) on the RT to help users. 2. 6 RT tickets - Unable to access websites including bank sites and social media sites eg. Instagram. We point users to the "Banking sites blocked over Tor & Basic troubleshooting when users can't access any particular website" article (template) on the RT to help users. 3. 3 RT tickets - Error "RSA_get0_d could not be located in the dynamic link library tor.exe" on Windows. We have a GitLab ticket regarding this long standing issue. [1] 4. 3 RT tickets – TB crashes/ Goes blank after Windows 10 version 21H1 update. We have a GitLab ticket regarding this issue. [2] 5. 9 RT tickets - Installation Issue 2 - Windows : We ask them to download the correct version TB 32-bit or 64-bit. [3] 4 - Windows : Trying to install in wrong directory 3 - macOS : Error "no mountable file systems". We ask users to update their OS. 6. 3 RT tickets - Questions around VPN. We direct users to the article on the Support Portal. [4] and "Tor vs VPN" template. 7. 4 RT tickets - Change my guard/torrc file to not pick nodes from the same country. We teach users why modifying the way that Tor creates its circuits is strongly discouraged and point them to the article on the Support Portal. [5] 8. 3 RT tickets - Cannot upload files on Tor Browser for Android. Regarding this we have a ticket open on our GitLab [6]. This issue is already listed on 'Known Issues' section in the Tor Browser User Manual. [7] 9. 4 RT tickets - Error "Proxy Server Refused Connection". We ask users NOT to set TBA as their default browser and point them to the article in the Support Portal. [8] 10. 1 RT ticket – Error "java.io.IOException: Control port file not created". Regarding this we have a ticket open on our GitLab. [9] 11. 3 RT tickets – Confusion around F-Droid & what apk to download from our Download page. (under Android) [10] # Onion Services 5 tickets - v2 onion deprecation. Users were confused what to do, how to upgrade v2 to v3, will i be able to use Tor. We help users identify v2 and v3 onions, point them to the "v2 onion deprecation" article (template) on the RT . # Censorship Circumvention We got a total of 10 tickets requesting help to connect to Tor which have been from Iran, China and other countries. We provided private bridges for them. # UI/UX 1. Google Play Store We have recieved both positive and negative reviews. The negative ones are majorly about removing the "Quit" button which spans 11 comments. Other negative rating reviews revolve around not being able to download and slow speed of the browser. 2. Tor Stack Exchange - Statistics of what the discussion has been about (5 most active tags): tor-browser-bundle- 28 questions configuration (questions about configuring Tor software)- 19 questions hidden-services- 18 questions onion-routing - 5 questions anonymity- 10 questions security- 8 questions 3. Reddit - Discussion has mostly been around Tor + VPN, running Snowflake proxies, Unable to access sites, hosting onion servies, Cloudfare blocked over Tor and exit relays. If you have any suggestions, questions or want to discuss anything in detail please feel free to reach out to me and/or anyone from the Community Team! Thanks, Kulsoom Links: [1]: https://gitlab.torproject.org/tpo/core/tor/-/issues/33702 [2]: https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40422 [3]: https://www.torproject.org/download/languages/ [4]: https://support.torproject.org/#faq-5 [5]: https://support.torproject.org/#tbb-16 [6]: https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40283 [7]: https://tb-manual.torproject.org/mobile-tor/#known-issues [8]: https://support.torproject.org/tbb/tbb-32/ [9]: https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40196 [10]: https://www.torproject.org/download/#android

1 0

Monthly Status Report for irl
by Iain R. Learmonth 06 Jul '21

06 Jul '21

Hi All, This is my monthly status report for work complete during June 2021. This month saw the releases of metrics-lib 2.17.0 and Onionoo 8.0-1.26.1. The new Onionoo release includes a number of fixes that me and Karsten had previously been working on related to reliability, and now also uses the IP Fire database that is used by core Tor. This means that the GeoIP information on Relay Search is also now based on the IP Fire database. Work has begun on importing bridge reachability testing into the Tor Metrics pipeline to improve the UX situation for bridge operators regarding knowing if their bridge is online or not. Since this work has been delayed, it is now expected to be completed by August 31st. Support for parsing bridgestrap metrics has been merged to the development branch of metrics-lib although this has not yet been included in a release. I'm expecting that will happen early this month. Finally, I have been around in Matrix/IRC to answer Metrics questions and on occasion to provide a little end-user support in #tor. I've been attending the weekly network health meetings and will continue to do so. If you've got any questions about anything I'm working on, just send me an email or chat on Matrix/IRC. Thanks, Iain.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

tor-project July 2021