 Yes. Blink-a, blink-a, blink-a, blink-a, blink-a, blink-a. Okay. Big-ish news. We are approaching CircuitPython9 and with CircuitPython9, that means a bunch of new features and more. What things can people look forward to in CircuitPython9? Okay. There's actually a lot of stuff that's in Parathon9, so it's been cooking. It's been simmering on the stove for a while. Big updates are we've merged MicroPython119, 120, and 121N, so a lot of core library changes, including the MPY format has changed, I think, even twice. We're going to use some language improvements, which is great, and Scott's also working on some memory improvements in 9, but if you're upgrading to 9, you're going to have to update all your library files as well. I think we just updated the bundle to create MPYs for 9. You can see the list here. Some other stuff. We've got more USB host support, some tweaks to I-Squared-C peripheral, now I-Squared-C target. One thing I chat about, Scott, is that we removed stuff like Display.io show, which I think was going to break a bunch of codes. We now- That was a question in the chat. Why was it removed? I should ask Scott. There's reasons. I don't know the API reasons for it, but there must be reasons, because Scott doesn't make breaks unless it really improves something. But now it gives you a warning. It doesn't fully remove it, but it will tell you that it's about to be removed, which is kind of nice because otherwise you'll, or sorry, if it's removed, it'll tell you how to change your code to fix it. It's a very simple fix. I'm trying to think what else. Idea 5 for ESP support has been updated, and I think that's actually improved a lot of Wi-Fi and display stability for the expressive line as well. Okay. Then the other thing that we were going to talk about this week is CircuitPython Blink-A-Python compatibility layer, now supports Raspberry Pi 5. Yes. Melissa, who manages the Blink-A-Python layer, which lets you people use CircuitPython libraries and the API on Raspberry Pi computers. A perfect example of why it was such a good idea that we had this compatibility layer because stuff changed and broke. When the Raspberry Pi 5 came out, RPi GPIO had no longer works on Raspberry Pi, and that was what we were using as the underlying layer. Melissa has updated to use now LibGPIOD, much like other single board computers. It's nice and fast. You had a playground note about how it's nice and speedy for bit-banging, which is great. It now goes to the RP1 chip. And so far, so good. If folks have issues with installing Blink-A-Python or using our CircuitPython libraries, let us know. It seems like iSquared-C and GPIO and SPI support has pretty much all working. And then hopefully, as we learn more about the RP1 chip, I believe there's PWM support, there's native PIOs slash NeoPixel, there's maybe analog input support. We will add that to Blink-A-Python as well. So that'll be really nice. All the APIs that we already had that people are using for my controllers will be able to add even more of them to the Raspberry Pi. And in case you're wondering what we're all about, if you go to circuitpython.org, CircuitPython is kind of our sponsored project. We have our team that does it. We're funding it to have the best experience. We also help fund MicroPython. CircuitPython is the educational fork that works with lots of boards. We now have 448 boards. So right now, most of the boards are non-AdaFruit. Yeah, if you do flip filters, and you click on AdaFruit, which is like right over there, click on that, make it then you can press the X. So we have almost a hundred and there's 448. So we're less than a quarter. Yeah, and so that's important to us because we want to be clear about what we're doing. And the top boards here, they're not from AdaFruit. Yeah, we do open source hardware and we publish all the designs and schematics and code and we want you to use it and do cool stuff. Just don't say AdaFruit, that should come up with a different name. And then for MicroPython, CircuitPython, specifically our CircuitPython work, we want to make it easy for anyone to take a board and have CircuitPython on it. And we don't care if it's our hardware or not. So we want to see more boards out there. We can say things like that. We could use that as a like marketing thing like open and it's great, it's free. But we also want to demonstrate it. And so what we do is we have this list of boards that CircuitPython runs on. And if you just look at which boards from which companies, AdaFruit is not the most. And that's important to us. It means other people are using it. So that was the goal and it looks like it's still happening. And so if you're doing hardware and you don't want to maintain firmware for your device forever and you just want to just work, you can take a look at some of these boards and be like, oh, that's a cool board. I can just have CircuitPython on or I can make my own board, spend it on my own board. And I always get all those updates. No, I don't have any. And also saying actually there's two boards that she's trying to find images for. And so it actually is 450, but like we don't have. Yeah, we'll get there. So we'll update it. And there are eight different products. You know, you can always buy some to support us. But again, like we, this is one of the things we wanted to do for the world. Just like, here's a very cool easy way to do Python on hardware, built on MicroPython has all the cool things you can do with lots and lots of different hardware. One of the reasons that we make CircuitPython is so it runs on a variety of chips. And here it is. So that's our Python on hardware news this week. You can get this update for daily, deliver to your inbox every single week, spam free, tracking free. You don't even need to sign up. You can just go to for daily and look at the link. That's right. It's also on GitHub. And on the permanent web page, we really want to make it easy to do stuff. RSS, do you send it to us? Yes, RSS we do. So we do that. And Google leader it. Yeah, one of the things for folks who pay really close attention to stuff is we've been de-Google-ifying a lot of our properties. You know, Google Analytics, when you have a website, pretty much everyone's Google Analytics on their website. Yeah, yeah, yeah. And over the years, as we've developed our properties, we're like, how do we get out of this? Because we don't make money on views. We don't make money on ads. We don't make money on mining your personal information or selling it or doing anything with it. So why don't we just remove it? So we've been going through the process of making sure, like there's things, if we want to make sure we know like what guide is most popular, there's things that analytics are good for. But we also don't want to have all that information because we don't use it. Why have all this information about what browser you have, what country you're coming from? Who cares? We don't care. We don't use it. So that's also important to us for daily. You don't need to sign up as a newsletter. We use MailChimp and they have their own, tracking with URLs because people care about what's tracked. We don't. So you can also just get it as a standalone web page as well. We're kind of committed to this and that's why I kind of mentioned it every week because I know folks are, you just assume it works. We're like the CEU, we're a search engine unoptimized. Well, you know, and that's good because it's hard to even use web search now. I know. Google search doesn't need more. But I know the tendency is to just assume the worst and think that whatever you sign up for is you're just gonna like put banners everywhere. You're gonna get spam forever. But we work really hard at this tonight. But I also know like, because sometimes frustrating is people just like, well, I know you're just gonna send me information. Like we don't do that, but I get it. I get it. Like if you live in this world, it's not a bad bet sometimes to assume that. So anyways. Thank you.