- tor-project - lists.torproject.org

Anti-censorship meeting notes, 25 July 2019
by Philipp Winter 25 Jul '19

25 Jul '19

Here are our meeting notes: http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-07-25-16.59.html Here is our meeting pad: ANTI-CENSORSHIP work meeting pad -------------------------------- Next meeting: Thursday July 25th 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/… [View More]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 * Hiro is currently experimenting with gitlab. * Tickets that need reviews: https://trac.torproject.org/projects/tor/query?status=needs_review&componen… --------------------------- ---- 25th July 2019 ---- --------------------------- == Announcements == * == Discussion == * https://dip.torproject.org/anti-censorship/state-of-censorship/blob/master/… * Snowflake servers being blocked by Safe Browsing (#31230) == Actions == * == Interesting links == * == 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-07-25): - Deployed in-progress BridgeDB metrics patch to see if it suits our needs + Stumbled upon numerous bugs, many of which in BridgeDB - Started working on PT spec improvements + https://trac.torproject.org/projects/tor/ticket/29285#comment:5 has become canonical list of spec issues + For now, based on our 1.0 spec, and hopefully find a way to merge it with the 2.x spec + https://dip.torproject.org/phw/torspec/tree/feature/29285 (work in progress) - Will attend OTF summit in Taipei + Hopefully will push forward the "help NGO with private bridges" topic - Filed #31228 for having a single Tor instance support, say, more than one obfs4 instances - Resurrected #29480 to expose BridgeDB's assignments file again + Would allow bridge operators to see what bucket their bridge is in - Updated obfs4 setup guide with notes on how it takes a while for a bridge to see traffic Next week: Help with: - Help me improve https://dip.torproject.org/anti-censorship/state-of-censorship/blob/master/… Gaba: (updated ) Last week (): This week (): * 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-07-25 Last week: - More PETS and travelling and recovering from travel - worked on #31100 - review of #27385 This week: - snowflake dogfood - check in on pion proxy, and work on windows build (#28942 and #28942) - sequencing layer for snowflake (#29206) - prepare for CitizenLab Summer Institute Help with: - review of #31100 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-07-25 Last week: - just some patch reviews (#31126, #31203) Next week: - revisions to #30310 - start looking at the suggestions in #31109 - add a build step / documentation for code reuse in cupcake - review of #31170 Help with: - review of #27385 dcf: 2019-07-25 Last week (since 2019-06-27): - merged a compatibility fix for the Snowflake websocket server (#30998) - closed a packaging issue in go-webrtc (not our bug, https://github.com/keroserene/go-webrtc/issues/89 ) - made a Firefox account for Snowflake add-on (#30931) - reviewed port of proxy-go to pion (#28942) - reviewed draft of Snowflake session layer (#29206) - published sanitized pre-sanitization Snowflake broker logs (#30731) - reviewed proxy-go test code (#30867) - reviewed the CoffeeScript removal patch (#30933) - fixed bugs in query string parsing in Snowflake proxy, thanks arlolra for review (#31126) - started dealing with Snowflake infrastructure domains being blocked by Safe Browsing (#31230, #31231, #31100) - Tor meeting, attended these anti-censorship sessions: - https://trac.torproject.org/projects/tor/wiki/org/meetings/2019Stockholm/No… - https://trac.torproject.org/projects/tor/wiki/org/meetings/2019Stockholm/No… - https://trac.torproject.org/projects/tor/wiki/org/meetings/2019Stockholm/No… - https://trac.torproject.org/projects/tor/wiki/org/meetings/2019Stockholm/No… - https://trac.torproject.org/projects/tor/wiki/org/meetings/2019Stockholm/No… - mostly implemented a dark mode in the Snowflake addon (#31170) - posted/archived stuff related to the Kazakhstan HTTPS MITM - looked into the status of IPv6 for the Snowflake broker (#31203) - fixed bugs in Parse.byteCount in the Snowflake addon, thanks arlolra for review (#31203) - reviewed a Snowflake proxy localization patch (#30310) - reviewed a draft of the Emma lightweight censorship analyzer (#30794) - Metrics Timeline maintenance Next week: - mostly offline, however hopefully experimenting with QUIC AMP etc. - review #31100 Help with: - looks like dark mode will require icons that work on both light and dark (#31170) [View Less]

1 0

Tails report for June 2019
by sajolida 24 Jul '19

24 Jul '19

https://tails.boum.org/news/report_2019_06/ Releases ======== * Tails 3.14.1 was released on June 20 (emergency release) to fix a critical security vulnerability in the JavaScript engine of *Firefox* and *Tor Browser*. https://tails.boum.org/news/version_3.14.1/ * Tails 3.14.2 was released on June 20 (emergency release). to fix a critical vulnerability in *Tor Browser*, a *sandbox escape* that we couldn't fix in time for 3.14.1. https://tails.boum.org/news/version_3.14.2/ * … [View More]Tails 3.16 is scheduled for September 3. Code ==== - We published a new version of the verification extension with a non- minified Forge library, as per an updated Mozilla policy. (#16686) Documentation and website ========================= - We tested all our documentation against the beta version of Tails 4.0, based on Debian 10 (Buster) and started fixing it. Infrastructure ============== - Our web translation platform reached an important milestone: translations done there will now automatically appear on the Tails website within hours. Expect a more detailed announcement and documentation for translators soon! :) https://translate.tails.boum.org/ - As part of our ongoing effort to migrate to better maintained Puppet modules, we ported our infrastructure to puppetlabs-apt. (#15510) - We programmed an automated reminder to send our Code of Conduct to all our public mailing lists every 3 months. Funding ======= - We applied to the Mozilla Open Source Support to work on: - Improve Upgrades (#8415 and #15281) - Support Secure Boot (#6560) - Migrate to GitLab (#15878) https://www.mozilla.org/en-US/moss/ - We applied to the ISC Project to: - Explain better what Tails is (#9814) https://www.iscproject.org/technology-grants - We improved the visibility of the "*Other ways to donate*" on our donation page. (#16170) Outreach ======== Past events ----------- - Estrella Soria gave a workshop about Tails from a cyberfeminist perspective on June 18 in the Virgen de los Deseos social center in La Paz, Bolivia. https://twitter.com/tecnochamana/status/1141018007281573889 - Another Tails workshop was held in Guadalajara, Mexico on June 29, as part of the 'Cuidarnos en red(es)' day of Digital self-defense at Huizache: https://mastodon.social/@noticiasdeabajo/102279012433478653 Translations ============ ## All the website - fr: 90% (5054) strings translated - es: 52% (2911) strings translated - de: 41% (2303) strings translated - it: 35% (1961) strings translated - fa: 32% (1806) strings translated - pt: 26% (1464) strings translated Total original words: 58995 ## Core pages of the website https://tails.boum.org/contribute/l10n_tricks/core_po_files.txt - fr: 97% (1736) strings translated - es: 79% (1420) strings translated - de: 68% (1228) strings translated - it: 65% (1161) strings translated - pt: 46% (820) strings translated - fa: 35% (626) strings translated Total original words: 16629 Metrics ======= * Tails has been started more than 751 230 times this month. This makes 25 041 boots a day on average. * 8018 downloads of the OpenPGP signature of a Tails USB image or ISO from our website. -- sajolida [View Less]

1 0

S27: Onion Services meeting this week: Tuesday 23rd July @ 15UTC
by Pili Guerra 23 Jul '19

23 Jul '19

Hi everyone, This is a reminder of the next Onion Services meeting happening this week on Tuesday 23rd July at 15UTC on #tor-meeting. We hope to see you there. Thanks! 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

Network team meeting notes, 22 July 2019
by Nick Mathewson 22 Jul '19

22 Jul '19

Hi! The IRC logs from our weekly meeting are available at http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-07-22-16.59.html Below are the contents of our pad. = Network team meeting pad! = This week's team meeting is at Monday 22 July at 1700 UTC on #tor-meeting on OFTC. We have changed the day from Tuesday to Wednesday. July schedule: * Wednesday 3 July 2300 UTC - Changed Day! * Monday 8 July at 1700 UTC * (In-person meeting 12-14 July) * Monday 22 July 1700 … [View More]UTC * Monday 29 July 1700 UTC Welcome to our meeting! First meeting each month: Wednesday at 2300 UTC Other meetings each month: Mondays at 1700 UTC until 3 November 2019, when daylight saving time changes On #tor-meeting on OFTC. (This channel is logged while meetings are in progress.) (See https://lists.torproject.org/pipermail/tor-project/2017-September/001459.ht… for background.) Want to participate? Awesome! Here's what to do: 1. If you have updates, enter them below, under your name. 2. If you see anything you want to talk about in your updates, put them in boldface! 3. Show up to the IRC meeting and say hi! After each week's meetings, the contents of this pad will be sent to tor-project @ lists.torproject.org. After that is done, the pad can be used for the next week. == Previous notes == (Search the list archive for older notes.) 3 June: https://lists.torproject.org/pipermail/tor-project/2019-June/002343.html 10 June: https://lists.torproject.org/pipermail/tor-project/2019-June/002354.html 17 June: https://lists.torproject.org/pipermail/tor-project/2019-June/002365.html 24 June: https://lists.torproject.org/pipermail/tor-project/2019-June/002373.html 3 July: https://lists.torproject.org/pipermail/tor-project/2019-July/002389.html 8 July: https://lists.torproject.org/pipermail/tor-project/2019-July/002390.html In-person meetings: https://trac.torproject.org/projects/tor/wiki/org/meetings/2019Stockholm/No… == Stuff to do every week = * Let's check the 0.4.1 release status page. See https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/CoreTor… (This page automatically shows the latest trac ticket status.) * Let's check and update the roadmap. What's done, and what's coming up? We're using a kanban board: https://storm.torproject.org/shared/_mx8PMGOHFBOximocl1gy3COvhLPr6k3Ja7JA1v… Click on 'all boards' and then the network team one. Filter by your name and check the 'in progress' column is correct. * Check reviewer assignments! How reviews from last week worked? Any blocker? Here are the outstanding reviews, oldest first, including sbws https://trac.torproject.org/projects/tor/query?status=needs_review&componen… Any blocker from last week? == Reminders == * Remember to "/me status: foo" at least once daily. * Remember that our current code reviews should be done by end-of-week. * Make sure you are in touch with everybody with whom you are doing work for the next releases. * Remember to fill up the 'actual point' field when you close a ticket. We need those to calculate velocity. * Check other's people call for help in their entries. When you are overloaded, it is ok to say "no" to things. And it is ok to reschedule things. ------------------------------- ---- 22 July 2019 ------------------------------- == Announcements == reminder: catalyst will be AFK Jul 29 through Aug 18 nickm will be AFK August 12 through August 16 ahf will be AFK all of August for BornHack and CCC Camp, but will be on IRC every now and then == Discussion == Rotation updates: See https://trac.torproject.org/projects/tor/wiki/org/teams/NetworkTeam/TeamRot… CI/coverity catalyst -> catalyst & teor coverity the defect browser was down last week; it seems to be back now (Waiting on update after merging coverity fixes: Coverity does not seem to have noticed 30150 yet.) Looking at coverity -- it seems our builds may have been stuck. I've cancelled the stuck builds. Also, they say they are going to have a planned outage to upgrade their backend, starting today and lasting about 3-4 days. Friday would be a good day to have another look. -nm stuff got unstuck on 28 Jun or maybe earlier? -catalyst Correct; we've been getting updates since then. I opened tickets for the first day's updates; there are more I hope to get to soon. jenkins some intermittent failures that could be network-related Travis teor did some work on stem failures, we need to add a control message trace to tor to diagnose (#30901) waiting for catalyst's advice, because they are refactoring this code Appveyor Bug triage ahf -> asn Things are looking OK asfaik. catalyst asks if we want to re-evaluate https://trac.torproject.org/projects/tor/ticket/31081 or stay with "make the spec match the code" Please give feedback on proposal 306: IPv6 "Happy Eyeballs" for Tor clients https://lists.torproject.org/pipermail/tor-dev/2019-June/013907.html == Recommended links == == Updates == Name: Week of XYZ (planned): - What you planned for last week. Week of XYZ (actual): - What you did last week. Week of ABC (planned): - What you're planning to do this week. Help with: - Something you may need help with. PLEASE DO NOT BULK-DELETE THE OLD ENTRIES! Leave the "Planned" parts! Leave the parts for last week and this week! gaba: Last week (actual): This week (planned): . tor meetup Help with: teor: (offline at the usual meeting time) Week of 8 July (actual): Urgent: - Taking time off before long-haul travel and Stockholm meeting - Travel preparation - Ticket triage - Proposal responses Backlog: - code reviews - add tor controller trace logging to diagnose stem hangs (#30901) - disown or quick fix the rest of my tickets: - I should only be owner on tickets I will work on in the next month - fix sponsor on tickets? - CI for pluggable transports (#29267) <-- this is priority over #29224 and 29227 in the roadmap --gaba - Update EndOfLifeTor.md with our latest end of life process (#30839) - document disabled CI (#30745) - triage remaining backport backlog Nick: Week of 15 July (actual): - Attend PETS reception - Take it easy post-meeting - Travel home - More work on refactorings for 29211 (config.c redesign) - Several practracker improvements - Catch up on email and expenses Week of 22 July (planned): - Review and merge - Try to release 0.4.1.4-rc - Backports for 0.4.0.x? - More 29211 work (config.c): can I get all the backend code written? - Reply wrt proposal 295 - Reply wrt proposal 306 - More practracker fixes, time permitting Mike (afk: jetlagged and recovering from 12 days travel+work) catalyst: week of 07/08 (2019-W28) (planned): - travel prep - Stockholm meeting week of 07/08 (2019-W28) (actual): - travel prep - Stockholm meeting week of 07/15 (2019-W29) (actual): - travel - time off to recover from travel week of 07/22 (2019-W30) (planned): - Season of Docs selection due 07/23 - expense reports - follow up from Stockholm meeting - hand off some reviews to teor - working partial days this week asn: Week of 07/01 (actual): - Pushed #26294 branch to needs_review. - Some more thoughts on the DoS thread. - Some more thoughts on scaling thread. - Lots of hackerone activity/triaging/rewarding (#31022, #31001, plus one more not yet filed) - Finished review/merge backlog. Week of 07/08 (planned): - Triaged a few wtf-pad related tickets but need more work: #30649, #31098. - Tor meeting in Stockholm. - Allhands expenses ahf Last N-weeks: - Send vacation info to the network team ML. - Traveled to Stockholm, had a good time with you all. Week of 22/7: - Do reimbursement - Go over all notes from Stockholm that seems relevant to me. - Follow up on pre-Stockholm items: - Continue figuring out some info on a potential Danish funder. - Continue with #5304 and #28930 dgoulet: (offline) Week of 07/01 (actual): - s27 DoS work: #15516, #24963/#24964 - Tor-dev update on the DoS experimentation: https://lists.torproject.org/pipermail/tor-dev/2019-July/013923.html Week of 07/08 (planned): - Stocklholm. - Need to address urgently a series of pending bad-relays email. [View Less]

1 0

June 2019 report for the Tor Browser team
by Georg Koppen 19 Jul '19

19 Jul '19

Hello! In June we released 5 Tor Browser releases: 8.5.1[1], 9.0a2[2], 8.5.2[3], 8.5.3[4], and 9.0a3[5]. The last three were due to two chemspill releases Mozilla managed to do while they had their All Hands meeting in Whistler (Canada) and a group of Tor people attended as well, to discuss both further uplift + fingerprinting work and performance + scalability improvements. Tor Browser 8.5.1 was the first bugfix release in the 8.5 series which fixed minor shortcomings in 8.5 and defended … [View More]

1 0

Anti-censorship meeting notes, 18 July 2019
by Philipp Winter 18 Jul '19

18 Jul '19

Here are our meeting logs: http://meetbot.debian.net/tor-meeting/2019/tor-meeting.2019-07-18-17.00.html And here is our meeting pad: ANTI-CENSORSHIP work meeting pad -------------------------------- Next meeting: Thursday July 18th 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 … [View More]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 * Hiro is currently experimenting with gitlab. * Tickets that need reviews: https://trac.torproject.org/projects/tor/query?status=needs_review&componen… --------------------------- ---- 18th July 2019 ---- --------------------------- == Announcements == * Added Stockholm meeting notes to: https://trac.torproject.org/projects/tor/wiki/org/teams/AntiCensorshipTeam#… == Discussion == * https://dip.torproject.org/anti-censorship/state-of-censorship/blob/master/… * Is this a good start? == Actions == * == Interesting links == * https://www.swadeshimedia.in/spring-epfl-lightnion/ == 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-07-18): * Working with obfs4 bridge operators who couldn't get their bridge to run. * Filed OONI ticket to have OONI measure reachability of STUN servers. * Started working on a repository that keeps track of what's necessary to connect to Tor in censoring countries. * https://trac.torproject.org/projects/tor/ticket/28531 * Filed a ticket to get a new default obfs4 bridge running. * https://trac.torproject.org/projects/tor/ticket/31164 * Filed a ticket to have www services of anti-censorship team monitored. * https://trac.torproject.org/projects/tor/ticket/31159 * Wrapped up creation of docker image. * https://trac.torproject.org/projects/tor/ticket/30708 * Filed ticket for an easy-to-use bridge setup meta package in Debian. * https://trac.torproject.org/projects/tor/ticket/31153 * Read Matic et al.'s NDSS'17 paper and sent summary to anti-censorship-team@. * https://lists.torproject.org/pipermail/anti-censorship-team/2019-July/00002… * Moved forward with understanding the "long tail" of network traffic (required for Sponsor 28). * Attended Tor dev meeting in Stockholm. * Sponsor 30 kick-off meeting. * Had a chat with Antonela about UX challenges wrt bridges. * Had a chat with Hiro about the future of GetTor. * Had a chat with Nathan and Benjamin about ORbot and OnionBrowser. * Had a chat with Tails folks about maintenance of obfs4proxy package. * Had a chat with David about PT v2.0 and snowflake. * Attended session on anti-censorship rapid response. * Attended session on how to attract more snowflakes. * Attended session about Tor's upcoming dev portal. * Roadmapping. Next week: Help with: Gaba: (updated ) Last week (): This week (): * 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-07-18 (will try to attend but still at PETS) Last week: - Tor Meeting and PETS - deployed a proxy-go instance that uses pion/webrtc library (#28942) - updated snowflake bridge survival guide instructions for new proxy-go instances - starting sorting out webextension infinite loop bug (#31100) This week: - Still at PETS and then travelling/recovering from travel - finish up addressing issues with #31100 - more dogfood catalyst: week of 06/13 (planned): - mostly focusing on sponsor31 week of 06/13 (actual): - cleaned up (and relinquished) more of my owned tickets - mostly sponsor31 stuff (control.c refactoring) week of 06/20 (planned): - mostly sponsor31 week of 06/20 (actual): - mostly sponsor31 - helped ahf with some bootstrap stuff week of 06/27 (planned): - mostly sponsor31 arlolra: 2019-06-27 Last week: - a bit of snowflake webextension This week: - getting the webextension published (#30931) Next week: - review #30934 Help with: - fixing our websocket server implementation (#30998) [View Less]

1 0

April Fundraising Report
by Sarah Stevenson 17 Jul '19

17 Jul '19

Hello - below is the Fundraising team’s April update. Let us know if you have any questions! ## Grants The biggest news in the world of grants is that our proposal to DRL for anti-censorship work was approved. Al also submitted a proposal to CS Fund/Warsh Mott Legacy, Rights, and Governance that was declined and a proposal to Wallace Global on which we are still awaiting a response. We are also waiting to hear a response back from the DIAL Open Source Center about funding for the ESR … [View More]migration. In these monthly updates we will begin informing you about proposals we intend to submit in the next month in case anyone might have comments or concerns about the funders, or connections that might help our chances. As a reminder, our grant work flow can be found on the Fundraising Team Wiki[1]. We plan to submit proposals to Media Democracy Fund, who have been funding us for several years now, the Reva and David Logan Foundation, NLnet, and The Charles Léopold Mayer Foundation for the Progress of Humankind. We welcome any and all feedback sent to grants(a)torproject.org <mailto:grants@torproject.org>. We have been working to better communicate with our grant program officers and, to that end, we sent our first Sponsors Newsletter[2]. The intent is to demonstrate the full impact of our work to funders who may only be familiar with specific projects. We plan to send the next newsletter after the meeting in Stockholm. Additionally, Isa and Sarah met with Michael Brennan from the Ford Foundation and are planning a follow-up meeting in June with others from Ford. ## Small Foundations / Major Donors In an effort to get lapsed major donors and small foundations to donate again, we sent a solicitation letter via postal mail. We included a nice insert, created by Steph, featuring Tor stories that we plan to use for acknowledgements that need to be sent in the mail. We’ve seen a small response. We sent a version of the Sponsors Newsletter to current major donors to let them know how impactful their giving has been. ## Monthly Giving / Defenders of Privacy We launched a donation page dedicated to monthly giving[3]. This will allow us to promote the Defenders of Privacy program and try to convert one-time givers into monthly givers. We currently have 334 people in the group who generated $3,438 in income in April. We will send a three-part series of emails to one-time givers beginning in May and will offer a new sticker or patch (yet to be determined) in the second invite. I will keep you updated on the growth of this program. ## Website Since the new website was launched at the end of March, we have been tracking the number of unsolicited donations from the website. That number decreased about 30% with the new site design. Our theory was that the Donate button was less noticeable, so at the end of April, Antonela changed the design and added a yellow Donate button in the header and footer. Since that change was made, donations are now almost double what they were per day before the website redesign. ## Administrative We have been working with a company called Labyrinth on making sure we are registered to fundraise in each of the 50 US states. This is a requirement that can result in fines if you are not properly registered. The process is a bit arduous since each of the states has different requirements. Thankfully, the process is almost complete for this year. ~ Fundraising Team [1] https://drive.google.com/file/d/17jFJ_cFoB2FRKFhoo3on3SChMKSJPzhF/view <https://drive.google.com/file/d/17jFJ_cFoB2FRKFhoo3on3SChMKSJPzhF/view> [2] https://crm.torproject.org/civicrm/mailing/view?id=158 <https://crm.torproject.org/civicrm/mailing/view?id=158>[3] https://donate.torproject.org/monthly-giving <https://donate.torproject.org/monthly-giving> [View Less]

1 2

Damian's Status Report - June 2019
by Damian Johnson 13 Jul '19

13 Jul '19

Hi all! Sadly not much worth noting on the tor front. I have a feature branch in the works [1] that should hopefully be ready to announce later this month. https://blog.atagar.com/june2019/ Cheers! -Damian [1] https://gitweb.torproject.org/user/atagar/stem.git/log/?h=collector

1 0

OONI Monthly Report: June 2019
by Maria Xynou 10 Jul '19

10 Jul '19

Hello, In June 2019, the OONI team published two research reports, released OONI Probe mobile 2.1.0, improved analysis capabilities through a series of improvements to the OONI data processing pipeline, and continued to make progress on the development of the OONI Probe desktop apps and probe-engine. We also continued to work towards the stable release of the revamped OONI Explorer. ## Report on Facebook live-streaming interference in Jordan In collaboration with our Jordanian partners, … [View More]

1 0

Tor's Defenders of Privacy Program
by isabela 09 Jul '19

09 Jul '19

Hello Tor! Today we launched our Defenders of Privacy program, a monthly giving program designed to honor donors who make privacy a priority. We have so many people who support us with donations, and some folks has signed up to give a small amount every month. These steady contributions allow us to make long-term plans and to be agile with our development. Because this type of contribution is so important to us, and for privacy, we decided to honor these donors by giving them the ‘Defenders … [View More]

1 0