 Here is Antonella from the Tor Project and she's going to tell us how the Tor Project was designed and their open project came out. In Liner we've had it for seven years, like Diana, so unfortunately we may not be able to team at the Tor Project. They use Team at the Tor Project to work across all the teams. We worked with the applications team, building TorRoser for Android and TorRoser for desktop. We worked with the community team travelling around the world in something that we call the Global House Initiative. I will talk a little bit about that later. Meeting human rights organizations and internet freedom people around the world. We worked with the communications team, some teams like NOPier, Campaign and Brighton Money. We worked with the methods team finding a way to show and open that up easily for users. We worked with the members team also including the access to online services. The foundation of the Tor Projects are based on creating technologies that respect users. I really like this pyramid from the Indians. It's very easy because Tor Technology is like coloring the baseboard. Tor Technology is the central item of the project. It's open. It's an internet problem. It's tactical. It's secure. And we try to make it simpler. What's on the top is something that we are trying to focus on. We respect users in all the stages. Our approach to usability is being unrespective and user data. We try to place it where we use our rights with Brighton usability that we use in us. It's very hard, but it's very rewarding too. Our work is open. You can read everything while moving. If you type Antonina in our track bag, you can see what I have been doing the last month. People who came to our meetings are anonymous. We work with people who sometimes we know who they are, sometimes we don't. And it's pretty nice. The project we built is graphic from OpenSync.org, which explains basically our process. This is very nice, but the process often is something like this. Steam works more like a bridge. We try to tell users stories that make sense for users. And we try to improve our products and our technology to make them usable for our users. Based on the work, we have people collecting feedback from a lot of channels. We have Reddit, Stack Overflow, our Backpacker, Google Play, everywhere. We work together on standardized tasks and we try to support all these tasks based on the sponsor. Focusing on connecting with communities. If you make a line in a map among these, you will find countries like Colombia, Uganda, Kenya, and India. We travel there, we meet people, we talk with them. We see how poor the infrastructure is. We see how expensive it's accessing the internet there. We see how oppressive governments are ruling these countries. And this allows us to understand our users in context. As I said before, we don't track users like the industry does. So the only way we have to understand our users is to stop using them. This is an academic organization. We have a lot of working groups researching our door everywhere. I'm happy that we have more and more people interested in usability because academic research quite validates our assumptions. Last year we launched DoorRoser 8. It says that this is the year to break door. So it's nice. Focusing now the browser limits fingerprinting by normalizing different features that can track you, like your window size, the font size, the location you have, dramas. The more people who use DoorRoser that look the same, the stronger the door is. This is by design. User experience for that needs to be a priority. If you have more people using DoorRoser, it's better for everybody. This DoorRoser 8 release was launched last year. It was a much more released published on U.S. I think DoorRoser 8 will change. So what to do, but I'm really happy when we arrived. It was a much more released published on end user experience and I think it's very good. There's a story about some features that we have been working with. One of them is security expectation for onion services. When you visit onion services before, you don't have any clue about your security. When I talk about security indicators, I'm talking about this tiny lock icon that you have in your bar. We have been working on that. 7 button foils doesn't have anything. On the best cases, you have nothing, but on the worst cases, you have a red lock which is something like it's not real because onion services are often more secure than HTTP sites. There are some iterations that we may have. We have onion padlocks for different type of ion configuration. This is super technical. If you want to know more about that, you can talk later. Another thing we improved was the secret display. The secret display is new element that for sure makes part of the DoorRoser experience. It tells users how the door connections have been made. We have several problems before. The secret display, this is important. DoorRoser has first-party isolation by default. That means that each time you open the doorRoser renders a new secret for you. So basically, this secret works per tab and per type of USB. So this is why we moved the secret display from the DoorWooTone which was in every day. So they come to send the lock longer, which is pretty much the same because it works this night. We are working with one of the door onboarding. People who are right at DoorRoser for the first time have several ideas about what we are interested in. We found that people open the doorRoser and say, wow, this is a normal doorRoser. Yeah, for sure. So what we try to do is to explain how the door works, how the doorRoser can protect them on network level, on client level, and our tracking devices. So we try to match features with desktop and with mobile phone. It's very hard, but we are trying to do that. We'll use the doorRoser renderer to show that later. Localization. The doorRoser have a land in 24 languages. I think it's nice because Eric is doing it. We know that localization is critical to reach end users. End users doesn't have technical background. Many of them even speak English. So we really want to reach more abroad users. Localization is critical. How to contribute to the project? As I said, all our work is 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're interested in that, please feel me. I really have to explain how to join us. What I will do now is to show here. This is a new version. I'm going to show you something. I have it here. You can download the doorRoser alpha. Which is new. If you want to try it, you can find the future for them. Create a meet-up tomorrow. So if you are a technical person and you want to collaborate with the network, I don't know. But if you check Twitter, you can see it. I think it's 8pm on Sunday. On Sunday. Theme under your tools. You collaborate. What tool do you use to communicate between designers? Because you don't know each other. Which kind of tool do you use? The third team, which tool do we use to communicate and to work between teams? We work remotely. We are another team. We have a core team, which is the door process foundation. And then we have a community, which is huge. We collaborate with others. Basically, we use IRC for communications. We're old school. We're sad. We're just working. On this time, specifically, we have track. We have backtrackers, so we can collaborate. We have open discussions over track tickets. Tools that you want to know. Design tools. Okay, I'm using Sketch. It's not open, but it's something that works. I like Sketch. The size of the team. It's really on me. We are, yeah, the team. The other team is very small. We have a localization manager, who helps us to connect with localization labs to provide these, as I said, versions of our products. We have a developer, who then develops from the developer to help us to build something. Often, we work one-on-one with developers. I mean, I have been doing the improvements, so I have been working personally on them. 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, particularly in those contexts? There are no besides infrastructure issues. I mean, there are a lot of issues, but infrastructure and access to the web, to the internet, it's, like, critical. Our idea is that if we can make work, a tool works on places over where internet is, like, super expensive, where data is, like, expensive, where infrastructure is work, where hardware is all, then making that work in the north is very easy. And so, localization helps us to find metaphors to explain difficult concepts because, sorry, that difficult technology is playing for people who doesn't have a clinical background. So, data-validation helps us a lot to find the words to explain non-tech people who are also end-users to understand what is happening. On our track, you have more information about our user research program. As I said, our project is NDO. We are founded by organizations and we have this program where we travel 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 into rows, 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, I'm coming from the commercial world and now I'm here and it's, like, one step more of difficult. I love what you've learned in an open way. Yeah. It's difficult. We have super technical users who have been using Torso far. And when I say Toro, I'm talking about products. I mean, I'm talking about Toro today. Specifically. We want to make this technology available for people who doesn't have any understanding because very often the people who most need this technology is people who live in a present world and it's people who doesn't have 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 an easy way people can understand. We really believe that users should be up in and 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. Often, I mean, all this year, this technology having made for super techie people it's fine. It's necessary, it's a process but I think it's important to work with modern technology. Interesting that you are talking a lot. I think you are doing a very good job actually in designing videos. I heard that you said something that I can do here to so two questions. One question is the current UI has it already been evaluated in my opinion here? So I think you have really similar approach to publish your work. Thank you. As I said, the Rosarache launched I think October or November. We talk people in universities like Greenstone, New York University. They have researching groups from New South America. There are people writing about this improvement. I don't know if they are measuring what we have been using like two months ago but some probably having addresses are problems that have been running or stored from a lot of things. I mean, it was just the first step making this use of it. I'm really looking forward for the next one. We really need the Rosarache 9 and I hope we have a time research running questions about what we are doing. About what we are doing, I'd say that we have quite 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 at that other project, we work with the state people and we are trying to use it without tracking it. I hope it will be useful.