Hey everyone!
Here are our meeting logs:
And our meeting pad:
Anti-censorship
···
--------------------------------
Next meeting: Thursday, February 19 16:00 UTC
Facilitator: cohosh
^^^(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:meskio
== 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 ==
* Go version bump to v1.24 for snowflake?
* we are keeping support for go 1.22 because TB needs this version to support an old version of OSX
* Draft: Update pion stack with security fix and performance increase (!662) · Merge requests · The Tor Project / Anti-censorship / Pluggable Transports / Snowflake · GitLab
== Actions ==
*
== Interesting links ==
* Cf. [Iran] unrest 2025-2026 (#40068) · Issues · The Tor Project / Anti-censorship / censorship-analysis · GitLab
* FOCI 2026 Winter: February 19th 17:00 - 21:30 UTC (after this meeting)
* https://foci.community/
* Snowflake Stats - Alexander Hansen Færøy's Homepage
* Alexander Hansen Færøy: "Wrote a simple stats parser and visualizer for th…" - Mastodon
* looking into kindling (GitHub - getlantern/kindling: Library using a series of techniques to send and receive small amounts of data through censoring firewalls) I found out they use snowflake's amp cache implementation importing snowflake directly from GitHub - getlantern/amp: AMP cache 
* 2026 January update - Open Collective
== 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-02-12
Last week:
- fixup snowflake message library refactor (snowflake!658)
- snowflake broker proxy pool refactor (snowflake!663)
- fix android CI test failures (snowflake!664)
- worked more on simulations for proxy fairness proposal (snowflake#40507)
Next week:
- 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-02-05
Last week:
- commented on some bootstrapping reports from Iran [Iran] unrest 2025-2026 (#40068) · Issues · The Tor Project / Anti-censorship / censorship-analysis · GitLab
Next week:
- 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-02-12
Last week:
- Investigate lyrebird crash in TorBrowser (tor-browser#44624)
- look into the status of builtin bridges
- grants grants...
Next week:
- investigate why there is webtunnel bridges in the email distributor (rdsys#174)
Shelikhoo: 2026-02-12
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(Expore DNS tunneling options (#173) · Issues · The Tor Project / Anti-censorship / Team · 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
- MR Review
- Design experment for internet shutdown
- Vantage point maintaince
- Expore DNS tunneling options(Expore DNS tunneling options (#173) · Issues · The Tor Project / Anti-censorship / Team · GitLab)
onyinyang: 2026-02-12
Last week(s):
-Completed first attempt at making it harder to inject a bridge to a specific client https://gitlab.torproject.org/tpo/anti-censorship/rdsys/-/issues/257#note_3322645
- Use root key for rdsys to derive keys for each of the distributors
- Working on https distributor language selector HTTPS distributor is missing a language selector menu (#196) · Issues · The Tor Project / Anti-censorship / rdsys · GitLab
- fixing some errors in the translated pages
- does the translation work for bridges.torproject.org exist somewhere already?
Next week:
- 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: Set up a more permanent Conjure bridge (#46) · Issues · The Tor Project / Anti-censorship / Pluggable Transports / conjure · GitLab
- review Tor browser Lox integration Bug 43096: Move to Rust for the Lox integration (!1300) · Merge requests · The Tor Project / Applications / Tor Browser · GitLab
- add TTL cache to lox MR for duplicate responses:
Enable repeat responses to successful Lox requests (!305) · Merge requests · The Tor Project / Anti-censorship / lox · GitLab
- Work on outstanding milestone issues:
- key rotation automation
Later:
pending decision on abandoning lox wasm in favour of some kind of FFI? Consider dropping Lox's WASM (#43096) · Issues · The Tor Project / Applications / Tor Browser · GitLab):
- add pref to handle timing for pubkey checks in Tor browser
- add trusted invitation logic to tor browser integration:
Lox module doesn't include trusted invitation redemption (#42974) · Issues · The Tor Project / Applications / Tor Browser · GitLab
- 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-12
Last weeks:
- Bumping pion stack version: 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
--
meskio | https://meskio.net/
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
My contact info: https://meskio.net/crypto.txt
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Nos vamos a Croatan.