Re: [tor-bugs] #6922 [Company]: Write the storyboard/script for this video

["Tor Bug Tracker & Wiki" <blackhole@xxxxxxxxxxxxxx>]

#6922: Write the storyboard/script for this video
-------------------------+----------------------
     Reporter:  phobos   |      Owner:
         Type:  project  |     Status:  new
     Priority:  normal   |  Milestone:
    Component:  Company  |    Version:
   Resolution:           |   Keywords:  SponsorI
Actual Points:           |  Parent ID:  #5991
       Points:           |
-------------------------+----------------------

Comment (by runa):

 Comments on the updated script:

 '''Slide 2''': Perhaps say that Tor was originally developed by the U.S.
 Naval Research Laboratory, with the U.S. Navy in mind, for the purpose of
 protecting government communications. You should also mention when Tor was
 first released as a way to point out to viewers that Tor's been around for
 a long time. You should also introduce The Tor Project before you talk
 about it being a non-profit organization and all that.

 '''Slide 3''': You should make it clear that the user numbers are per day,
 and that we do not (and can not) track individual users (that is, we know
 500k users are using Tor daily all over the world, but we can't tell
 whether or not Alice in Boston, USA is using Tor to browse
 torproject.org).

 '''Slide 4''': The image on this slide shows relays and bridges, but you
 only talk about relays in your script. Perhaps replace the image with one
 showing just relays? Consider rephrasing the sentence that says "No one
 really runs the Tor network". This would be a good time to define the word
 "relay operator".

 '''Slide 5''': Rephrase the sentence which says that Tor encrypts all your
 traffic, we don't want users to think Tor does end-to-end encryption
 between the user and the destination website. If you are going to talk
 about risks, such as one operator controlling a large portion of the
 network, you should also talk about operators sniffing traffic from exit
 relays -- or drop the topic completely.

 '''Slide 6''': Instead of saying that example.com and the ISP will know
 who you are, the pages you're visiting, when, and how often, can you think
 of a more concrete example? Non-technical viewers may appreciate a more
 concrete example than one with a fictional website. You may also want to
 consider mentioning data retention issues here.

 '''Slide 7''': You may want to define HTTPS to a non-technical audience
 (what does it look like? how do I know I'm secure? what if the site does
 not support it?). Consider naming the relays on this slide "guard relay",
 "middle relay", and "exit relay", and explain how much information each
 relay has about the user and the data/traffic.

 '''Slide 8''': You can probably drop the blurb about HTML5 to save a few
 seconds. Users who are concerned about being deanonymized by external
 resources (doc/pdf) should at the very least go offline before opening
 them - maybe also consider a vm or second laptop. This may or may not be
 too much information for a non-technical audience.

 '''Slide 9''': Use the term "relay" instead of "node", consider not
 mentioning bridges here. If the target audience is non-technical, leave
 out the "if you are a developer"-portion too. Actually, maybe consider
 swapping this "if you would like to help Tor"-slide for a "if you would
 like to learn more about Tor"-slide.

-- 
Ticket URL: <https://trac.torproject.org/projects/tor/ticket/6922#comment:3>
Tor Bug Tracker & Wiki <https://trac.torproject.org/>
The Tor Project: anonymity online
_______________________________________________
tor-bugs mailing list
tor-bugs@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-bugs