It’s Been A Hell Of Week

This week has been absolutely crazy so far. There is just an endless amount of interesting things. So, we thought we would break down some of the wildest stuff that has happened this week. Claude Code's source code got leaked. Axios was hacked. And uh that's major for some various reasons. There's something called pretext which had every single person on the internet tweeting about text rendering. It has been absolutely wild. My name is Scott Tinsky. I'm a developer from Denver. With me as always is Wes Boss. What's up, Wes? It's Tuesday and I can't believe everything's going Tuesday, my dudes. Unbelievable. By the time you listen to us, it'll probably be about a week later, but like we're going to get into it and talk about I think there's some good lessons to be learned here. Um, as well as just like interesting tidbits to to dive into. So, let's start with the first one, which is like Claude Code leaked. So what happened was is the exact same thing that happened with the the Apple app store which is um when they publish a website you have what's called a source map and a source map takes your like minified bundled mangled code and then it will simply just like point to where in the like the parts of the code where it was unminified. Um, and when you do that, you're able to actually see what the unminified code looks like. And then it also includes things that were maybe dropped during compiling. Most notably, that's often like comments and things that are are dipping in there. Um, and Cloud Code published their source map. It was 60meg file. They published it to npm. In the case of Apple, it was just simply on their website. You open up dev tools, um, and it downloaded. And and generally I don't know this it's not generally something you want on your website if you're your like client code is something that is somewhat sensitive because like you're still shipping the code to the user but you're essentially giving them access to the uncompiled version. You can see their folder structure, how they do CSS, all the comments, all that crazy stuff. Yeah. You know, it's so funny when we uh when CJ put together that Apple source code video leaking, people were like, "This isn't this isn't leaked. This is just client side available code." Like, man, this source map stuff is real. And like, uh it's it's wild to see definitely to peer inside of things. I I I've been like just waking up to see all of this information, so I haven't had a chance to dive into this thing yet. Yeah, I I did a quick little look and the first thing I do of course was I looked for the spinner verbs. So when you run cloud code, it'll say things like flumxing or envisioning or whatever. And I was always curious if those were like AI generated, but I've I've seen specifically I've seen halalooing more times than I can count. Um so I immediately went in and looked for it and yes, there's 187 uh spinner verbs in there. And and this is not something that like you would have been able to find this out previously because like you can't the thing about like strings is that you can't encrypt them or like compress them because they're they're strings that need to make it into the final thing. So you probably could have found this previously, but I thought it was kind of interesting to take a look at it. Um, another thing they had was they're they've when they share like five character IDs, um, when you're you're handling channel permissions, they just generate a random five thing from the alphabet, right? They take L out of it cuz it looks too close to a one. Um, and then they also have this like huge avoid substrings, which is just bad words that may possibly Wink Poo. I'm not going to say any of the other ones. Wes, we got to blur those. Some of those are actual slurs here, so yeah, you don't want to Randy Randy will blur them. Um, and then the last one here was that when you swear at cloud code, it actually flags it with a reax. Um, surprisingly, and so if you say like garbage, what the hell? Um, and many other terrible things which is like, don't swear at the robots, folks. They're going to come get you. But basically, I was I was surprised to see that was an Englishon reax. And then when when they detect that it is a negative prompt, it's sent to their analytic server as a negative prompt. They probably use that for like reinforcement training. Uh being like, "No, that was that was not a good one." I think some of my most sent messages to AI are you [ __ ] you eat, please bleep that out, editor. Yes. Yeah. Um so my question is like is is this a big deal that that this happened? Obviously, I feel bad for they're like DMCAing it. They're taking it down. anyone that's forked it. Interestingly, somebody converted the entire thing to Python and now they're having trouble having that taken down because it's not technically the code. There's this whole crazy world now where like interesting. It is their code. You're just you're just going around it by converting it to Python. Um but like is this a big deal that that this happened? Like this is the this is not their model. Their model did not leave, but it is all of the code behind the CLI, the desktop app, the SDK, all of that type of stuff. and and this was code that they were just willingly giving you. Um, but now it's simply just easier for you to deconstruct it because you have the the source map. So, I don't know that like somebody like like OpenAI is going to be like, "Oo, now we have access to the all of their components and things like that." Yeah. Yeah. Um, I don't know. There's probably a couple little tricks here and there, but I I don't think that this is a a like crazy game changer. You could always give Claude a bundled thing and ask it to decompile it and it does a pretty good job at that. Yeah. What's so funny here, Wes, is that uh this is kind of on the heels of this whole conversation about people hitting their Claude code limits way faster. So that's been a major topic of conversation. People have been leaving comments on our videos even asking about this where in claude code what was happening is that you were hitting your limits much faster recently. Now, uh I they haven't had any official statement here, but someone on Reddit did dive into this and found that there were two major situations where cash invalidation was essentially ruining the prompt caching uh causing you to hit your limits much faster. So, this isn't necessarily the official explanation from Claude that something is happening, but this was a we'll put this link in the show notes for this Reddit post because it was a really interesting deep dive into what exactly is going on. Basically, uh part of their string replacement that they're using to what I understand is to validate billing stuff is one of the bugs that is causing the cache to be invalidated on every request. As far as I'm I did hear I was talking to Kramer at our um syntax meetup and he said yeah there was some he said he mentioned something about there being a cash issue and their their bill went up like 10 grand in one day or something. I don't know what the the output of that actually was but maybe that that was related to this. Um they are also cloud code is is just like like breaking at the seams. Everybody wants to use it. So they've been they've been trying to like enforce off hours like if you have to do stuff that's not like mission critical. It's really funny like they literally say during these times you may hit your limit faster and it's just like there's like 1 hour of like like California lunch where it that just dips right down. That's it's so funny to me that we have all of this power and uh you still see the the lunch break goes down, you know, or uh you've heard of like like tea breaks, the electricity grid in Britain, you know, they have to during commercial breaks for like I don't know what the Brits watch, you know, like Road to Aly or something like that. The electricity spikes as everyone turns their kettle on at the exact same time. Wild wild world, but it is. Yeah. I wonder if we're seeing uh the start of the subsidizing of these these models starting to crack a little bit. I don't know. I'm not smart enough to have the answer for that. Interesting stuff. I think we'll we'll probably get there at some point. Um I don't know if we're there yet because it's still a huge battle between like OpenAI Codeex, Cloud Code, you know, Gemini, like I hear Grock's going to be dropping their own coding model relatively soon. So, everybody is just trying to like capture that huge audience. So, they're probably going to be subsidizing it for as long as possible. Yeah. Yeah. Uh and and and in that regard, like right now, just spend as much tokens as possible if you're not paying for the API, if you're on one of those Max plans. Uh next one we have here is Axios had a hack which was was kind of scary. Um so Axios obviously like a huge kind of fetch replacement um it is still even though we've had for fetch for many many years um it is still very big because it is a dependency of of many things people have older projects that they don't want to move off and there are several little nicities of Axios that allow you to that are much nicer than just using fetch. We did a show many years ago like why are people still using Axios. Um, and I I no longer use Axios in any of my projects simply because most of the stuff like cancelling requests or having timeouts, most of those have been implemented in the platform now. But a lot of people still use it. Bazillions of downloads every single day. And one of the core maintainers had his credentials stolen or or hacked or something like that. They released a 4.2.0 which nice hacker that was that was cool. um which is a clean they call it a decoy copy um and there was no there was nothing in there um and it basically just was like like a full version um and then what they did is they released a point version which if you know about sever if you release a point version and you have like 4.2.0 zero specified in your package JSON then npm installing will will install any if it depends on if you have like the tilda or the squiggle I have a whole video on it but basically for most people when you install it will just install the the newest version so there was a thing on here that drop it's called a rat I had to look this up it stands for remote access trojan um essentially what it does is you install it it runs a post install script and and then that will install a remote access Trojan on your machine and then they can they can do whatever they want um on your machine which is is kind of scary. Yeah, luckily I don't know people caught it relatively quickly. Um I I didn't hear of anybody getting hacked yet, but certainly people have installed this and and run the code. So I would certainly check your your package lock json for the specific versions mentioned here. Yeah, it's so funny. I' I've never knowingly used Axios as in like none. I've never installed it myself and and not like what you're saying. Yeah. Yeah. Yeah. But I did a search for Axios on my computer just to see how many copies of it I have in which projects. And the thing that was the most interesting for me was that the only one I have, believe it or not, is my clawbot, my open claw. It's the only one, which is probably uh not great, but yes. Yeah. Well, that was a kind of the scary thing is like even if you don't use Axios, the probably one of your packages uses Axios down the line and if it's anywhere in your dependency tree, then you're you're going to get in trouble. You know what I find interesting about the the fact that it is Axios besides the fact that so many things use Axios is that if if since OpenClaw does use Axios, I like wonder if that was a targeted. Now you got all these like people who aren't developers installing Open Claw and just yoloing everything. It's like a slot factory. Like is was that was that like a target, you know? Yeah. Like what's what's the endg game of these things? Like previously it was people trying to like steal your crypto, but now I think like I had somebody email me the other day and they said I can get you what's called residential proxies. And I was like, residential. And I was like, oh, the hardest part of being a spammer is getting like clean IP addresses. And if you're running these things on like a bot farm on like some sketchy server farm, then your IP address is going to get flagged for that type of thing. But if you run them through IP addresses of like legitimate like Comcast at at someone's house, like that's that's a huge asset. So, I almost wonder if these types of things are like I simply just want to run a very quiet proxy on they'll probably be looking for banking information and whatnot as well, but simply just having an army of computers is is a huge thing and an army of clean clean IP addresses that can yeah, I don't know do all kinds of bad things. The question of like how how do you stop this from happening, right? Because every time this type of thing happens, everyone's like, "Oh, you shouldn't be doing that. You should be like hard coding absolutely everything." And and the reality is is that like the entire software ecosystem is built on dependencies. You know, this has happened to Linux. It happens to node a lot because our our ecosystem is very big and this whole like nested dependencies is a very big problem. There are many like looks like the step security, I haven't heard of them, but they had a really good write up on it. Socket.dev for his stuff is really good. They seems like they caught a lot of that type of stuff. But the the very minimum thing you should do is if you're using like PNPM, um you can put a minimum release age on your things there. And what that will do is you can simply just wait one or two days to update your your dependencies. And and what and what that'll do is it'll give you a couple days to just make sure everything is is good. you know, like this type of thing was caught within hours and that way you're not accidentally npm installing something that has a malicious value in it. Yeah. And I would say PNPM does such a better job at this than most. Like there's the uh the thing that I find to be annoying is probably for the best where there's uh you have to approve scripts in PNPM. Like sometimes after you install things, it will say, "Yeah, you need to run PNPM approve." uh builds or approved scripts or whatever that is. So, shout out to PNPM for actually doing something good. It's that's a tricky thing because like like a post install script is sometimes handy where like you install this thing and now you need to to do a little bit of setup that is specific to your machine, but also it's kind of scary that simply just installing a package is able to like execute code on your computer. Yeah, it's at least good to have that even if it might be obnoxious at the time that like um but I think the whole I don't know the whole sandboxing is going to get a lot more popular as as we're just running random code from agents. I know a lot of people right now are just like yoloing it running everything on a single computer dangerously accept absolutely everything because that's just the fastest way and it has access to everything. But I think we're in for a couple couple years of hurt with with stories like this until the models can get better at detecting like cuz it's clut code is so annoying when you have to like sit there and approve everything you know or you have to make an array of things it's allowed to do like yeah of course you can you can like read a file that is in this directory but no you shouldn't like rm my entire database right yeah it it's I think this is this is if you think this is a one-off thing, I you know, this is just going to get more and more common for sure. Yeah. The next one we have here is pretext. Now, pretext is a a a new library or you could say a new uh package from the creator of React Motion and was he a member of the React team itself at some point? Yes, core contributor to React. um also was one of the guys behind what's the O'Camel language re you know smart guy yeah reason smart guy to to say the least yes and this library uh is basically a way to measure text in a highly performant way and Wes this is one of those ones where I see the demos and like many of other people at first I'm like okay CSS can do some of this. Uh like like one of the the um accordion example he had showed doing animating from zero to height auto. I'm like a CSS can do that. Uh at least modern CSS can like what is this actually getting us? And you dove into it considerably more than I did. So, I I'm interested to hear what your thoughts are on this considering uh a lot of people what they did is they saw the demo which was a bunch of orbs passing through text and the text moving around and there's so many bad takes where they're just like why would I ever want the text to move like this? Like that's it's a it's a tech demo. It's not a a UI demo. Well, all of the demos were simply just like doing funny things with the text. Like this one where someone the text is getting out of the way of your your thumb, right? Oh, that's pretty cool, actually. Yeah, that actually was really cool. Um I I made a couple demos where like I did like a video of myself and the text was just falling around the video of myself. Um there's some cool demos around different algorithms for justifying text which is I didn't even realize this was a thing you know like like text align justify that that is just a thing but there are different algorithms that make it much more readable um to enjoy. So what this is is it's a library for simply measuring text without having to append it to the DOM. So right now like here's a little demo I have with like something like fit text. This is the way fit text works is that you you just increase the font size every time and then as soon as you hit the font size that is larger than what container. Yeah. Yeah. I'm I'm too big here. Then you you back it up one and then you're you're at your final value. Um and and that requires you to update the DOM in this case I don't know nine times. read the DOM size and then like even if this is obviously slowed down here to to show the visual but even then if you were to do it instantly it's still a visual flicker where whereas this you can simply just measure how big text will be um it does it via canvas it parses every single word it measures them all it caches them it does it does it really quickly this to me is one I I know this is like one of the minor use cases for this but I I actually maintain spelt fit text which is like an action And that does. So I have experience with fit text to see that is like oh that rules because I always found that process to be unusual where you're just like looping and making it bigger. Oh, it's too big. All right, back off. And then you have to choose what that interval is. So yeah. it's a very cool implementation. Um, and I think the use case of it is is not yet revealed. Um, I'm doing a video on what I think it is, but this is this is one of the guys that worked on the virtual DOM for React. Basically, someone that looked at the browser and looked at the DOM and said, I'm going to build my own. Now, he's looking at the DOM and sizing text and goes, I'm going to build my own. So there's there's kind of like two things I'm I'm thinking here is is either he's making an entire like this is a primitive to something that is much bigger like like a React Native where he's building an entire UI ecosystem that renders not to the DOM but will render to like like canvas or OpenGL or Metal or or like like something that is native or and I think I think that this is probably it is that I think that he works at Midjourney and I think Midjourney is working on like a Figma competitor. And a lot of these new Figma killers that are coming out right now, they are all built in web tech. Um, and what that allows you to do is you you can use claude or whatever to build something in these apps like paper pencil is one. And then when you go when it comes time from going from design to code, it's a lot easier because your design was done in in web tech. Um, and then the other way is is great as well is if you cla make a website and you want to bring that into a design app, it's a lot easier to take an existing website and put it into um like a Figma, you know, it goes both ways. So, I bet that MidJourney is working on something like this and part of their app that they need to do. They hired the like rendering guy, you know, they're probably building some super performant Figma like application and part of that is you have to figure out how to do text. Um, you got to figure out how to size text properly and and know how big things are and and figure out if it should wrap or not. Like that's what that's exactly what this thing does. So, I bet that this is a primitive for that type of thing. And also, if you go to the midjourney website, look at look at right here. It says projects. Over the coming months, we're unveiling a wide range of ambit ambitious projects over the themes of imagination, coordination, reflection, beauty, and human flourishing. But look at this one. TBA software. What's that? A pen. TBA software. What's that? If you inspect element on this image, it says people.png. So, this is going to be a collaborative app. for doing designs and then you investigative dev work here. Well, I could be wrong. I thought I thought Dino was going to get bought by Open AI and I was wrong about that. But this is just my crazy Yeah. No, I I like I like all these uh cuz you're you're not like just shooting in the dark here. I I do find this the one of the things that I think a lot of people that a question about is because when they see some of these things, they think, "Oh, is this using canvas?" Right? Is canvas involved here? Um, and canvas is doing the measure that measuring. That's correct. Yeah, canvas is doing the measuring. Y, but it's not doing the actual uh rendering at the end of the day because I I did see comments being like, how could this be accessible if you're just doing canvas, but all of the demos have text on the DOM? They're just getting the measurements via canvas. It it can be either. So essentially there is a prepare function which will measure all the words and then there's a layout function that you pass it a width. So you say lay this out given a 500 pixel width and then it will figure out where the wrapping and everything goes. And what it gives you at the end of the day is simply just the text and the words the and the width for that one. And then it's up to you to figure out what to do with that. So you could just write this to canvas, which I think this is a huge use case. Writing text to canvas right now sucks because there's no word wpping. But so now we have word wrapping in canvas. You can just use this. Um but all most of the demos people are simply just absolute positioning this. So this is movie. I absolute position every single word in bem movie and it took 42 milliseconds um to parse and then one millisecond to lay out and then that means if the layout changes you don't have that initial 42 milliseconds and and that's why all of these demos are like stupid like things because he wanted to show how fast it was that you can literally lay out text at 120 frames a second no problem and and that's why it was Nobody's actually building these like silly editorial layout type of things. Yeah, I I think there's there's a couple of classes of bad takes on this. One, there was the CSS can do this already or this is dumb kind of take because that's not really what this is about. Two, the the bad take uh on uh the demos being unusable. The demos are just tech demos, folks. They're just there to illustrate how uh like the the limits that you can push this type of thing. They're not meant to be like, oh yes, we should be reading a blog post with moving text. That's not like what these are about. Another bad take I saw on this was this changes absolutely everything. The web will no longer dead. So many takes like that. They're crazy. Uh the Liam like what's so weird about this is for being something that is like nerd interesting, it really blew up in an odd way of people either hating on it or thinking it's like uh going to be uh you know curing all disease. It's unbelievable that people would would say CSS is dead because like you do not want to be laying out your text where everything is absolutely positioned and you give up all of the the benefits of the flow of the DOM. Um, in some cases, yeah, you do, but in most cases, no. Like if if we were the other way around where we were manually looping over segments and laying out sentences one by one and then somebody came out with the fact that you have relative positioning. Game changer. A game changer. Wait, you just put a paragraph and the the image goes below it. It you don't have to position it, you know, like that would be hilarious. Yeah. But here here's one more thing. A lot of people were saying CSS can do this and they're linking all these demos. Here's one of them where we have shape outside in CSS which allows you if you have an image you can float it left or right and then your text will wrap around it. And I was like I was working on a video a couple months ago being like why is nobody using this? And then I started like building something. I was like oh it's cuz this sucks. It doesn't actually work very well. Um like this example right here. There's a girl and then text is going around it. First of all there's two columns. You have to manually figure out which what text goes in those two columns, right? And so you're you're kind of out of luck there. And then also this girl is like literally had split in half so that you can float one left and one right. There's there's no way there's no like clear both in in CSS where you can like wrap text around an object. It either goes to the left or to the right. So like again this is a cool demo but like there's a reason why you don't see websites using this because it it doesn't work very well. Yeah. And to me that's like that type of layout is maybe even like the least captivating part of any of this. So yeah, last one here. And this one is not to necessarily dunk on railway, but it's more of like a an interesting thing I think all developers should know because this is kind of a a scary security thing that people don't necessarily think about. So, Railway had an incident where they changed something with their CDN and they accidentally cached private pages and then shared them uh between that domain. So, the way that this works is if you have like a page where like I'm logged in to my bank.com/accounts and you I I render out the page that shows all of my account balances. If you cache that page like just simply the caching the HTML or any other resource you're putting you put that you can throw that into in either cache it in the browser you can cache it in a private CDN or you can you can cache it on a public CDN. Um and and things like your homepage for your bank may maybe want to be cached but stuff that has private information you shouldn't be sharing that cash between the two. Right. Yeah. And what happened with railway here is that they they changed something with how their CDN worked and then people were starting were loading pages of of applications and realizing I'm this is not my data like why am I seeing stats for somebody else. There were several instances where people had like medical information and people were seeing medical information for other ones and that's because the cache was not scoped to the user. It was a it was a u a public cache which is a huge security issue right um caching lot how many of these issues are caching cash ruins everything around me cash is always the biggest problem that I have here so that sucks I want to talk real quick about like how do how you can you avoid this because this this kind of happened to us on luckily it wasn't security issue but this happened to us on the syntax website where we had user specific themes themes. So, you go to the syntax website, you set a theme to be like dark or like synth wave or something like that, and then when you visit a page, we the the theme is sent in a cookie, and then we server render that theme with all of the classes on it. And the first person who would go to uh like like a random page, if they had a different theme than what you had, what would would happen is that that person's page would be the cache and we stored that in the cache, you know? Um but really that that person's theme and their CSS that was specific to them and that shouldn't have been like shared amongst other people, right? And we were trying to be smart by like server rendering the theme so you wouldn't get that flicker. Yeah. No flash all all in the just to improve the server response there. The remove the flash of unstyled content. Uh luckily this wasn't tied to user accounts or anything. Just user preferences and you would just get a random like flash of r somebody else's theme on random pages. So how do you avoid this? Um don't cache private pages um or or maybe cache the templates but don't c the actual data. um use the cache control private header. So meaning that it's not cache control public. It's not going to be shared amongst a a public one. You can also there's also a vary header where um if you're like caching a resource, you can set a very header on it for like something like the user ID or the user cookie, something like that. and then and then that will make sure that okay I will cache it but I'm going to use this specific piece of information to cache for that specific person. Um although Cloudflare doesn't support the very head header. I know Netlefi does. Um I was talking to Matt from Netifi about this specific problem when we had it on our theme um as well. So essentially just like I would probably say don't catch sensitive information like that because that's a whole another HIPPA compliance problem that you're gonna have. Yeah, man. This stuff is tough. Uh we're dealing with all kinds of stuff on the web. But uh be careful out there, folks. Stay safe. Stay safe. Yeah, stay safe. Uh let's get into the point of the show where we talk about sick picks. Wes, do you have a sick pick for us today? Boy, do I. So, I like that. Boy, do I. Man, so every couple years I go through like like a chargers. Um, and I think, man, I need I need like a better charger for this type of thing. And like one thing I hate is super dog slow chargers that can't like, oh, you can't charge your laptop on this one. It's not as good. Or like, uh, my phone is dead. I can I can charge to 80% in like 20 minutes, but I don't have the proper charger. So a couple months ago I bought this U green 200 watt 8 port GAN charger and it has one two three six USBC's two USBAs. It's like super high quality. It's all metal. If you go on Amazon and you search for chargers you're going to see like people are like 700 watts for 20 bucks and like be very suspicious of high claiming chargers that are very cheap because they they don't exist. Um, but I've landed on this UG Green 8 port one and I got it for all the kids because all of our kids, we've got what, three or four iPads. We've got they all have headphones that need to charge and then there's several other things like um we got a Meta Quest VR thing. You did? Yeah. Awful. Absolutely. Oh man, makes me want to puke. We'll talk about more about that later. I want to see if I can get React Native running on it, but oh my god, we got to charge all that stuff. And it's so nice having a like high quality charger that will charge nice and fast. You can put plug your laptop into it. I know USBC's been around for a long long time, but I'm like we're almost at a point now where the whole world is USBC and it will just everything will charge on it. So, I bought another one because I was like, I want one from beside my bed and I want to be able to I was having problems where like some stuff wouldn't charge or wasn't charging fast enough with like a crappy old one I have. And I'm like, I'm sick of this. So, get the UG Green 8 port. Big fan of it. Yeah, I need one uh by my bed to charge my computer while my agents run while I'm trying to sleep. Well, that's the thing is like beside my bed, I've got like a Apple Watch charger and then I have like a dock, like a Mag Safe dock, but then I also have USB C to charge my phone and I have another one if I want to charge my computer at the same time. And then like there's several other things and it's kind of getting away from me. And then I also realized that you can get these like USBC to barrel connectors and like if you have something that is running on like a 12vt 8 volt, you can just change out your barrel connectors for USBC. So, I might do that as well. Yeah, just standardize. Yeah. Yeah. The Google Home has a little barrel jack on there and you have to plug it into the wall. I was like, I could probably get a USBC for that. Yeah. Okay. I'm going to stick pick uh something in along something that you might charge with that, which is for Christmas. We got our kids color soft Kindles. They make Kindles for kids. And we got these color soft. So, it's a color Kindle for kids. They have a kids account and they are just downloading all kinds of graphic novels and comics on here. You can do audio books on these. Now, the only problem with the audiobook stuff is that they do need Bluetooth headphones for some stupid reason. There's no headphone jack on them. So, our kids have to use Bluetooth headphones and then we have to keep the Bluetooth headphones charged. But like both of our kids have been going nuts for these because they're just at the right age where my daughter can read now and my son is like really getting into comic books and graphic novels and he's like reading all these different kinds of comic books that are available on here. And I got to say the the product I've never had a Kindle personally um but the product is really good. Now you are locked into the whole Amazon ecosystem of things. Yeah. And there is that that Bluetooth headphones thing, but the actual device and reading experience on this is so good. And our kids just cannot put theirs down. They are reading every single night. So for me, that's like a huge huge win to see them so like interested in reading as opposed to watching TV or playing games or something. Cool. Man, I'm going to give you another stick pick right now. We've had these for a long time. the wise noiseancelling Bluetooth headphones. I was like a Bluetooth headphone hater for the longest time for the kids because a they they break everything that you give them. Like they're so rough on them and like b like I I was at a point where I was I was putting replaceable headphone jacks in all of our headphones because like they would always like mash the end. And then finally when they got new iPads, there was no headphone jack obviously. So I was like, "All right, we got to get some some Bluetooth headphones." and they have been fantastic. So, we had for two years we had Wise noise cancelling headphones. They're super high quality. They held up to all of the abuse and after 2 years we like one of our kids broke them and I had to glue them back together and we got him another set because they go on sale right now. They're on sale for 35 bucks. Um, and they battery lasts forever. They're the most comfortable headphones aside from my Bose QC35s. They're probably the most comfortable headphones I've ever worn and they're noise cancelling. The kids love them. And like if you need headphones for your kids, get them. Like they leave them on all the time, you know, but it doesn't matter. Battery lasts forever and they charge USBC. Yeah. Very interesting. Cool. I never even seen that. That's Yeah, they're they're fantastic. We're on like almost three years with them now. So, I I almost almost tempted to buy like a whole stock extra of. They're so good. Uh, one to stock and one to rock. I gota All right, cool. Well, uh, anything else before we get out of here? That's it. Use Sentry sentry.io/sintax. Peace. Peace.