 Not on hardware time, like, yeah. We do a newsletter every single week. I got two things I want to talk to you about. Yes. First up, we have the recap from Circuit Python Day. I know. It was a big success. Yeah. And I think one of the things that's really hard to do is an event in general. And you probably always need to do a virtual hybrid now and have the recordings in a place. In-person's a little bit harder now, especially like whatever natural disaster, weather thing, sickness, something's going on always. So I think we figured out a way to keep Circuit Python Day going while we figure out what type of in-person thing would we do when we bolt onto an event. So check out all of the videos that we have from our shows that we did, 3D Hangouts, Keeps and Boops, Game Jam, The Biportal Message Project, Circuit Python Day Chat. And you can also watch some of the stuff with Scott, some of the really deep innards of Circuit Python. We do have an 8.23 release. That's a dot update. So if you're really interested in things, there's RGB matrix timing on that with SAM, X5, X5, same things. Yeah, we've been doing a lot of hacking to the matrices, some of the ones that we have in stock now are a little bit that pickier about timing. So we just got that going. Lots of projects. One that I wanted to just mention is, so I saw that movie Interstellar. I liked the graphics with the, especially the black hole. I was like, oh, you know, they're pretty good. I think it was around that time when we were getting the images of a black hole, like the first time. It was neat to kind of see that. But the robot, the Tars robot, I thought that was a really cool idea, this robot companion that it was AI and it's there to help you and stuff. And when I saw, maybe it was open-sauce, someone had tagged us because they made a bot and they used some metaphor stuff. And that was really neat. So that's in the newsletter. I think this is a cute robot because it was a very different design. It's this walking robot that has these blocks. It wasn't like a humanoid. It was meant to, clearly it's a robot. It's not just something that looks like a human. Like, I am human, I'm data. Data is fine. I'm data. But for this little segment, I wanted to ask you about merging. The urge to merge. The urge to merge. What's going on when we do a merge and more with? Well, one of the big projects that we're doing right now is prepping for CircuitPython 9. Like, we're already at 8.23. We've been supporting Expressif very well lately. So time to think about 9. And one of the things that we like to do is when we do a major release, that's a good time for us to do an upstream merge from MicroPython because we love MicroPython, but they kind of like to make API changes, especially MPY file changes, and they've got good reason to do it. They're doing this cool load from file system stuff. But we don't like to have breaking changes unless it's a major version. And so we kind of waited until we're kind of settled with 8. We're ready to do 9. 9 is going to be USB host, as well as maybe some Bluetooth stuff we'll see. And the theme you think for 9, USB host? I think USB host is going to be the theme, yeah, because we're basically getting something. Got to work on a new poster. You're going to be like a little hostess. Yeah, it could be like. Don't put the USB logo in there because I think you have to license it. You're not going to know. And who knows what the right logo anymore because there's like a billion USB variants. And you could be like the blink of tail with the. It could be a blink of serving up. Serving up the goodness. Max, B, B, Mini. So we're getting that going. But we're also doing this upstream merge from 1.19 and 1.20. We just have an MPY change. We're also having just a lot of changes, which is good. I mean, we are the biggest or one of the biggest sponsors of MicroPython. Yeah, I guess we should, I guess we should mention it because you know, you don't get credit and there's people that try to dunk on you. So we give money to, we specifically sponsor MicroPython and we increase that every single year. I think we're the largest one, but someone can correct me if I'm wrong. We also help fundraise every year on the GitHub sponsors. So you can go to the MicroPython GitHub repo and you can see the sponsors. We also did that there because we wanted to show like, hey, like we can do it because organizations could do it. But then they're getting closer to reaching their goals and then they're able to hire more people, do more things. All these things work together. So MicroPython is an open source core that we base sort of Python off of and then we do upstream changes and they do changes and we do stuff. And then you get a really nice ecosystem that allows hardware support across lots of different ports. MicroPython is going to support this stuff. We're going to be able to support like all 400 plus boards that we want to support. Other people can make boards. So when we're doing upstream changes, what's the thing that we have to do to make it work each time for people? We have such stuff that we've done to the core. And you know, it's a little bit like a lean week. I think last week you mentioned it was like a Linux distro. You have the same kernel, but the distribution then what's enabled in the modules and like any changes, like Raspbian is based heavily on Linux, but they do make changes to the kernel and they make changes to the way they package things in the file system. It's very simple. The kernel functionality is the same between MicroPython and CircuitPython, like the parser and like, you know, whether we support async or, you know, F strings, that all comes from MicroPython. And then CircuitPython adds API changes on top of it. And sometimes there's a little bit more conflict and like the changes affect the same file. And so doing the merge where we pull in all the changes from, you know, MicroPython. And of course we also send stuff upstream as well. We send bug fixes and changes and updates to them. But getting it to sync up right, it's non-trivial. People who've done merges, they know. It's like it can be hundreds and hundreds of files that are edited and it's like you have to make sure that you stick them together perfectly. So I think Scott's probably gonna end up doing a video or something about this or maybe Dan. Well, yeah. So Scott and Dan and Jep are all worked on this merge, but it's compiling and it's passing CI. So it's now on to test. And we're also gonna update ESP5, the IDF5. That's also coming up next. We want to do the merge first. Could we figure that was tough for everybody to do that? And then we're gonna do ESP5 because it's gonna come in with a lot of fixes and updates and we'll let us support more expressive chips. Which is, yeah, 18. All right. Well, if you wanna keep up on all these and more, we deliver this newsletter. Every single week go to AdafruitDaily.com separate site because we don't want your customer information mixed in with newsletter stuff. So that's why we made another site. Well, AdafruitDaily, we don't spam. We don't share the information. We hate spam and all of that just as much as you do. Maybe even more.