This was originally sent to tor-meeting@, but is being forwarded here by
request. Hope it is useful! =)
-------- Original Message --------
Hi all,
At the meeting, there was a discussion on how people can learn how to
give talks -- particularly if they have some experience but want to
refine their skills a bit. I'm not sure if there was a proper
report-back on it, but here are some suggestions on getting experience:
1) Join Toastmasters or similar clubs
Toastmasters costs money ($128/year in Boston), but there are lots of
similar clubs on Meetup and around universities that don't cost anything
and are a great way to get over fear of speaking and get feedback on
technique.
2) Prepare and give a talk to your cat
Or by yourself. Presenting your talk to yourself (out loud) is a great
way to figure out what works and what doesn't, or what passages just
need more work. It's also good to do this before giving a proper talk
-- not just for practice, but also to make sure that your talk is within
time limits.
3) Give talks at small events that aren't recorded
Presenting a lightning talk at a hackerspace or small conferences can be
a low-stress way to get experience.
4) Hard Mode
Give talks that *are* recorded, and pick apart your performance later by
watching that talk on YouTube. I wouldn't say I *recommend* this, but
have definitely done it ;P
MOAR TIPS:
http://web.mit.edu/urop/resources/speaking.htmlhttps://www.toastmasters.org/Resources/Public-Speaking-Tips
--
Accept what you cannot change, and change what you cannot accept.
PGP: 0x03cf4a0ab3c79a63
Notes are at https://storm.torproject.org/grain/Xyq4zgG9PZop5SxaG8yPoj
# Glossary
* Work has been done on glossary in the last few weeks
https://storm.torproject.org/shared/wjpmSOq0ku3zZEppCdPV_xXr4mXPxjKvIH3PUyx…
* Almost done, needs reviewing
* Should try to make less jargony and easier to understand
# Support desk stopgap efforts
* support.torproject.org is in the works, RT help desk being
disabled
* Help desk getting too many requests, but now all users emails
execdir@ for help
* Support messages being forwarded to a mailing list staffed by
Phoul + flexlibris
* Only meant to be a temporary stopgap
* No current timeline on the portal
# Tor browser manual progress
* Manual has been edited
* Ready apart from a few screenshots that have to be retaken
* Next steps are publishing blog post and opening up translations
# What we need help with
* Support portal templates (some out of date, some unfriendly,
and some not covered)!
# T-Shirt update
* Jon has processes in place and want to see if he can keep up on
his own - doesn't want help
* Don't want to start sending emails about tshirts while not being
able to keep up with backlog
* Not 100% on size of backlog - maybe hundreds?
* Emails operators to say that we're working on backlog and thinking
of other stuff
* Possibility of automating (enter fingerprint to check eligibility)
* Automatically sending emails to eligible operators.
* Possibility of editing the Tor Weather code to do this
* Handing out tshirts at 33C3/other cons to people who don't wish to
give address - ask arma2
--
pgp: 0xBD26F0F8029825DD
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
See this posting for context:
https://lists.torproject.org/pipermail/tor-project/2016-April/000223.html
Notes for October 13 2016 meeting:
Georg:
1) Worked on the upcoming proposal for OTF
2) SponsorU items
3) Whom do we plan to have on stage for a possible 33c3 talk?
4) Helped a bit with the meeting with the frontend dev for the
security slider port to Orfox
Nick:
1) Very soon, 0.2.9 will be in testing. We will need it tested!
Isabela will send out requests and appeals. Please help!
2) Not much else to report.
Kate:
1) Following up on multiple articles in progress about Tor (good news
articles).
2) Following up on Seattle meeting action items
3) Holiday plan for teaching family and other totally nontechnical
people about Tor (Each one teach five).
4) Sent Q and A to reporter who is covering trump and uses SecureDrop.
5) Tweaking Wendy's privacy op-ed.
6) Met with reporter and all he wanted to talk about was fixing Tor
Messenger bug b/c he loves Tor Messenger.
Mike:
1) The blog is being converted. Performing complicated comment
merge+extraction will cost more $$. Do we really need those comments?
(We probably should have reverted to the dump where they still existed
if so, so I guess not?)
2) Android is still a mess. The CopperHead folks are upset about
Android 7.1 and the semi-discontinuation of the current devices. This
may delay things, but they think if we launch Tor Labs soon, it will
be OK. I told them I am shooting for end-of-month.
Arturo:
1) Posted OONI UX designer job on the Tor website and open source
design
(https://www.torproject.org/about/jobs-ooni-ux-designer.html.en,
https://github.com/opensourcedesign/jobs/pull/112). Please share and
spread as much as you can.
2) Resolved some of the last critical bugs for the 2.0.0 release, so
that is likely to be released very soon now.
3) We would like to have a OONI internal meeting mid November + 2 days
of Open Hack day. This would allow us to meet the new developer in
person and do some better coordination.
4) We published a long report on internet controls in Zambia during
the elections:
https://ooni.torproject.org/post/zambia-election-monitoring/
5) The 2.0.0 release of ooniprobe will have enabled by default a tor
deck, that will check to see if the meek domain fronts are working and
if plain tor is able to bootstrap properly.
6) Working on a report on internet censorship in Ethiopia.
Alison:
1) had a call with Maria to begin preliminary work on future
partnerships with OONI and the Community Team (for Rapid Response,
Outreach, etc)
2) support portal: still chugging along, will talk to Shari today
about getting the resources we need to make this happen
3) membership guidelines: waiting on Lunar's final notes and then will
send the doc to tor-internal@ to approve
4) been noticing/hearing from users about our woefully out-of-date and
misleading documentation. we should have a sprint to fix these. will
the website redesign help? should this happen before that?
5) where do we stand on the general contact email?
Karsten:
1) We're very close to merging and deploying data synchronization
between CollecTor instances. Finally!
2) Planning to ask devs to help with writing and testing CollecTor and
later Onionoo operation guides, though not before end of next week:
https://people.torproject.org/~karsten/volatile/metrics-operation-guides-20…
3) We realized that metrics-lib builds are reproducible, and we're
considering to publish a guide for reproducing them, to have multiple
people building and signing releases, and to publish this as Good Tor
News later this year or in 2017.
Isabela:
1) Follow up with Adam on OTF reports and NCE
2) Follow up with OTF proposal v4 / deadline friday
3) Plan on sending out today a call asking help on testing core tor
releases / goal is to have a QA team that can help us with that on
every release / 0.2.9 will be a pilot
4) Met Thomas the dev who will do the orfox front end gig with us / we
will send him the contract asap and he should get started pretty soon
5) Great progress on security slider user experience on orfox / which
can be used on tor browser desktop as well / Linda is driving this
6) Preparing for Chile
7) Starting to collect stuff for Q3 report to sponsorS
8) all week next week at OTF summit
Roger:
1) CCC tickets: connect people who need them with people who have
tokens. I've done some of this connecting, and I'll do more soon.
People should let me know if they still need a ticket / if they have
an extra voucher.
2) NSF posters + slides: for the January NSF PI meeting, we need one
summary slide per NSF project, and we have five of them. Also an
optional poster. I'll be commandeering Tor people to help with those
in the coming week.
3) Rachel's NSF proposal: her sociology Tor+Wikipedia paper got
accepted, and now they plus Mako are writing an NSF proposal to
explore the
https://blog.torproject.org/blog/call-arms-helping-internet-services-accept…
topic further. I'm going to write them a letter of support on behalf
of Tor, but not be a co-proposer, because conflict.
4) Next dev meeting: Mar 12-16 is during swsx so it's a poor choice.
Next option we're looking at is Mar 23--27. Let us know if there's a
conflict.
5) Speaker's bureau: I filed a ticket:
https://bugs.torproject.org/20305 but there is no movement yet.
6) I'm talking to some professors about a new NSF proposal to fund a
research testbed Tor network, which could build from the testing Tor
network that dgoulet et al are operating. The proposal timing is not
good but maybe we'll try something anyway. I have Cass in the loop.
Shari:
1) trying to catch up after a week's vacation. :(
2) on the verge of hiring a chief financial and grants officer
3) working on getting end-of-year campaign ready
4) revising budget for otf proposal
5) finishing up with 990
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
iQEcBAEBCAAGBQJYBMiDAAoJEC3ESO/4X7XBYycH/iH12PocwTnQQAmQaru8MOWG
F7RjvNGZMsIcmdNfhAWFuvekrNeoCL00DugnLJU8+PCebrvFwY1VCjVjmmMQIGIx
XtOqEJDMXb0MSQjI8VQNn7nExuoHw6TQNQftfzuh70Xt8VMdGgMgTuIIuRykaWBF
Phrz4B+L28ChRmEXy09FwW60xpj2SDSDEwHHTKLGYQc1we+6DVZI7S1ohlN6LW8X
ADwi3llfYAJc+J3bN6KrE6nBtDuzKBQZgNsOZllFwHd5DfRfKATGzz3BVP77NBhi
D70PMRkutkxI+A3J26reMVyeTGJ8Xger02qOhPo6DdHddQUuyChhWQR721S7cig=
=YMid
-----END PGP SIGNATURE-----
FYI
-------- Forwarded Message --------
Subject: Tech For Justice Hackathon Invite
Date: Fri, 14 Oct 2016 10:47:39 -0500
From: Christy Leos <christy(a)internetbar.org>
To: nima(a)torproject.org
CC: Jeffrey Aresty <jeffaresty(a)internetbar.org>
Hello Nima,
My name is Christy Leos and I am the Director of Operations for Tech For
Justice. My boss Jeff Aresty mentioned meeting you at Rights Con and
discussing Tor and some of our projects as well.
I wanted to reach out and invite you to our upcoming virtual hackathon
techforjustice.org/legal-justice-hackathon. We would love to have you work
with us to create solutions; Tor's expertise and know how would be
extremely beneficial for the justice issues currently plaguing our
communities.
If you could share this information with your organization and its members,
that would be amazing. Please let me know if you have any questions or
would like more details.
Thank you for your time,
Christy Leos
*Director of Operations *
*InternetBar.org <http://InternetBar.org> Institute *
*The Houston Bar Center*
*723 Main St. Houston, TX*
361-220-8128
https://events.ccc.de/2016/09/01/call-for-participation-33rd-chaos-communic…https://events.ccc.de/2016/09/13/33c3-ticket-sales/
Congress is on track to sell out again this year.
We plan to have a bunch of Tor people there, so we can answer Tor
development and community questions for all the people who will have them.
So if you are planning to be there, be sure to make plans to get a
ticket!
Some of our friends at CCC still complain about last year when we
surprised them by wanting five tickets two weeks before the event.
Let's not do that again.
This month (October) is the best month for getting a ticket, since after
October everything gets messier.
Let us know if you will be going there as a Tor person and you need a
ticket. Let us know early and often until it is resolved!
Thanks,
--Roger
> Begin forwarded message:
>
> From: پیوندی <rastin(a)tuta.io>
> Subject: Research about Tor Security Problem
> Date: October 14, 2016 at 7:52:05 AM PDT
> To: <execdir(a)torproject.org>
>
> hi
> A lot of research has gone into improving the Tor network, but its use of DNS has received little attention. In this research project, we set out to learn how DNS can harm the anonymity of Tor users, and how adversaries can leverage the DNS protocol to deanonymize users.
>
> website:
> https://nymity.ch/tor-dns <https://nymity.ch/tor-dns/>
>
> Report:
> https://nymity.ch/tor-dns/tor-dns.pdf <https://nymity.ch/tor-dns/tor-dns.pdf>
>
>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256
See this posting for context:
https://lists.torproject.org/pipermail/tor-project/2016-April/000223.html
Notes for October 6 2016 meeting:
Roger:
1) We added Arturo to the Vegas team! Now we will have more chances to
get OONI better integrated into the rest of the Tor work. I am
especially excited to get them thinking more about Tor blocking, and
about tools to more efficiently figure out *how* Tor is blocked in a
given place.
2) I heard Shari suggest "Amsterdam, March" for our next dev meeting.
So I sent that mail out to the tor-meetings list. March 12-16, with
optional hackdays after that, looks promising. How to proceed?
3) Any news on our blog rewrite contract?
4) Did you know we submitted a proposal to the DRL-metrics
call-for-proposals? I only learned it accidentally. Is there some more
consistent mechanism we should use for letting people know about such
things? Maybe this particular one will get better now that Arturo is here.
5) Similarly, did you know we picked a services administrator? I only
learned it accidentally last week. I bet many people still don't know.
6) We should set up a "speakers bureau" to coordinate around all the
talks we do and are invited to do. Who should run it? Dgoulet has offered.
Nick:
1) Nothing needed from other teams this week.
2) I'm getting out of the way as everybody does grantwriting/fundraising.
2a) But folks keep asking questions that I don't know answers to.
Grants are confusing.
3) Talking to reporter about prop224, at Kate's request.
4) A short list of things I'm aware of that nobody's taken charge of
so far as I know:
4a) Setting up GPG reencryptor for tor-security list.
4b) Setting up a securedrop instance
4c) Getting the board mailing lists the way the board wants them.
4d) Collecting the onboarding stuff we did with the last N people we
onboarded in a way that we can onboard the next N more easily.
Kate:
1) Working with Yawning on Q and A blog post about his Firefox sandbox
2) Working with Wendy on op-ed about Rule 41 (also: There is growing
interest and support for shutting down the changes to Rule 41 but
basically no time or chance to do so in Congress before December 1.
However, this thing can be shut down at any time in the next
legislative session, so the work in sharing info about Rule 41,
getting people to call Congress and spread the word to their friends
and family is still very useful.)
3) Met with EFF and Mozilla policy folk as well as SF-based reporters
4) Following up with Chilean and Indian policy advocates as well as
others (there is interest in an International Privacy Day as a way of
reaching out to people who don't know much about privacy issues)
5) Congrats to everyone on making the Seattle meeting a success! We
were all trying hard and together, we did it. I learned a lot at the
meeting that I'll be using in our communications work (for instance, I
got to talk to Yawning). I'll have more follow up from the Seattle
meeting next week.
6) I don't need anything from the group at present.
7) Welcome, Arturo!
Georg:
1) Started to look at the Cloudflare proposal on tor-access list
2) Worked on the OTF proposal
3) Tied down remaining Tor Browser SponsorU items
Arturo:
1) First time attending the Vegas team meeting. Looking forward to
seeing how we can better support the work of the rest of Tor and being
better integrated into the Tor ecosystem.
2) OONI has submitted a talk to CCC.
3) Working towards releasing 2.0.0 (with our new web UI)
4) Will try to push out this week a job posting for a UI/designer position
4a) Should reach out to Mike and Linda for feedback and suggestions
on how to handle this hiring process
4b) Will interact with Scout and SimplySecure on how to ensure it
reaches the maximum amount of people and for help during the hiring
process
5) This month we are switching over to the OTF grant (from the MDF grant)
6) Will publish this week or beginning of next week a report on
internet controls in Zambia
Isabela:
1) working on reports to OTF - reports on deliverables we are
invoicing them / august report that I am late on core tor part /
September report that I am also late with core tor part
2) isc contract started on september - amogh will do the backend part
but we are missing someone to do the frontend part. I think I found
the person, is a firefox addon developer from NL - will set up an irc
chat with Geko and Nathan and him.
2.1) Nathan actually helped me find this person. this is a 25hrs
$100/hr contract.
2.2) posted wireframes of the experience for review (reviewer: Linda)
3) many follow ups from Seattle Tor Meeting:
3.1) follow up on tor browser roadmap
3.2) follow up on network team discussion
3.3) follow up on visual style guide discussion
4) working with Giant Rabbit to make sure we unblock them -- mostly
getting info for admins to set up vms for them
5) working with Linda on her goals for the month - had a 1:1 with her
on skype about it and also answered many questions she listed while
ramping up
6) trying to figure out how to cut 200k from our otf proposal :(
7) events - i will be attending an event in Chile.
8) NCE for OTF sponsorU work (extend till end of nov)
9) service admin intern will start on nov 1st (silvia)
Alison:
1) Don't need anything from other teams this week.
2) I'm mostly afk this week as i finish moving and take a few days
off. I'll be back to following up on meeting stuff next week.
Karsten:
1) Writing code, nothing to see here.
-----BEGIN PGP SIGNATURE-----
Comment: GPGTools - http://gpgtools.org
iQEcBAEBCAAGBQJX+0J0AAoJEC3ESO/4X7XBfgAH/3d44Igrvx4gcyoFnCNGMHKn
JB7UwPJdPAKMnAotpNEgZAu2s6YT6H3+WM31RWN8WHGkBKwMMuULUkyzJ2LPK47K
5Vgv7zTwW1mLtOrpi74p/uh6gfgp3NkHXPZJ8REJdu5MfkZdIiovgAP0tWbjl5Kz
llGJsPiLC//rR5rN5OW9bPI4EISwSlQVqF7MMI6UR275nj8QgQyJzCal3w8MC9/u
ky+V1cOPZTDRT1ci3nHFkScnTJyPTPcNhXjWL/KBMcQGxyv0/RChutzvv5iS/xYz
Pr6eJjwufR6JvaD2drsXd0mmqD6Qdx+Ti8O9vMMk+EEoPqjDAIxWWeW+JA8MgXs=
=dcSu
-----END PGP SIGNATURE-----
----- Forwarded message from dan <dan(a)opentechfund.org> -----
> From: dan <dan(a)opentechfund.org>
> Subject: [OTF-Announce] Announcement of Funding Opportunities
> Date: Fri, 7 Oct 2016 11:28:53 -0700 (PDT)
> Message-Id: <fa072fb2-9d17-4705-9737-8686bb2eb64b(a)opentechfund.org>
> To: OTF-Announce <otf-announce(a)opentechfund.org>
> Reply-To: otf-announce+managers(a)opentechfund.org
> Delivered-To: <isis+torproject(a)patternsinthevoid.net>
>
>
>
>
>
> *--- OTF FUNDING ANNOUNCEMENTS
> ---==============================================*Please find below several
> upcoming internet freedom-relevant funding application deadlines. There are
> two sections, the first for OTF support and the second for all alternative
> support mechanisms. Note that some of the listed application windows close
> in just a few days.
> If you have any questions on the information below, please feel free to
> give a shout to us at OTF anytime. Thanks!
>
>
> *1. OTF FUNDING==============================================*
>
> -
> *OTF - Internet Freedom Fund *
> *Deadline: 2016-11-01 *The Internet Freedom Fund is OTF's primary way to
> support projects and people working on open and accessible
> technology-centric projects that promote human rights, internet freedom,
> open societies, and help advance inclusive and safe access to global
> communications networks. Successful applicants are awarded monetary support
> up to $900,000 and no less than $10,000, with preference given to those
> projects and people who are new to the internet freedom community, helping
> those living within repressive environments, and are requesting less than
> $300,000 for a duration of less than 12 months.
> Apply: https://www.opentech.fund/requests/internet-freedom-fund
>
>
> -
> *OTF - Rapid Response Fund *
> *Deadline: Ongoing *The Rapid Response Fund is part of a broader OTF initiative
> which aims to facilitate the development of a strong digital emergency
> response community that can work together to resolve threats in a timely
> and comprehensive manner. OTF offers both direct financial support as
> well as technical services from trusted partners to resolve digital
> emergencies experienced by high-risk Internet users and organizations, such
> as bloggers, cyber activists, journalists. and human rights defenders.
> Apply: https://www.opentech.fund/requests/rapid-response-fund
>
>
>
> *2. ALTERNATIVE FUNDING==============================================*
>
> - *Human Rights Watch - Various Fellowships*
> *Deadline: October 8, 2016*
> Human Rights Watch has several available fellowships all with a deadline
> of tomorrow, 10/8/16.
> More
> information: https://careers.hrw.org/opportunities/?employmentLevel=Fellowship&location=…
>
> -
> *National Science Foundation (NSF) - Secure and Trustworthy Cyberspace
> (SaTC) *
> *Upcoming windows: October 12 - October 19 and November 02 - November 16,
> 2016 *"The SaTC program welcomes proposals that address cybersecurity
> and privacy, and draw on expertise in one or more of these areas:
> computing, communication and information sciences; engineering; economics;
> education; mathematics; statistics; and social and behavioral sciences.
> Proposals that advance the field of cybersecurity and privacy within a
> single discipline or interdisciplinary efforts that span multiple
> disciplines are both encouraged."
> More information and apply:
> https://www.nsf.gov/funding/pgm_summ.jsp?pims_id=504709
>
> -
> *National Science Foundation (NSF) - Computer and Network Systems (CNS):
> Core Programs *
> *Upcoming windows: October 12 - October 19 and November 02 - November 16,
> 2016 *"CISE’s Division of Computer and Network Systems (CNS) supports
> research and education projects that develop new knowledge in two core
> programs: Computer Systems Research (CSR) program and Networking Technology
> and Systems (NeTS) program." Funding is available for small projects (up to
> $500,000 total budget, durations up to three years), medium projects
> ($500,001-$1,200,000 total budget, durations up to four years), and large
> projects ($1,2000,001-$3,000,000 total budget, durations up to five years).
> More information and
> apply: https://nsf.gov/pubs/2016/nsf16579/nsf16579.htm
>
>
> - Echoing Green Fellowships
> Deadline: October 25, 2016
> "Echoing Green Fellows are the innovators, instigators, pioneers, and
> rebels that reject the status quo and drive positive social change all over
> the world. While their work, their geographies, and even their approaches
> may be as varied as the problems they are working to solve, their common
> passion and commitment form the base of this robust, active community of
> leaders"
> Apply: http://www.echoinggreen.org/fellowship/apply
>
> - *State Department DRL Request for SOIs: Human Rights, Accountability,
> and Access to Information in the Democratic People's Republic of Korea
> (DPRK or North Korea) *
> *Deadline: October 31, 2016 by 11:30pm Eastern Time*
> "*Fostering the Free Flow of Information into, out of, and within the
> DPRK *(approximately $1,600,000, pending availability of funding, with
> potentially more than two (2) projects awarded)...DRL’s goal is for the
> people of North Korea to have increased access to independent information
> that provides a range of viewpoints and increases exposure to and
> understanding of environments where individuals are able to communicate
> information and express their opinions freely."
> More information and apply: https://www.state.gov/j/drl/p/262180.htm
>
> -
>
> *Shuttleworth Foundation Fellowships Deadline: November 1, 2016 *"The
> Shuttleworth Foundation offers fellowships to individuals to implement
> their innovative idea for social change. We are most interested in
> exceptional ideas at the intersection between technology, knowledge and
> learning, with openness being the key requirement. The Foundation funds
> people from all over the world regardless of gender, age, nationality or
> experience. We are looking for a complete picture of you and your idea."
> Apply: https://www.shuttleworthfoundation.org/application-form/
>
> - *National Endowment for Democracy (NED) - Reagan-Fascell Fellowship
> Program*
> *Deadline: November 1, 2016*
> "The Reagan-Fascell Democracy Fellows Program hosts democratic
> activists, scholars, and journalists for five-month fellowships, bringing
> fresh insights and perspectives to Washington, DC. The fellowship offers an
> important opportunity to explore new ideas in a comparative context,
> undertake individual research, and share best practices with one another."
> Apply:
> http://www.ned.org/fellowships/reagan-fascell-democracy-fellows-program/app…
>
>
> -
>
> *Mozilla Open Source Support (MOSS) Deadline: November 30, 2016 "*The
> Mozilla Open Source Support program is designed to recognize and celebrate
> communities who are leading the way with open source projects that
> contribute to our work and the health of the Web. It encompasses a “give
> back” element for Open Source and Free Software projects that Mozilla
> relies on (the "Foundational Technology" track), a “give forward” element
> for supporting other projects whose goals are in alignment with ours (the
> "Mission Partners" track), and an element for improving the security of the
> open source ecosystem (the "Secure Open Source" track)."
> More information: https://wiki.mozilla.org/MOSS#Program_Overview
>
> Apply: https://docs.google.com/a/opentechfund.org/forms/d/e/1FAIpQLSe9a9h4afnJnDp3…
>
> ---------
> In addition to the open application windows listed above, you can always
> check our compiled list of alternative sources of support:
> https://www.opentech.fund/apply/alternative-sources-support
>
> --
> This is the announce list for Open Technology Fund, https://www.opentechfund.org
> ---
> You received this message because you are subscribed to the Google Groups "OTF-Announce" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to otf-announce+unsubscribe(a)opentechfund.org.
> For more options, visit https://groups.google.com/a/opentechfund.org/d/optout.
----- End forwarded message -----
--
♥Ⓐ isis agora lovecruft
_________________________________________________________
OpenPGP: 4096R/0A6A58A14B5946ABDE18E207A3ADB67A2CDB8B35
Current Keys: https://fyb.patternsinthevoid.net/isis.txt
Hey there,
I'm not sure if I mentioned this on a public channel before, but I'm
running a bandwidth authority from a VPS in HK.
It has been running since Aug 1st, 2016. For now, the results are being
pushed to a repo[0] on a hourly basis.
I thought I'd mention this for anyone who wants to study them or if any
of the DAs need a bwscanner to pair with. I'm planning to keep this
running for the foreseeable future.
You can directly fetch the latest scan[1][2] or measured percentage[3].
I can later put them on a webserver if that makes a difference.
[0] https://github.com/mrphs/bwauth
[1] https://github.com/mrphs/bwauth/blob/master/latest_bwscan
[2] https://raw.githubusercontent.com/mrphs/bwauth/master/latest_bwscan
[3]
https://raw.githubusercontent.com/mrphs/bwauth/master/measured_percentage.t…
Peace,
--
Nima
0X58C4B928A3E218F6 | @mrphs
"I disapprove of what you say, but I will defend to the death your right
to say it" --Evelyn Beatrice Hall
Here's the summary of meek's CDN fees for August 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
August 2016 $0.00 + $1038.62 + $607.13 = $5400.12
--
total by CDN $13138.96 + $17939.22 + $4792.99 = $35871.17 grand total
https://metrics.torproject.org/userstats-bridge-transport.html?start=2016-0…
The number of users continued to rise last month, getting almost to
10,000, about the level it was at before the meek-google shutdown.
(There's a big dip near the end of the month, but it doesn't seem to
have lasted long.) That means that meek-azure and meek-amazon are under
increased load compared to before--about 7 TB/month for meek-azure and
3 TB/month for meek-amazon. If I get a chance, I'm going to try
installing an ECDSA (as opposed to RSA) certificate on meek-azure, and
see if it relieves the CPU load.
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
== Amazon a.k.a. meek-amazon ==
Asia Pacific (Singapore) 77M requests $93.24 428 GB $57.27
Asia Pacific (Sydney) 6M requests $7.52 33 GB $4.51
Asia Pacific (Tokyo) 1M requests $1.38 7 GB $0.95
EU (Ireland) 299M requests $359.00 997 GB $77.22
Global 1M requests $1.91 6 GB $0.48
South America (Sao Paulo) 22M requests $49.82 177 GB $42.23
US East (Northern Virginia) 247M requests $247.36 1214 GB $95.24
--
total 655M requests $760.23 2865 GB $277.90
charge for alarms $0.50
https://atlas.torproject.org/#details/F4AD82B2032EDEF6C02C5A529C42CFAFE5165…
== Azure a.k.a. meek-azure ==
Zone 1 6731 GB $585.61
Zone 2 156 GB $ 21.52
--
total 6887 GB $607.13
https://atlas.torproject.org/#details/AA033EEB61601B2B7312D89B62AAA23DC3ED8…
Earlier reports in this series:
https://trac.torproject.org/projects/tor/wiki/doc/meek#Costs