Item h under
https://www.torproject.org/getinvolved/volunteer.html.en#OtherCoding
discusses (at least) the images at this page,
https://www.torproject.org/about/overview.html.en
which look as if they're copied from some EFF presentation. I've recreated them as svg. Svg being a fairly standard vector markup, I supposed that it would be more amenable to automatic string replacement than a png (I'm not sure what wml is). Please look them over and give me feedback. If they are ultimately found acceptable, you are welcome to use them for the site. Thanks.
Justin
On Sat, Nov 09, 2013 at 03:16:41AM -0700, jfindlay@gmail.com wrote 263K bytes in 0 lines about: : which look as if they're copied from some EFF presentation. I've : recreated them as svg. Svg being a fairly standard vector markup, I : supposed that it would be more amenable to automatic string : replacement than a png (I'm not sure what wml is). Please look them : over and give me feedback. If they are ultimately found acceptable, : you are welcome to use them for the site. Thanks.
Thanks! These look great.
They weren't copied from an EFF presentation, they were made by the EFF for us. You can find the originals inside https://media.torproject.org/image/official-images/tor_design_archive.zip
I've added them to the site image directory for now.
On 11/09/2013 06:20 PM, andrew@torproject.is wrote:
They weren't copied from an EFF presentation, they were made by the EFF for us. You can find the originals inside https://media.torproject.org/image/official-images/tor_design_archive.zip
I've added them to the site image directory for now.
Awesome. There's lots of raster diagrams there. There are eps versions of the three EFF ones I remade, but they seem to contain many binary blobs and I couldn't find the text therein as actual text. It might be vector markup, sure, but that's much lower level than an svg's text and font statements. Besides, eps isn't a format easily supported natively by any browser, whereas svg is practically designed for this purpose. (I'm still not sure what wml is and why it should be preferred. Does this have something to do with the framework of the site and how it is rendered?)
To me there seems to be two purposes: 1) remake the illustrations in a format such that the included text can be easily automatically translated and 2) use vector graphics, raster being somewhat retrogressive. [1]
I used inkscape for the three images I remade and don't necessarily consider them the best/final versions. As a programmer, I'm more comfortable with an expressive language like TikZ that can be rendered to svg than a wysiwyg editor.
Justin
[1] https://en.wikipedia.org/wiki/Wikipedia:Preparing_images_for_upload
Justin Findlay:
Item h under
https://www.torproject.org/getinvolved/volunteer.html.en#OtherCoding
discusses (at least) the images at this page,
https://www.torproject.org/about/overview.html.en
which look as if they're copied from some EFF presentation. I've recreated them as svg. Svg being a fairly standard vector markup, I supposed that it would be more amenable to automatic string replacement than a png (I'm not sure what wml is). Please look them over and give me feedback. If they are ultimately found acceptable, you are welcome to use them for the site. Thanks.
I think they look great. :)
But something has always bothered me with these diagrams: they make it look like Tor relays are run on everyone's computer. With Justin's revision, it looks like they are run on laptops. The vast majority of Tor relays are run on stable servers and most of the traffic flows through high capacity servers, hosted in datacenters behind high capacity links. So I think picturing a laptop might be misleading…
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256
On 11/11/13 14:10, Lunar wrote:
Justin Findlay:
Item h under
https://www.torproject.org/getinvolved/volunteer.html.en#OtherCoding
discusses (at least) the images at this page,
https://www.torproject.org/about/overview.html.en
which look as if they're copied from some EFF presentation. I've recreated them as svg. Svg being a fairly standard vector markup, I supposed that it would be more amenable to automatic string replacement than a png (I'm not sure what wml is). Please look them over and give me feedback. If they are ultimately found acceptable, you are welcome to use them for the site. Thanks.
I think they look great. :)
But something has always bothered me with these diagrams: they make it look like Tor relays are run on everyone's computer. With Justin's revision, it looks like they are run on laptops. The vast majority of Tor relays are run on stable servers and most of the traffic flows through high capacity servers, hosted in datacenters behind high capacity links. So I think picturing a laptop might be misleading?
Whilst we're on that topic, labelling the final link from the exit node to the destination as "unencrypted" is unnecessarily scary as well Perhaps we could reword it to "encrypted if destination service is encrypted" and the other links to "always-encrypted".
X
- -- GPG: 4096R/1318EFAC5FBBDBCE git://github.com/infinity0/pubkeys.git
On Mon, Nov 11, 2013 at 02:42:24PM +0000, Ximin Luo wrote:
Whilst we're on that topic, labelling the final link from the exit node to the destination as "unencrypted" is unnecessarily scary as well Perhaps we could reword it to "encrypted if destination service is encrypted" and the other links to "always-encrypted".
Great point.
But applying the word 'encrypted' for both Tor's crypto and the horrible web CA model makes me itch.
How about "Encrypted by Tor" / "Not encrypted by Tor"?
With pointers in the text to https://www.eff.org/pages/tor-and-https and https://svn.torproject.org/svn/projects/articles/circumvention-features.html...
--Roger
On 11/11/13 15:40, Roger Dingledine wrote:
On Mon, Nov 11, 2013 at 02:42:24PM +0000, Ximin Luo wrote:
Whilst we're on that topic, labelling the final link from the exit node to the destination as "unencrypted" is unnecessarily scary as well Perhaps we could reword it to "encrypted if destination service is encrypted" and the other links to "always-encrypted".
Great point.
But applying the word 'encrypted' for both Tor's crypto and the horrible web CA model makes me itch.
How about "Encrypted by Tor" / "Not encrypted by Tor"?
With pointers in the text to https://www.eff.org/pages/tor-and-https and https://svn.torproject.org/svn/projects/articles/circumvention-features.html...
--Roger
That sounds good! More precise than my last suggestion.