 But hopefully, everyone is praying and fascinated. And so what we're talking about today is how do the people in security in the data core? It is, it does. It does not deal with the data. Back in the adversary, it does not deal with the data security in the description. So we're going to talk about data security in Drupal 8. So first off, who am I? I'm an open source developer for public security and coding and most of all, I'm an open source developer. So what I can work with is working with hundreds of local markets, startups, and I know that I know that. One thing is reasonable, and I care about the data. So the question is, do you know where your data is going to go? Do you know it's going to stay in places that's not in there? Do you think they're useful? Anywhere. We've got a lot of data that's no longer just in the database. It is everywhere. And so what we're talking about is, why are we storing the data in those places? Well, the database, you have to keep it in it. So a lot of the times, when you've got the security to your security, they say, I'm going to put this data in it. I'm going to put that into a pretty good to the very best human because no one's going to look at a very best human because it's a description key. And then, I hope you know what I'm talking about. All of you have to do that. But the next thing I can say, play this forever. This question, again, one of us. So if you and me, if you don't like me, ask me to do this for you. Albers, I've got that risk for security and I'll get you to have a good question and then we'll have an indication about it. And then there's a lot of passing. Passing is great, and that's a really fast performance site. But we now keep in data that you have and spreading all over the world, in some places where you may or may not control how they sort of write it so you can see how you can make money passing and where you can see it. What can you do for us in the case that we can't use? So the first step is keep your data. That should be separate. If you are collecting or have sensitive data, can you help and criticize? You are going to have to encrypt it with the process that I just explained. Just so I have no idea what it says. It's basically taking a plan and joining a group vote. If you're physically taking a group in Egypt, you can take any type of stuff in there. So you're welcome to do it. So these are the never-good boundaries. And so starting with a used document, we decided some of us decided that we're going to rewrite this kick-ass in. And we're talking to the RLH, which is right here. So I'm going to get some work on this. And what we decided was that the tick-moss or stuff that you put in is going to be in the RLH. It's going to be a branch of the station for all of us to get work done. So it's going to be a huge start in put-not-go. And there are a lot of us out in the RLH that never got access to a put-not-go program. That's intentional. But if you get what they put-not-go in, you have to, you want to get the ability to present whatever you want to put something out of it. The reason that I just said, and both of us is to create a single-profile input, and you can have your B-primers input in the program. They can have two-to-two different keys, and you can have two people that can extend into the put-not-go format. And the RLH also allows for a five-rowing input, which is a good practicing input. It means that you can start using new keys regularly in some sort of schedule. And that schedule can be quick-to-be by the intercepting of the diagram or by a proper guideline, but if you don't just go on to my presentation case. This is a set of two-piles with a single key that gets released, so it's compromised. It doesn't run on top of the Russian data paper. It doesn't run on B, right away, and that's what that key may help you get. So the way the profiles are done is you can create a new profile, and that's got a new profile to a key, and you can set it for whatever your scripting is, and then, what we're gonna do, you can just call it that new profile. And when data is encrypted in two-piles, you store the profile alongside the data, because it's hard to know if you're using the user profile. User profile on the one side will happen, because if you keep the information, it's not easy to profile that as easy as it is for you. And you better be able to keep the information in place with the new profile, too, you can call it. It will slow down your data to such a big use to the new interface, I think. But, I guess that being quick-to-be itself doesn't actually give you a quick-to-be, so it's only on the side of the real US market. This is the recommended module to use. It's the implementing ADS-166 with HVAC, based on the disease library, if you know of the disease library, it's kind of a quick-to-be for HVAC in person. We're gonna go ahead and put that in the briefcase. These guys are waste-parted analysts that come back. And what HVAC does for those that want to know is that there are translations in the text. In prison, you can actually get it to output a different information, or you can put it to it. And output a different information, you can do a mess with the payload, you can do a similar thing. So there's this model system, extra validation of cases. The data that came in matches the data that's been found. And so, again, these are best practices to use and the ADS-166 provides that. It really puts the bumpers in the bolder way for you to use in person, just makes it taxiconic. The difference was that this talk was more common. I think we go into a high-definition of those two other things that HVAC's people can do. But it actually goes from a, whether they're organic or organic, as you know, it's all in the middle of the site. And during the demo, it was an extra three minutes. We had to deal with people and put it back. There was no reason. And so, the most common implementation of it is the field input model, because fields don't have everything. You can choose that box. The security member field doesn't decide if they're on a form or the credit card input field. It's pretty exciting, but I'm fine with the right data. You can decide now, I want to interpret that data. Yeah, yeah. So, it's pretty simple implementation. It's a complete rewrite of P7. So, you need to use P7 to get back to it. And so, that's the question of access from that. But, probably, being able to completely rewrite these fields improved, you know, a number of areas. One of them being passing. It wasn't really talking about the passing. People's really good at passing. Making it self-performed, and getting access to all the latest classes. In Drupal 7, it was really hard to validate the typical fields kind of on the open page. In Drupal 8, we had a better capability in point. So, in Drupal 7, where you were using the field input model, you basically had a term called field pick. In Drupal 8, you can still keep some of the passing information out. Either our web portal tips and highly-picked, well, this is a lot. One of the things that we've been talking about recently is also the 15 passing policies. And being able to complete it pretty well. So, it was kind of a concept that, even to be a team, you can do it out of each of those. But, in Drupal 8, a lot of classes are in the spectrum. We're now taking this really simple case and starting to expand the part of the list. And with that, we've got green chips, which does all of the green centralization for all of it. If you could get the answer out. And it's not really a fantastic doing. But that's a big part of the encryption. But the most important part in California is the key. And in Drupal 7, the input model is how to come in with the train trip in Drupal 8. And so, we created the key model. Centralized key model, this type of is the ownership of where this input is probably meant to be. The first key model, that's what it has. And then, you know, what's the problem with it? Part of the reason for that was earlier, I think, it's being saved in a certain group of servers. But I'm trying to figure this out again. I always get to all of your tokens. All of your tokens are used in this part of your group. What we do is, we say, okay, because it's going to be a terminal, in the U.S. it can save the U.S. getting a token spoke to this token. And basically, we're just battling some of these so that you can split to see the amount of value that's needed for all of these keys. So if you go to this environment, this is going to be a decent value. Centralizing the one spot, even if you're so used to it, you'll take that over. At least we want to say, you're starting to see less. But, this brings to the fore of why this should be important, because we are collecting all this information. The trip model is a really awesome tool that we know this, but we're not trying to use it to talk about the values and the values. So, it's not just a tool that's talking about this, you know, a lot about the amount of loss made from, we need to talk to our team of you. That should have already happened. We should have been talking about that this time. But, now we also have to talk about security. And let us say in federal regulations, very important rights and regulations, because, believe it or not, our pricing concerns and the other thing that we have to do at the base that we're going to be in the federal range is also part of what we're going to be able to do. So, we've proposed really four policy initiatives to start dealing with these issues. So, giving you tools, you're going to have to do this and how this looks like and what it does. But, it's not going to be the people who will take some of these grills. We're asking you to go through and mark the outcome of these policies and the kind of same policies that we're going to take. And so, we can stand on the foundations that we're going to put in place and what these ideas are going to be. So, we can do these policies by using the solution by integrity and protocol. And, we've got the rights there. Can you talk about how this is going to be done? So, it's like it's a real work. So, you're going to have to say this and see how this is going to be done. And I think that's also important. Just because you have this. So, for the price of your protection, we can do the amount in which it's going to be. Yes, it is important to use it because it's not just because it works for you, it's not just for you. You also have, So, security, you know, it's just one way to do that. This is because it's not going to be some of the different systems. So, this is going to take the action three or two years in a row and find the value of that. So, the other model is actually the story that you said. And so, I thought the story came up with that. It was sort of an open field, so for a minute. And that's exactly the idea that I'm doing. And so, for most of it, it's sort of the machinery of those people and because you can do great grants, you can do a lot of things, but you can do a lot of good grants. So, you can do a lot of good trade, but a lot of good jobs, you can do a lot of good trade. So, the key model of the price model is kind of the core. If you are open to both of us. So, it's worth that amount that we can just as I ran into in a couple of seconds. As much as I want to say that, you know, to us, we need to convey the real value of good data. We should be able to set up the way we're going to keep our funds for a long time. So, for about three years to go, it keeps up the connection to that. But using P, it keeps up the connection to that. Yeah, just to add a little bit, if you have any questions around, we'll put them down for you guys.