T

Team

Meta for projects management and general information in the wiki.

About us

Welcome to the anti-censorship team page. The anti-censorship team is a group of people who make Tor reachable anywhere in the world. We analyze censorship attempts and develop technology to work around these censorship attempts. One of the reasons we are not listing the names of the team members here is because we want to keep the team open to everyone. You're on the team if you're participating in discussions and development.

Excited about joining the team? Here is more information on how to get started.

IRC meetings schedule

We use ​IRC for our weekly meetings and we meet on the ​OFTC network in the #tor-meeting channel. The meeting takes place each Thursday at 16:00 UTC and typically lasts for an hour. ​This page can tell you what time this is in your part of the world. Sometimes, we have to cancel our meeting but we announce cancellations on our ​mailing list. Besides, our ​meeting pad always shows the date of the next meeting.

If you want to get involved in Tor's anti-censorship work, try to show up to the team meeting! To get an idea of what we discuss in our meetings, take a look at our ​meeting pad. In a nutshell, we use our weekly meetings to:

  • Make announcements to the team.
  • Discuss topics like our development roadmap, team processes, or code architecture.
  • Ask for help with whatever we're working on.
  • Coordinate code review.

People on the anti-censorship team use the pad to keep track of what they did the past week, what they plan to do next week, and what they need help with. If you missed a meeting, fret not! We post log files of our meetings on the ​tor-project mailing list, typically with the string "Anti-censorship meeting notes" in the email's subject line.

We use the string "anti-censorship-team" on IRC to reach all team members, e.g. "anti-censorship-team: take a look at bug #1234". Be sure to configure a highlight in your IRC client for this string.

Mailing list

For asynchronous communication, we use our ​anti-censorship-team mailing list. The list is ​publicly archived and available for anyone to sign up, so feel free to participate! Among other things, we use this mailing list to coordinate meetings, send announcements, and discuss all matters related to the anti-censorship team. Note that for development-related topics, we use the ​tor-dev mailing list.

Roadmapping goals

The following are our goals for 2021:

  • Improve reputation based bridge distribution (e.g. Salmon)
  • Better bridge distribution strategies (e.g. Conjure, Salmon)
    1. conjure first priority <---
    2. salmon second priority Task 4.1 Let's build a plan for how we're going to start the Salmon research work (Task 4).
  • Make GetTor more reliable and reduce maintenance burden <--- Rewrite gettor in Go to include it in rdsys <-- Evaluate if it makes sense to integrate The hard part of keeping gettor working in the past has been keeping all the files we distribute up-to-date. So let's not forget that part. :)
  • Complete integration of bridgedb into the more general rdsys <--- Integrating, not replacing bridgedb.
  • Improve the performance of Snowflake for users in Asia The destination we want is that users use multiple Snowflakes and it helps
  • Snowflake network health -- have enough of the right snowflakes, have volunteers happy Provide more feedback to users that run Snowflake proxies
  • Tor reachability from various countries Task 1.1 Automated scans to create a reachability dataset Task 1.1 Baselines before the blocking event -- get people used to running the tools and sending us the outputs. Maybe work with UX team to streamline this process, identify usability gaps in the tools.

The following were our goals for 2020:

  • We want to have more comprehensive BridgeDB metrics.
  • We will improve BridgeDB's broken CAPTCHA system.
  • We will monitor all critical components of the team's infrastructure.
  • Re-engineer GetTor to use multiple distributors (in addition to email)
  • We want to have accurate and safely-collected statistics of GetTor use.
  • Snowflake should allow clients to start browsing quickly and with reasonable bandwidth
  • We have happy Snowflake proxy volunteers that remain active.
  • We have a good understanding of censorship events and performance of snowflake in different countries.
  • Build feedback loop between BridgeDB and OONI.
  • Experiment with a modular BridgeDB architecture.

You can follow up our roadmap in this kanban board.

Active Sponsors and Contracts

Projects that the team maintains

Becoming a volunteer

Thanks for volunteering with us! There are many things that we need your help with:

  • Do you think that Tor (or one of its pluggable transports) is blocked in your country or network? Let us know!
  • Do you know how to code? Come help us improve one of our software projects! See below for more details.
  • We maintain lots of documentation which regularly needs updates and new content.
  • Do you have a background in UX? We maintain user-facing software whose user experience matters to us.

The best way to get involved is to visit our weekly IRC meeting (see above). Tell us your background and interests and we will find a project for your to get started.

Archive

https://trac.torproject.org/projects/tor/wiki/org/teams/AntiCensorshipTeam