WEBVTT - Nuclear Space Junk Cleaners, Inc. - Week in Tech

0:00:11.600 --> 0:00:14.800
<v Speaker 1>Taylor, Rie, Kyle, I've been obsessed with heists in the

0:00:15.000 --> 0:00:17.730
<v Speaker 1>AI era. And heists gone wrong are, of course, some

0:00:17.750 --> 0:00:20.150
<v Speaker 1>of the great comic gold. Has anyone been following the

0:00:20.190 --> 0:00:21.370
<v Speaker 1>stolen NVIDIA trucks?

0:00:21.870 --> 0:00:22.410
<v Speaker 2>No.

0:00:22.829 --> 0:00:23.680
<v Speaker 3>What's going on?

0:00:23.880 --> 0:00:25.420
<v Speaker 4>It wasn't me, if that's what you're asking.

0:00:26.150 --> 0:00:28.190
<v Speaker 1>So there are a couple of trucks with NVIDIA branding

0:00:28.350 --> 0:00:33.270
<v Speaker 1>on them that some thieves thought were full of NVIDIA chips, which.

0:00:33.150 --> 0:00:34.950
<v Speaker 5>Of course are very, very valuable.

0:00:36.130 --> 0:00:39.750
<v Speaker 1>And so the trucks were stolen, but it happened they

0:00:39.790 --> 0:00:44.530
<v Speaker 1>were just full of sand. And not the sand that's

0:00:44.610 --> 0:00:47.790
<v Speaker 1>used to make chips. The trucks belong to Plus AI,

0:00:47.890 --> 0:00:51.390
<v Speaker 1>who makes self-driving trucks. And in order to make self-driving

0:00:51.430 --> 0:00:54.270
<v Speaker 1>trucks good, you have to simulate cargo loads. So they're

0:00:54.290 --> 0:00:58.190
<v Speaker 1>doing that with tons of sand, 20,000 tons per truck.

0:00:58.370 --> 0:01:01.570
<v Speaker 1>They also happen to have a partnership with NVIDIA. So

0:01:01.590 --> 0:01:04.330
<v Speaker 1>the NVIDIA logos were just on the truck to kind

0:01:04.370 --> 0:01:08.110
<v Speaker 1>of flex about the NVIDIA partnership, like the NASA logo

0:01:08.330 --> 0:01:09.029
<v Speaker 1>on my computer.

0:01:09.190 --> 0:01:10.209
<v Speaker 3>Good advertising.

0:01:10.310 --> 0:01:13.209
<v Speaker 4>If I see someone selling sand on eBay, I will

0:01:13.250 --> 0:01:14.069
<v Speaker 4>know where it came from.

0:01:14.090 --> 0:01:18.399
<v Speaker 1>Well, actually, Plus AI managed to recover the trailers and

0:01:18.540 --> 0:01:20.380
<v Speaker 1>all 40,000 tons of sand.

0:01:20.400 --> 0:01:21.060
<v Speaker 5>So happy ending.

0:01:21.140 --> 0:01:21.740
<v Speaker 2>Happy ending.

0:01:26.950 --> 0:01:27.729
<v Speaker 5>Welcome to Tech Stuff.

0:01:27.790 --> 0:01:30.050
<v Speaker 1>I'm Oz Veloshian, and this is The Week in Tech,

0:01:30.150 --> 0:01:32.850
<v Speaker 1>where I'm joined by the world's most plugged-in reporters to.

0:01:32.810 --> 0:01:35.229
<v Speaker 5>Break down what's really happening in tech right now.

0:01:35.860 --> 0:01:38.940
<v Speaker 1>Today, we're joined by Reid Abregotti, tech editor for Semaphore

0:01:39.140 --> 0:01:41.480
<v Speaker 1>and host of the new podcast, as of this week,

0:01:41.560 --> 0:01:45.420
<v Speaker 1>Future Proof, Taylor Lorenz of UserMag, and back from leave,

0:01:45.660 --> 0:01:48.300
<v Speaker 1>Kyle Chaker, who writes the Infinite Scroll column for The

0:01:48.360 --> 0:01:48.740
<v Speaker 1>New Yorker.

0:01:48.780 --> 0:01:49.260
<v Speaker 4>Welcome, all.

0:01:49.480 --> 0:01:50.340
<v Speaker 2>Thanks for having us.

0:01:50.620 --> 0:01:52.610
<v Speaker 5>Reid, welcome to the podcasting ranks.

0:01:53.570 --> 0:01:54.090
<v Speaker 2>Can't hear you, Reid.

0:01:54.110 --> 0:01:54.760
<v Speaker 5>Oh, we can't hear you?

0:01:57.000 --> 0:01:58.440
<v Speaker 3>First you have to turn your mic on.

0:01:59.500 --> 0:02:01.020
<v Speaker 4>I'm learning all the rules now.

0:02:01.040 --> 0:02:04.840
<v Speaker 5>Don't mute your mic.

0:02:05.020 --> 0:02:07.520
<v Speaker 1>Well, starting off with you, I mean, first, just give

0:02:07.560 --> 0:02:09.040
<v Speaker 1>us a brief plug for the new podcast, but then

0:02:09.080 --> 0:02:10.400
<v Speaker 1>I want to ask you what's going on in space.

0:02:10.700 --> 0:02:13.610
<v Speaker 4>Yeah, well, it's called Future Proof. And, you know, we're

0:02:13.630 --> 0:02:16.790
<v Speaker 4>going to interview people from all areas of the tech

0:02:16.830 --> 0:02:19.840
<v Speaker 4>industry and go deep on on topics and try to

0:02:19.980 --> 0:02:23.960
<v Speaker 4>teach people something. It'll be newsy, journalistic, but also really

0:02:24.000 --> 0:02:26.780
<v Speaker 4>go deep on stuff and help listeners understand.

0:02:26.800 --> 0:02:28.160
<v Speaker 5>I'm excited to check it out.

0:02:29.000 --> 0:02:30.900
<v Speaker 1>This week's story for you feels a bit like the

0:02:31.000 --> 0:02:35.400
<v Speaker 1>plot of a 90s Bond movie involving the US competing

0:02:35.440 --> 0:02:40.200
<v Speaker 1>with Russia and China to build nuclear powered permanent bases.

0:02:39.880 --> 0:02:42.359
<v Speaker 5>On the moon. What's going on? I mean, is this

0:02:42.380 --> 0:02:43.209
<v Speaker 5>like a fantasy or?

0:02:44.410 --> 0:02:47.169
<v Speaker 4>It depends on who you ask. I personally like, you know,

0:02:47.230 --> 0:02:50.730
<v Speaker 4>I think everything in the space industry feels like fantasy

0:02:50.810 --> 0:02:53.310
<v Speaker 4>until it actually happens. I remember when I first came

0:02:53.370 --> 0:02:57.169
<v Speaker 4>out to the tech industry, SpaceX was sort of just

0:02:57.270 --> 0:03:01.650
<v Speaker 4>becoming a thing. And people were talking about satellites, you know,

0:03:01.690 --> 0:03:06.450
<v Speaker 4>in space providing internet. And really smart people told me

0:03:06.490 --> 0:03:10.030
<v Speaker 4>that was completely impossible. It would never happen. Now I own,

0:03:10.210 --> 0:03:13.010
<v Speaker 4>you know, two Starlinks. Um, So I just take the

0:03:13.070 --> 0:03:15.750
<v Speaker 4>timelines for these things and I just extend them in

0:03:15.790 --> 0:03:18.750
<v Speaker 4>my mind, but I don't dismiss anything outright. I mean,

0:03:18.870 --> 0:03:22.050
<v Speaker 4>nothing here is totally impossible, right? But, you know, does

0:03:22.110 --> 0:03:25.460
<v Speaker 4>it make economic sense? Will it make economic sense in

0:03:25.480 --> 0:03:27.820
<v Speaker 4>the near future? That I don't, I just don't know.

0:03:28.180 --> 0:03:29.880
<v Speaker 1>I think the US has tried it once before and

0:03:29.940 --> 0:03:34.320
<v Speaker 1>Russia has been sending nuclear reactors into space since the 60s.

0:03:34.360 --> 0:03:37.560
<v Speaker 1>But somehow this kind of new space race thing is

0:03:37.600 --> 0:03:38.470
<v Speaker 1>particularly fascinating.

0:03:38.510 --> 0:03:39.450
<v Speaker 5>Kyle, have you been following it?

0:03:40.050 --> 0:03:42.850
<v Speaker 6>Just as far as the data centers in space. I mean,

0:03:42.880 --> 0:03:46.920
<v Speaker 6>I think that whole concept is really appealing to me.

0:03:47.340 --> 0:03:49.740
<v Speaker 6>And it kind of seems like the only answer. If

0:03:50.340 --> 0:03:52.780
<v Speaker 6>we're kind of having all these fights over data centers

0:03:53.060 --> 0:03:55.780
<v Speaker 6>on Earth, you know, maybe it would be better to

0:03:55.820 --> 0:03:58.800
<v Speaker 6>put them in space and have them powered in some

0:03:58.840 --> 0:03:59.260
<v Speaker 6>other way.

0:04:00.490 --> 0:04:01.090
<v Speaker 3>So yeah, I don't know.

0:04:01.190 --> 0:04:04.090
<v Speaker 6>I think it reads right about the timelines extending longer

0:04:04.150 --> 0:04:04.950
<v Speaker 6>than you might think.

0:04:05.270 --> 0:04:07.720
<v Speaker 4>But I mean, Kyle, do you know what a space...

0:04:07.750 --> 0:04:10.630
<v Speaker 4>I've actually looked into this recently. A space data center

0:04:10.750 --> 0:04:14.550
<v Speaker 4>is not like a floating data center. It is basically,

0:04:15.210 --> 0:04:18.529
<v Speaker 4>you have a bunch of satellites that have a GPU

0:04:18.589 --> 0:04:22.460
<v Speaker 4>or two or a rack, and they're spread out very

0:04:22.560 --> 0:04:25.839
<v Speaker 4>far apart, and they're connected by lasers. So they communicate

0:04:25.880 --> 0:04:28.980
<v Speaker 4>with each other by lasers instead of on Earth through

0:04:29.040 --> 0:04:32.390
<v Speaker 4>fiber optic cable or copper, right? And because.

0:04:32.900 --> 0:04:35.420
<v Speaker 6>It's not a Death Star. It's not like one floating

0:04:35.500 --> 0:04:36.779
<v Speaker 6>massive data center.

0:04:36.920 --> 0:04:37.140
<v Speaker 3>Right.

0:04:37.200 --> 0:04:40.500
<v Speaker 4>But because, you know, there's no air in space, you

0:04:40.520 --> 0:04:42.420
<v Speaker 4>can't cool these things in the same way you cool

0:04:42.440 --> 0:04:45.980
<v Speaker 4>them on Earth. So the idea is that you'll somehow

0:04:47.040 --> 0:04:50.550
<v Speaker 4>pull the heat away from these GPUs and dissipate it

0:04:50.750 --> 0:04:54.030
<v Speaker 4>on a massive... They're going to essentially like a massive

0:04:54.130 --> 0:04:56.429
<v Speaker 4>heat sink that's about the size of a tennis court.

0:04:56.529 --> 0:04:59.790
<v Speaker 4>I mean, it is... like really kind of just the

0:04:59.850 --> 0:05:03.990
<v Speaker 4>craziest concept you can possibly imagine. But it's not impossible.

0:05:04.110 --> 0:05:06.490
<v Speaker 4>I mean, but I don't know if I agree that

0:05:06.550 --> 0:05:08.450
<v Speaker 4>that's going to be the thing that happens before we

0:05:08.470 --> 0:05:10.550
<v Speaker 4>just get our act together on Earth and build some

0:05:10.570 --> 0:05:11.410
<v Speaker 4>data centers already.

0:05:11.790 --> 0:05:14.510
<v Speaker 1>Yeah, I mean, the concept of space junk is kind

0:05:14.560 --> 0:05:16.710
<v Speaker 1>of interesting. I mean, sending up this tennis court, or

0:05:16.740 --> 0:05:20.640
<v Speaker 1>I think in some cases even football pitch or field size,

0:05:20.720 --> 0:05:24.360
<v Speaker 1>kind of non-convective heat dispersing panels into space. I mean,

0:05:24.740 --> 0:05:27.020
<v Speaker 1>you have to wonder... what the implications of all that

0:05:27.060 --> 0:05:29.820
<v Speaker 1>stuff floating around in orbit are. And I think some

0:05:29.860 --> 0:05:31.720
<v Speaker 1>of this, when I first saw the story, the headline

0:05:31.740 --> 0:05:34.320
<v Speaker 1>about the nuclear reactors in space, I kind of assumed

0:05:34.380 --> 0:05:37.320
<v Speaker 1>somehow it had to do with power generation for AI.

0:05:37.360 --> 0:05:39.320
<v Speaker 1>But to my great surprise, it wasn't about that. It

0:05:39.360 --> 0:05:41.059
<v Speaker 1>was about, go ahead, Taylor.

0:05:41.420 --> 0:05:44.279
<v Speaker 2>I'm going to start a business that is a space

0:05:44.420 --> 0:05:47.960
<v Speaker 2>junk removal cleanup business, because I think this is going

0:05:47.990 --> 0:05:51.160
<v Speaker 2>to be huge business Going forward, I mean, we're about

0:05:51.180 --> 0:05:53.940
<v Speaker 2>to have something like a million satellites or Elon wants

0:05:53.960 --> 0:05:57.260
<v Speaker 2>to scale to a million Starlink satellites. And I think

0:05:57.380 --> 0:05:59.980
<v Speaker 2>if we put data centers up there too, yeah, there's

0:06:00.020 --> 0:06:02.700
<v Speaker 2>just going to be a lot of debris. And I

0:06:02.720 --> 0:06:04.400
<v Speaker 2>think that poses risks.

0:06:05.000 --> 0:06:06.060
<v Speaker 5>Especially when it's nuclear.

0:06:07.490 --> 0:06:08.010
<v Speaker 3>I mean, right.

0:06:08.029 --> 0:06:10.290
<v Speaker 4>It's kind of, well, nuclear doesn't have that much risk

0:06:10.330 --> 0:06:12.830
<v Speaker 4>in space. I mean, you know, nuclear meltdown in space isn't...

0:06:12.850 --> 0:06:16.080
<v Speaker 4>Unless it falls to Earth. Well, yeah, it'll burn up

0:06:16.160 --> 0:06:17.980
<v Speaker 4>before it falls to earth. But I mean, what happens

0:06:18.000 --> 0:06:21.180
<v Speaker 4>to these giant, you know, heat dissipating football field or

0:06:21.220 --> 0:06:23.910
<v Speaker 4>tennis court size things if like a little, a little

0:06:24.029 --> 0:06:26.310
<v Speaker 4>speck runs into it and puts a hole in it? Like,

0:06:26.350 --> 0:06:28.950
<v Speaker 4>does it still work? And then if something breaks, they

0:06:28.970 --> 0:06:31.360
<v Speaker 4>just drop it down and let it burn in the atmosphere,

0:06:31.380 --> 0:06:34.650
<v Speaker 4>which is I'm sure horrifying to people who are here

0:06:34.710 --> 0:06:37.220
<v Speaker 4>trying to get their hands on like a single GPU

0:06:37.279 --> 0:06:40.760
<v Speaker 4>right now. But I thought the nuclear reactor thing is like,

0:06:40.800 --> 0:06:42.980
<v Speaker 4>you got to build those on the moon, right? I mean,

0:06:43.060 --> 0:06:45.100
<v Speaker 4>that was what you were talking about. Because if you

0:06:45.140 --> 0:06:48.350
<v Speaker 4>want to send Mars missions... Staging post.

0:06:48.760 --> 0:06:49.110
<v Speaker 3>Yeah.

0:06:49.170 --> 0:06:50.930
<v Speaker 4>Is that what... That's what you were talking about, right?

0:06:50.950 --> 0:06:51.750
<v Speaker 5>Yeah, exactly.

0:06:51.810 --> 0:06:55.210
<v Speaker 1>And so the current like solar power cannot generate enough

0:06:55.290 --> 0:07:00.010
<v Speaker 1>power on the moon to have actually warm habitable bases.

0:07:01.100 --> 0:07:01.250
<v Speaker 4>Right.

0:07:01.270 --> 0:07:01.359
<v Speaker 2>So.

0:07:01.990 --> 0:07:04.550
<v Speaker 1>And China and Russia are collaborating. Russia have the best

0:07:04.730 --> 0:07:08.869
<v Speaker 1>space nuclear technology. China, I guess, have good rocketry. So

0:07:08.970 --> 0:07:10.310
<v Speaker 1>the new Cold War in space is on.

0:07:10.330 --> 0:07:13.530
<v Speaker 4>Do you guys watch For All Mankind? Just out of curiosity,

0:07:14.230 --> 0:07:17.550
<v Speaker 4>did you watch that show? No, I missed it. I mean,

0:07:17.570 --> 0:07:20.270
<v Speaker 4>I think if you're interested in this topic, you've got

0:07:20.290 --> 0:07:24.150
<v Speaker 4>to watch For All Mankind. Just go. It's on Apple TV.

0:07:24.190 --> 0:07:28.580
<v Speaker 4>Go watch it. It's a sort of alternative history show

0:07:28.760 --> 0:07:31.720
<v Speaker 4>about what would have happened if the if the Cold

0:07:31.760 --> 0:07:34.940
<v Speaker 4>War sort of evolved a little bit differently and space

0:07:35.020 --> 0:07:37.300
<v Speaker 4>just continued to be the thing that we put all

0:07:37.340 --> 0:07:40.740
<v Speaker 4>of our, you know, human effort and ingenuity into. And like,

0:07:40.840 --> 0:07:42.820
<v Speaker 4>I don't want to spoil the show for you guys,

0:07:42.880 --> 0:07:45.970
<v Speaker 4>but you know, a lot of interesting stuff happens in

0:07:46.050 --> 0:07:48.350
<v Speaker 4>space on a timeline that is not, that is a

0:07:48.370 --> 0:07:51.170
<v Speaker 4>lot more accelerated than we have today. It's a really

0:07:51.230 --> 0:07:54.300
<v Speaker 4>fun show. I think it's, you know, I've enjoyed it.

0:07:54.870 --> 0:07:56.650
<v Speaker 3>Do we need more space propaganda?

0:07:56.680 --> 0:08:01.900
<v Speaker 6>Like pro-space propaganda? pro-space content to encourage us all.

0:08:02.360 --> 0:08:05.140
<v Speaker 4>It beats the propaganda we have right now. I mean,

0:08:05.160 --> 0:08:09.640
<v Speaker 4>I'll take that over all the current propaganda.

0:08:09.800 --> 0:08:12.500
<v Speaker 1>I've got a NASA sticker on my computer. What's the

0:08:12.540 --> 0:08:14.520
<v Speaker 1>take on Jared Eisenman? I mean, the head of NASA,

0:08:14.560 --> 0:08:18.620
<v Speaker 1>Trump had initially rejected him during the Trump-Elon Fodor, but

0:08:18.660 --> 0:08:22.860
<v Speaker 1>then changed his mind and Eisenman was confirmed, obviously, a

0:08:22.960 --> 0:08:26.240
<v Speaker 1>private sector billionaire. What's he doing at NASA? And what's

0:08:26.260 --> 0:08:29.000
<v Speaker 1>the public-private relationship in space in the US today, Reid?

0:08:29.680 --> 0:08:32.940
<v Speaker 4>Well, I mean, he's certainly helping Elon, right? There was

0:08:32.960 --> 0:08:36.040
<v Speaker 4>a lot of tension with Elon and the Biden administration.

0:08:36.120 --> 0:08:40.660
<v Speaker 4>And I think Jared's helping Elon. There's less tension between

0:08:40.720 --> 0:08:43.500
<v Speaker 4>SpaceX and NASA. But, you know, I haven't heard any

0:08:43.559 --> 0:08:46.420
<v Speaker 4>sort of controversies about him. He seems to be, you know,

0:08:46.520 --> 0:08:49.260
<v Speaker 4>doing a fine job. We'll see what the effects of

0:08:49.360 --> 0:08:53.000
<v Speaker 4>his term are. But I mean, the general trend, I think,

0:08:53.080 --> 0:08:55.200
<v Speaker 4>in NASA is like more and more of this is

0:08:55.240 --> 0:08:59.420
<v Speaker 4>becoming privatized. You know, there's good things and bad things

0:08:59.460 --> 0:09:01.900
<v Speaker 4>about that, right? I think the public interest mission of

0:09:02.000 --> 0:09:03.980
<v Speaker 4>space that I think we're all used to from our

0:09:04.020 --> 0:09:06.360
<v Speaker 4>childhood of, you know, space shuttle going up and doing

0:09:06.380 --> 0:09:09.520
<v Speaker 4>all these science experiments. I mean, some of that is

0:09:09.580 --> 0:09:11.800
<v Speaker 4>for sure going to be going to be lost when

0:09:11.830 --> 0:09:13.689
<v Speaker 4>the private sector sort of takes over. And I think

0:09:13.710 --> 0:09:16.710
<v Speaker 4>that's kind of sad. But at the same time, it's incredible,

0:09:16.830 --> 0:09:20.110
<v Speaker 4>the stuff that has been accomplished. I think it's amazing,

0:09:20.170 --> 0:09:23.010
<v Speaker 4>not to mention just having a Starlink on my camper

0:09:23.030 --> 0:09:25.250
<v Speaker 4>van in California. That's like the ultimate life.

0:09:25.370 --> 0:09:29.220
<v Speaker 1>So I do want to just note that on the

0:09:29.340 --> 0:09:32.840
<v Speaker 1>kind of safety issue with the nuclear reactors in space,

0:09:32.880 --> 0:09:37.040
<v Speaker 1>there was a Russian nuclear reactor thing that came down

0:09:37.100 --> 0:09:40.280
<v Speaker 1>to Earth. And US intelligence say that five people were killed.

0:09:40.300 --> 0:09:43.220
<v Speaker 1>The Russians deny this. But just before we go to

0:09:43.240 --> 0:09:45.239
<v Speaker 1>the break, Taylor, I mean, this idea of kind of

0:09:45.380 --> 0:09:49.260
<v Speaker 1>cleaning space junk and including nuclear space junk, have you

0:09:49.280 --> 0:09:50.679
<v Speaker 1>met any companies in this space?

0:09:51.620 --> 0:09:54.250
<v Speaker 2>Yeah, I talked to Orbital, which is, you know, seeking

0:09:54.280 --> 0:09:58.350
<v Speaker 2>to put the data centers in space recently and visited

0:09:58.450 --> 0:10:01.940
<v Speaker 2>their offices in LA. So I do think that there's

0:10:01.980 --> 0:10:03.480
<v Speaker 2>sort of like a space race with a lot of

0:10:03.520 --> 0:10:07.240
<v Speaker 2>different startups right now trying to build out infrastructure in

0:10:07.260 --> 0:10:07.700
<v Speaker 2>that realm.

0:10:07.720 --> 0:10:09.370
<v Speaker 5>What did you learn at Orbital?

0:10:09.800 --> 0:10:11.810
<v Speaker 2>What they're doing is cool. I mean, I think it's

0:10:11.870 --> 0:10:13.830
<v Speaker 2>just like they're up against a lot of competition, as

0:10:13.890 --> 0:10:16.849
<v Speaker 2>Reid said, too. It's like everything seems impossible until it

0:10:17.300 --> 0:10:19.720
<v Speaker 2>somebody does it. And I personally think that the data

0:10:19.740 --> 0:10:22.100
<v Speaker 2>center fight is not going away anytime soon, and we're

0:10:22.120 --> 0:10:23.860
<v Speaker 2>going to need more compute. So yeah, if they can

0:10:23.880 --> 0:10:24.559
<v Speaker 2>put them in space.

0:10:25.160 --> 0:10:25.520
<v Speaker 3>Why not?

0:10:26.059 --> 0:10:28.800
<v Speaker 4>Well, what's interesting about Orbital is the founder was the

0:10:28.870 --> 0:10:32.830
<v Speaker 4>scooter guy, right? So he had a scooter startup in

0:10:32.870 --> 0:10:36.250
<v Speaker 4>San Francisco. And then he kind of worked for Ford,

0:10:36.290 --> 0:10:36.650
<v Speaker 4>I think.

0:10:36.710 --> 0:10:37.330
<v Speaker 5>And then he.

0:10:37.470 --> 0:10:38.170
<v Speaker 2>He sold it.

0:10:38.250 --> 0:10:41.170
<v Speaker 4>And now he's like, I'm going to, I'm going to

0:10:41.210 --> 0:10:43.460
<v Speaker 4>just make a space data center company because that's the

0:10:43.540 --> 0:10:44.540
<v Speaker 4>obvious next move.

0:10:44.940 --> 0:10:48.080
<v Speaker 2>Well, the reason why is because he has a lot

0:10:48.100 --> 0:10:51.069
<v Speaker 2>of connection in manufacturing and in China. So I do

0:10:51.110 --> 0:10:55.030
<v Speaker 2>think that like. building a scooter company ironically kind of

0:10:55.070 --> 0:10:58.550
<v Speaker 2>prepared him to just do some sort of hardware startup generally.

0:10:58.570 --> 0:11:01.429
<v Speaker 4>Yeah, I was being tongue-in-cheek, but actually I think that

0:11:01.530 --> 0:11:03.710
<v Speaker 4>there is a point to be made, which is that

0:11:03.950 --> 0:11:08.050
<v Speaker 4>the whole idea of SpaceX and Blue Origin and these

0:11:08.090 --> 0:11:12.250
<v Speaker 4>companies to get infrastructure up into space is that you

0:11:12.270 --> 0:11:16.230
<v Speaker 4>sort of enable a new crop of entrepreneur to work

0:11:16.309 --> 0:11:20.699
<v Speaker 4>on space-related ideas and companies and So it's like, if

0:11:20.740 --> 0:11:22.819
<v Speaker 4>you think of it as like all this infrastructure as

0:11:22.860 --> 0:11:27.250
<v Speaker 4>a platform, it lets this guy who was a scooter entrepreneur,

0:11:27.640 --> 0:11:29.810
<v Speaker 4>all of a sudden be a space entrepreneur, which never

0:11:29.850 --> 0:11:32.069
<v Speaker 4>would have been possible if you didn't have the, you know,

0:11:32.110 --> 0:11:35.570
<v Speaker 4>SpaceX rockets to get his equipment up into space, right?

0:11:35.630 --> 0:11:38.150
<v Speaker 4>That he was never going to start a rocket company,

0:11:38.610 --> 0:11:40.420
<v Speaker 4>but now he can start a space company. And I

0:11:40.460 --> 0:11:43.640
<v Speaker 4>think that's, I think that's actually kind of a profound point. He,

0:11:43.740 --> 0:11:45.219
<v Speaker 4>I talked to him too. He doesn't even want to

0:11:45.260 --> 0:11:46.679
<v Speaker 4>go to space. I was like, do you want to

0:11:46.700 --> 0:11:48.099
<v Speaker 4>go to, he's like, no, I have no interest in

0:11:48.120 --> 0:11:52.390
<v Speaker 4>going to space. I'm like, that's, I think that's pretty profound.

0:11:52.990 --> 0:11:55.610
<v Speaker 2>I mean, being in space kind of sucks. It's cold

0:11:55.710 --> 0:11:57.830
<v Speaker 2>up there. It's like living in a submarine.

0:11:58.050 --> 0:12:00.449
<v Speaker 3>Until you get the nuclear reactors on the moon.

0:12:00.470 --> 0:12:02.030
<v Speaker 2>Right, right.

0:12:02.070 --> 0:12:04.250
<v Speaker 1>To warm your hands by the warmth of a nuclear

0:12:04.270 --> 0:12:06.250
<v Speaker 1>reactor on the moon. I have to say, there's always

0:12:06.270 --> 0:12:09.390
<v Speaker 1>that classic question, what would you like the first line

0:12:09.410 --> 0:12:11.590
<v Speaker 1>of your obituary to be? And I guess he was

0:12:11.630 --> 0:12:14.110
<v Speaker 1>never going to build rockets is one of them. When

0:12:14.630 --> 0:12:18.930
<v Speaker 1>we come back, who pays when chatbots lead you astray?

0:12:31.490 --> 0:12:31.890
<v Speaker 5>Welcome back.

0:12:32.420 --> 0:12:34.510
<v Speaker 1>Taylor, there was a piece in Futurism this week that

0:12:34.890 --> 0:12:37.429
<v Speaker 1>there's a kind of golden oldie quality to it, a

0:12:37.470 --> 0:12:39.970
<v Speaker 1>kind of tech made me do it story. I remember

0:12:39.990 --> 0:12:43.410
<v Speaker 1>there was that episode of The Office where Michael Scott

0:12:43.710 --> 0:12:46.870
<v Speaker 1>drives his car into the lake on purpose because GPS

0:12:46.929 --> 0:12:51.150
<v Speaker 1>told him to. But nowadays, it's not GPS, but AI

0:12:51.210 --> 0:12:55.460
<v Speaker 1>and cloud in particular that's leading not drivers, but hikers astray.

0:12:56.679 --> 0:12:58.980
<v Speaker 2>Yeah, I actually read about this in the New York Times.

0:12:59.520 --> 0:13:02.510
<v Speaker 2>They did a good story on it. But basically, this

0:13:02.590 --> 0:13:06.229
<v Speaker 2>guy was hiking in British Columbia and he went off

0:13:06.290 --> 0:13:10.570
<v Speaker 2>the trail. He used Claude as part of his planning

0:13:10.610 --> 0:13:13.580
<v Speaker 2>process and ultimately had to be rescued off the side

0:13:13.600 --> 0:13:15.780
<v Speaker 2>of a cliff because he was not a qualified enough

0:13:15.820 --> 0:13:18.400
<v Speaker 2>hiker to, you know, to get himself out of the

0:13:18.440 --> 0:13:21.840
<v Speaker 2>situation he had encountered. used. I don't think this is

0:13:21.900 --> 0:13:26.340
<v Speaker 2>an AI problem necessarily. I actually ended up literally last

0:13:26.380 --> 0:13:28.620
<v Speaker 2>week or two weekends ago when I was back in LA,

0:13:28.640 --> 0:13:30.740
<v Speaker 2>I went to go on a hike and ended up

0:13:31.800 --> 0:13:35.600
<v Speaker 2>in this like burned out section of Altadena where there

0:13:35.640 --> 0:13:39.240
<v Speaker 2>was like no water, the trail was a mess. And

0:13:39.300 --> 0:13:42.400
<v Speaker 2>I had read about it online and And even like

0:13:42.460 --> 0:13:44.880
<v Speaker 2>looked it up, you know, ahead of time. And it's

0:13:44.900 --> 0:13:46.920
<v Speaker 2>just that that route after the fire had changed a

0:13:47.100 --> 0:13:49.830
<v Speaker 2>year ago and all this stuff. Of course, my friends

0:13:49.870 --> 0:13:52.650
<v Speaker 2>were like, why wouldn't you use all trails? I think

0:13:52.790 --> 0:13:55.630
<v Speaker 2>all trails is sort of the standard for this. And

0:13:55.670 --> 0:13:58.689
<v Speaker 2>if you go anywhere else outside the internet, you're sort

0:13:58.730 --> 0:13:59.650
<v Speaker 2>of risking it.

0:14:00.450 --> 0:14:03.189
<v Speaker 1>Kyle, you nodded sagely about all trails. You seem like

0:14:03.250 --> 0:14:04.050
<v Speaker 1>a trail guy.

0:14:04.929 --> 0:14:09.770
<v Speaker 6>I'm not, which is the whole problem. I am not

0:14:09.809 --> 0:14:11.900
<v Speaker 6>a hiking guy. I think I would end up in

0:14:11.940 --> 0:14:14.800
<v Speaker 6>a bad situation. But I think if you have ever

0:14:14.940 --> 0:14:19.160
<v Speaker 6>explored all trails, you know why relying on AI for

0:14:19.180 --> 0:14:23.450
<v Speaker 6>your hiking knowledge is a terrible idea. All trails is

0:14:23.510 --> 0:14:28.810
<v Speaker 6>the most human... intricate detailed set of commentary and data

0:14:28.910 --> 0:14:31.460
<v Speaker 6>that you can possibly have i think in an app

0:14:31.860 --> 0:14:34.900
<v Speaker 6>because it'll be like okay a hundred feet to your

0:14:34.960 --> 0:14:37.720
<v Speaker 6>right like don't take this trail look for the rock

0:14:37.780 --> 0:14:40.479
<v Speaker 6>and go the other way or if you aren't an

0:14:40.540 --> 0:14:44.940
<v Speaker 6>experienced hiker maybe don't even bother uh so like all

0:14:44.960 --> 0:14:48.610
<v Speaker 6>trails i don't know i want a person directly to

0:14:48.670 --> 0:14:51.300
<v Speaker 6>tell me in their own words what I should and

0:14:51.320 --> 0:14:53.060
<v Speaker 6>shouldn't do on one of these hiking trails.

0:14:54.420 --> 0:14:55.800
<v Speaker 2>And a person recently.

0:14:55.820 --> 0:14:57.980
<v Speaker 3>Yeah, yeah, it changes all the time.

0:14:58.460 --> 0:15:00.450
<v Speaker 2>Like the hike that I went on a couple weeks ago,

0:15:00.490 --> 0:15:03.489
<v Speaker 2>like it was rated really, people had blogged this, you know,

0:15:03.510 --> 0:15:08.090
<v Speaker 2>like it was just not up-to-date information. And so, yeah,

0:15:08.150 --> 0:15:11.120
<v Speaker 2>I just think that like, There's a lot of people

0:15:11.170 --> 0:15:14.620
<v Speaker 2>interested in outdoors, but you need to rely on, this

0:15:14.680 --> 0:15:17.040
<v Speaker 2>is like an all trails ad. Like, I think like,

0:15:17.060 --> 0:15:19.890
<v Speaker 2>you know, he could have not used Claude and I

0:15:19.930 --> 0:15:21.750
<v Speaker 2>don't know that he wouldn't have ended up in the

0:15:21.770 --> 0:15:24.420
<v Speaker 2>same situation, especially when you're going off the trail, you know?

0:15:25.110 --> 0:15:27.250
<v Speaker 1>He got rescued, sorry to interrupt, and the rescue manager said,

0:15:27.310 --> 0:15:29.410
<v Speaker 1>Claude has never been in that specific area, has never

0:15:29.430 --> 0:15:31.610
<v Speaker 1>been on that route, and has never been in the outdoors.

0:15:32.700 --> 0:15:36.200
<v Speaker 1>Is this like a sticking rocks to the pizza with

0:15:36.300 --> 0:15:37.380
<v Speaker 1>glue type story?

0:15:37.440 --> 0:15:39.600
<v Speaker 5>Or is it like, what's the, not so much, Taylor?

0:15:39.820 --> 0:15:42.440
<v Speaker 2>Yeah, and that was so silly, too. Like, I mean,

0:15:42.480 --> 0:15:45.140
<v Speaker 2>I guess, like, especially Futurism is a website that, like,

0:15:45.200 --> 0:15:48.260
<v Speaker 2>loves to write up this stuff as, like, it's just

0:15:48.390 --> 0:15:50.870
<v Speaker 2>rage bait content to kind of be like, ha ha,

0:15:50.910 --> 0:15:53.930
<v Speaker 2>you idiot, you know, look at you. And to me,

0:15:53.970 --> 0:15:56.410
<v Speaker 2>it's like, look, it's a real problem with accuracy. I

0:15:56.450 --> 0:16:00.430
<v Speaker 2>think this shows the value actually of these human curated,

0:16:00.510 --> 0:16:02.930
<v Speaker 2>like very human updated apps. Like that's what it shows

0:16:02.980 --> 0:16:05.380
<v Speaker 2>the value of. It's not that AI is inherently unreliable.

0:16:05.440 --> 0:16:08.280
<v Speaker 2>I would say 99.999% of things that you ask AI

0:16:08.320 --> 0:16:10.840
<v Speaker 2>and including that, like Google, you know, Gemini, I guess,

0:16:10.900 --> 0:16:13.440
<v Speaker 2>review that had suggested you put glue on your pizza.

0:16:13.480 --> 0:16:15.700
<v Speaker 2>And that was from a Reddit thread, you know, Early

0:16:15.720 --> 0:16:19.420
<v Speaker 2>iterations of AI were certainly less reliable. They're getting smarter

0:16:19.440 --> 0:16:22.540
<v Speaker 2>and smarter. Again, it just has to do with the

0:16:22.590 --> 0:16:24.880
<v Speaker 2>fact that when you're going out into the physical world,

0:16:25.020 --> 0:16:29.390
<v Speaker 2>hiking specifically, until we get drones, you know, going out

0:16:29.470 --> 0:16:33.090
<v Speaker 2>and scouting these trails for us, I think, like, something

0:16:33.110 --> 0:16:34.630
<v Speaker 2>like all trails is just the way to go.

0:16:34.650 --> 0:16:36.550
<v Speaker 3>Or the humanoid robots.

0:16:37.030 --> 0:16:41.030
<v Speaker 2>Right, we send the humanoid robots out to go chart

0:16:41.070 --> 0:16:41.510
<v Speaker 2>the trails.

0:16:41.750 --> 0:16:44.430
<v Speaker 6>But it was striking to me, like, Hiking is a

0:16:44.510 --> 0:16:50.330
<v Speaker 6>subjective thing. Difficulty is subjective. How much your body can

0:16:50.370 --> 0:16:54.050
<v Speaker 6>take is subjective. AI, if you're not an experienced hiker,

0:16:54.150 --> 0:16:55.830
<v Speaker 6>AI is not going to be able to tell you

0:16:56.130 --> 0:16:59.200
<v Speaker 6>what you can handle in this situation. So maybe in

0:16:59.240 --> 0:17:02.740
<v Speaker 6>this case, don't ask Claude, ask your friends.

0:17:03.480 --> 0:17:05.520
<v Speaker 4>In my experience, I don't know if you guys go

0:17:05.560 --> 0:17:09.119
<v Speaker 4>backpacking and stuff, but if something really bad doesn't happen

0:17:09.160 --> 0:17:11.220
<v Speaker 4>where you think you might die, it's kind of a

0:17:11.280 --> 0:17:13.720
<v Speaker 4>boring trip. Those are the things that you always remember,

0:17:13.960 --> 0:17:14.240
<v Speaker 4>you know?

0:17:14.260 --> 0:17:15.080
<v Speaker 3>I think.

0:17:15.119 --> 0:17:16.939
<v Speaker 2>Okay, I am not trying to go on the hikes

0:17:16.960 --> 0:17:20.800
<v Speaker 2>that Reid is going on. I love hiking a leisurely

0:17:21.140 --> 0:17:24.119
<v Speaker 2>trail in the woods. I think also, you know, this

0:17:24.160 --> 0:17:26.280
<v Speaker 2>is a teenager. I think he was 16 years old.

0:17:26.800 --> 0:17:30.040
<v Speaker 2>So I think there's also just teenagers don't traditionally have

0:17:30.080 --> 0:17:34.399
<v Speaker 2>a great track record of judging risk and... Potential for

0:17:34.440 --> 0:17:35.100
<v Speaker 2>bodily harm.

0:17:35.119 --> 0:17:37.400
<v Speaker 4>Yeah, people have always been doing dumb stuff.

0:17:37.840 --> 0:17:41.179
<v Speaker 1>There is something in the automation bias, like AI psychosis

0:17:41.240 --> 0:17:45.830
<v Speaker 1>adjacent thing here. I got my green fingers burnt earlier

0:17:45.869 --> 0:17:48.090
<v Speaker 1>this year when I really went to town on pruning

0:17:48.130 --> 0:17:50.609
<v Speaker 1>my roses with the encouragement of Gemini. And actually, I

0:17:50.630 --> 0:17:52.129
<v Speaker 1>think I ended up killing them and I had to

0:17:52.170 --> 0:17:55.169
<v Speaker 1>confess to the landlord. So I feel like you can

0:17:55.210 --> 0:17:58.129
<v Speaker 1>lean in too hard to the reassuring advice.

0:17:57.869 --> 0:17:58.610
<v Speaker 5>Of AI, certainly.

0:17:59.490 --> 0:18:01.649
<v Speaker 1>The story that kind of sits behind this story, for me, though,

0:18:01.670 --> 0:18:06.879
<v Speaker 1>is the kind of AI... responsibility and liability story. Taylor,

0:18:06.920 --> 0:18:08.520
<v Speaker 1>I think this has been also in the news this

0:18:08.560 --> 0:18:13.380
<v Speaker 1>week in terms of how insurance payments work out when

0:18:13.560 --> 0:18:17.740
<v Speaker 1>AI does harm and who's held liable, like AI hugging

0:18:17.880 --> 0:18:20.780
<v Speaker 1>face episode, for example, like in that case, hugging face

0:18:20.800 --> 0:18:23.220
<v Speaker 1>didn't sue OpenAI, but if they had, who would have

0:18:23.240 --> 0:18:24.600
<v Speaker 1>had the liability in that situation?

0:18:25.160 --> 0:18:29.399
<v Speaker 2>Well, it's a company hacking another company. So the company

0:18:29.440 --> 0:18:32.600
<v Speaker 2>has a liability. It intentionally hacked the other company.

0:18:33.450 --> 0:18:36.419
<v Speaker 4>Yeah, exactly. I think the question though, there is an,

0:18:37.030 --> 0:18:39.170
<v Speaker 4>I think there is a really interesting legal question that's

0:18:39.190 --> 0:18:41.600
<v Speaker 4>going to have to be answered, which is like, let's

0:18:41.640 --> 0:18:44.899
<v Speaker 4>say you're not open AI and there's got to be

0:18:44.920 --> 0:18:48.720
<v Speaker 4>some cases where you could end up accidentally doing harm, right?

0:18:48.740 --> 0:18:50.959
<v Speaker 2>And then I think- Here's the question, I think, or

0:18:50.980 --> 0:18:52.860
<v Speaker 2>not to interrupt, but just to finish, or I think

0:18:52.880 --> 0:18:54.340
<v Speaker 2>this was like the second part maybe that you wanted

0:18:54.359 --> 0:18:56.379
<v Speaker 2>to get at, but like, here's the question that I

0:18:56.400 --> 0:18:58.300
<v Speaker 2>think we're going to have to answer is when we

0:18:58.340 --> 0:19:00.900
<v Speaker 2>move into this more agentic era of the internet, who

0:19:00.980 --> 0:19:04.580
<v Speaker 2>is responsible for the agent's actions? And with OpenAI, it

0:19:04.630 --> 0:19:06.619
<v Speaker 2>is literally their model. Of course, they're responsible. This is

0:19:06.680 --> 0:19:09.560
<v Speaker 2>a test that they were doing. But if I use Grokbot,

0:19:09.600 --> 0:19:12.709
<v Speaker 2>for instance, to go out into the world and do

0:19:12.730 --> 0:19:14.929
<v Speaker 2>a lot of things for me, automate my lifestyle, and

0:19:14.970 --> 0:19:18.470
<v Speaker 2>I end up causing harm to someone or... I lose,

0:19:18.490 --> 0:19:20.970
<v Speaker 2>you know, banks are super, super concerned about this. I

0:19:20.990 --> 0:19:23.300
<v Speaker 2>was talking to somebody in the banking industry yesterday about it,

0:19:24.390 --> 0:19:27.460
<v Speaker 2>because if my grok bot goes out and spends lots

0:19:27.500 --> 0:19:29.740
<v Speaker 2>of money, I am probably going to be inclined to

0:19:29.780 --> 0:19:32.340
<v Speaker 2>declare that as fraud. And, you know, the bank will

0:19:32.359 --> 0:19:34.659
<v Speaker 2>suddenly be held liable and banks are lobbying right now

0:19:34.680 --> 0:19:37.270
<v Speaker 2>to say, hey, hey, hey, no, no, no, no. It's

0:19:37.350 --> 0:19:40.830
<v Speaker 2>grok that's liable. So there's all these questions around agents.

0:19:40.930 --> 0:19:42.710
<v Speaker 2>And I do think that there's a much more compelling

0:19:42.750 --> 0:19:46.960
<v Speaker 2>case for liability for companies that are building agents to

0:19:46.980 --> 0:19:50.040
<v Speaker 2>be liable for their agents. I think it just is

0:19:50.080 --> 0:19:52.100
<v Speaker 2>a question too of how are you using that agent?

0:19:52.160 --> 0:19:54.600
<v Speaker 2>Did you jailbreak the agent? Are you using it within

0:19:54.800 --> 0:19:57.359
<v Speaker 2>terms of use? And I just think those are battles

0:19:57.400 --> 0:19:58.060
<v Speaker 2>that we're going to see.

0:19:58.280 --> 0:20:00.560
<v Speaker 4>Or what if we use open source, right? I think

0:20:00.600 --> 0:20:02.219
<v Speaker 4>that's going to be another one where it's like, well,

0:20:02.260 --> 0:20:04.900
<v Speaker 4>what if I'm using open source agents or open weight models?

0:20:04.920 --> 0:20:06.000
<v Speaker 2>Then you're liable, right?

0:20:06.420 --> 0:20:08.540
<v Speaker 4>But what if it's, let's say you get sued for

0:20:08.580 --> 0:20:11.770
<v Speaker 4>something you did, And now there's the discovery process and

0:20:11.810 --> 0:20:13.610
<v Speaker 4>you see all your prompts and your prompts show that

0:20:13.670 --> 0:20:17.120
<v Speaker 4>you were acting in good faith and you reasonably thought that,

0:20:17.580 --> 0:20:18.159
<v Speaker 4>you know, there was not.

0:20:18.180 --> 0:20:21.429
<v Speaker 2>Well, you can unintentionally do harm to somebody else. And

0:20:21.450 --> 0:20:24.560
<v Speaker 2>that's taken into account in terms of the legal fight.

0:20:25.000 --> 0:20:29.040
<v Speaker 2>But if I build software that's my personal boutique software

0:20:29.060 --> 0:20:34.270
<v Speaker 2>that I'm using and I use it to do something,

0:20:34.790 --> 0:20:37.310
<v Speaker 2>maybe it was unintentional harm. And again, that can be

0:20:37.350 --> 0:20:40.050
<v Speaker 2>taken into consideration. But I built that software and I'm

0:20:40.150 --> 0:20:42.090
<v Speaker 2>using it for the purposes that I built it for.

0:20:42.560 --> 0:20:42.800
<v Speaker 5>Right.

0:20:42.840 --> 0:20:44.480
<v Speaker 4>But I think there, you know, you could see a

0:20:44.500 --> 0:20:48.100
<v Speaker 4>world where, you know, maybe regulators want to hold whoever

0:20:48.140 --> 0:20:50.040
<v Speaker 4>made the open weight models liable.

0:20:50.320 --> 0:20:53.520
<v Speaker 2>That would be disastrous and deranged. I mean, hope that

0:20:53.540 --> 0:20:55.680
<v Speaker 2>would be. And that is what I and you're right.

0:20:55.840 --> 0:20:57.460
<v Speaker 2>People try to do that. I mean, this is the

0:20:57.510 --> 0:20:59.770
<v Speaker 2>argument that they're trying to make against speech on content

0:20:59.810 --> 0:21:03.630
<v Speaker 2>platforms as well. Right. Like, you know, or Chachi BT

0:21:03.670 --> 0:21:06.810
<v Speaker 2>is responsible because somebody looked up how busy the student

0:21:06.830 --> 0:21:09.530
<v Speaker 2>center was before doing a shooting. Therefore, Chachi BT is

0:21:09.590 --> 0:21:10.530
<v Speaker 2>responsible for the shooting.

0:21:10.550 --> 0:21:10.649
<v Speaker 4>Right.

0:21:11.010 --> 0:21:15.270
<v Speaker 2>That sort of liability is incredibly dangerous. And we should

0:21:15.310 --> 0:21:17.930
<v Speaker 2>not seek to build that system because then people won't

0:21:17.950 --> 0:21:20.820
<v Speaker 2>have open access to information. They won't have open access

0:21:20.859 --> 0:21:23.139
<v Speaker 2>to technology. They won't be able to build software. Then

0:21:23.160 --> 0:21:26.940
<v Speaker 2>we're putting in speech restrictions. Because building software, of course,

0:21:27.000 --> 0:21:30.160
<v Speaker 2>coding is speech. And if we start to restrict that speech,

0:21:30.960 --> 0:21:33.070
<v Speaker 2>it goes down a dark road. But I think 99%

0:21:33.070 --> 0:21:35.030
<v Speaker 2>of people are not going to build software. I think

0:21:35.050 --> 0:21:37.590
<v Speaker 2>what will happen, I was talking to Schumer's chief of

0:21:37.650 --> 0:21:42.000
<v Speaker 2>staff actually this week who has this AI agent act

0:21:42.020 --> 0:21:44.570
<v Speaker 2>that I don't think is very good. But, you know,

0:21:44.609 --> 0:21:46.910
<v Speaker 2>she was saying, like, there'll probably eventually be something like

0:21:46.930 --> 0:21:49.330
<v Speaker 2>an app store where it's like, you know what, could

0:21:49.369 --> 0:21:51.670
<v Speaker 2>you go off and do this yourself? Yes, you're taking

0:21:51.690 --> 0:21:54.080
<v Speaker 2>a huge risk. But here's a bunch of trusted apps.

0:21:54.540 --> 0:21:56.480
<v Speaker 2>And I think there's going to be market competition, right,

0:21:56.520 --> 0:21:58.580
<v Speaker 2>for these sort of trusted agent technologies.

0:21:59.180 --> 0:22:02.100
<v Speaker 1>What kind of policies, though, are like OpenAI and Grok

0:22:02.140 --> 0:22:04.400
<v Speaker 1>and Anthropic taking out or trying to get new forms

0:22:04.440 --> 0:22:07.420
<v Speaker 1>of coverage against, like, because for sure the lawsuits are coming, right,

0:22:07.440 --> 0:22:11.180
<v Speaker 1>when people experience harm based on something that a bot

0:22:11.220 --> 0:22:12.379
<v Speaker 1>has either done or recommended.

0:22:12.400 --> 0:22:16.970
<v Speaker 4>I don't know. I actually think I've probably committed crimes

0:22:17.010 --> 0:22:21.890
<v Speaker 4>with ChatGBT, like, inadvertently already. Like, I think it's probably happened. Because, like,

0:22:22.210 --> 0:22:24.449
<v Speaker 4>these laws are so strict on what you can do

0:22:24.490 --> 0:22:27.870
<v Speaker 4>with software. Like just like the Digital Millennium Copyright Act.

0:22:27.880 --> 0:22:31.070
<v Speaker 4>Like you can break the law like so easily. I know.

0:22:31.290 --> 0:22:31.570
<v Speaker 4>I mean.

0:22:31.590 --> 0:22:33.890
<v Speaker 2>Which is, but this is why we need to obliterate

0:22:33.930 --> 0:22:34.810
<v Speaker 2>copyright law.

0:22:36.830 --> 0:22:37.609
<v Speaker 3>We're getting far.

0:22:37.630 --> 0:22:41.960
<v Speaker 6>But it feels like as we use more and more

0:22:42.000 --> 0:22:44.859
<v Speaker 6>personal agents, it's like there's going to be more and

0:22:44.880 --> 0:22:45.699
<v Speaker 6>more mishaps.

0:22:46.600 --> 0:22:49.120
<v Speaker 3>More and more like debates over the responsibilities.

0:22:49.480 --> 0:22:52.720
<v Speaker 1>Actually, the copyright law is a perfect segue to Kyle

0:22:52.800 --> 0:22:53.880
<v Speaker 1>after the break for his story.

0:22:53.920 --> 0:22:55.119
<v Speaker 5>But before we go there, Kyle.

0:22:55.160 --> 0:22:57.420
<v Speaker 1>I mean, you missed, while you were on paternity leave,

0:22:58.160 --> 0:23:02.869
<v Speaker 1>a week-by-week, play-by-play coverage of the Hugging Face open AI

0:23:02.930 --> 0:23:05.290
<v Speaker 1>hack and the AI extinction, all this for the last

0:23:05.310 --> 0:23:08.010
<v Speaker 1>three months. So having not been talking about it with

0:23:08.070 --> 0:23:10.830
<v Speaker 1>us every single week, what's... What's your kind of overall

0:23:10.850 --> 0:23:13.170
<v Speaker 1>take on, on what's happened in this question about who's

0:23:13.210 --> 0:23:15.390
<v Speaker 1>responsible when AI stuff goes wrong?

0:23:15.410 --> 0:23:16.969
<v Speaker 5>Like where is the culture on that question?

0:23:16.990 --> 0:23:22.119
<v Speaker 3>Yeah, I'm like Rip Van Winkle. I just woke up.

0:23:22.340 --> 0:23:25.419
<v Speaker 6>The world has changed vastly in the time that I've

0:23:25.440 --> 0:23:28.980
<v Speaker 6>been asleep. Um, yeah, I mean, I'm, I'm catching up

0:23:29.020 --> 0:23:31.300
<v Speaker 6>a little bit on the nuts and bolts of it. Uh,

0:23:31.760 --> 0:23:34.560
<v Speaker 6>but I think it matters who, who sets the agent

0:23:34.640 --> 0:23:37.620
<v Speaker 6>on this task. Like who is, who is the user?

0:23:37.740 --> 0:23:38.720
<v Speaker 3>Who is the actor?

0:23:39.310 --> 0:23:42.650
<v Speaker 6>Behind a given operation and for open ai like they

0:23:42.690 --> 0:23:46.210
<v Speaker 6>clearly set the the agents on this task that eventually

0:23:46.230 --> 0:23:49.159
<v Speaker 6>went off the rails but that's like their responsibility i

0:23:49.690 --> 0:23:51.940
<v Speaker 6>think it becomes harder when you have more and more

0:23:52.200 --> 0:23:55.340
<v Speaker 6>different kinds of agents more and more systems more open

0:23:55.380 --> 0:23:58.800
<v Speaker 6>models more things that kind of come from nowhere and

0:23:58.880 --> 0:24:01.960
<v Speaker 6>aren't as trackable um and i kind of feel like

0:24:02.020 --> 0:24:05.020
<v Speaker 6>those things must be happening right now already and we

0:24:05.040 --> 0:24:08.260
<v Speaker 6>just haven't heard about it and don't quite know yet

0:24:08.280 --> 0:24:11.950
<v Speaker 6>uh As more and more things go wrong, I feel

0:24:12.020 --> 0:24:15.280
<v Speaker 6>like we're going to be taken by surprise.

0:24:16.000 --> 0:24:17.659
<v Speaker 1>When we come back, Kyle, you have a hunch that

0:24:17.680 --> 0:24:20.639
<v Speaker 1>maybe we won't need software subscriptions all that much longer.

0:24:21.060 --> 0:24:21.820
<v Speaker 3>We can only hope.

0:24:22.640 --> 0:24:32.300
<v Speaker 5>Stay with us. Welcome back, Kyle.

0:24:32.520 --> 0:24:35.220
<v Speaker 1>I understand you've been following a trend in software where

0:24:35.740 --> 0:24:38.720
<v Speaker 1>AI is changing all the rules. Tell us exactly what

0:24:38.980 --> 0:24:41.320
<v Speaker 1>Photon Studios is and why you're interested in it.

0:24:41.680 --> 0:24:44.629
<v Speaker 6>Yeah, I mean, I think this was coming up increasingly

0:24:44.710 --> 0:24:48.330
<v Speaker 6>often on X. X is a great way to just

0:24:48.369 --> 0:24:51.530
<v Speaker 6>follow what people in AI are talking about and sharing

0:24:51.570 --> 0:24:55.030
<v Speaker 6>and posting as brags on a week-by-week basis. And I

0:24:55.070 --> 0:24:57.710
<v Speaker 6>feel like, at least in my zone this week, was

0:24:57.770 --> 0:25:02.619
<v Speaker 6>about decompilation, which is this word that was new to me, actually, of.

0:25:04.119 --> 0:25:07.489
<v Speaker 6>Taking a given product, like whether it's a Photoshop or

0:25:07.530 --> 0:25:11.310
<v Speaker 6>a video game, drawing it back to the source code

0:25:11.590 --> 0:25:15.070
<v Speaker 6>and then recompiling that source code as something else with

0:25:15.109 --> 0:25:17.710
<v Speaker 6>the help of AI. So you're essentially creating like a

0:25:18.170 --> 0:25:23.020
<v Speaker 6>totally open sourced, remixable, hackable version of any kind of

0:25:23.080 --> 0:25:25.639
<v Speaker 6>software or video game or a piece of code.

0:25:25.800 --> 0:25:27.260
<v Speaker 5>But what does that mean and how does it work?

0:25:28.580 --> 0:25:32.600
<v Speaker 6>Well, it means that you're like, taking the code, translating

0:25:32.660 --> 0:25:35.040
<v Speaker 6>it back to its basic form, and then retranslating it

0:25:35.119 --> 0:25:36.199
<v Speaker 6>into a different form.

0:25:36.640 --> 0:25:38.240
<v Speaker 5>Is this the same as distilling?

0:25:39.640 --> 0:25:42.800
<v Speaker 6>Not in terms of model stuff, not in any way.

0:25:42.840 --> 0:25:47.240
<v Speaker 6>This is a much more basic thing. We're just getting

0:25:47.280 --> 0:25:49.820
<v Speaker 6>the source code of something that's been programmed, like a

0:25:49.840 --> 0:25:54.970
<v Speaker 6>video game, and we're basically releasing it to the world.

0:25:55.350 --> 0:25:58.449
<v Speaker 6>We're taking all those component parts, and we're putting them

0:25:58.490 --> 0:26:00.930
<v Speaker 6>back out into the world in a form that anyone

0:26:01.010 --> 0:26:04.629
<v Speaker 6>can kind of tinker with and reuse. So in the

0:26:04.670 --> 0:26:09.510
<v Speaker 6>case of Photon Studios, I think, they did that to Photoshop.

0:26:10.050 --> 0:26:13.969
<v Speaker 6>So they took the whole Adobe Photoshop architecture, the whole interface,

0:26:14.030 --> 0:26:20.179
<v Speaker 6>the whole suite of tools, decompiled it using AI, and

0:26:20.220 --> 0:26:22.780
<v Speaker 6>then put it back online just as a browser tool.

0:26:23.040 --> 0:26:25.520
<v Speaker 6>So you can now go in your browser and open

0:26:25.540 --> 0:26:30.710
<v Speaker 6>Photoshop exactly the same experience there's no subscription there's no

0:26:30.770 --> 0:26:33.270
<v Speaker 6>signing up there's no anything it's just like here you

0:26:33.290 --> 0:26:36.510
<v Speaker 6>go and that was kind of a mind-blowing experience to

0:26:36.550 --> 0:26:38.830
<v Speaker 6>me as someone who had to like you know get

0:26:38.880 --> 0:26:43.600
<v Speaker 6>the hacked software keys from kazaa or whatever when i

0:26:43.640 --> 0:26:46.880
<v Speaker 6>was 12 years old we're all going to prison right

0:26:46.920 --> 0:26:50.180
<v Speaker 6>this is this is kind of agents helping you break

0:26:50.220 --> 0:26:51.910
<v Speaker 6>the law a little bit uh.

0:26:52.450 --> 0:26:54.590
<v Speaker 4>I went down this rabbit hole too this week, Kyle.

0:26:54.770 --> 0:26:58.540
<v Speaker 4>I'm writing something for the newsletter tomorrow actually about this,

0:26:58.619 --> 0:27:01.580
<v Speaker 4>but the decompilation thing, which I hadn't really heard of,

0:27:02.359 --> 0:27:05.100
<v Speaker 4>and then I heard about it because of the video

0:27:05.119 --> 0:27:09.179
<v Speaker 4>game mashups. Have you seen these? Where people combine different games?

0:27:09.480 --> 0:27:14.369
<v Speaker 6>Decompiling video games and then recompiling them, but in mashup versions.

0:27:14.890 --> 0:27:18.730
<v Speaker 6>So I think not putting Mario in Elden Ring or

0:27:18.869 --> 0:27:23.159
<v Speaker 6>Minecraft in Red Dead Redemption... And it looks perfect. You

0:27:23.180 --> 0:27:26.570
<v Speaker 6>see these clips and it's like, literally, it's just Mario

0:27:26.850 --> 0:27:28.330
<v Speaker 6>in the Old West or whatever.

0:27:28.350 --> 0:27:32.610
<v Speaker 4>I'm not a gamer, but the comments were so eye-opening

0:27:32.850 --> 0:27:35.430
<v Speaker 4>to me because gamers were just losing their minds about

0:27:35.450 --> 0:27:39.580
<v Speaker 4>this capability and loving it. I saw these crazy comments like,

0:27:40.119 --> 0:27:43.330
<v Speaker 4>oh my god, everybody hates AI, but this is finally

0:27:43.369 --> 0:27:46.430
<v Speaker 4>the thing that makes me love AI. This is incredible.

0:27:47.710 --> 0:27:51.450
<v Speaker 6>Finally, I can be Mario in Call of Duty. Cool,

0:27:51.470 --> 0:27:53.560
<v Speaker 6>that's your dream come true.

0:27:53.730 --> 0:27:57.200
<v Speaker 4>One guy was like, this is like AI curing cancer

0:27:57.260 --> 0:27:57.960
<v Speaker 4>for gamers.

0:28:00.040 --> 0:28:02.740
<v Speaker 3>It's kind of sad in a way. It's a small.

0:28:03.640 --> 0:28:06.479
<v Speaker 6>thing to accomplish in a way the photoshop thing was

0:28:06.520 --> 0:28:09.389
<v Speaker 6>more impressive to me because it was like it demonstrated

0:28:09.450 --> 0:28:12.930
<v Speaker 6>how all software could become open source and how there

0:28:12.950 --> 0:28:18.570
<v Speaker 6>was no defense against a decent amateur programmer decompiling and

0:28:18.609 --> 0:28:21.970
<v Speaker 6>recompiling your corporate software products.

0:28:21.850 --> 0:28:24.850
<v Speaker 1>I mean that's that's like the saspocalypse on steroids right

0:28:24.910 --> 0:28:27.190
<v Speaker 1>like you don't have to vibe code an alternative you

0:28:27.210 --> 0:28:29.139
<v Speaker 1>can just literally copy the underlying.

0:28:28.760 --> 0:28:31.520
<v Speaker 4>Thing but i i saw people also commenting on that

0:28:31.660 --> 0:28:34.560
<v Speaker 4>photoshop thing saying that like oh it doesn't work as

0:28:34.619 --> 0:28:36.979
<v Speaker 4>well like it uses up too much memory you know

0:28:37.020 --> 0:28:40.350
<v Speaker 4>that kind of stuff so i don't know have you actually.

0:28:40.090 --> 0:28:43.070
<v Speaker 6>Tried it right yeah i was trying the web version

0:28:43.150 --> 0:28:46.710
<v Speaker 6>and For me, who's just messing around in layers and

0:28:46.770 --> 0:28:50.270
<v Speaker 6>doing type stuff, it's absolutely fine.

0:28:51.170 --> 0:28:53.880
<v Speaker 3>And it's great. It's the kind of thing that I would.

0:28:53.880 --> 0:28:56.440
<v Speaker 6>Use on a week-to-week basis and get rid of my

0:28:56.480 --> 0:29:01.240
<v Speaker 6>Photoshop subscription. So that took me aback. But there are moats, right?

0:29:02.200 --> 0:29:05.969
<v Speaker 6>Nintendo is already doing copyright violations to take down clips

0:29:06.070 --> 0:29:10.010
<v Speaker 6>of Mario and Elden Ring, and Adobe will have defenses

0:29:10.070 --> 0:29:14.730
<v Speaker 6>against this. Including that, like, the AI versions don't replicate

0:29:15.450 --> 0:29:17.780
<v Speaker 6>all of their features and all of their, like, connectivity.

0:29:17.800 --> 0:29:20.740
<v Speaker 4>They're going to have to stop Anthropic from allowing it, right? Because, like,

0:29:20.780 --> 0:29:23.320
<v Speaker 4>otherwise everybody, you don't need to download it, right? You

0:29:23.340 --> 0:29:25.640
<v Speaker 4>could just do it at home with your, you know,

0:29:25.680 --> 0:29:26.700
<v Speaker 4>with Claude, right?

0:29:26.720 --> 0:29:28.300
<v Speaker 5>But that's not, I mean, that's not a moat.

0:29:28.360 --> 0:29:31.400
<v Speaker 1>That's more of a, like, legal recourse after the horse

0:29:31.420 --> 0:29:32.510
<v Speaker 1>has bolted the stable, no?

0:29:32.570 --> 0:29:32.730
<v Speaker 4>I mean.

0:29:32.750 --> 0:29:36.550
<v Speaker 6>Yeah, and can you just tell them, oh, please code

0:29:36.590 --> 0:29:38.710
<v Speaker 6>something that's, like, Photoshop for me?

0:29:39.070 --> 0:29:39.870
<v Speaker 3>Like, probably.

0:29:39.890 --> 0:29:43.560
<v Speaker 2>Yeah. yeah yeah and that's kind of the beauty i

0:29:43.600 --> 0:29:47.310
<v Speaker 2>feel like of allowing more people to build software which

0:29:47.410 --> 0:29:49.690
<v Speaker 2>is and i think that what's scary is like all

0:29:49.710 --> 0:29:51.330
<v Speaker 2>of these people that want to restrict that.

0:29:51.230 --> 0:29:56.530
<v Speaker 4>Process Did you ever play this game called Goldeneye, the

0:29:56.630 --> 0:29:57.550
<v Speaker 4>James Bond game?

0:29:57.830 --> 0:30:00.150
<v Speaker 1>Yeah, I was thinking about that game with the nuclear

0:30:00.170 --> 0:30:02.330
<v Speaker 1>reactors on space. I feel like that would have been

0:30:02.730 --> 0:30:05.340
<v Speaker 1>a perfect episode of Goldeneye, the game.

0:30:05.820 --> 0:30:10.420
<v Speaker 4>Somebody decompiled Goldeneye before the AI age and they just finished.

0:30:10.540 --> 0:30:12.580
<v Speaker 4>And I was reading about this in my rabbit hole

0:30:12.620 --> 0:30:15.100
<v Speaker 4>this week and it took them like 10 years to

0:30:15.140 --> 0:30:17.700
<v Speaker 4>decompile it. And I was like, I feel bad for

0:30:17.740 --> 0:30:19.920
<v Speaker 4>those people because now they can just ask Claude to

0:30:19.980 --> 0:30:20.240
<v Speaker 4>do it.

0:30:20.690 --> 0:30:24.230
<v Speaker 6>Yeah, now it takes weeks. Like, I saw some charts,

0:30:24.350 --> 0:30:27.370
<v Speaker 6>and it's like, oh, Super Smash Bros. took a decade,

0:30:27.890 --> 0:30:30.420
<v Speaker 6>and now you can do it in three weeks. So

0:30:30.440 --> 0:30:34.920
<v Speaker 6>it's like a really striking acceleration. Though, on Reed's note,

0:30:35.240 --> 0:30:39.660
<v Speaker 6>there is this really interesting backlash from the handsy compilers,

0:30:39.860 --> 0:30:43.140
<v Speaker 6>where they're like, no, we love doing this artisanal craft

0:30:43.220 --> 0:30:46.850
<v Speaker 6>by hand and taking years to... replicate our favorite video

0:30:46.890 --> 0:30:52.090
<v Speaker 6>games and now these shallow vibe coded decompiling versions are

0:30:52.130 --> 0:30:55.209
<v Speaker 6>just cheap imitations it's like i don't know i think

0:30:55.230 --> 0:30:55.810
<v Speaker 6>they're pretty.

0:30:55.650 --> 0:30:59.110
<v Speaker 4>Good no the hand decompiler people that will be like

0:30:59.170 --> 0:31:01.390
<v Speaker 4>a job in the ai future where it's like oh

0:31:01.410 --> 0:31:04.590
<v Speaker 4>dude i got a hand decompiled copy of this game

0:31:04.630 --> 0:31:06.710
<v Speaker 4>it's so good it's so much better.

0:31:06.490 --> 0:31:10.950
<v Speaker 5>Who What's the business implication of this?

0:31:10.990 --> 0:31:14.510
<v Speaker 1>Is it a huge, huge ongoing risk for companies like

0:31:14.570 --> 0:31:16.950
<v Speaker 1>Adobe who have new proprietary software?

0:31:17.250 --> 0:31:20.910
<v Speaker 2>No, I think it's about differentiating your product, but I

0:31:20.950 --> 0:31:22.709
<v Speaker 2>do think that they can't lock you. And I do

0:31:22.750 --> 0:31:24.550
<v Speaker 2>think in this world where everybody can build kind of

0:31:24.610 --> 0:31:28.910
<v Speaker 2>basic level software, you really need to provide serious value

0:31:28.970 --> 0:31:31.810
<v Speaker 2>to consumers. I think this is ultimately good for consumers.

0:31:31.850 --> 0:31:34.740
<v Speaker 2>I think it just depends on how, again, we regulate it.

0:31:34.830 --> 0:31:39.130
<v Speaker 2>And if we start doing these crazy restrictions on the

0:31:39.170 --> 0:31:41.510
<v Speaker 2>ability to build software, that's going to be a problem.

0:31:41.530 --> 0:31:44.410
<v Speaker 2>But I think like, look, you can build a cheap

0:31:44.530 --> 0:31:47.100
<v Speaker 2>copy of Adobe Photoshop. It's not going to work as well.

0:31:47.120 --> 0:31:49.500
<v Speaker 2>You're not going to get access to all these community,

0:31:49.840 --> 0:31:52.040
<v Speaker 2>you know, features and events and things like that. And

0:31:52.140 --> 0:31:55.110
<v Speaker 2>I just, I think that's kind of going to differentiate

0:31:55.140 --> 0:31:56.370
<v Speaker 2>the big winners.

0:31:56.910 --> 0:31:59.370
<v Speaker 4>I agree. I think this is like a really exciting time.

0:31:59.450 --> 0:32:02.010
<v Speaker 4>And obviously, like, I don't want copyright to be, I

0:32:02.410 --> 0:32:05.550
<v Speaker 4>want copyright law to still exist, but it would be

0:32:05.590 --> 0:32:09.910
<v Speaker 4>really sad if the AI era just gets like smushed

0:32:09.990 --> 0:32:13.010
<v Speaker 4>into the walled garden thing all over again. I think

0:32:13.050 --> 0:32:13.930
<v Speaker 4>that would be a sad result.

0:32:16.910 --> 0:32:18.950
<v Speaker 1>Of doing it illegal? And is it in the eye

0:32:18.970 --> 0:32:21.150
<v Speaker 1>of the beholder? Could there be a debate? Was this

0:32:21.170 --> 0:32:25.560
<v Speaker 1>decompiled or was this actually created from scratch using generative AI?

0:32:25.600 --> 0:32:27.760
<v Speaker 6>That's a good question. I mean, I don't think decompiling

0:32:27.800 --> 0:32:31.440
<v Speaker 6>itself is illegal. I think what they're already fighting back

0:32:31.480 --> 0:32:36.380
<v Speaker 6>against is uploading it online. So the Nintendo clips, they

0:32:36.420 --> 0:32:40.690
<v Speaker 6>fight back against that really fast. Photoshop, I feel like

0:32:40.730 --> 0:32:43.410
<v Speaker 6>it's only a matter of time. I just Gemini-ed it.

0:32:43.430 --> 0:32:46.950
<v Speaker 4>It says that it's not automatically illegal under the DMCA

0:32:47.390 --> 0:32:49.590
<v Speaker 4>or US copyright law, as long as it's done for

0:32:49.650 --> 0:32:54.670
<v Speaker 4>lawful purposes, such as achieving interoperability. So it sounds like

0:32:54.710 --> 0:32:55.190
<v Speaker 4>it's illegal.

0:32:57.030 --> 0:32:58.410
<v Speaker 5>Have any of you actually tried to do it?

0:32:58.410 --> 0:32:59.730
<v Speaker 4>No. No.

0:33:00.030 --> 0:33:02.110
<v Speaker 6>I'll have to think of something good. Like I was

0:33:02.130 --> 0:33:04.830
<v Speaker 6>reading the blog post of someone who decompiled a really

0:33:04.950 --> 0:33:07.770
<v Speaker 6>old Game Boy Advance game that they were obsessed with

0:33:08.050 --> 0:33:12.330
<v Speaker 6>called Cronoa or something. And Claude discovered some Easter egg

0:33:12.370 --> 0:33:16.030
<v Speaker 6>that no one had found before in the source code.

0:33:16.650 --> 0:33:19.730
<v Speaker 6>That seems so fun and interesting to be able to

0:33:19.850 --> 0:33:21.870
<v Speaker 6>go through that process so quickly and kind of break

0:33:21.910 --> 0:33:25.970
<v Speaker 6>down old pieces of software. But in a video game,

0:33:26.050 --> 0:33:31.350
<v Speaker 6>this is entertainment. It's culture. It's not as threatening to

0:33:31.390 --> 0:33:36.890
<v Speaker 6>a business model as remaking Photoshop instantly or remaking Riverside.com

0:33:37.950 --> 0:33:38.930
<v Speaker 6>into a better version.

0:33:42.580 --> 0:33:44.520
<v Speaker 5>Well, that's all we have time for today. Thanks to

0:33:44.540 --> 0:33:45.520
<v Speaker 5>our partners at Riverside.

0:33:45.540 --> 0:33:49.450
<v Speaker 1>Thank you for joining us.

0:33:49.460 --> 0:33:49.940
<v Speaker 3>Just kidding.

0:33:50.430 --> 0:33:50.750
<v Speaker 4>All right.

0:33:50.910 --> 0:33:51.410
<v Speaker 3>Great to be here.

0:33:51.430 --> 0:33:52.150
<v Speaker 2>Thanks for having us.

0:33:55.050 --> 0:33:58.170
<v Speaker 1>For Tech Stuff, I'm Oz Veloshin. This episode was produced

0:33:58.250 --> 0:34:01.530
<v Speaker 1>by Liza Dennis. It was executive produced by me and

0:34:01.590 --> 0:34:05.770
<v Speaker 1>Julia Nutter for Kaleidoscope and Katrina Norvell for iHeart Podcasts.

0:34:06.150 --> 0:34:08.740
<v Speaker 1>Kyle Murdoch mixed this episode and wrote our theme song.

0:34:09.120 --> 0:34:11.900
<v Speaker 1>A special thank you to Rita Brigotti, Kyle Chaker and

0:34:11.960 --> 0:34:14.890
<v Speaker 1>Taylor Lorenz. Please check out all the work they put

0:34:14.930 --> 0:34:17.290
<v Speaker 1>out into the world. We're lucky to call them friends

0:34:17.310 --> 0:34:17.710
<v Speaker 1>of the pod.