Hi again,
I just wanted to let provide an update to my previous email to let
everyone know that my last official day as Communications Director for
Tor Project, Inc will be on April 30th (this Sunday).
Best,
Josh
On 04/14/2017 04:57 PM, Joshua Gay wrote:
> Hello,
>
> I wanted to let you all know that in the near future, Tor Project will
> be starting the process of finding a new Communications Director.
> Unfortunately, I was unable to do the job, and so I will be stepping
> down from my role when my replacement is hired. But, until then, I will
> be continuing to help with press inquiries as well as wrapping-up and
> sharing some of the work (research, planning, etc) that I began.
>
> While I am sad that things didn't work, it was my sincere pleasure to
> have met and worked with many of you and I am grateful for having been
> given the opportunity to help Tor Project. If you have any questions or
> would like my help on something (proofread a blog post?), please don't
> hesitate to ask! My email address is <joshuagay(a)riseup.net>, and I will
> also continue to lurk on IRC (jgay) in #tor-project and elsewhere.
>
> Best,
>
> Josh
>
>
--
Joshua Gay
Communications Director
Tor Project https://torproject.org
GPG: 59F4 F183 7CC2 7193 3850 21A9 5211 5F6F E922 09E1
Notes for April 20 2017 meeting:
Alison:
1) Support portal
1.1) adding lots of content, figuring out how it'll fit with the the
rest of the website redesign
1.2) we still don't have a timeline/date for a testing site because
we're waiting to hear about the funding first
1.3) we're meeting weekly about this and the outreach portal
2) Outreach portal
2.1) began sitemapping and organizing content ideas (training,
brochures, localization)
3) Global South
3.1) researching GS meeting locations for March 2018 or September 2018
3.2) ilv set up a new bandwidth server in Santiago
3.3) LFP made it to round two of the Lush Digital Fund, which could get
us about $12k for Global South outreach
3.4) connected NoiseTor to ilv to make plans for Global South relay support
3.5) we now have two comms channels for Global South chatter: #tor-south
and tor-south(a)lists.tpo
4) Trainings
4.1) Sukhbir is speaking about Tor at Google India's Open Data Camp in
Bangalore
4.2) ilv is speaking at Cryptorave
4.3) LFP trainings
4.3.1) last week: Tennessee Library Association Conference, Univ of
Michigan, Political Research Associates, ALA
4.3.2) upcoming: New Jersey Library Association Conference, New
Hampshire Library Association Conference
4.4) second Rocnation Tor training is May 10
5) commsdir interviews
6) connecting with some people in Turkey about Tor blocking
7) social contract vote ends 25 April
8) Phoul is working with Jon to send tshirts and stickers to active
Transifex translators
9) reviewing results from the Tor Meeting survey and starting to plan
for Montreal
10) next: LFP is working on a survey of all our participating libraries
to find out what Tor stuff they're doing
11) traveling next week, the week after, and a lot throughout May, now
that I think about it
Nick:
1) On vacation this week
2) All's well!
3) I owe Isabela a bunch of answers for different spreadsheets and
things once I'm back.
Roger:
1) Where are we on the new blog?
2) I'm going to update the sponsors page soon; let me know of any new
sponsors.
3) There's a recent press request that it would be wise for somebody to
handle.
4) I'll be traveling much of the next two weeks.
Mike:
1) Working on netflow and adaptive padding patches
2) Reading about and learning Rust
Arturo:
1) The OONI team is applying to the CitizenLab Summer Institute
2) Making progress on the probe orchestration and data processing pipeline
3) SuperQ is helping us setup better monitoring of our infrastructure
(https://github.com/TheTorProject/ooni-sysadmin/pull/106)
isabela:
1) roadmap + dependencies track process started with network, tbb,
metrics and ux teams - I wonder if OONI and Community want to do this too
2) starting to pick up NSF stuff this week / hopefully this work will be
organized (eventually) within network team's roadmap
3) writing an article about orbot and orfox to a brazuka magazine/newsletter
Georg:
1) New Tor Browser releases got out; 7.0a3 alpha is the first one based
on Firefox 52 ESR
2) We stopped the hardened Tor Browser series; blog post etc. should go
out soon
3) Bug bounty program is moving slowly towards being publicly available
Hi! Our meeting transcript is at:
http://meetbot.debian.net/tor-dev/2017/tor-dev.2017-04-24-16.59.html
Below are the status reports from this week:
====================
Network team meeting pad update notes, 24 April 2017
nick:
* was on vacation.
* finished consdiffmgr branch (merged today)
* reviewed a bit
* Refactored directory request api
* This week:
* aiming to get consdiff implementations mostly done; will
depend on compression status.
* aiming to review and merge much more, especially compression
* Aiming to help others with priorities etc
* What am I forgetting?
* Concerning topics:
* Review backlog.
* **Revision backlog**
dgoulet:
- Worked on some small 031 tickets, most of them in needs_review or merged.
- Finalize the prop224 service hashring and upload descriptor code. (#20657)
- Working on adding unit test coverage to #20657 (ongoing work is in branch
ticket20657_031_02)
- Tickets from the prop224 groundwork are getting merged (#21888). Yay! More
ticket to come such as #21979 (load and configure service).
This week:
- Second round of review on #16861 (mike's branch)
- Continue on unit testing for #20657 while adding more and more ticket
for upstream merge by pieces.
- Resolve some 031 tickets.
ahf:
Last week (unordered):
Sponsor4:
- Monday was easter holiday.
- Got #21662, #21663, and #21664 reviewed (first round).
- Reviewed #21647 for Nick.
- Do coverage runs for the compression code and start adding
`LCOV_EXCL_*` in appropiate places and fix tests.
This week (ordered):
Sponsor4:
- Working on cleaning-up things from the #21662, #21663, and
#21664 review: currently missing to fix refactoring the different
compression test cases into one compression test suite.
- Finish coverage fixes.
- Fix #22051 (make non-streaming compression API use the
streaming compression API).
- Handle upper-bound of memory usage in LZMA code (postponed
from last week).
- Look into next steps for Sponsor4: measurements?
pastly:
- so much paper writing
- the original "vanilla" Tor scheduler has some configurable limits.
- They are never effective in practice (chosen conservatively
and never hit).
- The vanilla sched is called many times per ms. The
intra-tor process queueing times are ~0.
Therefore, 100MB (the limits
Scheduler{Low,High}WaterMark__) of data never accumulate in the
outbufs.
- I also plan on removing SchedulerMaxFlushCells__ in favor
of a static 1000 (its default).
Such a large value makes the sched behave like Tor did
before it even had a global sched:
one socket at a time. This further cleans the line between
the "vanilla" and "kist" schedulers
- Maybe max flush cells should be configurable still, but
for many other reasons, it isn't useful.
- (end for brevity)
- They were added to make the scheduler KIST-like.
- I plan on removing them. My new scheduler should be used for
KIST behavior
- As mentioned in previous meetings, it's easy to switch
between schedulers
Sebastian:
* Have been oxidating. Unfortunately, a big part of the planned
rust integration won't be as
nice as it could be, because Rust doesn't want to guarantee
interface stability for allocing
across an FFI border, even if we can ensure that the same
allocator is used.
* consdiff code compiles on debian stretch, on amd64 (probably x64
too, haven't tested)
* Found a couple of bugs in the C consdiff code, nothing major.
* Working on final touches, next up is blog post. Will send draft
to network-team list before posting.
catalyst:
* bug triage. not very many new tickets needed adjusting.
* looked at #12930. still working out how the data flow from SMETHOD
ARGS to Bridge config lines work, along with quoting, etc. will
probably propose some spec revisions to exclude problematic characters
from args as a short-term workaround.
* looked at snowflake proxy (the browser crowdsourced proxy component)
* helped gather info on some macOS Tor Browser 7.0a3 bugs (default
search engine, etc.)
* wrote regression test for #22034 (GETINFO extra-info/digest/)
* obfs4 often fails for me on Tor Browser 7.0a3 in macOS, but meek and
obfs3 work. obfs4 in 6.5.2 also works. trying to get more info about
this. could learn useful background for improving bootstrap feedback.
* a little distracted by buying a house
Mike:
Last Week:
* Updated #16861 based on dgoulet's review. Let me know if I
should squash/rebase again.
* Did some work on protocol negotiation for Adaptive Padding
* Started learning Rust. It's pretty nice!
This week:
* More Adaptive Padding, more Rust
* Bug Triage
asn:
Last week:
* About 80% to doing the ed25519 validation. Pushed branch at
#22006 . Lots of head beating with crypto math -- Ian helped.
* Talked with blockstack people. They will publish a plan for
blockstack integration with Tor in two weeks. (ask me for more info)
* Reviewed a bunch of prop224 groundwork tickets (#21888)
* Did some unittests for my WIP rend circuit crypto branch #21859
* Opened #21969 since it seems the "We're missing descriptors
for some of our primary entry guards" bug is still with us.
* GSoC stuff
Next week:
* The Roadmap Email
* Finish up the ed25519 validation code #22006
* Take care of some more ed25519 prop224 business (#22052)
* Continue work on the e2e circuit stuff (#21859). ETA
probably next week
EOF
Isabela
* Working with teams on roadmaps&dependencies - need help adding
tasks related to NSF grants and sponsorR - two dependencies people
have related to this team: tbb+ux depend on isis bridges work (already
following up with her via email) and maybe on the implementation of
the automation for tor launcher (pt selection)
* DRL sent us more questions related to our proposal - working on
answering those and will have a call with them this week
* Will share this week the DRL propsal tasks with all the teams who
will be working on them
isis:
Last week:
* finished OTF work
* set up meek-server and also meek reflector on AppEngine for
bridgedb channel to new distributor
* released draft design of distributor
* did status reports and billing and paperwork things
This week:
* Taking time off because I've not started at Tor yet (also
another personal reason)
Hi!
Here is a copy of my status report for the month of April, as sent to
OTF just now. (It's sent today because this is the last day of my OTF
Project funding.)
----- Forwarded message from isis agora lovecruft <isis(a)patternsinthevoid.net> -----
> From: isis agora lovecruft <isis(a)patternsinthevoid.net>
> Subject: April 2017 Report for Tor Bridge Distribution
> Date: Fri, 21 Apr 2017 20:20:18 +0000
> Message-ID: <20170421202018.GB4452(a)patternsinthevoid.net>
> To: otf-projects(a)opentechfund.org, otf-active(a)opentechfund.org
> Cc: isis agora lovecruft <isis(a)patternsinthevoid.net>, Henry de Valence <hdevalence(a)hdevalence.ca>
>
> Hello,
>
> The following progress was made in April 2017:
>
> - We redesigned some parts of our protocol, specifically with the aim of
> improving user experience and making it easier to design user interfaces
> for it, i.e. making the proofs about the credentials smaller.
>
> - We released a provisional draft of our social bridge distribution
> protocol, now called Hyphae, including implementation and design notes. [0]
>
> - We designed a RESTful API for Tor Browser to use to automate requests for
> bridges and reporting that bridges are blocked (cf. Appendix B of [0]).
>
> - We set up a meek-server for BridgeDB, a new Google developer account, and
> an AppEngine meek reflector, in order to allow automated requests to the
> new distributor be made in a censorship-resilient manner. [1]
>
> This is our final report for this project. We are incredibly thankful to
> OTF for their support, both financial and in terms of the wonderful
> community of fully excellent people they have worked so hard to establish
> and maintain. As always, we're happy to help ongoing and future OTF
> projects acheive their goals in the future. Also happy to just chat with
> any of you any time. Thanks! <3
>
> [0]: https://lists.torproject.org/pipermail/tor-dev/2017-April/012221.html
> [1]: https://bugs.torproject.org/16650
>
> Best regards,
> --
> ♥Ⓐ isis agora lovecruft
> _________________________________________________________
> OpenPGP: 4096R/0A6A58A14B5946ABDE18E207A3ADB67A2CDB8B35
> Current Keys: https://fyb.patternsinthevoid.net/isis.txt
----- End forwarded message -----
--
♥Ⓐ isis agora lovecruft
_________________________________________________________
OpenPGP: 4096R/0A6A58A14B5946ABDE18E207A3ADB67A2CDB8B35
Current Keys: https://fyb.patternsinthevoid.net/isis.txt
Notes for April 13 2017 meeting:
Nick:
1) I'll be away from IRC next week, but hacking as time permits
2) Network-team development continues apace
3) worked with Isa on roadmap
4) worked with Roger/asn on SponsorM-catalyst coordination
Roger:
=====Ongoing issues we should be aware of:
1) The russian exit relay operator
2) Khazakstan's dpi censorship (Allot) has spread to Azerbaijan. Also
Turkey continues to block Tor quite well and we don't know how. How do
we make progress there?
3) Snowflake development could use some attention.
4) Fastly blog post and renew
=====Stuff for individual people:
5) Fyi, MIT has blackholed all of riseup. (Fixed as of a week later.)
6) Who is leading: Sida follow-up?
7) Who is leading: Choosing people for DRL implementor's meeting?
8) Working with Nick on "censorship stuff Catalyst could work on"
9) Working with Griffin on "posting our 2015 990 soon"
10) Working with Isabela on "nsf point people from the network team"
11) Working with Linus on posting the corporate documents
Shari:
1) Met with Mozilla last week and following up this week or early next week.
2) Talked about some AMS feedback with Biella and Linus.
3) Checking in with Jon about Montreal plans.
4) Scheduling trip to NY for Netgain meeting. Making plans to meet lots
of folks while I'm there.
5) Reviewing resumes for writer applicants and doing screening
interviews with Erin.
6) Interviewing/talking with a couple of people for CommDir position.
Georg:
1) We are busy with preparing the new stable and first alpha release
(based on esr52)
2) I started to move our bug bounty program forward again
Isabela:
1) One last thing with ISC - changes on milestone 3
2) Following up on the roadmaps/dependencies things - emails to teams
are going out today
3) be off tomorrow all day
4) interviewing for comms dir
5) hiro is pretty much ready with a gitlab instance for network team to
try out (migrate out of trac project) / she is also digging into the
blog upgrade/migration work
6) Linda is working on the website redesign project - check her list for
this month at the ux team roadmap:
https://storm.torproject.org/shared/sphA6vPmW1ZI4owe0kPRRukQu3T_lvADnmnZCuH…
Mike:
1) Met with Mozilla last week
2) Distracted by taxes this week
Karsten:
1) Got the funding proposal in shape for Cass to turn it into real
English next week.
2) Worked more on simulation of directory-request statistics with
Laplace noise with mixed results.
3) Got 3 OnionPerf instances up and reporting useful measurements.
4) Preparing to go on vacation starting tomorrow night until next Friday
morning. (Somebody else will have to send these notes if they're
supposed to go out on Monday, otherwise they'll go out next Friday.)
5) Started a vote on the social contract, almost started another one for
community council membership.
Arturo:
1) We released ooniprobe 2.2.0 that includes the new web UI:
https://github.com/TheTorProject/ooni-probe/releases/tag/v2.2.0
2) We wrote a blog post with some of events we attended in the past
months: https://ooni.torproject.org/post/ooni-iff-rightscon/
3) We wrote a blog post for a Brazilian newsletter (not yet published)
4) We are coordinating with people in DRC (Congo) to monitor ongoing
possible censorship events due to current protests
5) Updated test lists for Azerbaijan and Venezuela following reports
from people informing us of censorship events in the countries
Apologies for the last minute notice, but I just found out about this
and thought maybe folks on this list might want to cobble together a
last minute application.
>From their website:
"The Citizen Lab Summer Institute (CLSI) is a meeting place for
researchers and practitioners from academia, civil society, and the
private sector who are working on Internet openness, security, and
rights. It brings together perspectives from a wide range of backgrounds
across technical and social science disciplines. Participants range from
established experts to those just entering the area."
https://citizenlab.org/summerinstitute/2017.html
Hi all,
We're meeting weekly on https://meet.jit.si/TorUX on Mondays at 15:00 UTC.
Currently, it's going to be discussions about redesigning the website.
Feel free to listen in on what is going on, if you are curious.