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, 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 Tillensgama, developer from Denver. With me, as always, is Wes Bos. What's up, Wes?

It's Tuesday, and I can't believe everything's going down. My dudes. Unbelievable. By the time you listen to this, it'll probably be about a week later, but, like, we're gonna get into it and talk about I think there's some good lessons to be learned here, as well as just, like, interesting tidbits to to dive into. So let's start with the first one, which is, like, cloud code leaked. So what happened? It was it's exact same thing that happened with the the Apple App Store, which is, when they publish a website, you 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.

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.

And Cloud Code published their source map. It was 60 meg file. They published it to NPM. In the case of Apple, it was just simply on their website. You open up dev tools, and it downloaded. And and generally I don't know. Node it's not generally something you want on your website if your your, like, client code is something that is somewhat sensitive because, like, you're still shipping the code to the user, but Yeah. 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 Wes we, when CJ put together that Apple source code video leaking, people were like, this isn't this isn't leaked. This is just client Node available code. Like, man, this source map stuff is real, and, like, it's it's wild to see, definitely, to peer inside of things.

I I've been,

like, just Wes 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 flummoxing or envisioning or or whatever. And I was always curious if those were, like, AI generated, but I've I've seen specifically, I've seen hullabalooing more times than hullabalooing can count.

So I immediately went in and looked for it, and, yes, there's a 187, 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 kinda interesting to take a look at it.

Another thing they had was they're they've when they share, like, five character IDs, 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 because it looks too close to a one.

And then they also have this, like, huge avoid substring, which is just bad words that may possibly Wink,

pee, poo.

I'm not gonna say any of the other ones. Wes, we gotta blur those. Some of those are actual slurs here. So Yeah. You don't wanna Sanity, Randy will blur them.

And then the last one here was that when you swear at cloud code, it actually flags it with a regex, surprisingly.

And so if you say, like, garbage, what the hell, and many other terrible things, which JS, like, don't swear at the robots, folks. They're gonna come get you. But, basically, I was I was surprised to see that was an English only regex. And then when when they detect that it is a negative prompt, it's sent to their analytics server as a negative prompt. They probably use that for, like, reinforcement training.

I mean, no. That was that was not a good one.

I think some of my most sent messages to AR are you you. Eat.

Please bleep that out,

Esther. Yeah. Yeah.

So my question is, like, is is this a big deal that that this happened? Obviously, I feel bad for they're, like, DMCA ing it. They're taking it pnpm, 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.

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. No. 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, 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 gonna be like, oh, now we have access to their all of their components and things like that. Yeah. Yeah. Yeah. Yeah.

I don't know. May 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, this is kind of on the heels of this whole conversation

about people hitting their cloud 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 Wes, in cloud code, what was happening is that you were hitting your limits much faster recently.

Now, 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 cache invalidation was essentially ruining the prompt caching, causing you to hit your limits much faster. So this isn't necessarily the official explanation from Yeah. Claude that something is happening, but this was a a Reddit post because it was a really interesting deep dive into what exactly is going on. Basically, 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, 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 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.

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, one hour of, like like, California lunch where Yeah. It that just dips right down.

That's it's so funny to me that we have all of this power, and, you still see the the lunch break goes down. You know? Or, you've heard of, like, like, tea breaks, the electricity grid in Britain. You know? They have to Yeah. During commercial breaks for, like, I don't know what the Brits watch, you know, like, Roe Taverny or something like that. The the electricity spikes as everyone turns their kettle on at the exact same time.

Wild wild wild world. But It is. Yeah.

I wonder if we're seeing, 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. Yeah. Interesting stuff. Yeah. We'll probably get there at some point.

I don't know if we're there yet because it's still a huge battle between OpenAI Node, Cloud Code, you know, Gemini. Like, I hear Grok's gonna be dropping their own coding model relatively soon.

So

everybody is just trying to, like, capture that huge audience, so they're probably gonna be subsidizing it for as long as possible. Yeah. Yeah. 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 out of those Max fans.

Next one we have here is Axios had a hack, which was was kind of scary.

So Axios, obviously, like, a huge kind of fetch replacement.

It is still even though we've had for fetch for many, many years, it is still very big because it is a dependency of of many things. People have older projects that they don't wanna move off, and there are several little niceties of Axios that allow you to that are much nicer than just using fetch. Wes did a show many years ago, like, why are people still using Axios? And I I no longer use Axios in any of my products simply because most of the stuff, like canceling 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 four point two point zero, which Node hacker. That was that was cool. Which is a clean they call it a decoy Scott.

And there was no there was nothing in there. And it basically just was like a like a full version.

And then what they did is they released a point version, which if you know about SemVer, if you release a point version and you have, like, four point two point zero specified in your package JSON, then npm installing will will install any. It it depends on if you have, like, the tilde or the squiggle. I have a whole video on it. But, basically, for most people, when you install it, it will just install the the newest version. So there was a thing on here that dropped it's called a RAT. I had to look this up. It stands for remote access Trojan.

Essentially, what it does is you install it. It runs a post install script, and and that will install a remote access Trojan on your machine, and then they can they can do whatever they want, on your machine, which is is kinda scary.

Yeah. Luckily Yeah. I don't know. People caught it relatively quickly. 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've I've never knowingly used Axios as in, like, none I've never installed it myself. And and and Node 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 and 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 clawed bot, my open claw. It's the only Node, which is probably, not great.

But yes. Yeah. Well, that was a kind of the scary thing. It's like, even if you don't use Axios,

probably one of your packages uses Axios down the line. And if it's anywhere in your dependency tree, then you're you're gonna 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 since OpenClaw does use Axios, I, like, wonder if that was a targeted now you've got all these, like, people who aren't developers installing OpenClaw and just YOLO ing 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 endgame 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 pro 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 gonna 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 wanna run a very quiet proxy on they'll probably be looking for banking information and whatnot as Wes, 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. Yeah. The the question of, like, how how do you stop this from happening? Right? Because every time this type 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. Scott dot dev for Bos. His stuff is really good. They it 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, 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.

Yeah.

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, the thing that I find to be annoying is probably for the best where there's, you have to approve scripts in PNPM. Yeah. Like, sometimes after you install things, it will say, yeah. You need to run PNPM approve, build or approve scripts or whatever that is. So shout out to PNPM for actually doing something good.

It that's a tricky thing because, like like, a post install script is sometimes handy Wes, 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 kinda scary that simply just installing a package is able to, like, execute code on your computer.

Yeah. It's at at least good to have that even if it may be obnoxious at the time, that, like Mhmm.

But I I think the whole Yeah. I don't know. The whole sandboxing is gonna 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, YOLO ing 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 because it's a cloud 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. Like, 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 gonna 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, package from the creator of React Motion. And was he a member of the React team itself Yeah. At some point? Wes. Core contributor to React,

also was one of the guys behind what's the OCaml language? Re Reese's ML. You know? Reason? Smart guy. Yeah. Reason smart guy, to to say the least. Yes. And this library,

is basically a way to measure text in a highly performant way.

And, Wes, this is one of those ones where I see the Deno, and, like, many of other people at first time, like, okay. But CSS can do some of this.

Like like, one of the the, accordion example he had showed doing animating from zero to height auto. I'm like, ah, CSS can do that.

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, 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? So, like Yeah. 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. Yeah. Like this one Wes someone the text is getting out of the way of your your thumb. Right? Oh, that's pretty cool, actually. Yeah. Act that actually was really cool.

I I made a couple demos where I, like, I did, like, a video of myself, and the text was just falling around the video of myself.

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 Of course.

It much more readable, 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 Node, like, here's a little demo I have with, like, something like fit text. This is the way fit text works JS that you you just increase the font size every time, and then as soon as you hit the font size that is larger than the one that you're doing. 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.

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.

It does it via Canvas. It parses every single word. It measures them all. It 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 I actually maintain Svelte fit text, which JS, like, an action that does Yeah. So I have experience with Fit Text. To see that JS 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. Alright. Back off. And then you have to choose what that interval is. So Yeah. Yeah.

It's a very cool implementation, and I think the use case of it is is not yet revealed.

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 gonna build my own. Now he's looking at the DOM and sizing text and Node, I'm gonna build my own. So there's there's kinda, like, two things I'm I'm thinking here JS is either he's making the 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 ideas. Figma killers that are coming out right now, they are all built in WebTech.

Mhmm. 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.

Yeah. And then the other way is is great as well JS if you have Claude make a website and you wanna bring that into a design app, it's a lot easier to take an existing website and put it into, like a Figma. You know? It goes both ways.

So Yeah. 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.

You gotta 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 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 gonna be a collaborative app for doing designs, and then you Look at this investigative dev work here. Well Yeah. I could be wrong. I thought Node thought Deno was gonna get bought by OpenAI, and I was wrong about that. But this is just my crazy

Yeah. No. I I like I like all these, because 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 Wes about is because when they see some of these things, they think, oh, is this using Canvas? Right? Is Canvas involved here? And Canvas is doing the measure. That measuring. That's correct? Yeah. It Canvas is doing the measuring. Yep. But it's not doing the actual 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 Well 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 wrapping. But so now we have word wrapping in Canvas. You can just use this.

But all most of the demos, people are simply just absolute positioning this. So this is Bee Movie. Yep.

I absolute positioned every single word in Bee Movie, and it took forty two milliseconds.

Crazy.

Node parse and then one millisecond to layout. And then that means if the layout changes, you don't have that initial forty two milliseconds. And and that's why all of these demos are, like, stupid, like, things because Yeah. He wanted to show how fast it Wes, that you can literally lay out text at 120 frames a second Deno problem.

And and that's why it was but 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 Yeah. Take because that's not really what this is about. Two, the the bad take, on, the demos being unusable. The demos are just tech demos, folks. They're just there to illustrate how, 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 Node, like, what these are about. Another bad take I saw on this Wes, this changes absolutely

everything. The web will no longer be the same. Dead. So many things like that.

They're crazy.

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, going to be, you know, curing all disease.

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.

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. What that 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 Yeah. 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 Wes 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 because this sucks. It doesn't actually work very well. Yeah. 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 kinda 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 in objects. 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 Yeah. It doesn't work very well. Yeah. I 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 cashed private pages and then shared them, between that domain. So the way that this works is if you have, like, a page or, like, I'm logged in to mybank.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.

And and things like your Node page for your bank may may be want to be cached, but stuff that has private information, you shouldn't be sharing that cache be 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 incidences 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, a public cache, which is Yeah. A huge security issue. Right?

Caching. A lot how many of these issues are caching?

Cash ruins everything around me. Cache is always the biggest problem that I have here. So that sucks. I wanna 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 Sanity issue, but this happened to us on the Syntax website where we had user specific 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, like like, a random page, if they had a different theme than what you had, what would what would happen is that that person's page would be the cache, and we stored that in the cache. You know? But, really, that person's theme in 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 all in the just to

improve the server response there, the Yes. Remove the flash of unstyled content.

Luckily, this wasn't tied to user accounts or anything No. Just user preferences, and you would just get a random, like, flash of somebody else's theme on random pages. Yeah. So how do you avoid this? Don't cache private pages, or or maybe cache the templates, but don't cache the actual data.

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, if you're, like, caching a resource, you can set a vary 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 gonna use this specific piece of information to cache for that specific person.

Although Cloudflare doesn't support the very heady header, I know Netlify does.

I was talking to Matt from Netlify about this specific problem when we had it on our theme, as well.

So, essentially, just like I I would probably say don't cache sensitive information like that because that's a whole another HIPAA compliance problem that you're gonna have.

Yeah. Man, this stuff is tough.

We're dealing with all kinds of stuff on the web, but, be careful out there, folks. Stay safe.

Stay safe. Wes. Stay safe.

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 Oh, I like that Node. Do I? Man so

every couple Yarn, I go through, like like, a Chargers, 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, my phone is dead. I can I can charge to 80% in, like, twenty minutes, but I don't have the proper charger? So couple months ago, I bought this Ugreen 200 watt eight port GaN charger, and it has one, two, three, six USB c's, two USB a's. It's, like, super high quality. It's all metal. If you go on Amazon and you search for chargers, you're gonna see, like people Yarn, like, 700 watts for $20 and, like, be very suspicious of high claiming chargers that are very cheap because they they don't exist.

But I've landed on this Ugreen eight 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, we got a meta Wes VR thing. You did. Yeah. Awful.

Absolutely.

Oh, man. Makes me wanna puke. We'll talk Node about that later. I play music. I get React Native running on it. But Oh my god. We Scott charge all that stuff. And it's so nice having a, like, high quality charger that will charge nice and fast. You can put put plug your laptop into it. I know USB C has been around for a long, long time, but I'm like, we're almost at a point now where the whole world is USB C, 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 wanna 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 UGREEN eight port.

Big fan of it.

Yeah. I need one, by my bed to charge my computer while my agents run while I'm trying to sleep.

Well, that's the thing. It's, like, beside my bed, I've got, like, a Apple Watch charger, and then I have, like, a dock, like, a MagSafe dock, but then I also have USB Bos to charge my phone, and I have another one if I wanna charge my computer at the same time. And then, like, there's several other things, and it's kinda getting away from me. And then I also realized that you can get these, like, USB c to barrel connectors. And, like, if you have something that is running on, like, a 12 volt, eight volt, you can just change out your barrel connectors for USB c. So I might do that as well.

Yeah. Just standardize. 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 USB c for that. Yeah.

Yeah.

Okay. I'm gonna stick pick, something in the long something that you might charge with that, which is Alright. For Christmas, we got our kids ColorSoft Kindles. They make Kindles for kids.

And we got these color so it's a color Kindle for kids. They have a kid's account, and they are just downloading all kinds of graphic novels and comics on here. You can do audiobooks 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 Node. 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 gotta say the the product I've never had a Kindle personally, 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 gonna give you another sick pick right now. We've had these for a long time. The Wyze Node canceling Bluetooth headphones.

I Wes, 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's no headphone jack, obviously. So I was like, alright. We gotta get some some Bluetooth headphones. And they have been fantastic. So we had for two years, we had Wyze noise canceling headphones. They're super high quality. They held up to all of the abuse.

And after two years, we like, one of our kids broke them, and I had to glue them back together. And we got them another set because they go on sale. Right now, they're on sale for $35, and the battery lasts forever. They're the most comfortable headphones.

Aside from my Bose QC 30 fives, they're probably the most comfortable headphones I've ever warp. And they're noise canceling. 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 USB c.

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 Hell yeah. I I almost almost tempted to buy, like, a whole stock extra of them. They're so good.

One to stock and one to rock. I gotcha. Alright. Cool. Well, anything else before we get out of here? That's it. Use Century. Century.o/syntax.

Peace.