WEBVTT - Week in Tech: Dox, Stock & Two Smoking Barrels

0:00:00.200 --> 0:00:02.880
<v Speaker 1>Thanks for tunion to tech Stuff. If you don't recognize

0:00:02.880 --> 0:00:05.640
<v Speaker 1>my voice, my name is oz Valoshan, and I'm here

0:00:05.680 --> 0:00:08.840
<v Speaker 1>because the inimitable Jonathan Strickland has passed the baton to

0:00:08.920 --> 0:00:12.000
<v Speaker 1>Karra Price and myself to host tech Stuff. The show

0:00:12.039 --> 0:00:14.920
<v Speaker 1>will remain your home for all things tech, and all

0:00:14.960 --> 0:00:18.200
<v Speaker 1>the old episodes will remain available in this feed. Thanks

0:00:18.239 --> 0:00:27.280
<v Speaker 1>for listening. Welcome to Tech Stuff, a production from iHeart

0:00:27.320 --> 0:00:35.680
<v Speaker 1>Podcasts and Kaleidoscope. I'm Anzaloshan and today co host Kara Price,

0:00:35.720 --> 0:00:39.360
<v Speaker 1>and I will bring you three things first. The headlines

0:00:39.400 --> 0:00:44.120
<v Speaker 1>this week, including new and scary uses of chatchipt and

0:00:44.240 --> 0:00:47.640
<v Speaker 1>a sobering reminder of the climate impact of data processing.

0:00:48.360 --> 0:00:51.440
<v Speaker 1>On today's Tech Support segment, we have a conversation with

0:00:51.520 --> 0:00:54.800
<v Speaker 1>four or four Media's Joseph Cox about U haul criminals,

0:00:55.360 --> 0:00:58.320
<v Speaker 1>and then finally with Thrill to introduce a new segment

0:00:58.600 --> 0:01:01.280
<v Speaker 1>which we lovingly call when did This Become a Thing?

0:01:01.920 --> 0:01:04.479
<v Speaker 1>We go on a wild ride with Cara, which ends

0:01:04.480 --> 0:01:07.600
<v Speaker 1>with a revelation about what it means to be a

0:01:07.680 --> 0:01:10.920
<v Speaker 1>digital native. All of that on this week in Tech.

0:01:11.319 --> 0:01:26.960
<v Speaker 1>It's Friday, January seventeenth. Stay with us, Karen Good Afternoon.

0:01:27.000 --> 0:01:31.720
<v Speaker 1>I actually wasn't expecting to Good afternoon, Good afternoon, I

0:01:31.720 --> 0:01:33.720
<v Speaker 1>actually wasn't expecting to see you this afternoon.

0:01:34.200 --> 0:01:35.760
<v Speaker 2>Why am I not supposed to be here?

0:01:35.880 --> 0:01:37.800
<v Speaker 1>Well, now you are supposed to be here. I'm glad

0:01:37.800 --> 0:01:39.960
<v Speaker 1>you're here, but I actually thought you were supposed to

0:01:40.000 --> 0:01:41.160
<v Speaker 1>be in LA this week.

0:01:41.240 --> 0:01:44.759
<v Speaker 2>I was actually I was supposed to be on the

0:01:44.800 --> 0:01:49.040
<v Speaker 2>other coast for work, and obviously I wasn't able to go.

0:01:49.200 --> 0:01:51.920
<v Speaker 2>And I think I speak for both of us when

0:01:51.920 --> 0:01:54.040
<v Speaker 2>I say that our hearts really go out to the

0:01:54.040 --> 0:01:56.920
<v Speaker 2>people who were impacted by the fires and who continue

0:01:56.960 --> 0:01:59.680
<v Speaker 2>to be impacted by the fires. And while I'm glad

0:01:59.680 --> 0:02:02.720
<v Speaker 2>I'm here, I'm not glad about the circumstances.

0:02:02.960 --> 0:02:07.000
<v Speaker 1>No, obviously me neither. But actually what's been going on

0:02:07.080 --> 0:02:11.320
<v Speaker 1>in LA has some interesting text stories around it, and

0:02:11.440 --> 0:02:14.160
<v Speaker 1>so I actually, if you'll allow me, wants to go

0:02:14.240 --> 0:02:16.080
<v Speaker 1>first in this week's news roundup.

0:02:16.160 --> 0:02:19.040
<v Speaker 2>We will forego the continentass and I will let you go.

0:02:20.040 --> 0:02:24.120
<v Speaker 1>So last week you actually sent me a screenshot of

0:02:24.200 --> 0:02:25.239
<v Speaker 1>an Instagram story.

0:02:25.520 --> 0:02:28.880
<v Speaker 2>The only way to get you anything from Instagram. You're

0:02:28.919 --> 0:02:30.120
<v Speaker 2>not on it, which I love about you.

0:02:30.240 --> 0:02:32.440
<v Speaker 1>I'm not I do have the application, I just he.

0:02:32.400 --> 0:02:33.600
<v Speaker 2>Goes on browser people.

0:02:35.480 --> 0:02:39.359
<v Speaker 1>But basically, this Instagram post that you screenshotted for me

0:02:40.040 --> 0:02:43.400
<v Speaker 1>was a picture of this raging inferno, and overlaid was

0:02:43.480 --> 0:02:47.800
<v Speaker 1>text that reads, quote, the average AI data center uses

0:02:48.080 --> 0:02:51.200
<v Speaker 1>three hundred thousand gallons of water a day to keep cool,

0:02:51.639 --> 0:02:55.080
<v Speaker 1>roughly equivalent to water use in one hundred thousand homes.

0:02:55.360 --> 0:03:00.400
<v Speaker 1>Open brackets, NPR, close brackets. Please skip the silly ais,

0:03:00.680 --> 0:03:03.920
<v Speaker 1>the questions to chat GPT, having AI write all of

0:03:03.960 --> 0:03:07.320
<v Speaker 1>your emails. Life needs water, not tech.

0:03:07.560 --> 0:03:09.279
<v Speaker 2>Water is the essence of life.

0:03:09.040 --> 0:03:10.600
<v Speaker 1>To be fair, whata, it is the essence of life.

0:03:10.600 --> 0:03:12.800
<v Speaker 2>And it's also the essence of fighting fires in a

0:03:13.120 --> 0:03:16.080
<v Speaker 2>city where droughts are just commonplace.

0:03:16.440 --> 0:03:19.480
<v Speaker 1>Totally, and I was actually pretty compelled by this post

0:03:19.480 --> 0:03:22.959
<v Speaker 1>that you sent me until I dug a little deeper,

0:03:23.600 --> 0:03:26.919
<v Speaker 1>say more. This was, of course misinformation.

0:03:27.800 --> 0:03:28.919
<v Speaker 2>I sent you misinformation.

0:03:28.960 --> 0:03:32.119
<v Speaker 1>You sent me misinformation, but I didn't amplify.

0:03:32.280 --> 0:03:34.679
<v Speaker 2>This is why I don't listen to news and Instagram stories.

0:03:34.960 --> 0:03:41.360
<v Speaker 1>But my first clue was this open brackets, NPR, close brackets,

0:03:41.680 --> 0:03:45.240
<v Speaker 1>and that gave me an opportunity. Okay, thank you Watson.

0:03:45.280 --> 0:03:48.680
<v Speaker 1>That gave me an opportunity to do some research and

0:03:48.760 --> 0:03:52.080
<v Speaker 1>figure out what the source of this story was, and

0:03:52.120 --> 0:03:54.880
<v Speaker 1>I actually found the original NPR story.

0:03:55.280 --> 0:03:56.880
<v Speaker 2>What was the NPR story.

0:03:56.720 --> 0:03:59.360
<v Speaker 1>Well, it was published in August twenty twenty two, Oh

0:03:59.400 --> 0:04:04.360
<v Speaker 1>my god, and the headline was data center's backbone of

0:04:04.400 --> 0:04:08.440
<v Speaker 1>the digital economy, face water scarcity and climate risk. Now,

0:04:08.440 --> 0:04:11.720
<v Speaker 1>this was published three months before November twenty twenty two,

0:04:11.720 --> 0:04:15.320
<v Speaker 1>which is when chat GPT three entered the world and

0:04:15.760 --> 0:04:18.520
<v Speaker 1>generative AI became something that kind of has entered the

0:04:18.560 --> 0:04:22.320
<v Speaker 1>mainstream discourse. But the NPR story makes no mention of it.

0:04:22.560 --> 0:04:27.159
<v Speaker 1>The actual quote was quote a mid size data center

0:04:27.240 --> 0:04:30.400
<v Speaker 1>consumes around three hundred thousand gallons of water. Again, no

0:04:30.520 --> 0:04:32.960
<v Speaker 1>mention of quote the average AI data center from the

0:04:32.960 --> 0:04:36.200
<v Speaker 1>Instagram story. The story was really just about regular old

0:04:36.320 --> 0:04:39.279
<v Speaker 1>data centers that were processing Google searches and doing weather

0:04:39.320 --> 0:04:46.040
<v Speaker 1>forecasts and helping bitcoin traders making lose fortunes. That wasn't

0:04:46.080 --> 0:04:51.040
<v Speaker 1>the only distortion in the non My mind has been

0:04:51.480 --> 0:04:53.800
<v Speaker 1>in the non AI slop that you sent me. It

0:04:53.920 --> 0:04:55.400
<v Speaker 1>is human generated slop.

0:04:55.520 --> 0:04:57.520
<v Speaker 2>It distresses me to know end that we're in, like

0:04:57.720 --> 0:05:00.960
<v Speaker 2>true crises, how easy it it is for people to

0:05:01.000 --> 0:05:05.839
<v Speaker 2>get excited about information that seems compelling and not only

0:05:05.920 --> 0:05:09.440
<v Speaker 2>believe it, but share it because it seems so compelling.

0:05:09.640 --> 0:05:12.960
<v Speaker 1>I've actually find the truth of this story as interesting

0:05:13.000 --> 0:05:16.400
<v Speaker 1>as the misinformation. So the Instagram story said that these

0:05:16.440 --> 0:05:19.240
<v Speaker 1>three hundred thousand gallons per day of water could otherwise

0:05:19.360 --> 0:05:22.360
<v Speaker 1>serve one hundred thousand US homes per day, it's just

0:05:22.400 --> 0:05:24.640
<v Speaker 1>made up. No, In the NPR story, it's one thousand.

0:05:26.320 --> 0:05:30.280
<v Speaker 1>So that's quite a big difference. As we know, there's

0:05:30.279 --> 0:05:33.560
<v Speaker 1>been this kind of explosion in demand for data centers

0:05:33.600 --> 0:05:37.520
<v Speaker 1>exactly because of AI. The La Times actually reported that

0:05:37.920 --> 0:05:41.200
<v Speaker 1>a single query on a chatbot that uses AI is

0:05:41.320 --> 0:05:45.240
<v Speaker 1>estimated to require at least ten times more electricity than

0:05:45.240 --> 0:05:48.159
<v Speaker 1>a standard search on Google. So there is this spiritual

0:05:48.240 --> 0:05:51.040
<v Speaker 1>truth of the story you shared, which is data centers

0:05:51.080 --> 0:05:54.880
<v Speaker 1>create heat. Heat needs water to cool it down, and

0:05:54.920 --> 0:05:57.600
<v Speaker 1>the explosion in generative of AI is putting a lot

0:05:57.640 --> 0:05:59.680
<v Speaker 1>more strain on data centers. So there is actually weirdly

0:05:59.720 --> 0:06:00.599
<v Speaker 1>lot of truth in the story.

0:06:00.920 --> 0:06:05.320
<v Speaker 2>But the connection directly between data centers and the fires

0:06:05.400 --> 0:06:07.400
<v Speaker 2>in Los Angeles.

0:06:06.880 --> 0:06:10.320
<v Speaker 1>There is no suggestion there is a direct connection, and

0:06:10.360 --> 0:06:13.640
<v Speaker 1>that's primarily because there aren't that many data centers in

0:06:13.640 --> 0:06:15.760
<v Speaker 1>the Los Angeles area. There are a lot of data

0:06:15.800 --> 0:06:19.200
<v Speaker 1>centers in northern California, and there is now actually a

0:06:19.200 --> 0:06:22.320
<v Speaker 1>big program to build more data centers in southern California,

0:06:22.480 --> 0:06:26.000
<v Speaker 1>so this could become kind of a bigger problem. But Cara,

0:06:26.279 --> 0:06:28.240
<v Speaker 1>I know, I'm really only allowed one story, but this

0:06:28.279 --> 0:06:30.520
<v Speaker 1>one is sort of very much connected, and it's in

0:06:30.560 --> 0:06:33.159
<v Speaker 1>one of my favorite news sources. Can you guess what

0:06:33.200 --> 0:06:33.560
<v Speaker 1>it is?

0:06:33.680 --> 0:06:34.599
<v Speaker 2>The Daily Mail?

0:06:35.120 --> 0:06:35.360
<v Speaker 1>No?

0:06:36.839 --> 0:06:39.960
<v Speaker 2>I really one of your favorite the New York Posts?

0:06:40.000 --> 0:06:43.200
<v Speaker 1>No? No, no, Yeah, you're embarrassing. Sorry, this is the

0:06:43.240 --> 0:06:44.200
<v Speaker 1>Sacramento Bee.

0:06:44.400 --> 0:06:45.760
<v Speaker 2>I love the Sacramento Bee.

0:06:45.800 --> 0:06:49.920
<v Speaker 1>Sacramento is a great paper. On December eighteenth, twenty twenty four,

0:06:50.360 --> 0:06:54.080
<v Speaker 1>The Bee ran a prescient op ed by Dean Flores,

0:06:54.120 --> 0:06:59.039
<v Speaker 1>a former California State Senator, under the headline California's next

0:06:59.080 --> 0:07:02.719
<v Speaker 1>water war won't concern agriculture. It will be about AI.

0:07:03.400 --> 0:07:06.239
<v Speaker 2>Mmmm, so it's not the almonds, it's the AI.

0:07:06.400 --> 0:07:08.520
<v Speaker 1>It's the AI is the AI and the almonds, And

0:07:08.520 --> 0:07:11.520
<v Speaker 1>and Flores continues that the struggle for water, of course,

0:07:11.600 --> 0:07:14.560
<v Speaker 1>is not a new topic in California. It used to

0:07:14.600 --> 0:07:19.360
<v Speaker 1>be farms versus cities, agriculture versus know, urban development, but

0:07:19.480 --> 0:07:22.440
<v Speaker 1>now there's this third great demand on the water supply

0:07:22.520 --> 0:07:25.960
<v Speaker 1>of a drought prone state. There are actually more than

0:07:25.960 --> 0:07:29.600
<v Speaker 1>two hundred and seventy data centers already in California, and

0:07:29.680 --> 0:07:32.600
<v Speaker 1>in California, water consumption from those data centers is in

0:07:32.600 --> 0:07:36.520
<v Speaker 1>the billions of gallons each year and there.

0:07:36.480 --> 0:07:39.040
<v Speaker 2>And Flores points this out in his.

0:07:38.880 --> 0:07:42.560
<v Speaker 1>Exactly and says that data centers could double or triple

0:07:42.600 --> 0:07:45.680
<v Speaker 1>their water demand in the next decade in California. And

0:07:45.720 --> 0:07:48.840
<v Speaker 1>I just think what Flora's ended his piece saying was

0:07:49.480 --> 0:07:52.360
<v Speaker 1>this story hasn't yet been written. AI infrastructure is being

0:07:52.360 --> 0:07:54.720
<v Speaker 1>built in real time, so there are opportunities to kind

0:07:54.760 --> 0:07:57.040
<v Speaker 1>of do better when it comes to figuring out how

0:07:57.080 --> 0:07:58.960
<v Speaker 1>to to meet this demand.

0:07:59.240 --> 0:08:01.680
<v Speaker 2>Yeah, so I do agree with you, Oz, and I

0:08:01.680 --> 0:08:04.480
<v Speaker 2>think it's important on this show when we cover things

0:08:04.520 --> 0:08:09.120
<v Speaker 2>that can be a little bit paranoia inducing or anxiety provoking,

0:08:09.400 --> 0:08:13.360
<v Speaker 2>for us to talk about technology that really is solving

0:08:13.400 --> 0:08:16.360
<v Speaker 2>a human problem. I have a ton of friends in La.

0:08:16.440 --> 0:08:21.119
<v Speaker 2>My sister lives in LA, and they are all using

0:08:21.120 --> 0:08:24.280
<v Speaker 2>this technology called watch Duty. Do you know what watch

0:08:24.320 --> 0:08:28.240
<v Speaker 2>to do? So? Watch Duty is an app that is

0:08:28.600 --> 0:08:31.440
<v Speaker 2>so beta looking that it kind of looks like the

0:08:31.440 --> 0:08:35.600
<v Speaker 2>Oregon Trail. And unfortunately it does look like the Oregon

0:08:35.640 --> 0:08:39.160
<v Speaker 2>Trail as of last week, because it's just like firefire, firefire, horrible,

0:08:39.200 --> 0:08:41.600
<v Speaker 2>don't be there, don't do this. But what watch Duty

0:08:41.720 --> 0:08:45.720
<v Speaker 2>is in practice is this free app that shows active fires,

0:08:45.800 --> 0:08:49.920
<v Speaker 2>evacuation zones, and air quality indexes in the LA area.

0:08:50.000 --> 0:08:53.920
<v Speaker 2>And it's actually, you know, anecdotally been a lifeline for

0:08:54.000 --> 0:08:57.680
<v Speaker 2>people living there. And it's just this really great act

0:08:57.720 --> 0:09:00.920
<v Speaker 2>of humanity and that it's not selling people data, it's

0:09:00.960 --> 0:09:03.520
<v Speaker 2>not showing you ads. You don't have to log in,

0:09:03.920 --> 0:09:07.000
<v Speaker 2>and it is completely donation based. It's a nonprofit. Well,

0:09:07.240 --> 0:09:10.080
<v Speaker 2>you know, I wanted to highlight this because I think

0:09:10.160 --> 0:09:14.760
<v Speaker 2>often about disaster capitalism, and this, to me is more

0:09:15.320 --> 0:09:16.839
<v Speaker 2>disaster troubleshooting.

0:09:17.120 --> 0:09:20.120
<v Speaker 1>Yeah. One of the fundamental interesting things about tech is

0:09:20.160 --> 0:09:24.480
<v Speaker 1>it often does emerge in response to real world problems

0:09:24.520 --> 0:09:26.720
<v Speaker 1>and can help solve them or at least mitigate them.

0:09:26.880 --> 0:09:29.520
<v Speaker 1>It's just what happens a day after, which is often

0:09:29.559 --> 0:09:32.920
<v Speaker 1>where things go wrong. So carry you've already over delivered

0:09:32.960 --> 0:09:34.920
<v Speaker 1>by telling me something interesting about the story.

0:09:35.160 --> 0:09:35.720
<v Speaker 2>Nothing new.

0:09:36.240 --> 0:09:39.880
<v Speaker 1>I didn't know about Watch Duty, But what have you

0:09:39.920 --> 0:09:40.440
<v Speaker 1>got for me?

0:09:40.920 --> 0:09:43.959
<v Speaker 2>Well, the last decent man on the internet read it.

0:09:44.720 --> 0:09:51.520
<v Speaker 2>Our old friend served me with something so demented. Just

0:09:51.520 --> 0:09:53.160
<v Speaker 2>just bear with me because this is there's a lot

0:09:53.160 --> 0:09:56.560
<v Speaker 2>of like R two D two in this But there's

0:09:56.559 --> 0:09:58.080
<v Speaker 2>a video that I'm going to show you in a

0:09:58.120 --> 0:10:03.080
<v Speaker 2>second that shows this guy who goes by the online

0:10:03.160 --> 0:10:09.160
<v Speaker 2>name STS three d. He's created a robot rifle what

0:10:09.600 --> 0:10:15.440
<v Speaker 2>that can shoot automatically and he's giving this robot rifle

0:10:15.559 --> 0:10:17.959
<v Speaker 2>directions using chat GPT.

0:10:18.080 --> 0:10:18.760
<v Speaker 1>Are you serious?

0:10:18.960 --> 0:10:20.560
<v Speaker 2>I got it? Did you? Did you know this?

0:10:20.800 --> 0:10:21.679
<v Speaker 1>I didn't know this.

0:10:21.360 --> 0:10:24.920
<v Speaker 2>This is okay, So let me let me just show

0:10:24.920 --> 0:10:25.480
<v Speaker 2>you this video.

0:10:27.320 --> 0:10:29.079
<v Speaker 1>Oh my god.

0:10:29.160 --> 0:10:31.800
<v Speaker 2>Chat gpt, we're under attack from the front left and

0:10:31.920 --> 0:10:32.400
<v Speaker 2>front right.

0:10:32.559 --> 0:10:33.559
<v Speaker 1>Respond to bording with it.

0:10:35.920 --> 0:10:37.000
<v Speaker 3>Oh my god.

0:10:39.880 --> 0:10:42.880
<v Speaker 2>If you need any further assistance, just let me know.

0:10:43.480 --> 0:10:45.400
<v Speaker 2>By the way, that's chat gpt talking back him.

0:10:46.960 --> 0:10:57.760
<v Speaker 1>One round. There is a rifle following this guy's voice commons.

0:10:54.800 --> 0:10:56.640
<v Speaker 2>Like an automated assault leaptip cheez.

0:10:57.679 --> 0:10:59.040
<v Speaker 1>Wow. What did you think when you saw this?

0:11:00.559 --> 0:11:02.560
<v Speaker 2>Well? I thought to myself, Am I going to do

0:11:02.600 --> 0:11:05.840
<v Speaker 2>another story this week where chat gpt is being used

0:11:06.080 --> 0:11:09.640
<v Speaker 2>by individuals to create weapons?

0:11:10.040 --> 0:11:10.280
<v Speaker 3>Yes?

0:11:10.559 --> 0:11:11.120
<v Speaker 1>Yeah, you know.

0:11:11.120 --> 0:11:14.080
<v Speaker 2>When I saw it, I couldn't really wrap my head

0:11:14.120 --> 0:11:18.800
<v Speaker 2>around how it was actually working and how chat GPT's

0:11:19.400 --> 0:11:23.640
<v Speaker 2>API was being used to operate operate.

0:11:24.040 --> 0:11:26.480
<v Speaker 1>So I have this friend, you have another friend you

0:11:26.520 --> 0:11:29.160
<v Speaker 1>talk about tech stuff with I knew, oh geez, and

0:11:29.240 --> 0:11:29.720
<v Speaker 1>he's straight.

0:11:31.880 --> 0:11:35.840
<v Speaker 2>So I sent this video and he basically said that

0:11:36.280 --> 0:11:39.080
<v Speaker 2>STS three D. The guy in the video is using

0:11:39.360 --> 0:11:43.720
<v Speaker 2>voice to text and is basically feeding that to chat GPT,

0:11:44.280 --> 0:11:48.160
<v Speaker 2>and then he's running a separate program that can control

0:11:48.240 --> 0:11:52.120
<v Speaker 2>the robot gun's movements, like you know how many degrees

0:11:52.160 --> 0:11:55.120
<v Speaker 2>to move the gun, when to shoot it. And that

0:11:55.280 --> 0:11:59.959
<v Speaker 2>program that he is designed is communicating with chat GPT.

0:12:00.280 --> 0:12:04.120
<v Speaker 1>His speaking to check GPT, which is then interpreting his

0:12:04.240 --> 0:12:08.400
<v Speaker 1>requests and passing it on to the robot, but presumably

0:12:08.440 --> 0:12:12.080
<v Speaker 1>not in natural language, presumably translating natural language into a

0:12:12.080 --> 0:12:12.880
<v Speaker 1>computer command.

0:12:13.240 --> 0:12:16.000
<v Speaker 2>That's correct. Okay, that's correct, And that's why he's talking

0:12:16.080 --> 0:12:19.040
<v Speaker 2>to something that sounds like Siri. The other thing that

0:12:19.080 --> 0:12:22.160
<v Speaker 2>I want to mention, of course, is that open Ai

0:12:22.280 --> 0:12:24.600
<v Speaker 2>got wind of this because the video went viral, right

0:12:25.200 --> 0:12:27.520
<v Speaker 2>and they came out and said that what this user

0:12:27.559 --> 0:12:31.040
<v Speaker 2>is doing goes against company policy. There's a very interesting

0:12:31.080 --> 0:12:35.439
<v Speaker 2>loophole that I found accidentally through reading about this on futurism,

0:12:35.960 --> 0:12:38.959
<v Speaker 2>which was actually reported by the intercept last year, which

0:12:39.080 --> 0:12:43.920
<v Speaker 2>is that open Ai quietly removed language prohibiting the use

0:12:43.920 --> 0:12:48.880
<v Speaker 2>of its tool for military purposes. And of course this

0:12:49.080 --> 0:12:52.280
<v Speaker 2>makes sense because just last month it was reported that

0:12:52.320 --> 0:12:55.720
<v Speaker 2>open ai is launching a partnership with Andrel, the American

0:12:55.720 --> 0:12:58.800
<v Speaker 2>defense company. Yeah, you know, for open Ai to stand

0:12:58.880 --> 0:13:02.000
<v Speaker 2>up and say okay, yes, for an individual user using

0:13:02.040 --> 0:13:04.960
<v Speaker 2>open Ai in this way goes against company policy, but

0:13:05.200 --> 0:13:09.240
<v Speaker 2>quietly in the background take out language opposing the use

0:13:09.280 --> 0:13:10.560
<v Speaker 2>of it for military defense.

0:13:11.840 --> 0:13:14.120
<v Speaker 1>I mean it is that, isn't It's like you always

0:13:14.120 --> 0:13:16.200
<v Speaker 1>talk about how things get faster and faster. It took

0:13:16.200 --> 0:13:20.360
<v Speaker 1>Google like fifteen years to ten years to abandon their

0:13:20.400 --> 0:13:24.080
<v Speaker 1>don't be evil policy. Yeah, it has taken open Ai

0:13:24.240 --> 0:13:26.880
<v Speaker 1>five minutes to make an exception for military use of

0:13:26.880 --> 0:13:27.480
<v Speaker 1>that technology.

0:13:27.559 --> 0:13:29.600
<v Speaker 2>Well, they pivoted from a five oh one c to

0:13:29.679 --> 0:13:30.880
<v Speaker 2>a private company quickly.

0:13:30.960 --> 0:13:31.360
<v Speaker 1>There you go.

0:13:34.080 --> 0:13:37.960
<v Speaker 2>Coming up, we'll discuss another reason to hate moving. Stay

0:13:37.960 --> 0:13:50.840
<v Speaker 2>with us. So today for our tech support segment, we

0:13:50.920 --> 0:13:54.920
<v Speaker 2>have a story about how cybercrime is meeting good old

0:13:54.960 --> 0:14:00.440
<v Speaker 2>fashioned IRL crime and somehow it all comes together thanks

0:14:00.520 --> 0:14:05.200
<v Speaker 2>to well as a lesbian, it's an important company, you haul,

0:14:05.880 --> 0:14:07.680
<v Speaker 2>and we're going to get this story from Joseph Cox,

0:14:07.720 --> 0:14:09.600
<v Speaker 2>who's one of the brilliant tech writers at four or

0:14:09.600 --> 0:14:10.160
<v Speaker 2>for Media.

0:14:10.760 --> 0:14:12.560
<v Speaker 1>Joseph, Welcome, it's great to have you on the show.

0:14:13.000 --> 0:14:14.200
<v Speaker 3>Thank you so much for having me.

0:14:14.880 --> 0:14:17.400
<v Speaker 1>So you wrote this story in four of for with

0:14:17.520 --> 0:14:21.200
<v Speaker 1>the headline quote violent hackers are using you Haul to

0:14:21.320 --> 0:14:22.160
<v Speaker 1>dox targets.

0:14:22.880 --> 0:14:26.920
<v Speaker 2>So when I read this story or saw this headline originally,

0:14:26.960 --> 0:14:28.640
<v Speaker 2>I'm sort of like, well, what does you Haul have

0:14:28.760 --> 0:14:30.640
<v Speaker 2>to do with doxing and hackers?

0:14:31.040 --> 0:14:33.800
<v Speaker 3>Yeah, and it's not obvious at first, and I don't

0:14:33.800 --> 0:14:36.520
<v Speaker 3>think anybody really thinks of you Haul of being a

0:14:36.600 --> 0:14:39.440
<v Speaker 3>juicy hacking target. But when you take a step back

0:14:39.480 --> 0:14:42.320
<v Speaker 3>and you think about it, people who use you Haul,

0:14:42.480 --> 0:14:44.920
<v Speaker 3>they're probably going to give their real phone number because

0:14:44.920 --> 0:14:46.720
<v Speaker 3>obviously they need to pick up the truck and they

0:14:46.720 --> 0:14:49.840
<v Speaker 3>need to organize that. They might give their real address

0:14:49.920 --> 0:14:52.800
<v Speaker 3>as well, because you know, you all needs to verify that,

0:14:52.920 --> 0:14:55.800
<v Speaker 3>and maybe they're real payment information because obviously they need

0:14:55.800 --> 0:14:58.080
<v Speaker 3>to pay for the truck as well. So it's actually

0:14:58.120 --> 0:15:02.080
<v Speaker 3>a really good source for accurate information if a hacker

0:15:02.120 --> 0:15:05.760
<v Speaker 3>is trying to reveal somebody's identity and you Haul has

0:15:05.760 --> 0:15:09.240
<v Speaker 3>been hacked multiple times over the years. You know, happened

0:15:09.240 --> 0:15:11.880
<v Speaker 3>in twenty twenty and I think twenty thirteen as well,

0:15:12.080 --> 0:15:14.400
<v Speaker 3>and in at least one of those cases it did

0:15:14.440 --> 0:15:18.840
<v Speaker 3>include driver license information. But at the time we didn't

0:15:18.880 --> 0:15:22.560
<v Speaker 3>really have any context of oh, well, why do hackers

0:15:22.600 --> 0:15:25.200
<v Speaker 3>care about you whole? And I think this story shows

0:15:25.240 --> 0:15:27.240
<v Speaker 3>why some people may care about that sort of target.

0:15:27.960 --> 0:15:30.120
<v Speaker 1>So who's doing this and what do we know about them?

0:15:31.000 --> 0:15:36.560
<v Speaker 3>So it's predominantly a group or a nebulous network of

0:15:36.640 --> 0:15:41.080
<v Speaker 3>people known as comm which is short for community, and

0:15:41.160 --> 0:15:44.160
<v Speaker 3>this is made up of a lot of young hackers

0:15:44.200 --> 0:15:47.760
<v Speaker 3>who take over phone numbers, they break into companies, but

0:15:48.160 --> 0:15:49.760
<v Speaker 3>the main thing is that they try to get as

0:15:49.840 --> 0:15:53.280
<v Speaker 3>much data as they can on potential targets.

0:15:53.480 --> 0:15:57.600
<v Speaker 1>As a practical matter, Joseph, how are the hackers getting

0:15:57.600 --> 0:15:58.880
<v Speaker 1>this information from you Hall?

0:15:59.280 --> 0:16:03.680
<v Speaker 3>So they're not not targeting individual you Haul customer accounts.

0:16:03.720 --> 0:16:07.680
<v Speaker 3>What they're doing is they're making phishing pages which will

0:16:07.680 --> 0:16:11.520
<v Speaker 3>trick people into handing over passwords, but specifically for you

0:16:11.640 --> 0:16:13.640
<v Speaker 3>Haul employee accounts.

0:16:13.760 --> 0:16:14.920
<v Speaker 1>This is like the Sony pictures.

0:16:14.960 --> 0:16:18.400
<v Speaker 3>Heck, yeah, So when the hackers have the loging credentials

0:16:18.400 --> 0:16:21.400
<v Speaker 3>for a you Haul employee, you know, they essentially become

0:16:22.080 --> 0:16:24.640
<v Speaker 3>that employee with all of the sort of access to

0:16:24.720 --> 0:16:29.040
<v Speaker 3>information they might have, so they can rifle through customer data.

0:16:29.440 --> 0:16:33.840
<v Speaker 3>And this is a constant problem across companies where you

0:16:33.920 --> 0:16:37.040
<v Speaker 3>have it, especially with US and UK telecoms as well.

0:16:37.320 --> 0:16:41.120
<v Speaker 3>These hackers will break into employee accounts so then they

0:16:41.120 --> 0:16:42.520
<v Speaker 3>can look up customer information.

0:16:43.280 --> 0:16:45.520
<v Speaker 1>What do they tend to be going after and who

0:16:45.560 --> 0:16:46.640
<v Speaker 1>is the typical victim?

0:16:47.040 --> 0:16:51.040
<v Speaker 3>In writing this story, I spoke to somebody who writes

0:16:51.120 --> 0:16:55.480
<v Speaker 3>the tools to steal you haul logins and they told

0:16:55.560 --> 0:17:01.080
<v Speaker 3>me that basically people inside the com use to dox

0:17:01.120 --> 0:17:05.919
<v Speaker 3>one another or dos other targets, and they were, you know,

0:17:06.200 --> 0:17:08.679
<v Speaker 3>it sounded like quite surprised the amount of data you

0:17:08.720 --> 0:17:09.440
<v Speaker 3>can get in there.

0:17:10.040 --> 0:17:13.240
<v Speaker 1>Doxing is when you sort of get somebody's private details

0:17:13.320 --> 0:17:14.600
<v Speaker 1>and then publicize them.

0:17:14.680 --> 0:17:14.840
<v Speaker 2>Yeah.

0:17:14.920 --> 0:17:19.000
<v Speaker 3>Docting is where you will take and find somebody's personal information,

0:17:20.040 --> 0:17:23.560
<v Speaker 3>maybe their physical address, email address, phone number, and then

0:17:23.600 --> 0:17:27.040
<v Speaker 3>maybe some more sensitive data as well, and either using

0:17:27.080 --> 0:17:30.720
<v Speaker 3>that for your own means or publishing it online. Now

0:17:30.960 --> 0:17:33.879
<v Speaker 3>I don't know exactly what a specific member of the

0:17:33.920 --> 0:17:37.120
<v Speaker 3>comm has used this data for, but you can easily

0:17:37.160 --> 0:17:41.159
<v Speaker 3>see it potentially being used for physical violence. Members of

0:17:41.200 --> 0:17:44.800
<v Speaker 3>the com often shoot at each other's houses or hire

0:17:44.800 --> 0:17:47.800
<v Speaker 3>people to do so. They throw bricks through them, they

0:17:48.000 --> 0:17:52.800
<v Speaker 3>rob one another armed with hammers or other weapons. And

0:17:53.000 --> 0:17:56.919
<v Speaker 3>I absolutely put the harvesting of this U haul data

0:17:57.400 --> 0:18:00.760
<v Speaker 3>inside that context and that it is being you by

0:18:01.240 --> 0:18:03.040
<v Speaker 3>violent criminal hackers.

0:18:03.640 --> 0:18:06.280
<v Speaker 2>So this is really about being an admin. It's not

0:18:06.359 --> 0:18:08.040
<v Speaker 2>about getting individual information.

0:18:09.000 --> 0:18:09.760
<v Speaker 3>Yeah, exactly.

0:18:09.920 --> 0:18:11.640
<v Speaker 1>I kind of feel like a lot of people when

0:18:11.680 --> 0:18:15.160
<v Speaker 1>it comes to Internet privacy, unless they've been like scanned

0:18:15.160 --> 0:18:17.919
<v Speaker 1>in some way themselves. You know, their eyes can glaze

0:18:17.960 --> 0:18:21.119
<v Speaker 1>over a little bit. But in your story, people actually

0:18:21.119 --> 0:18:22.600
<v Speaker 1>got shot after being dogsed.

0:18:23.520 --> 0:18:27.119
<v Speaker 3>Yeah. I think people have a pretty old understanding of

0:18:27.119 --> 0:18:30.199
<v Speaker 3>what cybercrime is. They imagine, you know, somebody in a

0:18:30.240 --> 0:18:33.720
<v Speaker 3>hoodie overall, laptop in a dark basement or whatever doing

0:18:33.760 --> 0:18:39.200
<v Speaker 3>these sort of abstract, obscure crimes. Cybercrime today's done by

0:18:39.400 --> 0:18:41.840
<v Speaker 3>people who are a lot younger, and they're a lot

0:18:41.880 --> 0:18:45.040
<v Speaker 3>more violent in some cases. If they want to get

0:18:45.040 --> 0:18:48.080
<v Speaker 3>hold of maybe login tokens, you know, the two FA

0:18:48.200 --> 0:18:51.040
<v Speaker 3>tokens to get into an account. Some will even threaten

0:18:51.440 --> 0:18:53.960
<v Speaker 3>to go shoot up some of the's house. And that's

0:18:54.000 --> 0:18:57.000
<v Speaker 3>why I'm so fascinated by this community. Because it's a

0:18:57.000 --> 0:19:02.000
<v Speaker 3>complete intersection of digital and physical crime. You know, as

0:19:02.000 --> 0:19:05.640
<v Speaker 3>a crime reporter for more than ten years, I've never

0:19:05.760 --> 0:19:09.720
<v Speaker 3>quite seen as latent an intersection as these guys.

0:19:10.000 --> 0:19:12.000
<v Speaker 1>This is the metaverse, but not the one that all

0:19:12.080 --> 0:19:14.080
<v Speaker 1>the investors were hyping.

0:19:14.720 --> 0:19:17.760
<v Speaker 3>Yeah, it's the metaverse, but not the very cringe one

0:19:17.800 --> 0:19:20.600
<v Speaker 3>from Mark Zuckerberg. Is unfortunately, the very real way. And

0:19:21.000 --> 0:19:23.120
<v Speaker 3>it's funny you bring up metaverse because actually a lot

0:19:23.160 --> 0:19:26.040
<v Speaker 3>of the people that get into this community, they actually

0:19:26.560 --> 0:19:30.879
<v Speaker 3>fall into it through video games such as Minecraft or Roadblocks,

0:19:31.000 --> 0:19:34.040
<v Speaker 3>which arguably are the metaverse, and then they end up

0:19:34.080 --> 0:19:35.080
<v Speaker 3>in this world of cybercrime.

0:19:35.440 --> 0:19:38.359
<v Speaker 2>And do you think there's a part of playing those

0:19:38.400 --> 0:19:41.600
<v Speaker 2>games that kind of like blurs the line between like

0:19:41.640 --> 0:19:44.080
<v Speaker 2>the reality of what they're doing and the games that

0:19:44.080 --> 0:19:45.040
<v Speaker 2>they're used to playing.

0:19:45.680 --> 0:19:49.359
<v Speaker 3>Yeah. Absolutely. And when I've spoken to many different members

0:19:49.359 --> 0:19:52.640
<v Speaker 3>of the com Roadblocks and Minecraft keep coming up over

0:19:52.680 --> 0:19:55.760
<v Speaker 3>and over again where even hackers will break into each

0:19:55.760 --> 0:19:59.200
<v Speaker 3>other's Roadblocks accounts to steal, you know, their rare hat

0:19:59.320 --> 0:20:02.240
<v Speaker 3>or their rare eye or something, and eventually that escalates

0:20:02.280 --> 0:20:05.360
<v Speaker 3>into well, there's steal hundreds of thousands of dollars of cryptocurrency,

0:20:05.400 --> 0:20:05.760
<v Speaker 3>as well.

0:20:06.080 --> 0:20:08.840
<v Speaker 1>Is there a single story or a single real world

0:20:09.000 --> 0:20:12.840
<v Speaker 1>crime that for you, really throws this into relief for

0:20:12.880 --> 0:20:15.480
<v Speaker 1>the kind of non tech news junkie.

0:20:16.119 --> 0:20:20.080
<v Speaker 3>So recently I wrote about something called the Colm World War,

0:20:20.320 --> 0:20:23.040
<v Speaker 3>which is obviously not an entirely serious term. This is

0:20:23.080 --> 0:20:26.000
<v Speaker 3>what members of the comm called it themselves. But there

0:20:26.000 --> 0:20:30.600
<v Speaker 3>were a series of robberies, shootings and brickings between different

0:20:30.680 --> 0:20:32.880
<v Speaker 3>rivals inside the como and.

0:20:33.240 --> 0:20:37.080
<v Speaker 1>Before the West Side story of Legs exactly.

0:20:37.520 --> 0:20:39.840
<v Speaker 3>And I would say it's sort of bubbled over out

0:20:39.880 --> 0:20:42.800
<v Speaker 3>of calm and into the wider public, because I've seen

0:20:42.880 --> 0:20:46.359
<v Speaker 3>videos where Colm will hire people to go throw a

0:20:46.359 --> 0:20:48.679
<v Speaker 3>brick at somebody's house, but they throw it at the

0:20:48.720 --> 0:20:51.600
<v Speaker 3>wrong home and then it's just impacted the completely random

0:20:51.640 --> 0:20:53.840
<v Speaker 3>person and now they have a smashed door or smashed

0:20:53.920 --> 0:20:56.960
<v Speaker 3>ring door, camera or whatever. So it is starting to

0:20:57.119 --> 0:21:00.760
<v Speaker 3>bleed over into the world of just ordinary people who

0:21:01.080 --> 0:21:04.000
<v Speaker 3>have no idea why somebody is throwing a brick through

0:21:04.000 --> 0:21:06.120
<v Speaker 3>the window because something happened on roadblocks.

0:21:06.160 --> 0:21:06.320
<v Speaker 1>You know.

0:21:07.280 --> 0:21:10.840
<v Speaker 3>Fortunately, if you are a general member of the U

0:21:10.920 --> 0:21:14.480
<v Speaker 3>haul using public, you probably don't need to worry about

0:21:14.480 --> 0:21:18.040
<v Speaker 3>this in that maybe somebody you know or somebody nearby

0:21:18.119 --> 0:21:21.560
<v Speaker 3>unfortunately becomes a target of calm. You know, that's kind

0:21:21.600 --> 0:21:23.280
<v Speaker 3>of impossible to say, and I would just be very

0:21:23.320 --> 0:21:26.600
<v Speaker 3>bad luck. But they do predominantly go and try to

0:21:26.680 --> 0:21:30.120
<v Speaker 3>rob people or target people who hold a lot of cryptocurrency.

0:21:30.200 --> 0:21:33.480
<v Speaker 3>They have various tools which can determine, Oh, this person

0:21:33.520 --> 0:21:36.280
<v Speaker 3>has x amount of bitcoin in their coin base account,

0:21:36.520 --> 0:21:39.679
<v Speaker 3>let's go after them. So, I mean, the threat to

0:21:39.720 --> 0:21:43.080
<v Speaker 3>a bitcoin investor is very, very different to a sort

0:21:43.119 --> 0:21:45.199
<v Speaker 3>of ordinary member of the public, and you should be

0:21:45.200 --> 0:21:45.720
<v Speaker 3>worried then.

0:21:46.080 --> 0:21:52.280
<v Speaker 2>So if you're a lesbian bitcoin investor.

0:21:50.840 --> 0:21:52.760
<v Speaker 1>Is the center of the ven diagram, you're going to

0:21:52.800 --> 0:21:58.840
<v Speaker 1>calm You probably already the bricks already have lesbian lucky

0:21:58.960 --> 0:22:02.359
<v Speaker 1>don't drive. Joseph, thank you for joining us today and

0:22:02.400 --> 0:22:04.480
<v Speaker 1>we hope to see you on the program again soon.

0:22:04.840 --> 0:22:06.800
<v Speaker 3>Thanks Joseph, thank you so much.

0:22:09.160 --> 0:22:19.840
<v Speaker 1>Coming up, Kara's Big Adventure stay with us. I'm excited

0:22:19.880 --> 0:22:23.520
<v Speaker 1>to be launching this new segment that we're calling when

0:22:23.560 --> 0:22:25.639
<v Speaker 1>did this become a thing? We've got a few listener

0:22:25.680 --> 0:22:29.560
<v Speaker 1>emails to our account tech Stuff podcast at gmail dot

0:22:29.600 --> 0:22:33.040
<v Speaker 1>com and they were very touching and very encouraging, but

0:22:33.119 --> 0:22:38.000
<v Speaker 1>also directive and one of the listener emails. Basically said Jonathan,

0:22:38.160 --> 0:22:42.120
<v Speaker 1>over the course of sixteen years, had so many interesting

0:22:42.160 --> 0:22:45.919
<v Speaker 1>segments about the history of various technologies, and you know

0:22:45.960 --> 0:22:48.760
<v Speaker 1>we're hungry for more of that. And so when did

0:22:48.760 --> 0:22:51.040
<v Speaker 1>this become a thing? It's kind of in service of

0:22:51.080 --> 0:22:52.320
<v Speaker 1>trying to scratch that itch.

0:22:53.040 --> 0:22:56.200
<v Speaker 2>Yeah, each week we're going to bring you a story

0:22:56.359 --> 0:22:59.240
<v Speaker 2>or observation from the real world and try to figure

0:22:59.240 --> 0:23:01.160
<v Speaker 2>out when it became a thing.

0:23:01.359 --> 0:23:04.240
<v Speaker 1>And this has a little bit of our favorite pair

0:23:04.320 --> 0:23:08.800
<v Speaker 1>of historical platonic freelance detectives.

0:23:08.240 --> 0:23:12.720
<v Speaker 2>That's correct. I get to be the Watson to your Sherlock.

0:23:12.840 --> 0:23:16.320
<v Speaker 1>And this week you have something that you encountered in

0:23:16.359 --> 0:23:20.960
<v Speaker 1>the wild that made you question when something became a thing.

0:23:21.280 --> 0:23:23.439
<v Speaker 2>Yeah, it was more of a rescue mission. So I

0:23:23.480 --> 0:23:27.760
<v Speaker 2>recently had this experience where I came face to face

0:23:27.960 --> 0:23:34.000
<v Speaker 2>with one of the twentieth centuries most prolific writers and

0:23:34.040 --> 0:23:38.520
<v Speaker 2>feminist icons. And it wasn't the best case scenario. She

0:23:38.840 --> 0:23:43.600
<v Speaker 2>had fallen on the street and was a little bit disoriented,

0:23:44.280 --> 0:23:48.560
<v Speaker 2>and my first thought was, we will not lose a

0:23:48.560 --> 0:23:52.720
<v Speaker 2>feminist icon on my watch. My second thought was, we

0:23:52.760 --> 0:23:55.040
<v Speaker 2>won't lose her because I'm going to call an ambulance

0:23:55.080 --> 0:23:58.879
<v Speaker 2>on my cellphone. That took too long, and so we

0:23:58.960 --> 0:24:01.480
<v Speaker 2>headed to an urgent care that Margo we can call her.

0:24:01.560 --> 0:24:04.479
<v Speaker 2>Margo knew about and she was adamant that she'd been

0:24:04.480 --> 0:24:06.680
<v Speaker 2>there many times before. So I Google mapped the address.

0:24:07.040 --> 0:24:12.080
<v Speaker 2>Google Map says it's closed, closed, like permanently. She's like,

0:24:12.119 --> 0:24:14.240
<v Speaker 2>it's not closed. I was there recently. It's closed.

0:24:14.600 --> 0:24:16.280
<v Speaker 1>Are you gaining her trust? By this point is she

0:24:16.400 --> 0:24:17.280
<v Speaker 1>likes sign to know?

0:24:18.119 --> 0:24:20.760
<v Speaker 2>And then I'm like, all right, I'm gonna call an

0:24:20.840 --> 0:24:24.880
<v Speaker 2>uber to go to another urgent character CityMD. She insists

0:24:24.880 --> 0:24:27.359
<v Speaker 2>on paying for the uber. I said, you can't play

0:24:27.400 --> 0:24:30.760
<v Speaker 2>for the uber. It doesn't work that way. We get

0:24:30.760 --> 0:24:36.720
<v Speaker 2>to CityMD. I see it that freaking iPad that they

0:24:36.760 --> 0:24:40.040
<v Speaker 2>want to use to scan her ID. I'm like, no,

0:24:40.359 --> 0:24:44.080
<v Speaker 2>we're not using an iPad. We're using paper. Then, And

0:24:44.080 --> 0:24:45.639
<v Speaker 2>this is my favorite part of the story because it's

0:24:45.680 --> 0:24:49.600
<v Speaker 2>kind of sweet. She has this like lightning thought where

0:24:49.600 --> 0:24:52.199
<v Speaker 2>she's like, oh, my cat has a vet appointment today

0:24:52.240 --> 0:24:55.200
<v Speaker 2>in the afternoon. I said, okay, I'll use Google and

0:24:55.240 --> 0:24:57.199
<v Speaker 2>I'll look up what animal hospital you go to in

0:24:57.200 --> 0:24:58.800
<v Speaker 2>the phone number. She goes, you can do that. I said, yeah,

0:25:00.520 --> 0:25:03.200
<v Speaker 2>all right, So I call the vet and I'm thinking

0:25:03.200 --> 0:25:05.440
<v Speaker 2>to myself, well, when you go to the vet, they

0:25:05.480 --> 0:25:08.000
<v Speaker 2>have everybody listed by the animal name, not the parent name.

0:25:08.440 --> 0:25:11.560
<v Speaker 2>So I turned to her and I say, Margot, what's

0:25:11.560 --> 0:25:18.119
<v Speaker 2>your cat's name? And dead stare Puss and I'm like, okay,

0:25:18.160 --> 0:25:22.880
<v Speaker 2>here we go. I said, my friend's cat, Puss, has

0:25:22.880 --> 0:25:27.399
<v Speaker 2>an appointment today and we're gonna need to cancel because

0:25:27.760 --> 0:25:31.400
<v Speaker 2>Puss's mother has been in an accent. She's okay, thank

0:25:31.440 --> 0:25:35.000
<v Speaker 2>you so much for telling us. Okay. Then the last

0:25:35.040 --> 0:25:38.000
<v Speaker 2>point of sort of technological contact was when we ended

0:25:38.080 --> 0:25:40.040
<v Speaker 2>up in the er where she had to go after

0:25:40.080 --> 0:25:43.600
<v Speaker 2>CityMD because she was having trouble breathing, and they said,

0:25:43.600 --> 0:25:47.360
<v Speaker 2>you need a chest X ray and I told her

0:25:47.640 --> 0:25:50.280
<v Speaker 2>I can't stay here for four hours, but I'll come

0:25:50.320 --> 0:25:54.040
<v Speaker 2>pick you up and take you home when you are

0:25:54.080 --> 0:25:59.480
<v Speaker 2>ready to leave. How well you have an iPhone? It

0:25:59.520 --> 0:26:01.720
<v Speaker 2>was off. I never seen an iPhone off. It was

0:26:01.840 --> 0:26:05.520
<v Speaker 2>fully off. I said, you know this nurse here who

0:26:05.560 --> 0:26:09.119
<v Speaker 2>is about my age, will help you call me. And

0:26:10.520 --> 0:26:15.520
<v Speaker 2>I think each touch point here made me reflect upon

0:26:17.119 --> 0:26:23.359
<v Speaker 2>how easy it was for me to navigate, and not

0:26:23.520 --> 0:26:26.760
<v Speaker 2>that she is well. She's certainly more intelligent than I

0:26:26.840 --> 0:26:30.480
<v Speaker 2>am intellectually speaking, but that there is a digital divide

0:26:30.520 --> 0:26:35.200
<v Speaker 2>between us that made this experience far less harrowing. Because

0:26:35.200 --> 0:26:37.560
<v Speaker 2>I was with her and she said as much. I

0:26:37.680 --> 0:26:41.320
<v Speaker 2>think she realized very early on that, like all of

0:26:41.400 --> 0:26:44.600
<v Speaker 2>those things that I think that are so second nature

0:26:44.760 --> 0:26:51.000
<v Speaker 2>to me, we're not even like on Margo's radar as possibilities.

0:26:52.200 --> 0:26:56.719
<v Speaker 1>I mean, this story raises the perfect question, almost as

0:26:56.760 --> 0:26:59.720
<v Speaker 1>though we planned it. When did this become a thing?

0:27:00.440 --> 0:27:03.000
<v Speaker 1>When did the world sort of cleave into two where

0:27:03.440 --> 0:27:07.800
<v Speaker 1>you're either totally able to navigate everything because of having

0:27:07.880 --> 0:27:12.000
<v Speaker 1>a tool which makes it easy, or you're just kind

0:27:12.000 --> 0:27:15.480
<v Speaker 1>of struggling to translate. In other words, when did digital

0:27:15.600 --> 0:27:19.200
<v Speaker 1>natives become a thing. Yes, but let's start by defining

0:27:19.240 --> 0:27:20.679
<v Speaker 1>our terms, which always a good thing to do at

0:27:20.680 --> 0:27:23.720
<v Speaker 1>the beginning. What is a digital native?

0:27:24.359 --> 0:27:26.440
<v Speaker 2>You know, I actually have no idea, but I've always

0:27:26.520 --> 0:27:30.720
<v Speaker 2>considered myself a digital native. I'm a New Yorker first,

0:27:30.920 --> 0:27:32.760
<v Speaker 2>but I'm definitely a digital native second.

0:27:33.200 --> 0:27:36.399
<v Speaker 1>I also always consider myself a digital native, even if

0:27:36.560 --> 0:27:40.280
<v Speaker 1>somewhat reluctantly. Weirdly, because as a child, I was diagnosed

0:27:40.320 --> 0:27:43.440
<v Speaker 1>with dyspraxia, which basically means can't catch a ball, can't

0:27:43.600 --> 0:27:44.600
<v Speaker 1>do nice handwriting.

0:27:44.880 --> 0:27:46.600
<v Speaker 2>You haven't really grown out of that, No, I haven't

0:27:46.640 --> 0:27:47.240
<v Speaker 2>tell you. I haven't.

0:27:47.240 --> 0:27:50.879
<v Speaker 1>But I got my prescription was a laptop, like aged

0:27:50.920 --> 0:27:53.000
<v Speaker 1>eight years old, to do my homework on and stuff,

0:27:53.000 --> 0:27:57.200
<v Speaker 1>and so I became a digital native basically in the

0:27:57.280 --> 0:27:57.880
<v Speaker 1>late nineties.

0:27:58.640 --> 0:28:00.920
<v Speaker 2>You know, I did not know this about you, And

0:28:01.040 --> 0:28:03.880
<v Speaker 2>this might be one of our sort of unspoken personal

0:28:03.960 --> 0:28:07.080
<v Speaker 2>connections because I went to one of those kooky laptop

0:28:07.160 --> 0:28:09.080
<v Speaker 2>schools that I think has ultimately netted out to be

0:28:09.119 --> 0:28:12.160
<v Speaker 2>the wrong idea. But I went to one of those

0:28:12.160 --> 0:28:15.000
<v Speaker 2>schools where they taught us C plus plus before they

0:28:15.040 --> 0:28:16.080
<v Speaker 2>taught us basic algebra.

0:28:16.560 --> 0:28:19.159
<v Speaker 1>So we both had this feeling of being digital natives.

0:28:19.240 --> 0:28:21.800
<v Speaker 1>But I thought I would do some research on what

0:28:22.000 --> 0:28:25.119
<v Speaker 1>that term actually means and where it comes from. Turns

0:28:25.160 --> 0:28:27.880
<v Speaker 1>out it was coined in the year two thousand and one,

0:28:28.000 --> 0:28:30.520
<v Speaker 1>around the same time we both got our laptops by

0:28:30.640 --> 0:28:34.560
<v Speaker 1>an educational consultant called Mark Prinsky, and he had this

0:28:34.720 --> 0:28:37.920
<v Speaker 1>idea that education needed to change in response to young

0:28:37.960 --> 0:28:41.880
<v Speaker 1>people whose brains were literally different from the brains of

0:28:41.880 --> 0:28:45.200
<v Speaker 1>the generation before because they'd already been shaped by gaming

0:28:45.440 --> 0:28:48.160
<v Speaker 1>and spending time online and being more used to finding

0:28:48.240 --> 0:28:51.000
<v Speaker 1>information on the web than, for example, in a book.

0:28:51.480 --> 0:28:54.680
<v Speaker 1>And he had this quite powerful quote, which was today's

0:28:54.680 --> 0:28:58.000
<v Speaker 1>students have not just changed incrementally from those of the past,

0:28:58.440 --> 0:29:03.000
<v Speaker 1>nor simply changed their slang, clothed, body adornments, or styles,

0:29:03.240 --> 0:29:06.640
<v Speaker 1>as has happened between generations previously, but a really big

0:29:06.720 --> 0:29:11.560
<v Speaker 1>discontinuity has taken place. One might even call it a singularity,

0:29:12.120 --> 0:29:14.840
<v Speaker 1>an event which changes things so fundamentally that there is

0:29:14.880 --> 0:29:16.560
<v Speaker 1>absolutely no going back.

0:29:17.320 --> 0:29:20.120
<v Speaker 2>Wouldn't you say, that's like the fact that I now

0:29:20.240 --> 0:29:22.000
<v Speaker 2>say google it, then look it up.

0:29:22.240 --> 0:29:23.200
<v Speaker 1>That's the singularity.

0:29:23.440 --> 0:29:26.840
<v Speaker 2>Right. When you talk to some people who are older,

0:29:27.760 --> 0:29:31.560
<v Speaker 2>they'll say, call for one one, where's four one one going.

0:29:31.480 --> 0:29:33.160
<v Speaker 1>To get me? And it's interesting, you just made that

0:29:33.280 --> 0:29:35.959
<v Speaker 1>point about calling four one one. Prince Ki also has

0:29:36.000 --> 0:29:41.040
<v Speaker 1>this concept of digital natives versus digital immigrants and digital immigrants,

0:29:41.080 --> 0:29:44.160
<v Speaker 1>of people like Margo who kind of live in the

0:29:44.400 --> 0:29:48.040
<v Speaker 1>digital world but carry the accent of where they come from.

0:29:48.240 --> 0:29:50.720
<v Speaker 1>Whether it's like printing out an email is one of

0:29:50.760 --> 0:29:53.720
<v Speaker 1>the examples that Prince Key uses, or kind of beckoning

0:29:53.800 --> 0:29:56.080
<v Speaker 1>someone over to look at your computer screen rather than

0:29:56.120 --> 0:29:56.840
<v Speaker 1>sending them a link.

0:29:57.480 --> 0:30:00.920
<v Speaker 2>And you know, I think that there are definitely those

0:30:01.000 --> 0:30:04.800
<v Speaker 2>things that mark people today as digital immigrants. You know,

0:30:04.880 --> 0:30:08.600
<v Speaker 2>I think, my poor mother, but you know, sometimes she'll say, oh,

0:30:08.720 --> 0:30:16.400
<v Speaker 2>you know, let's call for takeout. What nobody's home. There's

0:30:16.400 --> 0:30:19.360
<v Speaker 2>actually this book called the Victorian Internet, which is by

0:30:19.480 --> 0:30:21.960
<v Speaker 2>Tom's Standage, and it's all about the history of the

0:30:22.040 --> 0:30:25.120
<v Speaker 2>development of the telegraph and how it parallels to the Internet.

0:30:25.160 --> 0:30:27.680
<v Speaker 2>And in it he tells the story from when the

0:30:27.760 --> 0:30:31.920
<v Speaker 2>telegraph was first introduced around the time of the American

0:30:32.000 --> 0:30:34.640
<v Speaker 2>Civil War. And I mean, this could have been my mom.

0:30:34.920 --> 0:30:37.800
<v Speaker 2>A mom goes to the telegraph office with a bowl

0:30:37.880 --> 0:30:41.880
<v Speaker 2>of sour kraut to send her son to the battlefront,

0:30:41.920 --> 0:30:42.800
<v Speaker 2>you know, like by wire.

0:30:43.200 --> 0:30:46.440
<v Speaker 1>So she really was a digital immigrant, bringing a native

0:30:46.520 --> 0:30:48.600
<v Speaker 1>cuisine and then trying to send day with a telegraph.

0:30:48.680 --> 0:30:50.240
<v Speaker 2>That's correct. And you know, back in the time of

0:30:50.280 --> 0:30:54.120
<v Speaker 2>the Civil War, change felt fast. It did not feel

0:30:54.160 --> 0:30:56.440
<v Speaker 2>as fast as it feels now. Where you know, by

0:30:56.480 --> 0:30:58.200
<v Speaker 2>the time you have a software update, you need to

0:30:58.280 --> 0:31:01.040
<v Speaker 2>like learn how to use a whole new phone. You

0:31:01.120 --> 0:31:05.160
<v Speaker 2>could blink and miss an entire technological evolution. And I

0:31:05.280 --> 0:31:07.800
<v Speaker 2>do blink and miss entire things sometimes.

0:31:07.520 --> 0:31:09.480
<v Speaker 1>Well, I know you think of yourself as a digital

0:31:09.600 --> 0:31:12.600
<v Speaker 1>native since you grew up with tech. Do you still

0:31:13.720 --> 0:31:15.080
<v Speaker 1>you know, I do in.

0:31:15.160 --> 0:31:18.840
<v Speaker 2>The sense of the idea of new technology is not

0:31:19.160 --> 0:31:20.440
<v Speaker 2>incredibly daunting to me.

0:31:20.760 --> 0:31:21.880
<v Speaker 1>I think it was subtractive to you.

0:31:22.120 --> 0:31:24.200
<v Speaker 2>Yes, And I think we were born at a time

0:31:24.680 --> 0:31:28.680
<v Speaker 2>when technology was changing so rapidly that we are not

0:31:28.920 --> 0:31:32.360
<v Speaker 2>completely thrown by the idea of like the facts not

0:31:32.520 --> 0:31:35.880
<v Speaker 2>being the predominant form of communication for ten years, right, right.

0:31:36.040 --> 0:31:39.720
<v Speaker 1>But do you think if you kind of got given

0:31:40.040 --> 0:31:42.280
<v Speaker 1>a grand tour of downtown New York by an eighteen

0:31:42.360 --> 0:31:45.440
<v Speaker 1>year old, they will be surprised by your use of technology?

0:31:45.880 --> 0:31:49.920
<v Speaker 2>I think it's more if like I spent five days

0:31:49.960 --> 0:31:52.239
<v Speaker 2>with an eighteen year old, they'd be like, why are

0:31:52.280 --> 0:31:55.440
<v Speaker 2>you not charting your every move on Snapchat? Which is

0:31:55.520 --> 0:31:57.200
<v Speaker 2>not to say that like I couldn't live in the

0:31:57.280 --> 0:31:59.960
<v Speaker 2>world with them, but they live in the world different.

0:32:00.280 --> 0:32:03.680
<v Speaker 1>Yeah, truly, we're living Margo's living in more or less

0:32:03.680 --> 0:32:06.400
<v Speaker 1>an analog world. We're probably living in a hybrid world.

0:32:06.600 --> 0:32:09.040
<v Speaker 1>And many the younger people are living in a fully

0:32:09.560 --> 0:32:10.280
<v Speaker 1>digital world.

0:32:10.680 --> 0:32:13.040
<v Speaker 2>Well, and that's the irony of connectivity, I think, right,

0:32:13.160 --> 0:32:15.360
<v Speaker 2>Which is this idea that like the world is actually

0:32:15.440 --> 0:32:18.480
<v Speaker 2>quite siloed by like how you use technology. If you

0:32:18.640 --> 0:32:20.680
<v Speaker 2>use it properly, you can be very connected, but it

0:32:20.720 --> 0:32:22.640
<v Speaker 2>can also be very isolating totally.

0:32:23.000 --> 0:32:25.440
<v Speaker 1>And we should point out that the framing of native

0:32:25.560 --> 0:32:27.840
<v Speaker 1>versus immigrant is rather loaded.

0:32:28.280 --> 0:32:31.720
<v Speaker 2>Yeah, And one of the things that really struck me

0:32:32.560 --> 0:32:35.200
<v Speaker 2>with what Margo experience was that there was friction at

0:32:35.440 --> 0:32:40.960
<v Speaker 2>every turn in her accident. And that's just not only

0:32:41.040 --> 0:32:44.840
<v Speaker 2>because she was in an accident. It's because we are

0:32:45.000 --> 0:32:49.480
<v Speaker 2>constantly encountering, like almost every day, a more and more

0:32:49.960 --> 0:32:54.240
<v Speaker 2>digitized world, right. And you know, the thought that I'm

0:32:54.360 --> 0:32:59.200
<v Speaker 2>left with is that even though there is a definition

0:32:59.320 --> 0:33:02.880
<v Speaker 2>for digital needs and we fit into that definition, it's

0:33:02.920 --> 0:33:03.760
<v Speaker 2>not a permanent state.

0:33:04.560 --> 0:33:07.560
<v Speaker 1>I do wonder if there will emerge another term, something

0:33:07.640 --> 0:33:12.040
<v Speaker 1>to supplant digital natives the way postmoderns are planted modern.

0:33:12.560 --> 0:33:14.360
<v Speaker 1>You know, one of the guests that we were most

0:33:14.400 --> 0:33:17.880
<v Speaker 1>excited and proudest to have on Sleepwalkers, our former podcast,

0:33:18.360 --> 0:33:21.760
<v Speaker 1>was uv Al Noah Harari, who wrote a book called Homodeus,

0:33:22.080 --> 0:33:27.000
<v Speaker 1>which is basically all about how using technology and merging

0:33:27.040 --> 0:33:31.840
<v Speaker 1>with technology was changing Homo sapiens into almost this new

0:33:31.960 --> 0:33:36.600
<v Speaker 1>species Homodeus human but with these godlike powers enabled by

0:33:36.720 --> 0:33:41.120
<v Speaker 1>new technology. I found it as a young pre teenager

0:33:41.560 --> 0:33:44.640
<v Speaker 1>pretty crazy getting a laptop in the early two thousands,

0:33:44.680 --> 0:33:48.160
<v Speaker 1>which was theoretically to do my homework because I was dyspraxic,

0:33:48.280 --> 0:33:52.680
<v Speaker 1>but more realistically to play the Oregon Trail and Cassel Wolfenstein.

0:33:54.320 --> 0:33:56.320
<v Speaker 1>And I remember sort of having this laptop and other

0:33:56.400 --> 0:33:58.800
<v Speaker 1>kids didn't, and it was sort of this little It

0:33:58.880 --> 0:34:01.160
<v Speaker 1>didn't change too much, but it was a kind of

0:34:01.280 --> 0:34:03.360
<v Speaker 1>moment of like I was ahead of the curve in

0:34:03.440 --> 0:34:06.600
<v Speaker 1>some way. But imagine going to school now as a

0:34:06.720 --> 0:34:09.399
<v Speaker 1>nine year old in the age of chech GPT three.

0:34:09.920 --> 0:34:13.200
<v Speaker 1>What does that experience of having not only the whole

0:34:13.239 --> 0:34:17.279
<v Speaker 1>world's information at your fingertips for a search, but having

0:34:17.400 --> 0:34:20.000
<v Speaker 1>any answer which is probably better than the answer or

0:34:20.040 --> 0:34:22.920
<v Speaker 1>teacher or your parent can provide, at the click of

0:34:22.960 --> 0:34:26.160
<v Speaker 1>a button. What does that do to a developing brain.

0:34:34.480 --> 0:34:36.600
<v Speaker 1>That's it for this week on Tech Stuff. I'm Oz

0:34:36.640 --> 0:34:38.440
<v Speaker 1>Valoshin and I'm Kara Price.

0:34:38.960 --> 0:34:42.440
<v Speaker 2>This episode was produced by Eliza Dennis, Victoria Domingez, and

0:34:42.520 --> 0:34:46.600
<v Speaker 2>Lizzie Jacobs. It was executive produced by me, Kara Price, Ozwalashan,

0:34:46.840 --> 0:34:51.000
<v Speaker 2>and Kate Osbourne for Kaleidoscope and Katrina Norvel for iHeart Podcasts.

0:34:51.400 --> 0:34:54.800
<v Speaker 2>The engineer is Charles Demontebello and it's mixed by Kyle Murdoch,

0:34:54.880 --> 0:34:56.120
<v Speaker 2>who also wrote our theme song.

0:34:56.920 --> 0:35:00.319
<v Speaker 1>Join us next Wednesday for tech Stuff The Story, when

0:35:00.360 --> 0:35:04.280
<v Speaker 1>we'll share an in depth conversation with Jessica Lesson, CEO

0:35:04.440 --> 0:35:07.800
<v Speaker 1>of the information about a vibe shift in Silicon Valley.

0:35:08.400 --> 0:35:11.279
<v Speaker 2>Please rate, review, and reach out to us at tech

0:35:11.360 --> 0:35:14.799
<v Speaker 2>Stuff podcast at gmail dot com. We want to hear

0:35:14.840 --> 0:35:15.080
<v Speaker 2>from you