John (2:52)

I mean, videos are inherently viral and driving real awareness in a way traditional memes no longer can. Not just because they're novel and more entertaining, but because a single AI clip can travel further and compound harder than traditional meme formats and social feeds that now heavily favor video. This suggests. Yeah, it's interesting on. On X, it's still very easy for an image to go viral. But if you think about, you know, Instagram, YouTube, like a standalone image, just can no longer actually get that escape velocity.

Dylan Abrascato (3:19)

I mean, what about dripped out Pope? Remember that?

John (3:22)

Yeah, a little bit. But people are just spending so much time in the short form feeds and there can go in there, but there's certainly. This suggests a new playbook for marketers, especially in entertainment. If you're about to drop a trailer for a new movie or show, you need to be thinking about your rage bait character, the one people will latch onto. Remix with AI and build around. Conan tried to force a Leo meme down our throats at the Oscars. Didn't see that because I was sleeping, but this might have worked 12 years ago. That playbook is over. Today, enraged fans and communities will, if you're successful, take your characters or moments and turn them into something much bigger. Entire cinematic universes. I'm just very impressed by the overall quality of those outputs.

Dylan Abrascato (4:03)

The Oscar selfie. I remember this. This, I think, became the most liked image on Twitter at the time in 2014. Briefly, this is the canonical clout bomb. If you're a fan of Bradley Cooper, you like it. If you're a fan of Meryl Streep, you like it. You're a fan of Brad Pitt, you like it. And so you're amplifying all of the ultimate collab post. And this has become a format that's been used time and time again. But now the future is AI. Let's pull up the dripwart School of Drip video. I want to watch this one. Let's see if we can play this.

Guest or Contributor (4:34)

That's Harry Potter. Are you really Harry Potter? My G type shit type shit type shit type shit. None of that. None of that, broski. We're all here on the Maybach Express for one reason and one reason only, and that's to go to Dripwatch, the school of Drip,

Dylan Abrascato (4:53)

the Maybach pulling the Train is pretty good. So, yes, very effective. I was reflecting on this and thinking about how it's not just AI videos that are unlocked as the new meme format. Like 20 years ago, video editing was extremely difficult. Like you had to do it on a desktop. You had to have a piece of software that probably cost a lot of money. It was not widely accessible. And so these image makers, image memes. I was talking to Brandon about this, like Good Guy Greg was one of these, or like the Insanity Wolf. And it would just be like one image of a duck. And the duck would be on sort of like a solid colored background and that would be the template. And then somebody would put white text with black, like block text, impact font on the top and the bottom. And that was like the image meme. And that was accessible in the sense that it could be like generated on Ms. Paint. It was free to generate it, basically. Then we got video editing cap cut Instagram reels as an editor called Edits. And all of a sudden it became easy for someone to take a vibreal and put different text over it. I send you a bunch of these where I'll find some crazy vibreal and I'll just recontextualize it with a new laughing thing, new caption, basically. And so the classic one is like those four, those four jets and the new Top Gun. And it's like when, when you and the boys all drive somewhere in separate cars or something like that, you know, as an example. But now you can generate, you know, full AI videos that can express the joke of the meme. And I think the next version of this is like software as a meme. S A A M, something like that. And we've been experimenting with the simulators. There's TBPN simulator, Jeremy Gaffon simulator. There are more simulators coming. And all of a sudden we, you know, the idea of building a video game, becoming a video game studio was like an impossible challenge. It would be months and months of time, maybe millions of dollars to get anything reasonable. So you had to be commercial about it. You could not do it as a comedy bit, but now you can. But incredible, increasingly it's going to be more and more just like a few prompts on your phone to get the piece of software that is that meme. And you can think about the JMail Suite from Riley Walls as another software as a meme moment where he's making a commentary on the Jeffrey Epstein saga and all of that, but he's instantiating the humor, the commentary in a piece of software that actually works. So there is a whole bunch of hack news going on. We're in a very weird week in terms of the news cycle because it's spring break and so a lot of executives at big tech companies are like, don't launch while my kids are out of school and we're going on vacation. I actually think this is my real theory. So we're in a little bit of a slow news week and you can see that like the Journal is covering announcements that happened last week. They're talking about Sora, they're talking about Disney, they're talking about, you know, things that, that are more like reflective. In Strathecary, Ben Thompson has sort of a 50 year retrospective on Apple. It's not driven by a news item. Like, it's not like Apple launched a new product this week. So Ben Thompson is taking a step back and reflecting. It's a great piece, but there are a ton of crazy hacks, starting with Axios. There is an active supply chain attack on axios, one of NPM's most dependent on packages. So if you have been vibe coding, Axios is a package that helps with HTTP requests. So it gets sucked into all sorts of different projects. And if you upgraded to the latest version, you basically got a virus with that. And if that's running in the cloud it's building and that's probably maybe bad because it could steal API keys or SSH keys. It could do a lot of things could wreak havoc on your system. Also, if you built this piece of software and you included the contaminated Axios installer or package locally, it could potentially weasel its way out of your local environment and get onto your desktop. It's a virus, so be careful out there and I'm sure people will be responding. The recommendation from Ferros who sort of broke the news over at Socket Security, is that if you use Axios, pin your version immediately and audit your lock files. Do not upgrade socket analysis confirmed that this was malware. Plain Crypto JS is an obfuscated dropper loader that deobfuscates embedded payloads and operational strings at runtime, dynamically loads FSOs and exec sync to evade static analysis, executes decoded shell commands, stages and copies payload files into ostemp and Windows program data directories, deletes and renames artifacts post execution to destroy forensic evidence. So very risky, I would say if you have installed this, you should just freak out basically.

John (9:52)

And if you break your comp, that's like the first thing you should do just like, try to slam.

Dylan Abrascato (9:56)

Yeah. Take the computer, throw it in the lake.

John (9:58)

That's how you should start.

Dylan Abrascato (10:01)

I concur. I mean, practical. I mean, there is going to be some sort of, like, power law response here where of the people that are victims of the attack, they will go after the most vulnerable with the highest, like, ransomware potential. And I think we're seeing that with one company. I believe Mercour was targeted, but I don't know if that's.

John (10:18)

Because I don't bel. Was that. Yeah. My understanding is that. Yeah. The crazy thing is you have this, like, Claude code leak that.

Dylan Abrascato (10:27)

That was completely separate.

John (10:29)

Even though I do believe they use Axios in Claude code. I saw something on that.

Dylan Abrascato (10:33)

Sure, sure, sure.

John (10:34)

And you have the Merkor leak, which is.

Dylan Abrascato (10:36)

Well, it's not a leak. It's ransom.

John (10:37)

It's a ransomware.

Dylan Abrascato (10:39)

Yeah. Someone stole some data.

John (10:40)

Yeah, they stole a bunch of data and now they're trying to, you know, get bids on it. We'll get to that in a little bit.

Dylan Abrascato (10:46)

Okay.

John (10:47)

And then there's this Axios supply chain attack.

Dylan Abrascato (10:51)

Yeah.

John (10:51)

Aneesh had a little bit more context. He said a tiny piece of code called Axios runs inside almost every app on your phone and every website you visit. Developers download it 100 million times a week. A few hours ago, someone poisoned it with malware that hands an attacker full control of your computer. If you've never heard of Axios, that's normal. It does one boring but important job. It lets apps talk to the Internet. When a website pulls up your feed or an online checkout processes your card, Axios is probably doing the work underneath. Over 173,000 other code packages plug into it. It's everywhere. The attacker stole a lead developer's login for npm. Think of it as an app store, but for code that programmers use. Once inside, they swapped the developer's email to an autonomous ProtonMail account and uploaded the poisoned version by hand. That jumped past every security check. The project normally runs before new code goes live, and this was not a rush job. The stackers staged the malware at least 18 hours before pulling the trigger. They built separate versions for Windows, Mac and Linux. They poisoned both the current version and an older 1 Within 39 minutes of each other, casting the widest. Net possible. Once the malware ran on a machine, it deleted itself to cover its tracks. The trick was smart. They never touched a single line of code inside Axios itself. Instead, they tucked in a fake add on called plain crypto JS built to pass as a well known trusted library. It copied the real library's description and author info so nothing looked off at a glance. When a developer installed Axios, this fake package quietly ran the malware on its own. When a smaller package called UA parser JS got hijacked back in 2021 with about 8 million weekly downloads, the security world treated it like a free for alarm fire. Axios has 100 million over 12xe exposure with 173,000 packages depending on it socket. The security firm that flagged this caught it in about six minutes. That's fast, but six minutes is still plenty of time for automated systems at companies everywhere to pull and install the bad version before anyone can react. If you or your team run axios freak tf out, no lock your version to 1.14.0, change every password, API key and access token on any machine that installed the compromised update, and check your network logs for connections to SFR, CL, a K.com or the IP address. 1421-120-673 Andre Karpathy said New supply chain

Dylan Abrascato (13:01)

attack this time for NPM Axios, the most popular HTTP client library with 300 million weekly downloads. That's a lot. Scanning my system Andrej Karpathy says he found a use imported from Google workspace/c CLI from a few days ago when I was experimenting with Gmail GCAL cli. The installed version luckily resolved to the previous version, the unaffected 1 13.5, but the project dependency is not pinned, meaning that if he did this earlier today, the code would have resolved, everything would have updated and he would have been pwned. It is possible to personally defend against these to some extent with local settings, e.g. release age constraints or containers or et cetera. But I think ultimately the defaults of package management projects, pip, npm, et cetera have to change so that a single injection, usually luckily fairly temporary in nature due to security scanning, does not spread through users at random and at scale via unpinned dependencies. So very, very crazy, crazy story.

John (14:10)

I just think it's bullish overall for cybersecurity. Like I think every cybersecurity company will probably do well. People are on edge already and everyone's even. Even though this type of attack has happened for years, long before, like the popularity of vibe coding, it just feels like there's a bunch of new solutions that are needed. The kind of incumbent cybersecurity players will do well. They're going to release a lot of new products. I think the question that I have is like why seven minutes? Right? Like if, why not check it before

Dylan Abrascato (14:42)

it's merged in in the first place?

John (14:44)

Yeah, yeah. Or just like, you know, these are machines, so theoretically they can be constantly monitoring versus like, yeah, I don't know.

Dylan Abrascato (14:53)

And, and the question is, I. We're going to be digging into this story more over the next few days, but I'm interested to know, like, it's found in seven minutes. When is it actually rolled back? If you look at 300 million weekly downloads, like, clearly there are people that were downloading it at that moment in time. At all seven of those minutes, there's probably like thousands of downloads, if not tens of thousands. How quickly was it rolled back? So is it only if you're in that seven minutes or was it. It was discovered in seven minutes and then it took them another 20 minutes to roll it back and stop serving the contaminated package. Understanding the scope of this, because it's very clear that as Andrej Karpathy explained, like he was actively using it every single day and yet was not caught in that seven minute window and so he was cleaned. And, and understanding the scope and scale of the impact is very much determined by how many just, just how, just, just how broad and how many installs happened during the contamination. Anyway, Will Brown has a good take. He says, I hope someone at Axios is reporting on this and I completely agree. It's going to be, it's going to be confusing when they do.

John (15:59)

Last night source code was leaked via map file in the NPM registry. There's just a link to.

Dylan Abrascato (16:08)

Wait, someone just actually do not click a link. If somebody ever says, hey, I got some really great source code here, just click this link. Probably don't click it. Let other people screenshot it. There's plenty of meta analysis over here. Seems messy. Seems unfortunate. Heart goes out to the folks who are dealing with the situation at the same time. Codex is open source. It's not the end of the world. But it did reveal a bunch of things about the roadmap and also some of the internal April Fools. That is the worst part. We love a secret surprise April Fool's joke. I love a good joke. And nothing spoils a joke like hearing about it a day early. Much more importantly, there are lots of other critiques of the way CLAUDE code is implemented. What are the bad.

John (16:53)

I don't think this hurts their business at all because people are using CLAUDE code to make other products and then also having to take basically a fork of CLAUDE code, maintain that, try to be shipping features against it. Which is, again, I think it seems to not be legal at all to just fork the code base just because it's out there.

Dylan Abrascato (17:13)

Oh, yeah, you can't just.

John (17:13)

People are converting it into other languages and maybe there's some argument there, but. But still, I don't think this hurts their business at all.

Dylan Abrascato (17:23)

But understand some of the secrets, what's special. But at the end of the day, all of these tools, especially something like Claude code, that's so new, like, it's more of, like, the process, it's more bad for.

John (17:34)

For the overall brand of vibe coding.

Dylan Abrascato (17:36)

Totally, totally. Yeah, yeah, it's rough.

John (17:39)

The irony here is that every time Anthropic has released any feature related to cybersecurity, all the big cyber companies have been selling off, you know, ten tens of billions of dollars.

Dylan Abrascato (17:50)

Yeah, yeah, yeah. The question of, like, yeah, does this build trust in, like, using viacode?

John (17:55)

Yeah, so. So overall, overall, it hurts some trust, but again, very obviously going to get through this.

Dylan Abrascato (18:02)

Yes. So the. How it started, how it's going is of course, landing like a ton of bricks. In the last 30 days, 100% of the contributions to Claude code were written by Claude code. And how it's going is that it leaked the source code, which is not what you want to have happen. This is like, you know, you didn't get to watch the super bowl. You have it DVR'd at home. Do you want spoilers? Should we review the April Fool's joke, or should we leave it unspoiled?

John (18:30)

It's cool. It's very cool.

Dylan Abrascato (18:32)

You've already read it.

John (18:33)

I read through it, but it's not. It's not to my.

Dylan Abrascato (18:36)

Were you belly.

John (18:37)

I don't think we're getting a knee slapper out of it, but it's very cool.

Dylan Abrascato (18:40)

Okay.

John (18:41)

I think it'll be cute.

Dylan Abrascato (18:42)

Okay, well, then we can move on. Tookie summed it up here. Do you understand what just happened at Anthropic? Someone on their team ran a production build of Claude code. The compiler generated a map file, which is literally a blueprint that reverses the entire code base back to its original source, and then they published it straight to NPM for the whole world to download. And it really does show you how fast the NPM downloads. There are people that are downloading it every single minute. And so if, even if it's only up there for a minute, someone's going to get it, and then all they need to do is send it to somebody, zip it, and post a link on X and it goes viral. It's like locking every door in your house, installing cameras, hiring armed guards, then accidentally uploading your floor plans to Google Maps. Does that matter? No, that's a bad analogy. I don't like that analogy. Floor plans are not why I lock every door in my house. I install cameras, I hire armed guards. Aren't floor plans public on like Zillow oftentimes.

John (19:33)

Let's go over to Lee San. Algae.

Dylan Abrascato (19:35)

Yes, yes, yes.

John (19:35)

A few takeaways from the Claude code leak. Anthropic is actively using Mythos for development.

Dylan Abrascato (19:40)

Okay.

John (19:41)

They are already at Capybara V8. We learned last week that Capybara is are extremely deadly, but can be deadly in the right context. Capybara still has issues.

Dylan Abrascato (19:52)

The foreshadowing. The foreshadowing is crazy. We were talking about how the Faustian bargain that is getting a capybara as a pet seems so cute, but it can bite you.

John (20:02)

Capybara has 1 million token context window and fast mode.

Dylan Abrascato (20:08)

Numbat is another interesting code name tagged with Odell Launch Remove the section where we launched Numbat. Fennec seems to be the Fennec Fox. Fennec Fox is very cute, but also not a domesticated animal. How about we get some golden retriever code names? How about Big Fluffy Poodle? That's a good code name for your animal themed AI model. Anyway, let me tell you about console. Console builds AI agents that automate 70% of it. HR and finance support, giving employees instant resolution for access requests and password resets. And let me also tell you about Lambda Lambda is the superintelligence cloud building AI supercomputers for training and inference that scale from one GPU to hundreds of thousands.

John (20:49)

Arvid says hot take. Anthropic leaked Claude code intentionally to get a Nerdosphere code review it would have never gotten if they had just open sourced it.

Dylan Abrascato (20:59)

Oh, that's actually true.

John (21:00)

Way more intentional. You don't leak your entire feature roadmap. You don't do. I mean, it's funny. And I'm sure they'll make the most of this.

Dylan Abrascato (21:07)

This is 4D chess right here.

John (21:09)

But I'm not seeing the 4D chess.

Dylan Abrascato (21:11)

I'm seeing the 4D chess convinced this is. I mean, we're in completely uncharted territory for marketing stunts and pre releases and sneaky footage that goes viral and maybe was planted. You don't know. And it's like some leaked account. Like, I don't know. I think everything's. I think the gloves are off. Everything's on the table. This could be an April Fool's joke. This could be a stunt to draw to drive attention to an open source move. Although Tyler, you said that Dario is not a fan of open source at all. Right? He's like against unilaterally. He doesn't want to do open source. I feel like isn't there some steel man there where if you open source like Opus 2 or something that's really old, it's entirely commoditized in the research community. So all of those secrets that went into making Opus 2 good, those have been commoditized, they've been discussed at the house parties and sf the researchers have moved from one place to another. So everyone knows these, they've implemented, they're available as open source. But by, by open sourcing your model you can share with more of like the up and coming academic community. Like if, if I'm a, if I'm a computer scientist. Yeah, but if all the research is already commoditized and yeah, I guess you could just use the other ones. It doesn't really have a benefit. Maybe.

John (22:29)

Yeah. So has any. Has anyone at Anthropic? Has anyone at Anthropic commented on this at all?

Dylan Abrascato (22:34)

I haven't seen anything. Anyone? There is news out of out of Google A Google paper warns that warns crypto on quantum risk ahead of 2029 timeline so we've heard about the risk of quantum computing affecting the cryptocurrency industry, crypto projects broadly. There is some new research out of Google that provides some more perspective. So Google researchers have warned that future quantum computers may be able to break some of the cryptography protecting Bitcoin and other digital assets with fewer resources than previously thought, adding urgency to the debate over how the industry should prepare. The researchers did not indicate such a machine exists today, but said new work suggests the computing power needed to carry out that kind of attack may be lower than earlier estimates had suggested. In a Google Research blog post. This is from Bloomberg. The researchers said that a future quantum computer could break elliptic curve cryptography, a form of public key encryption used across much of the market. Their latest estimate points to a 20 fold reduction in the quantum computing hardware needed to break what's known as ecdlp 256, a mathematical problem that helps secure crypto wallets and transactions. That does not mean Bitcoin and Ethereum are suddenly exposed, but the researchers in the white paper dated Monday said the clearest defense is a shift towards post quantum cryptography, or pqc. I'm sure this will be a hot topic over the next few months, a newer form of security designed to withstand attacks from powerful machines. They also urge the crypto industry to cut avoidable risks. And in the meantime, we urge all vulnerable cryptocurrency communities to join the migration to PQC without delay. Google cast the paper as a warning meant to give the industry time to time to act, not as a prediction of imminent collapse. Last week, the tech giant introduced a timeline to fully migrate its own security systems to post Quantum cryptography by 2029 have swirled for years. In January, Coinbase established an independent advisory board to study what quantum computing could mean for the blockchain. That same month, Christopher Wood, global head of equity strateg at Jefferies, removed a 10% allocation to Bitcoin from his model portfolio, citing fears that the advent of quantum computing could undermine the token. The time left before such machines arrive still appears longer than the time needed to move public blockchains to post quantum cryptography.

John (24:55)

One concern that people in the community have had that I've seen talked about is this idea that if you did have a computer powerful enough to crack these encryptions, unless you were like Google, and you already had billions and billions and billions of dollars of cash flow, you wouldn't exactly stand up and say like, hey, I have cracked Bitcoin. Because the incentive for a certain team would just be to go around and find these wallets that were maybe, maybe didn't have any activity for a long time and just start cracking those individually. Because if you just stood up and said, hey, I have a quantum computer that destroys Bitcoin, the, the price would go down and then the hacker wouldn't get any benefit from it.

Dylan Abrascato (25:38)

What are quantum stocks doing on this news?

John (25:40)

Quantum probably ripping.

Dylan Abrascato (25:42)

They rip on everything. So Nick Carter was talking about this. He said many are wondering what Google saw that caused them to revise their post quantum cryptography transition deadline to 2029. This week it was this and it's from research, google research.google, which we will go through. Max, the VC says Google's basically saying we've we've cut the quantum resources needed to break Bitcoin's encryption by 20x. We can now break it, we can prove it. We're just not going to tell you how we've slowed down research to give crypto a chance. You have until 2029 to figure out a solution. Good luck. Elon chimed in and said, on the plus side, if you forgot your password, the password to your wallet, it will be accessible in the future

John (26:24)

also to everyone else.

Dylan Abrascato (26:25)

So the Chance that NASA lands on the moon. We were tracking this yesterday. The missions are starting to happen for 2020. Kalshi is now at 14% before 2027 is at 4.7%. So they are racing. Of course. This Artemis 2 mission is not boots on the ground on the moon. It is rocketing around the moon. We'll have more about this tomorrow.

John (26:49)

They're just going to check it out.

Dylan Abrascato (26:50)

They're going to be gone for 10 days. They're going to be in space for 10 days. Brendan Gorell was doing some deep dives on the technology. The streaming technology was what we really care about here. That will be on board something like 20 cameras, 4K live streams, laser beams to make sure it's low latency. Super chats, a lot of fun. Super chats would be good. We got to get a chat going. I'm sure there might actually be because they usually stream on YouTube. And so I wouldn't be surprised if.

John (27:17)

Is it going to be a 24, 7, like, perpetual stream that's always on?

Dylan Abrascato (27:21)

Yes.

John (27:22)

Even when the astronauts are taking a sleep.

Dylan Abrascato (27:25)

Yeah.

John (27:25)

Taking a little nap.

Dylan Abrascato (27:26)

Yeah. Yeah.

John (27:27)

Okay. All the conspiracy theorists are going to be sitting there watching it very closely and then pausing.

Dylan Abrascato (27:31)

And there was a glitch there.

John (27:33)

Did you see that glitch?

Dylan Abrascato (27:33)

That was. That was vfx. That was AI. No, this is my mark. I will believe that it's real if I see an astronaut put three fingers in front of their face.

John (27:43)

Yeah.

Dylan Abrascato (27:43)

Because this is the one thing that the AI can't do right now. If you're ever on a zoom call with someone you suspect of being fake, a scammer who said, hey, let's get on zoom. Let's talk about some financial investment opportunity. And it looks like someone you think is the person, but you suspect that it might not be. And they will be able to show you. Look. Look at the fingers. The fingers are perfect. It's fine. It's fine. That's because this part is not AI. Just the face is AI. This is the deep fake stuff that's happening. So what you have to do is you have to ask them to hold up three fingers. They'll be like, yeah, three fingers. This is fine. Right? I satisfy the task. You got to say, no, put the three fingers in front of your face. Because if you put the three fingers in front of your face, the AI gets confused and it breaks the deep fake that's happening underneath.

John (28:27)

Elon Colossus shares. Elon has spent a decade trying to control an AI lab. He tried to absorb DeepMind into Tesla in 2014, then OpenAI in 2018. When that failed, an intern spoke up. It did not. Interesting.

Dylan Abrascato (28:40)

Okay, let's read through this.

John (28:41)

He also tried to control xai to some degree.

Dylan Abrascato (28:45)

Doesn't he control.

John (28:45)

Well, he controls it, but at what cost, right? All. All seven co founders.

Dylan Abrascato (28:50)

Oh, true, true, true.

John (28:51)

That's what you're referring to anyways from. From the book. Pushing back against Musk's obsession with the race against Google and DeepMind, Brockman added, it doesn't matter who wins if everyone dies. Musk responded. The next morning at 3:52am he confronted Brockman with a proposal that recalled Pichai's pitch. OpenAI should spin into Tesla. Initially, OpenAI's team could accelerate Tesla's development of autonomous vehicles. Next, it could use the profits from self Driving car fund its AGI moonshot. Tesla is the only path that could even hope to hold a candle to Google, Musk declared. Even then, the probability of being a counterweight to Google is small. It just isn't zero. At an all hands meeting on the top floor of a converted truck factory that housed OpenAI, Musk announced to the employees that he was quitting the lab,

Dylan Abrascato (29:34)

scornfully adding that I need Raptors. I need a new Ford Raptor potentially every day. We gotta put this lab above inside

John (29:43)

of a truck factory.

Dylan Abrascato (29:44)

This is amazing.

John (29:45)

Scornfully adding that OpenAI would have to sprint faster to stay relevant. I guess they did.

Dylan Abrascato (29:50)

I guess.

John (29:51)

Hoping to lure away some researchers, he declared there was a much better chance of building AGI at a strong business like Tesla.

Dylan Abrascato (29:57)

Yeah.

John (29:57)

Showing courage, or perhaps just youthful innocence, an intern asked Musk if speed might be reckless from a safety perspective. Besides, wasn't developing AI at a for profit company like Tesla the same as creating it at a for profit company like Google? Isn't this going back to what you said you didn't want to do? The intern demanded. You're a jackass. Mus retorted. Then he stormed out of the meeting. That intern, Tyler Cosgrove.

Dylan Abrascato (30:20)

No, that intern was Steve Jobs. Just kidding.

John (30:23)

It's been an honor.

Dylan Abrascato (30:24)

See you tomorrow. Goodbye flashbang. Bye.