UX at Tor: an Open Approach
This is a modal window.
The media could not be loaded, either because the server or network failed or because the format is not supported.
Formal Metadata
Title |
| |
Title of Series | ||
Number of Parts | 561 | |
Author | ||
License | CC Attribution 2.0 Belgium: You are free to use, adapt and copy, distribute and transmit the work or content in adapted or unchanged form for any legal purpose as long as the work is attributed to the author in the manner specified by the author or licensor. | |
Identifiers | 10.5446/44635 (DOI) | |
Publisher | ||
Release Date | ||
Language |
Content Metadata
Subject Area | ||
Genre | ||
Abstract |
|
FOSDEM 2019459 / 561
1
9
10
15
18
19
23
24
27
29
31
33
34
35
38
39
40
43
47
49
52
53
54
55
58
59
60
63
65
67
69
70
78
80
82
87
93
95
97
102
103
104
107
110
111
114
116
118
120
122
123
126
127
131
133
136
137
139
141
142
148
153
155
157
159
163
164
168
169
170
171
172
173
174
181
183
185
187
188
193
196
197
198
199
200
201
205
207
208
209
211
213
214
218
221
223
224
226
230
232
234
235
236
244
248
250
251
252
253
255
256
257
262
263
264
268
269
271
274
275
276
278
280
281
283
284
288
289
290
293
294
296
297
300
301
304
309
311
312
313
314
315
317
318
321
322
327
332
333
334
335
336
337
338
339
340
343
345
346
352
353
355
356
357
359
360
362
369
370
373
374
375
376
377
378
383
384
387
388
389
390
391
393
394
395
396
406
408
409
412
413
414
415
419
420
425
426
431
432
433
434
435
436
438
439
440
441
445
446
447
448
453
455
457
459
466
467
471
473
474
475
476
479
480
484
485
486
489
491
492
496
499
500
502
505
507
508
512
515
517
518
529
531
533
534
535
536
539
540
546
550
551
552
553
554
555
557
558
559
560
561
00:00
Open setOpen setMoment <Mathematik>Projective planeComputer animation
00:44
Computer networkMetric systemOpen setMoment <Mathematik>UsabilitySeitenbeschreibungsspracheLattice (order)Type theoryTrailBridging (networking)Product (business)FeedbackCartesian coordinate systemBuildingStack (abstract data type)Projective planeGoogolMetric systemValidity (statistics)SoftwareAndroid (robot)MereologyBitProcess (computing)Right angleSelf-organizationOpen setInternetworkingTelecommunicationService (economics)Musical ensembleSet (mathematics)WordComputer animation
04:27
Group actionMusical ensembleMoment <Mathematik>Data storage deviceMultiplication signFactory (trading post)Self-organizationLimit (category theory)WindowComputer fontLocal ringLine (geometry)Level (video gaming)Context awarenessTrailWeb browserUsabilityVideo gameComputer animation
06:38
Musical ensembleMatching (graph theory)Computer animation
07:18
Information securityService (economics)WindowComputer iconPressure volume diagramElectronic visual displayDigital electronicsService (economics)Computer iconIterationDifferent (Kate Ryan album)Expected valueMereologyWebsiteWeb browserVolume (thermodynamics)Library catalogInformation securityType theoryElectronic visual displayConfiguration spaceElement (mathematics)Connected spaceMultiplication signDefault (computer science)LiquidForcing (mathematics)CASE <Informatik>Musical ensembleTotal S.A.Touch typingXML
09:05
Web browserClient (computing)SoftwareMultiplication signTriangleResultantNormal (geometry)Computer configurationWhiteboardLevel (video gaming)Computer animation
09:48
Musical ensembleMatching (graph theory)Web browserComputer animation
10:21
Formal languageLocal ringWeb browserValidity (statistics)Computer animation
11:03
Lattice (order)Computer animation
11:24
Session Initiation ProtocolNormed vector spaceWeb browserRevision control
11:47
Source code
12:15
Computer hardwareProjective planeIntegrated development environmentSoftware developerSelf-organizationComputer programmingProduct (business)CollaborationismComplex (psychology)Core dumpChemical equationSoftware bugModal logicTrailLengthLocal ringProcess (computing)InformationElectronic mailing listRevision controlUniverse (mathematics)Address spaceInternetworkingState of matterOpen setWordWikiData managementSocial classMusical ensembleData storage deviceTable (information)Nichtlineares GleichungssystemRow (database)Data structureAnalogyWeb 2.0Computer animation
21:06
Canonical ensembleComputer animation
Transcript: English(auto-generated)
00:10
Our next speaker is Antonella from The Torque Project and she's gonna tell us how The Torque Project was designed and their open project, please Antonella.
00:25
My name is Antonella, I'm from China. We've been traveling and working around the world for the past seven years. I'm quite tired now, and unfortunately
00:40
I've been leading the UX team at The Torque. The UX team at The Torque Project works across all the teams. We work with the applications team, building Torque for Android and Torque for desktop. We work with the community team,
01:02
traveling around the world in something that we call the Global South Initiative. I will talk a little bit about that later. Meeting human rights organizations and internet freedom people around the world. We work with the communication teams on things like
01:20
end of the year campaign and raising money. We work with the metrics team, finding a way to show our open data and easy for users. We work with the network team also to improve the access to any service. The foundation of The Torque Project
01:41
are based on creating technologies that respect users. I really like this pyramid from the India team. It's very easy because Torque technology it's like covering the base part.
02:02
Technology is decentralized, it's private, it's open, it's an integral problem, it's a cure, and we try to make it simple. Both of the Torque is something that we are trying to focus on. We respect users in all the states.
02:27
Our approach to usability is being on respected and useful data, we try to place where we use data like the industry does.
02:41
It's very hard, but it's very rewarding too. Torque is open. We have meetings on ERC, you can read everything what we do. If you type Antonina in our track bar you can see what I have been doing the last month.
03:04
People who came to our meetings it's people like sometimes it's anonymous, so we work with people who sometimes we know who they are, sometimes we don't. And it is pretty nice. And the product we build,
03:26
a topic from OpenDesignkey.org which explains basically our process. This is very nice, but the process often is something like this. Steam works more like a bridge.
03:43
We try to tell user stories that make sense for a user, and we try to improve our products and our technology to make them usable for our end users. It's in the world, we have people collecting feedback
04:02
from a lot of channels, Reddit, Stack Overflow, our backtrackers, Google Play, everywhere. We work together on paradise and we try to also discuss based on sponsors, validate.
04:29
We focus on connecting with communities located in the global south. If you make a line in a map among these you will find countries like Colombia,
04:42
Uganda, Kenya, and India. We travel there, we meet people, we talk with them. We see how poor infrastructure is. We see how expensive it's accessing to internet there. We see how oppressive governments are ruling these countries.
05:04
And this allow us to understand our users context. As I said before, we don't track users like the industry does, so the only way we have to understand our user needs is to talk to them.
05:22
First in academic organization, we have a lot of working groups researching our tour everywhere. I'm happy that we have more and more people interested in usability because academic research quite validates our assumptions. We apply that in real life.
05:46
Last year we launched tour browser eight. We will say that this is the year to break tour. So it's nice. For full and all, tour browser limits fingerprinting
06:01
by normalizing different features that can track you. Like your window size, the fonts you use, the localization you have, the more people who is using tour that look the same, stronger tour is.
06:24
This is by design. User experience for that needs to be a priority. If you have more people using tour, it's better for everybody. This tour browser eight release was launched last year.
06:42
It was a match for release focusing on U.S. I think the users we have here. Since you remember the green about page, we changed it. So I'm really happy when we arrived.
07:11
As I said, this was a match for release focused on end user experience, and I think it's very good.
07:20
The story about some features we have been working with. One of them is secure expectation for our new services. When you visit the new services before, you don't have any clue about your security. When I talk about security, I'm talking about this tiny little icon that you have in your bar. We have been working on that,
07:42
and 7.4 doesn't have anything. On the best cases, you have nothing, but on the worst cases, you have like a red lock, which is something like it's not real because the new services are often more secure than HTTP sites. There are some iterations that we made.
08:01
We have volume catalogs for different type of audio configuration. This is super technical. If you want to know more about that, I can talk later, but I don't want to annoy you. We can see. Another thing we improved was the SQL display. The SQL display is a new element that for sure
08:24
makes part of the Tor browser experience. It tells users how the Tor connections have been made. We have several problems before. The SQL display, this is important. The Tor browser has first-party installation by the phone.
08:41
That means that each time you open the browser, renders a new SQL for you. So basically, this SQL works for that and for cellular visiting. So this is why we moved T-shirt with display from the Tor button, which was like in every day. So they can't present a lot longer,
09:01
which is pretty much sense because it works this way. We've been working with our onboarding.
09:21
People who are writing their browser for first time has the browser doing, but then during our initial research, we found that people open the browser and say, whoa, this is a normal browser. Yeah, for sure. So what we try to do is to explain Tor work,
09:43
how the browser can protect them on network level, on client level, and on devices.
10:11
So we try to match features with desktop and with mobile phone. It's very hard, but we are trying to do that.
10:21
I was loose on the browser calendar. We made it. Localization, the browser have learned in 24 languages.
10:41
I think it's nice because Erin's doing it. We know that localization is critical to reach end users. End users doesn't have technical background. Maybe they don't even speak English. So we really want to reach more abroad users. And localization is critical.
11:02
How to contribute to the project? As I said, all our works open, so you can come to our meetings. There are a lot of things to do. You can't imagine. So if you are a designer and you have some hours and you are interested to do that, please ping me. I really have to explain how to join us.
11:26
Up here, the new version of the browser.
11:42
Show you some things I have here. And you can download the browser alpha, which is new. If you want to try it, if you find bugs,
12:01
please record them tomorrow.
12:26
So if you are a technical person and you want to collaborate with the network, you are. I don't know, but if you check Twitter, you will see. I think it's 3 p.m. on Sunday.
12:40
On Sunday. Collaborate. It's the size of the tech team and the design team. And what tools do you use to communicate between designers?
13:05
And because you don't know each other, which kind of tools do you use? The third team we have. Sorry, which tools we use to communicate and to work in between teams. We work remotely.
13:21
We are an open team. We have a core team, which is only about the third process foundation. And then we have a community, which is huge. We collaborate with that. Basically, we use IRC for the navigation. For all schools. On the site, specifically, we have track.
13:43
We have bugs. Bug tracker, so we can collaborate. We have open discussions or track tickets. Tools. Do you want to know design tools? I'm using Sketch. It's not open, but it's something that works.
14:03
The size of the team. It's really on me. We are, yeah, the team is very small. We have a localization manager who help us to connect with localization labs to provide these
14:21
localization versions of our products. We have a developer who then develops content developers to help us to build something. Often we work one on one with developers. I mean, I have been doing the last improvement,
14:40
so I have been working personally on that. And we work one on one with developers. You mentioned you did some research on developing nations. I was wondering if they were, I mean, besides the infrastructure issues, were there any findings particular to the use of those contexts?
15:03
There are no besides infrastructure issues. I mean, there are a lot of issues, but infrastructure and access to web, to the internet, it's like critical. Our idea is that if we can make works on places where internet is like super expensive,
15:23
where data is like expensive, where infrastructure is poor, where hardware is poor, then making that work in the north is very easy. So localization help us to find metaphors to explain difficult concepts because
15:41
it starts with difficult technology to explain for people who doesn't have technical background. So the localization help us a lot to find the words to explain, not to teach people who are also end users to understand what is happening.
16:01
On our track, it's wiki.oprocha.org. You have seen, you have more information about our user research program. As I said, Top Project is an NGO. We are founded by organizations. We have this program where we travel
16:21
to global south countries. We meet people in person and this is critical for our work. Basically because even if I want to track users in the roads, then I can't. I don't know who is on the other side. We can't do that. It's challenging because it's like
16:41
I'm coming from the commercial world and now I'm here and it's like one step more of difficulty.
17:16
We have super technical users who have been using Tor so far.
17:21
When I say Tor, I'm talking about products. I mean, I'm talking about Tor products. We want to make this technology available for people who doesn't have technical understanding because very often, people who must need this technology is people who live in a present environment and it's people who doesn't have
17:41
the technical background to understand that. So we should balance what we are explaining and what we are not. Often we want to explain everything. We really believe that we can empower users through education and if we can explain complex concepts in easy way, people can understand.
18:00
We really believe that users should opt in and opt out of things. So it's a balance between technical users and non-technical users. I'm focused on end users that are not technical and this is what we are trying to do. I mean, all this year, this technology has been made for super techy people.
18:23
It's fine. It's necessary. It's a process. But I think it's important to reach more people. I think I'm starting to talk in length.
18:52
From my opinion, you are doing a very good job actually in the 90s with you. I'm a divergent in a company, an academia,
19:02
to the 90s with a person in the class. So two questions. One question is, is it already in development in the 90s in New York? The university is at the same list as the other world resource projects.
19:22
I think you have a very similar approach. Why don't you publish your work tomorrow? Thank you. As I said, our project launched on, I think, October or November. We have people in universities like Princeton and New York University.
19:41
They have research in the world of technology. It's going to be fetched in a few months. So there are people writing about this improvement. I don't know if they are measuring what we have been missing two months ago. But some problems we have in addresses
20:01
are problems that have been running or absorbed from a lot of people. So, I mean, it was just the first step in making this usable. I'm really looking forward for the next version. We really need to close at nine. And I hope we have a kind of research
20:24
running questions about what we are doing. About what we are doing. I'd say that we keep past this wide information. If you want to read more, you can find it there. This place is a good place to share experiences and how we are working. And if we are a direct-color project, I mean, we work with the state people also.
20:43
We decided to research on end users without tracking them. So, yeah. I hope it is very extra sure. How we work.