tor-project

tor-project@lists.torproject.org

16 participants
2324 discussions

Notes from September 1 2016 Vegas team meeting
by Karsten Loesing 05 Sep '16

05 Sep '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 See this posting for context: https://lists.torproject.org/pipermail/tor-project/2016-April/000223.html Notes for September 1 2016 meeting: Georg: 1) The GSoC project Fingerprint Central (https://fpcentral.irisa.fr/) ("our" Panopticlick tool) is done and the question is what to do with the custom statistics. Current idea is to limit access to the 10 most popular values by unauthorized users and 200 by authorized ones. 2) I helped with the OTF proposal a bit and with getting the ISC work (porting the Security Slider to Android) going 3) Who can help me understand what's up with the tbb-build machine? Maybe we are still paying for it and it is not reachable for us? Kate: 1) Exciting to see people tweet that they are starting new Tor relays 2) New bridge authority uptake is increasing: https://people.torproject.org/~karsten/volatile/running-bridges-2016-09-01.… 3) Tor traffic questions: Tor metrics are not yet reflecting new Bifroest bridge authority, but will soon :) 4) Upcoming posts: Isis (about the new bridge authority), a Q and A with an exit relay operator, new Tor Messenger beta release, GSoC student 5) We are building relationships with a wider demographic range of software devs and anti-surveillance activists--they are following us now on Twitter for the first time and encouraging others to also. 6) Diversity = bigger array of skills, access to new networks of people, and greater resilience to attack (more groups of people have our back). We're less easy to pigeonhole, too (already true if you know us well). Alison: 1) Meeting planning progress: agenda engagement is going REALLY well! 2) Public hack day promotion: positive messaging 3) Metrics for relay operators: collecting ideas here https://pad.riseup.net/p/metricsneeds, then working with metrics and community teams to use Onionoo data to better support relay operators. Thinking of other ways we can support our relay community... 4) Community docs progress: working a lot on membership docs, getting some good feedback. I'd like to get these finished at the Tor meeting, ideally. I need other people to review them with me. 5) Support desk progress: phoul is setting up support.torproject.org and we hope to be able to share soon. also working on updating old RT tickets to use in the FAQ, building the glossary. 6) Rapid response project: the community team is just getting started on Isa's idea here https://trac.torproject.org/projects/tor/wiki/org/teams/CommunityTeam/Proje… 7) Organizing Tor event at Aaron Swartz Day -- still need more Bay Area people to join us! Nick: 1) I coded this week! So did my team. 1b) Infrastructure diversions happen while coding; these are valuable. 2) Trying to advance project security policies w Georg, anyone else who can help. No time. 3) Team headcount: how do I know if I can hire? 4) Grants process: we should figure out how to improve. Shari 1) We were approved for $250k from MDF for general operating support! :) 2) Lots of grant proposals these past couple of weeks. Thanks to everyone for all of their hard work. OTF goes in today. I'm currently working on the budget. 3) Lots of meeting planning. 4) What do folks think about Amsterdam/Utrecht for next Tor meeting in March? 5) Job posting for chief grants/finance officer went up. We've got a couple of promising applicants. What should the process be? 6) Linda Lee accepted the UX lead job and starts on 9/21. Isabela: 1) organizing the kick off of the ISC tor browser mobile project 2) working on proposal for otf 3) organizing the internal launch of style guidelines 4) trying to prep for dev meeting Mike: 1) Got the Copperhead+Tor prototype build scripts working: https://github.com/mikeperry-tor/mission-improbable/. I'm using it now, but I have a couple more things to improve and then it should be ready for a much wider announcement as part of Tor Labs. I think it is time to start soliciting Tor Labs posts from tor-internal perhaps? 2) Working on the otf proposal Karsten: 1) Spent a fair amount of time on the Tonga/Bifroest migration, including updating metrics-related code to handle two concurrent bridge authorities. 2) Evaluated sanitized web server logs together with Georg to learn about Tor Browser downloads (~8M/quarter) and update pings (indicating 900k concurrent users). 3) Discussed the ExoneraTor database design with Sebastian who pretty much took over the testing; preliminary results are very promising. 4) Finally released metrics-lib/DescripTor 1.4.0. 5) Starting to prepare for the Berlin meetup next weekend. -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQEcBAEBAgAGBQJXzWixAAoJEC3ESO/4X7XBuRQH/RUraonnI2Ipt09XUtxfOVVF vmTGCM7dpK1fvuF+EUfcBACHjPtLNH7Kkglt7G6B2ikf9wBH0CwlUiNpII9wtxLR BO1a/1xkGX41r/rn2aFJZq96o5tnDP3ReBbyf/ZOvZyu2r26tNp+Lu95WlorFSbt 6oY/7UjjGzU0Mca8hTNyaIQrrwRBIT7t062qqByX/N6ty1BGFIKgpL51GQxC5Dpz umzthvUmmvbLlpTv8JKIxNWtWN55sna+bW3kRtTxCZ8g6UdSw0EwRyBBp+MZQWjQ Cgy3gym8LUJhjulNycxRg22jFt9mPJ44bAaxS3ImfBfRIdI4u2+X4A/2JRPJ+fs= =Oxyt -----END PGP SIGNATURE-----

1 0

Metrics to help relay operators?
by Karsten Loesing 31 Aug '16

31 Aug '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Alison, moving this thread from the metrics-team@ moderation queue to this list with your permission: > Hi Metrics team, > > I was talking to Roger on IRC about how great it is that he sent > those checkin mails to everyone who runs a fast relay, and he had > an idea for the metrics and community teams to work together to > get useful lists that we could use to help give better support to > our network of relay operators. For example, a weekly mail of all > the relays that just passed the "earned a tshirt" threshold, or > some other threshold about how much bandwidth they've pushed over > a period of time, etc. The community team could then contact the > relay operator(s) and congratulate them, thank them for their > service, see if we can offer them help in any other ways, and so > forth. > > I've copied the community team here. Let's chat if you guys are > interested! > > Alison Sure, let's do this. I might not be able to hack much on this myself in the next weeks, but I'm happy to speculate how such a tool could be designed. Is there anybody in the community team (or another friendly volunteer on this list) who'd be comfortable writing a small Python script that fetches Onionoo data [1] and filters out contact information of relays matching given criteria? That's how Compass [2] was started before it became a website, and it's how the t-shirt script [3] came to life (shortly before it was forgotten). I could imagine that we start with a simple Python script that can be run whenever somebody from the community team is ready to reach out to new relay operators. We could later automate that process by letting cron run that script once per week and have it send the output to some mailing list. But that could be step two. Hope that helps as a start. All the best, Karsten [1] https://onionoo.torproject.org/ [2] https://compass.torproject.org/ [3] https://gitweb.torproject.org/metrics-tasks.git/tree/task-9889/tshirt.py -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQEcBAEBAgAGBQJXxT3zAAoJEC3ESO/4X7XBilwH/21JJ6HS8Nr1gfIrOWGurAQl qJBSref2NoPsXJuwG1Z038Zq6JysTRNkzZoqgmZTbILwnMAoXM8rXRZuUQnCGgxN jP5V0xjtSM6d7VRLr34JXt8pbo1Cqd1/tGzEHzsS2muUA80vZK9klv/M6O5CS0wE nqjApwD2OHRBVPq4D+MX2DxV705DJTCgCF3caA8z2nocs0oKDzC8078Wy4usc4KB l9Yf/WLyv24Ny2Uq7m8C/WkyAYEOBAQwze9/Z7leTASUaF9EtSxJKbdx1dIUexgv tTCr7mEBRqdAeKfUNUmrQxBkJdZxLUAnHGjuJrmj+GHrXawmsLkguu4dNf23sKc= =i5Pp -----END PGP SIGNATURE-----

3 4

Summary of meek's costs, July 2016
by David Fifield 30 Aug '16

30 Aug '16

Here's the summary of meek's CDN fees for July 2016. App Engine + Amazon + Azure = total by period all 2014 $600.63 + $917.89 + $0.00 = $1518.52 January 2015 $464.37 + $669.02 + $0.00 = $1133.39 February 2015 $650.53 + $604.83 + $0.00 = $1255.36 March 2015 $690.29 + $815.68 + $0.00 = $1505.97 April 2015 $886.43 + $785.37 + $0.00 = $1671.80 May 2015 $871.64 + $896.39 + $0.00 = $1768.03 June 2015 $601.83 + $820.00 + $0.00 = $1421.83 July 2015 $732.01 + $837.08 + $0.00 = $1569.09 August 2015 $656.76 + $819.59 + $154.89 = $1631.24 September 2015 $617.08 + $710.75 + $490.58 = $1818.41 October 2015 $672.01 + $110.72 + $300.64 = $1083.37 November 2015 $602.35 + $474.13 + $174.18 = $1250.66 December 2015 $561.29 + $603.27 + $172.60 = $1337.16 January 2016 $771.17 + $1581.88 + $329.10 = $2682.15 February 2016 $986.39 + $977.85 + $445.83 = $2410.07 March 2016 $1079.49 + $865.06 + $534.71 = $2479.26 April 2016 $1169.23 + $1074.25 + $508.93 = $2752.41 May 2016 $525.46 + $1097.46 + $513.56 = $2136.48 June 2016 $0.00 $1117.67 + $575.50 = $1693.17 July 2016 $0.00 $1121.71 + $592.47 = $1714.18 -- total by CDN $13138.96 + $16900.60 + $4792.99 = $34832.55 grand total https://metrics.torproject.org/userstats-bridge-transport.html?start=2016-0… The number of users recovered somewhat since the beginning of July, rising to about 7,500. It seems to be former meek-google users who are being absorbed into meek-azure and meek-amazon. If you are one of the users affected by the meek-google shutdown, see here for a workaround: https://lists.torproject.org/pipermail/tor-talk/2016-June/041699.html == App Engine a.k.a. meek-google == 0 GB $0.00 0 instance hours $0.00 https://atlas.torproject.org/#details/88F745840F47CE0C6A4FE61D827950B06F9E4… == Amazon a.k.a. meek-amazon == Asia Pacific (Singapore) 285M requests $342.71 628 GB $84.78 Asia Pacific (Sydney) 7M requests $9.27 38 GB $5.20 Asia Pacific (Tokyo) 1M requests $1.85 6 GB $0.81 EU (Ireland) 256M requests $307.53 1032 GB $79.86 South America (Sao Paulo) 18M requests $40.32 170 GB $40.51 US East (Northern Virginia) 144M requests $144.71 811 GB $63.68 -- total 713M requests $846.39 2687 GB $274.84 charge for alarms $0.50 https://atlas.torproject.org/#details/F4AD82B2032EDEF6C02C5A529C42CFAFE5165… == Azure a.k.a. meek-azure == Zone 1 6103 GB $530.99 Zone 2 445 GB $ 61.48 -- total 6549 GB $592.47 https://atlas.torproject.org/#details/AA033EEB61601B2B7312D89B62AAA23DC3ED8… Earlier reports in this series: https://trac.torproject.org/projects/tor/wiki/doc/meek#Costs

1 0

Notes from August 25 2016 Vegas team meeting
by Karsten Loesing 29 Aug '16

29 Aug '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 See this posting for context: https://lists.torproject.org/pipermail/tor-project/2016-April/000223.html Notes for August 18 2016 meeting: Shari: 1) Working with Gunner and Alison on the semi-annual Tor meeting agenda. 2) Working with our lawyer on his presentation for the meeting. 3) Reviewing DRL grant proposals. Nick: 0) Vacation was lovely, got a bit of programming done. 1) Trying to program 1a) Distracted by need to put out two releases 1b) Distracted by grants stuff Kate: 1) Fact sheets--organizing their finishing; hoping to hire artist/web designer for a bit of freelance design 2) Blog posts from GSoC student and HOPE 3) Had stomach bug Tuesday and Wednesday 4) Seeking new good news to promote after Labor Day :) Isabela: 1) working with the ux team to prepare for internal launch of our style guidelines and how we will roll it out 2) working on DRL proposals - deadline is tomorrow (august 26) 3) got reports out to otf and drl 4) coordinating with ux team and network team some ideas of sessions for dev meeting (trac session, style guidelines session etc) Alison: 1) Tor meeting agenda planning 1a) we need to talk about agenda priorities (from this team and getting individual community member engagement); One from Shari:" I’d really like there to be a discussion about a theme for our end-of-year fundraising campaign. Last year it was “This Is What a Tor Supporter Looks Like.” What should it be this year?" 1b) welcoming new people: buddy system, welcome event 1c) creating a "safer space" 2) Working on HOPE wrapup post 3) Community team continuing to work on the support portal 4) and membership docs Karsten: 1) Drafted a first schedule for the Berlin meeting together with Georg. https://trac.torproject.org/projects/tor/wiki/org/meetings/2016BerlinMeetup 2) Almost released metrics-lib 1.4.0 together with iwakeh, but ran into a bug and postponed the release. 3) Worked a lot on the ExoneraTor database redesign I started with Sebastian the week before. 4) Commented a bit on grants in response to questions by Isabela and Cass. Roger: 1) Doing all my logistics Mike: 1) I got image signing working for CopperHead - I now have a script that takes the official copperhead images, adds in Google Apps and OrWall, and produces verified-boot compatible images. I'm still working out some bugs with OrWall and the keyboard, and need to figure out how updates are going to work, but concept is now more or less proven. 2) Been helping a bit with the DRL Tor Browser Mobile proposal. -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQEcBAEBAgAGBQJXw/RwAAoJEC3ESO/4X7XBZYMH/i0m1E8h/M8OR/eiaVZQ0yJy zMJqx20DmmPAGgzqdHk/MlZKt9EXoNho4Mg96BA5p4sB+RmQ6/ksDIkkPp1uFNmt Em3xifkJ2Ie7TVFHkjtd9wiwDowJr++44ht1yXk9BIdMgEFrKnCo852TjTUGBd5R IElY/BMLNiE49hnmyw+vTHx98OH2eDPfr+RuBnYN1FaGKdAJbCMYidcYojQUfKwS 8TuqWn/WsjZUjHrOUflBsrTBZ3RuEokbv2vOtW8HnVuj2NRyDsFLGNfNQKBsCSNA Lv62DOxBn7TkMy2C54lEZAoVQZ3xpNVJ72W2geQuWAall0alyKRFvTxk/9Jh2l0= =qKsA -----END PGP SIGNATURE-----

1 0

New Bridge Authority
by isis agora lovecruft 26 Aug '16

26 Aug '16

Hello all, Today, I am very excite to take a field trip (!!) to a datacenter (!!!) with some most excellent folks from Greenhost (DrWhax and Sacha!!!). We will be racking a server and installing an OS on it, and getting it ready to be a new Bridge Authority to replace Tonga. Earlier this week, David Goulet and I got a Bridge Authority up and running in a test network, so perhaps a logical step will be to put the new Bridge Auth into the test network and ensure that it's at least cursorily behaving. The new Bridge Auth needs a name. Suggestions welcome. :) Best regards, -- ♥Ⓐ isis agora lovecruft _________________________________________________________ OpenPGP: 4096R/0A6A58A14B5946ABDE18E207A3ADB67A2CDB8B35 Current Keys: https://fyb.patternsinthevoid.net/isis.txt

16 21

I'm offline Aug 29 - Sep 13
by Roger Dingledine 24 Aug '16

24 Aug '16

Hi everybody, Here's a reminder that I'll be offline Aug 29 - Sep 13 inclusive. And I mean actually offline with no devices. So if there's something critical that you need me to do before I disappear, now is a great time to remind me of it. Items on my current high priority todo list: * Get the SponsorM (NSF) annual report in, so the program manager can have a chance to review it and tell us what changes she wants. I'll aim to coordinate with somebody smart to cover for me while I'm gone in case they throw some surprise last-minute time-critical questions at us. Based on past experience there is a good chance they will. :( * Get the SponsorV (NSF) annual report in, if Micah Sherr (prof at Georgetown who is ) finishes his first draft of it in time. * Get the "here are the tickets and stuff that we did for year 2" list to SponsorR so they can pay us for year 2 and so they can start the paperwork for year 3. * Try to get my upcoming travel under control, along with expenses and reimbursements. Aren't logistics fun! * Follow up to Shari about some future funding opportunities and whether they match our mission enough for us to go for them. * What else am I missing? --Roger

1 0

Rapid response against censorship
by isabela 22 Aug '16

22 Aug '16

Hello Tor, I took the freedom to create a project under the Community Team wiki which is an attempt to create a rapid response program against censorship events. In the past months we did a little bit of that, by tweeting in PT to people in Brazil teaching them to use Tor when Brazuka judge blocked Whatsapp, we tweeted reaching out to Uganda folks also in an attempt to get as many people to know about Tor as possible when the government was blocking social media during the elections, and most recently we tweeted in TR when the government blocked Social Media during the coup event last month. One might say: 'well if social media is blocked why you using to teach people how to circumvent the blockade?'. What works here is the 'mouth to mouth' outreach, while many in the country where the censorship event might not be able to access social media, relatives and friends abroad can still do it and they are in communication with those inside the country. As an immigrant living abroad I can tell you that *it is a thing* I for instance called my family and told them to use orbot so we could still talk with Whatsapp while the blockade was happening. Of course we could do more and spread the word via email lists and other venues and communication channels. We also could be more prepared and have messages already translated in multiple languages so it's easier to have something in the right language for the population we want to reach. We can try to document these events and our actions to respond to it as well e.g. https://blog.torproject.org/blog/tracking-impact-whatsapp-blockage-tor There is many things we could be building here to have such a program in place! I started this wiki: https://trac.torproject.org/projects/tor/wiki/org/teams/CommunityTeam/Proje… Just to show how we can start organizing this things -- those phrases there are just examples, not the real thing right now. I was wondering if the Community Team and others would be into this idea and would like to help improve that page. Maybe we can even do it during the hacking day of the dev meeting! What y'all think of that? Cheers, Isabela -- PM at TorProject.org gpg fingerprint = 8F2A F9B6 D4A1 4D03 FDF1 B298 3224 4994 1506 4C7B @isa

4 4

Notes from August 18 2016 Vegas team meeting
by Karsten Loesing 22 Aug '16

22 Aug '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 See this posting for context: https://lists.torproject.org/pipermail/tor-project/2016-April/000223.html Notes for August 18 2016 meeting: Georg: 1) I helped a bit with the OTF proposal 2) The tbb-build machine is still not reachable. Who can move this forward? Shari: 1) Lots of planning for the meeting formerly known as TorDev. Question: Will people be hanging out in Seattle for the weekend after the meeting for hacking? If so, can we estimate how many people might stay so we can make sure we've got a good space for this to happen? 2) Trying to get a handle on our funding proposal processes. Worked on a job description for a grants manager, talking with team on how to make budgets look more like other nonprofit funding proposals, sent note to OTF asking for some specific guidance. 3) Reached out to a couple of community members to offer them the opportunity to talk about all that's been happening. 4) Trying to help think about the organization of the UX team. Mike: 1) Finally got email working again over the weekend. I think I didn't lose any, but not sure. 2) Helped with OTF budget revamp. Isabela: 1) OTF proposal deadline moved to sept 1st! 2) I will need someone to review my grammar at drl reports 3) documenting 'rapid response' plan in the wiki -- katie and alison will probably want to be involved here 4) starting to work on wireframes for metrics team \o/ 5) working on priorities with network team since we are in the last mile with 2 contracts 6) prep for proposals deadline on august 26 Karsten: 1) met with Sebastian; worked on databases for website statistics and TB downloads and on fixing ExoneraTor by making its database smaller 2) talked to isabela and then made some preliminary plans for extending scope of metrics to client and application statistics, based on sanitized website logs, possibly GetTor requests, possibly app store statistics, etc. 3) made plans with iwakeh to put out two new releases of metrics tools this month -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQEcBAEBAgAGBQJXuqLSAAoJEC3ESO/4X7XBkwkIAMCr/1Nbi7SMRMPMR8LEv34C T1JRs8WeiSjeGogze2qpeRcJYCtq4HsbWCCEjOvpxfS+70kDDe/jZag6wc/1HsPr TPnYe+yl3Dp9j8jBYE40ixDd/ESQiYa/dA6ScsaFaUXb6dbxghzJKxHwE+oHXxjU i340LP4IG5waF0kz7IRPT+w1flm/UYbfMlg//HeVNdOWbdAfuf2qs1Y0xQCiDy3Q eMQMVS4LBjm5NCZnr4YEoS9t6jHIv+q5Bb6lbibUD1EIW5yE9f+gQVz18hfHGqUg ZSJYjDYcObhF5P9unduagdn7Z1tQRzRcVEvlvzZhmRl+bm9PZKTEvFL8igPr7LI= =c/mI -----END PGP SIGNATURE-----

1 0

A Vote of No Confidence in Shari Steele: A Proposal For A Tor Relay Operator Strike.
by stderr＠riseup.net 19 Aug '16

19 Aug '16

It has recently come to light that the Tor Project chose Franklin Bynum as the “outside counsel” to investigate the allegations sexual assault and sexual harassment against Jacob Appelbaum. Frank Bynum is in a romantic relationship with one of the principle complainant in that investigation, Alison Macrina. In addition, Shari Steele allowed Macrina to become extensively involved in the investigation of Appelbaum’s conduct, despite the fact that she is an interested party in that investigation, since she claimed to have been taken advantage of by him. This is completely unacceptable and unprofessional conduct by Tor’s executive director. If the allegations against Appelbaum are true or substantially true, then this is a gross disservice to victims, since Shari’s actions robbed the process of any appearance of impartiality or legitimacy. If the allegations against Appelbaum are false or false in part, then this just as bad or possibly worse. Either way, Shari’s actions needlessly exposed the Tor Project to civil liability, by creating an obvious appearance of bias, when she allowed Bynum and Macrina to conduct the investigation. Shari Steele has failed in her fiduciary duty towards the project. The Tor Project should not expect volunteers to offer their time and resources, when Tor’s leadership is sending a clear signal that it will condone the preferential treatment of some community members over others, that it may aid and abet public shaming campaigns, and that it will simultaneously undermine the credibility of people who come forward with abuse complaints by poisoning the investigation with obvious bias. Tor needs an impartial, professionally-minded executive director who can insure that influential members of the Tor community do not abuse their power, whether they engage in unwanted sexual advances or expose the project to liability through irresponsible public shaming campaigns. I call upon other relay operators to conduct a coordinated 24 hour shutdown of the Tor network, in order to send a clear vote of “no confidence” in Shari Steele. It’s time for a new executive director and a saner, less favoritism-ridden and personality-driven Tor Project. This is neither an endorsement of Jacob Appelbaum nor an endorsement of the accusations against him. At this point the Tor Project’s conduct is so reprehensible, that it doesn’t matter who is in the right — the leadership needs to go. https://medium.com/@stderr/a-vote-of-no-confidence-in-shari-steele-380e327d…

5 4

Notes from August 11 2016 Vegas team meeting
by Karsten Loesing 16 Aug '16

16 Aug '16

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 See this posting for context: https://lists.torproject.org/pipermail/tor-project/2016-April/000223.html Notes for August 11 2016 meeting: Isabela: 1) finished sida proposal ! 2) have many reports pending that I am trying to work on while I am not working on grant proposals :( 3) trying to get 029 to a realistic state by eow 4) got names/resumes for service maintainer position -- didn't have time to review them yet :( 5) synced with Arturo - I will start having a bi-weekly sync with the OONI team starting in September to help them be on track for deliverables etc Kate: 1) Fastly blog post 2) Multiple media requests 3) Released Social Contract to the media; meh response (however, it got a positive response on social media). OTI liked it Mike: 1) My mail server is offline due to FDC being a horrible ISP. Hopefully will have it relocated soon, though doing so is going to cost me time. I also may or may not be losing mail right now. 2) I'm still working on a Tor Phone prototype based on Copperhead. I've almost got Verified Boot working. Maybe will be able to launch Tor Labs next week or the week after with details. Nick: 1) On vacation next week! I will check email every day or two. I will avoid IRC. Call if there is an emergency. 2) Overwhelmed wrt 029 triage, OTF reply, sponsorV listing. 3) Overwhelmed with people dropping 1-2 hour tasks on me. Roger: 1) I'm on vacation next week too! I will probably be more online than Nick though. 2) My meeting with the SponsorR program manager went well last week. Now it remains for us to actually build and deploy the new onion services design. 3) I submitted a no-cost-extension request for SponsorM which caused a landslide of chaos that I am now riding. 4) I'm still trying to get Mike Perry to talk to Jeremy Epstein about his secure browser ideas. 5) I think we should consider having internal funding proposal deadlines, followed by internal red-teaming of the proposals. 6) I got invited to do a keynote in March and they offered me a $20k honorarium(!) I've asked them to give it to Tor since that's how I think these things should work. 7) NSF grant with UIC is progressing, and we have some decisions to make, to ensure it turns into the kind of project we want it to. Georg: 1) I've been dealing with my backlog after my vacation 2) I helped a bit with the SIDA proposal 3) I dealt with some fallout from bug 19890 4) How can we move bug 19652 forward (getting Whonix to use Tor Browser officially)? <- Georg will answer on the bug Alison: 1) social contract is getting amazing reception, including a note from Chelsea Manning: https://twitter.com/xychelsea/status/763535177683382273. I still need to add this to the website in "About Tor" but we should talk about what else could go in a values/ethics subcategory there 2) Phoul and I have been working on fixing Tor support and we'd like to start working on a support portal, support.torproject.org, modeled after support.twitter.com and using the new Tor Browser manual, Tor glossary, and some revised versions of the old templates from the support desk. Phoul can do the design. 3) continuing work on other community governance docs, planning some Tor Dev stuff with gunner, contacting other community councils, doing lots of trainings Shari: 1) In San Francisco this week to meet with Gunner and our attorney about TorDev meeting plans. 2) Preparing for board meeting on Monday. -----BEGIN PGP SIGNATURE----- Comment: GPGTools - http://gpgtools.org iQEcBAEBAgAGBQJXss07AAoJEC3ESO/4X7XBLHIH/iGgIQmtn6HAtp0T9QjopaaU svy3w+6oKMpqIHuDc7hjvq3bODF86hDOUvp4KiVAqSxiuY5Ma/XjiEZTGNLr/Y+k TMxMUj95MXlVOlNcj5LMG+4qoxC7XbwwiHYINmbOlNtYJvE4BI65/StmryoF2Qcg lXHcAl4buerfzxIgCUz+qABAeyqVyVVu+5P4u3JEqOInObXl5qkTGpeSvdL7jKkq WI0g1s5GJmHxm09VBFjmIWRo+JMPB5MCcQ2tNKiAA2iz8jP3MVe6d+KhmBrhxJSX ZgC8YrA3RSjKekbI2qB/tBdRSf0BXz2UP+QA6ilcVeVRjvuAjUjN9P3dHEgGcxg= =G4S0 -----END PGP SIGNATURE-----

1 0

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

tor-project