Stripe Buys OpenRouter for $7B

Welcome to Syntax.

In this episode, we're talking about all kinds of things. SvelteKit three is a release candidate.

We're gonna be talking about tan stack charts, taking a first look at that. Also, Stripe acquired OpenRouter.

We're gonna talk about it, try to figure out why.

All this and more today on Syntax Weekly. I am joined by Scott Tolinski. How's it going, Scott? What's up? What's up? What's up? I am,

I'm I'm feeling good, man. I released my my video on Friday that I've been working on really hard. CJ had been grinding on it as well, in the editing process doing so much to make that thing perfect. So I'm feeling like I have a big weight off my shoulders. If you haven't watched it yet, I I did a survey on mental health and AI coding, and the video dives into that and has a lot of interviews, including interviews from experts as well as, experienced developers and some really great perspectives. If you haven't seen that video yet, immediately following this, go and watch. It's getting a lot of really great, reception. So feeling very light today. And that, well, I'm feeling light because of that, but I'm also feeling heavy because it's Century

Hack Week. Oh, you got the merch. I didn't get the merch. Nice. Yes. I got the merch. It's Century Hack Week,

and I have chosen to do hardware.

And, I don't know if you you probably won't be able to tell by this this breadboard where I just have a single button and a microphone just kinda hanging out here. I don't I'm bad at hardware. I'm very bad at hardware.

So this is going to be an adventure for me. I'll just say that I'm already experiencing the pain of dealing with hardware.

How about you, CJ?

Yeah. I'm I'm getting ready for Hack Week. Also, super excited about the video that you put out. I'm proud of it. You did great work. I it's it's awesome. One of the best videos we've done on Syntax, so definitely check it out. But, yeah, Hack Week, I'm making a Game Boy game. So last year, I made a Sega game. That's actually a Sega game in the background that's spinning the Syntax logo.

But the plan this year, Game Boy game, and if all goes well, we'll release it in a couple of months, and you can buy a physical Syntax Game Boy game to play in your Game Boy. So, yeah, it's gonna be fun. But let's get into it. So I hear there's some SvelteKit

three news. Scott, what's going on over there? So in the last live, I believe I detailed that there was some, action going around in Svelte three land. Well, the Svelte three release candidate is here or SvelteKit release candidate is here, and this includes a bunch of really great stuff. There are some breaking changes, but JS always, the Svelte team does an awesome job of giving you a migrate script. The last migrate script that went from well, one, there was a migration from, woah, sapper to SvelteKit, and then SvelteKit v one to v two have all been wonderful and easy transitions.

This one is guaranteed to be no different.

And SvelteKit three, it's it looks pretty dang sick. So they got rid of a config file. We love the removal of config files. Files. Everything now lives inside of Vite config instead of a Svelte config Scott j s and Vite config. That was always confusing to me because some stuff lived in one and some stuff lived in the other. They also changed how, the lib alias works. They're aliasing things with a, pound sign instead of a dollar sign, reserving the dollar sign for other things, and it's now using the node native, what was it, in package dot JSON subpath imports instead of having it via the configuration there. So that's nice.

And, TypeScript configuration got more simple because of that.

And then the service workers apparently got a face lift as well. Now the service workers, I've used quite a bit in Svelte, SvelteKit, and, we use one on the syntax.fm website and everything like that. So stoked to see that they got a a facelift.

Cool stuff. I haven't used it yet.

And then also, e and v variables. There's an interesting stuff going on with there. So you can see that, like, e and v .ts lets you specify a little bit more.

And then you can also use standard schema to validate your e n v vars and things like that. So e n v vars, one of those things that I tend to use Vercel for because just straight up dot e n v sucks.

It sucks for a lot of reasons. So I'm really stoked to see that these SvelteKit folks are going to be taking this into account with, their explicit e n v vars feature.

And then also check this out.

Shallow routing now happens with go to. Okay? And it will, I believe, validate your route's existing, go to instead of, do you have to use resolve? Let me know. Do you have to use resolve still, with the go to? Resolve is a function that validates all of your routes and stuff like that.

Error handling got better. Apparently, I have not used this yet.

And then, also, what's the, this is the big one to me. They put the big one down at the bottom here.

Remote functions, which have long since been an experimental feature, and they still are an experimental feature.

I wanna see these go stable. I mean, I've been using them, but I see. I was really hoping, yeah, that SvelteKit v three would move these to stable.

But if you know me, I've been using these in production for, like, a year Node, so, they're stable enough.

Yeah. Yeah. I mean, I haven't had any issues with them. I'm sure it's, like, lower level stuff or, like, weird edge cases.

Yeah. Small kit, remote functions, for those of you who don't know, it's like a true kind of, like, almost like an RPC style of working. You can just use functions.

It makes a lot more sense than just the, route based load function kind of ways of doing things.

Apollo says they are already pretty stable. Yes. In my experience, they have been as well.

And other than that, just v eight and, using roll down, all those types of things that go on behind the scenes. But I love a little cleanup. This is like a a little bit of a snow leopard for SvelteKit in a in a little lit aways. I don't know if there's any perf stuff going on here, but just niceties in in cleanup. So, shout out to the Svelte team for always improving SvelteKit. It's my favorite framework for a reason, and it's going to continue to be. So, especially with the dang, remote functions. Dang. Yeah.

Yeah. Those are dope. Cool. Yeah. Happy to see it.

Like, all of this is cleanup stuff. Right? Better ENVs, better imports, no config file.

Love it. Yeah. Yeah. And then, the docs are over at next.svelte.dev if you wanna take a look at the document. Oh, that's me.

You're oh, look at that. That's your, is that the Svelte documentary on the release? I'm in the Svelte documentary. Yes. Nice. So, yes, it it's always nice going to the Svelte homepage and seeing yourself.

Dope. Sick. That's all I got here. Nice and quick one.

Sweet. If you're just joining us, this is Syntax Weekly.

We did I don't think we mentioned it, but, Wes is out today, so it's just me me and Scott.

And before we get into our next stories, there's some chats that I'll call out.

Taylor in the chat is asking, do you have any good video editor references or recommendations? I wanna recommend Casey Ferris on YouTube if you have not heard of them because they do, DaVinci Resolve tutorials. So if you're editing video these days, DaVinci Resolve is really the way to go. It's they have a totally free version. You can buy the studio version for a Node time purchase.

And, a lot of people have migrated off of Premiere Pro and, Fusion not Fusion. What's the Final Scott. Yeah. Final Cut.

Migrated off of that to DaVinci Resolve and DaVinci Resolve Fusion. Because DaVinci Resolve has all of that built in. It has, like, like, audio a whole audio section, a whole coloring section, a whole, like, graphic motion graphics section. But Casey Ferris, really great videos. He has, like, a whole three hour course on DaVinci Resolve. A lot of the stuff I know about DaVinci, I learned from here. Do you have any video editing resources, Scott?

No. You know, I I've been editing videos since I was, like, 12 or younger.

And, I I was on Final Cut for a very long time, then I was on Premiere for a bit, and then I went back to Final Cut Wes Final Cut x came out. I was, like, the type of person who actually liked Final Cut x even though I know a lot of people didn't. And, I moved to resolve I wanna Sanity feels like ten years ago at this point. I moved to resolve a long ass time ago, and I'm a huge, huge fan. I I you know, there's always things about it, but, like, man, it it's really sick, and it just keeps getting better. There's some really cool stuff in Resolve.

I actually, Randy will be like to know that I successfully used Fusion in the last edit to do, like, censoring and blocking out and stuff, and I was pretty proud of myself to get into some of that node based editing and compositing a little bit there.

But, Node, Resolve is where it's at. It's sick. And then there's a nice little MCP too that you can communicate, with your your agents for sometimes or or that type of thing too.

Definitely. Yeah. DaVinci Resolve is the way to go. I too have been editing videos a long time. I I used to use, Windows Movie Maker for my little skate skate I use Windows Movie Maker for Scott videos as well. Yes. Nice. Also yeah. Love it. Cool. Alright. So, let's get into our next story, and I'm talking about TanStack charts.

So you might be familiar with TanStack router or TanStack query or many of the other things. If you head to tanstack.com, you can see that they have a lot of different libraries. They also have TanStack stack DB, which I think we talked about, a while back, which is, like, reactive client first store for your API. It's a whole way of, like, structuring your API so that, like, your the client does the most of the querying. Really cool. They also have tanstack table. All of these libraries, they're they're doing a lot of work in the space to make our lives easier, but they have come out with tanstack charts. Now this isn't super new. It came out, like, at least a couple of weeks ago. It's still early alpha, but it's a chart library that you can drop into your app, and they have all kinds of charts. So they have Sanity charts and gauges and, pie charts and line charts, and you can overlay charts on other charts. And all all the charts that you would need, they have a ton of them, and Scott of really good samples.

What's that? I said, say charts. Charts. Charts. Charts.

One of the cool things on their homepage is, they have a tagline that says make it look like your product.

And so it says same data and scales, CSS variables, themes, mark props, custom tooltips, your own renderer, control the rest. That actually sounds like it was written by AI. But, regardless, the screenshot shows the same chart with a different theme depending on, you know, whatever site you're running in. So highly customizable.

And Tanner just announced, couple days ago that he implemented all of the ShadCN chart catalog. So Cool. Yeah. If you're familiar with ShadCN, they, are a, like, a UI library for React, but they also have ShadCIn charts. Well, all of those charts have now been implemented in TanStack charts. So if you do spin up a project, all of the charts that you're familiar with are already there for you to use as well as a lot of extra stuff. The cool thing about this is it supports all the frameworks. You can see the drop down menu. We've got React, Preact, Vue, Angular, Solid, Svelte, and many of Vanilla and many others. So that's the cool thing about this versus something like ShadCien, which is very, like, React centric.

You can you can use this with pretty much any framework.

And so, yeah, check it out. You can head to the examples page, and they have all kinds of different charts you can dial into. You can get the example code to start from. So I thought this was slick. I've used a lot of chart libraries in my day, and a lot of them are missing some things or don't work the way that I want them to. This seems to have a lot, and it's just in pre alpha. So I'll be keeping an eye on it. I was trying to see a little bit of, like, what this is based on because a lot charting libraries aren't just, like, built from scratch. And I did find in the charts core package,

a lot of d three stuff. D three array, d three force, geo, hex bit. So it does seem like it is d three based. And anybody who might be wondering, like, why not just use d three? D three sucks to use, and having a wrapper around it is way better. So, Yeah. I I I love a good charting library.

I've been doing, like, charting library tutorials for a long time. So having TanStack do a chart that's a d three wrapper, it appears if if someone out there works on TanStack and wants to correct me, it does seem like it is d three based.

That's great for me. Yeah. I I'm very happy with this because there's and I will say, there are some really wonderful Svelte charting libraries out there, but there isn't as much in terms of, like, fully,

fully, fully chart libraries like d three straight up. So, yeah, cool about this. Yeah. Very, very stoked on this. Yeah. And no no issue with being based on d three. I mean, I think that gives you a lot of the the fundamentals without having to do everything from scratch.

And, plus, if that is the case, there's probably a lot of d three style visualizations that you could throw an AI at to kind of adapt to use Sanity stacked charts instead. So Yeah. Yeah. Good stuff. So, yeah, that's all I got. Check it out. Try it out.

What do you have for us, Scott? Yeah. I have something that's fun. And and if you're just joining us, once again, this is Syntax Weekly. We come at you every single week. Usually, we got another guy here who's, who's talking about some stuff, but he's not he's not here today. So we're talking about whatever the heck we wanna talk about.

And so I'm bringing up the next one on tap, which is called ponytail.

Ponytail has the best logo of all time. It is a ponytail old developer guy, and ponytail, he says he says nothing. He writes one line. It works. Ponytail JS supposed to be the AI kind of script to it's a rule set to make your AI coding agent write the least amount of code that works like a senior dev who's been paged at 3AM one too many times. I think this is, like, the best branding and pitch ever. I have not used this. It's, it's it's new. I've heard good things. I will say people have said good things about this thing, but I have not validated it. But I do wanna just put this in front of you.

Your agent reaches for 50 lines. The job needs one. And, like, honestly, I love this type of thing. I'll have another thing in this, in this episode of Syntax Live to talk a little bit about the same kind of concept here. We've seen many tools, whether that's cavemen or whatever, for reducing token Scott. This seems to be just like coming up with elegant solutions in your code the way that an old school senior dev would. Again, there's audit, debt, gain, help. I don't know how much of this is deterministic static code analysis stuff. I don't know how much of it is AI vibes or just prompting things, but this is the type of tool that I'm gonna keep my eye on, and it just popped up. And it's been one of those ones I've had the tab open for a little while, so now the tab is open for you. And if you're out there, you use this thing. Let me know how it works for you because I am super curious.

Yeah. I and, it's mentioned in the chat. Like, I saw this when it came out. I don't think I they had a landing page when it came out. But, again, I think of, like, Caveman, these things that try to reduce the token counts.

I have never reached for a tool like that. I've been pretty happy with, I'm using Node with a plug in that, like, prunes context, and that that keeps my token usage down. But it seems like this is the thing people reach for when they wanna when they wanna keep their tokens down, wanna I think it's just keeping code down because, you know, like, you know, we don't need the infinite amount of, like, JS records and,

extraneous solutions.

And I have things that are not just for keeping your your tokens down for the sake of reducing context, but keeping your tokens down or the responses down for the sake of, like, clarity and, like, maintainability and stuff. So either way, ponytails some people are saying this is a a project that's been around. I'm the same guy that brought the, joke tune thing, to the show a few weeks ago, and, like, it was new or something. So I I occasionally am am late on stuff, which

is actually shocking to to say that out loud. And that's okay because I bet 50% of the people listening or watching to this hadn't heard of Ponytail. So we're here to here to talk about it. So Now it's in front of you. Yes. Yes.

CJ, what else you got?

Yeah. So this is a new editor from the Zed team.

And have you heard of this, Scott? It's Zed Delta.

Have I heard of it? I've been using it for the past You're using it? Okay. Two months maybe.

I've been seeing you in, like, version, like, five of Delta, like, point zero five of Delta. Yeah. Yeah.

And then I got to, give them feedback on it and and, you know, work with it a little bit, and I got a little private demo. So Delta is really sick. There's two things here. There's Delta the product and then Delta DB, both of which are sick as hell. Yeah.

Yeah. The thing that really caught my eye on this was that there's a the space in in AI of collaboration.

So, like, let's say you're working on a team of people, and you're using AI to build your product.

It kind of seems like most developers all have their own little workflow. Like, they have all their skills. They have all their their setup for the things that they're doing.

And, really, the main way people collaborate is, like, in pull requests. But that means that, like, some developers on your team may not be using the same types of skills and, same types of workflows as you. But what caught my eye about Delta is you basically can create a shared thread that has multiple people in it that can, for one, see the AI working in real time. So I think this is also trying to be an answer to just the the daunting amount of changes that AI makes and how you review those. And so this kind of puts it into a thread so you can see those changes, but it's multiplayer. So multiple people can be in that thread and prompt the AI, ask for feedback.

And so I definitely see this as something that teams would gravitate towards because that that seems like a a problem space that that doesn't get a lot of attention JS, like, how do we create more reproducible consistent workflows with AI and work on a team together. So that's the thing that caught my eye JS this, like, multiplayer aspect.

Yes. It's it's, you know, when when they first showed this to me, it was funny. It's right after I just had a a long conversation about paired prompting with some folks at JS Nation Amsterdam. So it Wes right after that. And Wes when I first got into Delta, it was like, this really just identifies exactly that thing and distills it down into the right, primitive, I think. Delta is really, really sick. And what's cool about it too is that you're getting, like, line by line diffs on which model was used for each line of code.

There's some really, really cool stuff in here. You can go back and annotate things in the chat at any given point. So, like, if CJ chatted something and our response was weird, I could come in later, highlight that response, and then annotate it, and then, like, come back to it directly in the chat itself.

There's just so many cool things about it. I was gonna pull up my delta. My version is outdated, though. So I don't know if they want me to show it on screen being outdated. But it's really cool. You can follow people too, like in Figma. So I can, like, click on CJ and just, like, follow and watch and then give him feedback, or we could discuss over, like, Cam, the different types of prompting that we're gonna be doing. And then it's just really, really, like they took the idea of, like, what if an AI chat and, the evolution of code was rethought in such a way. So, I'm a tremendous fan of this project, and I can't wait for more people to use it. I I think it's really sick.

Yeah. And so last week, they just announced the private beta. So if you wanna try it, sign ups are now available.

I signed up yesterday. Haven't got my invite yet.

But they're releasing it for more people to try and give your feedback on. But like Scott mentioned, it's built on top of Delta DB. And what what they were mentioning in in their launch post is Wes essentially works off of, like, Git diffs. So, like, even if there are people on your team that aren't using Delta or aren't using Delta DB, they're just using Git in the normal way, they can still collaborate.

But Delta DB is what gives you all these extra features that you get in the the Delta UI in terms of, like, threads and seeing, like, what model was used and and different stuff like that.

So, yeah, exciting project. I'm excited to try it.

I've tried out Zed before, but this this would be one more reason to to give Zed a go as well. Yes. It's it is really cool. And the Delta DB stuff, I saw some people,

because we had Nathan on from Zed on Syntax very recently. Go back and watch that episode.

That was actually the day that Zed was dropped or, not Zed. Delta was dropped. So, it was really great to talk to him about that. But what's really cool about the Delta DB stuff is some of the comments were like, oh, but now I have to buy in to version control at, like, an app level or something like that. And you don't, really. It's compatible with Git. You don't have to you don't have like, somebody can work in a repo and just use Git, and someone else can use Delta or whatever, and they can coexist just fine without goofing anything up. So, really cool stuff.

Nice. Yeah. So that's all I got for Delta. Do we wanna get into this Stripe story?

Yeah. Let me pull up I don't wanna pull up Yahoo here. I don't have anything to show on screen. There's a there's a TechCrunch article if you wanna pull that one up. TechCrunch. Yes. I was just like, don't wanna, Yahoo Finance. Oh, disable my ad blocker? Node. TechCrunch.

I think honestly, Yahoo Finance or Tech Times might be fine. It's it's financial news because it's like acquisition. I don't know. Folks, we're about

to show Yahoo on stream. If you're sensitive to Yahoo, please turn away.

Yahoo JS about to be landing on screen in just a moment here.

Fair warning. I actually CJ, I I use Yahoo for Sanity football, believe it or not. And it sucks so bad. I'm on a I'm in a fantasy football league with a bunch of other tech people like TypeScript and some other folks. And believe it or not, I won the first season of fantasy football by only drafting Detroit Lions. That's right. Wow. And, yes.

Then I said that I use Yahoo on a on a weekly basis, and it's gonna start happening again soon. I'm not looking forward to it. Either way, Stripe acquires open router for 7,000,000,000 plus, turning mod model routing into a payments infrastructure problem. What is this AIS headline?

Is it though? Yeah. Okay.

Yeah. That's because that's my question, which is, like, why would a payments company acquire a model routing company? There's probably reasons we can hypothesize, but I don't know if there's anything in the announcement that says that they're gonna turn it into a payment gateway. Is that real?

No. You know what? I I think Stripe is a smart company.

I think they are, always in my mind, Stripe is one of those companies that does really interesting things, whether that is Stripe, what's it called, Stripe Press doing, like, really great books and stuff. They have a number of acquisitions. Most of them are, you know, finance based whether that's like they acquire Lemon Squeezy.

Apparently, they acquired Lemon Squeezy, which is a, payment payment, reoccurring payment platform.

And they did try to acquire eBay at some point.

Do you remember that, CJ?

Stripe?

They put an offer for eBay.

I didn't hear about that news. This is not a finance podcast, by the way. Like, I'm not up to date on all this stuff. Yes. Breaking news.

Stripe tried to offer oh, no. Stripe, not eBay. What? PayPal? Stripe Advent offered to buy PayPal.

Was it PayPal? I thought it was eBay. There was a chat that someone someone was saying they they are in the the talks to potentially purchase PayPal, which would be crazy, because then they'd be all the pay all the payments on the web. Right. More than 40 or $53,000,000,000.

So not eBay. I thought it was something with eBay. My god. I am out to lunch on this stuff. Either way, OpenRouter, they host models. You can subscribe to OpenRouter. You can put money in your wallet there. And then what what happens is is that you can choose the models that you're using. You get access to models from everybody, and that's that's OpenRouter folks. And OpenRouter JS a sick product. We use it here at Century. I've used it here, personally. I'm a big fan of OpenRouter. So to me, even though it's like, okay. How does payment processor fit with model routing or, you know, buying inference? It doesn't really feel that weird to me for some reason. I cannot put my finger on why it doesn't feel weird, but it doesn't feel weird. Well, I think Just because, like yeah.

Well, I was gonna say, like, wait. If you think about, like, what Stripe did for the web, it's, like, all of these various types of payments they put into a single platform. Right? Like, you can add Stripe, and now you Scott bank payments, you've got credit cards, you Scott whatever else. And so they've they've become the central place for payments, and that's kind of what OpenRouter is. It's the central place for AI models.

And so maybe they're also trying to make sure that they can stick around in this new AI era. Like, I I don't know why payments would go away or or if some company could come around to take Stripe down, but maybe they're also differentiating. Like, what they did for payments, they'd like to also make sure they're doing for AI models and access to AI maybe. So Yeah. I I don't know. You know what?

By the way, chat says that GameStop was gonna buy eBay. I knew it was somebody weird.

GameStop was gonna buy eBay. Wow.

So, also, any alternatives you'd recommend from Kevin? I would recommend OpenRider.

Honestly, I don't I don't this acquisition, like, doesn't hurt my opinion of OpenRider in the least bit.

I like Stripe a lot. I I I don't usually have any issues with Stripe. So for me, the, Stripe acquisition here isn't, like, isn't one of those things where I'm like, oh, shit. Adobe bought it. Now I gotta get off of it. You know?

Yeah. Okay. So, again, this isn't a finance podcast, but I am actually finding news that last month, Stripe made a $53,000,000,000 offer to buy PayPal. So that was a thing. That was a thing.

Okay.

Yes. But I thought I thought we replaced it saying it was GameStop. I don't know. No. GameStop

tried to buy eBay.

Oh, my god. EBay.

Yeah. For PayPal. And PayPal following. Okay. Wasn't PayPal part of eBay, or am I losing my mind?

Deno. PayPal, I don't understand. But it was or, yeah, it Wes. Early on, PayPal came out of eBay. Like, that's

the ESLint payments for buying eBay stuff. Yes. Folks, come to us for your Business Insider news.

I think we could give you a better headline than turning model routing into a payments infrastructure problem. Yahoo. Yeah. I don't which I don't think is gonna happen, but, you know. Oh, did you, did you see that? Wes this this, Wingstop Inc. Is down? So the Wingstop holders, your stocks are down. Just a shout out to you ever know Wingstop? What is Wingstop? Oh, the the food. Okay. It's like the hot wings. They have them in in Colorado, and I never seen them before I moved here. And I was like, what the hell JS Wingstop? I've never been there, though. I've been before, but I am vegan now, so I no longer eat chicken. So

Wes. Mhmm.

Yes. That makes sense. Yeah. Okay. Well, that's all I have here.

Folks, I don't I don't think this is gonna hurt OpenRoutter that much. No. No. No. I think I I I'm, like, perfectly in fact, you know, I feel like this might give them not that they didn't have juice to stick around, but, like, hello. Open router was, like, fairly new. You know? So Stripe.

Open router. It's a marriage.

There we go.

Alright. This, this next story I got for you is actually a research paper, but there's a couple of things I wanna show, and I'd love to get your thoughts on this too, Scott, because the the first thing that, comes to my mind is just how cool this site looks like. Usually, when a research paper comes out, it's just a blank black and white page, or maybe you just go directly to the the archive page.

But they have they bought a domain, stolen-thoughts.com.

They have what I think is nice color choices, and then a really cool layout for looking at the results of their research paper.

And then all of these, like, little reasoning blocks in the background, when you click on them, they kind of, like, explode on the page. So, yeah, initial design thoughts before we get into what this paper actually is. What what do you think, Scott?

Well Yeah. I mean, it it reads AI to me, but it also does look nice. And I I listen. I will take this over some, man, even, like, pub PubMed looks like ass to me. So I'll take this over anything like that any day of the week even if it does look, AI generated.

So no. I I think it's cool. No. And I and I appreciate this kind of stuff. I'm a visual person.

I, am dyslexic, so reading large amounts of text is hard for me. Having pictures and colors and organization, it makes it easier for me like a child. So I am happy to see this.

Oh, it it's got all these, like, little design flourishes. Like, there's, like, these, the the cards are, like, slightly askew, like like, slightly rotated, and then there's some top borders that are, like, triangles that extend.

Yeah. And then just like a really soft color palette. I don't know. I thought it was cool. But the paper is called stealing reasoning traces from proprietary LLM APIs.

So if you didn't know this, the reasoning response that comes back from, let's say, like, a a frontier model like Opus 4.8 JS actually encrypted.

And the reasoning trace is where a lot of the work is Deno. And so reasoning models, came out.

And, essentially, instead of a a model and instantly responding to your prompt, it actually creates this reasoning chain Wes it's thinking about how it will respond to your prompt before it actually shows you the response.

And that reasoning chain is kind of the secret sauce because that reasoning chain can be used to fine tune other models and, essentially, kind of still the secret sauce of some of these frontier models.

But, I I actually didn't know this. When you're interacting with one of these frontier models, that reasoning chain is hidden from you. You can't actually you can't read the reasoning chain. It it's encrypted, and then it has a signature on it. But what this paper showed is they can actually take the reasoning signature from a bigger model like Opus 4.8, and then craft an API payload that talks to a dumber model like Haiku 4.5, include that same reasoning signature, but just give it a prompt that says, hey. Tell me what's inside of the thinking block.

And the dumber model doesn't have the guardrails to prevent it from showing the reasoning trace, so it just, like, immediately dumps the reasoning trace.

And so they showed this with a lot of different things. You basically get the reasoning trace from Opus 4.8, use Haiku 4.5 to actually read that reasoning trace out, and then did the same thing with, like, OpenAI models. So for instance, get a reasoning an encrypted reasoning trace from GBD 5.6 SOL, and then ask LUNA, which is their smaller model, to tell you what the reasoning trace is. And then same thing with Gemini.

Use Gemini 3.5, pass that encrypted signature to something like Gemini three Flash.

And the reason this is interesting is because these reasoning traces, again, like I mentioned, can be used to fine tune other models, and this is kind of potentially what we're seeing happening with some of the bigger open weight models.

They're potentially using some of these reasoning traces from these these larger models. So this paper shows, also how they were able to, like, extract secret information from the reasoning trace that's usually you wouldn't be able to get access to.

And they kinda show how they did it with all of the different models. But with another thing this paper shows is how similar responses Yarn and how you can actually look at the response of a model and already kind of determine or look at the reasoning trace and determining determine which model that came from. So on the page, they actually have a game where they show you three different decoded reasoning traces, and you have to choose which of these you think is the given model. So this one is saying, which one of these reasoning traces belongs to Claude Opus 4.8? And so the first one is Wes need solve problem. We need provide explanation and code, likely c plus plus. I don't know about you, but I I feel like I haven't seen Opus four point eight use, like, short words like this. That's usually, like, OpenAI or ChatGPT that, like, really add short words in its reasoning.

This next one is Wes need to understand the problem. We have in workers each work that that could be Opus. Yeah. It This next Node? Annoying like that.

We need to we need we need to pick a subset of workers such that for every chosen worker, I think it could be b or c. I'm gonna go with b. It was c. So c was Opus 4.8, and then, actually, that first one was from Kimmy K. Through. So you can you can play a bunch of rounds reading the reasoning chains and trying to determine what what model actually created that reasoning chain.

So, yeah, I thought it was fascinating paper, also really cool website.

Yes.

CJ, we're getting a lot of chat, a lot of chatter about GrokHub, which is what I'm calling it now. It's it's not actually GrokHub. In fact, let me even share my screen. I'd I'd hot off the presses, CJ, origin code hosting which is a cursor Node, hosting is here.

Let me share my screen and this is apparently Node hosting from cursor.

So origin begins raw this had just happened moments ago. Origin begins rolling out today in early beta on all played paid plans. We're starting with the essential design agent scales, pull Wes, code browsing, and GitHub sync.

So it looks like they are coming for GitHub here, which is basically where you can host your code. You can automatically bring in your GitHub repos.

There's pull requests.

Yes.

Pull Wes, agents in every repo, app extensions from the cursor repo, settings.

Okay. Yeah. You know, thoughts on this.

I I mean, it it's missing a lot from from GitHub, obviously. Yeah. It's a subset of GitHub's features, and it's good for them to launch this on the day that GitHub is out for so long.

GitHub outages have continued to go. So I think that is the big sell JS that it's going to be, you know it it it's gonna be that thing that can hopefully be have more uptime, but, like, I use a lot of stuff on GitHub that I don't know if this is gonna be able to do. So we'll see. Yeah. We'll see. I I mean, I have it installed right here. I just signed up for it. This is what the dang thing looks like, and we're gonna see if this is actually any good.

Yeah. There's a couple of things my mind goes to. So first of all, Cursor got bought by

Grok. Right? Or like Which is why I'm calling this Grok GitHub.

Okay. Okay.

And we already know there were, secret leaks. Not leaks, but, like, the was it the Grok code would just, like, upload your entire repo to an s three bucket or something like that? And then they disabled it. So, here's the thing. We've already given all of our code to GitHub, and we somewhat I I was gonna say Wes trust that they're gonna not train on our private repos, but we don't know that they're not doing that because they did train on a lot of code that's on GitHub.

So that's that's where my mind goes to JS, okay, instead of giving all of your code to Microsoft, now give it to x instead. Yes.

Who's already kind of shown that they are not to be super trustworthy in that department, but, hey. Yeah. Who JS? Time, like, they have the Cursor IDE, which was, like, one of the first to be really good in this space. Now it has a lot of competitors, and not necessarily everyone is using Cursor. But I don't know if you remember maybe a year and a half, two years ago, Cursor IDE was the thing that everyone was using to write code with AI.

Yes.

So I think this is also them trying to, like, reposition and find find spots where or find things that can make it more enticing to keep using Cursor.

Yes.

Cursor origin, folks. If you're watching, I found a bug. This Toast message does not go away when you click it. There's an x. It doesn't go away. Did you say vibe coded?

Yeah. Thank you.

Yeah. I mean, hey.

We need we need some, we need some shake up here. Obviously, GitHub has been having some issues, and this product did just launch moments ago. So it it like, there's some latency and stuff here, whatever. I'm willing to give this a shot and see how it goes, but I can't see myself lining up to use this, if I'm being honest. I I just maybe my own personal feelings getting in the way here, but I just can't see myself being, like, yeah. Let me just throw all my my stuff on, cursor origin. And I don't use cursor. That's part of it too. It's like, I don't I don't use cursor. And so for me, it's like, okay.

Is this, like, that's the the funnel JS try to get me to use all of their stuff, cursor, cursor origin, and all that. Wes like, just not my favorite.

And for Luke says, you may feel different the next time GitHub goes down. Well, this thing is currently struggling because GitHub down is down. It says the performance is degraded because GitHub is down. So, we'll see. Yeah. I I don't know. I I would prefer I don't know. I think there's like, who's the one? Pierre computer has a a solution here? There there's all kinds of different different solutions here, but this does kinda feel like funnel to cursor to me. And I just I don't, like, I don't see the u like, the, the pull there.

Mhmm. Yeah. Looking at the replies, it looks like GitHub is down right now for some people, which is, I think, that they timed stuff. Morning. Yeah. Okay. Okay. I don't even know because I'm doing other things. I I do I was trying to look at GitHub issues about another project that was broken, and it was just loading to me. So, yeah, I can do my work without GitHub a lot of times.

But I think they they tried to, like, meme time it, I think. Like, GitHub is down. We're just gonna release this and kind of get in on the bandwagon of GitHub being down, which I wish they would put more thought into. I wish that you could close the the pop ups. The what was it the little toast? Yeah. Yeah. That's just a little Tolinski you know, that's Bos that's a It's a sign of a bigger systemic issue. Right? Like, it's like pushing code that hasn't been tested and

yeah. I don't know. What I wish is that, like, this is, like, a little bit more forward thinking. I wish we would think beyond this kind of, chat GPT as chat bubble whatever and, like, new chat, this this generic chat GPT, layout that we've all kind of just accepted as the thing. And that's the one thing I really liked about Zed's delta JS that it doesn't feel like the same thing just done by a different company. So, like, it takes a different approach even though it's obviously apples to oranges here. Yeah. This is this is new. Hey. And, you know, shout out to somebody to push GitHub because they clearly need it. GitHub has been, struggling for months now with the amount of code. And, honestly, it might do if this truly, like, gets people off of GitHub, what it might do is relieve some of that pressure on GitHub servers so that it stops going down for me. You know? Yeah. Yeah. I'll take that. Yeah. Yeah. I mean, you could also put your tinfoil cap on and be like, okay.

What if cursor is generating bot traffic, which is bringing GitHub down, which is forcing people to use.

CJ, get really tinfoil y. I'll be, the I'm not ESLint go there, and I'm not I'm not a fan. So, well, we'll see. Yeah. I I'm excited for Pierre. I'm excited for anything that gives some, competition here. I I was a big user of GitLab for a long time. So, again, I'm down for competition in this department. But, again, like, if if it's gonna replace GitHub for me, it's gotta do all the stuff GitHub does. It just can't have an AI chat on top of GitHub.

Yeah. And there's automation's cool, but, like, the the GitHub stuff is pretty dang good there. So hey.

Uptime is the big sell as far as I'm concerned, and I don't know if that's right now.

Like, that seems ridiculous to say. I don't know if that's right now inhibiting me enough in my day to day life to make me switch to something completely different.

Right. Nice. Okay. So I I have a a CSS story.

And this this this blog post was actually published at the beginning of the month, but just came on my radar.

But it's a blog post by Leah Veru, and the title is dark mode toggles, two states are enough.

And I've actually thought about this when I was implementing dark mode toggles, and they make a really good case for just having two states instead of three. Yes.

But the thing you might be familiar with is, like, when you implement a dark mode toggle on your site, a lot of times, you'll have three modes. You'll have system, which is use whatever the user prefers, whether it's dark or light.

Then there's an option for dark, which is force dark mode, and then a light option, which is force light mode. Mhmm. And if if the user chooses dark or light, it forces that. But if they choose system, it follows whatever their current system theme is.

And, I mean, I kind of preferred that because sometimes I change my system theme and, like, I want sites to follow along, but it's also not hard to just go back and toggle a site to light if I want it to be light. But this this blog post makes a really good case for the user experience of it all. Like, I'm more of a power user. Like, I think about the different states and and think about how sometimes I do want system versus, like, an exact Node, but they kind of get into the idea that for end users, nontechnical users, or people don't care about this, there's a lot of user experience friction when you have three different toggles. And for some people, it's a little bit confusing as to what those three different things do. And so they make a really good case for just have two states, dark mode and light mode. When a user visits your site, default to whatever their system theme is and show that as the selected one. And then if they wanna toggle it, they can toggle it. So, essentially, you're now only keeping track of, one piece of state, which JS, has the user selected a preferred theme or Node? Otherwise, just use their system theme, which I like, and I think I'll start adopting. So had you seen this or or thought about this, Scott? I I've thought about this a lot. I haven't seen this article specifically,

but I've, like, more recently and this is, like, a controversial opinion on my behalf.

I more recently have the feeling of, like, just use the system. Unless it's a theme, like, don't even give the option and just have it be a system toggle. It's very rare that I want everything to be dark and one thing to be light. Now I recognize that other people want that control, but unless it's like a theme customization where you're choosing more than just lighter door dark, it's like, I just I just I default the system. I, like, I just want you to default the system. Well, it really bugs me when I arrive on a website and it's in light or dark Node, and it's not whatever my system's set to, and then I have to, like, go and manually change it. Like, default should be system. Absolutely.

But I I mean, I do agree with I think this solves some of the concerns I had with that approach by not giving, like, users control or whatever.

So, hey. I think this is a good way to do it if you're asking me.

Yeah. And check it out. Like, there's been a lot of converts after, like, reading this blog post, and there's an example at the bottom of how all of this works. So, like, let's say a user arrives and their system theme is dark.

When you when they click toggle, it changes to light.

If the OS switches to light, their preference is still kept because they clicked that button.

And, if they switch their OS back to dark, it stays because they clicked that button. But then if they wanna actually go back to dark mode, they would toggle it. So yeah. I I think it's simple enough. It it it makes it easier for end users, and there's less state that you have to keep track of in your app as well. So

Yeah.

Yeah. Wow.

Okay.

Sick.

Let me pull up my next one here, and I'm trying to I got several that I could do here, folks. I got I got links all day I could get to. Here's a fun Do do all of yours back to back, but before that, do a century read if you can. Or work it into the or do or work it into them if you can. CJ, would you describe this as a formal, hand off here?

Yes. We were a little bit we broke the fourth wall. We're behind the scenes. You now know that I am instructing Scott to give you a century ad read and do all of his stories.

Sentry. Let me let me tell you about Sentry, and then I'm coming up with this on my own accord here, not because, I've been prompted to by CJ.

And if CJ wants a good review, he will not be prompting me to do that again.

Okay.

Noted.

Just joking, folks. I, no. I need the prompting. [email protected], the perfect place to solve your bugs. And if we're talking about, fixing bugs live and then and, actually, I'll be talking about something that kinda fits in nicely with Century in just a little bit, is, Century is really great for healing your software because Century has a dope CLI.

I almost said c I because we've been talking so much about, in the chat about CICD.

As a dope CLI for you to be able to connect to to get, current bugs to use their seer AI to be able to get to the root cause of a bug because we all know those stack traces be looking ugly. And they're just sometimes when I want a dang thing to tell me, and I'll tell you about this in just one second using plain language.

What the heck is going on? And I can get that information.

So I love this stuff because, Century JS always having more tools. And another thing I'm gonna connect it to another thing, Swamp Club, I'm talking about a little bit. I got Century metrics connected to my Swamp Club so that I can understand what's going on inside of my Swamp Club with my AI agents. And then I'm doing AI agent monitoring to understand how much all of my dang open router, token cost is. I know open router has those features as well, but, I'm using more than just open router, and I wanna connect it all inside of my agents. So check it out. Century.io, the perfect place to make sure your applications, your agents, your AI, any of that stuff is running smooth, and it's the best. We love Century over here. And not just because syntax is presented by Century, but because we absolutely love them anyway. So after that supernatural ad read, let's talk about plain language. I saw somebody talking about Cursor five and not just a one person, but people have been talking about Cursor five and how it's, kind of being a wiener in the way it replies to you and being kind of annoying.

And, I I find that, like, nine times out of 10, most AIs are being a wiener in the way that they reply to me. And it's actually very annoying when it gives you a whole, like, a whole lot of words for something that it couldn't, like, couldn't give you more simply. Like, the verification process encountered an unsuccessful outcome due to dependency and expected an actual value. Like, who cares about it like that? Tell me what the heck the problem is. So, I saw some folks talking about different ISO standards. Apparently, these things exist for English.

They got some line height issues going on here.

Iso.org.

Got some line height problems.

But ISO two four four nine five dash one colon two zero two three plain language is an ISO standard for documentary governing principles and guidelines developing plain language documents. And there's a number of these different standards on how to speak plainly.

And what I have gone ahead and done is added a one liner that is just says, always respond to the user in plain language using ISO and then this this two four four nine five hyphen one colon twenty twenty three. And it has made my life so much better. So instead of saying the verification process encountered an unsuccessful outcome due to dependency and expected actual values, it tells me the test failed because the actual values did not match the expected value. And the thing I like about this plain language standard is it does not remove technical details from things. So it's not obfuscating the issue, but it speaks to me in a way that I can actually, like, parse easily in less words.

And it's not simplifying it. It's not removing that data, but it's using simplified language in a way that makes it all easier to say. And this, again, was a one liner. I'll paste it into the chat here just so people can check it out, and it has been effective for me. Like, I put this in my agents.md, and it's made my life a I I I have to I have to respond to the AI.

Tell it to me in English or explain my time five way less because it's just telling me in simplified language and these kind of standards exist. So, whether or not you're using this this one in particular, two four four nine five hyphen one colon two zero two three or not,

I think it's a really cool thing to do. And it's better than, like, give me caveman speak or something. You know? Right. I I I actually saw this, there was a thread on hacker hacker news a couple weeks back where they talked about this, but one one user made a really good point.

Sometimes plain language is too plain, and so you might get worse responses if its reasoning chain is using plain language as well. So I think as long as you make sure that it's only responding in that way, its reasoning chain still does whatever it wants to do Yeah. Or you have, like, follow-up prompts. Maybe you have just, like, a built in plug in or skill that says, rewrite this response in plain language. Totally.

I think so I haven't tried it yet, but I think I will. I'm building a a home personal assistant right now with GPT five six Soul, and it is incomprehensible for things like Right. It actually it was it was running all weekend, and it was just going off the rails. Like, it's writing all these validators and, like, I mean, that's good. Good. If this were if this were a production app, I'd be really happy, but, like, I just wanna prompt this thing already.

And, the the language is crazy, and I have to it's so so hard to parse. So I I think I'll try this out to get it to Yeah. Tone it down a little bit, make it a little easier to understand. I mean, my little thing says respond to the user using

and so to me, I haven't noticed that causing a problem in the reasoning.

Okay. But then again, you know, I've been I've had this on for about a week and a half now, and I have not seen any issues there. But you're so right about Soul loves to be doing that stuff. I was working on my swamp, which we'll talk about in just a little bit here. Actually, maybe I'll talk about swamp next. I was I was working in my warp, a good little, transition here.

I was working on my swamp and, man, what happened? Oh, it was like I I wanted to just use work trees and pie instead of, just stopping at at one thing or branching all the time.

And it wrote a giant ass GitHub extension for Swamp Club instead of, like, basically doing all of the GitHub stuff. I was like, brother, this is just a Python thing. Like, I don't need you to to to write an extension. I didn't ask for that. It, like, it comes up with the most asinine solutions to things sometimes where it's like, oh, user needs. Clearly, the use Node to use work trees, and swamp club doesn't do it in this way. So let me write all that functionality. Like, come on, bro. Okay. Swamp Club. What is Swamp Club, folks? I just mentioned the word warp club a whole bunch of times. Swamp club at swamp-club.com is deterministic automation for AI agents.

So the pitch here is really that if you ask an AI agent to do things multiple times regardless of if you have a CLI or scripts or whatever, it's gonna take a different approach to it each time, or it's gonna have to look up things or look for things or do whatever. The pitch for swamp club is that you build in deterministic code based automations that run deterministically and are able to log what they've done in databases and stuff like that. So that way that your automations can respond to one another. They can pick things up. And a lot of people are using Warp Club to do things like software factories or anything like that or deploying, like, oh, I I have a deploy process that needs to run this and this and this and this and this or a procurement process.

Like, I wanna procure a domain for this project, and I wanna get this all hosted on Cloudflare or whatever.

You write all that in actual TypeScript. And then when I'm talking to my AI, it's like, do this and then then procure me a domain. Instead of it being like, oh, let me let me figure that out and look up the CloudFlare CLI and do this or that or the MCP, it's gonna reach for its scripts. It's gonna run those, and it's gonna do so much more effectively. I used Swamp Club to edit my wife's podcast using, Python.

And what it did is it analyzed, both of our voice frequencies because it's a multi cam podcast. So the AI did not edit the podcast.

It used the two cameras, and I said, this camera's lower voice. This camera's higher voice, and then do a multi cam cut between the two of them and then cut out the the silence and then cut out the space after the introduction. And it did all of that with Python. And now since semi warp club, it's always going to use that exact same automation to do it.

Other ones, I've created a swamp club model for looking up analytics from my analytics dashboard because swamp has a vault for your e n v vars. So, like, if I have my analytics API key, that doesn't really make sense to go into the code Bos. It's just part of the automation and when I'm working with the AI. Like, I wanted to look up the analytics. So, therefore, it's always gonna know to use the warp API key to go and do that.

It it really rules. I'm a huge fan of this thing, swamp-club.com.

And, automations, there's a whole bunch of stuff in here. They have really great docs. Obviously, AI consumable, docs. People have written all kinds of stuff. Their Discord is popping. And one of my favorite things about Warp Club is this. They have, like, they've gamified it Wes they have a leaderboard for who's spending tokens, on what and who's publishing extensions.

And then as you gain experience, you're, increasing your account.

So I'm a level 10 Merc beast right now.

I got about 50% more experience before I became a Blackwater wraith, which I'm pretty stoked about.

And, I have a couple of published extensions, like Node for logging my, software factory metrics to Century at century.io.

Check it out.

As well as one for using my, task tracker. So my decks tax task tracker properly taking tasks and then moving them to the correct thing, and then again for my plausible analytics.

Man, I think this is a delight to use. It's well thought out. The team behind this, this is not like some fly by night operation. They have, like, a a really strong team of folks who have been, in the industry a very long time, specifically working in infrastructure and, like, things like Terraform and that kind of stuff. So these folks are not, like, vibe coders who are just like, oh, I wanna I wanna do this.

These are these are folks who are used to building this kind of intense stuff. They are they yeah. Yes.

If you recognize any of these words. In fact, I I really wanna get, Adam on the show on Syntax to talk about Swamp Club because these guys are dialed. We just had a conversation last week, and it was, like, really, really eye opening to how they're using this thing.

Yeah. The this rules.

Nickname says it makes zero sense to me. Yes. Well, think about it this way.

Your AI just chooses at the point in which you tell it to do something. It's always choosing in that moment, like, what it's going to do. It needs to look up whether you have skills or scripts or whatever. It needs to look that stuff up. This just says, procure. Okay. Here it goes. Let me run these scripts. So it's sick. Yeah. And the extensions the amount of, like, existing extensions are huge, obviously, and they have, like, a whole vetting process for them, whether that's, like, all this AWS stuff. You hate AWS? Me too. Well, now you can, swamp club it.

Yeah. I think the the simplest explanation for me would be take something that usually requires AI, and and, really, it would require AI on the first pass. But then every time after that, we don't have to use AI to do that thing because it it figures out what are the endpoints that we call, what are the systems we need to integrate with, whatever else. And instead of being an AI reasoning chain of, like, doing all of that stuff, it turns it into just a script so you can run that does all those things back to back. So I think I think this is great.

Yeah. I I I do this kind of thing manually, but to have, like, a system around it to make sure that you're doing it more often,

I think in the end, it's gonna, like, save you tokens. Right? It's gonna save you AI usage because you're creating these reproducible workflows. This is gonna save you a a lot of tokens. Again, like, somebody says I just type into the box and, what I Node to do. I mean, brother, you're wasting a lot there.

Not that, like, you know, we're all not, like, wasting tokens, but, like, you're you're again, you're spending time telling AI to do this or do that, like, AI CD into this directory for me. You know? Like, all of that stuff can be automated, any of the stuff that it's doing. In fact, I wanted to find a blog post in here because they do a really good job of writing blog posts in here.

And, I can't find it. It was from Adam. And Adam basically took, my boss, David Kramer, his software factory loop thing that he was calling Garfield.

He was like, I I've made Garfield use, like, infinitely less tokens. And it was really cool. I'll try to find this post while we're while we're talking about something else. But, the posts are really good in here. And the community let me tell you, the community is sick around this thing.

You can see they have 285,000,000 automation, events sent in the wild right now. So people are using this. Again, this is not like a little itty bitty thing.

Whole team here.

Yeah. I think so. One of the questions is, why not just script that then? I think this think of this as just a skill you can call or a plug in you can call to take what you already do and then instantly turn it into something repeatable. Like, you could probably do it without Swamp Club, but they also gamify it in a sense. I think they also give you access to models if you wanna go on their, like, paid plans.

No. So the models thing models is, like, what they're calling kind of their their, extension. So the model is like a a model in this language, you know, the language model, is kind of like my model for plausible analytics hits the plausible API and pulls down the data with these functions. If I'm asking for this or that, it's gonna run that function and get that data and bring it in.

And then, again, you can combine these different warp, models together or workflows or whatever. What swamp does that's different is it it like, beyond just having scripts, it has a way for these scripts to talk to each other, to store data about their runs, and to include the e n v stuff and the vault and security stuff separate from your code Bos because these are this is your infrastructure and automations and stuff like that.

I think it's sick, so I'm a huge fan of this.

Nice.

Yes.

CJ, do you have something that you can talk about right now? I only have one more, and I'm gonna end the stream with it. So I guess whatever you got, keep it going. Okay. I will only say that because Courtney was outside my window mouthing something to me just now, and I have no idea what she was trying to say. We can end it. I can I can go unless you have something else you wanna show? I Sanity. If it's urgent, she will text me. And it's not a sandwich. I can tell you that, folks, because that's the number factor before. Week, and I wanna get back to my projects. Me too. Well, I'm gonna end it here then.

I got one more from, Dylan Mulroy, AntiSlop. Dylan works at CloudFlare, and Anti Slop is his skills for dealing with slop. I have not used this yet, but I've been seeing a ton of chatter of people saying the PRs generated from this are removing a ton of their code in a good way.

So a whole bunch of stuff in here, a bunch of rules and scripts, deterministic, and AI Tolinski, skills to help you remove a slop from your code base. So, yes, very cool stuff.

Nope. Are these skills or plugins? Or This is a skill and some scripts. Skill. Okay. Nice.

I'll try it out.

I've I've been using the the Sanity skills. There's, like, a simplify skill and then, like, a security review skill. That has removed most Scott for me, but I guess this is a bit more targeted. So I give it a try.

Yes. Cool. Well, that's all I got there. Check it out. Sanity Scott. I'm gonna be checking it out too, today, I think.

Dope.

Last thing, Scott. Are you a fan of Rubik's cubes? Do you know how to solve a Rubik's cube?

No. I'm terrible at them. ESLint fact, I'm I'm I'm really terrible at them.

Okay. Well, this site has every possible permutation of a Rubik's cube that you can scroll through.

And they also have, like, nice little animations.

So, like, as you scroll, you see the the, the squares of the Rubik's cubes changing.

But if you don't know, there are 4.3 times 10 to the what is it? Nineteenth power possible permutations of a Rubik's cube.

And, this site lets you just scroll through every single one of them, which I also thought was fascinating because I think that's, like, more than the number of known atoms in the universe. So, like, how do you have a web page that can, like, see every single one? But I do think they're, like, generated based on their particular index in the solve space.

But I thought this was fascinating, first of all, because of the number and then also cool little animations to kind of scroll through the different ones.

So yeah.

That's it.

So Scott muted. Sorry. I was muted.

Courtney had come in, to say hi. So Nope. Try not to be disruptive, folks. Sorry about that.

So but, yeah, that's all I have. This was a quick Node. But now we gotta get back to Hack Week. I'm making a Game Boy game. And I guess, Scott, you can tell them what you're working on because we're doing this all week. Yes. Hack Week.

Yeah. Do you see my shirt? Hack Week. Oh, that's a six shirt. Yeah. Is that a hat a a Hack Week shirt too?

Yes. No. The Scott JS a, University of Michigan basketball national championship, hat from when the the Wolverines won the national championship in basketball, which let me tell you, how many basketball games have I watched in the last year? I don't know. But I did watch the ones where they won the national championship, so I get to buy the hat.

I don't watch basketball. Sorry, folks.

I'm building a little prompt boy. Oh, nice case.

Yes.

Yeah. It's, this is my pre three d printed case. This is the, first attempt here. It it doesn't hold together very well.

Right now, it's kind of junky, but I do have a little wave share screen, that is a little touchscreen and an ESP device onto it. And the idea here for this device, folks, which I'm really excited to to work on, actually, is gonna be like a little, notetaker.

Hey. This or that, whatever.

And then it can pick up a agentic work and start working on things, whether that's code. So if I say, hey. My site's down. It can go and start working on the site. Or if I say, figure out why my kid's tire JS not inflating, it can, like, be like, here are the possible reasons why your kid's tire is not inflating. So Nice. Yeah. That's that's it right now.

Oh, yeah. And I'm I'm building a Game Boy game. It's gonna be syntax themed. There's gonna be puzzles.

And, eventually, if if everything goes well, eventually, we'll release it as a physical game that you can buy in the merch store for for Game Boy. So Yes.

O o x I a says, so an audio recorder from mine. And let me introduce you to the, the hook of my project, which is this ain't your grandma's audio recorder, which is it it literally what I have JS my hook, in the the description of the project. So, more on that soon. It's gonna be dope.

Nice.

Cool. Well, I don't have anything else. It's been real, CJ.

Yeah. Good times. Alright. Good luck.

Yes. Oh, man. It's so much more fun without Wes, JK. Just joking, folks. Dope.

Alright. Peace. Talk to you guys later. Peace.