Hi all,

Here are our meeting minutes:

http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-04-09-17.59.html

And here is our meeting pad:

Anti-censorship work meeting pad --------------------------------

Next meeting: Thursday April 9th 18:00 UTC

Weekly meetings, every Thursday at 18: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: https://gitlab.torproject.org/torproject/anti-censorship/roadmap/boards * Our roadmap consists of a subset of trac tickets. For 2020 Q1, the trac keyword is anti-censorship-roadmap-2020Q1 * Next planning session: last week of April * The anti-censorship team's wiki page: https://trac.torproject.org/projects/tor/wiki/org/teams/AntiCensorshipTeam * Past meeting notes can be found at: https://lists.torproject.org/pipermail/tor-project/ * GetTor's roadmap: https://gitlab.torproject.org/groups/torproject/anti-censorship/gettor-proje... * Tickets that need reviews: from sponsors we are working on: * https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor30 * https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor28 * Anti-censorship related tickets that we want other teams to fix: * https://pad.riseup.net/p/tor-anti-censorship-tickets-keep

------------------------- --- April 9th 2020 -- -------------------------

== Announcements ==

*

== Discussion ==

*

== Actions ==

* Please jot down your March 2020 highlights for our monthly team report * https://pad.riseup.net/p/GDSSo-bqhi_dE1oJENyP

== Interesting links ==

*

== Reading group ==

* We will discuss "SymTCP: Eluding Stateful Deep Packet Inspectionwith Automated Discrepancy Discovery" on April 16 * https://censorbib.nymity.ch/#Wang2020a * 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 (related to anti-censorship work). Help with: - Something you may need help with.

phw: This week (2020-04-09): * Made sure that my feedback was still covered in catalyst's rebase of #5304. * Left some feedback in #10831. * Found a new maintainer of a next default bridge in noisebridge. * Finally wrapped up #13727 now that noisebridge01 is no longer in Tor Browser. * Wrapped up #29686 and #30941. * Filed #33835. * Reviewed Tor Research Safety Board submission. * Organised letter of support for an OTF application that seeks to distribute bridges in Turkey. * Made good progress on #32740. Next week: * Write a summary of our current BridgeDB distribution mechanisms and brainstorm new ones * Make BridgeDB report internal metrics (#31422) * Will have to tackle #32740 (Implement a feedback loop between BridgeDB and OONI) Help with: *

Gaba: () Last week (2020-03-30): * not much related to anti-censorship This week (planned): * anti-censorship retrospective

cecylia (cohosh): last updated 2020-04-09 Last week: - diagnosed proxy issues (#33666) - some grant submission things - started looking into building a test suite for NAT topologies (#25595) - investigated setting up a TURN server (#25596) - gave feedback on #32740 - team retrospective - popets things (paper reviews, artifact review) - sent an email to the pion peeps about testing NAT topologies (#25595) This week: - Resume obfs4 tests (#31701, #32657) - see if i can help push snowflake for android along (#28672) - set up some kind of NAT topology testing suite (#25595) - look into setting up a TURN server (#25596) - take a look at reviving the twitter responder in GetTor (#33036) - review GSoC proposals Needs help with:

juggy :

This week: - Tried to study Moat to implement audio captchas Next week: - Implement audio captchas in moat - Keep studying BridgeDB to write architectural overview Help with: - Question about current Moat implementation - it seems to be using XUL, which is deprecated by Firefox if I'm not wrong. I saw a thread in trac discussing reimplementing it with the newer Web Extensions API (but that was years ago)- is that still going on?

arlolra: 2020-03-26 Last week: - merged #33665 Next week: - maybe the proxy parts of #19026 - start on #31201 Help with: - review of #19026 but also answer the question there

dcf: 2020-04-09 Last week: - worked on branches for snowflake turbotunnel merge (#33745) - helped test snowflake proxy failures (#33666) - removed uniuri dependency from snowflake (#33800) Next week: - branches for snowflake turbotunnel merge (#33745) - share access to the snowflake broker CDN configuration (#30510) Help with:

cjb: 2020-04-09 Last week: - gonna be afk with kids Next week: Help with:

antonela: 2020-03-26 - working with Babatunde's interviews (OTF Fellowship) from Nigeria and Cameroon. Shared preliminar notes with Tunde and Nah (#32811) - started to work on this user research document, we still stick to the plan of running it during April (#31870) Help with: - nothing yet :)

agix:2020-04-09 Last week: - Worked on #19997, but the issue seems to be in check.torproject - Worked on #33835, patch needs a few more tests before submission Next week: - Check out check.torproject's code base Help with: -

catalyst: 2020-04-09 last week: - network team roadmapping and estimating s28/s30 tickets this week: - looking into how best to coordinate work on reachability testing (thanks, teor)

thymbahutymba: 2020-04-02 Last week: - CI/CD pipeline for multiarch docker images, which has a problem with the apt tor version even though the apt repository have been changed into the Dockerfile. Next week: Help with:

Hiro: (last updated before 2020-01-09) Started restoring Twitter Responder. When retrieving tweets I need to check for new tweets only otherwise Gettor will end up responding to old back log and already answered messages. <-- is this #27330 ? Next Week: - Work on gettor specs <-- Is this #3781? - More with review of strings and website content and translation