Here are our meeting notes:
http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-08-01-17.00.log…
And here is our meeting pad:
Anti-censorship work meeting pad
--------------------------------
Next meeting: Thursday August 1st 17:00 UTC
Weekly meetings, every Thursday at 17: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://storm.torproject.org/shared/knaG2lEzepdsCC21DYk4dD4hRtwcUGnXQvalH1s…
* Our roadmap consists of a subset of trac tickets.
* Note that there's a bug that causes the roadmap to load slowly. To work around it, first click on "All boards", and then on "ROADMAP Anti-censorship team"
* The anti-censorship team's wiki page: https://trac.torproject.org/projects/tor/wiki/org/teams/AntiCensorshipTeam
* GetTor's roadmap: https://dip.torproject.org/anti-censorship/gettor/boards
* Tickets that need reviews: https://trac.torproject.org/projects/tor/query?status=needs_review&componen…
---------------------------
---- 1st August 2019 ----
---------------------------
== Announcements ==
*
== Discussion ==
* Gettor seems to be down #31307
* Roadmap: how are we doing? Is everybody ok for me to organize it in gitlab instead of storm?
* trac updated it under keyword anti-censorship-roadmap: https://trac.torproject.org/projects/tor/query?status=accepted&status=assig…
== Actions ==
*
== Interesting links ==
* https://davidschinazi.github.io/masque-drafts/draft-schinazi-masque.html
* We should at least follow the standardisation process.
== Updates ==
FORMAT!
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.
hiro: (gettor days are Thursday)
This week:
Next week:
Past week:
phw:
This week (2019-08-01):
* Filed #31250 for snowflake.
* Filed #31252 for snowflake.
* Reviewed Tor Research Safety Board submission.
* Proof-read Roger's DEFCON slides.
* Revised BridgeDB patch for #9316 and sent summary of preliminary results to tor-dev@.
* Inspired by Karsten's feedback, thought about how to implement aggregate statistics.
* Got the commit bit for the website and updated obfs4 setup guide.
* Added a work-in-progress wiki page on retiring pluggable transports:
* https://trac.torproject.org/projects/tor/wiki/doc/PluggableTransports/Guide…
* Read new IETF MASQUE proposal and subscribed to their mailing list:
* Here's a summary: https://lists.torproject.org/pipermail/anti-censorship-team/2019-July/00002…
* Started working on improving flow obfuscation in obfs4:
* Realised that obfs4's iat=1 mode sends 1350-byte (instead of 1500-byte) packets on both Linux and Windows? Trying to figure out why.
* A little bit more work in improving PT spec based on the issues we collected:
* https://trac.torproject.org/projects/tor/ticket/29285#comment:5
Next week:
Help with:
Gaba: (updated August 1st)
Last week ():
* off-line
This week (planned):
* hopefully will get into the roadmap
* hopefully move forward organizing s30
ahf
Last week:
- Worked on #28930
This week:
- Finished refactoring parts of #28930. Trying to figure out if we should begin the discussion on how PT's can report back on bootstrap info.
- Continued to work on a tool to convert Trac tickets into Gitlab tickets.
cecylia (cohosh): last updated 2019-08-01 (will try to attend, but at CLSI)
Last week:
- CLSI (31 July - 2 Aug)
- talk preparation
- checked on pion proxy and made progress towards windows build
- review of #27385 and merges
- review of some racecar reports/documents
This week:
- going to be on vacation Aug 5 - Aug 7
- snowflake dogfood
- finish windows build of pion branch (#28942 and #28942)
- sequencing layer for snowflake (#29206)
Help with:
catalyst:
week of 07/11 (actual):
- Stockholm meeting
week of 07/18 (actual):
- recovering from travel
week of 07/25 (planned):
- recovering from travel
- mostly sponsor31
- preparing for extended leave starting 07/29
arlolra: 2019-08-01
Last week:
- review of #31170
- deployed #27385
Next week:
- revisions to #30310
- start looking at the suggestions in #31109
- add a build step / documentation for code reuse in cupcake
- maybe more review of #31170
Help with:
-
dcf: 2019-08-01
Last week:
- merged some refactoring for Snowflake dark mode (#31170)
- reviewed proxy deadlock fix (#31100)
Next week:
- finish Snowflake dark mode (#31170)
Help with:
Hello Tor,
S27 - Onion Services
================
- We continued working with onionsites authentication.
https://trac.torproject.org/projects/tor/ticket/30237
- We shared working time with Tor Browser and Network developers during
the dev meeting to discuss our next steps on this project. You can
follow our design exploration by reading the relevant tickets or sneak
peeking here
https://trac.torproject.org/projects/tor/attachment/ticket/30281/O2.pdf
S9 - User Research
===============
- Gus and Narrira have been traveling through Uganda and Kenya during
June and July. With these travels, we consolidated our relationship with
partners in the global south community to follow our work on the next
sponsor year.
- We shared our first Persona work during the dev meeting. It is one of
the first steps to introduce human-centered design practices on our
workflow. If you didn't make the session, you could see our presentation
and downloads here
https://trac.torproject.org/projects/tor/attachment/wiki/org/meetings/2019S…https://trac.torproject.org/projects/tor/ticket/30430
- During the dev meeting, we distributed a survey to collect feedback
about Tor Browser Usage. We will be sharing the results with the lists
soonish. Also, we want to collect this kind of feedback from the broad
community, so we are planning to extend this survey online.
S30 - Snowflake
============
- The anti-censorship team is working on the Snowflake web extension. We
worked the user interface and other design deliverables.
https://trac.torproject.org/projects/tor/ticket/23888
OONI Explorer
===========
- We were working on reach the stable release for the new OONI Explorer.
We have been polishing UI and UX tickets. You can play with the beta here
https://explorer-beta.ooni.io
- All the tickets we have been working on are here
https://github.com/ooni/explorer/issues?utf8=%E2%9C%93&q=is%3Aissue+label%3…
Fundraising
=========
- We gave support to the Fundraising team on the Bug Smash Fund and
Defenders of Privacy campaigns. We provide visuals for the various
platforms used for promoting them.
- We published a fundraising banner at the latest Tor Browser release.
https://trac.torproject.org/projects/tor/ticket/30577
Thanks,
A
--
Antonela Debiasi
UX Team Lead
@antonela
E2330A6D1EB5A0C8
https://torproject.org
**
*Hello Tor! *
*
Today we launched our Bug Smash Fund. Through the month of August, all
donations the Tor Project receives will be marked to help us smash bugs
and respond rapidly to critical security issues. Many of you have
experienced why we need such a fund: this kind of work is not usually
covered by sponsors or grants, so we have to divert time and funds when
these kind of things happen. And we know that they will happen. So this
month is an opportunity to help us prepare for smashing the bugs ahead.
If you’re able to make a donation, you can do so at
https://donate.torproject.org
We’re reaching out to community members, press, and influencers to
spread the word, and we could use your help spreading the word, too.
If you are on Twitter, you can help by sharing the blog post[1], writing
a tweet using one of the graphics Antonela made (which you can find on
the blog and our tweets) and using the hashtag #TorBugSmash, or just by
liking or RTing our posts[2] or any other positive mentions. Talking
about the fund IRL with someone close to you works great, too.
If you feel comfortable, writing a post that mentions your involvement
can have more impact than one without. You could write something like:
“Bugs happen. I’ve worked on fixing them with @torproject, and we know
there will be more. You can help us be prepared for what bugs may come
by making a donation this month. All donations will go towards smashing
bugs. #TorBugSmash https://donate.torproject.org”
As always, I’ll be watching for posts from the Tor community to engage
with and support. If there’s anything related to this campaign or our
work in general that I’ve missed or would be relevant for us to share,
please let me know. I’m also happy to talk over something you’re
considering posting if you want feedback. You can DM @torproject or me
personally @walnutwordsalad, send me an email, or ping me on IRC (stephw).
Cheers!
Steph
[1] https://blog.torproject.org/tors-bug-smash-fund-help-tor-smash-all-bugs
[2] https://twitter.com/torproject/status/1156910864391262208
*
--
Stephanie A. Whited
Communications Director
The Tor Project
IRC: stephw
PGP Fingerprint: E976 9771 7D46 2E63 9697 9F6D 6D6B 72C3 39A8 76AD
<https://pgp.mit.edu/pks/lookup?op=get&search=0x6D6B72C339A876AD>
