 Hi everyone, okay now we got your attention. Today I'm both challenged and both excited. Challenge because I know there's a lot of both platforms out there and a lot of cool things out there, but my excitement lies in the fact that today I get to get back and I get to announce something very cool that we got going on at WIRE. My name is Helena, I work at WIRE and my coming down is also presenting to you. Okay, so throughout the years you notice that a lot of new tech converges and there's always like this one thing that keeps on repeating like a pattern. And whether it's internet or smartphones or VR, there's this area that doesn't get addressed and keeps on being ignored, which is privacy. But first I want to introduce you to WIRE. WIRE is a fully entered and encrypted app based in Berlin, as you can see. This is our office. This is only the half of our office. You can see the other half later if you go on a tour with us. Where is the map? It's not only fun, but it's also productive. It has a lot of features that you can use on a daily basis, like screen sharing, video calls, group stereo calls, location sharing, file transfers, but it has a lot of fun features, like uniquely embedded GIFs and sending funny audio messages with filters to your friends. It has a sketchy background. It has a lot of features that you can use on a daily basis, like screen sharing, video calls, group stereo calls, location sharing, file transfers, but it has a lot of fun features like uniquely embedded GIFs and sending funny audio messages with filters to your friends. It has sketches and emojis on images, so everything you see in any other messaging app, but even more. Two more serious matters, which is privacy. WIRE servers are located in the European Union, so there's no way any user data is shared or sold to any third parties. WIRE is fully entered and encrypted. There's no back doors to WIRE, and there's also no middleman attack because the thing has been comparison. And this is the point you might like a lot. WIRE is the app and encryption protocol are open sourced, and you can find all the code on GitHub. It was reviewed by security experts and users on a daily basis, and just if you go on github.com slash wire app, you can find all the data. So earlier I asked you if you ever tried out a book that handled some kind of sensitive data. So we can see that this technology is on a rise and everyone is jumping on this train. And many businesses are joining from retail and sales and marketing and customer service. But as many organizations join, they actually have to take a step back and take a moment to consider the security implications because once you deploy a chatbot on a book platform, all of its security capabilities lie at the mercy of the book platform. So if you use a public platform public channel and you deploy a book there, the provider sees the data, but the book platform might also see your data. So for example, you're using a banking chatbot and you check your salary on a monthly basis. The book platform might take that data and sell it to advertisers and then you might get ads based on your salary. It's pretty creepy stuff. And this is where wire comes in. So wire covers all of these privacy and security needs. Wire is a book platform that does not sell or share any of the data. So you have the banking app and you trust the bank, but you also trust wire to not share your data. And this is why wire supports integration in the future will aim at sectors like banking, internet of things, healthcare, education and many others. So also a few weeks ago, we had this pleniment. We went to Deutsche Bank Hackathon and we built a secure chatbot that could check your balance and voice recognition and also it tracked and basically categorized a lot of expenses that are unknown like cash payments and all kinds of options there. And we had a lot of fun there. We're going to continue working with Deutsche Bank. This is like our first really successful use case, business use case that we noticed. And yeah, now since we're not a bot company, but we did try first hand building this bot. And then some other bots that we have like Chefpaul and FooSpots. But we want to also invite other developers soon to join us and to help us build bots. And I hope you enjoyed this part. Now we'd like to announce my colleague Dan who's going to show you a bit of the technical part. Thank you. Thank you guys. We are excited with this talk with Helen Head. We'd like to go now a bit more into technical details just to show like what we have done so far, what we have by it. We can just quickly implement the Java SDK just to demonstrate how to use it. And we put a simple HelloBots application that you just allow it to get going just to get the grasp on it. So if you go to GitHub, wire up HelloBots, here it is. This is the repository. Once you go there and you clone this, you will find some simple steps that you need to do. And show that also you have the wiki there which you can check with documentation. It's on this side. That shows you a bit more about the rest of the bot API. If you want to go more into details, you get familiar with it. Once you clone this repository, you would go to your favorite ID, I use lj. And there you would find classes like simple copy class if you need to specify a code name or proper picture. Still, one of the greats are just simple main class where you basically initiate the objects that you need. And here I would like to show the message handler class, which is actually the main logical unit here. And this method on message will be called each time somebody posts something into a conversation where your bot is one of the participants. As you can see, it's very simple. It's loading and the main part is here. The method accepts the client object and the message object. Important to say here that the message object is here. It's already decrypted and it has all the content there ready to be consumed. So if the user posted a picture, it will be over the key of that picture, it will be there so you will be able to download it. The text is there, it will be decrypted over here. So our echo bot would just take that content and it would reply into that conversation. So once you execute this call, the echo will be then placed into that conversation so the other users can see it. Similar logic for the pictures. Here in the example, we have a picture, somebody posted it, you can download the picture. This is already decrypted and you can post it back. Once you post it, the SDK will take the lifting input from the encryption and it will send all the devices to all users in that conversation. That's basically it. For both, you would build this code and you would deploy that to your server where you have the public IP and then where you're going to have your bot running and listening to talk. One thing is missing here. You have to go somehow, you have to go to wire back end, register yourself as a bot developer and you have to register your bot. That bot has to get the name and ID and all this stuff. We thought it would be cool to create another bot that would help you set up your bot. We have a bot called DevBot. Having it here already connected to it, you can start talking to it, you have to register yourself. Once you've done that, you can start maybe trying to create your first bot. So let's try to create our bot. This is the time that we are creating our first bot, first time. The bot is asking us what should we call this bot. That should be, you can put some catch in there. I don't know. Medici, let's call it. Tech. It's one catch in there. You can have something. Again, you have to specify the end public endpoint. This will be the endpoint where the wire back end will be called. Every time something happens in the conversation, every time somebody asks this bot, your bot to a conversation, that endpoint will be called and you will get some information that will help you set up everything yourself for interacting. I already have some endpoint there. So let's say, I don't know, mybot.com slash whatever you want. Again, some questions. I love bots. That's the last step. Why you require certificate bidding? Either you already have some certificate for your websites or if you don't, you can also, as a part of the big process, the Herobot would create a self-signed certificate for you. You can use that for now. I have it here somewhere. It wants you to send it to the public key, not the private key. Let's go back. Okay, perfect. Set to the public key and create another first bot. The bot is already registered with the back end. Everything is hopefully set up there and fine. We got that big thing there, which you see, that's authentication token. That's a token which is kind of like additional security. Wire back and we'll be sending that big chunk there in our HTTP header every time you close your endpoint. So you should remember that. I mean, your config part should remember that. And you should always verify that actually, that we are on the same page. It's not that somebody else is calling your endpoint and maybe is trying to run that. So, there it is. Go back to your... Not here, but here. And in your config, you would put it there, save it. And basically, after setting that, you can take a look at your config. It's very simple. You are ready to deploy your code to your server. You would go back to your favorite bot here. And you would say Navel. Navel bot. Okay. And basically that's it. At that moment, your bot is alive. I only had my bot deployed. So, opening the wire up again. And that's it. It's told us, you know, right, there's something in the back. So, yeah, this was the demo and the presentation. This is a really initial version of the API. We will have so many more things coming like the bot website where you can register and not go into the bot, but also other places and a lot of things in the UI that we're preparing for the beginning of next year. But if you're interested in knowing more or even developing your bot like in the early alpha phase, then you can go to developer.wire.com and just leave your email so that your preferred SDK and we'll get in touch with you. Thank you.