- tor-project - lists.torproject.org

S27 meeting today: Tuesday 31st March @ 15UTC
by Pili Guerra 31 Mar '20

31 Mar '20

Hi everyone, This is your weekly reminder of our S27[1] (Onion Services) meeting today. This will likely be the last meeting on this sponsor for a while as we wrap up the implementation of this project. I look forward to seeing you there! Thanks, Pili [1] https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor27 <https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor27> — Project Manager: Tor Browser, UX and Community teams pili at torproject dot org gpg 3E7F A89E 2459 B6CC A62F 56B8 C6CB 772E F096 9C45

1 0

Network health meeting notes, 30 Mar 2020
by Georg Koppen 31 Mar '20

31 Mar '20

Hi! Yesterday, we had our last weekly meeting in March 2020 in #tor-meeting. The IRC log can be found at: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-03-30-18.00.log… Here come the items from our pad (both statuses and discussion points): Discussion: -Do we have criteria for badexit flag in case of non-malicious behavior? See for instance thread on tor-relays <https://lists.torproject.org/pipermail/tor-relays/2020-March/018276.html>ff. Should we essentially overrule dir-spec here, defining what a(n) (good) exit is? [GeKo: it seems we are in favor for creating some policy according to which we badexit relays even though they formally fulfill the dir-spec requirements; I put that on my plate and loop the folks on the network-health list in] Statuses: GeKo: Last week: -sbws work (mainly reviewing #30905) -more work on issues encountered with our bad relay scanners (dug a bit more into #33663; might be a check/exitscanner bug) -more work on resource load failures caused by Cloudflare (for the Coil folks) -badexiting relays for #32864; follow-up This week: -review follow-up patches for #30905, finishing #33009 -work on #33758 (more fixups/investigations for issues with bad relay scanners) -work on #33696 (integrate badexiting into badconf-entry.py script) -more work on exit relay blocking problem (#33500 etc.) -monthly team admin stuff -ggus: the eff got back to us how should we proceed? [GeKo: ggus goes over the mail and sets up a pad where we then can collaborate] Gus: Last week: - Worked with Steph on tweet/announcement: https://twitter.com/torproject/status/1243251875601952771 This week: - Review EFF Legal FAQ Georg

1 0

Tor Browser Release meeting this week: Wednesday 18th March @ 18UTC
by Pili Guerra 30 Mar '20

30 Mar '20

Hi everyone, We’ll be having our Tor Browser release meeting this week. This week we’re moving the time of this meeting to its summer time schedule: Please join us on Wednesday 18th March @ 18UTC on #tor-meeting. Thank you! Pili — Project Manager: Tor Browser, UX and Community teams pili at torproject dot org gpg 3E7F A89E 2459 B6CC A62F 56B8 C6CB 772E F096 9C45

1 1

Tor Browser Team Meeting Notes, 23 March 2020
by Matthew Finkel 30 Mar '20

30 Mar '20

Hello everyone, We held our weekly meeting on 23 March, 2020. The meeting log is available at http://meetbot.debian.net/tor-meeting2/2020/tor-meeting2.2020-03-23-17.59.l… During that meeting we improving our release process and which responsibilities can be distributed differently across members of the team. ================================ Week of March 23, 2020 Discussion: Please tag transition/migration tickets for S58 Retrospective Dockshackathon this week - Is there anything missing in the Tor Browser Manual we could add during this week? Release management pospeselr: Last week: - #19251 code review - #33534 (release notes/tickets review) - Made it halfway through FF74 tickets, should have the ticket short list by EOD This week: - #33534 -> rest of FF74 and FF75 mcs and brade: Last week: - Code reviews. - Revised patch for #19251 (onion services error page). - Helped with #33672 (Force include https-everywhere in incremental mar update). - Responded to Thomas Klausner (NetBSD) on tbb-dev (Tor Launcher questions). This week/upcoming: - Review latest patch for #21952 (Onion-Location). - Review latest patch for #28005 (.onions in HTTPS-E). - Review rebased updater patches (#33533). - Revisit #30732 (“Your Firefox is critically out of date" banner). - Revisit #32418 (on every start TB complains that it can't update). - Investigate #29630 (TorBrowser creates empty directory in "/tmp”). sisbell: Last Week: #33685: zlib support for Android (in review) #31499: Update libevent 2.1.11: tested across platforms, don’t need osx path with latest (in review) #28765: Libevent for Android: update rbm,conf so we include options across all platforms (windows, Mac, linux). Verified building for each. (In review) #28766: tor build for android, includes zlib support (in review) Fenix: #33557: Android Toolchain for Fenix: fix bin path #33561: Upgrade openssl to use Android NDK 21 This Week: Follow up on reviews of Android Tor Support (priority) Fenix: #33564, #33565, #33562 -libevent, zstd, lzma for NDK 21 #33626: Add TBB project for GeckoView Jeremy Rand: Last week: - Got some test reports via r/Namecoin. Much of it was constructive. - Lower productivity than usual due to isolation precautions to avoid COVID-19. This week: - Relay r/Namecoin test reports to tor-talk mailing list, file bugs where appropriate, ask for additional clarification from testers where appropriate. - Try asking for more test reports via Twitter, maybe elsewhere in my social graph. boklm: Last week: - Made a patch for #33672 (Force include https-everywhere in incremental mar update) - Rebased patch for #25102 (Add script to sign nightly build mar files, generate update-responses xml and publish the new version) - Helped with new releases - Monitored blog comments This week: - Some reviews - Work on proposal for quilt workflow - Work on testsuite setup - Work on setup of automatic rebasing of tor-browser patches on mozilla-central - Help with getting rebased patches from #33533 building in tor-browser-build pili: Last week: - trac triage - Tor Browser release meeting - Started putting together Sponsor58 page for transition to Fenix: https://trac.torproject.org/projects/tor/wiki/org/sponsors/Sponsor58 - Started tagging S58 tickets: https://trac.torproject.org/projects/tor/query?sponsor=^Sponsor58&col=id&co… This week: - trac triage - S58 - Docshackathon - S27 March report sysrqb: Last week: - Release prep for 9.0.7 - Firefox bug - Chatted with sisbell about Fenix - Made progress on macOS signing/notarization - Investigated https-everywhere downgrade question This week: - Releasing 9.0.7, release prep 9.5a9, releasing 9.5a9 - Finally looking at acat's rebasing work? acat: Last week: - Revised #28005 (Officially support onions in HTTPS-Everywhere to use securedrop testing update channel.) - Revised #21952 (Onion-location) - Updated Onion-Location spec to match current implementation. This week: - Possibly revise #28005, #21952. - Try to get #33533 working in tor-browser-build (will try boklm suggestion) - Get browser unit tests working for #33533? ================================ Thanks, Matt

1 0

Tor Browser Team Meeting Notes, 16 March 2020
by Matthew Finkel 30 Mar '20

30 Mar '20

Hello everyone, We held a weekly meeting on 16 March, 2020. The meeting log is available at http://meetbot.debian.net/tor-meeting2/2020/tor-meeting2.2020-03-16-17.59.l… During the meeting we discussed how Javascript should be handled and disabled on the Safest security level. ================================ Week of March 16, 2020 Discussion: - Should we be using Trac’s merge_ready status for tickets for which review is complete? Who should change a ticket’s state to merge_ready? - Javascript configuration on Safest pospeselr: Last week: - release note reviews (#33534) - windows update/platform documentation updates This week: - finish release note reviews (#33534) GeKo: Last week: - not much done; a bit help with the JS bypass bug This week: - more design doc update (#25021) - test new mar signing key (#33173) - maybe working on reproducibility of lucetc (#33488) mcs and brade: Last week: - Code reviews. - Reviewed the manual update instructions, etc. for the TB 9.5a7 release. - Replied to email query from Guardian Project people r.e. implementing Moat. This week/upcoming: - More code reviews, including rebased updater patches (#33533). - Respond to review comments in #19251 (onion services error page). - Revisit #30732 (“Your Firefox is critically out of date" banner). - Revisit #32418 (on every start TB complains that it can't update). - Investigate #29630 (TorBrowser creates empty directory in "/tmp”). acat: Last week: - Reviews (#33482: Update about:tor donate string, #19251: TorBrowser might want to have an error page specific to when .onion links fail) - Made patch for #33342 (Disconnect search addon causes error at startup) - Revised #28005 (Officially support onions in HTTPS-Everywhere) to use securedrop testing update channel. This week: - Revise #21952 (Onion-location: increasing the use of onion services through automatic redirects and aliasing) to address review comments. - Whatever is most useful for Tor Browser ESR -> regular release migration (or Fenix): - Try to get a tor-browser-build for #33533 (Rebase Tor Browser esr68 patches on top of mozilla-central) - Take a look at fixing tests? - ... sysrqb: Last week: - Released 9.5a7, 9.0.6, and 9.5a8 - Investigated Javascript bug on Safest security level This week: - Close-out javascript bug - Release prep for 9.0.7 and 9.5a9 - Respond to sisbell regarding Fenix questions - Look at acat's work with rebasing patches boklm: Last week: - Tested updates in nightly builds: it seems to be working correctly - Opened upstream pull request for #33535 (Patch openssl to use SOURCE_DATE_EPOCH for copyright year) - Looked at possible workflow with quilt - Helped with new releases - Looked at blog comments This week: - Try to get rebased patches from #33533 building in tor-browser-build - Set branch for #25102 in needs_review (Add script to sign nightly build mar files, generate update-responses xml and publish the new version) - Work on testsuite setup - Work on setup of automatic rebasing of tor-browser patches on mozilla-central - Work on proposal for quilt workflow - Some reviews Jeremy Rand: Last week: - Relayed some Namecoin feedback from Twitter and LinuxReviews to tor-talk. - Posted on r/Namecoin asking for more feedback, hopefully some more feedback will trickle in soon. - Hacked around with #32355 some more. This week: - Wait for more feedback on the Namecoin integration in Nightly. - Maybe hack around with #32355 some more. sisbell: Last Week: - #33556: TBB for android-components - After integrating with fenix build, I identified a number of unneeded Mozilla project dependencies and removed them. Various plugin fixes. Package artifacts as maven repo. Cleaned up patches. I also identified a couple of areas further of investigation. - #33184: Support for fenix - various plugin fixes, removing of dependencies, now using android-component artifacts locally, learning build internals This Week: - #33184: Fenix - get complete build working (this will still use precompiled artifacts from Mozilla’s gecko view aar) - #33626: TBB for GeckoView - start setting this up so I can identify build dependencies for this (rust, clang). Open related issues. pili: Last week: - trac triage - Browser team February report This week: - trac triage - Tor Browser release meeting ================================ Thanks, Matt

1 0

This week, time zone + Americans = confused
by Roger Dingledine 29 Mar '20

29 Mar '20

Hi folks! Here is your notice that this week, if you have a meeting that involves UTC times and involves Americans, you should expect confusion. (The time in the US and maybe some other places just changed today, but UTC didn't.) Here is your chance to take this information and do something proactive and smart with it. :) I hear the Europeans will go through the reverse version of this confusion on March 29. Be safe, --Roger

1 1

Notes from Vegas Meeting MARCH 26 2020
by Erin Wyatt 28 Mar '20

28 Mar '20

Vegas Team Meeting notes March 26 2020 NEW BUSINESS + Gaba: tor releases: we are thinking on call them outside of the network team meetings and review each time with more people what is going in (similar than the Tor Browser release meetings). Thoughts? - We are going to bring this back to the network team and move forward with release planning meetings. + Pili: We are going to be implementing onion-location headers on our websites to take advantage of a new feature we will introduce into Tor Browser in an upcoming alpha release to redirect visitors using tor-browser to the .onion address. We should coordinate this work to happen on websites at the same time as we release Tor Browser Alpha and also to make a nice announcement about it. We would also like to reach out to some orgs who are operating onion services to let them know about this new feature. GENERAL NOTES GeKo 1. network health work is moving along 2. spent some time getting back to Coil and their issues with using Tor for Webpayments (spoiler alert: we found some weird breakae due to Cloudflare; following up on that this week) 3. more work on the licensing/copyright issue for TPI folks 4. getting back to onion service education coordination 5. H1 bug bounty fun Sarah 1. Major donor virtual happy hour tonight 2. Will follow up with 1:1s with attendees 3. Moving onto plans for April 13th foundation presentation 4. Working on projections for FY21 Antonela • 1. working on s30 user research, listening ICFP fellow interviews in Cameroon and Nigeria. Due covid-19 the scheduled interviews are going to 2. continue remotely • 3. planning remote user research for s9 • 4. working with onions in multiple salads, closing s27 • 5. moving forward with diogosergio's proposal for design git • 6. #docshackathon: working on having Tor Browser's new features highlights in a webpage • 7. tagging s58 ux issues Gaba • 1. DoS follow up on funding proposals • 2. Gitlab migration plans • 3. syncs with ahf & nick and follow ups • 4. tor releases: we are thinking on call them outside of the network team meetings and review each time with more people what is going in isabela: 1. getting ready for today's event and the follow up after that 2. following up with some discussions/email threads that I was behind w/ 3. preparing things for the next board meeting Steph 1. Preparing for today's event, adding new slides 2. Working with OTF Learning Lab 3. Press inquiries 4. Remote work and personal safety post published 5. Invited to do a podcast 6. Social media Mike: 1. HS DoS experiments and literature review 2. Employee peer reviews 3. Press inquiry help Alex: 1. Had 1:1:1 with Gaba and Nick. Some follow ups from that. 2. Had Gitlab meeting with Gaba where we went over the list of issues that remained and tried to make a plan. 3. GeKo and I started having weekly sbws meetings with Juga. 4. General development. 5. Concentration back to normal this week. Nick: 1. Bad concentration this week; but trying to get back into productivity. Experience has taught me not to try to force it too hard. 2. Trying to write end-of-month notes, and including the question "what is my job anyway". Let's see how that goes. Gus: 1. DocsHackathon week! If you want to join us, jump on #tor-www IRC channel! 2. Running new Outreachy project and onboarding new applicants 3. Network Health: worked with Steph to announce 0.2.9 and 0.4.0 rejection from the tor network 4. Drafting an email to contact our training partners Pili: 1. Starting to wrap up S27 and taking stock of what we have achieved. • - We are going to be implementing onion-location headers on our websites to take advantage of a new feature we will introduce into Tor Browser in an upcoming alpha release to redirect visitors using tor-browser to the .onion address. We should coordinate this work to happen on websites at the same time as we release Tor Browser Alpha and also to make a nice announcement about it. We would also like to reach out to some orgs who are operating onion services to let them know about this new feature. 2. Helping outreachy and GSoC candidates 3. Pushing github sponsors forward and some other github admin. 4. Trying to get Same-Origin Onion Certificates for Tor Onion Addresses scheduled and possibly funded. I need to write an email about this. 5. Docshackathon and other website work this week. 6. Setting up for S58 7. Planting lots of herb and vegetable seeds and obsessively watching for germination :) anarcat 1. whoa, weird color 2. investigated possible solutions for onion v3 deployment in our fleet, will require puppet development work 3. (basic) install of the new ganeti server with a single command, automation is starting to give us real benefits 4. started the migration of kvm3, you might have seen some tickets warning you about server moves, let me know if you have any questions 5. deployed a new IRC bot to automate IRC notifications for planned outages 6. did research on the possibilities hosting our own audio and/or video conferencing software in #33700 7. regular housekeeping (email aliases, code reviews, smartd SNAFU #33684 ewyatt 1. HR/Personnel Stuff 2. Still chipping away at things, trying to stay focused amid all the craziness Philipp 1. Made some progress on sponsor 30 deliverables 2. Found some time to help out volunteers Karsten: 1. Rewrote OnionPerf's tgen plots in seaborn and pandas (#33258). 2. Worked on various character encoding tickets (#24384, #21933). Charly 1. Working on some new documentation drafts with the help of gaba for meetings and organizing ourselves on the non-technical side 2. Trying to still meet with everyone on Vegas to get a sense of their action items needed from Isa 3. Slowly coming up with a system for organizing and integrating the tools we use like NextCloud 4. Getting ready for tonights event

2 1

Anti-censorship meeting notes, 26 Mar 2020
by Philipp Winter 26 Mar '20

26 Mar '20

Hi all, Here are our meeting minutes: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-03-26-17.59.html And here is our meeting pad: Anti-censorship work meeting pad -------------------------------- Next meeting: Thursday April 1st 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 meetings' notes can be found at: https://lists.torproject.org/pipermail/tor-project/ * GetTor's roadmap: https://gitlab.torproject.org/groups/torproject/anti-censorship/gettor-proj… * 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 ------------------------- --- March 26th 2020 -- ------------------------- == Announcements == * == Discussion == * Can we close https://trac.torproject.org/projects/tor/ticket/29863 (snowflake infra disk space monitoring) ? * What's there to do for https://trac.torproject.org/projects/tor/ticket/29274 (get developers using new PT alphas) ? == Actions == * == Interesting links == * https://uncensoredlibrary.com/en * https://geneva.cs.umd.edu/posts/iran-whitelister/ * https://github.com/SadeghHayeri/GreenTunnel * https://info.williamlong.info/2020/03/github-pages.html * reported TLS MITM of GitHub Pages in China == Reading group == * We will discuss "Detecting Probe-resistant Proxies" on April 2 * https://censorbib.nymity.ch/#Frolov2020a * 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-03-26): * Made decent progress on making BridgeDB report internal metrics (#31422). * Merged patch that made docker obfs4 image support docker-compose to (re-)deploy container. Thanks to thymbahutymba for the patch! * Spent a lot of time debugging the failure that resulted from my own creation (#33709). * Merged #31967, thanks to agix for the patch! * Fixed and merged #30317. * Implemented #33631. * Revised #30941. Next week: * Write a summary of our current BridgeDB distribution mechanisms and brainstorm new ones * Pay attention to volunteer work (help agix with BridgeDB reviews; thymbahutymba with docker; Sergey with https proxy) * Make BridgeDB report internal metrics (#31422) * Catch up on RACE; in particular wrt obfs4 improvements Help with: * https://trac.torproject.org/projects/tor/ticket/30941 Gaba: () Last week (2020-03-26): * not much related to anti-censorship This week (planned): * not much related to anti-censorship cecylia (cohosh): last updated 2020-03-26 Last week: - Updated Snowflake license (#33637) - worked on learning about Debian for Snowflake (#19409) - chipped away at updating the debian obfs4proxy package (#33736) - travis fixes for #33593 - lots of grant writing, the grant seems pretty much finished! - lots of gsoc things, reviewed proposals, talked to applicants - created #33740 - reviewed #33631 and #30317 - read up on history of #33693 This week: - Resume obfs4 and snowflake tests (#31701, #32657, and #32545) - see if i can help push snowflake for android along (#28672) - write a patch for #33693 - look into proxy issues (#33666) - take a look at reviving the twitter responder in GetTor (#33036) Needs help with: juggy : 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-03-26 Last week: - announced snowflake-turbotunnel packages built on 9.5a8 (#33519) - https://lists.torproject.org/pipermail/anti-censorship-team/2020-March/0000… - discussed snowflake client metrics (#33693) - security upgrade of snowflake bridge (#33644) - closed ticket for multiple SOCKS connections in turbotunnel snowflake (#33519) - reviewed unsafe logging patch (#33665) - investigated effects of missing client_ip at snowflake bridge (#33157) - https://lists.torproject.org/pipermail/metrics-team/2020-March/001139.html Next week: - file ticket for snowflake-turbotunnel merge - share access to the snowflake broker CDN configuration (#30510) Help with: cjb: 2020-03-26 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-03-26 Last week: - Finally patched #31967 - Finished the project proposal Next week: - Patch #31426 - Patch #33647 Help with: - catalyst: 2020-03-19 last week: - worked on #5304 (Obfsproxy should respect OutboundBindAddress in torrc) this week: - more work on #5304 and other s28/s30 tickets thymbahutymba: 2020-03-23 Last week: - CI/CD using github actions. - docker-obfs4-bridge CI/CD (testing and multiarch-testing branch) with release on hub.docker.com. Next week: Help with: - How should work (be triggered) the release of different arch images? 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

1 0

Metrics Meeting Notes, March 26th 2020
by Gaba 26 Mar '20

26 Mar '20

Hi! We had our weekly metrics team meeting today. The next one is going to be on April 2nd at 1430 UTC and it will be a retrospective and roadmap update. The pad for the meetings in 2020 is at https://pad.riseup.net/p/tor-metricsteam-2020.1-keep The agenda and notes for today is here: ----------------------------------- Agenda Thursday, March 26th, 15 UTC ----------------------------------- Time tracking (karsten) 1.8 Add CSV file export of graphed data (#33258) 0.7 Decode percent-encoded characters in qualified search terms (#24384) 0.5 Fix deserialization of UTF-8 characters in details statuses and documents (#21933) 0.3 Don't trust "bridge-ips" blindly for user number estimates (#18167) 0.1 Extend integration tests in metrics-test to also test Onionoo (no ticket) 0.1 Add Git repository containing lots of large files (#33692) 0.8 Other Time tracking (irl) 0.7 Tasks review / direct emails 0.1 Mailing lists 0.5 Migrate from GitLab CI to Travis CI on GitHub for metrics-cloud (#33713, #33714) 0.1 TorBulkExitList.py has wrong mime type (#33682) 0.2 Review, fix and/or ignore linter errors found by cfn-lint (#31414) Time tracking (dj) I have been asked to help out on a COVID-19 contact tracing app (making sure it is as privacy preserving as possible) This has limited my time for Tor related stuff last week / the coming week, but should clear up after that Time tracking: weeks, months, quarters, years (karsten) New Onionoo backends (irl) Suggest holding off for a bit while we figure out #33733 Service documentation (irl) Exit Scanner, Check, Onionoo, Monitoring Need SSH keys Reviews (karsten) We said before that first meeting of April will have Roadmap update and Retrospective. That is next meeting. It will be on Thursday, April 2 at 14:30 UTC. more topics here Log: http://meetbot.debian.net/tor-meeting/2020/tor-meeting.2020-03-26-15.01.log… -- Project Manager: Network, Anti-Censorship and Metrics teams gaba at torproject.org she/her are my pronouns GPG Fingerprint EE3F DF5C AD91 643C 21BE 8370 180D B06C 59CA BD19

1 0

Communications Report: January & February 2020
by Stephanie A. Whited 24 Mar '20

24 Mar '20

Hello Tor, Since the beginning of the year, we've been working with OTF Learning Labs to create new materials for debunking the dark web and promoting onion services. These are still in process. We've been working with the fundraising team to create new materials and prepare for events which are moving online. In January, we published a comprehensive review of press Tor received last year (in blog posts below). In February, Steph spoke on a Zeal community call about Tor and Walking Onions and responded to press inquiries from multiple outlets. Some of these correspondences are still open. Outreachy intern annalee_'s official internship has ended, but she will continue to work with us and is currently drafting a blog post. She helped us create a list of influencers, clean up blog tags, and clean up Steph's press list. Jan and Feb in links and stats: ## January = Blog posts = https://blog.torproject.org/tor-bug-smash-fund-progress https://blog.torproject.org/2019-campaign-wrapup-tor-take-back-the-internet = Twitter = https://twitter.com/torproject New followers: 3,537 Top tweets https://twitter.com/torproject/status/1212829700273426432 https://twitter.com/torproject/status/1221825005488488448 https://twitter.com/torproject/status/1222899806885957633 = Mastodon = https://mastodon.social/@torproject New followers: 350 = LinkedIn = https://linkedin.com/company/torproject New followers: 226 = Facebook = https://facebook.com/torproject New followers: 432 = Newsletter = https://newsletter.torproject.org/archive/2020-01-30-bug-smash-advocacy-wha… = Notable press = https://www.express.co.uk/life-style/science-technology/1227747/Android-upd… https://www.zdnet.com/article/50-orgs-ask-google-to-take-a-stance-against-a… ## February = Blog posts = https://blog.torproject.org/tor-village-iff-2020-call-proposals (event cancelled) https://blog.torproject.org/tor-media-2019 = Twitter = New followers: 4,835 = Top tweets = https://twitter.com/torproject/status/1233157310366855169 https://twitter.com/torproject/status/1227239767625977857 https://twitter.com/torproject/status/1230142134382211087 = Mastodon = New followers: 210 = Facebook = New followers: 348 = LinkedIn = New followers: 310 = Newsletter = https://newsletter.torproject.org/archive/2020-02-27-tor-in-the-news-we-are… = Notable press = https://techround.co.uk/interviews/interview-tor-project/ https://bitcoinmagazine.com/articles/2020-bitcoin-adoption-why-nonprofits-w… https://www.dw.com/en/tor-psiphon-signal-and-co-how-to-move-unrecognized-on… https://www.theverge.com/2020/2/21/21138403/tor-privacy-tools-private-netwo… https://computerworld.com.br/2020/02/24/8-etapas-para-ser-quase-completamen… -- 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>

1 0