WEBVTT 0 00:00:00.209 --> 00:00:00.529 Alright, 1 00:00:00.689 --> 00:00:01.269 there we go. 2 00:00:01.529 --> 00:00:01.830 Uh, 3 00:00:01.850 --> 00:00:03.769 I think we are ready to go ahead and, 4 00:00:03.779 --> 00:00:03.789 and, 5 00:00:03.799 --> 00:00:05.250 and get these questions going. 6 00:00:05.289 --> 00:00:06.119 If you don't know why you're here, 7 00:00:06.170 --> 00:00:08.970 you're here to listen to me answer questions about res and I. 8 00:00:09.090 --> 00:00:11.130 You can drop questions in the questions thread. 9 00:00:11.210 --> 00:00:13.359 I've linked that in the Office hours channel, 10 00:00:13.409 --> 00:00:16.989 but I'm also going to go ahead and link it in the side chat for this stage. 11 00:00:17.280 --> 00:00:17.569 Additionally, 12 00:00:17.639 --> 00:00:18.889 I've gotta close the baby gate. 13 00:00:19.209 --> 00:00:19.399 Alright, 14 00:00:19.479 --> 00:00:20.250 baby gate closed, 15 00:00:20.329 --> 00:00:22.829 let's go back to the list of questions. 16 00:00:23.049 --> 00:00:23.450 Yeah, 17 00:00:23.729 --> 00:00:24.290 whoa. 18 00:00:24.450 --> 00:00:25.190 um 19 00:00:25.520 --> 00:00:27.450 Red is asking about custom workspaces. 20 00:00:27.604 --> 00:00:28.004 Dash thing, 21 00:00:28.094 --> 00:00:28.975 how you make if you know, 22 00:00:29.135 --> 00:00:29.534 um, 23 00:00:29.684 --> 00:00:32.944 workspaces are currently restricted to uh just user space, 24 00:00:32.974 --> 00:00:35.845 so you'll have a very big difficulty using them. 25 00:00:36.134 --> 00:00:36.834 I don't know, 26 00:00:37.055 --> 00:00:37.715 um, 27 00:00:37.935 --> 00:00:41.354 what the sort of long-term intentions for the workspace component is. 28 00:00:41.514 --> 00:00:41.994 Um, 29 00:00:42.014 --> 00:00:43.595 I can see it going like 30 00:00:43.854 --> 00:00:44.694 two ways where we, 31 00:00:44.775 --> 00:00:46.724 we allow workspaces in worlds, 32 00:00:46.735 --> 00:00:46.994 um, 33 00:00:47.055 --> 00:00:48.965 or we don't allow workspaces in worlds. 34 00:00:49.095 --> 00:00:49.534 Uh, 35 00:00:49.575 --> 00:00:50.235 I 36 00:00:50.494 --> 00:00:52.174 can see it going both ways and I don't really know 37 00:00:52.174 --> 00:00:54.974 what like Crooks's original plan with the workspace component is. 38 00:00:55.319 --> 00:00:55.479 Uh, 39 00:00:55.520 --> 00:00:57.840 I routinely have difficulty with the workspace component. 40 00:00:57.950 --> 00:00:58.939 It is one of my, 41 00:00:59.000 --> 00:00:59.349 uh, 42 00:00:59.450 --> 00:01:00.680 most edited components. 43 00:01:00.759 --> 00:01:01.000 I just, 44 00:01:01.040 --> 00:01:01.430 I like, 45 00:01:01.639 --> 00:01:02.520 it's not that I hate it, 46 00:01:02.599 --> 00:01:03.549 it's just that like, 47 00:01:03.750 --> 00:01:03.959 I don't know, 48 00:01:04.010 --> 00:01:05.919 I kinda wanna rewrite it from scratch, 49 00:01:06.029 --> 00:01:07.360 but I don't really also want to do. 50 00:01:07.519 --> 00:01:07.589 Uh, 51 00:01:07.599 --> 00:01:08.779 you can probably use a mod, 52 00:01:08.919 --> 00:01:09.220 um, 53 00:01:09.319 --> 00:01:13.400 to sort of patch out the user space onlyss of workspace component. 54 00:01:13.680 --> 00:01:14.059 Um, 55 00:01:14.319 --> 00:01:16.739 do keep in mind though that anything that you shove in, 56 00:01:16.839 --> 00:01:17.349 um, 57 00:01:17.360 --> 00:01:18.660 like a custom space. 58 00:01:18.879 --> 00:01:19.360 It's not, 59 00:01:19.550 --> 00:01:20.510 it's not safe. 60 00:01:20.629 --> 00:01:22.599 It's not safe that you have to be careful. 61 00:01:22.760 --> 00:01:23.629 Moving forwards to Josh, 62 00:01:23.720 --> 00:01:24.910 who's saying what the dog doing? 63 00:01:25.160 --> 00:01:27.400 The dog's sat next to me on the couch, 64 00:01:27.480 --> 00:01:28.940 as she sat on the armchair 65 00:01:29.099 --> 00:01:29.639 and to play, 66 00:01:29.760 --> 00:01:31.220 like trying to get my attention basically. 67 00:01:31.720 --> 00:01:32.519 Welcome to my lap. 68 00:01:32.680 --> 00:01:33.339 Hi dog, 69 00:01:33.559 --> 00:01:34.069 you're on my lap, 70 00:01:34.139 --> 00:01:34.269 yeah, 71 00:01:34.400 --> 00:01:34.480 yeah, 72 00:01:34.680 --> 00:01:34.760 yeah, 73 00:01:34.879 --> 00:01:34.989 yeah. 74 00:01:35.160 --> 00:01:35.440 Alright, 75 00:01:35.559 --> 00:01:36.260 move forwards, 76 00:01:36.559 --> 00:01:36.940 uh, 77 00:01:37.120 --> 00:01:38.500 reed says not it today. 78 00:01:38.720 --> 00:01:39.519 I'll come back to you on that. 79 00:01:39.699 --> 00:01:41.389 I let my let my brain brew. 80 00:01:41.599 --> 00:01:42.419 Let my brain. 81 00:01:43.080 --> 00:01:44.040 Moving forwards, 82 00:01:44.160 --> 00:01:44.669 uh, 83 00:01:44.800 --> 00:01:45.819 Venport says, 84 00:01:46.080 --> 00:01:46.360 uh, 85 00:01:46.400 --> 00:01:47.489 what the business doing? 86 00:01:47.779 --> 00:01:49.260 Not much traction there. 87 00:01:49.989 --> 00:01:54.410 I'm trying to um get them headlesses set up um and you'll be like wow that's easy, 88 00:01:54.750 --> 00:01:55.169 but 89 00:01:55.430 --> 00:01:56.250 one of the thing 90 00:01:56.430 --> 00:01:57.389 is 91 00:01:57.550 --> 00:01:57.930 that 92 00:01:58.110 --> 00:02:01.489 we can't really use Steam um and so I'm like well what's the easiest way to do that? 93 00:02:01.709 --> 00:02:03.889 I'm probably gonna end up doing 94 00:02:04.290 --> 00:02:07.410 um a like docker container image 95 00:02:07.550 --> 00:02:09.169 that's privately published 96 00:02:09.279 --> 00:02:10.529 uh and then 97 00:02:10.669 --> 00:02:12.440 logging in to 98 00:02:12.589 --> 00:02:15.020 uh the container registry on the, 99 00:02:15.029 --> 00:02:16.270 the headless machine cloud. 100 00:02:16.309 --> 00:02:18.089 That to me sounds like the best way, 101 00:02:18.190 --> 00:02:18.850 uh, 102 00:02:18.860 --> 00:02:19.070 originally. 103 00:02:19.229 --> 00:02:20.639 I was gonna like do a full 104 00:02:21.059 --> 00:02:24.639 uh like a full pelican pterodactyl setup for them 105 00:02:24.820 --> 00:02:25.440 um 106 00:02:25.580 --> 00:02:25.899 but 107 00:02:26.020 --> 00:02:27.809 like that will add like another to it, 108 00:02:27.940 --> 00:02:29.119 so like I'm just gonna like 109 00:02:29.289 --> 00:02:30.929 shove one up via Docker and 110 00:02:31.139 --> 00:02:32.100 and another like cloud. 111 00:02:32.220 --> 00:02:33.800 The problem that I really want 112 00:02:34.020 --> 00:02:35.000 to avoid 113 00:02:35.220 --> 00:02:36.580 is um 114 00:02:36.740 --> 00:02:37.179 actually 115 00:02:37.369 --> 00:02:39.619 was researching this entire problem and came up with a 116 00:02:39.619 --> 00:02:41.130 bunch of sort of idea and theories on it, 117 00:02:41.139 --> 00:02:42.429 but that means I need to explain it. 118 00:02:42.699 --> 00:02:43.009 Uh, 119 00:02:43.020 --> 00:02:43.449 so 120 00:02:43.660 --> 00:02:47.559 when it comes to VMs or like just server boxes in general, 121 00:02:47.660 --> 00:02:48.320 um, 122 00:02:48.339 --> 00:02:48.539 you have. 123 00:02:48.649 --> 00:02:48.970 You have 124 00:02:49.250 --> 00:02:51.259 two types essentially in a 125 00:02:51.570 --> 00:02:52.889 cloud app setup. 126 00:02:53.169 --> 00:02:54.770 You have pet or cattle, 127 00:02:54.889 --> 00:02:55.050 uh, 128 00:02:55.119 --> 00:02:55.929 and to explain that, 129 00:02:56.250 --> 00:02:58.690 pet is something that you keep around for a long time, 130 00:02:58.770 --> 00:03:00.169 you take care of, 131 00:03:00.289 --> 00:03:00.929 you pet it, 132 00:03:01.009 --> 00:03:01.880 etc. 133 00:03:02.250 --> 00:03:03.350 Whereas a, 134 00:03:03.369 --> 00:03:03.919 um, 135 00:03:04.130 --> 00:03:06.910 a cattle machine is one that like is 136 00:03:07.050 --> 00:03:08.330 disposable, 137 00:03:08.570 --> 00:03:08.809 uh, 138 00:03:08.970 --> 00:03:11.070 used to serve one particular utility, 139 00:03:11.690 --> 00:03:13.130 not really valued as much, 140 00:03:13.250 --> 00:03:14.149 but like still, 141 00:03:14.369 --> 00:03:14.789 uh, 142 00:03:14.809 --> 00:03:15.289 important, 143 00:03:15.320 --> 00:03:16.320 and there's loads of them, 144 00:03:16.330 --> 00:03:17.179 or could be loads. 145 00:03:17.410 --> 00:03:17.789 So, 146 00:03:18.119 --> 00:03:19.020 Most of you 147 00:03:19.149 --> 00:03:21.940 um that exist on the on on on this community 148 00:03:22.470 --> 00:03:24.500 probably own pet like 149 00:03:24.639 --> 00:03:25.320 uh servers, 150 00:03:25.360 --> 00:03:25.509 right? 151 00:03:25.559 --> 00:03:26.899 You probably like for your 152 00:03:27.089 --> 00:03:30.039 headlesses maybe you rent um a VPS somewhere 153 00:03:30.039 --> 00:03:31.960 or like a bare metal headsna or something. 154 00:03:32.160 --> 00:03:32.750 That's like 155 00:03:32.880 --> 00:03:33.360 pet, 156 00:03:33.440 --> 00:03:33.779 uh, 157 00:03:33.839 --> 00:03:37.160 cos you know you you pay for it each month and then you do stuff to it, 158 00:03:37.419 --> 00:03:37.770 uh, 159 00:03:37.800 --> 00:03:40.919 that you like maybe right now it's a resonant headless but like a couple of 160 00:03:40.919 --> 00:03:44.440 years or maybe a few months ago it had a Minecraft server or whatever like. 161 00:03:44.559 --> 00:03:47.479 There is a sort of bit in the middle where you use docker containers for your health. 162 00:03:47.589 --> 00:03:49.990 Game servers and then it's sort of like half and half, 163 00:03:50.190 --> 00:03:51.720 but um I want to 164 00:03:51.880 --> 00:03:54.470 sort of expand that up to the VM tier 165 00:03:54.589 --> 00:03:57.350 and what that means is I don't really want anyone, 166 00:03:57.460 --> 00:04:03.259 and that includes me SSHing into the VM once it's set up and running a uh resonite 167 00:04:03.509 --> 00:04:04.350 headless in the, 168 00:04:04.389 --> 00:04:05.250 in their cloud 169 00:04:05.509 --> 00:04:06.289 because 170 00:04:06.550 --> 00:04:07.960 they shouldn't have to basically, 171 00:04:08.029 --> 00:04:08.979 like it should just, 172 00:04:08.990 --> 00:04:09.399 uh, 173 00:04:09.509 --> 00:04:11.070 that was the whole plan by Pterodactyl. 174 00:04:11.149 --> 00:04:11.389 I don't, 175 00:04:11.470 --> 00:04:14.449 I don't wanna add like another week to Rhea something so simple, 176 00:04:14.589 --> 00:04:16.988 so I will just docker containerize it. 177 00:04:17.230 --> 00:04:18.640 I could also do it by a zip, 178 00:04:18.829 --> 00:04:19.309 um, 179 00:04:19.450 --> 00:04:19.850 but 180 00:04:20.108 --> 00:04:20.510 like uh, 181 00:04:20.589 --> 00:04:20.660 it, 182 00:04:20.750 --> 00:04:24.380 it just like I can end up shoving like if like let's say the, 183 00:04:24.390 --> 00:04:26.329 the corporate universe needs 184 00:04:26.589 --> 00:04:28.540 400 headless instances later, 185 00:04:28.869 --> 00:04:31.769 we can just shove that container image into 186 00:04:32.649 --> 00:04:35.390 a container instances and it can do like thousands. 187 00:04:36.079 --> 00:04:39.350 More on that in in just a moment cos Jay's here talking about Cocois. 188 00:04:40.040 --> 00:04:40.519 um, 189 00:04:40.720 --> 00:04:41.119 Jack, 190 00:04:41.410 --> 00:04:42.429 let's jump around a little bit though. 191 00:04:42.720 --> 00:04:43.079 Jack says, 192 00:04:43.119 --> 00:04:45.679 are you gonna create an official Docker image for Resident Headlesses? 193 00:04:45.880 --> 00:04:46.109 Uh, 194 00:04:46.119 --> 00:04:47.739 that's basically what's gonna happen um 195 00:04:49.000 --> 00:04:50.079 no one will have access to. 196 00:04:50.269 --> 00:04:54.019 I'm looking into ways of like maybe being able to do it, 197 00:04:54.320 --> 00:04:55.040 but it's, 198 00:04:55.079 --> 00:04:58.190 it's like squirrelled in a corner to like corp over stuff, 199 00:04:58.200 --> 00:05:00.570 like I wouldn't be able to containerize 200 00:05:00.869 --> 00:05:00.880 anything. 201 00:05:01.029 --> 00:05:03.230 Think that would be compatible with your stuff. 202 00:05:03.540 --> 00:05:03.950 Basically, 203 00:05:03.959 --> 00:05:04.399 there's a, 204 00:05:04.440 --> 00:05:08.380 a branch of Fruits Engine um for Corpoverse and 205 00:05:08.640 --> 00:05:09.739 to meet their 206 00:05:09.910 --> 00:05:12.670 like deadlines and their requirements and their goals, 207 00:05:12.760 --> 00:05:16.600 I'm kind of ignoring the traditional sort of PR based 208 00:05:16.600 --> 00:05:18.920 process and just like hammering on this one branch, 209 00:05:18.959 --> 00:05:20.570 and so it takes to come back to the, 210 00:05:20.579 --> 00:05:21.559 into the mainline branch, 211 00:05:21.640 --> 00:05:23.109 I have to like split stuff up, 212 00:05:23.480 --> 00:05:23.709 uh, 213 00:05:23.720 --> 00:05:25.440 cos sometimes even I don't know what I'm changing, 214 00:05:25.480 --> 00:05:25.899 it's like, 215 00:05:25.910 --> 00:05:26.040 oh. 216 00:05:26.119 --> 00:05:26.359 You know, 217 00:05:26.440 --> 00:05:28.190 we really need this by like Tuesday, 218 00:05:28.200 --> 00:05:29.079 and I'm just like 219 00:05:29.399 --> 00:05:34.670 get commit blah I just deploy that to like corporate servers or works. 220 00:05:35.079 --> 00:05:35.619 So 221 00:05:35.880 --> 00:05:37.420 going back to that, 222 00:05:37.649 --> 00:05:38.149 uh, 223 00:05:38.200 --> 00:05:39.260 what I set up, 224 00:05:39.399 --> 00:05:39.959 um, 225 00:05:40.079 --> 00:05:40.910 over in the, 226 00:05:40.920 --> 00:05:42.500 the terraform repository 227 00:05:42.799 --> 00:05:43.519 is, 228 00:05:43.850 --> 00:05:44.269 uh, 229 00:05:44.279 --> 00:05:45.589 what's called Packer build script. 230 00:05:45.679 --> 00:05:49.239 Packer is like terraform's answer to VM pros provisioning, 231 00:05:49.510 --> 00:05:51.200 and what that does is it instals. 232 00:05:51.429 --> 00:05:51.440 To, 233 00:05:51.989 --> 00:05:52.799 uh, 234 00:05:53.040 --> 00:05:54.880 like utilities like Curl and Git, 235 00:05:55.160 --> 00:05:55.519 um, 236 00:05:55.739 --> 00:05:56.940 Docker and the dot, 237 00:05:57.040 --> 00:05:57.149 uh, 238 00:05:57.200 --> 00:05:59.239 and then it sets up like a template, 239 00:05:59.359 --> 00:05:59.519 um, 240 00:05:59.670 --> 00:06:01.929 System D uh service and 241 00:06:02.040 --> 00:06:02.519 it stops, 242 00:06:02.600 --> 00:06:03.230 that's the VM. 243 00:06:03.309 --> 00:06:04.679 It doesn't enable that system. 244 00:06:04.720 --> 00:06:04.869 Uh, 245 00:06:04.920 --> 00:06:08.059 then in the terra form we we can reference that, 246 00:06:08.239 --> 00:06:08.720 uh, 247 00:06:08.839 --> 00:06:11.040 built image cos the image is only built once and it just, 248 00:06:11.100 --> 00:06:12.940 it speeds up the image creation. 249 00:06:13.079 --> 00:06:13.390 Um, 250 00:06:13.559 --> 00:06:13.899 but 251 00:06:14.200 --> 00:06:14.390 in, 252 00:06:14.480 --> 00:06:14.750 in, 253 00:06:14.799 --> 00:06:16.359 in setting all of that up. 254 00:06:16.480 --> 00:06:17.440 I'm just like 255 00:06:17.760 --> 00:06:19.500 kind of just sounds like I should 256 00:06:19.720 --> 00:06:21.190 Fedora core OS this. 257 00:06:21.470 --> 00:06:22.000 And 258 00:06:22.279 --> 00:06:24.420 so then I got like paralysed by 259 00:06:24.859 --> 00:06:25.600 analysis, 260 00:06:25.760 --> 00:06:26.859 paralysis over 261 00:06:27.200 --> 00:06:30.299 hm should I just like undo all of this like 262 00:06:30.510 --> 00:06:31.480 Packer stuff, 263 00:06:31.619 --> 00:06:35.760 cloud in it stuff that that handles all this like provisioning of a VM 264 00:06:35.959 --> 00:06:37.829 and instead just provision a 265 00:06:37.950 --> 00:06:41.519 Fedora Co OS with like one YAL file and it'll just do it. 266 00:06:41.829 --> 00:06:42.109 Uh, 267 00:06:42.230 --> 00:06:45.649 so I went on a rabbit hole last night and looked into 268 00:06:45.869 --> 00:06:47.790 what J4 is doing with Co OS, 269 00:06:47.910 --> 00:06:48.500 um, 270 00:06:48.829 --> 00:06:49.260 to 271 00:06:49.440 --> 00:06:51.429 stand up our like internal IT services, 272 00:06:51.470 --> 00:06:52.059 and I'm just like, 273 00:06:52.070 --> 00:06:56.309 it looks like this would be easier and kind of exactly what I want. 274 00:06:56.549 --> 00:06:58.549 So I might eat the time and do that. 275 00:06:58.630 --> 00:07:01.899 I probably won't charge the corporate place for that cos like I've already done it, 276 00:07:01.910 --> 00:07:03.250 like it already works with Packer. 277 00:07:03.600 --> 00:07:04.040 Uh, 278 00:07:04.130 --> 00:07:05.140 but at that point 279 00:07:05.440 --> 00:07:06.380 they will have, 280 00:07:06.480 --> 00:07:06.920 um, 281 00:07:07.000 --> 00:07:09.640 a VM in Azure that is Fedora KRS. 282 00:07:09.880 --> 00:07:11.880 The reason why I'm saying Fedora KRS very clearly 283 00:07:11.880 --> 00:07:13.660 is cause if you look for CoroS Coors, 284 00:07:13.679 --> 00:07:14.899 you'll end up at Red Hat, 285 00:07:14.920 --> 00:07:15.750 and then it's like, 286 00:07:15.760 --> 00:07:16.630 I don't know what the hell, 287 00:07:16.799 --> 00:07:17.679 Fedora CoRS. 288 00:07:17.880 --> 00:07:18.390 Um, 289 00:07:18.399 --> 00:07:19.109 I have a question for you, 290 00:07:19.119 --> 00:07:19.269 Jay, 291 00:07:19.279 --> 00:07:19.440 as well, 292 00:07:19.519 --> 00:07:20.630 I'll get it to you in just a moment. 293 00:07:20.799 --> 00:07:21.279 Um, 294 00:07:21.589 --> 00:07:21.790 so I'm, 295 00:07:21.829 --> 00:07:22.269 I'm gonna look in, 296 00:07:22.320 --> 00:07:22.690 I'm gonna look in. 297 00:07:22.880 --> 00:07:23.679 I kinda just want to. 298 00:07:23.920 --> 00:07:25.380 Part of the way that like, 299 00:07:25.679 --> 00:07:26.470 uh, 300 00:07:26.559 --> 00:07:30.619 Frukes is like developed methodology and also mine due to 301 00:07:30.760 --> 00:07:33.279 particularly this project due to some of the requirements by the corporate. 302 00:07:33.494 --> 00:07:34.295 IT team, 303 00:07:34.505 --> 00:07:34.704 um, 304 00:07:34.774 --> 00:07:36.484 i.e. terraform and sort of, 305 00:07:36.665 --> 00:07:37.265 uh, 306 00:07:37.345 --> 00:07:38.515 unattended setup 307 00:07:38.665 --> 00:07:41.174 is like trying to do things the correct way. 308 00:07:41.385 --> 00:07:44.065 So like if you right now had access to like a 309 00:07:44.065 --> 00:07:46.964 corporate IT infrastructure that could spin up any VM you want, 310 00:07:47.144 --> 00:07:47.665 Ubuntu, 311 00:07:47.744 --> 00:07:48.454 Windows, 312 00:07:48.825 --> 00:07:49.625 Windows 7, 313 00:07:49.704 --> 00:07:50.225 Windows 8, 314 00:07:50.345 --> 00:07:51.184 like they've got all of like, 315 00:07:51.225 --> 00:07:54.174 I've got access to do like any VM you can imagine, 316 00:07:54.385 --> 00:07:55.184 and they were like, 317 00:07:55.464 --> 00:07:58.774 could you set us up a headless server so we can just prove that that works. 318 00:07:59.144 --> 00:08:00.364 You'd probably just like 319 00:08:00.744 --> 00:08:03.184 make a VM SSH into it and like run a. 320 00:08:03.320 --> 00:08:04.450 Bunch of manual commands, 321 00:08:04.489 --> 00:08:04.850 but like I, 322 00:08:04.920 --> 00:08:05.160 I just, 323 00:08:05.209 --> 00:08:06.450 I don't want to do that 324 00:08:06.890 --> 00:08:08.890 because I'll forget what ones I did. 325 00:08:09.209 --> 00:08:09.769 So I, 326 00:08:09.829 --> 00:08:10.049 I, 327 00:08:10.130 --> 00:08:11.859 I kinda wanna set it up properly, 328 00:08:12.010 --> 00:08:12.890 which leads to sort of, 329 00:08:12.970 --> 00:08:13.130 you know, 330 00:08:13.279 --> 00:08:14.649 more infrastructure as a code, 331 00:08:14.690 --> 00:08:15.070 etc. 332 00:08:15.239 --> 00:08:16.269 and then when I discover, 333 00:08:16.690 --> 00:08:17.119 hey, 334 00:08:17.369 --> 00:08:19.049 there's an entire OS 335 00:08:19.450 --> 00:08:21.510 dedicated to like this problem 336 00:08:21.910 --> 00:08:24.709 uh that you're trying to solve using like 337 00:08:24.809 --> 00:08:25.329 Terraform, 338 00:08:25.450 --> 00:08:26.359 that's one system, 339 00:08:26.570 --> 00:08:26.959 Packer, 340 00:08:27.049 --> 00:08:28.049 that's 2 systems, 341 00:08:28.250 --> 00:08:28.929 cloud in it, 342 00:08:29.010 --> 00:08:29.970 that's 3 systems, 343 00:08:30.010 --> 00:08:30.769 and then Docker, 344 00:08:30.809 --> 00:08:31.809 that's 4 systems. 345 00:08:31.929 --> 00:08:32.549 It's just like 346 00:08:32.679 --> 00:08:33.090 nah man. 347 00:08:33.195 --> 00:08:33.705 I think, 348 00:08:33.715 --> 00:08:34.695 I think we can just 349 00:08:34.945 --> 00:08:35.455 Kro and, 350 00:08:35.465 --> 00:08:36.825 and so then that gets into sort of like, 351 00:08:36.914 --> 00:08:37.284 hey, 352 00:08:37.554 --> 00:08:37.933 you know, 353 00:08:38.034 --> 00:08:38.445 um, 354 00:08:38.515 --> 00:08:40.375 Frukes' development methodology 355 00:08:40.585 --> 00:08:42.784 actually sort of encourages this kind of, 356 00:08:42.804 --> 00:08:43.715 of rabbit hole. 357 00:08:43.835 --> 00:08:44.215 Of course, 358 00:08:44.234 --> 00:08:46.695 read the how we prioritise document for more information about it. 359 00:08:46.835 --> 00:08:50.895 I'm gonna link Fedora um ROS in the video description, 360 00:08:51.025 --> 00:08:51.655 you know what I mean. 361 00:08:51.875 --> 00:08:52.094 Uh, 362 00:08:52.114 --> 00:08:52.554 here it is, 363 00:08:52.635 --> 00:08:53.494 it's uh 364 00:08:53.794 --> 00:08:55.815 like it's a lot to sort of figure out, 365 00:08:56.075 --> 00:08:56.474 but, 366 00:08:56.635 --> 00:08:57.244 um, 367 00:08:57.265 --> 00:09:00.775 essentially you throw like a Yamal file at like Fedora 368 00:09:01.065 --> 00:09:02.015 and it goes 369 00:09:02.474 --> 00:09:03.034 yo. 370 00:09:03.960 --> 00:09:05.159 And just like run stuff. 371 00:09:05.330 --> 00:09:05.890 However, 372 00:09:06.090 --> 00:09:08.969 the um the reason why I have a question, 373 00:09:09.239 --> 00:09:09.690 Jay, 374 00:09:10.010 --> 00:09:10.679 is, 375 00:09:11.010 --> 00:09:11.729 hi Jay, 376 00:09:12.010 --> 00:09:12.229 or, 377 00:09:12.239 --> 00:09:13.609 or Brodosing Breto's there. 378 00:09:13.890 --> 00:09:15.690 What is Fedora silver Blue, 379 00:09:15.929 --> 00:09:16.460 Fedora 380 00:09:17.090 --> 00:09:17.250 Knuote, 381 00:09:18.010 --> 00:09:18.460 uh 382 00:09:18.650 --> 00:09:20.250 Fedora sway atomic, 383 00:09:20.489 --> 00:09:22.190 Fedora budgie atomic, 384 00:09:22.450 --> 00:09:23.190 Fedora 385 00:09:23.539 --> 00:09:24.809 cosmic atomic. 386 00:09:25.090 --> 00:09:26.590 They're listed under the docks as 387 00:09:26.700 --> 00:09:27.729 atomic desktops, 388 00:09:27.770 --> 00:09:28.159 which they, 389 00:09:28.210 --> 00:09:29.330 they sound identical 390 00:09:29.809 --> 00:09:30.469 to 391 00:09:30.729 --> 00:09:31.489 Kos. 392 00:09:31.770 --> 00:09:31.890 So like. 393 00:09:32.023 --> 00:09:32.143 I, 394 00:09:32.174 --> 00:09:34.403 I don't understand like why there are so many. 395 00:09:34.664 --> 00:09:35.044 Um, 396 00:09:35.304 --> 00:09:35.864 that page, 397 00:09:35.943 --> 00:09:37.463 I'm just like for the benefit of everyone here, 398 00:09:37.544 --> 00:09:38.864 that page is just ridiculous, 399 00:09:38.924 --> 00:09:39.104 right? 400 00:09:39.213 --> 00:09:39.523 So 401 00:09:39.693 --> 00:09:40.624 Fedora Silver Blue, 402 00:09:40.703 --> 00:09:42.624 what's the description of Fedora Silver Blue? 403 00:09:42.864 --> 00:09:45.414 Fedora Silver Blue is a variant of Fedora workstation, 404 00:09:45.424 --> 00:09:46.054 and I'm just like, 405 00:09:46.143 --> 00:09:46.614 oh, 406 00:09:46.703 --> 00:09:47.283 OK. 407 00:09:47.783 --> 00:09:51.083 Do I need like a tech tree of Fedora instances at this point? 408 00:09:51.304 --> 00:09:53.164 But it gets even more ridiculous. 409 00:09:53.383 --> 00:09:57.703 Fedora Budgie Atomic is a variant of Fedora Budgie spin. 410 00:09:58.093 --> 00:09:58.263 What the, 411 00:09:58.304 --> 00:10:00.223 what the fuck is Fedora Budgie? 412 00:10:00.528 --> 00:10:00.708 Spin. 413 00:10:01.197 --> 00:10:01.567 OK, 414 00:10:01.788 --> 00:10:02.148 uh, 415 00:10:02.437 --> 00:10:03.737 Fedora spins 416 00:10:03.867 --> 00:10:04.398 are 417 00:10:04.668 --> 00:10:07.018 alternative desktops for Fedora, 418 00:10:07.197 --> 00:10:07.528 um, 419 00:10:07.757 --> 00:10:08.208 so 420 00:10:08.408 --> 00:10:12.437 Fedora Cinnamon has the cinnamon window manager or or desktop manager, 421 00:10:12.557 --> 00:10:13.757 terminology is more correct. 422 00:10:13.958 --> 00:10:14.158 So yeah, 423 00:10:14.237 --> 00:10:15.778 I don't understand the difference, 424 00:10:15.997 --> 00:10:16.658 uh, 425 00:10:16.908 --> 00:10:17.177 between 426 00:10:17.757 --> 00:10:18.598 what I just described, 427 00:10:18.677 --> 00:10:22.598 these Fedora Atomic desktops and Fedora Cos cos they sound like ident, 428 00:10:22.677 --> 00:10:23.148 um, 429 00:10:23.278 --> 00:10:23.877 I, 430 00:10:24.197 --> 00:10:24.718 a long, 431 00:10:24.838 --> 00:10:24.987 long, 432 00:10:25.038 --> 00:10:25.197 long, 433 00:10:25.237 --> 00:10:25.398 long, 434 00:10:25.437 --> 00:10:25.557 long, 435 00:10:25.627 --> 00:10:25.757 long, 436 00:10:25.828 --> 00:10:26.228 long, 437 00:10:26.437 --> 00:10:27.578 long time ago, 438 00:10:27.797 --> 00:10:28.398 um. 439 00:10:28.682 --> 00:10:30.411 I looked into Fedora Kos. 440 00:10:30.461 --> 00:10:32.492 This was before it was under the Fedora project, 441 00:10:32.611 --> 00:10:33.632 so it was just Coros, 442 00:10:33.651 --> 00:10:33.892 I think, 443 00:10:34.132 --> 00:10:35.122 because I was like, 444 00:10:35.452 --> 00:10:35.932 oh, 445 00:10:36.132 --> 00:10:37.052 it's beautiful, 446 00:10:37.132 --> 00:10:38.882 like this is like exactly what I want. 447 00:10:39.132 --> 00:10:41.392 But at the time there was like zero documentation 448 00:10:41.932 --> 00:10:43.182 and so I haven't touched it. 449 00:10:43.331 --> 00:10:43.651 Like I, 450 00:10:43.731 --> 00:10:45.111 I last looked at KroS 451 00:10:45.651 --> 00:10:46.072 like 452 00:10:46.452 --> 00:10:47.651 before I worked at Residite, 453 00:10:47.812 --> 00:10:49.471 probably before Mixer as well. 454 00:10:49.771 --> 00:10:49.971 Hey, 455 00:10:50.052 --> 00:10:50.401 uh, 456 00:10:50.651 --> 00:10:51.012 you know the, 457 00:10:51.091 --> 00:10:53.062 the Jedi Council got a bit suss 458 00:10:53.171 --> 00:10:54.952 um towards the end of the Jedi Order. 459 00:10:55.322 --> 00:10:56.771 Let's hope the Fedora Council. 460 00:10:57.346 --> 00:10:57.786 Um, 461 00:10:57.935 --> 00:10:58.065 you know, 462 00:10:58.185 --> 00:10:58.546 don't, 463 00:10:58.695 --> 00:11:01.335 don't have to like have an order 66 on them. 464 00:11:01.585 --> 00:11:01.825 Yeah, 465 00:11:01.935 --> 00:11:02.065 uh, 466 00:11:02.145 --> 00:11:02.726 Exxon, 467 00:11:02.786 --> 00:11:07.005 Nix OS is from 2003 and Nix has been like my hype for a bit, 468 00:11:07.265 --> 00:11:07.606 but 469 00:11:07.745 --> 00:11:10.226 like I look at like a Nix file for installing 470 00:11:10.226 --> 00:11:12.536 like Discord and I'm just like I hate this, 471 00:11:12.606 --> 00:11:15.776 like why is this like 50 lines of like I don't understand. 472 00:11:16.026 --> 00:11:16.455 Anyway, 473 00:11:16.546 --> 00:11:19.205 I believe that's enough on the sort of rat hole where 474 00:11:19.426 --> 00:11:21.245 I did a piece of work 475 00:11:21.385 --> 00:11:24.005 that I realised that J4 was also doing 476 00:11:24.306 --> 00:11:25.065 and then. 477 00:11:25.460 --> 00:11:26.000 Uh, 478 00:11:26.140 --> 00:11:27.039 get stuck 479 00:11:27.140 --> 00:11:27.820 in 480 00:11:28.020 --> 00:11:31.729 analysis paralysis and then sleep on it and figure out, 481 00:11:32.059 --> 00:11:32.219 yeah, 482 00:11:32.340 --> 00:11:34.780 my stuff's getting real complicated and all I really 483 00:11:34.780 --> 00:11:37.400 want to do is run like 3 docker containers 484 00:11:37.659 --> 00:11:38.500 on a VM 485 00:11:38.700 --> 00:11:39.440 that I can, 486 00:11:39.580 --> 00:11:39.929 you know, 487 00:11:40.299 --> 00:11:40.960 manipulate 488 00:11:41.380 --> 00:11:43.280 very easily and not 489 00:11:43.580 --> 00:11:44.159 allow, 490 00:11:44.299 --> 00:11:44.719 um, 491 00:11:44.900 --> 00:11:47.119 other people that will have access to it to make a mess space. 492 00:11:47.179 --> 00:11:47.979 For an indication of, 493 00:11:48.020 --> 00:11:48.219 of, 494 00:11:48.299 --> 00:11:49.650 of what I was dealing with, 495 00:11:49.659 --> 00:11:50.179 um. 496 00:11:50.344 --> 00:11:51.284 When I would hand them 497 00:11:51.734 --> 00:11:54.294 headlesses before we had all the seizure stuff set up, 498 00:11:54.505 --> 00:11:55.544 they would take it 499 00:11:55.705 --> 00:11:57.984 and then it would end up in this directory tree on, 500 00:11:58.025 --> 00:12:00.044 on the machine they were using to test the headless 501 00:12:00.315 --> 00:12:01.864 with like 3 or 4 like 502 00:12:02.104 --> 00:12:03.994 shell scripts that basically were like, 503 00:12:04.174 --> 00:12:04.825 run this version, 504 00:12:04.974 --> 00:12:05.734 run this version, 505 00:12:05.864 --> 00:12:06.614 use this folder, 506 00:12:06.684 --> 00:12:07.385 use this folder, 507 00:12:07.484 --> 00:12:08.065 use that folder, 508 00:12:08.184 --> 00:12:08.775 and it was just like, 509 00:12:08.794 --> 00:12:10.244 this is just like too complicated, 510 00:12:10.465 --> 00:12:11.765 like there's too much stuff. 511 00:12:11.945 --> 00:12:12.375 Uh anyway, 512 00:12:12.465 --> 00:12:14.104 we will continue with questions. 513 00:12:14.304 --> 00:12:14.594 Uhente. 514 00:12:15.909 --> 00:12:17.590 I want to create a fully functional chow garden. 515 00:12:17.669 --> 00:12:19.710 Does Resonate support cross-world data sharing, 516 00:12:19.789 --> 00:12:20.179 i.e., 517 00:12:20.619 --> 00:12:22.590 could players collect animals across several worlds 518 00:12:22.590 --> 00:12:24.020 to take into the chow garden world? 519 00:12:24.299 --> 00:12:25.150 Absolutely, 520 00:12:25.229 --> 00:12:25.500 um, 521 00:12:25.630 --> 00:12:27.250 there are many ways to do that. 522 00:12:27.419 --> 00:12:27.809 Uh, 523 00:12:27.909 --> 00:12:28.669 one of the 524 00:12:28.989 --> 00:12:33.059 maybe easiest ways to look at that I can think of right now is from an MMC, 525 00:12:33.109 --> 00:12:35.309 that's Metaverse Maker competition entry from, 526 00:12:35.469 --> 00:12:36.820 I wanna say like a year or two ago, 527 00:12:36.869 --> 00:12:38.210 I don't know how many though. 528 00:12:38.510 --> 00:12:39.099 Um, 529 00:12:39.349 --> 00:12:42.469 Cloudscape Harvest uses this like entity system where 530 00:12:42.469 --> 00:12:44.419 you can like save your game and. 531 00:12:44.711 --> 00:12:45.861 Store it in your inventory, 532 00:12:46.122 --> 00:12:47.262 and so 533 00:12:47.562 --> 00:12:50.361 all you'll have to do for that is like take a look at it for, 534 00:12:50.452 --> 00:12:50.961 for, 535 00:12:50.971 --> 00:12:51.122 you know, 536 00:12:51.202 --> 00:12:52.081 chows and stuff like that. 537 00:12:52.242 --> 00:12:52.481 Uh, 538 00:12:52.521 --> 00:12:53.161 for chows though, 539 00:12:53.202 --> 00:12:54.541 you might be able to do that 540 00:12:54.921 --> 00:12:55.642 without that system, 541 00:12:55.721 --> 00:12:59.271 you might just be able to use one of our features called dynamic variables, 542 00:12:59.281 --> 00:13:01.921 and then they just resave the chow to their inventory. 543 00:13:02.382 --> 00:13:02.392 Uh, 544 00:13:02.562 --> 00:13:04.382 the problem that you will have 545 00:13:04.521 --> 00:13:06.781 is that unless they resave it, 546 00:13:07.041 --> 00:13:07.171 uh, 547 00:13:07.322 --> 00:13:09.411 the information will be lost between sessions. 548 00:13:09.632 --> 00:13:12.041 So at which point you could use cloud variables, 549 00:13:12.202 --> 00:13:13.442 but at that point you would need. 550 00:13:13.533 --> 00:13:16.924 Like a cloud variable per chow and that's kind of problemic, 551 00:13:16.973 --> 00:13:17.393 so 552 00:13:17.494 --> 00:13:18.473 maybe back to 553 00:13:18.643 --> 00:13:19.973 cloud skip harvest System. 554 00:13:20.273 --> 00:13:21.374 savable entity system, 555 00:13:21.453 --> 00:13:21.703 yes, 556 00:13:21.883 --> 00:13:23.883 it's the MC entry I'm referring to. 557 00:13:24.093 --> 00:13:26.294 Kind of interesting cos you could bodge job 558 00:13:26.294 --> 00:13:29.374 the workspace component to like handle a pet. 559 00:13:29.573 --> 00:13:31.523 A workspace component will like 560 00:13:31.734 --> 00:13:33.484 periodically save if there have been updates, 561 00:13:33.494 --> 00:13:34.013 etc. 562 00:13:34.533 --> 00:13:36.283 and so if you could get it out of user space, 563 00:13:36.333 --> 00:13:36.754 you could, 564 00:13:36.773 --> 00:13:40.254 you could make like an auto saving like cookie clicker but like autosave. 565 00:13:40.453 --> 00:13:42.414 We're actually seeing is workspace is working. 566 00:13:42.666 --> 00:13:42.866 Space, 567 00:13:42.906 --> 00:13:46.385 you could put user space as a desktop facet and have it all saved with the workspace, 568 00:13:46.666 --> 00:13:47.005 but 569 00:13:47.265 --> 00:13:47.745 other than that, 570 00:13:47.786 --> 00:13:48.166 you can't. 571 00:13:48.346 --> 00:13:50.065 Workspaces are still user space only. 572 00:13:50.216 --> 00:13:51.026 Let us move forwards. 573 00:13:51.106 --> 00:13:51.606 Um, 574 00:13:52.026 --> 00:13:52.966 I'm speaking like a 575 00:13:53.265 --> 00:13:54.176 Jedi councilman, 576 00:13:54.306 --> 00:13:55.466 let us move forwards. 577 00:13:55.616 --> 00:13:58.406 What is the next item on the Jedi council's meeting? 578 00:13:58.585 --> 00:13:58.786 Uh, 579 00:13:58.825 --> 00:14:00.335 the next item is, 580 00:14:00.546 --> 00:14:00.745 alright, 581 00:14:00.825 --> 00:14:03.705 we're still talking about Linux Linux Linux disc draws. 582 00:14:04.085 --> 00:14:04.096 Uh, 583 00:14:04.106 --> 00:14:04.426 Reddit says, 584 00:14:04.466 --> 00:14:05.286 when are you publishing 585 00:14:05.825 --> 00:14:07.575 your office hours recordings next? 586 00:14:07.856 --> 00:14:09.085 Your latest one is from January. 587 00:14:09.306 --> 00:14:09.385 I, 588 00:14:09.426 --> 00:14:10.255 I have them all saved, 589 00:14:10.306 --> 00:14:10.495 actually, 590 00:14:10.505 --> 00:14:11.585 I think I lost one, 591 00:14:12.739 --> 00:14:14.940 I think I lost one due to my right click not working. 592 00:14:15.059 --> 00:14:16.200 Turns out it was the actual mouse. 593 00:14:16.380 --> 00:14:17.969 I just bought a new mouse and it's fixed. 594 00:14:18.140 --> 00:14:20.619 I don't like that cos I should have taken the mouse apart, 595 00:14:20.739 --> 00:14:21.119 but 596 00:14:21.630 --> 00:14:22.919 sometimes you just like need to 597 00:14:23.190 --> 00:14:24.700 push stuff out of the way and get, 598 00:14:24.820 --> 00:14:25.289 get on with it, 599 00:14:25.369 --> 00:14:25.979 and that's what's happened. 600 00:14:26.059 --> 00:14:28.400 My old mouse has just been pushed out of the way to another 601 00:14:28.780 --> 00:14:31.330 area of my desk directly above my mouse mat. 602 00:14:31.619 --> 00:14:33.520 And it's there to remind me to repair it, 603 00:14:34.099 --> 00:14:35.260 cos it's a really nice mouse, 604 00:14:35.340 --> 00:14:38.330 so all I need to do is figure out like why is the right click intermittent. 605 00:14:38.570 --> 00:14:39.849 er if the switch is wrong, 606 00:14:39.940 --> 00:14:42.659 I've got um an actual fully broken one of those 607 00:14:42.659 --> 00:14:45.789 mice in a cupboard somewhere and I can probably like er 608 00:14:45.900 --> 00:14:47.419 donor board it for a new switch. 609 00:14:47.609 --> 00:14:47.809 Anyway, 610 00:14:47.840 --> 00:14:49.979 we're talking about that because of office hours and 611 00:14:49.979 --> 00:14:51.780 new computers and the fact that I've lost one. 612 00:14:51.900 --> 00:14:54.140 So I have lost the recording of um 613 00:14:54.419 --> 00:14:54.710 additionally, 614 00:14:54.780 --> 00:14:55.500 I have all the other ones. 615 00:14:56.135 --> 00:14:57.895 But I don't have the script to upload them, 616 00:14:58.224 --> 00:15:00.094 because that is on my old hard drive, 617 00:15:00.304 --> 00:15:02.924 which is currently unplugged because 618 00:15:03.255 --> 00:15:07.414 uh I didn't have a spare USB port when I was diagnosing mouse issues, 619 00:15:07.695 --> 00:15:11.885 so I unplugged the external hard drive and plugged the mouse's uh dongle 620 00:15:12.184 --> 00:15:13.945 directly into the front panel bus. 621 00:15:14.375 --> 00:15:14.585 So like, 622 00:15:15.505 --> 00:15:17.364 that's also why I lost the recording, 623 00:15:17.424 --> 00:15:18.604 cos I interrupted 624 00:15:18.775 --> 00:15:19.625 it saving. 625 00:15:19.820 --> 00:15:20.950 To the old hard drive. 626 00:15:21.109 --> 00:15:21.859 I'm having fun, 627 00:15:21.989 --> 00:15:22.289 basically, 628 00:15:22.549 --> 00:15:23.549 the mouse issue is now. 629 00:15:23.940 --> 00:15:25.450 uh I'll get it done as soon as possible. 630 00:15:25.710 --> 00:15:26.580 uh one of the other things, 631 00:15:26.630 --> 00:15:30.190 and I know I keep saying this and I talked about it in the office hours announcement, 632 00:15:30.510 --> 00:15:30.890 I 633 00:15:31.190 --> 00:15:31.849 um 634 00:15:32.150 --> 00:15:34.010 want to get this up on Twitch, 635 00:15:34.190 --> 00:15:34.619 but 636 00:15:34.869 --> 00:15:38.650 what I need to do there is to set up um probably a bunch of scenes, 637 00:15:38.989 --> 00:15:41.229 and I also kind of wanna do something a little bit different, 638 00:15:41.349 --> 00:15:41.929 which is 639 00:15:42.190 --> 00:15:43.099 not be in resonate, 640 00:15:43.190 --> 00:15:43.710 I know that most. 641 00:15:43.794 --> 00:15:45.875 Of our office hours for on Twitch are in Resonate, 642 00:15:46.315 --> 00:15:48.234 but due to the nature of my office hours where 643 00:15:48.234 --> 00:15:50.294 I like dive into things like the tech tree, 644 00:15:50.434 --> 00:15:50.895 code, 645 00:15:51.304 --> 00:15:52.354 rant about recycling, 646 00:15:52.395 --> 00:15:52.994 etc. 647 00:15:53.275 --> 00:15:54.255 I think like a 648 00:15:54.525 --> 00:15:56.195 YouTuber setup would be a better thing. 649 00:15:56.315 --> 00:15:57.434 So I wanna get that set up. 650 00:15:57.515 --> 00:15:59.234 So you've got like me in the right corner, 651 00:15:59.315 --> 00:16:00.075 bottom right 652 00:16:00.284 --> 00:16:00.655 like 653 00:16:00.784 --> 00:16:01.575 emoting and, 654 00:16:01.585 --> 00:16:02.094 and stuff, 655 00:16:02.395 --> 00:16:05.835 and then you'll have like question feed or or like cali 656 00:16:05.835 --> 00:16:07.755 drawer in the middle and I think that's what I wanted. 657 00:16:08.500 --> 00:16:08.590 Oh, 658 00:16:08.669 --> 00:16:09.710 I bought ice cream today, 659 00:16:09.869 --> 00:16:10.460 hell yeah. 660 00:16:10.599 --> 00:16:11.140 Um, 661 00:16:11.390 --> 00:16:11.549 uh, 662 00:16:11.590 --> 00:16:12.059 Sente, 663 00:16:12.190 --> 00:16:12.729 um, 664 00:16:12.739 --> 00:16:13.489 asks about, 665 00:16:13.630 --> 00:16:14.219 um, 666 00:16:14.229 --> 00:16:16.330 Jack's savable entity system and says, 667 00:16:16.710 --> 00:16:18.070 is that vulnerable to hackers though, 668 00:16:18.159 --> 00:16:18.299 like, 669 00:16:18.349 --> 00:16:21.369 could cheaters go into their inventory code and give their Chow Max stats? 670 00:16:21.669 --> 00:16:21.900 Uh, 671 00:16:21.929 --> 00:16:22.710 at the moment, 672 00:16:22.900 --> 00:16:25.729 that sort of problem is impossible to resolve 673 00:16:25.869 --> 00:16:26.549 in resonate. 674 00:16:27.409 --> 00:16:28.039 Like a 675 00:16:28.630 --> 00:16:33.330 like significantly motivated person would be able to figure out how that works. 676 00:16:33.609 --> 00:16:34.669 I'll give you an example, 677 00:16:34.809 --> 00:16:35.059 um, 678 00:16:35.169 --> 00:16:38.909 some users have uh boot counters or head pack counters, 679 00:16:39.210 --> 00:16:39.719 um, 680 00:16:40.130 --> 00:16:41.210 on their avatars, 681 00:16:41.559 --> 00:16:43.609 and one user in particular, 682 00:16:43.690 --> 00:16:44.289 um, 683 00:16:44.570 --> 00:16:44.809 had. 684 00:16:44.940 --> 00:16:45.320 One 685 00:16:45.640 --> 00:16:47.200 that used an external API. 686 00:16:47.400 --> 00:16:49.520 So instead of using cloud variables or anything like that, 687 00:16:49.559 --> 00:16:51.659 it did a HTTP request 688 00:16:52.159 --> 00:16:53.400 every time they were booped. 689 00:16:53.580 --> 00:16:54.940 And uh 690 00:16:55.280 --> 00:16:56.580 someone figured out 691 00:16:56.880 --> 00:16:58.770 the API and how it worked, 692 00:16:58.840 --> 00:17:01.219 and they were able to cheat to get to the 693 00:17:01.559 --> 00:17:02.559 top of the boop. 694 00:17:03.390 --> 00:17:06.290 One of the important things to uh keep in mind 695 00:17:06.469 --> 00:17:07.098 is that 696 00:17:07.390 --> 00:17:10.229 even with like mainstream AAA games, 697 00:17:10.550 --> 00:17:11.930 people cheat on them all the time. 698 00:17:12.108 --> 00:17:14.550 And that's that's even things like Battlefield and stuff like that, 699 00:17:14.630 --> 00:17:16.030 and it's like in Battlefield etc. 700 00:17:16.348 --> 00:17:18.380 do they get like stopped or banned, 701 00:17:18.510 --> 00:17:18.670 yeah, 702 00:17:18.829 --> 00:17:19.910 cos it's like a big enough game. 703 00:17:20.108 --> 00:17:22.348 But smaller games like single player games, 704 00:17:22.709 --> 00:17:23.829 people cheat all the time. 705 00:17:24.113 --> 00:17:24.723 Um, 706 00:17:24.892 --> 00:17:25.551 you can't, 707 00:17:25.733 --> 00:17:26.233 like, 708 00:17:26.492 --> 00:17:27.922 always protect against it, 709 00:17:28.133 --> 00:17:28.762 and then resonate, 710 00:17:29.052 --> 00:17:32.213 particularly cos we have a feature gap for a system called hard permissions, 711 00:17:32.253 --> 00:17:33.392 which is on our roadmap, 712 00:17:33.642 --> 00:17:33.932 uh, 713 00:17:34.012 --> 00:17:36.442 it would be like quite difficult to, 714 00:17:36.532 --> 00:17:37.593 to make it secure 715 00:17:37.772 --> 00:17:38.363 right now. 716 00:17:38.613 --> 00:17:40.713 It would be less difficult to do that in the future, 717 00:17:40.973 --> 00:17:42.723 but still probably not for. 718 00:17:42.892 --> 00:17:44.572 Jay provided a picture of. 719 00:17:44.676 --> 00:17:44.965 Of 720 00:17:45.115 --> 00:17:45.975 their mouse 721 00:17:46.156 --> 00:17:47.556 and it's missing a battery flap. 722 00:17:47.715 --> 00:17:48.836 If you've got a 3D printer, 723 00:17:49.036 --> 00:17:52.036 you can probably 3D print a replacement pack. 724 00:17:52.145 --> 00:17:54.416 Do we have any additional questions? 725 00:17:54.635 --> 00:17:54.715 Oh, 726 00:17:54.755 --> 00:17:55.586 I might have missed some, 727 00:17:55.755 --> 00:17:56.995 but it looks like they're, 728 00:17:57.326 --> 00:17:58.176 they're being re-asked. 729 00:17:58.355 --> 00:17:58.696 Got it. 730 00:17:59.105 --> 00:17:59.235 It says, 731 00:17:59.276 --> 00:18:00.735 what's your favourite factory game type? 732 00:18:01.156 --> 00:18:02.475 It has to have conveyor belts. 733 00:18:02.676 --> 00:18:03.595 It has to have belts. 734 00:18:03.635 --> 00:18:04.355 If it doesn't have belts, 735 00:18:04.395 --> 00:18:05.316 I'm not really interested. 736 00:18:05.640 --> 00:18:09.180 I actually run a uh Steam um curator page 737 00:18:09.319 --> 00:18:10.760 uh called conveyor belts, 738 00:18:11.079 --> 00:18:13.140 where we only list games 739 00:18:13.439 --> 00:18:13.939 uh 740 00:18:14.079 --> 00:18:15.060 that have conveyor belts. 741 00:18:16.160 --> 00:18:19.560 If you uh scream at me that a game that has conveyor belts does, 742 00:18:19.640 --> 00:18:20.599 is not on that list, 743 00:18:20.640 --> 00:18:21.040 let me know, 744 00:18:21.160 --> 00:18:21.900 I will add it, 745 00:18:22.160 --> 00:18:22.569 um, 746 00:18:22.680 --> 00:18:23.900 cos I've probably played it. 747 00:18:24.079 --> 00:18:26.219 All the review does is it says, 748 00:18:26.800 --> 00:18:29.219 does it have conveyor belts and how good are the conveyor belts? 749 00:18:29.540 --> 00:18:29.859 That's it, 750 00:18:29.930 --> 00:18:31.699 the only thing that that curator paid you. 751 00:18:31.819 --> 00:18:31.930 Oh, 752 00:18:31.979 --> 00:18:32.739 and then Cyte says, 753 00:18:32.780 --> 00:18:35.890 is there an ATA on when Resonite may get a mobile client? 754 00:18:36.099 --> 00:18:36.300 Um, 755 00:18:36.380 --> 00:18:38.280 having a mobile client would probably be, 756 00:18:38.290 --> 00:18:38.569 uh, 757 00:18:38.579 --> 00:18:39.479 a lot later than, 758 00:18:39.530 --> 00:18:40.589 than many other things, 759 00:18:40.660 --> 00:18:41.699 we don't really get an ETA, 760 00:18:41.780 --> 00:18:42.760 but I wouldn't expect, 761 00:18:43.060 --> 00:18:43.400 uh, 762 00:18:43.420 --> 00:18:44.439 any news. 763 00:18:44.619 --> 00:18:45.060 This isn't, 764 00:18:45.140 --> 00:18:46.260 I wouldn't expect it, 765 00:18:46.339 --> 00:18:46.510 right? 766 00:18:46.619 --> 00:18:49.800 I wouldn't expect any news on a mobile client this year. 767 00:18:50.140 --> 00:18:51.780 And uh just being honest, 768 00:18:51.819 --> 00:18:54.199 I probably wouldn't expect any news on it next year. 769 00:18:54.449 --> 00:18:57.040 For us to like really look at mobile again, 770 00:18:57.339 --> 00:18:58.380 we need to get 771 00:18:58.579 --> 00:18:59.839 the new renderer done 772 00:19:00.109 --> 00:19:01.199 uh cos 773 00:19:01.500 --> 00:19:03.280 otherwise we would have to 774 00:19:03.579 --> 00:19:05.880 uh contend with getting Unity 775 00:19:06.089 --> 00:19:07.719 to run on a phone. 776 00:19:07.930 --> 00:19:08.979 Uh additionally, 777 00:19:09.060 --> 00:19:14.199 I do not know if we will be able to do the multiprocessor architecture the same way 778 00:19:14.339 --> 00:19:15.180 on a mobile phone, 779 00:19:15.219 --> 00:19:15.939 it might have to be like. 780 00:19:16.469 --> 00:19:17.530 Somehow different, 781 00:19:17.790 --> 00:19:19.119 so that would also be a factor. 782 00:19:19.310 --> 00:19:21.359 Do we have additional questions? 783 00:19:21.550 --> 00:19:21.910 All right, 784 00:19:22.150 --> 00:19:24.170 seeing as things are winding down naturally, 785 00:19:24.390 --> 00:19:26.109 I'm gonna go ahead and leave things off 786 00:19:26.109 --> 00:19:28.010 here and then immediately save the recording. 787 00:19:28.270 --> 00:19:29.650 As mentioned in office hours 788 00:19:30.030 --> 00:19:30.270 updates, 789 00:19:30.349 --> 00:19:32.010 I'm looking into 790 00:19:32.310 --> 00:19:35.790 uh doing a like public working session of just all 791 00:19:35.790 --> 00:19:37.900 the things I keep putting off at office hours. 792 00:19:38.109 --> 00:19:39.910 I was gonna do that straight after this, 793 00:19:40.030 --> 00:19:40.589 but like that's, 794 00:19:40.630 --> 00:19:41.810 that's never really ideal. 795 00:19:42.290 --> 00:19:42.630 Uh, 796 00:19:42.689 --> 00:19:47.290 so what I'm gonna do instead is I'm gonna go do a bunch of research into Core OS, 797 00:19:47.609 --> 00:19:48.170 uh, 798 00:19:48.530 --> 00:19:49.310 and, 799 00:19:49.369 --> 00:19:50.050 uh, 800 00:19:50.250 --> 00:19:52.140 rethink how I did everything 801 00:19:52.329 --> 00:19:54.119 that I was handling over in, 802 00:19:54.160 --> 00:19:54.630 uh, 803 00:19:54.729 --> 00:19:55.790 copper versus 804 00:19:55.969 --> 00:19:56.430 tariff. 805 00:19:56.650 --> 00:19:56.719 Oh, 806 00:19:56.770 --> 00:19:57.949 I'm voluntarily 807 00:19:58.170 --> 00:19:58.410 jumping. 808 00:19:58.489 --> 00:19:59.329 Into this rabbit hole, 809 00:19:59.410 --> 00:19:59.680 right, 810 00:19:59.969 --> 00:20:02.089 I have to first of all figure out if we can even 811 00:20:02.369 --> 00:20:05.550 like spin up Co OS on an Azure VM without like 812 00:20:05.650 --> 00:20:05.920 upload, 813 00:20:06.000 --> 00:20:06.160 I, 814 00:20:06.290 --> 00:20:07.810 I ain't uploading the ISO or anything. 815 00:20:07.890 --> 00:20:08.449 I think we can, 816 00:20:08.489 --> 00:20:09.290 I saw a document. 817 00:20:09.489 --> 00:20:10.750 I will be back 818 00:20:10.920 --> 00:20:11.670 next week 819 00:20:11.969 --> 00:20:12.969 again at prime time. 820 00:20:13.150 --> 00:20:13.709 Until then, 821 00:20:14.050 --> 00:20:14.609 bye bye.