 Hello everybody This is the second talk of day one as you guys know good friends have good friends and a good friend of links is Tesseract this young fellow here to my right. He will talk to us about The next step the next ideas that links just presented to us. Is that right Tesseract? More or less. Yes, the floor is all yours Okay. Hi At first sorry for the white background I hope it's not too too much for you and I will now Tell you something in more detail about SecureShare a distributed social network and in particularly About modeling trust with SecureShare so I will begin a little bit by explaining what I understand under with a Keyword trust Hopefully there is no Sciologist here in the audience and he may forgive me if I'm not perfect in a scientific sense, so What is what is trust if? We think of trust we Think of people who are behaving well to us and we think Then we can trust them we and And I'm not thinking about in information systems right now, but in our normal living that we trust in people who Support us in doing things Behaving well with our property or just support us and Trust is also depending on context and And There are two points here if we Think of trust in people we often group people into Different groups like family or colleagues and such and the second The context can switch So if we have some trust in people that trust can in some Context be maybe high and in another context it might be lower and The next thing is how we can handle if we Mistrust people and There we have the concept of anonymity that in the first place we give as less information about ourselves to people as possible and if we now think about information systems the things get more complex because in information systems if you give for example data to other people it can be Copy copied quite fast and given to other people and you have Quite fast problems in a in a big scale and if somebody is Doing something with your data for example, then it's Quite fast a big mess Okay, and here I have a list of Things or entities we normally have to trust in for example, we have to trust The hardware we are doing our daily work on we have to trust the software that is Running on that hardware. We have to trust platforms. We are using for example Google or or Facebook or such and We have to trust infrastructure operators like your ISPs or your mobile operators We have to trust server operators that for example are running the XMPP server you are using we have to trust our governments and For sure we have also to trust the social environment we are living in so Yes, I try and All those Things in the list have something in common and that is that more or less they are all Centralized entities like the platforms for example that are collecting data on their server infrastructure or The ISPs that are quite powerful because of their centralized being and some Solution to this is that we can decentralize and this is not only and this most of us I think think about this like having no central authorities But also with decentralized systems as you also can see from from the from the picture here have in smaller scale centralized nodes, so we also have the problem of centralization, but on another scale on a other scale and Solution to this is distributed systems and secure share and GNU net what is the base of secure share? Distributed systems Some could say that we also If you think of XMPP for example, everybody could run his own XMPP server and Then we do not need such this completely distributed systems But then we end up having scaling problems as I will explain later this is More or less common social graph with people interconnected with each other and if you think of non-distributed but decentralized systems and Those systems are trying to exchange Information informations they end up quite fast with a scaling problem because they are not Doing multicast most of the time if you compare multicast and Unicast routing of messages you see quite easily that messages are sent twice or more often than they need to be sent and secure share is doing multicast here to get rid of this scaling problem here like to Present to you a little bit more about the architecture of secure share as also links told you before the secure share is using GNU net and GNU net is made up of Several sub modules and we are not using all of them. There's quite interesting talk of the inventor of GNU net It's called 45 sub module sub modules in 45 minutes. So we are maybe using six of them and They are presented here in Layered so the the very basic one the GNU net core is used to do such things like Choosing which transports protocols are used and doing the basic link encryption the Caddits layer is doing the routing Using distributed hash table and doing the end-to-end encryption and the GNU net multicast layer is responsible for doing the multicasts to get rid of the scaling problem. I told you before the GNU net psych layer is a very Effective text messaging protocol we are using to to send the the messages and the Last layer before we have the app itself is the GNU net social layer Where we model different entities we are using for modeling the the trust in the application these entities are egos so in secret share you do not end up with one Username and you can use all of the time you can have different egos and each ego is On the on the technical side A key which identifies your ego and You can and there are nymphs nymphs are more or less the same than egos, but the the egos you you You communicate with and In secret share we have entity places this is Comparable to to chat rooms where those egos and nymphs can can meet up and exchange messages and and each place is Hosted by an entity called host and In those places you have other nymphs then that are called guests So now we Can have a look on how we model if we have Different nymphs we are talking to and we have different trust in them and For that purpose some user Alice could have different egos and depending on the context this Alice like to communicate you have Separated egos and those egos can then have separated Places For example we have here places like a family place or a friend's place and It's quite obvious that informations you share in the in the places in the Family place you do not want to share with those ones in the in the colleagues play place and You also see down there that I have there a place called psychiatrists. So Alice is talking to some psychiatrists via secret share and That one has also two nymphs so two identities and one of those identities is also a guest in his In Alice friends place so both of them do not know from the informations the The the application Gifts to them that they know each other from other places So places can also have different shapes. I compared them to chat rooms, but they can also be block pages or company websites and places also have can have attributes that are attached to those places and The there is no dedicated profile in secret share the profile some user sees is Aggregated by the places the the name is Gaston so Depending on in which places Other users are in they see different information from my particular ego Also places can inherit from each other for example if you have informations attached to the to the friends place those this place can The family place can inherit then the the friends place and Add additional information to the information that is already on the attached to the friends place Okay, so maybe we go back to that slide with the list who we have to trust and We are now secret share can help us to get rid of problems with those centralized entities and Okay, the hardware problem is out of scope for our project also the the software problem, but if we look at the infrastructure Secret share can definitely help us because As we already learned in links talk. There are different strategies to to have an anonymity and Therefore The data that is sent over our distributed network cannot be seen by for example your ISP Also, we have no problems regarding any platforms because there is no platform in this case and we also have no problem with any servers because there are no servers because in our case we have Distributed distributed network and each user of secure share is running a note by himself and do not has to trust in any in any server infrastructure so and also the trust in government in the List here the government could make any of the For example the infrastructure operator make To Spoof into your data. This is also not possible because they would need to Convince every every user of secret share to do this Okay So That's it. That was an amazing talk. Thank you very much tether, but they don't understand I also have three very difficult questions for you now that I have you here I was sitting right there and this young fellow next to me He was not paying attention. He was asking me all the questions that I will ask you now Okay, which one after these three questions. You can also ask questions The first thing which of these do you actually trust and how much do you trust them? The last one The social environment, okay now comes the other questions I have a dick pic Circling around in sick you share and do not and I do not want it to be circled around anymore. What can I do? Actually This depends also the the basic problem you have with any other social network is the same you have to be careful who you are Sending pictures So if it's already circling in a in a in some group you trust it and you cannot trust them Then you have also a problem and I cannot technically call back trust. Is that correct? Once it's out there. It's out there and social trust is all it that it keeps them. Yes I have a quest the last question from my side, then it's your guys's turn You know is our is human mankind able to behave well in trusted networks like sick you share and GNU net without any control of governments or server operators your word view on human behavior and human Typeness, do you think that we are ready to handle this kind of technology? I didn't get that exactly but There are also other problems sick you share cannot Cannot help because it's not a problem. You can solve technically so if You think of those kind of problems then sick you share cannot also not help But I do not know if I got it correctly Thank you very much. That was a difficult question because Bad human behavior cannot be solved by technicals things not even weapons We should all know that if anybody has a question to that ask Tesseract. Where can we find you later on? Also in the NGI assembly Great any questions Do you have a question? We on camera too, so so I add an answer regarding the social and social political aspects of sick you share I thought about it a lot and and so And it's There are several aspects to it we We have a different approach to most Decentralized chat systems. We don't try to make it an anarchic space But our chat rooms are usually owned by the person who starts it or something There's usually a kind of a responsibility chain Also, it's an we don't promote anonymity between people we promote anonymity against observers outside against Yeah, so Between the people we recommend people knowing each other and we don't even provide tools for people to find each other for Strange purposes, so if people want to meet because they have the same criminal intent It works better on a hidden hidden service in an in tour But sick you share doesn't model that so model the tick tick you share modeling is focused on on real world social Relationships So it is more applicable than to have on top Social structures like I want to have a moderator I want to have a justice system because I elected a court of arbitration or I want to call the police and I want to bring a person in front of a judge. So you can apply a traditional Rule of law later on maybe depending on the situation Thank you very much As you can see these guys can answer all the questions there are you find them in the NGI assembly