WEBVTT 0 00:00:00.039 --> 00:00:00.319 Anyway, 1 00:00:00.370 --> 00:00:00.639 we'll, 2 00:00:00.730 --> 00:00:01.409 we'll let that run. 3 00:00:01.529 --> 00:00:01.830 Um, 4 00:00:01.929 --> 00:00:04.239 I don't know where I put the old recording cos they want me to stop. 5 00:00:04.920 --> 00:00:04.940 Uh oh, 6 00:00:06.050 --> 00:00:06.590 where are we? 7 00:00:06.699 --> 00:00:08.649 I in here and here. 8 00:00:08.960 --> 00:00:09.449 OK, 9 00:00:09.529 --> 00:00:10.050 here we go. 10 00:00:10.289 --> 00:00:10.640 Uh, 11 00:00:10.770 --> 00:00:11.149 so 12 00:00:11.810 --> 00:00:12.489 to office hours, 13 00:00:12.609 --> 00:00:14.479 sorry for the delays and everything. 14 00:00:14.770 --> 00:00:16.370 Promise I'm trying to get more automation going. 15 00:00:16.549 --> 00:00:19.319 Here it's just like uh I've been trying to fix a problem uh 16 00:00:19.479 --> 00:00:19.920 um 17 00:00:20.069 --> 00:00:21.569 the corporate stuff for many, 18 00:00:21.600 --> 00:00:22.299 many weeks 19 00:00:22.520 --> 00:00:26.760 and I just like keep hammering away at it and it keeps not being so we go. 20 00:00:26.840 --> 00:00:30.379 I need to like search primetime dash and then 2026. 21 00:00:30.559 --> 00:00:31.280 Where are they? 22 00:00:31.360 --> 00:00:32.400 They should be on my desktop. 23 00:00:32.439 --> 00:00:32.750 I didn't 24 00:00:33.459 --> 00:00:35.060 apparently I accidentally deleted them. 25 00:00:35.389 --> 00:00:35.880 Uh, 26 00:00:35.889 --> 00:00:38.560 they are in recycle bins so I can just go ahead and restore them. 27 00:00:38.720 --> 00:00:39.159 What happened? 28 00:00:39.360 --> 00:00:41.479 I must have been like smoking some stuff or something. 29 00:00:41.599 --> 00:00:41.979 OK, 30 00:00:42.400 --> 00:00:43.150 um, 31 00:00:43.479 --> 00:00:44.240 so with all that done. 32 00:00:44.580 --> 00:00:44.860 Uh, 33 00:00:44.939 --> 00:00:48.049 are you planning to add a toggle to remove April Fool's events for business clients? 34 00:00:48.069 --> 00:00:48.860 It won't be a toggle, 35 00:00:48.900 --> 00:00:49.490 it'll be like a, 36 00:00:49.540 --> 00:00:50.529 a manual process. 37 00:00:50.619 --> 00:00:51.060 Basically, 38 00:00:51.099 --> 00:00:51.979 April Fools is, 39 00:00:52.020 --> 00:00:53.919 is driven by an engine property. 40 00:00:54.139 --> 00:00:55.380 I don't know what exactly it is, 41 00:00:55.459 --> 00:00:57.959 but it's something like engine is April Fools or something. 42 00:00:58.259 --> 00:01:02.060 And right now that is like due date maths is at April 1st, 43 00:01:02.209 --> 00:01:02.459 but what that. 44 00:01:02.755 --> 00:01:03.224 B is 45 00:01:03.404 --> 00:01:04.235 due date maths, 46 00:01:04.245 --> 00:01:05.385 is it April 1st 47 00:01:05.644 --> 00:01:06.264 and 48 00:01:06.644 --> 00:01:08.815 not in uh engine in universe, 49 00:01:09.084 --> 00:01:10.644 which is uh 50 00:01:10.885 --> 00:01:13.404 like a property which indicates if something is in a universe. 51 00:01:13.485 --> 00:01:15.574 Just tag that with like member not null as well. 52 00:01:15.894 --> 00:01:16.775 Member not nulls is, 53 00:01:16.785 --> 00:01:17.684 is really where are we? 54 00:01:17.885 --> 00:01:18.535 Member 55 00:01:18.764 --> 00:01:19.745 not null when, 56 00:01:19.925 --> 00:01:20.485 um. 57 00:01:21.209 --> 00:01:21.489 Mr. 58 00:01:21.510 --> 00:01:23.639 Cyro helped me understand this, 59 00:01:23.839 --> 00:01:24.529 uh, 60 00:01:24.790 --> 00:01:25.180 but 61 00:01:25.349 --> 00:01:26.550 what I can do 62 00:01:26.690 --> 00:01:27.910 is I can tag 63 00:01:28.290 --> 00:01:29.190 in universe, 64 00:01:29.769 --> 00:01:29.870 no, 65 00:01:29.930 --> 00:01:31.410 I can tag engine.universe, 66 00:01:31.489 --> 00:01:32.930 which is the universe that you're in, 67 00:01:33.129 --> 00:01:33.589 with 68 00:01:33.809 --> 00:01:35.410 member not null when, 69 00:01:35.569 --> 00:01:36.110 uh, 70 00:01:36.449 --> 00:01:37.559 in universe true, 71 00:01:37.650 --> 00:01:39.830 and then it will prevent a bunch of like 72 00:01:40.010 --> 00:01:40.919 universe null. 73 00:01:41.129 --> 00:01:41.519 Anyway, 74 00:01:41.680 --> 00:01:42.269 there we go. 75 00:01:42.480 --> 00:01:43.930 I do still plan to do that, 76 00:01:43.989 --> 00:01:45.989 it's not going to make tomorrow though. 77 00:01:46.250 --> 00:01:46.970 Um, 78 00:01:47.330 --> 00:01:48.430 most of the people 79 00:01:48.809 --> 00:01:49.569 involved at. 80 00:01:49.692 --> 00:01:52.751 The corporate client are on vacation so we're probably good, 81 00:01:52.972 --> 00:01:53.321 um, 82 00:01:53.372 --> 00:01:54.762 but I don't wanna lose momentum, 83 00:01:54.931 --> 00:01:55.132 right, 84 00:01:55.211 --> 00:01:55.491 you know, 85 00:01:55.531 --> 00:01:56.781 it was like a weird countdown, 86 00:01:56.872 --> 00:01:57.952 so I will do it this week, 87 00:01:58.171 --> 00:01:58.811 but it won't be, 88 00:01:59.891 --> 00:02:00.192 uh, 89 00:02:00.211 --> 00:02:00.811 cos like if I, 90 00:02:00.851 --> 00:02:01.531 if I delay it, 91 00:02:01.571 --> 00:02:04.232 it'll be this time next year and I'll be like fuck I didn't do it again. 92 00:02:04.442 --> 00:02:04.692 So I, 93 00:02:04.762 --> 00:02:05.251 I have to, 94 00:02:05.332 --> 00:02:05.912 I have to do it, 95 00:02:05.972 --> 00:02:06.431 otherwise, 96 00:02:06.611 --> 00:02:06.802 uh, 97 00:02:06.811 --> 00:02:07.192 I'm gonna. 98 00:02:07.531 --> 00:02:08.731 I guess I could just do it right now. 99 00:02:08.890 --> 00:02:10.852 Let's do it right now whilst we wait for some questions. 100 00:02:11.011 --> 00:02:11.572 How about that? 101 00:02:11.692 --> 00:02:12.701 I won't release it to them, 102 00:02:12.731 --> 00:02:13.671 like I wouldn't do that 103 00:02:13.802 --> 00:02:14.912 this close to 104 00:02:15.091 --> 00:02:16.052 the date and like I said, 105 00:02:16.091 --> 00:02:16.871 they're all on vacation, 106 00:02:17.052 --> 00:02:17.671 but there we go. 107 00:02:17.891 --> 00:02:18.332 cos they're giant. 108 00:02:18.643 --> 00:02:19.533 Corporate client, 109 00:02:19.694 --> 00:02:21.393 they've got like a common 110 00:02:21.854 --> 00:02:24.113 software delivery mechanism. 111 00:02:24.494 --> 00:02:26.733 It's common in corporate IT whereby like, 112 00:02:26.934 --> 00:02:27.134 you know, 113 00:02:27.214 --> 00:02:27.634 maybe 114 00:02:28.194 --> 00:02:28.554 like 115 00:02:28.854 --> 00:02:32.934 Softpedia or all those other like weird janky download websites are blocked, 116 00:02:32.973 --> 00:02:33.134 right, 117 00:02:33.173 --> 00:02:35.253 for good reason cos they're mostly full of viruses. 118 00:02:35.453 --> 00:02:36.753 But like if you want an application, 119 00:02:37.283 --> 00:02:38.533 you can go to like the 120 00:02:38.774 --> 00:02:39.634 uh corporate 121 00:02:40.134 --> 00:02:41.354 software like 122 00:02:41.554 --> 00:02:42.514 distribution 123 00:02:42.854 --> 00:02:43.774 UI somewhere, 124 00:02:43.813 --> 00:02:46.873 like it's usually like a desktop application or maybe it's like a website. 125 00:02:47.285 --> 00:02:51.046 And it lists like validated and approved applications and in 126 00:02:51.046 --> 00:02:52.886 some cases depending on like how cool it is, 127 00:02:52.936 --> 00:02:54.055 it will also keep them up to date. 128 00:02:54.255 --> 00:02:57.115 So it's like a business steam but for more than just games. 129 00:02:57.216 --> 00:02:58.235 And we wanna get 130 00:02:58.496 --> 00:03:00.395 um resona into that 131 00:03:00.496 --> 00:03:02.475 and being automatically delivered from, 132 00:03:02.535 --> 00:03:03.636 from CI as well. 133 00:03:03.735 --> 00:03:03.916 um, 134 00:03:03.936 --> 00:03:06.195 but right now I basically email them a zip 135 00:03:06.195 --> 00:03:08.916 and then they have to like slowly distribute it around 136 00:03:09.136 --> 00:03:10.475 so it wouldn't make it any. 137 00:03:10.615 --> 00:03:11.276 Uh 138 00:03:11.535 --> 00:03:11.776 OK, 139 00:03:12.016 --> 00:03:13.345 control April's. 140 00:03:13.615 --> 00:03:14.235 There is one 141 00:03:14.936 --> 00:03:15.856 L in April. 142 00:03:17.089 --> 00:03:17.600 If 143 00:03:18.429 --> 00:03:18.449 engine, 144 00:03:18.669 --> 00:03:19.990 so we don't need to engine cos we're in the engine. 145 00:03:20.089 --> 00:03:20.509 If in 146 00:03:21.250 --> 00:03:21.679 uh I, 147 00:03:22.410 --> 00:03:22.580 yeah, 148 00:03:22.729 --> 00:03:24.130 public ball in universe. 149 00:03:24.289 --> 00:03:24.449 Oh, 150 00:03:24.490 --> 00:03:27.500 it's not static and is April Fools is static. 151 00:03:27.690 --> 00:03:29.889 I guess we can do engine not current for the singleton. 152 00:03:30.089 --> 00:03:32.050 Engine not current in universe 153 00:03:32.610 --> 00:03:33.559 return false. 154 00:03:33.850 --> 00:03:34.479 Here you go. 155 00:03:34.770 --> 00:03:36.630 Here's how you turn off April Fool's mode 156 00:03:36.770 --> 00:03:37.449 for the corporates. 157 00:03:37.490 --> 00:03:38.770 It is two lines of code, 158 00:03:38.889 --> 00:03:39.429 ideally, 159 00:03:39.449 --> 00:03:40.369 like it could be one. 160 00:03:41.130 --> 00:03:42.440 Could be one like the uh 161 00:03:42.740 --> 00:03:44.250 enter an indentation there is, 162 00:03:44.259 --> 00:03:44.460 is, 163 00:03:44.500 --> 00:03:45.380 is not needed, 164 00:03:45.470 --> 00:03:45.979 but you know, 165 00:03:46.300 --> 00:03:46.820 two lines. 166 00:03:47.020 --> 00:03:47.339 Uh, 167 00:03:47.380 --> 00:03:48.039 so let's just 168 00:03:48.220 --> 00:03:48.619 check the 169 00:03:48.770 --> 00:03:49.419 error list. 170 00:03:49.619 --> 00:03:49.699 Yeah, 171 00:03:49.779 --> 00:03:50.139 that's fine. 172 00:03:50.240 --> 00:03:50.460 OK, 173 00:03:50.539 --> 00:03:52.850 so I can just literally shove that up to, 174 00:03:53.020 --> 00:03:55.619 up to their branch and it falls first. 175 00:03:55.979 --> 00:03:56.229 OK, 176 00:03:56.300 --> 00:03:56.940 it's fixed. 177 00:03:57.020 --> 00:03:59.059 It's not like in their hands, 178 00:03:59.380 --> 00:03:59.660 but it's, 179 00:03:59.699 --> 00:04:01.360 it's in the commit chain. 180 00:04:01.419 --> 00:04:03.179 It's in the commit chain, 181 00:04:03.220 --> 00:04:03.660 OK? 182 00:04:03.779 --> 00:04:04.139 It's in. 183 00:04:04.895 --> 00:04:04.914 In the, 184 00:04:05.595 --> 00:04:05.884 like 185 00:04:06.035 --> 00:04:07.854 the next build I publish for them 186 00:04:08.115 --> 00:04:09.134 will not have, 187 00:04:09.195 --> 00:04:09.804 uh, 188 00:04:10.074 --> 00:04:10.315 uh, 189 00:04:10.395 --> 00:04:10.895 will not have 190 00:04:11.225 --> 00:04:13.595 computers it says current activity of canine companion. 191 00:04:13.714 --> 00:04:13.955 Um, 192 00:04:14.065 --> 00:04:15.654 they're in their bark at the door mode. 193 00:04:15.835 --> 00:04:16.255 Um, 194 00:04:16.515 --> 00:04:16.644 uh, 195 00:04:16.673 --> 00:04:17.825 that's why I shut the baby gate, 196 00:04:17.954 --> 00:04:19.834 but they are sat on one of their beds. 197 00:04:19.915 --> 00:04:21.595 They've got like 2 or 3 at this point, 198 00:04:21.834 --> 00:04:22.375 um, 199 00:04:22.915 --> 00:04:24.154 staring at the baby gate, 200 00:04:24.234 --> 00:04:24.554 um, 201 00:04:24.674 --> 00:04:25.695 intermittently barking. 202 00:04:25.915 --> 00:04:26.894 They also don't like, 203 00:04:26.915 --> 00:04:27.355 um. 204 00:04:27.690 --> 00:04:30.040 I swapped to a new dog food. 205 00:04:30.250 --> 00:04:32.329 I usually do like a delivered food, 206 00:04:32.410 --> 00:04:36.070 but I'm moving soon and I didn't want there to be like an overlap of just like. 207 00:04:37.079 --> 00:04:38.829 A giant box of 208 00:04:39.010 --> 00:04:39.690 uh 209 00:04:40.100 --> 00:04:41.119 of frozen dog food, 210 00:04:41.250 --> 00:04:42.149 particularly when I'm moving. 211 00:04:42.570 --> 00:04:43.799 So I cancelled that and I'm like, 212 00:04:43.809 --> 00:04:44.089 we'll go, 213 00:04:44.209 --> 00:04:46.559 we'll go dry food until I've moved and then, 214 00:04:46.600 --> 00:04:46.730 you know, 215 00:04:46.809 --> 00:04:48.170 we'll go back to whatever we go from, 216 00:04:48.250 --> 00:04:49.739 from now after relook at prices. 217 00:04:49.970 --> 00:04:54.850 And so I bought like a 18 pound bag of dry dog food that he's previously liked, 218 00:04:55.049 --> 00:04:56.190 but he doesn't like it 219 00:04:56.329 --> 00:04:56.970 and 220 00:04:57.250 --> 00:04:58.179 so he's not eating, 221 00:04:58.410 --> 00:04:59.049 but I'm like, 222 00:04:59.100 --> 00:05:01.480 does he not like it because he doesn't like it or does he 223 00:05:01.480 --> 00:05:03.690 not like it because there's a problem with his teeth because he. 224 00:05:03.790 --> 00:05:04.670 He has a softer, 225 00:05:05.070 --> 00:05:07.970 so I'm gonna book him into the vet whenever I remember, 226 00:05:08.230 --> 00:05:08.489 uh, 227 00:05:08.510 --> 00:05:08.750 to. 228 00:05:08.869 --> 00:05:09.950 It's meant to be booked in today, 229 00:05:10.029 --> 00:05:10.670 maybe I could do that, 230 00:05:10.709 --> 00:05:11.660 it's already 4 though. 231 00:05:12.029 --> 00:05:12.630 Uh, 232 00:05:12.950 --> 00:05:13.829 just book him into the vet, 233 00:05:13.950 --> 00:05:14.420 be like, 234 00:05:14.579 --> 00:05:14.899 yo, 235 00:05:14.989 --> 00:05:15.290 hey, 236 00:05:15.510 --> 00:05:15.859 you know, 237 00:05:16.149 --> 00:05:17.209 double check his teeth. 238 00:05:17.309 --> 00:05:17.470 Um, 239 00:05:17.510 --> 00:05:18.510 he also might need some, 240 00:05:18.630 --> 00:05:19.589 some vaccinations. 241 00:05:19.709 --> 00:05:21.109 I've got a trip coming up, 242 00:05:21.190 --> 00:05:21.950 a travel trip, 243 00:05:22.059 --> 00:05:23.510 and he's gonna need to be boarded, 244 00:05:23.630 --> 00:05:24.070 so I've gotta, 245 00:05:24.149 --> 00:05:25.589 I've gotta check up on his, 246 00:05:25.670 --> 00:05:27.329 his vaccinations anyway. 247 00:05:27.540 --> 00:05:27.739 Um, 248 00:05:27.790 --> 00:05:28.149 if they're like, 249 00:05:28.230 --> 00:05:28.309 hey, 250 00:05:28.390 --> 00:05:29.380 his teeth are fine, 251 00:05:29.790 --> 00:05:30.369 then, 252 00:05:30.429 --> 00:05:30.670 um. 253 00:05:30.769 --> 00:05:30.929 Um, 254 00:05:31.130 --> 00:05:31.709 I will 255 00:05:31.970 --> 00:05:33.589 probably just like 256 00:05:33.809 --> 00:05:37.790 get like a smaller bag of a variety of dog foods and to try, 257 00:05:38.079 --> 00:05:38.350 um, 258 00:05:38.359 --> 00:05:43.329 and donate the rest of this 18 pound dog bag to a rescue organisation which visits 259 00:05:43.329 --> 00:05:46.609 the pet store around the corner to do an adoption event about once a quarter. 260 00:05:46.809 --> 00:05:47.079 I'll be like, 261 00:05:47.130 --> 00:05:47.329 hey, 262 00:05:47.450 --> 00:05:48.450 my dog hates this food. 263 00:05:48.529 --> 00:05:48.929 Here's like, 264 00:05:49.040 --> 00:05:49.369 I don't know, 265 00:05:49.649 --> 00:05:52.130 17.5 pounds of dog food. 266 00:05:52.410 --> 00:05:55.089 He will eventually eat it causes like hunger takes place 267 00:05:55.089 --> 00:05:57.649 and I've also had some mixed success with uh dumping. 268 00:05:57.940 --> 00:05:59.049 In like a cup of water 269 00:05:59.470 --> 00:06:00.010 onto 270 00:06:00.230 --> 00:06:00.589 the food, 271 00:06:00.670 --> 00:06:02.989 which like makes it moist and smell a bit better. 272 00:06:03.350 --> 00:06:04.010 There we go. 273 00:06:04.230 --> 00:06:04.950 Um, 274 00:06:05.190 --> 00:06:07.869 I missed a question from Fusa about something else. 275 00:06:07.950 --> 00:06:08.510 Uh, 276 00:06:08.750 --> 00:06:10.739 I'm enjoying the current cheese theme of April Fools. 277 00:06:10.760 --> 00:06:11.769 I believe it's only, 278 00:06:11.910 --> 00:06:12.299 um, 279 00:06:12.309 --> 00:06:13.290 an excellent event, 280 00:06:13.390 --> 00:06:13.739 um, 281 00:06:13.750 --> 00:06:14.399 in Resmonic, 282 00:06:14.459 --> 00:06:14.779 which is, 283 00:06:14.829 --> 00:06:15.549 is cheese. 284 00:06:15.709 --> 00:06:17.049 I am aware of what 285 00:06:17.269 --> 00:06:19.390 ressonite's gonna do tomorrow for April Fools. 286 00:06:19.470 --> 00:06:20.190 I cannot tell you, 287 00:06:20.309 --> 00:06:21.170 but I'm aware, 288 00:06:21.309 --> 00:06:21.829 um, 289 00:06:21.989 --> 00:06:23.029 it is not cheese related. 290 00:06:23.149 --> 00:06:23.429 But yes, 291 00:06:23.529 --> 00:06:24.630 I'm always happy to see. 292 00:06:24.829 --> 00:06:25.299 Cheese related item. 293 00:06:25.649 --> 00:06:28.649 We talk about this every year as well when it comes to 294 00:06:28.809 --> 00:06:29.440 um 295 00:06:29.589 --> 00:06:30.730 like April Fools, 296 00:06:30.850 --> 00:06:34.809 but like Frukes is happy for like other engineers to 297 00:06:35.049 --> 00:06:36.160 uh well it's like, 298 00:06:36.209 --> 00:06:36.329 you know, 299 00:06:36.369 --> 00:06:40.190 the Dogman Studios event but like it's uh you know uh the event 300 00:06:40.369 --> 00:06:44.010 is like Nexcellon's responsibility and then the code changes for the 301 00:06:44.010 --> 00:06:46.269 engine are Fruke's responsibility and as I was just saying, 302 00:06:46.329 --> 00:06:46.709 um, 303 00:06:46.730 --> 00:06:48.089 Frukes is open to 304 00:06:48.329 --> 00:06:49.709 other engineers submitting, 305 00:06:49.970 --> 00:06:50.399 um, 306 00:06:50.609 --> 00:06:51.649 April Fool's content. 307 00:06:51.980 --> 00:06:52.600 That doesn't 308 00:06:52.769 --> 00:06:55.769 tend to work out in my brain though because 309 00:06:56.070 --> 00:06:57.279 usually 310 00:06:57.619 --> 00:06:58.320 um 311 00:06:58.579 --> 00:06:58.809 you know, 312 00:06:58.859 --> 00:07:01.220 we need code reviews and things like that and I, 313 00:07:01.260 --> 00:07:01.859 I kind of just, 314 00:07:01.940 --> 00:07:03.899 I don't want meme content being code reviewed 315 00:07:03.899 --> 00:07:05.920 cos it's very difficult to write anyway. 316 00:07:06.420 --> 00:07:07.109 It's like, 317 00:07:07.459 --> 00:07:07.820 hey, 318 00:07:08.059 --> 00:07:10.880 she didn't use the most optimal and idiomatic 319 00:07:11.100 --> 00:07:11.839 open 320 00:07:12.299 --> 00:07:13.579 object orientated 321 00:07:13.980 --> 00:07:18.019 public static void made string arg's version of whatever 322 00:07:18.019 --> 00:07:20.600 the hell this is to like make everyone fart 323 00:07:20.850 --> 00:07:21.380 on the hour, 324 00:07:21.459 --> 00:07:22.140 every hour. 325 00:07:22.459 --> 00:07:25.519 That and it's kind of been beaten into me from 326 00:07:25.660 --> 00:07:28.760 uh my Microsoft days that like I kind of just don't do April. 327 00:07:28.980 --> 00:07:29.660 For those who aren'taware, 328 00:07:29.739 --> 00:07:33.279 Microsoft and therefore any product under their umbrella including. 329 00:07:33.519 --> 00:07:33.809 Box, 330 00:07:33.929 --> 00:07:34.279 um, 331 00:07:34.410 --> 00:07:35.040 and listen it now, 332 00:07:35.049 --> 00:07:35.450 I guess, 333 00:07:35.730 --> 00:07:37.679 are not allowed to do April Fools. 334 00:07:37.809 --> 00:07:39.309 It is a directive from 335 00:07:39.609 --> 00:07:39.989 the 336 00:07:40.369 --> 00:07:40.750 chief 337 00:07:40.970 --> 00:07:43.510 legal officer of Microsoft. 338 00:07:43.730 --> 00:07:45.480 I think one of the problems with April Fools 339 00:07:45.480 --> 00:07:47.510 as well when you get to a company that large 340 00:07:47.779 --> 00:07:49.829 is that it's very difficult 341 00:07:49.970 --> 00:07:52.230 for everyone to understand 342 00:07:52.489 --> 00:07:54.549 that it is a, 343 00:07:54.769 --> 00:07:55.160 a joke, 344 00:07:55.290 --> 00:07:55.679 right? 345 00:07:55.890 --> 00:07:59.329 Let's say like 80% of people understand that it's a joke, 346 00:07:59.410 --> 00:08:00.390 like whatever you do. 347 00:08:00.700 --> 00:08:02.230 The 20% who don't 348 00:08:02.549 --> 00:08:03.910 might not buy anything that day, 349 00:08:04.059 --> 00:08:07.380 and so you've still got like a 20% decrease in sales for a day, 350 00:08:07.390 --> 00:08:09.750 and that's like unacceptable to most businesses. 351 00:08:09.989 --> 00:08:10.390 Moving forward, 352 00:08:10.459 --> 00:08:11.709 skipping over the April Fool's question, 353 00:08:11.790 --> 00:08:12.529 I know exactly 354 00:08:12.910 --> 00:08:14.179 what's in the April Fool's update, 355 00:08:14.429 --> 00:08:15.730 like down to the latter, 356 00:08:15.790 --> 00:08:17.089 I was reading the commits last night, 357 00:08:17.470 --> 00:08:18.290 but I can't tell you. 358 00:08:18.489 --> 00:08:18.890 Um, 359 00:08:19.309 --> 00:08:19.950 moving forwards, 360 00:08:20.070 --> 00:08:20.200 Hecker, 361 00:08:20.790 --> 00:08:23.399 how much did the death of Resi of Resi, 362 00:08:24.010 --> 00:08:24.980 at least I didn't say Rizzi, 363 00:08:25.380 --> 00:08:27.390 how much did the death of Rizzi Player be, 364 00:08:27.630 --> 00:08:27.790 uh, 365 00:08:27.910 --> 00:08:28.570 Ready Player B. 366 00:08:28.730 --> 00:08:30.640 Affect the provision of business for any normal humans, 367 00:08:30.691 --> 00:08:30.960 uh, 368 00:08:30.990 --> 00:08:31.351 that 369 00:08:31.621 --> 00:08:33.241 went by the wayside for a bit. 370 00:08:33.570 --> 00:08:35.551 Lots of times the corporate client will, 371 00:08:35.791 --> 00:08:36.341 um, 372 00:08:36.650 --> 00:08:38.291 shove stuff over our way and be like, 373 00:08:38.370 --> 00:08:39.640 could you theoretically do this? 374 00:08:39.690 --> 00:08:40.080 And we're like, 375 00:08:40.130 --> 00:08:40.309 yeah, 376 00:08:40.491 --> 00:08:40.991 sure. 377 00:08:41.171 --> 00:08:41.809 Um, 378 00:08:42.010 --> 00:08:43.690 but they never actually ask us to do it. 379 00:08:43.971 --> 00:08:46.370 So like it goes on my list and I think about it 380 00:08:46.611 --> 00:08:47.231 and, 381 00:08:47.250 --> 00:08:47.810 uh, 382 00:08:47.841 --> 00:08:47.971 you know, 383 00:08:48.051 --> 00:08:48.960 then it doesn't happen. 384 00:08:49.161 --> 00:08:49.731 Right now in, 385 00:08:49.770 --> 00:08:50.401 in corporate land, 386 00:08:50.411 --> 00:08:51.471 I've actually got a break 387 00:08:51.611 --> 00:08:54.231 and for anyone who knows corporate internet security, 388 00:08:54.411 --> 00:08:54.731 uh, 389 00:08:54.741 --> 00:08:55.991 you're about to like love it, 390 00:08:56.051 --> 00:08:56.351 OK, 391 00:08:56.531 --> 00:08:56.690 so. 392 00:08:57.671 --> 00:08:59.452 We created a second copy 393 00:08:59.632 --> 00:09:02.012 of Resonate's cloud infrastructure 394 00:09:02.192 --> 00:09:05.952 with inside their cloud infrastructure in Azure. 395 00:09:06.151 --> 00:09:06.502 Um, 396 00:09:06.581 --> 00:09:09.411 the way that that's been done is using what's called a hub and spoke model. 397 00:09:09.632 --> 00:09:10.151 So, 398 00:09:10.312 --> 00:09:10.591 uh, 399 00:09:10.711 --> 00:09:13.072 there is network isolation between the rest 400 00:09:13.072 --> 00:09:16.021 of corporate's products and our corporate products, 401 00:09:16.072 --> 00:09:17.372 but they're still under the same, 402 00:09:17.432 --> 00:09:17.591 like, 403 00:09:17.622 --> 00:09:18.632 overall wheel, 404 00:09:18.831 --> 00:09:19.731 which means that 405 00:09:19.872 --> 00:09:22.791 the corporate client is paying for the Azure resources and not me. 406 00:09:22.911 --> 00:09:22.992 Oh, 407 00:09:23.111 --> 00:09:23.151 yeah, 408 00:09:23.262 --> 00:09:24.211 they're my studios. 409 00:09:24.471 --> 00:09:26.672 But they're also Means that there's a bunch of security involved, 410 00:09:26.853 --> 00:09:27.632 such that I 411 00:09:27.833 --> 00:09:29.393 don't understand 412 00:09:29.572 --> 00:09:32.953 the network topology of everything that I have deployed. 413 00:09:33.213 --> 00:09:35.293 Now we were OK for things like the API, 414 00:09:35.453 --> 00:09:36.973 the asset worker, 415 00:09:37.093 --> 00:09:37.442 um, 416 00:09:37.533 --> 00:09:38.893 the account websites, 417 00:09:38.932 --> 00:09:39.093 you know, 418 00:09:39.172 --> 00:09:39.853 things like stats, 419 00:09:39.922 --> 00:09:40.482 messages, 420 00:09:40.562 --> 00:09:41.112 inventory, 421 00:09:41.252 --> 00:09:41.843 stuff like that, 422 00:09:42.093 --> 00:09:43.213 cos that's all HTTP. 423 00:09:43.492 --> 00:09:44.713 HTTP is like 424 00:09:45.093 --> 00:09:45.612 everyone like, 425 00:09:45.963 --> 00:09:45.992 whoa, 426 00:09:46.252 --> 00:09:46.413 you know, 427 00:09:46.533 --> 00:09:47.153 chef kiss, 428 00:09:47.562 --> 00:09:48.513 everyone knows HTTP. 429 00:09:48.732 --> 00:09:49.052 And yes, 430 00:09:49.093 --> 00:09:51.372 it's HTTPS but I just can't be bothered to say the yes, 431 00:09:51.453 --> 00:09:52.273 so just leave me alone, 432 00:09:52.533 --> 00:09:52.893 um. 433 00:09:53.383 --> 00:09:56.713 It's all HTTP so it's all like really easy to understand. 434 00:09:56.874 --> 00:09:58.533 Firewalls are built for it, 435 00:09:58.763 --> 00:09:59.174 uh, 436 00:09:59.193 --> 00:10:01.304 firewalls are built to handle it really well, 437 00:10:01.554 --> 00:10:02.273 so it just works. 438 00:10:02.354 --> 00:10:06.314 So the corporate cloud is up and running and you can connect via HTTP 439 00:10:06.554 --> 00:10:06.674 and, 440 00:10:06.693 --> 00:10:07.583 and get all your data, 441 00:10:07.633 --> 00:10:08.383 all your contacts, 442 00:10:08.424 --> 00:10:10.783 all your inventory stuff and register accounts and all of that. 443 00:10:10.833 --> 00:10:11.414 That's great. 444 00:10:11.633 --> 00:10:13.283 What what they also wanted was, 445 00:10:13.583 --> 00:10:16.513 let's stick a headless VM in the same subscription. 446 00:10:16.633 --> 00:10:16.953 And I'm like, 447 00:10:16.994 --> 00:10:17.633 this makes sense, 448 00:10:17.674 --> 00:10:18.914 we can have a headless VM, 449 00:10:19.153 --> 00:10:19.624 um, 450 00:10:20.033 --> 00:10:20.713 but to do that, 451 00:10:20.823 --> 00:10:22.575 I then Needed to orchestrate it in such a 452 00:10:22.575 --> 00:10:24.434 way where it could be what's called unattended. 453 00:10:24.655 --> 00:10:24.955 So, 454 00:10:25.215 --> 00:10:25.455 uh, 455 00:10:25.534 --> 00:10:26.275 what they want 456 00:10:26.414 --> 00:10:28.695 is like infrastructure as code standards, 457 00:10:28.755 --> 00:10:29.125 you know, 458 00:10:29.494 --> 00:10:32.565 no one has actual access to the like Azure subscription. 459 00:10:32.815 --> 00:10:35.125 Infrastructure as code is the one that has to provision it, 460 00:10:35.284 --> 00:10:37.114 which means I had to like write code 461 00:10:37.414 --> 00:10:39.205 to provision a headless VM 462 00:10:39.534 --> 00:10:40.525 without my hands, 463 00:10:40.655 --> 00:10:40.895 right? 464 00:10:41.015 --> 00:10:41.974 I can't use my hands. 465 00:10:42.015 --> 00:10:43.815 I have to just use words that I can type. 466 00:10:44.094 --> 00:10:44.375 Uh, 467 00:10:44.534 --> 00:10:44.955 so 468 00:10:45.255 --> 00:10:46.234 Terraform 469 00:10:46.474 --> 00:10:47.515 stands up the, 470 00:10:47.614 --> 00:10:48.085 the, 471 00:10:48.294 --> 00:10:49.034 the virtual machine. 472 00:10:49.549 --> 00:10:49.719 Uh, 473 00:10:49.799 --> 00:10:51.070 the virtual machine runs, 474 00:10:51.119 --> 00:10:51.400 um, 475 00:10:51.510 --> 00:10:53.270 a version of Linux called Flat Car Linux, 476 00:10:53.289 --> 00:10:56.880 which is an immutable OS similar to Fedora Core OS or Core OS. 477 00:10:57.400 --> 00:10:58.000 Um, 478 00:10:58.200 --> 00:10:59.020 I had to get that 479 00:10:59.559 --> 00:11:01.239 clear through security as well cause, 480 00:11:01.280 --> 00:11:01.479 uh, 481 00:11:01.549 --> 00:11:04.119 it's technically a third party marketplace image 482 00:11:04.400 --> 00:11:05.200 even though 483 00:11:06.260 --> 00:11:09.260 Azure stre Microsoft own the company that that that 484 00:11:09.260 --> 00:11:11.520 makes Flat Car and Flatcar is open source. 485 00:11:11.760 --> 00:11:14.229 I still had to open a security ticket for them to say like, 486 00:11:14.520 --> 00:11:14.719 yes, 487 00:11:14.799 --> 00:11:15.280 you can install. 488 00:11:15.512 --> 00:11:16.351 This third party, 489 00:11:16.432 --> 00:11:18.711 even though it's not a third party operating system, 490 00:11:19.031 --> 00:11:19.341 um, 491 00:11:19.512 --> 00:11:20.211 so I can include, 492 00:11:20.432 --> 00:11:20.591 you know, 493 00:11:20.781 --> 00:11:21.151 flat car, 494 00:11:21.271 --> 00:11:21.531 great. 495 00:11:21.762 --> 00:11:21.911 Now, 496 00:11:22.031 --> 00:11:22.812 flat car, 497 00:11:23.031 --> 00:11:23.911 it runs, 498 00:11:23.992 --> 00:11:24.611 um, 499 00:11:24.752 --> 00:11:28.492 this language called Ignition at start and it will 500 00:11:28.791 --> 00:11:30.872 spin up whatever the ignition tells it to do. 501 00:11:31.151 --> 00:11:32.072 But Ignition is adjacent, 502 00:11:32.192 --> 00:11:33.341 it's really difficult to write, 503 00:11:33.432 --> 00:11:35.552 so you actually write it in a language called butane. 504 00:11:35.822 --> 00:11:37.231 Now butane is just Yamal, 505 00:11:37.322 --> 00:11:37.872 it's very, 506 00:11:37.981 --> 00:11:38.192 very, 507 00:11:38.281 --> 00:11:39.531 very similar to, 508 00:11:39.591 --> 00:11:40.052 um, 509 00:11:40.062 --> 00:11:41.171 like how you might structure. 510 00:11:41.664 --> 00:11:44.963 Like a docker compose file or basically any other like YAL thing, 511 00:11:45.184 --> 00:11:45.453 um, 512 00:11:45.583 --> 00:11:47.104 so you write that as butane 513 00:11:47.223 --> 00:11:48.343 and then you 514 00:11:48.754 --> 00:11:50.164 transpire it to ignition, 515 00:11:50.263 --> 00:11:52.184 which is basically just like YAML to 516 00:11:52.463 --> 00:11:54.773 Jason with like a couple of like extras, 517 00:11:54.783 --> 00:11:55.064 right? 518 00:11:55.383 --> 00:11:57.263 And then you pass that to the machine and 519 00:11:57.263 --> 00:11:59.604 the machine uses that as instructions to build it, 520 00:11:59.804 --> 00:12:00.304 um, 521 00:12:00.463 --> 00:12:03.583 because it's an immutable OS it's not the same as like running commands on there, 522 00:12:03.624 --> 00:12:05.333 like it actually like makes changes, 523 00:12:05.343 --> 00:12:05.653 like it's, 524 00:12:05.703 --> 00:12:06.963 it's a bit com anyway. 525 00:12:07.416 --> 00:12:09.455 The uh ignition stroke butane, 526 00:12:09.575 --> 00:12:12.255 what that does is instals Docker and Docker composer, 527 00:12:12.335 --> 00:12:14.926 then starts a docker headless component uh instance. 528 00:12:15.495 --> 00:12:17.296 That all works and if you log into 529 00:12:17.296 --> 00:12:19.476 the corporate client's version of Resonite right now, 530 00:12:19.935 --> 00:12:22.366 you will see their test headless up and running, 531 00:12:22.656 --> 00:12:23.796 but no one can reach it. 532 00:12:23.976 --> 00:12:26.895 And the reason you can see it up and running is cos like the hi, 533 00:12:26.935 --> 00:12:27.635 I'm here, 534 00:12:27.895 --> 00:12:30.635 that's all HTTP but the actual connection to them 535 00:12:30.895 --> 00:12:33.216 is uh UDP over the LNL. 536 00:12:33.408 --> 00:12:33.828 Um, 537 00:12:34.088 --> 00:12:34.478 system. 538 00:12:34.687 --> 00:12:34.838 Now, 539 00:12:34.848 --> 00:12:36.028 the problem with that 540 00:12:36.288 --> 00:12:36.987 is that 541 00:12:37.247 --> 00:12:41.538 all corporate files are like ancient and they don't understand UDP. 542 00:12:41.817 --> 00:12:42.997 They barely understand TCP, 543 00:12:43.038 --> 00:12:43.247 but they, 544 00:12:43.328 --> 00:12:44.617 they don't understand UDP. 545 00:12:44.807 --> 00:12:45.148 Um, 546 00:12:45.367 --> 00:12:45.638 so yeah, 547 00:12:45.687 --> 00:12:46.468 I can't connect. 548 00:12:46.648 --> 00:12:47.197 And then everyone's like, 549 00:12:47.208 --> 00:12:47.357 oh, 550 00:12:47.408 --> 00:12:48.778 what about the bridge or the relay? 551 00:12:48.888 --> 00:12:48.958 No, 552 00:12:49.047 --> 00:12:49.117 no, 553 00:12:49.208 --> 00:12:49.607 no, 554 00:12:49.768 --> 00:12:50.507 I can't get 555 00:12:50.728 --> 00:12:52.237 any traffic to the VM, 556 00:12:52.367 --> 00:12:53.848 so bridge and relay won't fix it here. 557 00:12:54.007 --> 00:12:56.187 Like you do a trace route to the VM's IP, 558 00:12:56.328 --> 00:12:56.918 it doesn't, 559 00:12:57.168 --> 00:12:57.797 doesn't resolve. 560 00:12:57.848 --> 00:12:58.607 You do a ping to the, 561 00:12:58.687 --> 00:12:59.288 the headless. 562 00:12:59.799 --> 00:13:00.719 It doesn't resolve. 563 00:13:00.960 --> 00:13:02.940 You deliberately open a port 564 00:13:03.119 --> 00:13:04.590 with a basic UDP like 565 00:13:05.400 --> 00:13:06.580 um echo server 566 00:13:06.919 --> 00:13:09.000 operating with LLL doesn't respond. 567 00:13:09.200 --> 00:13:11.500 So then the problem is like I don't understand 568 00:13:11.840 --> 00:13:12.210 what 569 00:13:12.479 --> 00:13:15.520 the client wants and what security can offer cos like, 570 00:13:15.760 --> 00:13:16.109 uh, 571 00:13:16.119 --> 00:13:17.260 number one would be 572 00:13:17.559 --> 00:13:20.520 headless VM is only exposed to corporate networks. 573 00:13:20.640 --> 00:13:22.859 So that would be um if you're 574 00:13:23.070 --> 00:13:25.320 logged into a machine on site like at. 575 00:13:25.461 --> 00:13:26.492 Corporate building, 576 00:13:26.552 --> 00:13:26.562 uh, 577 00:13:27.192 --> 00:13:28.541 or if you're off-site, 578 00:13:28.791 --> 00:13:30.432 you'd have to log in through the VM, 579 00:13:30.661 --> 00:13:30.671 uh, 580 00:13:30.711 --> 00:13:31.101 not VM, 581 00:13:31.151 --> 00:13:31.812 VPN, 582 00:13:32.111 --> 00:13:33.392 and then you'd gain access to it. 583 00:13:33.632 --> 00:13:34.831 And I don't understand if that's OK. 584 00:13:34.932 --> 00:13:35.062 Like, 585 00:13:35.072 --> 00:13:35.671 if that's OK, 586 00:13:35.752 --> 00:13:36.692 that's great. 587 00:13:36.882 --> 00:13:37.231 Um, 588 00:13:37.351 --> 00:13:40.072 but if they also want off-site non-VPN, 589 00:13:40.392 --> 00:13:42.392 then what I need you to basically do is like, 590 00:13:42.711 --> 00:13:43.312 hi, 591 00:13:43.932 --> 00:13:46.262 corporate client Azure security team, 592 00:13:46.512 --> 00:13:48.211 can I open this headless VM 593 00:13:48.552 --> 00:13:51.271 to like the entire internet on these ports? 594 00:13:52.010 --> 00:13:52.900 And they're probably gonna be like, 595 00:13:53.030 --> 00:13:53.900 no, 596 00:13:54.200 --> 00:13:54.580 um, 597 00:13:54.789 --> 00:13:55.150 but like I, 598 00:13:55.190 --> 00:13:55.510 I just, 599 00:13:55.590 --> 00:13:57.210 I simply don't understand their topology. 600 00:13:57.349 --> 00:13:59.429 So I was very brave and I typed up a, 601 00:13:59.500 --> 00:13:59.669 a, 602 00:13:59.750 --> 00:14:00.349 a very long, 603 00:14:00.510 --> 00:14:01.210 very complicated, 604 00:14:01.429 --> 00:14:03.750 very thoroughly explained and researched, 605 00:14:04.030 --> 00:14:04.570 um, 606 00:14:04.630 --> 00:14:06.849 ticket to their team that basically said like, 607 00:14:07.030 --> 00:14:08.570 don't know what the right move here is, 608 00:14:08.830 --> 00:14:09.799 here's what I would like, 609 00:14:10.030 --> 00:14:10.830 let me know, 610 00:14:11.130 --> 00:14:11.390 uh, 611 00:14:11.469 --> 00:14:12.010 but they haven't 612 00:14:12.119 --> 00:14:13.229 like responded to me today. 613 00:14:13.390 --> 00:14:14.770 So today I get to do, 614 00:14:15.070 --> 00:14:15.340 uh, 615 00:14:15.349 --> 00:14:16.229 non-corporate stuff. 616 00:14:16.510 --> 00:14:16.630 Yeah, 617 00:14:16.880 --> 00:14:17.669 they may be on vacation. 618 00:14:18.265 --> 00:14:18.426 Uh, 619 00:14:18.505 --> 00:14:19.585 so that was a long tangent, 620 00:14:19.705 --> 00:14:21.625 but onto Heo's second question. 621 00:14:21.866 --> 00:14:23.346 How do the impending deaths of Horizon of, 622 00:14:23.426 --> 00:14:23.875 uh, 623 00:14:24.106 --> 00:14:25.906 worlds and Recrum affect stuff in general? 624 00:14:26.226 --> 00:14:26.466 Oh, 625 00:14:26.546 --> 00:14:28.445 they haven't really affected anything at all. 626 00:14:28.705 --> 00:14:30.346 We're talking internally like maybe we could 627 00:14:30.346 --> 00:14:32.945 like time something for the Recrum demise, 628 00:14:33.015 --> 00:14:34.666 like at a welcome event or something, 629 00:14:34.906 --> 00:14:35.265 but, 630 00:14:35.556 --> 00:14:36.106 um, 631 00:14:36.306 --> 00:14:36.935 it's like, 632 00:14:37.026 --> 00:14:37.536 hm, 633 00:14:37.745 --> 00:14:39.156 what is going on 634 00:14:39.306 --> 00:14:41.145 that like can capitalise there. 635 00:14:41.385 --> 00:14:43.056 So like the Recrum dying, 636 00:14:43.145 --> 00:14:43.505 it's like. 637 00:14:43.981 --> 00:14:44.142 Well, 638 00:14:44.192 --> 00:14:45.242 that's mostly 639 00:14:45.581 --> 00:14:48.052 people who we can't host on our platform because it's 640 00:14:48.052 --> 00:14:50.401 mostly like kids and they're mostly like 16 or, 641 00:14:50.411 --> 00:14:50.992 or younger, 642 00:14:51.302 --> 00:14:52.401 so we can't really host them. 643 00:14:52.781 --> 00:14:52.932 Uh, 644 00:14:52.942 --> 00:14:53.822 and then Horizon Worlds, 645 00:14:53.901 --> 00:14:55.052 no one really played that, 646 00:14:55.111 --> 00:14:55.262 so 647 00:14:55.942 --> 00:14:57.531 we haven't really got some like, 648 00:14:57.822 --> 00:14:58.401 you know, 649 00:14:58.721 --> 00:14:59.392 um, 650 00:14:59.771 --> 00:15:02.302 we haven't really got some like market to capitalise on there, 651 00:15:02.382 --> 00:15:02.611 but like, 652 00:15:02.661 --> 00:15:02.822 hey, 653 00:15:02.872 --> 00:15:03.372 we'll see. 654 00:15:03.581 --> 00:15:06.111 Lots of uh businesses and industry people are using the, 655 00:15:06.171 --> 00:15:09.361 the collapse of both of those platforms as like a, 656 00:15:09.700 --> 00:15:10.150 Uh, 657 00:15:10.229 --> 00:15:10.390 you know, 658 00:15:10.469 --> 00:15:13.489 like a fire or a signal that like VR is dying. 659 00:15:13.679 --> 00:15:14.150 Um, 660 00:15:14.390 --> 00:15:14.950 obviously we, 661 00:15:15.010 --> 00:15:15.150 we, 662 00:15:15.229 --> 00:15:15.349 we, 663 00:15:15.429 --> 00:15:16.049 we don't think, 664 00:15:16.150 --> 00:15:17.390 I do think that like, 665 00:15:17.609 --> 00:15:18.030 you know, 666 00:15:18.390 --> 00:15:18.630 heavy, 667 00:15:18.750 --> 00:15:19.869 heavy headsets are dying. 668 00:15:19.909 --> 00:15:21.030 Like that's the problem I think. 669 00:15:21.109 --> 00:15:22.630 We need like lighter headsets. 670 00:15:22.700 --> 00:15:24.809 I am tired of like having radiators. 671 00:15:24.979 --> 00:15:25.260 Uh, 672 00:15:25.429 --> 00:15:28.109 Josh says something about the lines of like not, 673 00:15:28.309 --> 00:15:29.429 not knowing when 674 00:15:29.640 --> 00:15:30.849 you're running down the wrong 675 00:15:31.229 --> 00:15:33.250 path of type analysis and utilisation. 676 00:15:33.700 --> 00:15:36.080 It's subverting the type system rather than working with it. 677 00:15:36.299 --> 00:15:37.059 I agree, 678 00:15:37.260 --> 00:15:39.010 but like if it was up to me, 679 00:15:39.020 --> 00:15:40.809 we wouldn't have null on our codebase at all. 680 00:15:40.979 --> 00:15:44.750 Like I would just enable a rule globally on the entire codebase and say, 681 00:15:44.780 --> 00:15:44.929 hey, 682 00:15:44.979 --> 00:15:46.280 null isn't isn't allowed. 683 00:15:47.010 --> 00:15:47.750 And uh 684 00:15:48.010 --> 00:15:48.710 then that would, 685 00:15:48.890 --> 00:15:49.969 it would self resolve it. 686 00:15:50.830 --> 00:15:51.909 All the code I write, 687 00:15:51.989 --> 00:15:54.419 I try and make it like it doesn't allow null. 688 00:15:54.630 --> 00:15:56.669 Like any entry point to new code I write, 689 00:15:56.750 --> 00:15:57.299 it's like, 690 00:15:57.309 --> 00:15:57.469 hey, 691 00:15:57.500 --> 00:15:58.549 if that parameter's null, 692 00:15:58.750 --> 00:15:59.690 piss off. 693 00:15:59.909 --> 00:16:00.469 Um, 694 00:16:00.710 --> 00:16:02.530 you guys will know that as 695 00:16:02.869 --> 00:16:04.270 argument null exception. 696 00:16:04.590 --> 00:16:05.390 throwbi null. 697 00:16:06.159 --> 00:16:09.590 You just shove that at the top of your entry point to like an area of code, 698 00:16:09.679 --> 00:16:10.190 it's just like, 699 00:16:10.200 --> 00:16:10.359 guys, 700 00:16:10.440 --> 00:16:10.559 you're, 701 00:16:10.679 --> 00:16:11.599 you're just using me wrong, 702 00:16:11.679 --> 00:16:11.880 I don't, 703 00:16:11.919 --> 00:16:12.440 I don't allow. 704 00:16:12.710 --> 00:16:12.840 What, 705 00:16:12.900 --> 00:16:16.440 what bothers me more than anything is when people use a nullable bull 706 00:16:16.599 --> 00:16:18.200 to be a tri-state boolean, 707 00:16:18.280 --> 00:16:18.409 right, 708 00:16:18.520 --> 00:16:19.380 so you've got true, 709 00:16:19.880 --> 00:16:20.320 false, 710 00:16:20.479 --> 00:16:21.159 and null. 711 00:16:21.400 --> 00:16:21.950 I'm like, 712 00:16:22.200 --> 00:16:23.559 I think you want an enum, 713 00:16:23.640 --> 00:16:24.059 right? 714 00:16:24.359 --> 00:16:25.840 Result.s success, 715 00:16:26.239 --> 00:16:26.880 failure, 716 00:16:26.960 --> 00:16:27.869 and unknown. 717 00:16:28.159 --> 00:16:30.950 Much better than a tri-state fucking bill. 718 00:16:31.650 --> 00:16:32.900 It's weird cos like I don't, 719 00:16:33.140 --> 00:16:34.840 I don't understand how functional 720 00:16:35.369 --> 00:16:37.320 code bases grow to the size 721 00:16:37.580 --> 00:16:38.179 of like 722 00:16:38.409 --> 00:16:40.619 enterprise software without object oriented, 723 00:16:40.700 --> 00:16:41.080 but 724 00:16:41.299 --> 00:16:41.919 there we go. 725 00:16:42.109 --> 00:16:42.799 Um, 726 00:16:43.140 --> 00:16:46.400 but I do wish there was more functional matters 727 00:16:46.539 --> 00:16:47.059 in 728 00:16:47.359 --> 00:16:48.409 object orientated codebase. 729 00:16:48.580 --> 00:16:50.679 Like the result pattern is so much better than like 730 00:16:50.780 --> 00:16:51.400 I am a. 731 00:16:52.650 --> 00:16:53.000 OK, 732 00:16:53.169 --> 00:16:53.400 here's, 733 00:16:53.450 --> 00:16:55.229 here's the worst result signature 734 00:16:55.690 --> 00:16:57.179 task bull nullable. 735 00:16:57.690 --> 00:16:58.039 OK, 736 00:16:58.210 --> 00:16:59.630 so it's an async method 737 00:17:00.090 --> 00:17:00.359 that 738 00:17:00.690 --> 00:17:01.669 can fail, 739 00:17:01.890 --> 00:17:03.309 but if it succeeds, 740 00:17:03.580 --> 00:17:06.108 it's the option to tell you that it doesn't know what happened. 741 00:17:06.300 --> 00:17:06.449 Uh, 742 00:17:06.530 --> 00:17:07.589 we have another question here though. 743 00:17:07.839 --> 00:17:08.010 Uh, 744 00:17:08.130 --> 00:17:09.348 Qua says, 745 00:17:09.569 --> 00:17:13.180 inspired by a fairly brief and ultimately uneventful partial outage this weekend, 746 00:17:13.439 --> 00:17:16.368 not really knowing if there was a way to harangue someone on call about it, 747 00:17:16.719 --> 00:17:17.810 so I pinged you and freaks, 748 00:17:17.880 --> 00:17:18.410 just freaks, 749 00:17:18.608 --> 00:17:18.890 just freak. 750 00:17:19.134 --> 00:17:20.042 Have a an SLA? 751 00:17:20.093 --> 00:17:20.292 No. 752 00:17:20.493 --> 00:17:21.933 Does the public universe have an SLA? 753 00:17:22.323 --> 00:17:22.894 Or if something, 754 00:17:22.983 --> 00:17:23.163 uh, 755 00:17:23.213 --> 00:17:26.093 if something goes down at this point in a wider scale, 756 00:17:26.213 --> 00:17:27.673 then I recommend things to do here 757 00:17:28.053 --> 00:17:30.713 as a rando in the community for escalating if necessary. 758 00:17:30.973 --> 00:17:33.203 Make a GitHub request and get people to it. 759 00:17:34.024 --> 00:17:34.293 I don't, 760 00:17:34.364 --> 00:17:37.203 I don't mean that like I do mean that both sillililily, 761 00:17:37.654 --> 00:17:39.193 but also like, 762 00:17:39.413 --> 00:17:40.053 um, 763 00:17:40.333 --> 00:17:41.053 honestly as well, 764 00:17:41.173 --> 00:17:41.433 right? 765 00:17:41.573 --> 00:17:41.973 So 766 00:17:42.254 --> 00:17:45.534 one of the problems we had during some additional outage that we've had. 767 00:17:45.817 --> 00:17:46.517 Previously 768 00:17:46.738 --> 00:17:49.208 is that everyone was pinging fruit saying it's down, 769 00:17:49.218 --> 00:17:51.817 and they weren't specifying what was down or how they knew it 770 00:17:51.817 --> 00:17:54.767 was down or what the symptoms were or anything like that. 771 00:17:54.978 --> 00:17:56.618 And so the first thing he asked was like, 772 00:17:56.738 --> 00:17:56.817 hey, 773 00:17:56.897 --> 00:17:59.238 can you make a GitHub issue that describes why this is down, 774 00:17:59.407 --> 00:18:01.297 and then I'll be easily able to fix it. 775 00:18:01.447 --> 00:18:01.657 Uh, 776 00:18:01.738 --> 00:18:03.137 I would never advise pinging fruits. 777 00:18:03.177 --> 00:18:04.338 It's usually not the best way, 778 00:18:04.417 --> 00:18:06.238 but I don't really have any other suggestions. 779 00:18:06.297 --> 00:18:06.838 Um, 780 00:18:07.098 --> 00:18:09.868 we do have what looks to be an outage in the 781 00:18:10.047 --> 00:18:11.317 moderation portal, 782 00:18:11.858 --> 00:18:12.137 an ex-cloud. 783 00:18:12.531 --> 00:18:13.621 and wiki right now. 784 00:18:13.781 --> 00:18:14.021 Um, 785 00:18:14.082 --> 00:18:17.141 I do intend to resolve that immediately following office hours, 786 00:18:17.222 --> 00:18:18.661 but I didn't want to cancel office hours, 787 00:18:18.781 --> 00:18:19.082 so 788 00:18:19.302 --> 00:18:19.651 we'll just, 789 00:18:19.702 --> 00:18:19.862 you know, 790 00:18:19.972 --> 00:18:21.362 have an hour of downtime there. 791 00:18:21.621 --> 00:18:21.812 Uh, 792 00:18:21.901 --> 00:18:25.602 if you are in a modern code base and you see task boo question mark, 793 00:18:25.822 --> 00:18:27.452 and you can't really do much changes, 794 00:18:27.702 --> 00:18:28.371 consider a topple. 795 00:18:28.462 --> 00:18:29.491 You could do task, 796 00:18:29.682 --> 00:18:31.421 tuple brackets or square bracket, 797 00:18:31.482 --> 00:18:31.901 I don't remember, 798 00:18:32.041 --> 00:18:32.302 but whatever, 799 00:18:32.342 --> 00:18:33.141 you could do like boo, 800 00:18:33.501 --> 00:18:34.082 question mark, 801 00:18:34.092 --> 00:18:34.602 string 802 00:18:34.901 --> 00:18:35.281 and 803 00:18:35.942 --> 00:18:37.041 immediately, 804 00:18:37.342 --> 00:18:38.222 slightly better. 805 00:18:38.421 --> 00:18:38.822 Still got. 806 00:18:38.946 --> 00:18:39.696 damn awful, 807 00:18:39.826 --> 00:18:41.015 but slightly better, 808 00:18:41.186 --> 00:18:42.026 because at least with the string, 809 00:18:42.105 --> 00:18:43.566 you can kind of figure out what's going on, 810 00:18:43.576 --> 00:18:45.015 or at least log it to the log file. 811 00:18:45.066 --> 00:18:45.265 I mean, 812 00:18:45.306 --> 00:18:45.576 like, 813 00:18:45.586 --> 00:18:46.605 more optimally, 814 00:18:46.916 --> 00:18:47.725 you just do 815 00:18:47.855 --> 00:18:48.816 taskable, 816 00:18:49.395 --> 00:18:49.965 uh, 817 00:18:49.985 --> 00:18:50.446 result 818 00:18:50.625 --> 00:18:51.625 as like an enum, 819 00:18:51.826 --> 00:18:52.526 but at that point, 820 00:18:52.656 --> 00:18:53.465 you don't need the ball, 821 00:18:53.586 --> 00:18:54.806 so you just do task result, 822 00:18:54.826 --> 00:18:55.586 and at that point you're like, 823 00:18:55.625 --> 00:18:55.745 oh, 824 00:18:55.826 --> 00:18:57.345 I could write my own result class, 825 00:18:57.426 --> 00:18:57.755 and I'm like, 826 00:18:57.826 --> 00:18:57.906 no, 827 00:18:57.995 --> 00:18:59.066 just go use fluent results. 828 00:18:59.265 --> 00:19:02.206 For anyone who doesn't like C and is wondering why, 829 00:19:02.426 --> 00:19:04.245 if you read the fluent result page, 830 00:19:04.505 --> 00:19:05.446 you might be like, 831 00:19:05.456 --> 00:19:05.465 ah. 832 00:19:05.869 --> 00:19:06.140 Yeah, 833 00:19:06.390 --> 00:19:07.180 that's why I don't like it, 834 00:19:07.189 --> 00:19:08.180 because I didn't have this. 835 00:19:08.390 --> 00:19:09.599 And if that isn't enough, 836 00:19:09.670 --> 00:19:10.099 um, 837 00:19:10.349 --> 00:19:11.689 then you can go here 838 00:19:11.819 --> 00:19:13.430 and die cause it's very, 839 00:19:13.550 --> 00:19:13.709 very, 840 00:19:13.829 --> 00:19:15.329 very complicated and thick. 841 00:19:15.579 --> 00:19:15.930 But, 842 00:19:15.949 --> 00:19:16.250 uh, 843 00:19:16.260 --> 00:19:21.180 Luthi language extensions adds a bunch of functional programming stuff to C, 844 00:19:21.709 --> 00:19:22.069 um, 845 00:19:22.270 --> 00:19:22.949 but it is like, 846 00:19:23.030 --> 00:19:24.170 it's one of the thickest 847 00:19:24.630 --> 00:19:26.140 read mes I've ever seen. 848 00:19:26.270 --> 00:19:26.949 It is like I've. 849 00:19:27.066 --> 00:19:29.125 Read it like 5 times in a row, 850 00:19:29.336 --> 00:19:29.625 um, 851 00:19:29.745 --> 00:19:32.465 but it implements all the monads that you might be useful to. 852 00:19:32.576 --> 00:19:33.406 It's like option, 853 00:19:33.546 --> 00:19:33.965 either, 854 00:19:34.196 --> 00:19:34.666 thin, 855 00:19:34.865 --> 00:19:35.645 like all of them. 856 00:19:36.475 --> 00:19:36.826 Babertine says, 857 00:19:36.865 --> 00:19:37.806 when are you going to transition, 858 00:19:37.865 --> 00:19:38.015 uh, 859 00:19:38.026 --> 00:19:39.605 resonate to using an FX library? 860 00:19:39.745 --> 00:19:40.485 It's interesting, 861 00:19:40.786 --> 00:19:41.156 um, 862 00:19:41.225 --> 00:19:42.845 that you say that because like 863 00:19:42.946 --> 00:19:45.706 if you look into like UI based languages like, 864 00:19:45.906 --> 00:19:46.475 um, 865 00:19:46.906 --> 00:19:48.105 all the like Xama ones. 866 00:19:48.222 --> 00:19:48.352 I, 867 00:19:48.482 --> 00:19:48.612 I, 868 00:19:48.661 --> 00:19:50.562 I can't keep up to date with how many there are, 869 00:19:50.862 --> 00:19:51.182 um, 870 00:19:51.302 --> 00:19:52.222 but they have, 871 00:19:52.501 --> 00:19:55.271 they have this interface called I notify property change, 872 00:19:55.342 --> 00:19:55.822 um, 873 00:19:55.942 --> 00:19:56.192 and there's, 874 00:19:56.222 --> 00:19:57.552 there's various other types of it, 875 00:19:57.661 --> 00:19:59.202 but like that's how you sort of 876 00:19:59.452 --> 00:20:01.001 pick up on the fact that 877 00:20:01.381 --> 00:20:02.482 stuff is reactive 878 00:20:02.661 --> 00:20:02.862 and it, 879 00:20:02.901 --> 00:20:03.011 it, 880 00:20:03.062 --> 00:20:04.421 it tends up to be like 881 00:20:04.671 --> 00:20:07.161 a lot like how we do our data model, 882 00:20:07.261 --> 00:20:07.501 um, 883 00:20:07.781 --> 00:20:08.442 that's the, 884 00:20:08.462 --> 00:20:09.182 uh. 885 00:20:09.969 --> 00:20:10.520 So what I, 886 00:20:10.569 --> 00:20:13.069 I tend to use for UI is reactive UI, 887 00:20:13.369 --> 00:20:13.709 um, 888 00:20:13.719 --> 00:20:14.560 which I just linked, 889 00:20:14.689 --> 00:20:14.880 uh, 890 00:20:14.890 --> 00:20:15.949 but that even that 891 00:20:16.250 --> 00:20:17.150 turns into 892 00:20:17.650 --> 00:20:18.150 like 893 00:20:18.469 --> 00:20:19.609 something like 894 00:20:19.750 --> 00:20:20.890 our um 895 00:20:21.030 --> 00:20:22.010 sinky doodad, 896 00:20:22.250 --> 00:20:23.510 uh cos you can make 897 00:20:23.849 --> 00:20:27.410 any model reactive with some like annotations and they just like generate a bunch. 898 00:20:27.834 --> 00:20:29.755 So me as a naive uh person, 899 00:20:29.795 --> 00:20:30.375 I'm like, 900 00:20:30.395 --> 00:20:31.935 is this applicable to a resonate? 901 00:20:32.104 --> 00:20:33.084 And the answer is probably not, 902 00:20:33.114 --> 00:20:33.515 cos we're, 903 00:20:33.625 --> 00:20:35.915 we're not synchronising between UI threads, 904 00:20:35.944 --> 00:20:37.025 we're synchronising between computer. 905 00:20:37.155 --> 00:20:37.265 Yeah, 906 00:20:37.275 --> 00:20:37.834 I want, 907 00:20:37.915 --> 00:20:38.584 um, 908 00:20:38.795 --> 00:20:39.334 I don't 909 00:20:39.555 --> 00:20:41.895 really understand why the feature is called this, 910 00:20:42.194 --> 00:20:42.655 but 911 00:20:42.944 --> 00:20:44.925 discriminated unions in C. 912 00:20:45.594 --> 00:20:45.875 Like I, 913 00:20:45.954 --> 00:20:47.714 I don't call them discriminated unions. 914 00:20:47.755 --> 00:20:48.954 I'm like that thing I want. 915 00:20:49.719 --> 00:20:50.050 Uh, 916 00:20:50.140 --> 00:20:52.319 Kuala's is one of the best cheeses for a grilled cheese, 917 00:20:52.599 --> 00:20:53.420 so you actually want 918 00:20:53.719 --> 00:20:55.680 two cheeses in your grilled cheese. 919 00:20:55.920 --> 00:20:57.449 You want a flavorful cheese, 920 00:20:57.560 --> 00:20:58.959 which is like choice, 921 00:20:59.150 --> 00:21:01.060 whatever you want for like cheese flavour, 922 00:21:01.319 --> 00:21:02.699 but you wanna mix in some, 923 00:21:03.000 --> 00:21:03.530 um, 924 00:21:03.599 --> 00:21:04.479 like more goopy, 925 00:21:04.520 --> 00:21:05.439 stringy cheese. 926 00:21:05.645 --> 00:21:07.015 To get like the cheese pull, 927 00:21:07.204 --> 00:21:09.834 uh for that you'd like want mozzarella or something like that, 928 00:21:10.165 --> 00:21:11.704 there's there's cheeses that like 929 00:21:12.045 --> 00:21:15.484 melt and cheese pull better and there are cheeses that taste a bit like concrete. 930 00:21:15.564 --> 00:21:16.964 Do you know concrete's really complicated, 931 00:21:17.005 --> 00:21:19.165 like you can add and remove so many different 932 00:21:19.165 --> 00:21:21.305 like additives to concrete to change how it works. 933 00:21:22.750 --> 00:21:24.719 Grilled cheese is a lot like concrete 934 00:21:25.109 --> 00:21:26.099 2026. 935 00:21:26.260 --> 00:21:27.739 I'm looking for a, 936 00:21:27.800 --> 00:21:31.290 like a good guide into what discriminated unions would be for you guys, 937 00:21:31.510 --> 00:21:33.790 but I don't understand some of these articles. 938 00:21:34.069 --> 00:21:34.589 So like, 939 00:21:34.709 --> 00:21:35.180 you know, 940 00:21:35.430 --> 00:21:35.790 they're like, 941 00:21:36.069 --> 00:21:38.060 here's discriminated unions in C, 942 00:21:38.150 --> 00:21:38.589 and then they're like, 943 00:21:38.630 --> 00:21:40.589 here's some mathematics and some latex diagram. 944 00:21:40.739 --> 00:21:41.869 This is a great article, 945 00:21:41.949 --> 00:21:44.430 but it talks about them before it knew that .NET was getting them, 946 00:21:44.550 --> 00:21:46.270 so it's like using some like thing. 947 00:21:46.516 --> 00:21:46.746 Uh, 948 00:21:46.756 --> 00:21:48.057 and then here's the like learn. 949 00:21:48.237 --> 00:21:49.366 Microsoft page for it. 950 00:21:49.597 --> 00:21:49.827 But yeah, 951 00:21:49.876 --> 00:21:49.947 it, 952 00:21:50.036 --> 00:21:52.656 it's basically a solve to this whole problem of like 953 00:21:52.786 --> 00:21:53.237 null, 954 00:21:53.347 --> 00:21:54.996 it's like another solve for the null problem. 955 00:21:55.116 --> 00:21:56.796 If you want like unions or stuff like that, 956 00:21:56.886 --> 00:21:56.996 you, 957 00:21:57.107 --> 00:21:58.097 you need new collection. 958 00:21:58.266 --> 00:21:58.396 Like, 959 00:21:58.437 --> 00:21:58.717 bro, 960 00:21:58.796 --> 00:21:59.077 the day, 961 00:21:59.156 --> 00:22:00.457 the day we get collections 962 00:22:00.876 --> 00:22:02.107 and nested nodes, 963 00:22:02.317 --> 00:22:02.477 alright, 964 00:22:02.557 --> 00:22:03.636 do we have other questions? 965 00:22:03.837 --> 00:22:04.116 Epic, 966 00:22:04.197 --> 00:22:05.116 cos there's no more questions, 967 00:22:05.197 --> 00:22:07.776 I've gotta take the dog for a walk around the block and then uh 968 00:22:08.036 --> 00:22:09.296 fix the wiki 969 00:22:09.677 --> 00:22:10.097 next. 970 00:22:10.244 --> 00:22:11.244 And the moderation. 971 00:22:11.963 --> 00:22:12.083 Uh, 972 00:22:12.124 --> 00:22:12.364 it's, 973 00:22:12.443 --> 00:22:13.404 it's very logical though. 974 00:22:13.443 --> 00:22:14.644 It's a file space issue. 975 00:22:14.703 --> 00:22:17.443 So what I'm gonna do is go find out what's like eating file space, 976 00:22:17.673 --> 00:22:17.843 uh, 977 00:22:17.923 --> 00:22:18.504 and then 978 00:22:18.734 --> 00:22:20.604 shove as much of that as possible in R2. 979 00:22:20.764 --> 00:22:21.364 I know for example, 980 00:22:21.404 --> 00:22:22.543 you can configure, 981 00:22:22.884 --> 00:22:23.494 um, 982 00:22:23.884 --> 00:22:26.843 Nextcloud to use S3 as a document storage. 983 00:22:26.923 --> 00:22:28.313 So with like a couple of edits, 984 00:22:28.323 --> 00:22:29.303 I should be able to 985 00:22:29.563 --> 00:22:29.803 be like, 986 00:22:29.923 --> 00:22:30.384 hey, 987 00:22:30.604 --> 00:22:31.264 all of our 988 00:22:31.524 --> 00:22:33.443 PowerPoints and stuff are on Nex, 989 00:22:33.604 --> 00:22:33.754 are, 990 00:22:33.764 --> 00:22:34.043 are on. 991 00:22:34.331 --> 00:22:36.370 R2 now but like surface to Nextcloud, 992 00:22:36.451 --> 00:22:39.020 that'll be cool cos that would get rid of a lot of file space. 993 00:22:39.090 --> 00:22:39.750 But then 994 00:22:40.051 --> 00:22:41.250 one of the other problems I've noticed, 995 00:22:41.331 --> 00:22:42.520 and actually you saw me make a, 996 00:22:42.531 --> 00:22:44.630 a um a GitHub issue about this one, 997 00:22:45.571 --> 00:22:46.110 in 998 00:22:46.370 --> 00:22:48.020 the flat card Linux setup, 999 00:22:48.211 --> 00:22:49.340 we don't want 1000 00:22:49.610 --> 00:22:51.230 the headless logging to file 1001 00:22:51.571 --> 00:22:54.120 because the logs are flowed through Journal, 1002 00:22:54.370 --> 00:22:55.791 which is System D's 1003 00:22:55.931 --> 00:22:57.890 like logging thingy the bobby. 1004 00:22:58.239 --> 00:22:58.920 Um, 1005 00:22:59.119 --> 00:22:59.729 and 1006 00:22:59.880 --> 00:23:01.869 that means we don't need additional file logging. 1007 00:23:01.880 --> 00:23:03.599 Like Journal already does that for us, 1008 00:23:03.680 --> 00:23:03.839 and, 1009 00:23:03.949 --> 00:23:04.599 and not only that, 1010 00:23:04.680 --> 00:23:06.839 Journal will rotate logs as well, 1011 00:23:07.160 --> 00:23:10.630 whereas I don't think there's any logic that would be like, 1012 00:23:10.920 --> 00:23:11.439 hi, 1013 00:23:11.989 --> 00:23:12.760 or like headless, 1014 00:23:13.079 --> 00:23:15.599 the machine you're trying to write a log file to is kind of full, 1015 00:23:15.719 --> 00:23:15.959 could you, 1016 00:23:16.079 --> 00:23:16.739 could you not? 1017 00:23:16.920 --> 00:23:19.660 One of the things I was thinking of doing with like uh 1018 00:23:19.839 --> 00:23:21.430 Docker setup is like, 1019 00:23:21.680 --> 00:23:22.219 hey, 1020 00:23:22.489 --> 00:23:23.060 uh, 1021 00:23:23.270 --> 00:23:26.079 if we bind the log directory to Devkull. 1022 00:23:27.050 --> 00:23:27.729 Will that work? 1023 00:23:27.939 --> 00:23:28.810 Like resident will be like, 1024 00:23:28.859 --> 00:23:28.969 yeah, 1025 00:23:29.020 --> 00:23:30.010 I'm writing log files, 1026 00:23:30.060 --> 00:23:30.969 I'm writing log files, 1027 00:23:31.020 --> 00:23:32.339 and meanwhile the computer's just go, 1028 00:23:32.459 --> 00:23:33.000 yeah, 1029 00:23:33.819 --> 00:23:34.339 carry on. 1030 00:23:34.420 --> 00:23:35.650 Let's get you back to bed. 1031 00:23:36.020 --> 00:23:37.119 Resonite headless. 1032 00:23:37.500 --> 00:23:38.579 You're not writing log files, 1033 00:23:38.660 --> 00:23:39.140 you're writing to 1034 00:23:39.310 --> 00:23:39.319 know. 1035 00:23:39.780 --> 00:23:39.969 But yeah, 1036 00:23:40.060 --> 00:23:41.060 much easier to just turn those off. 1037 00:23:41.290 --> 00:23:41.609 Ah, 1038 00:23:41.900 --> 00:23:42.280 so 1039 00:23:42.380 --> 00:23:43.859 for the wiki and Nextcloud, 1040 00:23:43.939 --> 00:23:44.939 they aren't using journal, 1041 00:23:45.380 --> 00:23:45.609 um, 1042 00:23:45.699 --> 00:23:46.709 they'll be in the, 1043 00:23:46.780 --> 00:23:47.280 uh, 1044 00:23:47.339 --> 00:23:48.260 Docker log engine, 1045 00:23:48.290 --> 00:23:49.780 which I believe also handles rotating, 1046 00:23:49.859 --> 00:23:50.099 but I'm, 1047 00:23:50.170 --> 00:23:50.699 I'm not entirely. 1048 00:23:50.819 --> 00:23:51.359 As a reminder, 1049 00:23:51.500 --> 00:23:52.540 my goal for the machine. 1050 00:23:52.635 --> 00:23:53.714 That runs the wiki, 1051 00:23:53.834 --> 00:23:57.334 Nextcloud support and all that other stuff is to delete it. 1052 00:23:57.515 --> 00:23:57.834 Um, 1053 00:23:58.114 --> 00:23:58.635 so we, 1054 00:23:58.675 --> 00:23:59.185 we're getting there. 1055 00:23:59.354 --> 00:24:00.584 Some of this header stuff is actually helping. 1056 00:24:00.635 --> 00:24:00.785 Like, 1057 00:24:00.795 --> 00:24:01.175 I could 1058 00:24:01.635 --> 00:24:06.234 theoretically stand up like now a VM for us that would have the stuff that we need, 1059 00:24:06.435 --> 00:24:07.175 including the wiki, 1060 00:24:07.385 --> 00:24:07.625 but, 1061 00:24:07.795 --> 00:24:08.234 uh, 1062 00:24:08.395 --> 00:24:10.074 I'd also be stepping on someone's toes cause, 1063 00:24:10.194 --> 00:24:10.594 cause 1064 00:24:10.795 --> 00:24:11.814 Jay is trying to do that. 1065 00:24:12.275 --> 00:24:13.035 But that happens naturally. 1066 00:24:13.074 --> 00:24:13.944 It's never intentional. 1067 00:24:13.954 --> 00:24:14.584 It's just like, 1068 00:24:14.834 --> 00:24:15.234 hey, 1069 00:24:15.375 --> 00:24:16.155 corporate clients, 1070 00:24:16.234 --> 00:24:17.214 corporate clienting, 1071 00:24:17.474 --> 00:24:18.545 they want this thing this month, 1072 00:24:18.795 --> 00:24:19.155 next month, 1073 00:24:19.194 --> 00:24:19.915 they might want something. 1074 00:24:20.114 --> 00:24:20.234 Yeah, 1075 00:24:20.314 --> 00:24:20.895 I will.