 Welcome to the Minecraft DevSync. It is Tuesday, the 23rd of November. Christopher is on leave, so Derek, kick us off. Alright, well, I've continued to work on my mechanical CAD of the Mark II. I took a break this morning, though, to do a little holiday image for the Thanksgiving holiday. For the newsletter and blog and whatnot, for Sarah. But yeah, mostly continuing to work progress on the CAD for the latest revision. And it's going along, going along. Hopefully I can have it to a point where I can print. Well, you know, this week is a short week. So, you know, either at the end of very in a next week or the beginning of the week following. Lots still left to do little details and stuff. Good news is everything going well with the latest board spin. And I think those are maker fabs should have those back to us by the second week of December. Yeah, so at that point, we should have a good prototype. I thought we also... Is this a DFM prototype or not quite? Well, I'm thinking, so there's a point. So yes, it's on route to DFM. Everything is considered DFM. But there is this like kind of very last pass where you go in and like at each intersection of like a rib and the body, you have to like add this like tiny fillet, like the tiny rounded section and all this little nipping stuff that can take forever. It won't be fully done. I'm just going to go ahead and print it once I get everything in place. Because even though technically, yes, the fidelity of our SLA could probably do some of that stuff. It's really not going to matter. So get the fit tested first and then it'll probably be another week or two just doing that fine, fine tuning stuff to really wrap it up. Yeah, yeah. And of course, you could talk about this together, but we had a red sync with the blue systems folks this morning. And, you know, not much going on there, but there was some interesting... Well, just, yeah, everybody's, you know, been busy with other stuff. Did you have a cool update on schooling text? And they talked a little bit about how they had issues with Wi-Fi stuff too. So I don't know if any of that would be useful. Can buy bits and that over to you on very mostly. So yeah, that's it. That's it for me. Yeah, so there's a new proposed Marquee text delegate, which will do scrolling text. So the idea being, you know, particularly if you've got like a, you know, we were originally talking about it in terms of the media playback interface. And if you've got a really long artist name or a song title, you know, rather than just sort of truncating it with an ellipsis, then you could actually, you know, scroll across so people can read the entire song name. That's kind of the concept there. Ken. Yeah, so I continue to work on this. I guess the workarounds for the AW Connect container bugs. I did notice what Michael saw. My device actually freaked out too and started interplaying mimic one and mimic two. I did see 500 errors in the log at that time, but it also sounds like there's a caching problem. So when I get down to fixing the mimic stuff, the mimic one stuff, I will take a look at that and maybe that'll fix that as a byproduct of that. What I'm working on with the Wi-Fi right now is the two different types. And where I'm at is I'm trying to get it to reboot. It's just not rebooting with the standard boot command, reboot command from Linux. So that's that's kind of where I'm at right now. You know, if I see the clock is not set and I can detect that various ways. It's actually this, this more recent build, the default date changed to like 214 2019. But if I see the clock hasn't been set, that indicates one thing to me. If I see that the clock is set, but we're disconnected, then that indicates another thing to me. So what I've done is I've, in both cases, given them like three minutes. And if I don't see them coming back after that, then I go ahead and reboot. If there's no clock, that means it just didn't boot cleanly, which means probably bad creds. And if there was a clock, but it's still disconnected after three minutes, that means the network went out. The other issue I noticed with their access point is comes up too fast. So like fortuitously, I had a electrical adage today briefly reset all my equipment. And I noticed that when my crop came back up again, the access point came back up. Of course, because my home network router didn't come up faster than the access point. And the access point captured the networks that were available to it at the time of boot, which was not my network. Because my network hadn't come up yet. And it would never recover from that because it would never find my network. So that goes into the, you know, kind of old reboot process. So hopefully this will fix that. I've got two new files and a modified file that I'll need to get into the build once I have this debug. I thought that was the case and I was going to give it to you now, but I'm not sure why it's not rebooting. So once I figure out the reboot problem, then I'll send you a couple of files. They go into op-microft and then one modifies the startup.sh file. So we'll take it from there. And at some point this will have to get integrated with the Wi-Fi skill and stuff. Right now this will at least work on that. In terms of trying to issue a rebate command, are you using systemctl? No, I'm using a sudo reboot-r. Yeah, use systemctl, that should work. Yeah, that's what I'll use. Once I get work and I'll email you these files, let me know when they're in the next build. I'll have to go into the op-microft directory and then I can do a new build and give it a bad password to make sure it recovers from that. Alright, if they're intended for the op-microft directory, that's just microfcore. So if you put them in... They're outside of microfcore. Okay, I'll... If you look at where the Taz files are and the startup files, they go there. Alright, alright. Cool. On my front, the most exciting news is that the Sprint 22 is coming to a close because I finally did a PR for the Wolfram Alpha changes. It took far longer than I originally thought. Yeah, so the idea is that it's like the Wikipedia and DuckDuckGill, DuckDuckGo skills. You will now get a GUI anytime you ask a sort of common general question and answer type thing. But we had to go through a bit of process to get... There are different types of responses that Wolfram can provide. So at the moment, we're differentiating between three different response types. So if it's a basic calculation, so if you say what's 2 plus 2, it will display the equation itself. So 2 plus 2 equals 4. If you ask for a conversion, it will display the output of that conversion. So just the answer. So if you said like how many teaspoons in a tablespoon, it'll say three or whatever it is. And three teaspoons, I should say. And then if it's a general knowledge type thing that's about a particular topic, then we'll try and grab an image about that thing. So if you said who's the current president, it's going to show you a picture of Joe Biden with the title of Joe Biden. So we try and grab those images straight from Wolfram's response. But sometimes it gives us a Wikipedia image, so then we grab that. And if all of that fails, then we go and try and grab something from DuckDuckGo image search. So yeah, that's the current state of it. I think those GUIs, particularly like the conversions and things like that, there's some real scope for those to get fleshed out further. In terms of an MVP, it tells you the answer and displays the answer. So I think that's good for the moment and we could spend a huge amount of time making the displays for that look really pretty. Which I'm sure we'll do at some point, but we need to get the rest of the basics down first. So as soon as we've reviewed that and addressed any feedback and everything, we can close out 22. And that'll be super exciting. Yeah, I think that was the main thing from yesterday. Oh, I started adding some more stuff into the pull-down menus about page. And a teacher's been helping turning that into a flickable, so basically scrollable kind of element so that you can have more information than fits on a single screen, which would be sweet. But I'm going to put a hold on me doing new development stuff because I have been intending to get back and get onto community PRs for a little while. The Wolfram stuff just took way longer than expected. So I'm going to spend a bit of time getting back and reviewing things there and going on a bit of a merge fest. So that'll be my day today and probably tomorrow. All right. Well, if you don't hear from me tonight, you'll hear from me tomorrow. But I'll be sending you some files and I'll want to get them in the build and then just ping me back when the build's done. It doesn't matter. I'll work over the weekend. I don't have a lot of family in this week. My wife's family's coming in a week or two later. So I'll be working through the weekend mostly. But yeah, hopefully by Monday I'll have this stuff done. Tomorrow I'm hoping to switch over to fixing the mimic one stuff. And we'll still meet tomorrow, I presume. Yeah. Wednesday. Yeah, cool. All right. Fairly well, y'all. Cheers.