Building a social network on top of net2o, and importing your existing data I've a dream: A peer-to-peer network, where services like search engines or social networks aren't offered by big companies, who in turn need to make money by selling the privacy of their users. Where all data is encrypted, so that access is only possible for people who have the key and really are authorized. Which layman can use without cryptic user interfaces. Where the browser is a platform for running useful applications without the mess of Flash and JavaScript. Without the lag of “buffer bloat” and without the speed problems of a protocol not designed to be assisted by hardware. This dream is coming to reality: This talk will show how far I got, and what challenges still are ahead. The talk is in three parts: 1. a short overview over net2o 2. a demonstration of how the social network stuff looks like 3. and an outlook over what needs to be done to make it a polished product
 And now I'm very happy to introduce to you Bairnd Paeson, who is one of the GNU4th maintainers and who's the principal developer of Net2o. It's an alternative network stack as an overlay on UDP, which is quite interesting, and he has a dream. He wants to create an alternative, like he wants to fix the Internet and wants to create alternative infrastructure, and so he will speak about the cloud collapse. Thanks so much, Bairnd. Okay. So the cloud collapse is when the cloud collapses, and what do we do with the current cloud problems? We need a new Internet. The old one is broken. And so I started building Net2o about 10 years ago, bought them up, and now I'm reaching the top level, which is social networks, chat, the layer that comes between the user and the machine. And that is a progress report sort of because I've done a number of presentations on Net2o in the past. So my motivation is that the Internet is bad, gateway is broken in some ways. Six years ago at Snowden gave us a lot of insight what happened, but we don't need Americans, we don't even need Europeans, even when Germany can't break the Internet, there's a new law in discussion where telemedia providers are equalized to ISPs. You know, the ISPs have to hand over their data to the secret services, and as a telemedia provider that is something like YouTube, like Facebook, like Twitter, and there's a discussion about handing out passwords or similar account credentials to allow them to log into your account, take all your data there and manipulate like they want it. It's an online search of cloud data, and they also still want backdoors, which as Americans say is reasonable encryption and security guys says it's completely unreasonable if you give backdoors. And so you have rotated the topic of the month, one month it's terrorism, next month it's child power, and then it's protection of minors to force this again. So what do we have as progress? Well, alternatives, not just Net2O become more usable as alternatives. Also what I'm talking about Net2O, so the alternatives can talk for themselves better than I can do. And Snowden wrote a book in which he also talks about social networks and the introduction. So he said few of us understand it at that time, but none of the things that we'd go on to share would belong to us anymore. So it belongs to the companies. The successor of e-commerce companies have failed because they couldn't find anything we were interested in buying now had a new product to sell. That new product was us. So you are the product when you are on Twitter, Facebook, YouTube, and you are not the customer, you are the product, you are sold. And our attention, our activities, our locations, our desire, everything about us that we revealed knowing we are not was being surveyed and sold in secret. So as to delay, the inevitable feeling of violations that is for most of us coming only now and this surveillance would go on to be actively encouraged and even funded by an army of governments greedy for the vast volume of intelligence they would gain. That has some libertarian framing you find often in the American and UK world. But if the corporates do something, one thing is not as evil as if the government does the same thing. But in fact, it really doesn't matter. If the corporate takes your data and uses it to sell you stupid things you don't want, but they create the desire for you to buy a new iPhone every year or something like that. If I complain about SUVs and cities on Twitter, I get ads from companies which want to sell me SUVs. So they want to sell us products we don't need and the world is harmed by those products. It's not just the government is bad, it's also the companies are bad. So don't fall for this framing, it's not at that point when the government collects the data which is the bad part. It's already bad when the company is collected. We have some problems with people as well. One time I had this XKCD 386 as picture for what the companies want you to do. They want to stay you online and engage in heated discussions to get more of the adverts they want to show you. But we also have a problem with people online. The antithesis to the social network is the anti-social hate work. Why do people hate each other so much online? We have this problem not on Twitter. We have this since September, which is September 1993 when AOL connected the use net to the people who just bought these AOL CDs and put them in the cheap modem into the computer. And there are no longer students of elite universities but just normal people. And the reason is that opinions, when you talk about opinions are not about facts, it's about values people believe. And people believe things. It's not something that is open up for discussion for people. It's called values and their identity. And identity in discussion is vigorously defended and it's used to segregate people. So people in different communities have different identities, use different things to show their identity and if they clash on the Internet, they have the wall in the head. They don't need the wall around the community. And it causes them to be aggressive against these other opinions. And we had this free speech concept from the 17th, 18th century developed in a time where religion was strong and the communities were separated back at that time. So this free speech was about the states not intervening. So the communities themselves had a homogenous opinion, a homogenous belief and instead of having the head of state say what kind of religion you chose, your community chose yourself and the state doesn't engage. That is the free speech of that time and it helped coexistence of different beliefs but separated. And it also helped the people who did scientific research to do that against the dogmas of the church. But now we have communication between all these groups and we're no longer segregated. So we have to find a way around this and this is a social problem, it's not just the commerce which makes our life difficult online. The people themselves causes the problem. That is a non-technical problem but that is a problem of the commercial. When does try to amplify because they want to take you online and have you engage and don't go to bed, stay in the internet and watch the heated arguments and watch the adverts. So that's about, I showed this last year already, that is about how to design a network, a social network. We have centralized that is what the commercial do because it's easy to fund, it's also easier, a bit easier to develop and it has a lot of disadvantages. Then we have federated like Mastodon, Diaspora, which don't have this business model problems to take you captive but their business model doesn't give much money out. And then peer-to-peer in my opinion has the least problems from this control, control your own things but you are full responsible of your not, you don't get censorship. So that means you get all the hate speech or what you consider as hate speech because it violates your opinion and your belief, maybe for the other side it's not hate speech it's just defending their belief. You don't know but you don't like what they say and they don't like what you say so you are responsible to create a peaceful environment, good discussion, healthy discussion yourself which is difficult. And you are also responsible that no illegal things happen on your note which might cause some police interaction but when the police doesn't see you, they don't know if that is much of a problem for you but for society it might be a problem if too many things that are illegal for good reasons happen on this network. So what is Net2O? Net2O is a link to my video on the 313C where I went from 2 to 5 mostly with a bit of 6 so that is the starting point if you are interested in technical details. So that is the overlay network based on UDP. UDP is layer one, it's just a physical layer for Net2O using the current internet making sure you can pass through net address translated devices and can route from anywhere to anywhere without even when you are in a sort of captive environment have not so much freedom, not so much options to route. And peer to peer is a bit difficult for particular in IPv4 because we don't have enough addresses so all the traffic is net address translated somewhere. So how do I implement Net2O, social networks, what is the components? So I decided for text to format them in markdown, markdown is pretty popular and a lot of people know it already. Markdown has no very strict specifications so you can have slight modifications here and there. Markdown is not equal markdown but mostly the same. And I decided for very simple to decode images like JPEG and PNG, you don't have so much vulnerabilities. Movies that unfortunately cannot be done very simple so the container format should be something like MKV or WebM is a subset of MKV and inside like VT9 or AV1. Then comes the timeline. I have chat logs in the chat and this chat logs is a very universal structure. It's just one log is an entry and contains links to other things. So the chat log is for every data structure which has time discrete events. It's the master of this data structure. You can take other things out like the links like objects identified by hashes but the timeline in your social network essentially is a chat log. First thing is a distributed version control project and a distributed version control project itself is another chat log because every commit is a message in that system and a patch set of course or a snapshot. And a snapshot contains everything, a patch set just contains the differences. That helps to overcome this problem. How to edit something that is distributed peer to peer because essentially it's the right only thing. You can only write new messages out. You cannot really edit. So you can send out new things. You cannot easily recall them. But when you send out a patch it means I edit this file. So the other side knows I have to apply this change and that allows it to edit postings after the effect. And reshare is just take the VCS project from one timeline to another and post it there as message and the comment is similar to GitHub poll request. You create a forg of the project, you add your own comment, you try to push it back to the original owner and depending if there is automatic permission for you to post or if that person has said to moderate you, the poll request gets in immediately or after that person checks if your poll request is okay and accepts it. That allows you not only to comment, it allows you to edit the original message if there is permission for that. So you can use that Viki style where you edit the same document or you can use it Facebook style where you edit comment. That is just technology. This is all below the user interface. And likes is just direct chat log messages and of course it means you can send several likes or dislikes the last one counts. So last year I gave a talk on what I wanted to do. That was first finish the bike import for Google plus because Google plus is now dead. That is all you can do with Google plus is take it somewhere else. And that is a good motivation because actually if you have a living network, the motivation to take it somewhere else is always, yeah, but it already works. Google plus doesn't work. So there's a motivation to take it out and to be still able to read your own Google plus postings so it's not lost. And I figured also out I like to write a Twitter in part because Twitter looks simple. It's very short messages, just 280 characters, very few elements. You have hashtags, you have persons you can refer to. You have URLs, URLs and you have images. That is not difficult, but the difficult thing about Twitter is that it's usually ping-pong you communicate with somebody else and if you do a take out, you have only your own stuff. You don't have to reply to other people. So the take out in Twitter is mostly useless because if you have a threat of communication you want to represent in your decentralized network, you don't get it. Twitter fortunately has an API. So what I want to do is use that API to take out the actual things that reply to you. And that is more work than just import the take out. What was easy was to display the avatars, the markdown renderer. It took some time, it just takes the markdown, use my two UI to render it. Album viewer computed recently, but I don't, the app got stuck. This was a movie player on Linux because I wanted to use the Gstreamer interface and I want it to render into an OpenGL texture. It was simply rendered in an OpenGL texture and always opens me a window. I don't want a window, I have a window. I didn't figure out how to disable that. Otherwise it would not be so difficult. The key handover with the temporary key pair, every posting you get from another person when you're doing an importer needs a key because the chat message is signed by a key. This is not the real key of the real person because in Google plus or in Twitter they don't have keys, they just have accounts. They don't have net to O keys. They don't have, there's no authentication on these messages. You have to believe Google or Twitter or Facebook that what these people wrote really is from these people. You have to trust the platform. There's no inherent trust. From the peer-to-peer network you cannot trust the platform. Definitely not. Peer-to-peer, everybody can do anything. You have to trust the encryption. You have to trust the cryptography. So everybody needs a key. The key handover, this means when you have talked to some people on Google plus and both of them imported the Google plus data or Twitter data and you now share the keys and handover these temporary keys, make them invalid and replace that by the real key. I've not done that yet. It's not so important at the moment that Mark imported keys as not trustworthy was easy and very quickly to do. So I have now some hands on. So when you start the net to O, you get this huge netty. You can enter your password and then you get your list of imported data that is already imported from Google plus my account. For example, here I have a lot of photos. This is what I want to change in style. That is just the chat log now. The chat log is not completely appropriate here as display. The status structure is perfect, the display style should go on this side, should maybe have a thumbnail for every posting that has a photo. And it's not looking so nice, but what we can see when we go in is it looks not exactly like Google plus, but you see a lot of photos. And you can click on the photos, see the details and scroll between the photos. These are photos I took in my HDR phase of photography. So they are all done with the HDR and in Changsha chair, wonderful place in China. So the eBurnViewer works and that means you can import your photo section and watch them. You can also talk, take your things about political discussion here. For example, it's one of those typical discussions I had about the BND law. So we have comments here and this is just markdown rendered. All the comments are markdown rendered and have other tasks of these people displaying. So what works now is looking at what you did. What's missing now yet is that you create new postings and create new comments. That means add an editor. It's just work, it's drunk work. It's not a difficult thing. And go back because there were more challenges coming up. One challenge came up last year just before the presentations because the hacker said, oh, it's too bright. It's way too bright because it looked like this. We want a night mode. So now we have colored teams. You can switch between day and night mode and you could have more colored teams if you want to have a color team with bright colors or color team with dull colors for people who say, ah, I'm from the artistic spectrum. Don't show me bright colors. I'm epileptic. This black and white only. Then what I figured out is some JPEGs actually don't have thumbnails in it from cameras. I used to have cameras where everything had a thumbnail and I used the thumbnail all the time. And now my Galaxy Note 8 sometimes adds a thumbnail. But it's unreliable. There's a library from the Enlightenment Project which can open JPEGs very quickly if you specify that you only want a very small portion of it. And I need to add that if there's no thumbnail, I need to use this because if you load in one of these image albums with 200, 300 pictures, you want to load them in quickly. And that means thumbnails only. One picture, large, the rest thumbnails. Then that was the protocol challenge. That is what is the, who has what. I have a detail about this because each object is somewhere in the peer-to-peer network. You need to get it and you only get it when you have the right to get it, when you have the right to know it. It's not something the entire world should know that it's out there and can get. So the original plan was something like, I used like the Vittoran network where I have a DHT where every object is globally visible but it's not a good idea. And my original solution was to encrypt the sashes and provide the key to that. But it still has the same problem. If you have a query, I want this encrypted hash. You don't know what it is, but you know the same people want the same thing. You don't know what it is, but you know it's the same thing and the same people want it. That already reveals information about who is networked and maybe you can figure out how to get in. So another possible solution would be onion routing within the DHT. So you make the query to one node of the DHT and go through an onion routing to the DHT node who answers it. That is a solution. It's complex and slow. So I don't want it and that's a shortcut because the people who talk with you have the chat log structure shared with you. Already know who has what because they shared part of it before. So you can put that who has what within the chat log structure synchronized with the chat log and then you can ask the people connected to you, please send me this file, send me this patch set. Who means device.pubkey, unlike WhatsApp and other protocols out there now, you have multi-device ability, so you need to specify on which device is this file and pubkey is the owner of this device. Then you can connect to this device, ask for this object and it does not go outside this channel, this closed group you are talking with. So what the next thing was comfortable ID cloning. If you have multi-devices, you want to copy your ID from one device to the other and that does to be very simple for the normal user. So you need authorized remote file access. Fortunately, we have a protocol for Z, it's net2o, but you need to establish authorization. You don't have authorized key. So you first scan one of these color QR codes, send an invitation packet back that shows you have actually scanned this color QR code and are in proximity to the device. You get a confirmation by different color QR and then you can do a zero-knowledge proof of I have the password you choose to protect the secret key. So you are really the same person, it's not somebody wanting to steal your device, your ID. And then you have a proof of authority and then you can send over the keys with that net2o connection. So you are not completely finished now, that is from here the last two steps is still missing. There's an ETF task group who talks about general ideas how to do this, comes from the people in Switzerland doing that for email, because for email you already have this multiple device solution for a long time and you need to make easy ways to hand over your keys between your devices, the secure way. So then there's the permissions because now when you talk to people in the chat room you may choose different models how to moderate, do I have something in the permissions? No. Who are you allowed to post automatically without moderation, who do you want to moderate and who do you want to just read only your blog. Some people like to read only blogs like Fifi for example, this makes perfectly sense to define roles and permissions. And that wasn't in there, so that needs to be done. The likes really only the last one needs to count otherwise one person can send a thousand likes, that does not make much sense. Before I had one to one chats which were closed and group chats which were open to everybody who found the chat ID, now I added closed group chat, that is necessary if you want to kick out somebody. They already know the chat ID, you don't want to move that over to a new chat ID, lose everybody in the process, you just want to kick out. So you have a session key inside the chat which you share and if the person does not figure out how to get the session key because they can't open the session key, they don't have the necessary private key, secret key, they are out and they can get in again. So you can say okay, we make, we ban you for ten minutes and after ten minutes you are in back if you calm down and then you can continue. And you need permissions for moderator, normally only yourself can cancel messages. But if you have a heated discussion, a moderator may say oh, I want to cancel this, not legal speech in our country or insulting persons, it's better to delete it. That is within the group, that is not from outside in person, it makes a lot of sense if you have heated discussion, you don't want to have everything, you want to close lockdown groups at some time or you want to remove persons or you want to remove only some postings of them. And then as a meta data, the shareable list of collection you have, what you saw in my demonstration is at the moment not shareable, you need to know that. But I want to make use of this chat log structure there too so you can synchronize it, share it. And the last one, when you are roaming, when you are in different countries, have a Wi-Fi in the hotel or somewhere, you often encounter these port 53 UDP and 84.3 TCP only networks, you cannot do anything else on the web. The DNS is just going to the local resolver, so you cannot use DNS throughout, you can only use HTTP. So my idea is use something like WebSockets for this, have a server you can connect with WebSockets and on the client on the other side, it just pushes out the UDP packets. This needs to be done, I think it's not much work because WebSockets, you have libraries for that, do I have something for this? Yeah, that's here. One problematic part here is that the adversary like the great firewall of China tests this kind of connections. They do this for the Tor project, so if you make a connection with the Tor from inside China, the great firewall also tries to open the Tor protocol link to the same server and if they get one, then they close down the entire server. So you maybe can open Tor for half a minute and then the backlog of the server trying, removing all these things also opened it and then this Tor entry node is blocked forever and it's on a dynamic IP address, it means for one day, but this means from China it's useless. So add authorization and you need single packet authorizations, not hip, hop, hip, because if the hop comes back, it's already in answer where you see the answer to this protocol. You can send one packet out and it needs to contain everything for the authorization and it needs to make sure it's not revealing anything for the attacker. It does not reveal what kind of protocol it is, it does not reveal any identity of you or the other side, so it's just a random garbage send out and some random garbage comes in and then it goes and if they try to open it, they will fail because they don't have the authorization for it, they don't have a key known to this point. So that needs a change in the network connection setup because I need a single package authorization. Now I do the authorization with three-way handshake, it's easier to do, but it's also possible to do it with a single handshake. So this gives another improvement because with the nut traversal I have now a five-way handshake. I make a three-way handshake over the DHT route, some DHT forwards my packets and then I open up the net traversal. And so I could get one route around for the authorization and in the back already start opening up the net traversal, gives me one RTD less. It's not very important for low latency networks, but if you are far apart on the world then it helps, then you realize that that's what I'm now working on also that helps for this closed lockdown networks. Last year in China I was there in August and on August 1st the entire network of China mobile switched to IPv6, opened up IPv6. What they did at the same time is they changed their great firewall to this lockdown policy, probably because they don't have good code for targeted filtering in place for IPv6. They have for IPv4, they don't need the strict lockdown, but they don't have for IPv6. It's all new, so they just open the web and it's limited pretty much. And you don't see that when you go and Google an IPv6 deployment you don't see any of those 700 million devices that have now IPv6. You don't see any, they don't reach Google. It's not that they are not there, it's just they don't reach Google. Google doesn't know anything about that. So anything else? Yeah, that was it. So there are some non-technical problems with Net2O, that is when you have a lot of contacts in the Google Plus, Twitter, blah, blah, blah, you need to get them over to Net2O, you need to encourage them to install Net2O. It needs to work stable, it needs to be complete, it needs to be user-friendly, otherwise they don't come. Your contacts will not come when it's difficult. The second problem is how to make a social network a nice place. If you have these problems in the existing social networks, they are not nice places because the ad-based business model makes sure they don't become nice, they shouldn't become nice. The only nice thing is for these are the adverts, the ones who make you happy. So you buy the products. The other things should not make you happy, they should engage you and look at more adverts. And then there are some funding, I want funding. And I have thought about using this cryptocurrency, I started developing two years ago, but the cryptocurrency funding business is very toxic. You get a lot of money, but you get this toxic idiots, which want to get rich quickly. And the scammers, that is a conflict of ethics for me. So getting funded is one thing, but getting a toxic community of scammers and they manipulate the currency like Bitcoin and have this Tesla thing, which is very, very much a fraud. And I don't want to have this on my side. So I'm looking for other ways to fund things. I want to make an app that is sold on the app store and it will turn out. And I think it's not, if there's a somehow polished product, you can get enough money to sustain it because it's not, I don't need billions of Facebook needs to operate these things. I'm only doing the software development. Facebook has a lot of servers. You have to think about the resources you have in the cloud. You have to duplicate a lot of data. You have to duplicate a lot of processing. If you communicate peer-to-peer, you have your photos on your own device, anyhow. But if you want to use a cloud service to communicate, you have to make copies of them. They have to keep this data as well. And they have to use some delivery, content delivery networks as they duplicate several times. It's just not one copy. It's not enough. Especially if you share a lot to many people. In the peer-to-peer network, if you share a lot, then the copy of your data is out already a lot of times. Everybody got it, can share it again. But in the centralized thing, you need these copies done in the CDNs of the providers and it weighs a lot of energy there and a lot of hardware resources go in just to share some photos. And it's not free of charge. As a value of one Facebook user, I think it's in the several hundred dollar range. That is the value from you buying the useless things they want you to buy by the ads. And that is how they fund their business. So you really are an expensive product. It's not cheap. You have to think about this. So last page is this time I only give the starting point and these two color QR codes, I've tried with the night mode but the cameras have problems with the white balance. Here the day mode has a big white rectangle. So if you scan it with the Net2O app. This one is a blimp. If you're not perspective corrections and it's difficult but if you're straight heading it is just very easy. It's not even focusing it and then it scans it. This one is difficult because there's yellow and the white balance says, ah, this is probably white. But when it's probably white, it's wrong. It cannot scan correctly. So you need the white balance in the night mode. Sometimes works maybe with a projector. When you still have enough gray in the background it can work. This one is very reliable. This is the day mode. And that the color QRs are the means for people with mobile phones to quickly share their identities and connect to each other. People don't like to enter cryptic things no matter how you present them but they are very happy to scan QR codes. That is solving the so called triangle because you have to, when you get your contacts, you need a human meaningful name and figure out how it is connected to this cryptographic key. But if you can scan the key directly with a needset. So that's my talk. And if there are questions you can ask me now or later at the Forest Gesellschaft Bus. Thanks so much, Bern. If you have any questions you can raise your hand now and I will come to you with a microphone. And I can also come to the signal angel if you have any questions. Okay, not yet. So and also after the talk you can of course approach him directly. Maybe I'm not sure if it's a really relevant question but you said we cost 100, I mean we, not me, but some people cost 100 Euro for Facebook. Is that per, what is the time units? Like it's an ongoing cost or is it 100 Euro per year or something like that? But I'm planning, you mean the price for the app? The price for the app will be in the low Euro rate because you don't want to, if I sell 1 million apps for 2 or 3 Euros the funding is completely done. I don't need more. I just need to sell 1 million apps or so. And compared to how many uses you get for WhatsApp or WeChat or Telegram, 1 million is little. I don't even need to have everybody to pay it. I can make this voluntarily. I can give out a free app and if you want to donate you buy the Silver as a gold app. And when you go to Google Store you need to do the funding via their payment system. They don't like any other methods. They want their 30% share and because they do a lot of this infrastructure is okay for me. Give them 30%. It's not a big deal. I don't, when you are an institutional investor you can give me some 10,000 Euro. That is completely different. But if you are a private person I don't want to take a lot of money from you. One more question and we'll be back here. Yeah. Hi. You mentioned CDNs, content delivery. I was wondering if you have some sort of multicast in Net2o for doing. So if I send a message to a friend and then I forward that message to another friend but they have a closer link. Is it going to be shared from the first person I shared it to? That is what the peer-to-peer network comes in. When you share something with your friend, you send them your data. I have, and they copy your objects and forward that they also have it to their friends. So the friends now can choose where to download from their friends, from you, they have more options. So a peer-to-peer network is a content delivery network by nature. That is what it's supposed to be. The content delivery networks actually internally work like peer-to-peer networks. Use the same technology. They just don't give the end users the freedom to be part of this peer-to-peer network. They don't want you to be part of the network. You are the product. You are not part of the community. Thank you so much, Ben, for your talk. It was very interesting. There were more questions coming up, I think, directly afterwards in private to find out more about it. Thank you very much for presenting that at Open Infrastructure Orbit at Congress. Thank you.
 And now I'm very happy to introduce to you Bairnd Paeson, who is one of the GNU4th maintainers  and who's the principal developer of Net2o.  It's an alternative network stack as an overlay on UDP, which is quite interesting, and he  has a dream.  He wants to create an alternative, like he wants to fix the Internet and wants to create  alternative infrastructure, and so he will speak about the cloud collapse.  Thanks so much, Bairnd.  Okay.  So the cloud collapse is when the cloud collapses, and what do we do with the current cloud  problems?  We need a new Internet.  The old one is broken.  And so I started building Net2o about 10 years ago, bought them up, and now I'm reaching  the top level, which is social networks, chat, the layer that comes between the user and  the machine.  And that is a progress report sort of because I've done a number of presentations on Net2o  in the past.  So my motivation is that the Internet is bad, gateway is broken in some ways.  Six years ago at Snowden gave us a lot of insight what happened, but we don't need Americans,  we don't even need Europeans, even when Germany can't break the Internet, there's a new law  in discussion where telemedia providers are equalized to ISPs.  You know, the ISPs have to hand over their data to the secret services, and as a telemedia  provider that is something like YouTube, like Facebook, like Twitter, and there's a discussion  about handing out passwords or similar account credentials to allow them to log into your  account, take all your data there and manipulate like they want it.  It's an online search of cloud data, and they also still want backdoors, which as Americans  say is reasonable encryption and security guys says it's completely unreasonable if  you give backdoors.  And so you have rotated the topic of the month, one month it's terrorism, next month it's  child power, and then it's protection of minors to force this again.  So what do we have as progress?  Well, alternatives, not just Net2O become more usable as alternatives.  Also what I'm talking about Net2O, so the alternatives can talk for themselves better  than I can do.  And Snowden wrote a book in which he also talks about social networks and the introduction.  So he said few of us understand it at that time, but none of the things that we'd go  on to share would belong to us anymore.  So it belongs to the companies.  The successor of e-commerce companies have failed because they couldn't find anything  we were interested in buying now had a new product to sell.  That new product was us.  So you are the product when you are on Twitter, Facebook, YouTube, and you are not the customer,  you are the product, you are sold.  And our attention, our activities, our locations, our desire, everything about us that we revealed  knowing we are not was being surveyed and sold in secret.  So as to delay, the inevitable feeling of violations that is for most of us coming only  now and this surveillance would go on to be actively encouraged and even funded by an army  of governments greedy for the vast volume of intelligence they would gain.  That has some libertarian framing you find often in the American and UK world.  But if the corporates do something, one thing is not as evil as if the government does the  same thing.  But in fact, it really doesn't matter.  If the corporate takes your data and uses it to sell you stupid things you don't want,  but they create the desire for you to buy a new iPhone every year or something like that.  If I complain about SUVs and cities on Twitter, I get ads from companies which want to sell  me SUVs.  So they want to sell us products we don't need and the world is harmed by those products.  It's not just the government is bad, it's also the companies are bad.  So don't fall for this framing, it's not at that point when the government collects the  data which is the bad part.  It's already bad when the company is collected.  We have some problems with people as well.  One time I had this XKCD 386 as picture for what the companies want you to do.  They want to stay you online and engage in heated discussions to get more of the adverts  they want to show you.  But we also have a problem with people online.  The antithesis to the social network is the anti-social hate work.  Why do people hate each other so much online?  We have this problem not on Twitter.  We have this since September, which is September 1993 when AOL connected the use net to the  people who just bought these AOL CDs and put them in the cheap modem into the computer.  And there are no longer students of elite universities but just normal people.  And the reason is that opinions, when you talk about opinions are not about facts, it's  about values people believe.  And people believe things.  It's not something that is open up for discussion for people.  It's called values and their identity.  And identity in discussion is vigorously defended and it's used to segregate people.  So people in different communities have different identities, use different things to show their  identity and if they clash on the Internet, they have the wall in the head.  They don't need the wall around the community.  And it causes them to be aggressive against these other opinions.  And we had this free speech concept from the 17th, 18th century developed in a time where  religion was strong and the communities were separated back at that time.  So this free speech was about the states not intervening.  So the communities themselves had a homogenous opinion, a homogenous belief and instead of  having the head of state say what kind of religion you chose, your community chose  yourself and the state doesn't engage.  That is the free speech of that time and it helped coexistence of different beliefs but  separated.  And it also helped the people who did scientific research to do that against the dogmas of  the church.  But now we have communication between all these groups and we're no longer segregated.  So we have to find a way around this and this is a social problem, it's not just the commerce  which makes our life difficult online.  The people themselves causes the problem.  That is a non-technical problem but that is a problem of the commercial.  When does try to amplify because they want to take you online and have you engage and  don't go to bed, stay in the internet and watch the heated arguments and watch the adverts.  So that's about, I showed this last year already, that is about how to design a network, a social  network.  We have centralized that is what the commercial do because it's easy to fund, it's also  easier, a bit easier to develop and it has a lot of disadvantages.  Then we have federated like Mastodon, Diaspora, which don't have this business model problems  to take you captive but their business model doesn't give much money out.  And then peer-to-peer in my opinion has the least problems from this control, control  your own things but you are full responsible of your not, you don't get censorship.  So that means you get all the hate speech or what you consider as hate speech because  it violates your opinion and your belief, maybe for the other side it's not hate speech  it's just defending their belief.  You don't know but you don't like what they say and they don't like what you say so you  are responsible to create a peaceful environment, good discussion, healthy discussion yourself  which is difficult.  And you are also responsible that no illegal things happen on your note which might cause  some police interaction but when the police doesn't see you, they don't know if that is  much of a problem for you but for society it might be a problem if too many things that  are illegal for good reasons happen on this network.  So what is Net2O?  Net2O is a link to my video on the 313C where I went from 2 to 5 mostly with a bit of 6  so that is the starting point if you are interested in technical details.  So that is the overlay network based on UDP.  UDP is layer one, it's just a physical layer for Net2O using the current internet making  sure you can pass through net address translated devices and can route from anywhere to anywhere  without even when you are in a sort of captive environment have not so much freedom, not  so much options to route.  And peer to peer is a bit difficult for particular in IPv4 because we don't have enough addresses  so all the traffic is net address translated somewhere.  So how do I implement Net2O, social networks, what is the components?  So I decided for text to format them in markdown, markdown is pretty popular and a lot of people  know it already.  Markdown has no very strict specifications so you can have slight modifications here  and there.  Markdown is not equal markdown but mostly the same.  And I decided for very simple to decode images like JPEG and PNG, you don't have so much  vulnerabilities.  Movies that unfortunately cannot be done very simple so the container format should be something  like MKV or WebM is a subset of MKV and inside like VT9 or AV1.  Then comes the timeline.  I have chat logs in the chat and this chat logs is a very universal structure.  It's just one log is an entry and contains links to other things.  So the chat log is for every data structure which has time discrete events.  It's the master of this data structure.  You can take other things out like the links like objects identified by hashes but the  timeline in your social network essentially is a chat log.  First thing is a distributed version control project and a distributed version control  project itself is another chat log because every commit is a message in that system and  a patch set of course or a snapshot.  And a snapshot contains everything, a patch set just contains the differences.  That helps to overcome this problem.  How to edit something that is distributed peer to peer because essentially it's the  right only thing.  You can only write new messages out.  You cannot really edit.  So you can send out new things.  You cannot easily recall them.  But when you send out a patch it means I edit this file.  So the other side knows I have to apply this change and that allows it to edit postings  after the effect.  And reshare is just take the VCS project from one timeline to another and post it there  as message and the comment is similar to GitHub poll request.  You create a forg of the project, you add your own comment, you try to push it back  to the original owner and depending if there is automatic permission for you to post or  if that person has said to moderate you, the poll request gets in immediately or after  that person checks if your poll request is okay and accepts it.  That allows you not only to comment, it allows you to edit the original message if there  is permission for that.  So you can use that Viki style where you edit the same document or you can use it Facebook  style where you edit comment.  That is just technology.  This is all below the user interface.  And likes is just direct chat log messages and of course it means you can send several  likes or dislikes the last one counts.  So last year I gave a talk on what I wanted to do.  That was first finish the bike import for Google plus because Google plus is now dead.  That is all you can do with Google plus is take it somewhere else.  And that is a good motivation because actually if you have a living network, the motivation  to take it somewhere else is always, yeah, but it already works.  Google plus doesn't work.  So there's a motivation to take it out and to be still able to read your own Google plus  postings so it's not lost.  And I figured also out I like to write a Twitter in part because Twitter looks simple.  It's very short messages, just 280 characters, very few elements.  You have hashtags, you have persons you can refer to.  You have URLs, URLs and you have images.  That is not difficult, but the difficult thing about Twitter is that it's usually ping-pong  you communicate with somebody else and if you do a take out, you have only your own stuff.  You don't have to reply to other people.  So the take out in Twitter is mostly useless because if you have a threat of communication  you want to represent in your decentralized network, you don't get it.  Twitter fortunately has an API.  So what I want to do is use that API to take out the actual things that reply to you.  And that is more work than just import the take out.  What was easy was to display the avatars, the markdown renderer.  It took some time, it just takes the markdown, use my two UI to render it.  Album viewer computed recently, but I don't, the app got stuck.  This was a movie player on Linux because I wanted to use the Gstreamer interface and  I want it to render into an OpenGL texture.  It was simply rendered in an OpenGL texture and always opens me a window.  I don't want a window, I have a window.  I didn't figure out how to disable that.  Otherwise it would not be so difficult.  The key handover with the temporary key pair, every posting you get from another person  when you're doing an importer needs a key because the chat message is signed by a key.  This is not the real key of the real person because in Google plus or in Twitter they  don't have keys, they just have accounts.  They don't have net to O keys.  They don't have, there's no authentication on these messages.  You have to believe Google or Twitter or Facebook that what these people wrote really is from  these people.  You have to trust the platform.  There's no inherent trust.  From the peer-to-peer network you cannot trust the platform.  Definitely not.  Peer-to-peer, everybody can do anything.  You have to trust the encryption.  You have to trust the cryptography.  So everybody needs a key.  The key handover, this means when you have talked to some people on Google plus and both  of them imported the Google plus data or Twitter data and you now share the keys and handover  these temporary keys, make them invalid and replace that by the real key.  I've not done that yet.  It's not so important at the moment that Mark imported keys as not trustworthy was easy  and very quickly to do.  So I have now some hands on.  So when you start the net to O, you get this huge netty.  You can enter your password and then you get your list of imported data that is already  imported from Google plus my account.  For example, here I have a lot of photos.  This is what I want to change in style.  That is just the chat log now.  The chat log is not completely appropriate here as display.  The status structure is perfect, the display style should go on this side, should maybe  have a thumbnail for every posting that has a photo.  And it's not looking so nice, but what we can see when we go in is it looks not exactly  like Google plus, but you see a lot of photos.  And you can click on the photos, see the details and scroll between the photos.  These are photos I took in my HDR phase of photography.  So they are all done with the HDR and in Changsha chair, wonderful place in China.  So the eBurnViewer works and that means you can import your photo section and watch them.  You can also talk, take your things about political discussion here.  For example, it's one of those typical discussions I had about the BND law.  So we have comments here and this is just markdown rendered.  All the comments are markdown rendered and have other tasks of these people displaying.  So what works now is looking at what you did.  What's missing now yet is that you create new postings and create new comments.  That means add an editor.  It's just work, it's drunk work.  It's not a difficult thing.  And go back because there were more challenges coming up.  One challenge came up last year just before the presentations because the hacker said,  oh, it's too bright.  It's way too bright because it looked like this.  We want a night mode.  So now we have colored teams.  You can switch between day and night mode and you could have more colored teams if you  want to have a color team with bright colors or color team with dull colors for people  who say, ah, I'm from the artistic spectrum.  Don't show me bright colors.  I'm epileptic.  This black and white only.  Then what I figured out is some JPEGs actually don't have thumbnails in it from cameras.  I used to have cameras where everything had a thumbnail and I used the thumbnail all the  time.  And now my Galaxy Note 8 sometimes adds a thumbnail.  But it's unreliable.  There's a library from the Enlightenment Project which can open JPEGs very quickly if you specify  that you only want a very small portion of it.  And I need to add that if there's no thumbnail, I need to use this because if you load in  one of these image albums with 200, 300 pictures, you want to load them in quickly.  And that means thumbnails only.  One picture, large, the rest thumbnails.  Then that was the protocol challenge.  That is what is the, who has what.  I have a detail about this because each object is somewhere in the peer-to-peer network.  You need to get it and you only get it when you have the right to get it, when you have  the right to know it.  It's not something the entire world should know that it's out there and can get.  So the original plan was something like, I used like the Vittoran network where I have  a DHT where every object is globally visible but it's not a good idea.  And my original solution was to encrypt the sashes and provide the key to that.  But it still has the same problem.  If you have a query, I want this encrypted hash.  You don't know what it is, but you know the same people want the same thing.  You don't know what it is, but you know it's the same thing and the same people want it.  That already reveals information about who is networked and maybe you can figure out  how to get in.  So another possible solution would be onion routing within the DHT.  So you make the query to one node of the DHT and go through an onion routing to the DHT  node who answers it.  That is a solution.  It's complex and slow.  So I don't want it and that's a shortcut because the people who talk with you have the chat log  structure shared with you.  Already know who has what because they shared part of it before.  So you can put that who has what within the chat log structure synchronized with the chat  log and then you can ask the people connected to you, please send me this file, send me  this patch set.  Who means device.pubkey, unlike WhatsApp and other protocols out there now, you have multi-device  ability, so you need to specify on which device is this file and pubkey is the owner of this  device.  Then you can connect to this device, ask for this object and it does not go outside this  channel, this closed group you are talking with.  So what the next thing was comfortable ID cloning.  If you have multi-devices, you want to copy your ID from one device to the other and that  does to be very simple for the normal user.  So you need authorized remote file access.  Fortunately, we have a protocol for Z, it's net2o, but you need to establish authorization.  You don't have authorized key.  So you first scan one of these color QR codes, send an invitation packet back that shows  you have actually scanned this color QR code and are in proximity to the device.  You get a confirmation by different color QR and then you can do a zero-knowledge proof  of I have the password you choose to protect the secret key.  So you are really the same person, it's not somebody wanting to steal your device, your  ID.  And then you have a proof of authority and then you can send over the keys with that net2o  connection.  So you are not completely finished now, that is from here the last two steps is still missing.  There's an ETF task group who talks about general ideas how to do this, comes from the  people in Switzerland doing that for email, because for email you already have this multiple  device solution for a long time and you need to make easy ways to hand over your keys between  your devices, the secure way.  So then there's the permissions because now when you talk to people in the chat room you  may choose different models how to moderate, do I have something in the permissions?  No.  Who are you allowed to post automatically without moderation, who do you want to moderate and  who do you want to just read only your blog.  Some people like to read only blogs like Fifi for example, this makes perfectly sense to  define roles and permissions.  And that wasn't in there, so that needs to be done.  The likes really only the last one needs to count otherwise one person can send a thousand  likes, that does not make much sense.  Before I had one to one chats which were closed and group chats which were open to everybody  who found the chat ID, now I added closed group chat, that is necessary if you want to kick  out somebody.  They already know the chat ID, you don't want to move that over to a new chat ID, lose everybody  in the process, you just want to kick out.  So you have a session key inside the chat which you share and if the person does not  figure out how to get the session key because they can't open the session key, they don't  have the necessary private key, secret key, they are out and they can get in again.  So you can say okay, we make, we ban you for ten minutes and after ten minutes you are  in back if you calm down and then you can continue.  And you need permissions for moderator, normally only yourself can cancel messages.  But if you have a heated discussion, a moderator may say oh, I want to cancel this, not legal  speech in our country or insulting persons, it's better to delete it.  That is within the group, that is not from outside in person, it makes a lot of sense  if you have heated discussion, you don't want to have everything, you want to close lockdown  groups at some time or you want to remove persons or you want to remove only some postings  of them.  And then as a meta data, the shareable list of collection you have, what you saw in my  demonstration is at the moment not shareable, you need to know that.  But I want to make use of this chat log structure there too so you can synchronize it, share  it.  And the last one, when you are roaming, when you are in different countries, have a Wi-Fi  in the hotel or somewhere, you often encounter these port 53 UDP and 84.3 TCP only networks,  you cannot do anything else on the web.  The DNS is just going to the local resolver, so you cannot use DNS throughout, you can  only use HTTP.  So my idea is use something like WebSockets for this, have a server you can connect with  WebSockets and on the client on the other side, it just pushes out the UDP packets.  This needs to be done, I think it's not much work because WebSockets, you have libraries  for that, do I have something for this?  Yeah, that's here.  One problematic part here is that the adversary like the great firewall of China tests this  kind of connections.  They do this for the Tor project, so if you make a connection with the Tor from inside  China, the great firewall also tries to open the Tor protocol link to the same server and  if they get one, then they close down the entire server.  So you maybe can open Tor for half a minute and then the backlog of the server trying,  removing all these things also opened it and then this Tor entry node is blocked forever  and it's on a dynamic IP address, it means for one day, but this means from China it's  useless.  So add authorization and you need single packet authorizations, not hip, hop, hip, because  if the hop comes back, it's already in answer where you see the answer to this protocol.  You can send one packet out and it needs to contain everything for the authorization and  it needs to make sure it's not revealing anything for the attacker.  It does not reveal what kind of protocol it is, it does not reveal any identity of you  or the other side, so it's just a random garbage send out and some random garbage comes in  and then it goes and if they try to open it, they will fail because they don't have the  authorization for it, they don't have a key known to this point.  So that needs a change in the network connection setup because I need a single package authorization.  Now I do the authorization with three-way handshake, it's easier to do, but it's also possible  to do it with a single handshake.  So this gives another improvement because with the nut traversal I have now a five-way  handshake.  I make a three-way handshake over the DHT route, some DHT forwards my packets and then  I open up the net traversal.  And so I could get one route around for the authorization and in the back already start  opening up the net traversal, gives me one RTD less.  It's not very important for low latency networks, but if you are far apart on the world then  it helps, then you realize that that's what I'm now working on also that helps for this  closed lockdown networks.  Last year in China I was there in August and on August 1st the entire network of China  mobile switched to IPv6, opened up IPv6.  What they did at the same time is they changed their great firewall to this lockdown policy,  probably because they don't have good code for targeted filtering in place for IPv6.  They have for IPv4, they don't need the strict lockdown, but they don't have for IPv6.  It's all new, so they just open the web and it's limited pretty much.  And you don't see that when you go and Google an IPv6 deployment you don't see any of those  700 million devices that have now IPv6.  You don't see any, they don't reach Google.  It's not that they are not there, it's just they don't reach Google.  Google doesn't know anything about that.  So anything else?  Yeah, that was it.  So there are some non-technical problems with Net2O, that is when you have a lot of contacts  in the Google Plus, Twitter, blah, blah, blah, you need to get them over to Net2O, you  need to encourage them to install Net2O.  It needs to work stable, it needs to be complete, it needs to be user-friendly, otherwise they  don't come.  Your contacts will not come when it's difficult.  The second problem is how to make a social network a nice place.  If you have these problems in the existing social networks, they are not nice places  because the ad-based business model makes sure they don't become nice, they shouldn't  become nice.  The only nice thing is for these are the adverts, the ones who make you happy.  So you buy the products.  The other things should not make you happy, they should engage you and look at more adverts.  And then there are some funding, I want funding.  And I have thought about using this cryptocurrency, I started developing two years ago, but the  cryptocurrency funding business is very toxic.  You get a lot of money, but you get this toxic idiots, which want to get rich quickly.  And the scammers, that is a conflict of ethics for me.  So getting funded is one thing, but getting a toxic community of scammers and they manipulate  the currency like Bitcoin and have this Tesla thing, which is very, very much a fraud.  And I don't want to have this on my side.  So I'm looking for other ways to fund things.  I want to make an app that is sold on the app store and it will turn out.  And I think it's not, if there's a somehow polished product, you can get enough money  to sustain it because it's not, I don't need billions of Facebook needs to operate these  things.  I'm only doing the software development.  Facebook has a lot of servers.  You have to think about the resources you have in the cloud.  You have to duplicate a lot of data.  You have to duplicate a lot of processing.  If you communicate peer-to-peer, you have your photos on your own device, anyhow.  But if you want to use a cloud service to communicate, you have to make copies of them.  They have to keep this data as well.  And they have to use some delivery, content delivery networks as they duplicate several  times.  It's just not one copy.  It's not enough.  Especially if you share a lot to many people.  In the peer-to-peer network, if you share a lot, then the copy of your data is out already  a lot of times.  Everybody got it, can share it again.  But in the centralized thing, you need these copies done in the CDNs of the providers and  it weighs a lot of energy there and a lot of hardware resources go in just to share some  photos.  And it's not free of charge.  As a value of one Facebook user, I think it's in the several hundred dollar range.  That is the value from you buying the useless things they want you to buy by the ads.  And that is how they fund their business.  So you really are an expensive product.  It's not cheap.  You have to think about this.  So last page is this time I only give the starting point and these two color QR codes,  I've tried with the night mode but the cameras have problems with the white balance.  Here the day mode has a big white rectangle.  So if you scan it with the Net2O app.  This one is a blimp.  If you're not perspective corrections and it's difficult but if you're straight heading  it is just very easy.  It's not even focusing it and then it scans it.  This one is difficult because there's yellow and the white balance says, ah, this is probably  white.  But when it's probably white, it's wrong.  It cannot scan correctly.  So you need the white balance in the night mode.  Sometimes works maybe with a projector.  When you still have enough gray in the background it can work.  This one is very reliable.  This is the day mode.  And that the color QRs are the means for people with mobile phones to quickly share their  identities and connect to each other.  People don't like to enter cryptic things no matter how you present them but they are  very happy to scan QR codes.  That is solving the so called triangle because you have to, when you get your contacts, you  need a human meaningful name and figure out how it is connected to this cryptographic  key.  But if you can scan the key directly with a needset.  So that's my talk.  And if there are questions you can ask me now or later at the Forest Gesellschaft Bus.  Thanks so much, Bern.  If you have any questions you can raise your hand now and I will come to you with a microphone.  And I can also come to the signal angel if you have any questions.  Okay, not yet.  So and also after the talk you can of course approach him directly.  Maybe I'm not sure if it's a really relevant question but you said we cost 100, I mean  we, not me, but some people cost 100 Euro for Facebook.  Is that per, what is the time units?  Like it's an ongoing cost or is it 100 Euro per year or something like that?  But I'm planning, you mean the price for the app?  The price for the app will be in the low Euro rate because you don't want to, if I sell  1 million apps for 2 or 3 Euros the funding is completely done.  I don't need more.  I just need to sell 1 million apps or so.  And compared to how many uses you get for WhatsApp or WeChat or Telegram, 1 million is  little.  I don't even need to have everybody to pay it.  I can make this voluntarily.  I can give out a free app and if you want to donate you buy the Silver as a gold app.  And when you go to Google Store you need to do the funding via their payment system.  They don't like any other methods.  They want their 30% share and because they do a lot of this infrastructure is okay for  me.  Give them 30%.  It's not a big deal.  I don't, when you are an institutional investor you can give me some 10,000 Euro.  That is completely different.  But if you are a private person I don't want to take a lot of money from you.  One more question and we'll be back here.  Yeah.  Hi.  You mentioned CDNs, content delivery.  I was wondering if you have some sort of multicast in Net2o for doing.  So if I send a message to a friend and then I forward that message to another friend but  they have a closer link.  Is it going to be shared from the first person I shared it to?  That is what the peer-to-peer network comes in.  When you share something with your friend, you send them your data.  I have, and they copy your objects and forward that they also have it to their friends.  So the friends now can choose where to download from their friends, from you, they have more  options.  So a peer-to-peer network is a content delivery network by nature.  That is what it's supposed to be.  The content delivery networks actually internally work like peer-to-peer networks.  Use the same technology.  They just don't give the end users the freedom to be part of this peer-to-peer network.  They don't want you to be part of the network.  You are the product.  You are not part of the community.  Thank you so much, Ben, for your talk.  It was very interesting.  There were more questions coming up, I think, directly afterwards in private to find out  more about it.  Thank you very much for presenting that at Open Infrastructure Orbit at Congress.  Thank you.
36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_168_371.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_5352_6515.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_7848_9719.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_14460_17363.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_17364_18527.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_18528_22967.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_25740_25991.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_25992_26195.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_26196_26387.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_26388_26639.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_26640_30971.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_30972_31907.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_31908_32423.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_33372_33551.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_33552_33599.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_33600_33659.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_33660_33827.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_33828_33971.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_33972_34319.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_35244_35315.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_35952_36227.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_36228_36287.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_36288_38843.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_42828_43175.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_43176_44267.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_44268_44351.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_44352_44651.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_44652_45071.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_45072_45155.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_45156_45239.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_45240_46079.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_46080_52703.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_52704_58691.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_58692_58787.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_58788_58835.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_58836_59003.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_59004_60275.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_60276_60431.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_60432_60623.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_60624_60671.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_60672_60875.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_60876_61031.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_61032_61751.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_61752_62027.png 36c3-oio-162-eng-CloudCalypse_2_Social_network_with_net2o_YBTI_wefixthenet_session_hd_75084_75155.png