WEBVTT 00:00.000 --> 00:09.000 All right, so it's time for our next and final talk. 00:09.000 --> 00:12.000 Robert Hensing is going to talk about leeks of fall. 00:12.000 --> 00:16.000 And he's going to give a bit longer to the action of himself. 00:16.000 --> 00:19.000 Round of applause for the speaker, please. 00:25.000 --> 00:26.000 All right, yeah. 00:26.000 --> 00:29.000 So this is what makes it forward. 00:29.000 --> 00:31.000 There was a little bit of how. 00:31.000 --> 00:33.000 I'm Robert Hensing. 00:33.000 --> 00:36.000 And yeah. 00:36.000 --> 00:39.000 So I've created a third-class CI. 00:39.000 --> 00:42.000 I'm on the Nixon committee in the Nixon. 00:42.000 --> 00:45.000 And I work on these projects. 00:45.000 --> 00:49.000 The most of the services in single statistics point, 00:49.000 --> 00:55.000 like small things that I'm currently being a bit of attention to. 00:55.000 --> 00:58.000 So if you're interested, you can. 00:58.000 --> 01:00.000 Talk to me about those. 01:00.000 --> 01:05.000 Yeah, and this talk is about mixups for. 01:05.000 --> 01:07.000 And that's. 01:07.000 --> 01:10.000 Port the sponsored by the diversity project. 01:10.000 --> 01:14.000 Which is these organizations. 01:14.000 --> 01:17.000 And there will really. 01:17.000 --> 01:19.000 Cool. 01:19.000 --> 01:21.000 A project. 01:22.000 --> 01:23.000 I think. 01:23.000 --> 01:25.000 Yeah, I've highlighted this. 01:25.000 --> 01:28.000 This is from the website. 01:28.000 --> 01:32.000 So what I try to do is provide tooling for. 01:32.000 --> 01:33.000 Hosted culture. 01:33.000 --> 01:35.000 So this is not like. 01:35.000 --> 01:40.000 Home app stuff, but more for hosting providers. 01:40.000 --> 01:42.000 It's all based on the next list. 01:42.000 --> 01:45.000 And it's about. 01:45.000 --> 01:50.000 I think a pretty like sort of civilizational topic. 01:50.000 --> 01:53.000 Especially in like recent days. 01:53.000 --> 01:58.000 Yeah, about making social media. 01:58.000 --> 02:03.000 So open. 02:03.000 --> 02:05.000 It's cool. 02:05.000 --> 02:06.000 It's cool. 02:06.000 --> 02:07.000 Yeah. 02:07.000 --> 02:11.000 So there also. 02:11.000 --> 02:14.000 There's also a software program. 02:14.000 --> 02:15.000 Yeah. 02:15.000 --> 02:16.000 Yeah. 02:16.000 --> 02:17.000 Yeah. 02:17.000 --> 02:18.000 Yeah. 02:18.000 --> 02:20.000 So next up for. 02:20.000 --> 02:22.000 What is. 02:22.000 --> 02:24.000 It's. 02:24.000 --> 02:25.000 It's the deployment tool. 02:25.000 --> 02:28.000 You should know that it is working progress. 02:28.000 --> 02:30.000 This is like very early stages. 02:30.000 --> 02:32.000 And I would not recommend to use it. 02:32.000 --> 02:34.000 It's very unfinished. 02:34.000 --> 02:37.000 It's the successor to the next. 02:37.000 --> 02:41.000 And it combines a few concepts. 02:41.000 --> 02:43.000 I wouldn't say that it's novel. 02:43.000 --> 02:50.000 But it integrates a couple of ideas that make it work really well for. 02:50.000 --> 02:53.000 For deployments. 02:53.000 --> 02:55.000 So why? 02:55.000 --> 02:57.000 You might have heard of next ops. 02:57.000 --> 03:01.000 And next up is the two for deploying next to a systems. 03:01.000 --> 03:02.000 It does provisioning. 03:02.000 --> 03:05.000 It can deploy secrets for you. 03:05.000 --> 03:09.000 And also has a bit of support for doing some things around that. 03:09.000 --> 03:12.000 Like adding DNS entries in some cloud provider or whatever. 03:12.000 --> 03:16.000 Which kind of works. 03:16.000 --> 03:22.000 But it never really took off. 03:22.000 --> 03:23.000 Yeah. 03:23.000 --> 03:28.000 It had a bit of solo around testing and CI. 03:28.000 --> 03:29.000 Yeah. 03:29.000 --> 03:31.000 Because that was basically just a bit under development. 03:31.000 --> 03:32.000 So it was. 03:32.000 --> 03:33.000 It was. 03:33.000 --> 03:34.000 It was. 03:34.000 --> 03:35.000 It was. 03:35.000 --> 03:36.000 It was. 03:36.000 --> 03:37.000 It was. 03:37.000 --> 03:39.000 It was. 03:39.000 --> 03:40.000 It was. 03:41.000 --> 03:43.000 It's it's still bad. 03:44.000 --> 03:46.000 Yeah. 03:46.000 --> 03:48.000 I think also part of the reason was the. 03:48.000 --> 03:52.000 Because it was written in Python, which is probably fine. 03:52.000 --> 03:54.000 It's an okay language. 03:54.000 --> 03:57.000 I'm I'm personally not much over fun. 03:57.000 --> 04:01.000 But I noticed that a lot of other contributors had sort of the same thoughts. 04:01.000 --> 04:04.000 And probably part of this was caused by the way it was set up. 04:04.000 --> 04:05.000 It had some tooling. 04:05.000 --> 04:07.000 Set up in the repo. 04:08.000 --> 04:10.000 To add types, but the way was set up. 04:10.000 --> 04:13.000 It was causing some issues that people thought that PR was bad or something. 04:13.000 --> 04:16.000 Even if it was actually fine. 04:16.000 --> 04:19.000 And yeah, it was a lot of friction. 04:19.000 --> 04:22.000 And the the the main issue. 04:22.000 --> 04:25.000 Why all what I thought that. 04:25.000 --> 04:27.000 This had to be a rewrite. 04:27.000 --> 04:29.000 Is the way it integrated with nicks. 04:29.000 --> 04:31.000 It called the evaluator. 04:31.000 --> 04:32.000 Twice. 04:32.000 --> 04:34.000 Which is both. 04:35.000 --> 04:36.000 And so many. 04:36.000 --> 04:37.000 Right. 04:37.000 --> 04:38.000 Because you in my think. 04:38.000 --> 04:40.000 I will just call it ones and it should be fine right. 04:40.000 --> 04:42.000 But if you have an appointment that has. 04:42.000 --> 04:44.000 Some interdependencies. 04:44.000 --> 04:46.000 You might not have all the information. 04:46.000 --> 04:47.000 At the right time. 04:47.000 --> 04:49.000 So you potentially need. 04:49.000 --> 04:51.000 Well, I'm undounded. 04:51.000 --> 04:52.000 I guess. 04:52.000 --> 04:54.000 But finite. 04:54.000 --> 04:57.000 Number of implications to make that work. 04:57.000 --> 04:59.000 We. 04:59.000 --> 05:00.000 Integrating through the nicks. 05:00.000 --> 05:02.000 Eli is just not the way to go. 05:02.000 --> 05:06.000 And that means large architectural changes to implement that. 05:06.000 --> 05:08.000 So. 05:08.000 --> 05:10.000 Um. 05:10.000 --> 05:11.000 Yeah. 05:11.000 --> 05:12.000 Before that. 05:12.000 --> 05:14.000 There was an effort to. 05:14.000 --> 05:17.000 So some of the problems in in nicks. 05:17.000 --> 05:18.000 Um. 05:18.000 --> 05:19.000 With plugins. 05:19.000 --> 05:21.000 But that turned whole thing into. 05:21.000 --> 05:23.000 A multi repo. 05:23.000 --> 05:24.000 Set up. 05:24.000 --> 05:27.000 And that actually makes things even harder to change. 05:27.000 --> 05:29.000 So. 05:29.000 --> 05:32.000 I have to apologize for this picture. 05:32.000 --> 05:33.000 Um. 05:33.000 --> 05:34.000 That this is the way it works. 05:34.000 --> 05:35.000 So I do you have. 05:35.000 --> 05:37.000 Uh, a superclass and some subclasses. 05:37.000 --> 05:39.000 But the superclassism on people. 05:39.000 --> 05:41.000 The subclasses are in another. 05:41.000 --> 05:42.000 Um. 05:42.000 --> 05:43.000 Yeah. 05:43.000 --> 05:44.000 These two nicks. 05:44.000 --> 05:45.000 It. 05:45.000 --> 05:46.000 It. 05:46.000 --> 05:47.000 It. 05:47.000 --> 05:48.000 It. 05:48.000 --> 05:49.000 Uh. 05:49.000 --> 05:50.000 I mean. 05:50.000 --> 05:51.000 I. 05:51.000 --> 05:52.000 I only took maintenance. 05:52.000 --> 05:54.000 Uh, I took over maintenance in. 05:54.000 --> 05:55.000 Uh. 05:55.000 --> 05:57.000 For a year after this. 05:57.000 --> 05:58.000 Uh. 05:58.000 --> 05:59.000 But the people before this. 05:59.000 --> 06:01.000 They put a lot of effort. 06:01.000 --> 06:02.000 Um. 06:02.000 --> 06:03.000 So to make it better. 06:03.000 --> 06:04.000 Um. 06:04.000 --> 06:05.000 Um. 06:05.000 --> 06:06.000 It was a bit too late. 06:06.000 --> 06:07.000 Uh. 06:07.000 --> 06:08.000 Yeah. 06:08.000 --> 06:09.000 That. 06:09.000 --> 06:10.000 That. 06:10.000 --> 06:11.000 That. 06:11.000 --> 06:12.000 That. 06:12.000 --> 06:13.000 That. 06:13.000 --> 06:14.000 That. 06:14.000 --> 06:15.000 That. 06:15.000 --> 06:16.000 Um. 06:16.000 --> 06:17.000 So why I. 06:17.000 --> 06:18.000 I. 06:18.000 --> 06:19.000 In. 06:19.000 --> 06:20.000 Twenty twenty one. 06:20.000 --> 06:22.000 I was still very optimistic about it. 06:22.000 --> 06:23.000 Um. 06:23.000 --> 06:24.000 Yeah. 06:25.000 --> 06:27.000 And it was still the only two. 06:27.000 --> 06:28.000 Um. 06:28.000 --> 06:30.000 That like nearly integrates nicks and. 06:30.000 --> 06:31.000 And provisioning. 06:31.000 --> 06:32.000 Uh. 06:32.000 --> 06:34.000 Which is something that I badly needed. 06:34.000 --> 06:35.000 So at the. 06:35.000 --> 06:36.000 Uh. 06:36.000 --> 06:37.000 I'll. 06:37.000 --> 06:38.000 I'll. 06:38.000 --> 06:40.000 I'll. 06:40.000 --> 06:41.000 I'll. 06:41.000 --> 06:42.000 I'll. 06:42.000 --> 06:43.000 I'll. 06:43.000 --> 06:44.000 I'll. 06:44.000 --> 06:45.000 I'll. 06:45.000 --> 06:47.000 I'll. 06:47.000 --> 06:49.000 I'll. 06:49.000 --> 06:50.000 I'll. 06:50.000 --> 06:51.000 I'll. 06:51.000 --> 06:52.000 I'll. 06:52.000 --> 06:53.000 I'll. 06:53.000 --> 06:54.000 Yeah, I'll. 06:54.000 --> 06:55.000 I'll. 06:55.000 --> 06:56.000 I'll, I'll. 06:56.000 --> 06:57.000 I'll. 06:57.000 --> 06:58.000 I'll. 06:58.000 --> 06:59.000 So, uh. 06:59.000 --> 07:00.000 Can I can. 07:00.000 --> 07:01.000 Uh. 07:01.000 --> 07:02.000 What. 07:02.000 --> 07:03.000 What? 07:03.000 --> 07:04.000 Well, what? 07:04.000 --> 07:05.000 Mm. 07:05.000 --> 07:06.000 Um. 07:06.000 --> 07:07.000 Um. 07:07.000 --> 07:08.000 It's. 07:08.000 --> 07:10.000 Um. 07:10.000 --> 07:11.000 Uh. 07:11.000 --> 07:12.000 Uh. 07:12.000 --> 07:13.000 Uh. 07:13.000 --> 07:14.000 Uh. 07:14.000 --> 07:15.000 Uh. 07:15.000 --> 07:16.000 Uh. 07:16.000 --> 07:17.000 Uh. 07:19.000 --> 07:20.000 Uh. 07:20.000 --> 07:21.000 Okay. 07:21.000 --> 07:22.000 Uh. 07:22.000 --> 07:22.500 Um. 07:22.500 --> 07:28.500 more of an engineered thing. And for this week, we can take a look at the next architecture, 07:28.500 --> 07:34.980 which is actually very successful. So the way the next works, if you use the next expression 07:34.980 --> 07:44.420 language, you can use one to the end, by pointing. Yeah, so use the expression language to create 07:44.740 --> 07:53.620 function calls, that creates derivations, derivations refer to other derivations to serpets. 07:54.980 --> 08:02.100 And then next uses a sandbox and this, the next door to make over happen. 08:03.540 --> 08:11.140 And so for next lecture, we extend that architecture. So now we also use the expression language 08:11.140 --> 08:19.940 to configure resources. I'll get into what those are later. And yeah, similar to how it works 08:19.940 --> 08:30.740 in next these resources are processes that then you can like similar to how the derivation 08:30.740 --> 08:39.380 door can anything that you like as well. So it's decoupled in that way. And that's a big difference 08:39.380 --> 08:47.220 between x-ups for and the opening x-ups is this decoupling. That this will enable other people 08:47.220 --> 08:55.300 to write resources without the inside to open that to many architectural details. 08:55.460 --> 09:09.940 Right, so what is the resource? A resource is a declaration of a real world object that's supposed 09:09.940 --> 09:20.980 to exist and has basically to create operations. So these operations are implemented in the resource 09:21.940 --> 09:26.820 when you're using a resource, you don't really have to think about it. It is still declarative 09:26.820 --> 09:32.100 as you know with the next language that's sort of what you get, right? It's declarative. 09:34.100 --> 09:41.220 And so next up is responsible for connecting all these operations and sort of the data flow between them. 09:41.220 --> 09:52.900 So deployment is a collection of resources. And yeah, I'm decides to call operations. 09:53.620 --> 09:57.380 It'll also have sort of a next one like capability, which is great for scripting. 09:59.460 --> 10:04.980 And you can do build use that for things like backup for a geotation or really any sort of 10:04.980 --> 10:10.420 operation that you have to do on a deployment. You can use the values from that deployment to 10:10.420 --> 10:21.300 implement your script. Resource provider is a program that's built with nix. As you remember in 10:21.300 --> 10:29.540 the architecture, the middle layer, nix of course it. It talks to a patient protocol, which is adjacent 10:29.540 --> 10:38.660 over just kind of input and output streams. Yeah, so when you're using it, it looks something 10:38.660 --> 10:46.260 like this. So you may have a flick. And yeah, there's attribute here. It's the default deployment. 10:46.900 --> 10:50.900 That's just a name. If you don't specify name on a command file, you get the 10:50.900 --> 10:59.460 default deployment. Yeah, and you can see it's a function that 11:01.220 --> 11:09.220 take us an argument to resources and uses that to declare the resources. So this is 11:10.260 --> 11:14.980 what you might call a fixed point and nix ups is responsible for connecting those together. 11:15.700 --> 11:19.700 Next is the language, which is the reason why this can even work. 11:24.900 --> 11:30.740 Yeah, and we sort of zoom in onto that resources function. I'd practice a little looks 11:30.740 --> 11:37.380 up like this. We use an emergency system as well. So you see it have we're importing 11:37.380 --> 11:41.620 something from another flick, which helps with doing an XOS deployment. 11:42.580 --> 11:46.980 And it's specified the details for how that deployment should look. 11:49.380 --> 11:54.100 And now you can add more resources. So there's an example right where you have this dependency, 11:54.100 --> 11:58.260 because you're going to meet the RDSH keypad for doing an XOS deployment. 11:58.260 --> 12:02.420 And there's something you can declare in a single deployment expression. 12:02.420 --> 12:18.260 Yeah, so next up is this, yeah, what we call a stateful deployment tool, which means that 12:18.260 --> 12:23.220 it can track the existence of things. So that when you, for example, when you remove something 12:23.220 --> 12:28.100 from your configuration, they can take care of, I don't know if you're thinking those things 12:28.100 --> 12:34.740 in the real world as well. Also, as some advantage is where you can create a 12:34.740 --> 12:41.060 difference between the old state and the new state, more easily. It is optional. If you're 12:41.060 --> 12:46.260 using me for a state-owned, we rely on state. You can get away without it. And that's also the way 12:46.260 --> 12:53.060 that you would step in the first place. Here, in the example, we're using an S3 object 12:53.140 --> 12:58.260 to store a state, so that makes sure that everyone works with the deployment. 12:59.540 --> 13:02.740 It's sort of using the same view of what's in there. 13:11.300 --> 13:16.340 Yeah, and so because we're using a virtual system, you can also do some of your own domain 13:16.420 --> 13:25.220 specifics of in those expressions. And I sort of split up according to your needs. 13:28.340 --> 13:32.900 Oh, let's skip this one. Let's I think here takes a long to explain. 13:33.780 --> 13:40.020 Oh, I'll be happy to explain it later outside. 13:41.940 --> 13:47.780 All right, so yeah, I think next we'll skip you the old VIX development experience. 13:51.300 --> 13:57.380 Yeah, it's pretty much the only two really integrated. For example, there's also a 13:57.380 --> 14:04.580 tyrannics. Next up is a really inspired on terraform. And the difference between tyrannics and 14:04.580 --> 14:09.860 next ops is the tyrannics. You're really only generating a config file. And that doesn't 14:09.860 --> 14:15.140 be allow data form the deployments to flow into the next language and back into the 14:16.020 --> 14:25.060 deployment. So you really still stuck with the hash core of conflict language, which is like 14:25.220 --> 14:30.180 embed inside of your next strings, which I think is not a great experience. 14:32.340 --> 14:36.580 Yeah, definitely not for like the sort of, but I hope this is going to become like the 14:36.580 --> 14:40.340 flagship tool for doing big ones with with next. 14:48.660 --> 14:51.220 I think all I'll just get these so that we can get to the questions. 14:52.180 --> 14:59.380 Question section. Yeah, I guess I guess this is also was implemented is sort of the basics. 15:01.220 --> 15:07.620 So the general architecture and some preparations for if you're making this work is implemented 15:07.620 --> 15:13.780 in Rust, but it's talking to Nick's which is the class. So we have this CAPR layer in between. 15:14.500 --> 15:24.260 Yeah, so it's still allowed is to be done. Currently we have a create operation. 15:26.100 --> 15:31.220 What is sort of the read update and the lead stuff and even making it safe for is here to be done. 15:31.860 --> 15:44.100 Yeah, and also the plan is to have an adapter to the resource provided in 15:44.100 --> 15:47.620 presentations that are written for whatever we can be used in next social. 15:50.500 --> 15:51.540 So questions. 16:02.100 --> 16:10.820 Yes, it does work. Yes, that is the question is the question is doesn't work and yes, it does work. 16:11.540 --> 16:16.260 But the only part of the really works is it's the create operation. We have a next 16:16.260 --> 16:22.820 source next. So that's actually also an important difference is that in the original next 16:23.780 --> 16:30.180 it was really only for next. Whereas next for it is a platform that you can use to do 16:30.180 --> 16:35.940 basically anything. So we have a next was integration now, but you may as well deploy it to 16:35.940 --> 16:42.020 an external or next PSD, which is a project that's like a really new. So that's one point. 16:42.740 --> 16:44.020 Those will also be possible. 16:46.020 --> 16:50.340 And all the ready scary details that you just go with the button that make it look like it can 16:50.340 --> 16:58.180 end up like previous. So the question is, is there like any red flags? I guess the end 16:58.180 --> 17:04.420 of the previous. That yeah, that would end up like the previous one. I think it's a bit too early 17:04.420 --> 17:10.500 because a lot of it was sort of the ecosystem that did or did not do around it. 17:13.220 --> 17:17.140 I've paid a lot of attention to making sure that it's a work document and will test it. 17:18.100 --> 17:25.220 So that should help a lot. But yeah, I would have to prove myself in practice, but I'm hopeful 17:25.220 --> 17:26.420 with good reason, I think. 17:26.420 --> 17:30.500 Yeah. 17:43.780 --> 17:45.780 Yes. 17:50.580 --> 17:55.460 Yeah, so the question is, will next up to implement the same sort of state 17:55.460 --> 18:02.020 life cycle, that terraformed advance? I haven't quite decided. 18:25.460 --> 18:35.460 Yeah. 18:35.460 --> 18:39.860 Okay. Yeah. So basically, I should get some advice, not to say to it like terraformed. 18:39.860 --> 18:41.860 And I would love to talk later. 18:41.860 --> 18:42.260 Yeah. 18:42.260 --> 18:44.100 Not like you can have the conversation about that. 18:44.100 --> 18:46.980 And maybe we can back get back to that topic. But I think there's more questions 18:46.980 --> 18:50.900 that we are not so tight on time because this is the last talk, and I also, 18:50.900 --> 18:55.060 there is some time on the schedule. So I think there was a question in the back. 18:55.060 --> 18:57.060 Really? Yeah. 19:03.060 --> 19:09.060 How often? And the reason I used it was the one that was very good back to the house at the end. 19:09.060 --> 19:11.060 Yeah, you know. 19:11.060 --> 19:13.060 I think that's what we're looking for. 19:13.060 --> 19:15.060 How does it work? 19:15.060 --> 19:19.060 We seem to be a lot more than just like revolting. 19:19.060 --> 19:33.060 Yeah. So the question is, for a company, a user, can I start using it now? 19:33.060 --> 19:37.060 And I would say almost. 19:37.060 --> 19:45.060 We're kind of using it in a way similar to a company, I think, currently in the project. 19:45.060 --> 19:51.060 But we still have like a few rough edges that should be pretty easy to read also. 19:51.060 --> 19:57.060 I think in a month or two, you could give it a shot. 19:57.060 --> 20:01.060 Yeah. 20:01.060 --> 20:03.060 Yeah. 20:03.060 --> 20:05.060 Yeah. 20:05.060 --> 20:13.060 You mentioned the challenge of having information out below from some, I guess, 20:13.060 --> 20:19.060 these resources that the association has to be mixed with configuration. 20:19.060 --> 20:29.060 Would you be able to maybe comment on how I your approach to this comparison to 20:29.060 --> 20:35.060 how you make choice anywhere with your current or module. 20:35.060 --> 20:38.060 Like you need to start getting this new parameter, 20:38.060 --> 20:42.060 special parts that we allow to have like, 20:42.060 --> 20:45.060 that type of information, like flow into the, 20:45.060 --> 20:48.060 and it's just configuration. 20:48.060 --> 20:49.060 Yeah. 20:49.060 --> 20:57.060 So the question is how this, the data flow between resources differ from how it's done with an existing 20:57.060 --> 21:01.060 platform integration, which uses special arts. 21:01.060 --> 21:05.060 Yes, I have to summarize a bit. 21:05.060 --> 21:07.060 Yeah. 21:07.060 --> 21:11.060 So how it differs with nature is anywhere. 21:11.060 --> 21:13.060 And yeah. 21:13.060 --> 21:17.060 So the difference is that because it's all, 21:17.060 --> 21:19.060 or just in the nick language, 21:19.060 --> 21:23.060 you don't have to go through like a special attribute set that gets 21:23.060 --> 21:25.060 utilized or something, right? 21:25.060 --> 21:27.060 I think that's, that's how that works. 21:27.060 --> 21:33.060 And I mean, with them, like, I just believe it's a character or something, 21:33.060 --> 21:37.060 then you sort of get like a similar experience of, I guess, yeah. 21:37.060 --> 21:39.060 Yeah, yeah, it's, it is similar, but it's, 21:39.060 --> 21:42.060 it's just a bit more streamlined because you don't have to do it. 21:42.060 --> 21:47.060 I have to deal with two languages at a time and see a visualization between them. 21:47.060 --> 21:51.060 And I just like going through such a more traditional, 21:51.060 --> 21:55.060 traditional, it's not a platform flow. 21:55.060 --> 21:59.060 You would get like the entire platform ecosystem. 21:59.060 --> 22:03.060 Like, if you're using nicks off, like, 22:03.060 --> 22:07.060 wouldn't that kind of work, if you, like, 22:07.060 --> 22:11.060 when you get the strength of this reference? 22:11.060 --> 22:13.060 Um, 22:13.060 --> 22:18.060 So if you want to use the existing platform ecosystem, 22:18.060 --> 22:23.060 that that would still be possible by going through a mix-ups resource 22:23.060 --> 22:26.060 that that calls in to a platform, that that would basically naturally 22:26.060 --> 22:28.060 achieve the same thing. 22:28.060 --> 22:29.060 Yeah. 22:29.060 --> 22:30.060 That's, that's possible. 22:30.060 --> 22:31.060 Yeah. 22:31.060 --> 22:32.060 Thank you. 22:32.060 --> 22:33.060 Thank you. 22:33.060 --> 22:34.060 Oh, yeah. 22:34.060 --> 22:35.060 My version is, um, 22:35.060 --> 22:38.060 Can you move your hands to create, um, 22:38.060 --> 22:40.060 like, uh, provide it to terms on language, uh, 22:40.060 --> 22:42.060 uh, and you can control it, uh, 22:42.060 --> 22:44.060 and I can't control it. 22:44.060 --> 22:46.060 And I can control it. 22:46.060 --> 22:48.060 And I can control it. 22:48.060 --> 22:50.060 And I can control it. 22:50.060 --> 22:52.060 And I can control it. 22:52.060 --> 22:54.060 And I can control it. 22:54.060 --> 22:56.060 So it, I didn't actually look belong. 22:56.060 --> 22:58.060 I can control it. 22:58.060 --> 22:59.060 I mean, right? 22:59.060 --> 23:00.060 What? 23:00.060 --> 23:01.060 Right. 23:01.060 --> 23:05.060 Um, yeah, so, you're probably able to use the platform 23:05.060 --> 23:07.060 that to for a lot of things. 23:07.060 --> 23:08.060 Um, 23:08.060 --> 23:10.060 but if, if it doesn't exist yet, 23:10.060 --> 23:12.060 or maybe there's something, um, 23:12.060 --> 23:16.060 something special that might work better with a direct integration. 23:16.060 --> 23:18.060 Um, 23:18.060 --> 23:20.060 do we do that issue, uh, 23:20.060 --> 23:22.060 you write a provider, uh, 23:22.060 --> 23:23.060 which is, uh, 23:23.060 --> 23:26.060 it's a program that takes, uh, 23:26.060 --> 23:28.060 Jason objects in standard input. 23:28.060 --> 23:29.060 Um, 23:29.060 --> 23:30.060 it'll, it'll write, 23:30.060 --> 23:31.060 it'll have to write, uh, 23:31.060 --> 23:34.060 Jason objects on standard output, 23:34.060 --> 23:36.060 according to, um, 23:36.060 --> 23:38.060 it's a protocol that's documented in the, 23:38.060 --> 23:40.060 in the next one's manual. 23:40.060 --> 23:41.060 Um, and in addition to that, 23:41.060 --> 23:44.060 you'll, you'll have to provide some expressions to, 23:44.060 --> 23:46.060 um, 23:46.060 --> 23:48.060 sort of, 23:48.060 --> 23:50.060 provide the schema for it, I guess. 23:50.060 --> 23:52.060 Uh, that's going to be how it works. 23:52.060 --> 23:55.060 Um, we'll probably improve this a bit. 23:55.060 --> 23:56.060 Um, 23:56.060 --> 23:58.060 but that doesn't generate. 23:58.060 --> 23:59.060 And the question, 23:59.060 --> 24:01.060 what I think, how do you implement the cloud operations, 24:01.060 --> 24:02.060 just to detect it? 24:02.060 --> 24:03.060 Yeah. 24:03.060 --> 24:05.060 So the, the cloud operations, 24:05.060 --> 24:06.060 um, 24:06.060 --> 24:07.060 that's, 24:07.060 --> 24:08.060 the question you notice is, 24:08.060 --> 24:09.060 for the audience. 24:09.060 --> 24:11.060 Oh, but yeah, the, the question was, 24:11.060 --> 24:13.060 how, I was implemented the cloud operations. 24:13.060 --> 24:14.060 Um, 24:14.060 --> 24:15.060 yeah. 24:15.060 --> 24:16.060 Yeah. 24:16.060 --> 24:17.060 Yeah. 24:17.060 --> 24:18.060 Yeah. 24:18.060 --> 24:19.060 Yeah. 24:19.060 --> 24:20.060 Yeah. 24:20.060 --> 24:21.060 Yeah. 24:21.060 --> 24:23.060 We're actually funding this from, 24:23.060 --> 24:24.060 the NGO, 24:24.060 --> 24:26.060 the diversity project. 24:26.060 --> 24:28.060 And that until, 24:28.060 --> 24:32.060 at least one implementation of what mixups will do, 24:32.060 --> 24:34.060 in a very extended way. 24:34.060 --> 24:36.060 You can just click stuff and work. 24:36.060 --> 24:38.060 So no more people can also use mixups. 24:38.060 --> 24:40.060 Which is like the holy grail. 24:40.060 --> 24:42.060 But yes, we're going to implement this. 24:42.060 --> 24:43.060 And if you want to work on this, 24:43.060 --> 24:45.060 we have a sub-branding program. 24:45.060 --> 24:49.060 They're still more than far, far more than a thousand euros payable. 24:49.060 --> 24:51.060 So look at our website. 24:51.060 --> 24:54.060 And then apply for a grant with an L net. 24:54.060 --> 24:56.060 And maybe in the next few months, 24:56.060 --> 24:59.060 you will get some money to actually help us, 24:59.060 --> 25:04.060 reach the holy grail. 25:04.060 --> 25:07.060 How easy. 25:07.060 --> 25:13.060 So I guess the question is, 25:13.060 --> 25:15.060 please go to fetaversity.edu. 25:15.060 --> 25:20.060 We have a sub-brands program with many of them available, 25:20.060 --> 25:26.060 where you can help out with doing really cool mixups. 25:27.060 --> 25:29.060 To bring it to... 25:29.060 --> 25:32.060 Oh, I don't want no more people. 25:32.060 --> 25:33.060 Here is the next one. 25:33.060 --> 25:35.060 I will be outside. 25:39.060 --> 25:42.060 Are there any more questions? 25:42.060 --> 25:44.060 Can we? 25:44.060 --> 25:45.060 Oh, yeah. 25:45.060 --> 25:47.060 Oh, are you money or not? 25:47.060 --> 25:49.060 Yes, I'm having fun. 25:49.060 --> 25:50.060 Welcome. 25:56.060 --> 25:58.060 Thank you.