April 2022 - tor-project - lists.torproject.org

Are there countries where using Tor is illegal?
by Cristian Consonni 11 May '25

11 May '25

Hi, (Sorry if this question has already been asked in the past, feel free to point me to the relevant resources.) I know that the legal FAQs by the EFF state that: «we believe that running a Tor relay — including an exit relay that allows people to anonymously send and receive traffic — is legal under U.S. law.»[1] I also know there is a list of countries for which there is legislation that exclude communication service providers from liability. They are indicated in the Legal of the Tor Exit Guidelines page[2], they are USA, Germany, Netherlands, Austria, France, and Sweden. >From some articles in the press[3a][3b] it may be illegal - depending on how you interpret the wording[*] - to use Tor (and other technologies such as VPNs or proxies) in the UAE, with fines ranging in the millions of dirhams (hundreds of thousand of dollars). A couple of weeks ago it was discussed - on this list as well - that a law was introduced to the state parliament to ban Tor[4a][4b]. This follows a case of some months ago of a Russian Tor exit node operator being arrested for inciting mass riots and terrorism[4c][4d]. The idea of blocking VPNs or Tor seems to have already been considered in the past[4e]. This infographic about pluggable transports[5] suggests access to the Tor network is censored or limited in China, Uzbekistan, Iran, and Kazakhstan. Tor being censored orblocked may be different from it being illegal. What about other countries? Is there a place where I can find more about this topic? Cristian [1]: https://www.torproject.org/eff/tor-legal-faq.html.en [2]: https://trac.torproject.org/projects/tor/wiki/doc/TorExitGuidelines [3a]: http://www.emirates247.com/news/emirates/dh500-000-fine-if-you-use-fraud-ip… [3b]: http://news.softpedia.com/news/people-caught-using-vpns-tor-or-proxies-in-t… [*]: «Whoever uses a fraudulent computer network protocol address (IP address) by using a false address or a third-party address by any other means for the purpose of committing a crime or preventing its discovery» [4a]: https://lists.torproject.org/pipermail/tor-talk/2017-June/043293.html [4b]: https://trac.torproject.org/projects/tor/ticket/22055 [4c]: https://lists.torproject.org/pipermail/tor-talk/2017-April/043109.html [4d]: https://techcrunch.com/2017/04/24/dmitry-bogatov-tor-russia/ [4e]; https://torrentfreak.com/vpn-and-tor-ban-looming-on-the-horizon-for-russia-… [5]: https://www.torproject.org/images/PT/2016-07-how-to-use-PT.png

4 3

TPA-RFC-20: bullseye upgrade schedule
by Antoine Beaupré 23 Jun '22

23 Jun '22

Note: this proposal is also visible in: https://gitlab.torproject.org/tpo/tpa/team/-/wikis/policy/tpa-rfc-20-bullse… Summary: bullseye upgrades will roll out starting the first weeks of April and May, and should complete before the end of August 2022. Let us know if your service requires special handling. # Background Debian 11 [bullseye][] was [released on August 14 2021][]). Tor started the upgrade to bullseye shortly after and hopes to complete the process before the [buster][] EOL, [one year after the stable release][], so normally around August 2022. In other words, we have until this summer to upgrade *all* of TPA's machine to the new release. New machines that were setup recently have already been installed in bullseye, as the installers were changed shortly after the release. A few machines were upgraded manually without any ill effects and we do not consider this upgrade to be risky or dangerous, in general. This work is part of the [%Debian 11 bullseye upgrade milestone][], itself part of the [OKR 2022 Q1/Q2 plan][]. # Proposal The proposal, broadly speaking, is to upgrade all servers in three batches. The first two are somewhat equally sized and spread over April and May, and the rest will happen at some time that will be announced later, individually, per server. ## Affected users All service admins are affected by this change. If you have shell access on any TPA server, you want to read this announcement. ## Upgrade schedule The upgrade is split in multiple batches: * low complexity (mostly TPA): April * moderate complexity (service admins): May * high complexity (hard stuff): to be announced separately * to be retired or rebuilt servers: not upgraded * already completed upgrades The free time between the first two will also allow us to cover for unplanned contingencies: upgrades that could drag on and other work that will inevitably need to be performed. The objective is to do the batches in collective "upgrade parties" that should be "fun" for the team (and work parties *have* generally been generally fun in the past). ### Low complexity, batch 1: April A first batch of servers will be upgraded in the first week of April. Those machines are considered to be somewhat trivial to upgrade as they are mostly managed by TPA or that we evaluate that the upgrade will have minimal impact on the service's users. ``` archive-01 build-x86-05 build-x86-06 chi-node-12 chi-node-13 chives ci-runner-01 ci-runner-arm64-02 dangerzone-01 hetzner-hel1-02 hetzner-hel1-03 hetzner-nbg1-01 hetzner-nbg1-02 loghost01 media-01 metrics-store-01 perdulce static-master-fsn submit-01 tb-build-01 tb-build-03 tb-tester-01 tbb-nightlies-master web-chi-03 web-cymru-01 web-fsn-01 web-fsn-02 ``` 27 machines. At a worst case 45 minutes per machine, that is 20 hours of work. At three people, this might be doable in a day. Feedback and coordination of this batch happens in issue [tpo/tpa/team#40690][]. ### Moderate complexity, batch 2: May The second batch of "moderate complexity servers" happens in the first week of May. The main difference with the first batch is that the second batch regroups services mostly managed by service admins, who are given a longer heads up before the upgrades are done. ``` bacula-director-01 bungei carinatum check-01 crm-ext-01 crm-int-01 fallax gettor-01 gitlab-02 henryi majus mandos-01 materculae meronense neriniflorum nevii onionbalance-01 onionbalance-02 onionoo-backend-01 onionoo-backend-02 onionoo-frontend-01 onionoo-frontend-02 polyanthum rude staticiforme subnotabile ``` 26 machines. If the worst case scenario holds, this is another day of work, at three people. Not mentioned here is the `gnt-fsn` Ganeti cluster upgrade, which is covered by ticket [tpo/tpa/team#40689][]. That alone could be a few day-person of work. Feedback and coordination of this batch happens in issue [tpo/tpa/team#40692][] ### High complexity, individually done Those machines are harder to upgrade, due to some major upgrades of their core components, and will require individual attention, if not major work to upgrade. ``` alberti eugeni hetzner-hel1-01 pauli ``` Each machine could take a week or two to upgrade, depending on the situation and severity. To detail each server: * `alberti`: `userdir-ldap` is, in general, risky and needs special attention, but should be moderately safe to upgrade, see ticket [tpo/tpa/team#40693][] * `eugeni`: messy server, with lots of moving parts (e.g. Schleuder, Mailman), Mailman 2 EOL, needs to decide whether to migrate to Mailman 3 or replace with Discourse (and self-host), see [tpo/tpa/team#40471][], followup in [tpo/tpa/team#40694][] * `hetzner-hel1-01`: Nagios AKA Icinga 1 is end-of-life and needs to be migrated to Icinga 2, which involves fixing our git hooks to generate Icinga 2 configuration (unlikely), or rebuilding a Icinga 2 server, or replacing with Prometheus (see [tpo/tpa/team#29864][]), followup in [tpo/tpa/team#40695][] * `pauli`: Puppet packages are severely out of date in Debian, and Puppet 5 is EOL (with Puppet 6 soon to be). doesn't necessarily block the upgrade, but we should deal with this problem sooner than later, see [tpo/tpa/team#33588][], followup in [tpo/tpa/team#40696][] All of those require individual decision and design, and specific announcements will be made for upgrades once a decision has been made for each service. ### To retire Those servers are possibly scheduled for removal and may not be upgraded to bullseye at all. If we miss the summer deadline, they might be upgraded as a last resort. ``` cupani gayi moly peninsulare vineale ``` Specifically: * cupani/vineale is covered by [tpo/tpa/team#40472][] * gayi is [TPA-RFC-11: SVN retirement][], [tpo/tpa/team#17202][] * moly/peninsulare is [tpo/tpa/team#29974][] ### To rebuild Those machines are planned to be rebuilt and should therefore not be upgraded either: ``` cdn-backend-sunet-01 colchicifolium corsicum nutans ``` Some of those machines are hosted at a Sunet and need to be migrated elsewhere, see [tpo/tpa/team#40684][] for details. `colchicifolium` will is planned to be rebuilt in the `gnt-chi` cluster, no ticket created yet. They will be rebuilt in new bullseye machines which should allow for a safer transition that shouldn't require specific coordination or planning. ### Completed upgrades Those machines have already been upgraded to (or installed as) Debian 11 bullseye: ``` btcpayserver-02 chi-node-01 chi-node-02 chi-node-03 chi-node-04 chi-node-05 chi-node-06 chi-node-07 chi-node-08 chi-node-09 chi-node-10 chi-node-11 chi-node-14 ci-runner-x86-05 palmeri relay-01 static-gitlab-shim tb-pkgstage-01 ``` ### Other related work There is other work related to the bullseye upgrade that is mentioned in the [%Debian 11 bullseye upgrade milestone][]. # Alternatives considered We have not set aside time to automate the upgrade procedure any further at this stage, as this is considered to be a too risky development project, and the current procedure is fast enough for now. We could also move to the cloud, Kubernetes, serverless, and Ethereum and pretend none of those things exist, but so far we stay in the real world of operating systems. Also note that this doesn't cover Docker container images upgrades. Each team is responsible for upgrading their image tags in GitLab CI appropriately and is *strongly* encouraged to keep a close eye on those in general. We may eventually consider enforcing stricter control over container images if this proves to be too chaotic to self-manage. # Costs It is estimates this will take one or two person-month to complete, full time. # Approvals required This proposal needs approval from TPA team members, but service admins can request additional delay if they are worried about their service being affected by the upgrade. Comments or feedback can be provided in issues linked above. # Deadline Upgrades will start in the first week of April 2022 (2022-04-04) unless an objection is raised. This proposal will be considered adopted by then unless an objection is raised within TPA. # Status This proposal is currently in the `proposed` state. # References * [TPA bullseye upgrade procedure][] * [%Debian 11 bullseye upgrade milestone][] [TPA bullseye upgrade procedure]: https://gitlab.torproject.org/tpo/tpa/team/-/wikis/howto/upgrades/bullseye/ [%Debian 11 bullseye upgrade milestone]: https://gitlab.torproject.org/groups/tpo/tpa/-/milestones/5 [bullseye]: https://wiki.debian.org/DebianBullseye [released on August 14 2021]: https://www.debian.org/News/2021/20210814 [buster]: howto/upgrades/buster [one year after the stable release]: https://www.debian.org/security/faq#lifespan [OKR 2022 Q1/Q2 plan]: https://gitlab.torproject.org/tpo/tpa/team/-/wikis/roadmap/2022 [tpo/tpa/team#40690]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/40690 [tpo/tpa/team#40692]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/40692 [tpo/tpa/team#40693]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/40693 [tpo/tpa/team#40471]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/40471 [tpo/tpa/team#29864]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/29864 [tpo/tpa/team#33588]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/33588 [tpo/tpa/team#40684]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/40684 [tpo/tpa/team#40694]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/40694 [tpo/tpa/team#40695]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/40695 [tpo/tpa/team#40696]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/40696 [tpo/tpa/team#40472]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/40472 [tpo/tpa/team#17202]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/17202 [TPA-RFC-11: SVN retirement]: policy/tpa-rfc-11-svn-retirement [tpo/tpa/team#29974]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/29974 [tpo/tpa/team#40689]: https://gitlab.torproject.org/tpo/tpa/team/-/issues/40689 -- Antoine Beaupré torproject.org system administration

1 4

Anti-censorship team meeting notes, 2022-04-28
by Shelikhoo 28 Apr '22

28 Apr '22

Hey everyone! Here are our meeting logs: http://meetbot.debian.net/tor-meeting/2022/tor-meeting.2022-04-28-15.58.html And our meeting pad: Anti-censorship work meeting pad -------------------------------- Next meeting: Thursday May 5th 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 check-in 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: * Roadmap: https://gitlab.torproject.org/groups/tpo/anti-censorship/-/boards * The anti-censorship team's wiki page: * https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/home * Past meeting notes can be found at: * https://lists.torproject.org/pipermail/tor-project/ * Tickets that need reviews: from sponsors we are working on: * All needs review tickets: https://gitlab.torproject.org/groups/tpo/anti-censorship/-/merge_requests?s… * Sponsor 28 * must-do tickets: https://gitlab.torproject.org/groups/tpo/-/milestones/10 * possible tickets: https://gitlab.torproject.org/groups/tpo/-/issues?scope=all&utf8=%E2%9C%93&… * Sponsor 96 * https://gitlab.torproject.org/groups/tpo/-/milestones/24 == Announcements == * polyanthum & gettor-01 will be upgraded next week, the servers where bridgedb,rdsys,gettor and other anti-censorship infra is hosted == Discussion == * Distributed Snowflake Server Support * Any feedbacks? * https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… * No blocker issue discovered. * will first deploy the new broker, and give time for proxies to update * removed smallerRichard builtin server * https://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/44 * RKS hackathon * (Discussion Skipped) == Actions == * == Interesting links == * https://www.codastory.com/authoritarian-tech/kazakhstan-shut-down-its-inter… * https://eprint.iacr.org/2020/114 == Reading group == * We will discuss "Blocking of HTTP/3 (QUIC) in Russia" on Apr/28th/2022 * https://dl.acm.org/doi/abs/10.1145/3487552.3487836 * https://github.com/net4people/bbs/issues/108 * 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. anadahz: 2022-01-27 Last week: - Increase timeout check cycles for default-bridge-felix-1 and default-bridge-felix-2 as they have been generating too many alerts: https://gitlab.torproject.org/tpo/anti-censorship/monit-configuration/-/mer… cecylia (cohosh): last updated 2022-04-14 Last week: - moved tor-specific snowflake code out of client library (snowflake#40124) - merge request: snowflake!85 - bump version of webrtc dependency (snowflake#40127) - merge request: snowflake!86 - commented on snowflake web workflow (snowflake#40125) - opened issue to bump version of snowflake and webrtc in tor browser (tor-browser-build#40474) - work on conjure test environment setup This week: - continue work on conjure PT - continue snowflake maintenance tasks Needs help with: dcf: 2022-04-28 Last week: - made graphs of the snowflake bridge since the server move 2 weeks ago https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… Next week: - look at STATUS VERSION proposal https://gitlab.torproject.org/tpo/core/torspec/-/merge_requests/63 - set up access control on the snowflake-02 bridge https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… Help with: arlolra: 2022-04-07 Last week: - Merged the rest of snowflake !81 Next week: - Get to snowflake-webext #10 Evergreen: - Figure out where in pion/webrtc ALPN should be configured and used - Maybe add Chacha20Poly1305 to pion/dtls https://github.com/pion/dtls#planned-features https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… Help with: - maxb: 2021-09-23 Last week: - Worked on https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… re: utls for broker negotiation - Had conversation with someone about upstream utls http round tripper https://github.com/refraction-networking/utls/pull/74 - Too busy with work :/ Next week: - _Really_ want to get a PR for utls round tripper meskio: 2022-04-28 Last week: - use bridgestrap results to select what bridges to distribute (rdsys#96) - give rdsys a free software license (rdsys#107) - removed smallerRichard builtin bridge (team#44) - brainstorm on dnstt (trac#40001) Next week: - deploy telegram in rdsys (rdsys#101) - advance on the onionsproutsbot deployment Shelikhoo: 2022-04-28 Last Week: - [Merge Request Awaiting] Add SOCKS5 forward proxy support to snowflake (snowflake!64) - [Coding & Deployment] Proposal: Centralized Probe Result Collector (anti-censorship/team#54) - [Discussion] Centralized Probe Log Collection Ascension Request - [Discussion] Hosting Centralized Probe Log Collection Server on TPA managed VPS - [Discussion] Proposal: Support for Dynamic IP obfs4 bridges with unattended proxy information update(aka "Subscription") - [Coding] Distributed Snowflake Bridges - Broker - [Coding] Distributed Snowflake Bridges Testing Environment - Dockerlized - [Deployment] Distributed Snowflake Bridges Testing Broker Next Week: - [Coding] Distributed Snowflake Bridges (continue) - [Research] Implement metrics to measure snowflake churn(https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transport… - [Research] Blocking of Snowflake in Turkmenistan, 2021-10-24 Itchy Onion: 2022-04-28 Last week: - debugged a RACE 2.1.0 issue - had a meeting with Georgetown folks (a recurring meeting to go over each other's channel code) This week: - go over snowflake code (in preparation for the next Georgetown meeting and also help with rebase snowflake rebasing) - go over RACECAR docs HackerNCoder: 2021-12-16 This week: Last/done: Setup web mirror on tor.encryptionin.space Next: Get (new VPs with) new IP and setup new web mirror on new domain

1 0

The Tor Project's priorities for April - June 2022
by Gaba 26 Apr '22

26 Apr '22

Hi! For visibility in the broader community, I'm sending the priorities we have for 2022 and specific projects and tasks we are working on for this quarter. There are links where you can read more about the work that different teams at Tor are doing. If you want to read about long term strategic goals for the Tor project organization, you can go to this wiki page: https://gitlab.torproject.org/tpo/team#organization # The Tor Project Priorities 2022 The Tor network Make the Tor network faster for users Get Arti to production level Improve bad relay tooling Support researchers for network experiments Improve monitoring and alerting for metrics services. Maintain a healthy relay operators community Increase adoption of onion services Trainings and User Research in the global south Connect with censored users to improve censorship circumvention Research on Tor Browser new features and VPN concept Collaborate with other organizations in the Tor ecosystem New Tor's "VPN" client Design safety criteria Define MVP for client Build the network engine for VPN solution Evaluate orbot and leap components and architecture Start working on UI Tor Browser Implement feedback from users Improve automatic censorship detection during bootstrap Enable HTTPS-only mode Browser is under control (releases on schedule, automated tests pass) Censorship Circumvention Implement new pluggable transport: Conjure & HTTPT Scale Snowflake Deploy improved bridge distribution system Monitor bridge health Censorship analysis and response to it Infrastructure User support tools gets improved User support Documentation keep up to date Improve mail services Rebuild donate page Make it easier for translators to contribute # Tor's TEAMS PRIORITIES FOR Q2 ---------------------------------- ## Applications (Led by Richard. Board https://gitlab.torproject.org/groups/tpo/applications/-/boards?label_name[]…) Implement Tor Browser UX changes that UX team is prioritizing from user research and feedback. Improve automatic censorship detection during bootstrapping in Tor Browser (desktop and Android). Evaluate orbot and leap for components and architecture. Design VPN safety criteria. HTTPS everywhere replacement. Go/Rust/Java dependency resolution: how to resolve dependencies ahead of time. Browser: Browser is under control Android Tor Browser releases are on schedule Android/Linux Tor Browser Automated tests are passing Survey the Browser ecosystem Integration: Begin understanding application integration/embedding Begin helping Network Team create easy-to-use Arti API Document required components for Android app integration ## Community (Led by Gus. Board https://gitlab.torproject.org/groups/tpo/community/-/boards?label_name[]=Q2 and https://gitlab.torproject.org/groups/tpo/onion-services/-/boards?label_name…) - assist network health team to maintain a healthy relay operators community - assist anti-censorship team on connecting with censored users to improve censorship circumvention - improve user support tools and documentation - lead trainings with communities in latinoamerica and east africa - look for spikes in tor usage and document process and resources available for it. ## Network Health (Led by Geko. Board https://gitlab.torproject.org/groups/tpo/network-health/-/boards?label_name…) - s61 O2.1: Reduce the number of slow and extremely slow sessions for our users by developing and deploying load balancing improvements. - s61 O4.2: Find and fix performance-impacting issues and bugs discovered from monitoring and scanning. - Run bad-relay detection scripts - Bad-relay tooling improvements . - Fix any sbws critical issues that may come up - Support for researchers for network experiments - Consider tickets from other teams - Support OTF fellow on Relay Operators Community Health Research - Relay operator meetups. - Keep moderating and answering the tor-relays mailing list - Handle EOL relays - Support mentee from GSoC - Improve monitoring and alerting for metrics services. - Deploy a data store for metrics servicesn plan - Refactor sbws2 - Surprise 'anomaly analysis' on the network as needed - Think about metrics for the VPN client and their possible privacy issues/risks - Network anomaly detection: use current monitoring infrastructure to get some of the anomalies we can catch with it. # Network (Led by Alex. Board https://gitlab.torproject.org/groups/tpo/core/-/boards?label_name[]=Q2) - S30 2.3.3 - Improve ability for bridgedb/authority to test bridges that only expose a pluggable transport. - S30 2.4.5 - Increase stability and resilience of bridge authority and bridgeDB by exploring and implementing decentralization of those services. - S61 O1.1: Optimize user-facing performance by tuning parameters of previously deployed Tor network improvements. - S61 O2: sbws with congestion control (Tor support to pin exits/Sos Rends, or just wait). - S61 O3.2: Implement promising performance improvements from evaluation in O3.1. - S61 O4.1: Improve and implement network health monitoring and scanning. - S96 O3.5: Integrate Tor+Snowflake/obfs4 capabilities into mobile applications. - S96 O3.5.1 OnionShare, iOS. - S96 O3.5.2: OnionShare, Android. - S96 O3.5.3: Save (Share-Archive-Verify-Encrypt) by OpenArchive . - S101 O3.2: Enhance Tor to act as a VPN service, rather than an opt-in proxy as it does today. - S119 Arti 1.0.0 - Try to reach "production quality". # Anti-censorship (Lead by Meskio. Board https://gitlab.torproject.org/groups/tpo/anti-censorship/-/boards?label_nam…) - S30 O2.3.1 - Develop new and/or improve existing bridge selection and distribution strategies based on data collected about successful, effective methods per evaluation during O1.1. Conjure/Tapdance implementation - S96 O1.1.1 Prepare the Snowflake system for a surge in operators and users. - S96 O1.2: Increase the number of Snowflake bridges. - S96 O1.3: Implement bridges with pluggable transport HTTPT support. - S96 O1.4: Increase the number of active obfs4 and HTTPT bridges. - S96 O2.2: Deploy improved bridge distribution systems. - S96 Start Salmon based design - S96 O2.3: React and steer our response to censorship. - S96 O4.3: Modify GetTor so that it can distribute Tor Browser via messaging apps - S28 RACE project - S2125 Automatize bridge rotation for telegram. Continue translations of anti-censorship material into russian. # UX (Led by Duncan. Board https://gitlab.torproject.org/groups/tpo/-/boards?label_name[]=UX%20Team) Roadmap in https://www.figma.com/file/n4ETd0cUkcfj3KyclJQnt3/UX-Team-Planning?node-id=… # TPA (Led by Anarcat. Board https://gitlab.torproject.org/groups/tpo/tpa/-/boards ) Roadmap in https://gitlab.torproject.org/tpo/tpa/team/-/wikis/roadmap/2022 # WEB It is a collaboration between TPA and Community teams. Board https://gitlab.torproject.org/groups/tpo/web/-/boards cheers, gaba (Tor's project manager)

1 0

Community Team Meeting notes - April 25 2022
by gus 25 Apr '22

25 Apr '22

Hi, Here's the Community Team meeting logs: http://meetbot.debian.net/tor-meeting/2022/tor-meeting.2022-04-25-13.59.log… And our meeting pad: ## Tor Community Team meeting pad Next meeting: Monday, May 2, 2022 - 1400 UTC Weekly meetings, every Monday at 14:00 UTC, in #tor-meeting at OFTC (channel is logged while meetings are in progress) ## Goal of this meeting Weekly check-in about the status of Community Team work at Tor. ## Links to Useful documents * Previous meetings: https://forum.torproject.net/tag/community-team * Monthly l10n hangout: https://community.torproject.org/localization/hangouts/ * Known issues with Tor Browser: https://tb-manual.torproject.org/known-issues/ and Tor Browser for Android: https://tb-manual.torproject.org/mobile-tor/#known-issues ## Discussion * Workshop: Relay Operator SysAdmin 101 - https://gitlab.torproject.org/tpo/community/relays/-/issues/36 * Announcement - TB user manual alpha branch: https://gitlab.torproject.org/tpo/web/manual/-/tree/alpha * Community member is suggesting to create an "Education" category in Tor forum and a #tor-education channel on IRC (with Matrix bridge): https://gitlab.torproject.org/tpo/community/support/-/issues/40070 * Related forum post: https://forum.torproject.net/t/tor-in-education-discussion/911/10 ## Updates Name: Last week: - What you worked on last week. This week: - What you are you planning to work on this week. Help with: - Something you need help with. Gus: Last week: - Started the Alix Dunn course - Worked on Sponsor96 and Sponsor30 reports - Sent the Tor Latam meetup agenda to participants - 1:1s with the team - Updated the relay associations page: https://community.torproject.org/relay/community-resources/relay-associatio… - RT ticket triage with Joydeep and Nina - Digital security training with Raya and Tor staff This week: - S96 meeting - Tor Latam meetup - 1:1s with the team - Sponsor125 final report Joydeep: Last week: - RT Ticket triage with Nina and Gus - Planning pre-release documentation updates wrt TB 11.5: https://gitlab.torproject.org/tpo/web/manual/-/issues/119, https://gitlab.torproject.org/tpo/community/support/-/issues/40073, https://gitlab.torproject.org/tpo/web/support/-/issues/298 - user support work on RT, Forum, cdr.link and SM. - Sponsor125 report wrt user support activities This week: - 1:1 with Gus - sync with the UX team - Triage more of the backlog on RT emmapeel: Last week: - Onboarding new translator for rapid response russia. - i18n for the onion support landing page - transifex, repo work - strings review - deal with input form translators in transifex - update website translation files This week: - support new russian translator - onboard sponsor123 translators for landing page - documentation updates raya: Last week: - meeting with s123 stakeholders - 1:1 with gus - work on training page revamp: - https://gitlab.torproject.org/tpo/web/community/-/issues/265 - security training with gus and team This week: - s123 monthly report: - https://gitlab.torproject.org/tpo/onion-services/onion-support/-/issues/75 - meeting with s123 stakeholders - depends on priority, but work on some other to-do's: - https://gitlab.torproject.org/dashboard/issues?scope=all&state=opened&assig… - 1:1 with gus Help with: - rhatto: Last week: - 1:1 with Gus - S123 - Onionprobe testbed: https://gitlab.torproject.org/tpo/onion-services/onion-support/-/issues/59 - S123 - Released Onionprobe 0.3.0 - * https://gitlab.torproject.org/tpo/onion-services/onionprobe/-/tags/0.3.0 * https://pypi.org/project/onionprobe/0.3.0/ - S123 - Onionprobe Debian package: https://gitlab.torproject.org/tpo/onion-services/onionprobe/-/issues/4 This week: - S123 - Continue the Onionprobe testbed setup: https://gitlab.torproject.org/tpo/onion-services/onion-support/-/issues/59 - S123 - Work on new deployments Nina: Last week: - User support on RT and Cdr.link. - Collecting data for Sponsor 125 final report - RT Ticket triage with Gus and Joydeep This week: - User support. - 1:1 with Gus -- The Tor Project Community Team Lead

1 0

Network Team - Upcoming tor.git 0.4.7.7 release - April 2022
by David Goulet 25 Apr '22

25 Apr '22

Greetings, Network team will be releasing on Wednesday (April 27th, 2022) the first stable release of the 0.4.7.x series. Very little has changed from the previous release candidate so this should be a smooth transition into the stable. We'll of course keep a close eye on it due to its drastic new feature: congestion control Upcoming versions: - 0.4.7.7 @network-team: It is _now_ a good time to start reviewing changes/ files: https://gitlab.torproject.org/tpo/core/tor/-/tree/main/changes Last, we've asked the dirauth to recommend this version few minutes ago. Keep an eye out for the release announcement and a blog post about this new stable version. Cheers! David -- g0mNrchagnDtRyN1ttVfag8Txoz/EKIKjotiMPGc7ug=

1 0

Anti-censorship team meeting notes, 2022-04-21
by meskio 21 Apr '22

21 Apr '22

Hey everyone! Here are our meeting logs: http://meetbot.debian.net/tor-meeting/2022/tor-meeting.2022-04-21-15.59.html And our meeting pad: Anti-censorship work meeting pad -------------------------------- Next meeting: Thursday April 21th 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. == Links to Useful documents == * Our anti-censorship roadmap: * Roadmap: https://gitlab.torproject.org/groups/tpo/anti-censorship/-/boards * The anti-censorship team's wiki page: * https://gitlab.torproject.org/tpo/anti-censorship/team/-/wikis/home * Past meeting notes can be found at: * https://lists.torproject.org/pipermail/tor-project/ * Tickets that need reviews: from sponsors we are working on: * All needs review tickets: https://gitlab.torproject.org/groups/tpo/anti-censorship/-/merge_requests?s… * Sponsor 28 * must-do tickets: https://gitlab.torproject.org/groups/tpo/-/milestones/10 * possible tickets: https://gitlab.torproject.org/groups/tpo/-/issues?scope=all&utf8=%E2%9C%93&… * Sponsor 96 * https://gitlab.torproject.org/groups/tpo/-/milestones/24 == Announcements == * == Discussion == * Do we have graphs about telegram bridge usage * irl has some script to generate them * current telegram bridges are not pressent in metrics.tpo as 'distributor telegram', as they are manually feeded. This will change when we start using rdsys for it. * Is the reading group reading supposed to be "Web censorship measurements of HTTP/3 over QUIC" https://dl.acm.org/doi/abs/10.1145/3487552.3487836 ? * or the threads https://github.com/net4people/bbs/issues/108 https://ntc.party/t/http-3-quic/1823 ? * one of the authors of the paper, Kathrin Elmenhorst, has posted some more recent measurements of HTTP/3 blocking in Russia specifically https://github.com/kelmenhorst/quic-censorship/issues/4 * we'll read the paper, the threads are for more context * Snowflake Multi-Server Broker Testing (https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow…) * (this is where the client tells the broker&proxy what bridge it wants to use, by putting fingerprint=1234ABCD... on its Bridge line) * testing is wellcome... * there are instructions for testing it in the issue * Report of CDN Block in Turkmenistan(https://gitlab.torproject.org/tpo/anti-censorship/censorship-a… * cloudflare is being blocked in Turkmenistan * in Russia they are blocking 2 IPs of cloudflare too, but might be an error of overblocking targeting a single site https://ntc.party/t/cloudflare-cdn/2245/24 * shell will talk with fastly and cloudflare to see what they know, and we'll look into setting up a vantage point in TM * meskio, if you could give rdsys a free software license, i will breathe easier at night: https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/issues/107 * meskio will add 3-BSD in the comming days * dnstt, next steps * https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/trac… * the major blocker now is to have support for PT commands over the SOCKS connection * will require forking the code into tpo == Actions == * == Interesting links == * https://pluggabletransports.info/blog/pt-meetup-apr2022/ == Reading group == * We will discuss "Blocking of HTTP/3 (QUIC) in Russia" on Apr/28th/2022 * https://dl.acm.org/doi/abs/10.1145/3487552.3487836 * https://github.com/net4people/bbs/issues/108 * 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. anadahz: 2022-01-27 Last week: - Increase timeout check cycles for default-bridge-felix-1 and default-bridge-felix-2 as they have been generating too many alerts: https://gitlab.torproject.org/tpo/anti-censorship/monit-configuration/-/mer… cecylia (cohosh): last updated 2022-04-14 Last week: - moved tor-specific snowflake code out of client library (snowflake#40124) - merge request: snowflake!85 - bump version of webrtc dependency (snowflake#40127) - merge request: snowflake!86 - commented on snowflake web workflow (snowflake#40125) - opened issue to bump version of snowflake and webrtc in tor browser (tor-browser-build#40474) - work on conjure test environment setup This week: - continued work on conjure PT - continue snowflake maintenance tasks Needs help with: dcf: 2022-04-21 Last week: - investigated how Tor Metrics estimates the number of users and asked questions about it https://lists.torproject.org/pipermail/tor-dev/2022-April/014724.html https://gitlab.torproject.org/tpo/network-health/metrics/website/-/issues/4… - made a graph of Tor users in Russia across all transports https://gitlab.torproject.org/tpo/community/support/-/issues/40050#note_279… - wrote feedback on the Def Con submission draft - installed a second snowflake bridge https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… Next week: - look at STATUS VERSION proposal https://gitlab.torproject.org/tpo/core/torspec/-/merge_requests/63 Help with: agix: 2021-02-10 Last week: - Continued work on gettor-twitter Next week: - Hopefully finish the task Help with: - arlolra: 2022-04-07 Last week: - Merged the rest of snowflake !81 Next week: - Get to snowflake-webext #10 Evergreen: - Figure out where in pion/webrtc ALPN should be configured and used - Maybe add Chacha20Poly1305 to pion/dtls https://github.com/pion/dtls#planned-features https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… Help with: - maxb: 2021-09-23 Last week: - Worked on https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snow… re: utls for broker negotiation - Had conversation with someone about upstream utls http round tripper https://github.com/refraction-networking/utls/pull/74 - Too busy with work :/ Next week: - _Really_ want to get a PR for utls round tripper meskio: 2022-04-21 Last week: - deploy rdsys 0.2 with many fixes - update monit configuration to the new snowflake bridge (monit-configuration!2) - merge moat documentation into rdsys (rdsys!34) - catch up after a week off Next week: - use bridgestrap results to select what bridges to distribute (rdsys#96) - give rdsys a free software license (rdsys#107) Shelikhoo: 2022-04-21 Last Week: - [Merge Request Awaiting] Add SOCKS5 forward proxy support to snowflake (snowflake!64) - [Coding & Deployment] Proposal: Centralized Probe Result Collector (anti-censorship/team#54) - [Discussion] Centralized Probe Log Collection Ascension Request - [Discussion] Hosting Centralized Probe Log Collection Server on TPA managed VPS - [Discussion] Proposal: Support for Dynamic IP obfs4 bridges with unattended proxy information update(aka "Subscription") - [Discussion+Coding] Support Automatic Bridge Info update(shelikhoo/LogCollectorAncillary#1) - [Discussion+Coding] Remove Inactive Bridge from Test Result(shelikhoo/LogCollectorAncillary#2) - [Coding] Distributed Snowflake Bridges - Broker - [Coding] Distributed Snowflake Bridges Testing Environment - Dockerlized - [Deployment] Distributed Snowflake Bridges Testing Broker Next Week: - [Coding] Distributed Snowflake Bridges (continue) - [Research] Blocking of Snowflake in Turkmenistan, 2021-10-24 Itchy Onion: 2022-04-14 Last week: - worked on rebasing RACECAR snowflake but didn't finish (3 day week) - read RACECAR doc This week: - debugged a RACE 2.1.0 issue - read snowflake code -- there is going to be a recurring 1:1 meeting between me and Eliana from Georgetown to go over each other's channel code HackerNCoder: 2021-12-16 This week: Last/done: Setup web mirror on tor.encryptionin.space Next: Get (new VPs with) new IP and setup new web mirror on new domain 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: - -- meskio | https://meskio.net/ -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- My contact info: https://meskio.net/crypto.txt -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Nos vamos a Croatan.

1 0

UX team meeting notes, April 19th
by Duncan Russell 19 Apr '22

19 Apr '22

Hello, Thanks to everyone who made it to today's UX Team meeting too! We’re looking forward to seeing you all again in a week’s time. Here are the minutes: http://meetbot.debian.net/tor-meeting/2022/tor-meeting.2022-04-12-16.59.log… <http://meetbot.debian.net/tor-meeting/2022/tor-meeting.2022-04-12-16.59.log…> Today we discussed the timings of updating the Tor Browser user manual ahead of Tor Browser 11.5 release, which we’re planning on bundling into the browser. *** == User Experience Team Meeting == UX Team meetings happen every Tuesday at 1600 UTC in #tor-meeting on OFTC. Here are the logs from our meeting on April 12th: http://meetbot.debian.net/tor-meeting/2022/tor-meeting.2022-04-12-16.59.log… <http://meetbot.debian.net/tor-meeting/2022/tor-meeting.2022-04-12-16.59.log…> == Useful links == About the UX Team: https://gitlab.torproject.org/tpo/ux/team <https://gitlab.torproject.org/tpo/ux/team> UX repository: https://gitlab.torproject.org/tpo/ux <https://gitlab.torproject.org/tpo/ux> UX roadmap: https://www.figma.com/file/n4ETd0cUkcfj3KyclJQnt3/UX-Team-Planning?node-id=… <https://www.figma.com/file/n4ETd0cUkcfj3KyclJQnt3/UX-Team-Planning?node-id=…> UX kanban: https://gitlab.torproject.org/groups/tpo/-/boards?scope=all&utf8=%E2%9C%93&… <https://gitlab.torproject.org/groups/tpo/-/boards?scope=all&utf8=%E2%9C%93&…> Team kanban: https://gitlab.torproject.org/groups/tpo/-/boards?scope=all&label_name[]=UX… <https://gitlab.torproject.org/groups/tpo/-/boards?scope=all&label_name[]=UX…> == Meetbot commands == - #startmeeting UX Team Weekly Meeting - #endmeeting --------------------------- Tuesday April 19th @ 16:00 UTC --------------------------- == What projects are we working on? == S9 - Usability and Community Intervention on Support for Democracy and Human Rights https://gitlab.torproject.org/groups/tpo/-/issues?scope=all&utf8=%E2%9C%93&… <https://gitlab.torproject.org/groups/tpo/-/issues?scope=all&utf8=%E2%9C%93&…> S30 - Empowering Communities in the Global South to Bypass Censorship https://gitlab.torproject.org/groups/tpo/-/issues?scope=all&utf8=%E2%9C%93&… <https://gitlab.torproject.org/groups/tpo/-/issues?scope=all&utf8=%E2%9C%93&…> S96 – Rapid Expansion of Access to the Uncensored Internet through Tor in China, Hong Kong, & Tibet https://gitlab.torproject.org/groups/tpo/-/milestones/24 <https://gitlab.torproject.org/groups/tpo/-/milestones/24> S101 - Tor VPN Client for Android https://gitlab.torproject.org/groups/tpo/-/milestones/32 <https://gitlab.torproject.org/groups/tpo/-/milestones/32> S123 - Tor Secure Access Package for USAGM https://gitlab.torproject.org/groups/tpo/-/milestones/34 <https://gitlab.torproject.org/groups/tpo/-/milestones/34> == Announcements == Nothing this week! == Agenda == Evergreen items: 1. Announcements 📣 2. Weekly planning 📅 3. Check-in with user support 💬 Discussion items for this week only: 4. Update Tor Browser User Manual with TB 11.5 release - related tickets: https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/11698 <https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/11698> - tb-manual.tpo: https://gitlab.torproject.org/tpo/web/manual/-/issues/119 <https://gitlab.torproject.org/tpo/web/manual/-/issues/119> - support.tpo: https://gitlab.torproject.org/tpo/web/support/-/issues/298 <https://gitlab.torproject.org/tpo/web/support/-/issues/298> - user support channels: https://gitlab.torproject.org/tpo/community/support/-/issues/40073 <https://gitlab.torproject.org/tpo/community/support/-/issues/40073> - localization: https://gitlab.torproject.org/tpo/community/l10n/-/issues/40068 <https://gitlab.torproject.org/tpo/community/l10n/-/issues/40068> Championquizzer: i'd also stress that we will have to keep a good time margin for l10n Richard: we should hash out some details in the release meeting re how this is actually getting integrated into tor-browser and the build system Deadline for changes to make the bundling: TBC, donuts will discuss with applications in our next release meeting == Weekly planning == Note: Please highlight anything you'd like to discuss below in **bold** duncan/donuts Last week (actual): - Split the newest designs in tor-browser#40773 into new tickets for implementation - Tested new connection features in 11.5a9 and posted feedback in applications/tor-browser#40887 - Began working on the next steps for tor-qa in applications/team#6 - Quarterly reports for funders This week (planned): - Combine, dedupe and finalize the two bridge-moji shortlists in applications/tor-browser#40860 - Add Tor Browser to the Internews UX Forum website - Design mockup for the bundled tb-manual in applications/tor-browser#40885 - Produce outline for tor-qa recruitment campaign in applications/team#6 - Start thinking about social previews/teasers for Tor Browser 11.5 - Maybe look at Snowflake landing page redesign in pluggable-transports/snowflake#40125 - Catch up on O1 activities for S101 - More quarterly reports for funders Nah Last week (actual): - gave a quick reading to s9 ToR - started analysing s30 feedback (start with spanish): https://gitlab.torproject.org/tpo/ux/research/-/issues/79 <https://gitlab.torproject.org/tpo/ux/research/-/issues/79> - reviewed s9 follow up, and sent compensation to s9 interviewees - transcribed and translated most of s9 interviews: https://gitlab.torproject.org/tpo/ux/research/-/issues/77 <https://gitlab.torproject.org/tpo/ux/research/-/issues/77> - did more s30 usability testing (mex) and br (two of them today) - transcribed and translated usability testing from mexico - attended "Obfuscated VPN: Lessons Learned and Future Work" - afk on Monday This week (planned): - meet and review s9 ToR today - transcribe and translate today's usability testing (s30) - schedule more 2 usability testing for connect assist - final analysis for these usability testing ^ - review s30 report - translate orbot's usability testing and survey (from portuguese to EN) - finish survey analysis (s30) - prepare s9 presentation for latam tor meetup - schedule meeting with sweetcurator to review script interview - catch up on s101 Need help: review card sorting survey based on job stories (s101) Near future: hope to start scheduling s101 interviewees mid-next-week with sweetcurator Nicob Last week (actual): - afk most of thurs + fri - USAGM:QA with Kez - Revise donate page header images - Revise monoprint onion sticker design - Dropping in content for Annual Report, beginning layout and design This week (planned): - USAGM: Design QA with kez - Annual report: Continue dropping in content as it becomes available; continue layout and design, plan graphics and illustrations - Artwork for Network Health blog post - Update outreach material with v3 onion address Joydeep Check-in with user support: - few more reports of TBA 11.0.8 crashing on launch (https://gitlab.torproject.org/tpo/applications/fenix/-/issues/40212 <https://gitlab.torproject.org/tpo/applications/fenix/-/issues/40212>) == Open Call for User Research == Find out how to contribute to the UX team: https://community.torproject.org/user-research/how-to-volunteer/ <https://community.torproject.org/user-research/how-to-volunteer/> Thanks everyone! *** Duncan Larsen-Russell Product Manager & UX Team Lead duncan(a)torproject.org <mailto:duncan@torproject.org>

1 0

UX team meeting notes, April 12th
by Duncan Russell 19 Apr '22

19 Apr '22

Hello, Thanks to everyone who made it to last week's UX Team meeting! Here are the minutes: http://meetbot.debian.net/tor-meeting/2022/tor-meeting.2022-0 <http://meetbot.debian.net/tor-meeting/2022/tor-meeting.2022-04-12-16.59.log…>4-1 <http://meetbot.debian.net/tor-meeting/2022/tor-meeting.2022-04-12-16.59.log…>2-16.59.log.html <http://meetbot.debian.net/tor-meeting/2022/tor-meeting.2022-04-12-16.59.log…> Note: Starting today, UX Team meetings will be happening 1 hour earlier at a new time of 1600 UTC. *** == User Experience Team Meeting == UX Team meetings happen every Tuesday at 1600 UTC in #tor-meeting on OFTC. Here are the logs from our meeting on April 12th: http://meetbot.debian.net/tor-meeting/2022/tor-meeting.2022-0 <http://meetbot.debian.net/tor-meeting/2022/tor-meeting.2022-04-12-16.59.log…>4-1 <http://meetbot.debian.net/tor-meeting/2022/tor-meeting.2022-04-12-16.59.log…>2-16.59.log.html <http://meetbot.debian.net/tor-meeting/2022/tor-meeting.2022-04-12-16.59.log…> == Useful links == About the UX Team: https://gitlab.torproject.org/tpo/ux/team <https://gitlab.torproject.org/tpo/ux/team> UX repository: https://gitlab.torproject.org/tpo/ux <https://gitlab.torproject.org/tpo/ux> UX roadmap: https://www.figma.com/file/n4ETd0cUkcfj3KyclJQnt3/UX-Team-Planning?node-id=… <https://www.figma.com/file/n4ETd0cUkcfj3KyclJQnt3/UX-Team-Planning?node-id=…> UX kanban: https://gitlab.torproject.org/groups/tpo/-/boards?scope=all&utf8=%E2%9C%93&… <https://gitlab.torproject.org/groups/tpo/-/boards?scope=all&utf8=%E2%9C%93&…> Team kanban: https://gitlab.torproject.org/groups/tpo/-/boards?scope=all&label_name[]=UX… <https://gitlab.torproject.org/groups/tpo/-/boards?scope=all&label_name[]=UX…> == Meetbot commands == #startmeeting UX Team Weekly Meeting #endmeeting --------------------------- Tuesday April 12th @ 17:00 UTC --------------------------- == What projects are we working on? == S9 - Usability and Community Intervention on Support for Democracy and Human Rights https://gitlab.torproject.org/groups/tpo/-/issues?scope=all&utf8=%E2%9C%93&… <https://gitlab.torproject.org/groups/tpo/-/issues?scope=all&utf8=%E2%9C%93&…> S30 - Empowering Communities in the Global South to Bypass Censorship https://gitlab.torproject.org/groups/tpo/-/issues?scope=all&utf8=%E2%9C%93&… <https://gitlab.torproject.org/groups/tpo/-/issues?scope=all&utf8=%E2%9C%93&…> S96 – Rapid Expansion of Access to the Uncensored Internet through Tor in China, Hong Kong, & Tibet https://gitlab.torproject.org/groups/tpo/-/milestones/24 <https://gitlab.torproject.org/groups/tpo/-/milestones/24> S101 - Tor VPN Client for Android https://gitlab.torproject.org/groups/tpo/-/milestones/32 <https://gitlab.torproject.org/groups/tpo/-/milestones/32> S123 - Tor Secure Access Package for USAGM https://gitlab.torproject.org/groups/tpo/-/milestones/34 <https://gitlab.torproject.org/groups/tpo/-/milestones/34> == Announcements == New meeting time starting next week: 1600 UTC New Release: Tor Browser 11.0.10 (Windows, macOS, Linux) https://blog.torproject.org/new-release-tor-browser-11010/ <https://blog.torproject.org/new-release-tor-browser-11010/> == Agenda == Evergreen items: 1. Announcements 📣 2. Weekly planning 📅 3. Check-in with user support 💬 == Weekly planning == Note: Please highlight anything you'd like to discuss below in **bold** duncan/donuts Last week (actual): - Reviewed and updated the team kanban with gaba - Read and reviewed first transcript from current round of S30 usability testing - Posted new iteration of torconnect designs in applications/tor-browser#40781 - Continued design-QA of torconnect in applications/tor-browser#40773 - Closed the tor-qa survey and posted results in ux/research#67 This week (planned): - Combine, dedupe and finalize the two bridge-moji shortlists in tor-browser#40860 - Create new tickets for buildable elements of tor-browser#40773 - Test new connection features in 11.5a8 and post feedback - Start to consider the next steps for tor-qa in applications/team#6 - Maybe design mockup for the bundled tb-manual in applications/tor-browser#40885 - Quarterly reports for funders ^ Half of this will spillover to next week Nah Last week (actual): - sent compensation to s9 interviewees (need to send more!) - send t-shirts to s30 testing volunteers (check with gus) - did one usability testing and interview sessions for s30 - scheduled usability testing and interview sessions (mexico) - training and collecting feedback on tuesday evening - training and collecting feedback on saturday morning - transcribed and translated s30 usability testing (portuguese) - did more 2 s9 interviews (spanish) This week (planned): - review s9 ToR - start analysing s30 feedback (start with spanish): https://gitlab.torproject.org/tpo/ux/research/-/issues/79 <https://gitlab.torproject.org/tpo/ux/research/-/issues/79> - last s30 training (cycle of training) today! - review s9 follow up, and send compensation to s9 interviewees - transcribe and translate s9 interviews: https://gitlab.torproject.org/tpo/ux/research/-/issues/77 <https://gitlab.torproject.org/tpo/ux/research/-/issues/77> - schedule s30 usability testing (mex) - more s30 usability testing (mex and br): https://gitlab.torproject.org/tpo/ux/research/-/issues/78 <https://gitlab.torproject.org/tpo/ux/research/-/issues/78> - check feedback on the VPN interview script - attending to "Obfuscated VPN: Lessons Learned and Future Work" need help: review card sorting survey based on job stories (s101) near future: hope to start scheduling s101 interviewees mid-next-week with sweetcurator Nicob Last week (actual): - afk 1/2 day friday - USAGM - RTL screens - Responsive screens (tablet, mobile) for LTR and RTL - Component states - Expanded screens - Started design QA with Kez This week (planned): - USAGM - Design QA with kez - S123 meeting - Annual report - Begin dropping in content from Al - Exploring layout design - Identify + brainstorm illustrations/graphics/components to be developed Imauri This week: - Awaiting schedule for upcoming VPN study interviews (s101) Last week: - Reviewed interview script for VPN study (s101) Joydeep ref. Check-in with User Support - user support report for March 2022 https://lists.torproject.org/pipermail/tor-project/2022-April/003338.html <https://lists.torproject.org/pipermail/tor-project/2022-April/003338.html> == Open Call for User Research == Find out how to contribute to the UX team: https://community.torproject.org/user-research/how-to-volunteer/ <https://community.torproject.org/user-research/how-to-volunteer/> Thanks everyone! *** Duncan Larsen-Russell Product Manager & UX Team Lead duncan(a)torproject.org <mailto:duncan@torproject.org>

1 0

Community Team meeting notes - April 18 2022
by gus 18 Apr '22

18 Apr '22

Hi, Here's the Community Team meeting logs: http://meetbot.debian.net/tor-meeting/2022/tor-meeting.2022-04-18-13.59.log… And our meeting pad: ## Tor Community Team meeting pad Next meeting: Monday, April 25, 2022 - 1400 UTC Weekly meetings, every Monday at 14:00 UTC, in #tor-meeting at OFTC (channel is logged while meetings are in progress) ## Goal of this meeting Weekly check-in about the status of Community Team work at Tor. ## Links to Useful documents * Previous meetings: https://forum.torproject.net/tag/community-team * Monthly l10n hangout: * https://community.torproject.org/localization/hangouts/ * Known issues with Tor Browser: * https://tb-manual.torproject.org/known-issues/ and Tor Browser for Android: https://tb-manual.torproject.org/mobile-tor/#known-issues ## Discussion * Tor Browser 11.5 release: * Alpha testers recruitment: * https://gitlab.torproject.org/tpo/applications/team/-/issues/6 - we can ask questions on #tor-browser-dev new channel. - Ask Russian users to report back on the telegram channel (@TorProjectSupportBot) Features: - connect:assist - it will be available this week on TB Alpha - https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues?scope=a… - Connection test - HTTPS-Only Mode (about:preferences#privacy) - New bridges configuration page - Bridges emoji identification and QRcode User docs tickets: * Alpha branch: https://gitlab.torproject.org/tpo/web/manual/-/issues/120 * TB-Manual: https://gitlab.torproject.org/tpo/web/manual/-/issues/119 * Support portal: https://gitlab.torproject.org/tpo/web/support/-/issues/298 * Localization: https://gitlab.torproject.org/tpo/community/l10n/-/issues/40068 * TB tickets: https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/40885 and https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/11698 * Support portal UX improvements: https://gitlab.torproject.org/tpo/web/support/-/issues/284 Next week (April 25): * Community member suggesting to create an "Education" category in Tor forum and a #tor-education channel on IRC (with Matrix bridge): https://gitlab.torproject.org/tpo/community/support/-/issues/40070 Related forum post: https://forum.torproject.net/t/tor-in-education-discussion/911/10 ## Updates Gus: This week: - Team 1:1s - Working with Network Health team to publish Expectations for Relay Operators v1 document - https://gitlab.torproject.org/tpo/community/relays/-/issues/18 - RT ticket triage with Joydeep and Nina (Friday, 22 13UTC) - Facilitation workshop Jumpstart with Alix Dunn - S9 - LATAM Meetup prep - S30 meeting - Working on S30 and S96 reports - Setting up a training time with Nicob and Melissa (cc Raya). - Working on the new training page with Raya: https://gitlab.torproject.org/tpo/web/community/-/issues/265 Joydeep: Last week: - Brainstorming more ideas for removing trusted contributors from the moderation queue on the forum: https://gitlab.torproject.org/tpo/community/support/-/issues/40060#note_279… https://meta.discourse.org/t/giving-certain-users-permission-to-post-withou… - User support activities on RT, cdr.link, IRC and Forum. This week: - RT Ticket triage with Gus and Nina. - Testing TB nightly and alpha builds. (related to https://gitlab.torproject.org/tpo/applications/team/-/issues/6, https://gitlab.torproject.org/tpo/web/manual/-/issues/119, https://gitlab.torproject.org/tpo/web/support/-/issues/298 and https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/11698) Nina: Last week: - User support on cdr.link and RT. - 1:1 meeting with Gus This week: - RT Ticket triage with Gus and Joydeep. - Wrap-up with contact -- The Tor Project Community Team Lead

1 0