Hey everyone!
Here are our meeting logs:
And our meeting pad:
Anti-censorship work meeting pad
···
--------------------------------
Anti-censorship
--------------------------------
Next meeting: Thursday, March 12 16:00 UTC
Facilitator:meskio
^^^(See Facilitator Queue at tail)
Weekly meetings, every Thursday at 16:00 UTC, in #tor-meeting at OFTC
(channel is logged while meetings are in progress)
This week's Facilitator: shelikhoo
== 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 the Tor Project and Tor community.
== Links to Useful documents ==
* Our anti-censorship roadmap:
* Roadmap:Issue Boards · Issues by Assignee · Boards · Anti-censorship · GitLab
* The anti-censorship team's wiki page:
* Home · Wiki · The Tor Project / Anti-censorship / Team · GitLab
* Past meeting notes can be found at:
* The tor-project Archives
* Tickets that need reviews: from projects, we are working on:
* All needs review tickets:
* Merge requests · Anti-censorship · GitLab
* Project 158 <-- meskio working on it
* Issues · Anti-censorship · GitLab
== Announcements ==
== Discussion ==
* Should we priorize better matching logic on snowflake broker
* Add three NAT type buckets to the snowflake broker (#40077) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab
* See also: RFC 5780 - NAT Behavior Discovery Using Session Traversal Utilities for NAT (STUN)
* [Option C] Fix it soon
* proposal to get a separate domain name for bridge reachability tests
* add a record for each known *.torproject.net bridge
* Proxies should not poll if they cannot reach a bridge (#40504) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab
== Actions ==
\*
== Interesting links ==
== 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?
\* Next in the Reading Group Queue:
\*
== 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): 2026-03-05
Last week:
- wrote a patch for go 1.22 support (snowflake#40490)
- worked on proxy bridge reachability checks (snowflake#40504)
- opened issue with TPA to get a bridge probe domain with multiple A records
- tried out mobile snowflake proxy app by contributor
- GitHub - blocoio/snowflake · GitHub
- caught up on IPtProxy issue about snowflake proxy events
- Support for remaining SnowflakeEvents · Issue #81 · tladesignz/IPtProxy · GitHub
- created issue to disable summary stats task if duration is 0 (snowflake#40524)
- implemented fix (snowflake!687)
- wrote script to parse OONI stun reachability check results (snowflake#40523)
- OONI STUN reachability check ($240) · Snippets · GitLab
- updated circumvention settings in rdsys (rdsys-admin!46)
- more work on proxy fairness proposal
Next week:
- finish working on snowflake compatability with go1.22
- research snowflake enumeration attacks (snowflake#40396)
- implement proxy fairness proposal
- follow up on snowflake rendezvous failures (snowflake#40447)
- revisit conjure integration with lyrebird
- take a look at potential snowflake orbot bug
- [BUG] 20% CPU overhead in kindness mode · Issue #1183 · guardianproject/orbot-android · GitHub
dcf: 2026-03-05
Last week:
- reviewed on a "??" geoip fix in snowflake proxy https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/snowflake/-/merge_requests/674
- made an issue for OS upgrade on snowflake-02, necessary before being able to updgrade tor Upgrade OS on snowflake-02 (#40522) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab
- wrote up a research idea for using rateless erasure codes for rendezvous Research ideas · Wiki · The Tor Project / Anti-censorship / Team · GitLab
- posted a short tutorial on using ooni-sync to download OONI measurements Some of our default STUN servers blocked in CN and RU (#40523) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab
- reviewed an MR to enable disable stats reporting in the snowflake standalone proxy Disable periodic proxy stats if SummaryInterval is 0 (!687) · Merge requests · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab
Next week:
- upgrade OS on the snowflake-02 bridge Upgrade OS on snowflake-02 (#40522) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab
- open issue to have snowflake-client log whenever KCPInErrors is nonzero Deploy snowflake-server for QueuePacketConn buffer reuse fix (#40260) (#40262) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab
- parent: Improve bug discovery process (#40267) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab
Help with:
meskio: 2026-03-05
Last week:
- grant writting
Next week:
- no webtunnel bridges in the https distributor (rdsys#262)
Shelikhoo: 2026-03-05
Last Week:
- [Testing] Unreliable+unordered WebRTC data channel transport for Snowflake rev2 (cont.)( Draft: Unreliable+unordered WebRTC data channel transport for Snowflake rev2 (!315) · Merge requests · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab ) testing environment setup/research
- Merge request Reviews
- Vantage point maintaince
- Expore DNS tunneling options(https://gitlab.torproject.org/tpo/anti-censorship/team/-/issues/173)
- [Research] proxy pool overload and potential blocking in Iran ( Add three NAT type buckets to the snowflake broker (#40077) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab )
- [Research] Add three NAT type buckets to the snowflake broker ( Add three NAT type buckets to the snowflake broker (#40077) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab )
Next (working) Week/TODO:
- Merge request reviews
- [Deployment]Unreliable+unordered WebRTC data channel transport for Snowflake rev2 (cont.)( Draft: Unreliable+unordered WebRTC data channel transport for Snowflake rev2 (!315) · Merge requests · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab ) Building custom Tor Browser with patch applied
- Vantage point maintaince
- [Research] proxy pool overload and potential blocking in Iran ( Add three NAT type buckets to the snowflake broker (#40077) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab )
- [Research] Add three NAT type buckets to the snowflake broker ( Add three NAT type buckets to the snowflake broker (#40077) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab )
onyinyang: 2026-02-26
Last week(s):
- attended FOCI
- Working on https distributor language selector HTTPS distributor is missing a language selector menu (#196) · Issues · The Tor Project / Anti-censorship / rdsys · GitLab
Next week:
- Away until March 18
- Continue work on rdsys#196
- Continue Investigating rdsys#248 i.e., why dysfunctional webtunnel bridges are being distributed
- Troubleshooting conjure not connecting in China
- waiting for more information from conjure authors/maintainers
Switch back to some of these:
As time allows:
\- Lox still seems to be filling up the disk on the rdsys\-test server despite changes made to delete old entries, look into what's going wrong
Blog post for conjure: https://gitlab.torproject.org/tpo/anti-censorship/pluggable-transports/conjure/-/issues/46
\- review Tor browser Lox integration https://gitlab.torproject.org/tpo/applications/tor-browser/-/merge_requests/1300
\- add TTL cache to lox MR for duplicate responses:
\- Work on outstanding milestone issues:
\- key rotation automation
Later:
pending decision on abandoning lox wasm in favour of some kind of FFI? https://gitlab.torproject.org/tpo/applications/tor-browser/-/issues/43096):
\- add pref to handle timing for pubkey checks in Tor browser
\- add trusted invitation logic to tor browser integration:
- improve metrics collection/think about how to show Lox is working/valuable
- sketch out Lox blog post/usage notes for forum
\(long term things were discussed at the meeting\!\):
\- brainstorming grouping strategies for Lox buckets \(of bridges\) and gathering context on how types of bridges are distributed/use in practice
Question: What makes a bridge usable for a given user, and how can we encode that to best ensure we're getting the most appropriate resources to people?
1\. Are there some obvious grouping strategies that we can already consider?
e\.g\., by PT, by bandwidth \(lower bandwidth bridges sacrificed to open\-invitation buckets?\), by locale \(to be matched with a requesting user's geoip or something?\)
2\. Does it make sense to group 3 bridges/bucket, so trusted users have access to 3 bridges \(and untrusted users have access to 1\)? More? Less?
theodorsm: 2026-02-19
Last weeks:
- Bumping pion stack version with backport: Sign in · GitLab
- Implementing DTLS 1.3 in pion
Next weeks:
- Implementing DTLS 1.3 in pion
Help with:
-
Facilitator Queue:
cohosh onyinyang shelikhoo meskio
1. First available staff in the Facilitator Queue will be the facilitator for the meeting
2. After facilitating the meeting, the facilitator will be moved to the tail of the queue