 Welcome to the micro of dead sink today is Wednesday the 17th of November yes, and Derek's kicking it off go Derek All right, so yes, I've been working on mechanical cat for essentially all week and today I Was essentially spending my time in the audio chamber For those of you that have actually seen the dev kit audio chamber or the 3d print version, you know It was kind of designed to actually be printed as one part, but it's totally not moldable So I have to split that up into front and the back and get all the draft angles right and make sure that the The holes for the mounting of the speaker Are in alignment with the draft and the direction of pull of the mold and all that stuff so Have to turn it from a 3d designed for 3d printing to design for injectable Yeah, that's what I've been working on. Let's get that audio chamber Squared away. Yeah, and I'll be continued to work on the cat stuff again tomorrow. So Go go Chris V So this morning I did some admin type stuff. I got some PR review for you, mr. Gazzling and It's some stuff with the high on the hiring front with the test for the server side developer and this afternoon I have been Working on the startup sequence specifically The mycroft ready portion of it I have some documentation put together in the startup sequence doc and I pointed to it in Matter most so you'll take a look at that and Tell me if I'm crazy. I'll be awesome Tomorrow will be more startup sequence stuff beautiful Ken Smith Okay, so I attended the open Voice meeting this morning. I reviewed Chris's document He was just discussing process and device status section I communicate with panic core. I'm still working on the debuffs and the statuses I suspect they have a bug in their container. So they're investigating that And uh, right now it looks like I get about three state changes. So I don't know how that's I'm figuring out how it's going to map into what we're looking for, but uh Yeah, and I'll be continuing to work on that beautiful um Yes, thanks for the reviews chris. I um, I just Pushed some prs to micro skills to put the new duck duck go and mark two skills into the Into the marketplace. So they they will go out onto all devices, but we should also Chuck them in that um in the mark two branch um The wool from I did a bunch of work on the wool from um skill Just tidying up What I'd done and uh getting the sort of Previously there was two wool from clients within the skill. Um, one if you, you know, had a local api key and the other if you um We're using selene But then I meant that, you know, you kind of had to keep the two in sync and and all that sort of stuff. So I I merged them into one that Just changes where it calls based on whether you have an api key local api key defined or not um I Have have mostly been testing it using the local api key And because I was having trouble with the the v2 endpoint on selene and um I thought it was my code Which, you know, there is nothing wrong with the v2 endpoint on selene. It's just that it was originally coded to provide To only take an input query and there's a bunch of other parameters that are accepted by the by the wool from endpoint that we can use Um, you know, one of which is like Returning jason instead of xml and that sort of thing And so I've kind of done the skill based on the assumption that I could use those things um Which isn't necessarily the case. So I was thinking about uh Doing some updates to that endpoint. Um But I also noticed that there was a suggestion to change the name of it because currently it's called w a So then I contemplated Yeah, really really a descriptive name there, right w a um It's the west Australian endpoint um So, yeah, so then I I thought rather than american rather than break. Yeah, washington washington endpoint um rather than break the You know do a breaking change on that Or writing a bunch of code to like, you know, check if if you know, it's in the old format Then or you know, if it doesn't have any of the new stuff then Use the old format and blah blah blah that maybe would just add a new endpoint and call the w a1 deprecated or something and you know so If you're sort of throw that as an idea and if you're happy with that, I'll I'll do a pf that today great um Yeah, we're not going to use the simple endpoint in the end. Um, I've left it in there just like in the skill as well in case someone wants to use it, but um, it provides really Ugly output so really detailed amazing stuff, but um Just not visually appealing at all So, yeah um I think that's about It um Yeah, I've been spending a fair bit of time Writing code, so I want to spend a fair bit of the rest of the week getting back in Looking at community prs and things all right anything else from anyone Well, will we call it a day? Womp womp cool. All right Did you stick around for just a second? Yes, can do All right, good After doing good evening and good night