WEBVTT - Tech News: ChatGPT Lands Lawyer in Legal Trouble

0:00:04.440 --> 0:00:12.399
<v Speaker 1>Welcome to Tech Stuff, a production from iHeartRadio. Hey therein

0:00:12.560 --> 0:00:16.320
<v Speaker 1>Welcome to Tech Stuff. I'm your host Jonathan Strickland. I'm

0:00:16.360 --> 0:00:19.880
<v Speaker 1>an executive producer with iHeartRadio. And how the tech are you?

0:00:20.239 --> 0:00:23.360
<v Speaker 1>It's time for the tech news for Tuesday, May thirty,

0:00:23.920 --> 0:00:29.520
<v Speaker 1>twenty twenty three. Nvidia CEO Jensen Wang spoke at the

0:00:29.680 --> 0:00:34.440
<v Speaker 1>Computech's forum in Taiwan yesterday and said something that I'm

0:00:34.479 --> 0:00:38.239
<v Speaker 1>sure has a lot of programmers anxious. Huang said that

0:00:38.560 --> 0:00:43.040
<v Speaker 1>due to how quickly generative AI evolves, we're entering into

0:00:43.040 --> 0:00:46.720
<v Speaker 1>an era in which essentially anyone can be a programmer.

0:00:47.200 --> 0:00:50.080
<v Speaker 1>It won't require you to have studied computer languages or

0:00:50.120 --> 0:00:53.600
<v Speaker 1>even computer science. All it will take is a sufficiently

0:00:53.640 --> 0:00:57.760
<v Speaker 1>sophisticated AI model to take your prompts and then turn

0:00:57.840 --> 0:01:02.160
<v Speaker 1>that into a well designed program. Wang unveiled a platform

0:01:02.240 --> 0:01:09.040
<v Speaker 1>called the DGXGH two hundred, essentially a supercomputing pro platform.

0:01:09.440 --> 0:01:12.959
<v Speaker 1>It's designed to help build the next generation of generative

0:01:13.000 --> 0:01:18.080
<v Speaker 1>AI models. This actually reminds me of the fictional supercomputer

0:01:18.480 --> 0:01:21.840
<v Speaker 1>Deep Thought in The Hitchhiker's Guide to the Galaxy books,

0:01:22.280 --> 0:01:26.039
<v Speaker 1>which explained that it was not sufficiently powerful enough to

0:01:26.080 --> 0:01:29.760
<v Speaker 1>provide the question to life, the universe and everything. It

0:01:29.800 --> 0:01:32.880
<v Speaker 1>gave us the answer, but not the question. However, it

0:01:33.040 --> 0:01:37.480
<v Speaker 1>was powerful enough to build a computer that could do that.

0:01:37.480 --> 0:01:39.680
<v Speaker 1>That seems to be what this is indicating. It's a

0:01:39.720 --> 0:01:45.040
<v Speaker 1>supercomputer meant to build better AI. Anyway, Wang's keynote seemed

0:01:45.040 --> 0:01:47.440
<v Speaker 1>to indicate that not too long from now, you won't

0:01:47.440 --> 0:01:50.640
<v Speaker 1>need a background in programming in order to be a programmer,

0:01:50.720 --> 0:01:53.600
<v Speaker 1>or at least that's how the articles covering his keynote

0:01:53.680 --> 0:01:57.120
<v Speaker 1>seemed to frame it. I'd like to think that generative

0:01:57.120 --> 0:02:00.880
<v Speaker 1>AI will help programmers and help them be more productive

0:02:00.880 --> 0:02:04.160
<v Speaker 1>and more efficient, and that AI will give them the

0:02:04.240 --> 0:02:08.440
<v Speaker 1>tools to build code that contains fewer errors, or to

0:02:08.680 --> 0:02:12.640
<v Speaker 1>check for mistakes as they're coding that kind of thing. So,

0:02:12.680 --> 0:02:15.040
<v Speaker 1>in other words, my hope is that this isn't a

0:02:15.080 --> 0:02:20.320
<v Speaker 1>step toward invalidating an entire career path or and this

0:02:20.480 --> 0:02:23.320
<v Speaker 1>is really the cynical part of me. I hope it's

0:02:23.360 --> 0:02:28.640
<v Speaker 1>not an attempt to justify hiring relatively unskilled employees at

0:02:28.680 --> 0:02:31.280
<v Speaker 1>a much lower salary than what it would cost to

0:02:31.320 --> 0:02:35.880
<v Speaker 1>bring on a qualified programmer. Right. That's the fear is

0:02:35.919 --> 0:02:40.800
<v Speaker 1>that if you've dedicated your time and energy. You pursued

0:02:40.840 --> 0:02:45.919
<v Speaker 1>an education in computer science and computer programming, and you've

0:02:45.960 --> 0:02:49.640
<v Speaker 1>built the skill set that would normally guarantee you a

0:02:49.760 --> 0:02:53.119
<v Speaker 1>chance of landing a lucrative career in the field you love,

0:02:53.639 --> 0:02:56.040
<v Speaker 1>and then you find out, oh, no, you're overqualified. We

0:02:56.120 --> 0:02:57.920
<v Speaker 1>just need someone who can talk to this computer and

0:02:57.960 --> 0:03:02.200
<v Speaker 1>make the thing that we want. It's not good. So

0:03:03.360 --> 0:03:06.079
<v Speaker 1>my hope is that a lot of the news that

0:03:06.320 --> 0:03:11.360
<v Speaker 1>covered this was doing so in a way that was

0:03:11.520 --> 0:03:14.960
<v Speaker 1>perhaps not reflective of what Wang was actually saying. I

0:03:15.000 --> 0:03:17.400
<v Speaker 1>say that because I didn't get a chance to actually

0:03:17.440 --> 0:03:21.200
<v Speaker 1>watch his keynote, so I'm not certain how he worded it.

0:03:21.240 --> 0:03:24.040
<v Speaker 1>I can only react to the way it's been reported.

0:03:24.880 --> 0:03:28.280
<v Speaker 1>Reuter's reports that deep Media, which is a company that

0:03:28.320 --> 0:03:31.720
<v Speaker 1>works to identify and track the proliferation of deep fake

0:03:31.840 --> 0:03:36.320
<v Speaker 1>videos and other deep fake content online, has indicated that

0:03:36.360 --> 0:03:39.400
<v Speaker 1>there's been a pretty significant jump in the number of

0:03:39.440 --> 0:03:43.040
<v Speaker 1>instances of deep fakes this past year. So, according to

0:03:43.040 --> 0:03:46.360
<v Speaker 1>deep Media, there are three times as many deep fake

0:03:46.480 --> 0:03:50.640
<v Speaker 1>videos circulating this year as there were in the same

0:03:50.760 --> 0:03:53.600
<v Speaker 1>span of time back in twenty twenty two, and there

0:03:53.640 --> 0:03:58.520
<v Speaker 1>are eight times as many deep fake voice recordings and

0:03:58.600 --> 0:04:03.040
<v Speaker 1>deep fake voice examples. I'm not sure how many examples

0:04:03.080 --> 0:04:05.960
<v Speaker 1>we're talking about with that, because keep in mind, this

0:04:06.000 --> 0:04:09.480
<v Speaker 1>all depends on how many were circulating in twenty twenty two.

0:04:09.640 --> 0:04:12.560
<v Speaker 1>They just said it's eight times as many. So if

0:04:12.600 --> 0:04:15.240
<v Speaker 1>only one deep fake voice recording had popped up in

0:04:15.240 --> 0:04:17.479
<v Speaker 1>twenty twenty two, that would just mean that there were

0:04:17.560 --> 0:04:20.400
<v Speaker 1>eight that popped up this year, So the details matter.

0:04:20.520 --> 0:04:23.680
<v Speaker 1>This is also, by the way, when you hear about

0:04:23.960 --> 0:04:27.799
<v Speaker 1>really the growth of any business, but specifically within technology,

0:04:27.839 --> 0:04:31.120
<v Speaker 1>when you hear the growth is being expressed in percentages,

0:04:31.640 --> 0:04:33.120
<v Speaker 1>you really need to say, all right, but what are

0:04:33.120 --> 0:04:36.320
<v Speaker 1>the actual numbers, because if the actual numbers are very low,

0:04:36.760 --> 0:04:39.800
<v Speaker 1>a huge percentage in growth still can mean a pretty

0:04:39.839 --> 0:04:44.880
<v Speaker 1>low number, right, That's important anyway. Deep Media estimates that

0:04:45.360 --> 0:04:48.080
<v Speaker 1>by the end of this year, there will be around

0:04:48.160 --> 0:04:51.320
<v Speaker 1>half a million deep fake videos and voice recordings that

0:04:51.360 --> 0:04:56.080
<v Speaker 1>will be shared across social media, and as you probably suspect,

0:04:56.120 --> 0:04:59.440
<v Speaker 1>a lot of those will likely center around politics and

0:04:59.480 --> 0:05:03.960
<v Speaker 1>misinform As the deep fake generators become more sophisticated, it

0:05:04.000 --> 0:05:06.800
<v Speaker 1>can be a challenge for a normal human type person

0:05:07.320 --> 0:05:10.480
<v Speaker 1>to tell the difference between real videos and deep fake videos.

0:05:10.880 --> 0:05:14.200
<v Speaker 1>There are often indicators that you might be able to

0:05:14.240 --> 0:05:16.040
<v Speaker 1>tell if you're looking on a large enough screen and

0:05:16.080 --> 0:05:18.600
<v Speaker 1>a high enough resolution, but if you're like watching little

0:05:18.640 --> 0:05:22.520
<v Speaker 1>videos on your phone, you might not notice. There are

0:05:22.640 --> 0:05:26.960
<v Speaker 1>detection tools that are more effective for spotting really good

0:05:27.040 --> 0:05:30.159
<v Speaker 1>deep fakes out there, but you can imagine the damage

0:05:30.200 --> 0:05:34.560
<v Speaker 1>that can be done with this type of technology, particularly

0:05:34.600 --> 0:05:40.440
<v Speaker 1>for people who are already predisposed to believe certain ideologies.

0:05:40.960 --> 0:05:44.200
<v Speaker 1>If there's a video that seems to reinforce that ideology,

0:05:44.200 --> 0:05:48.240
<v Speaker 1>they may not take the time to question the authenticity

0:05:48.680 --> 0:05:52.279
<v Speaker 1>of that video. Various companies in the generative AI space

0:05:52.360 --> 0:05:56.000
<v Speaker 1>have been working on different approaches to mitigate this issue

0:05:56.040 --> 0:05:59.880
<v Speaker 1>to prevent the misuse of the technology, but these are

0:06:00.320 --> 0:06:04.160
<v Speaker 1>are nowhere close to being comprehensive or fully effective. Already,

0:06:04.200 --> 0:06:06.200
<v Speaker 1>there have been a few cases in which folks in

0:06:06.240 --> 0:06:09.400
<v Speaker 1>the political sphere I shall not name names, but some

0:06:09.880 --> 0:06:14.360
<v Speaker 1>prominent people in politics have shared deep fake videos, sometimes

0:06:14.400 --> 0:06:17.120
<v Speaker 1>with like a half hearted disclaimer of something along the

0:06:17.120 --> 0:06:19.240
<v Speaker 1>lines of, I don't know if this is real or not,

0:06:19.880 --> 0:06:22.720
<v Speaker 1>so just a side note. If you don't know if

0:06:22.720 --> 0:06:26.720
<v Speaker 1>it's real, just don't share it. But you know, no,

0:06:26.800 --> 0:06:28.840
<v Speaker 1>I get it. You know. The folks who share this

0:06:28.920 --> 0:06:31.839
<v Speaker 1>kind of stuff typically they don't really care if it's

0:06:31.880 --> 0:06:34.680
<v Speaker 1>real or not. They're just looking for the effect. I mean,

0:06:34.720 --> 0:06:37.800
<v Speaker 1>if it's real, it's better, but it doesn't really matter

0:06:37.839 --> 0:06:41.480
<v Speaker 1>because they're just looking to stir up a group of people,

0:06:42.000 --> 0:06:44.240
<v Speaker 1>so it doesn't really matter if it's real. All I

0:06:44.279 --> 0:06:47.320
<v Speaker 1>can say is that the use of critical thinking is

0:06:47.360 --> 0:06:52.640
<v Speaker 1>more important than ever, that employing critical thinking also takes work.

0:06:52.800 --> 0:06:56.640
<v Speaker 1>You have to be actively working and engage in critical thinking.

0:06:56.680 --> 0:07:00.000
<v Speaker 1>You can't just, you know, lean back and rely on

0:07:00.040 --> 0:07:02.600
<v Speaker 1>upon it to kick in. Because goodness knows, I've been

0:07:02.600 --> 0:07:04.960
<v Speaker 1>guilty of being too lazy to use it in the past.

0:07:05.600 --> 0:07:08.160
<v Speaker 1>It's happened to me. I talk about critical thinking all

0:07:08.200 --> 0:07:11.040
<v Speaker 1>the time, but I'm also guilty of not employing it

0:07:11.080 --> 0:07:13.720
<v Speaker 1>on occasion. I have to think about it, I have

0:07:13.760 --> 0:07:16.400
<v Speaker 1>to actively do it, and we all need to try

0:07:16.440 --> 0:07:19.920
<v Speaker 1>harder because it's getting tricky to tell the difference between

0:07:19.960 --> 0:07:22.600
<v Speaker 1>fact and fiction. There are a lot of tools out

0:07:22.640 --> 0:07:25.520
<v Speaker 1>there and a lot of bad actors out there that

0:07:25.680 --> 0:07:31.160
<v Speaker 1>collectively can start to push false narratives and to trick us.

0:07:31.600 --> 0:07:34.480
<v Speaker 1>And it's across the spectrum. It's not like it's just

0:07:34.600 --> 0:07:37.840
<v Speaker 1>one group doing this. There are lots of different people

0:07:37.920 --> 0:07:42.120
<v Speaker 1>with different motivations doing the same sort of stuff, and

0:07:42.160 --> 0:07:44.560
<v Speaker 1>we have to be on the lookout for it. And

0:07:44.600 --> 0:07:48.680
<v Speaker 1>now for a piece about the consequences of relying on

0:07:48.840 --> 0:07:54.200
<v Speaker 1>generative AI. So, a lawyer named Stephen Schwartz apparently used

0:07:54.280 --> 0:07:57.640
<v Speaker 1>chat GPT while doing some legal research on a case

0:07:57.680 --> 0:08:02.240
<v Speaker 1>that he was working. Chat GPT provided some background research

0:08:02.360 --> 0:08:06.920
<v Speaker 1>that Schwartz apparently then used in filing this case. But

0:08:07.000 --> 0:08:11.720
<v Speaker 1>there was a truly huge problem. Chat GPT cited other

0:08:12.000 --> 0:08:16.440
<v Speaker 1>legal cases in order to provide support for Schwartz's legal argument,

0:08:17.040 --> 0:08:22.760
<v Speaker 1>except those cases weren't real. They had never happened. Chat

0:08:22.800 --> 0:08:25.880
<v Speaker 1>GPT created, or, if you want to use the parlance

0:08:25.960 --> 0:08:30.920
<v Speaker 1>of the AI times, it hallucinated these cases. And I've

0:08:30.920 --> 0:08:34.400
<v Speaker 1>talked about AI hallucinations not too long ago on this

0:08:34.640 --> 0:08:38.560
<v Speaker 1>very show. You how generative AI models are essentially using

0:08:38.600 --> 0:08:43.679
<v Speaker 1>a complicated statistical model to generate responses. And this model

0:08:43.760 --> 0:08:47.280
<v Speaker 1>draws on a lot of archived information, but sometimes it

0:08:47.480 --> 0:08:52.160
<v Speaker 1>just invents stuff and essentially is saying what word would

0:08:52.200 --> 0:08:56.240
<v Speaker 1>most likely follow this word. Then you get a response

0:08:56.280 --> 0:09:00.240
<v Speaker 1>that sounds perfectly cromulent, as the Simpsons would say, but

0:09:00.559 --> 0:09:05.680
<v Speaker 1>is in fact hogwash or gibber jabber, or balderdash or

0:09:05.760 --> 0:09:09.040
<v Speaker 1>just plain fake. And as you might imagine, presenting fake

0:09:09.200 --> 0:09:12.200
<v Speaker 1>court cases as if they are a legitimate precedent to

0:09:12.240 --> 0:09:15.959
<v Speaker 1>your own case is not looked upon kindly by the court.

0:09:16.600 --> 0:09:19.920
<v Speaker 1>If you claim a precedent, then you should expect the

0:09:19.960 --> 0:09:22.560
<v Speaker 1>court to look into the precedent to make sure that

0:09:22.600 --> 0:09:25.600
<v Speaker 1>what you're saying is accurate. And when the court did

0:09:25.920 --> 0:09:29.480
<v Speaker 1>do that, when they double checked Schwartz's filings, they found

0:09:29.480 --> 0:09:34.000
<v Speaker 1>that the numerous cases Schwartz presented as suggested by chat

0:09:34.040 --> 0:09:39.040
<v Speaker 1>GPT didn't actually exist. And when pressed, Schwartz said he

0:09:39.080 --> 0:09:42.720
<v Speaker 1>was not aware that chat GPT could just invent stuff.

0:09:42.920 --> 0:09:47.320
<v Speaker 1>He assumed that everything that chat GPT presented came from actual,

0:09:47.480 --> 0:09:52.000
<v Speaker 1>real information that had been stored somewhere. Now, the judge

0:09:52.040 --> 0:09:54.840
<v Speaker 1>has ordered a hearing a few weeks from now to

0:09:55.000 --> 0:10:02.440
<v Speaker 1>quote unquote discuss potential sanctions. Woof So. On the one hand, yeah, absolutely,

0:10:03.000 --> 0:10:06.400
<v Speaker 1>it would be unthinkable to let people submit fake evidence

0:10:06.440 --> 0:10:10.440
<v Speaker 1>to support their arguments and then receive no repercussions afterward.

0:10:10.960 --> 0:10:13.679
<v Speaker 1>On the other hand, I mean, the hype around chat

0:10:13.720 --> 0:10:17.640
<v Speaker 1>GPT and other generative AI models is absolutely painting an

0:10:17.679 --> 0:10:21.680
<v Speaker 1>inaccurate picture of what they can do. Though, honestly, it

0:10:21.720 --> 0:10:24.120
<v Speaker 1>really doesn't take that much work to find out that

0:10:24.160 --> 0:10:27.480
<v Speaker 1>these AI systems are flawed. It's just that I could

0:10:27.600 --> 0:10:32.920
<v Speaker 1>understand why someone would put too much stock in chat

0:10:32.960 --> 0:10:39.120
<v Speaker 1>GPT's performance because of the way it has been hyped. Again,

0:10:39.600 --> 0:10:42.600
<v Speaker 1>it really doesn't take that much work to find where

0:10:42.640 --> 0:10:46.280
<v Speaker 1>the problems are. So I can't give Schwartz a pass here.

0:10:46.320 --> 0:10:49.200
<v Speaker 1>I could just say I could understand why he would think, oh,

0:10:49.240 --> 0:10:50.839
<v Speaker 1>this is a valid tool for me to use, and

0:10:50.840 --> 0:10:53.240
<v Speaker 1>there shouldn't be any problems. I can kind of understand that.

0:10:53.800 --> 0:10:56.160
<v Speaker 1>But if he had taken even just a little bit

0:10:56.200 --> 0:11:00.320
<v Speaker 1>of effort, he would have seen that perhaps rely so

0:11:00.360 --> 0:11:03.640
<v Speaker 1>heavily on chat GPT, without you know, fact checking, it

0:11:03.679 --> 0:11:08.280
<v Speaker 1>would have been foolish. Okay, we've got a lot more

0:11:08.400 --> 0:11:10.720
<v Speaker 1>news to cover before we get to that. Let's take

0:11:10.880 --> 0:11:22.319
<v Speaker 1>a quick break. So we're back, and we've got another

0:11:22.360 --> 0:11:26.360
<v Speaker 1>open letter, actually just a short warning from various AI

0:11:26.480 --> 0:11:30.679
<v Speaker 1>experts about the potential dangers of AI. It is very short.

0:11:30.720 --> 0:11:32.959
<v Speaker 1>It is to the point I'll actually read the whole

0:11:33.000 --> 0:11:37.680
<v Speaker 1>thing because it isn't long. Quote. Mitigating the risk of

0:11:37.720 --> 0:11:41.760
<v Speaker 1>extinction from AI should be a global priority alongside other

0:11:41.840 --> 0:11:46.520
<v Speaker 1>societal scale risks such as pandemics and nuclear war end

0:11:46.600 --> 0:11:51.160
<v Speaker 1>quote that is it, that's the warning putting AI on

0:11:51.240 --> 0:11:54.440
<v Speaker 1>the same level as things like pandemics and nuclear war

0:11:54.559 --> 0:11:58.160
<v Speaker 1>as a potential threat to the human race. A lot

0:11:58.160 --> 0:12:02.440
<v Speaker 1>of high profile AI experts have already signed their names

0:12:02.480 --> 0:12:05.760
<v Speaker 1>to the statement. That includes Sam Altman, the CEO of

0:12:05.800 --> 0:12:09.120
<v Speaker 1>Open Ai, who's been sending some kind of mixed messages

0:12:09.120 --> 0:12:13.160
<v Speaker 1>about AI regulation in the United States versus in the EU,

0:12:13.400 --> 0:12:17.719
<v Speaker 1>and then the CEO of Google's Deep Mind added their

0:12:17.760 --> 0:12:21.079
<v Speaker 1>signature to it, among other experts. So, in other words,

0:12:21.080 --> 0:12:24.480
<v Speaker 1>this warning has the backing of some very influential, educated

0:12:24.559 --> 0:12:27.120
<v Speaker 1>and knowledgeable people who are in the field of AI.

0:12:27.240 --> 0:12:31.040
<v Speaker 1>Of course, that's assuming that the signatures are legit, because

0:12:31.080 --> 0:12:34.200
<v Speaker 1>we did have a case not that long ago where

0:12:34.240 --> 0:12:38.640
<v Speaker 1>there was an open letter warning about AI that contained

0:12:38.679 --> 0:12:42.640
<v Speaker 1>signatures from people who subsequently said they never signed it

0:12:42.760 --> 0:12:46.520
<v Speaker 1>or even heard about it. So assuming that this is

0:12:46.559 --> 0:12:50.200
<v Speaker 1>all legit, it sounds like we should really pay attention, right,

0:12:50.240 --> 0:12:53.600
<v Speaker 1>I mean, these are people who are working in that field.

0:12:54.559 --> 0:12:57.280
<v Speaker 1>That being said, I actually worry that some folks are

0:12:57.280 --> 0:12:59.719
<v Speaker 1>going to interpret this as meaning AI is on the

0:12:59.840 --> 0:13:04.800
<v Speaker 1>verse of becoming super intelligent and self aware or something.

0:13:05.120 --> 0:13:08.360
<v Speaker 1>As I mentioned earlier, generative AI leans on statistics and

0:13:08.440 --> 0:13:12.560
<v Speaker 1>training to create stuff. It's not thinking in the same

0:13:12.559 --> 0:13:15.440
<v Speaker 1>way that humans do, and I worry that if people

0:13:15.840 --> 0:13:20.000
<v Speaker 1>interpreted otherwise, then folks will be focusing on trying to

0:13:20.040 --> 0:13:23.720
<v Speaker 1>solve the wrong problem. AI definitely has the potential to

0:13:23.760 --> 0:13:27.840
<v Speaker 1>cause harm. Don't get me wrong. AI is potentially very harmful,

0:13:28.040 --> 0:13:30.840
<v Speaker 1>but it doesn't need to be, you know, brainiac in

0:13:30.920 --> 0:13:33.080
<v Speaker 1>order to be harmful. We can just look at the

0:13:33.120 --> 0:13:37.439
<v Speaker 1>instances of vehicles that have been operating in autonomous modes

0:13:37.679 --> 0:13:41.319
<v Speaker 1>that subsequently got involved in fatal car accidents. That proves

0:13:41.440 --> 0:13:44.240
<v Speaker 1>AI can be harmful and it doesn't need to be

0:13:44.320 --> 0:13:47.319
<v Speaker 1>super intelligent to do so. So I guess what I'm

0:13:47.360 --> 0:13:51.240
<v Speaker 1>saying is I believe that this warning is warranted. I

0:13:51.280 --> 0:13:54.080
<v Speaker 1>do think AI poses a threat and that we need

0:13:54.120 --> 0:13:58.640
<v Speaker 1>to have rules and regulations and approaches to AI that

0:13:58.760 --> 0:14:02.840
<v Speaker 1>are responsible and are least likely to cause harm. But

0:14:03.120 --> 0:14:06.400
<v Speaker 1>you know, it's it's trying to figure out how to

0:14:06.480 --> 0:14:10.400
<v Speaker 1>do that by framing the problem correctly. That's going to

0:14:10.400 --> 0:14:12.360
<v Speaker 1>be a big challenge. Right. You need to make sure

0:14:12.400 --> 0:14:16.080
<v Speaker 1>that you understand what the actual problem is and not

0:14:16.240 --> 0:14:20.800
<v Speaker 1>conflate it with something like super intelligence, in order to

0:14:20.880 --> 0:14:26.360
<v Speaker 1>create the proper framework to actually rectify the issue. And

0:14:26.400 --> 0:14:29.320
<v Speaker 1>in fact, like the people behind the statement said that

0:14:29.760 --> 0:14:34.120
<v Speaker 1>the whole goal of making something short and blunt was

0:14:34.440 --> 0:14:39.960
<v Speaker 1>to avoid issues of perhaps suggesting an approach that then

0:14:40.000 --> 0:14:43.960
<v Speaker 1>would just devolve into an argument over the best way forward.

0:14:44.720 --> 0:14:47.000
<v Speaker 1>But on the flip side, I would argue, well, yeah,

0:14:47.000 --> 0:14:50.560
<v Speaker 1>but if we're not suggesting approaches, then what good is

0:14:50.600 --> 0:14:54.280
<v Speaker 1>the warning? Like it's obviously we're not going to stop

0:14:54.320 --> 0:14:57.800
<v Speaker 1>developing AI. I mean, even the people who signed this

0:14:58.000 --> 0:15:02.480
<v Speaker 1>warning are actively pro promoting and developing AI right now.

0:15:02.840 --> 0:15:05.520
<v Speaker 1>There's like an AI arms race going on in the

0:15:05.520 --> 0:15:10.800
<v Speaker 1>world of computer science. So if is it just so

0:15:10.880 --> 0:15:12.920
<v Speaker 1>that you can fall back and say, well, I know,

0:15:13.000 --> 0:15:15.880
<v Speaker 1>we blew up the world, but we warned you back

0:15:15.920 --> 0:15:19.640
<v Speaker 1>in twenty twenty three. I don't know. Maybe I just

0:15:19.680 --> 0:15:25.280
<v Speaker 1>am a little too cynical about how these experts are

0:15:25.360 --> 0:15:29.840
<v Speaker 1>viewing the dangers of AI without any actual solutions to

0:15:30.520 --> 0:15:35.240
<v Speaker 1>address the problem. Moving on from AI, Japan's Space Administration

0:15:35.720 --> 0:15:39.080
<v Speaker 1>JACKSA is working with private companies in Japan to do

0:15:39.120 --> 0:15:43.520
<v Speaker 1>something pretty ambitious, So The plan is to launch collecting

0:15:43.600 --> 0:15:47.320
<v Speaker 1>satellites into space as early as twenty twenty five, and

0:15:47.360 --> 0:15:51.440
<v Speaker 1>these satellites will collect solar energy, convert that energy into

0:15:51.720 --> 0:15:56.080
<v Speaker 1>microwave beams, and then beam that energy down to receiving

0:15:56.120 --> 0:16:01.480
<v Speaker 1>stations here on Earth, which is entirely feasible. Questions remain

0:16:01.600 --> 0:16:04.160
<v Speaker 1>regarding how much energy these satellites will be able to

0:16:04.240 --> 0:16:07.280
<v Speaker 1>collect and transmit, but the point of this project is

0:16:07.320 --> 0:16:10.040
<v Speaker 1>to explore whether or not we can make solar collection

0:16:10.160 --> 0:16:13.440
<v Speaker 1>in space and microwave transmission a part of a larger

0:16:13.800 --> 0:16:17.760
<v Speaker 1>renewable energy strategy. For a country like Japan that might

0:16:17.800 --> 0:16:22.680
<v Speaker 1>have limited space for things like terrestrial solar arrays, this

0:16:22.720 --> 0:16:24.320
<v Speaker 1>could have a lot of appeal. I mean, it all

0:16:24.360 --> 0:16:27.880
<v Speaker 1>depends on how large the receiving station has to be.

0:16:27.920 --> 0:16:30.120
<v Speaker 1>I would imagine has to be quite big, so that

0:16:30.160 --> 0:16:33.160
<v Speaker 1>you're not having a super concentrated beam of microwave energy.

0:16:33.600 --> 0:16:36.920
<v Speaker 1>But it's neat like. If you can get this to

0:16:37.000 --> 0:16:41.120
<v Speaker 1>work and become a supplemental part of your energy strategy,

0:16:41.160 --> 0:16:44.520
<v Speaker 1>then it could be really useful, especially since with the

0:16:44.960 --> 0:16:48.240
<v Speaker 1>positioning of satellites, if you have a whole network out there,

0:16:48.840 --> 0:16:52.160
<v Speaker 1>you can be collecting solar energy twenty four to seven,

0:16:52.760 --> 0:16:57.200
<v Speaker 1>So and weather will never be an issue. I mean,

0:16:57.240 --> 0:16:59.760
<v Speaker 1>solar weather could potentially be an issue if you have

0:16:59.840 --> 0:17:02.600
<v Speaker 1>like a chronal mass ejection or something like that, but

0:17:03.120 --> 0:17:05.200
<v Speaker 1>you know, terrestrial weather wouldn't be an issue. So a

0:17:05.240 --> 0:17:07.560
<v Speaker 1>lot of the complaints around solar the fact that you

0:17:07.600 --> 0:17:10.400
<v Speaker 1>know you're only collecting when it's daytime and only when

0:17:10.440 --> 0:17:13.600
<v Speaker 1>you have a clear view of the sun, that ends

0:17:13.680 --> 0:17:17.199
<v Speaker 1>up being negated. But you still have questions of all, right, well,

0:17:17.200 --> 0:17:19.240
<v Speaker 1>how efficient is this going to be. How much energy

0:17:19.280 --> 0:17:22.000
<v Speaker 1>are you going to lose converting from solar to microwave,

0:17:22.400 --> 0:17:25.280
<v Speaker 1>you know, how much is lost in the transmission. These

0:17:25.320 --> 0:17:27.480
<v Speaker 1>are all questions that need to be answered as well.

0:17:27.520 --> 0:17:31.240
<v Speaker 1>But this is a cool step toward answering those questions.

0:17:31.560 --> 0:17:34.680
<v Speaker 1>Will it pan out, I don't know. I hope it does,

0:17:36.359 --> 0:17:39.040
<v Speaker 1>though obviously it also opens up other things that you

0:17:39.080 --> 0:17:44.160
<v Speaker 1>have to consider, like the potential for more space junk, right,

0:17:44.240 --> 0:17:47.080
<v Speaker 1>So there's always other things you have to bring into

0:17:47.119 --> 0:17:50.840
<v Speaker 1>the equation. But I think it's a cool project. Now.

0:17:50.880 --> 0:17:54.119
<v Speaker 1>Over this past weekend, I actually went to the amusement

0:17:54.160 --> 0:17:58.040
<v Speaker 1>park six Flags Over Georgia's for the first time in many,

0:17:58.760 --> 0:18:00.960
<v Speaker 1>many years, and I have to say. The park has

0:18:01.080 --> 0:18:04.679
<v Speaker 1>digitized a lot of operations since the last time I

0:18:04.840 --> 0:18:08.119
<v Speaker 1>went there, but at a couple of other Six Flags parks,

0:18:08.119 --> 0:18:09.919
<v Speaker 1>not at Georgia, but a couple of other ones, one

0:18:09.960 --> 0:18:13.919
<v Speaker 1>in California and one in New Jersey, that digitization is

0:18:14.080 --> 0:18:17.240
<v Speaker 1>ramping up a bit. And that's because those two parks

0:18:17.400 --> 0:18:21.760
<v Speaker 1>have partnered with Amazon and Coca Cola to incorporate one

0:18:21.800 --> 0:18:27.000
<v Speaker 1>of Amazon's grab and go cashierless shop concepts into the parks.

0:18:27.760 --> 0:18:31.480
<v Speaker 1>So just as you would in one of Amazon's operated stores,

0:18:31.840 --> 0:18:34.200
<v Speaker 1>you would be able to walk into one of these places,

0:18:34.640 --> 0:18:37.720
<v Speaker 1>pick up a product, and then stroll right out, and

0:18:37.760 --> 0:18:40.639
<v Speaker 1>you would be builled automatically through the Amazon system on

0:18:40.680 --> 0:18:44.399
<v Speaker 1>the back end. So products will include stuff like Coca

0:18:44.400 --> 0:18:47.679
<v Speaker 1>Cola products just as you would imagine, plus like snacks

0:18:48.280 --> 0:18:50.919
<v Speaker 1>and other stuff like the New Jersey location says it

0:18:50.960 --> 0:18:54.360
<v Speaker 1>will include necessities like sunblock and rain ponchos, that kind

0:18:54.400 --> 0:18:57.439
<v Speaker 1>of thing. And it's interesting to hear that the parks

0:18:57.440 --> 0:19:01.720
<v Speaker 1>are actually doing this because Amazon has actually shut down

0:19:01.760 --> 0:19:04.600
<v Speaker 1>several of its own locations, I think like eight total

0:19:04.840 --> 0:19:08.280
<v Speaker 1>in cities like New York and Seattle. However, it wouldn't

0:19:08.280 --> 0:19:10.640
<v Speaker 1>surprise me if the plan all along was to attract

0:19:10.640 --> 0:19:14.520
<v Speaker 1>partners like six Flags, where Amazon can serve as the

0:19:14.560 --> 0:19:17.159
<v Speaker 1>back end operations, but someone else is in charge of,

0:19:17.200 --> 0:19:20.240
<v Speaker 1>you know, restocking and cleaning the place and that kind

0:19:20.280 --> 0:19:24.600
<v Speaker 1>of thing. Over the weekend, Toyota entered a hydrogen powered

0:19:24.720 --> 0:19:28.320
<v Speaker 1>racing car into an endurance race in Japan. The company

0:19:28.320 --> 0:19:30.399
<v Speaker 1>said it looked at the race as a sort of

0:19:30.480 --> 0:19:34.560
<v Speaker 1>testing ground for the technology and an opportunity to uncover

0:19:34.680 --> 0:19:39.320
<v Speaker 1>areas of improvement that wouldn't necessarily pop up in a

0:19:39.359 --> 0:19:43.320
<v Speaker 1>laboratory setting, which is understandable, right Like in a lab

0:19:43.400 --> 0:19:46.920
<v Speaker 1>you can test technology quite a bit and see where

0:19:46.960 --> 0:19:49.520
<v Speaker 1>there may be areas that you need to focus on

0:19:49.560 --> 0:19:52.440
<v Speaker 1>to fix things, but it's not until you really get

0:19:52.480 --> 0:19:55.119
<v Speaker 1>something out in the real world and really put to

0:19:55.160 --> 0:19:58.760
<v Speaker 1>the test that some problems will become evident. And let

0:19:58.840 --> 0:20:01.160
<v Speaker 1>me tell you, an endurance race, a twenty four hour

0:20:01.280 --> 0:20:04.960
<v Speaker 1>endurance race. That's a heck of a test for a technology.

0:20:05.280 --> 0:20:09.400
<v Speaker 1>Toyota has actually been working on hydrogen fueled cars for

0:20:09.480 --> 0:20:13.440
<v Speaker 1>a while, and in fact has even fielded hydrogen fueled

0:20:13.480 --> 0:20:16.760
<v Speaker 1>cars in various races, but the big difference in this

0:20:16.840 --> 0:20:20.440
<v Speaker 1>most recent vehicle is that the car was using liquid

0:20:20.680 --> 0:20:25.119
<v Speaker 1>hydrogen rather than gaseous hydrogen. Now, liquid hydrogen comes with

0:20:25.160 --> 0:20:27.720
<v Speaker 1>a whole bunch of challenges, like you have to keep

0:20:27.800 --> 0:20:30.520
<v Speaker 1>the hydrogen at a very low temperature to keep it liquid.

0:20:31.000 --> 0:20:34.239
<v Speaker 1>But it also means that you end up with a

0:20:34.320 --> 0:20:39.639
<v Speaker 1>higher energy density fuel, right because liquid hydrogen packs more

0:20:40.240 --> 0:20:45.399
<v Speaker 1>energy per volume than gaseous hydrogen does, which is an

0:20:45.440 --> 0:20:48.120
<v Speaker 1>important consideration for an endurance race. You know, you want

0:20:48.160 --> 0:20:52.240
<v Speaker 1>to have a fuel or an energy rich fuel. I

0:20:52.280 --> 0:20:56.520
<v Speaker 1>should say I couldn't find any information on how well

0:20:56.880 --> 0:20:59.800
<v Speaker 1>it performed. The race happened just this past weekend, but

0:21:00.040 --> 0:21:01.639
<v Speaker 1>I did see a lot of articles saying, you know,

0:21:02.880 --> 0:21:06.160
<v Speaker 1>it did it. It didn't tell me how well it did.

0:21:06.760 --> 0:21:09.800
<v Speaker 1>Critics have long argued that Toyota has been dragging its

0:21:09.840 --> 0:21:14.639
<v Speaker 1>feet on developing electric vehicles. Obviously that's where the automotive

0:21:14.640 --> 0:21:19.359
<v Speaker 1>industry is really shifting toward, and as a result, because

0:21:19.400 --> 0:21:24.639
<v Speaker 1>Toyota did not jump onto that particular approach, it is

0:21:24.720 --> 0:21:27.560
<v Speaker 1>now lagging behind competitors as it tries to make up

0:21:27.560 --> 0:21:33.240
<v Speaker 1>for lost ground. Toyota, however, has long argued that it's

0:21:33.280 --> 0:21:36.720
<v Speaker 1>going to take longer to transition to pure electric vehicles

0:21:37.320 --> 0:21:41.680
<v Speaker 1>than most people expect and as a result, in order

0:21:41.760 --> 0:21:46.320
<v Speaker 1>to bring down carbon emissions while also transitioning to electric vehicles,

0:21:46.720 --> 0:21:50.840
<v Speaker 1>Toyota has said, we need to invest in alternatives to

0:21:51.000 --> 0:21:54.520
<v Speaker 1>just pure electric vehicles. This has been Toyota's message for

0:21:54.680 --> 0:21:58.520
<v Speaker 1>years and years, with fuel cell vehicles, hydrogen powered vehicles,

0:21:58.560 --> 0:22:02.080
<v Speaker 1>various hybrids, that kind of thing. There are critics who

0:22:02.119 --> 0:22:06.800
<v Speaker 1>say that Toyota has made the wrong call, that the

0:22:06.960 --> 0:22:11.560
<v Speaker 1>company is just trying to justify its approach to a

0:22:11.600 --> 0:22:16.679
<v Speaker 1>different branch of vehicle development, and that it's kind of

0:22:16.720 --> 0:22:19.480
<v Speaker 1>like it's sort of a sunk cost fallacy. It's gone

0:22:19.520 --> 0:22:22.480
<v Speaker 1>so far that it can't come back. Although the new

0:22:22.520 --> 0:22:26.720
<v Speaker 1>leadership at Toyota has been a bit more pro ev

0:22:27.040 --> 0:22:34.239
<v Speaker 1>side than previous leadership has. It's interesting there's a lot

0:22:34.240 --> 0:22:39.080
<v Speaker 1>of challenges that are associated with hydrogen based vehicles, including

0:22:39.080 --> 0:22:42.840
<v Speaker 1>how to harvest pure hydrogen without using too much energy

0:22:42.920 --> 0:22:46.120
<v Speaker 1>in the process. You may know hydrogen is the most

0:22:46.119 --> 0:22:51.200
<v Speaker 1>plentiful element in our universe, but it binds with stuff,

0:22:51.240 --> 0:22:54.880
<v Speaker 1>which means in order to get hydrogen, we frequently need

0:22:54.920 --> 0:22:59.679
<v Speaker 1>to expel energy to break those molecular bonds to harvest

0:22:59.720 --> 0:23:05.680
<v Speaker 1>pure hydrogen. And if you are spending more energy to

0:23:05.720 --> 0:23:08.760
<v Speaker 1>separate the hydrogen from stuff. Then you're getting out of

0:23:08.760 --> 0:23:12.720
<v Speaker 1>the hydrogen itself. Then you're at working at a net loss,

0:23:12.760 --> 0:23:16.359
<v Speaker 1>and you may need to just re evaluate what you're doing.

0:23:16.400 --> 0:23:18.280
<v Speaker 1>It may turn out that there's a different thing you

0:23:18.320 --> 0:23:22.960
<v Speaker 1>can do where you just eliminate that step and you're

0:23:22.960 --> 0:23:26.639
<v Speaker 1>wasting less energy. I'll have to do another episode in

0:23:26.680 --> 0:23:28.440
<v Speaker 1>the near future to kind of go down the list

0:23:28.440 --> 0:23:32.440
<v Speaker 1>of pros and cons of things like a hydrogen based economy.

0:23:33.359 --> 0:23:37.720
<v Speaker 1>A few decades ago, that was a really big thing,

0:23:38.040 --> 0:23:41.000
<v Speaker 1>at least in rhetoric in the United States, and we

0:23:41.119 --> 0:23:46.760
<v Speaker 1>haven't really seen it mature and turn into a real

0:23:46.880 --> 0:23:49.600
<v Speaker 1>technology here in the US, and I thought it might

0:23:49.640 --> 0:23:51.440
<v Speaker 1>be a good idea to kind of do a follow

0:23:51.520 --> 0:23:55.000
<v Speaker 1>up and talk about what are those pros and cons

0:23:55.200 --> 0:23:59.920
<v Speaker 1>and is it really a viable approach and a viable

0:24:00.000 --> 0:24:04.200
<v Speaker 1>alternative to your traditional internal combustion engines. Keeping in mind

0:24:04.440 --> 0:24:08.000
<v Speaker 1>a hydrogen based car also uses combustion. It's just when

0:24:08.040 --> 0:24:12.440
<v Speaker 1>you are you know, when hydrogen goes through combustion, you're

0:24:12.440 --> 0:24:14.560
<v Speaker 1>not getting the same byproducts as you would if you

0:24:14.600 --> 0:24:18.720
<v Speaker 1>were burning gasoline. Okay, I've got a couple more things

0:24:18.720 --> 0:24:21.160
<v Speaker 1>I want to talk about But before we get to those,

0:24:21.200 --> 0:24:33.879
<v Speaker 1>let's take one more quick break. We're back. So the

0:24:34.040 --> 0:24:38.080
<v Speaker 1>United States is not the only country planning to put

0:24:38.119 --> 0:24:41.840
<v Speaker 1>people on the Moon again. So NASA obviously has Project

0:24:42.000 --> 0:24:46.520
<v Speaker 1>Artemis Artemis one, which was a test flight of the

0:24:47.840 --> 0:24:51.920
<v Speaker 1>spacecraft and the launch vehicle. That's already happened, so Artemis

0:24:51.920 --> 0:24:57.720
<v Speaker 1>one was a success. Artimist two will see a crew

0:24:58.200 --> 0:25:04.520
<v Speaker 1>of astronauts launch off Earth and then circle around the

0:25:04.560 --> 0:25:08.440
<v Speaker 1>backside of the Moon, not the dark side because there's

0:25:09.240 --> 0:25:12.080
<v Speaker 1>the dark side changes, but the backside, the far side

0:25:12.080 --> 0:25:14.719
<v Speaker 1>of the Moon, and then return to Earth. They are

0:25:14.760 --> 0:25:17.200
<v Speaker 1>not actually going to touch down. And then Artemis three

0:25:18.000 --> 0:25:22.840
<v Speaker 1>is the mission where astronauts would land on the Moon again.

0:25:23.240 --> 0:25:27.560
<v Speaker 1>That one currently is projected for twenty twenty five. I'll

0:25:27.560 --> 0:25:32.320
<v Speaker 1>be shocked if we make that goal. But meanwhile, China's

0:25:32.400 --> 0:25:36.800
<v Speaker 1>Manned Space Agency announced that it plans to land Chinese

0:25:36.840 --> 0:25:40.960
<v Speaker 1>astronauts on the Moon by twenty thirty. To accomplish that goal,

0:25:41.000 --> 0:25:44.679
<v Speaker 1>the agency is developing a new launch vehicle and a

0:25:44.720 --> 0:25:51.399
<v Speaker 1>new spacecraft. Again, that's a really aggressive goal. If the

0:25:52.040 --> 0:25:54.840
<v Speaker 1>launch vehicle and the spacecraft are still in development, it

0:25:55.760 --> 0:25:59.399
<v Speaker 1>often can take a very long time to get that

0:25:59.480 --> 0:26:02.480
<v Speaker 1>kind of stuff buttoned up. Also, it will be interesting

0:26:02.480 --> 0:26:05.159
<v Speaker 1>to see if lunar real estate becomes the next big

0:26:05.320 --> 0:26:09.399
<v Speaker 1>land grab. You know, there are obviously space treaties that

0:26:09.440 --> 0:26:13.080
<v Speaker 1>are meant to prevent such things, but I would be

0:26:13.160 --> 0:26:18.760
<v Speaker 1>shocked if we don't see some rather aggressive moves to

0:26:18.840 --> 0:26:23.919
<v Speaker 1>claim lunar landscape for various purposes. So we'll keep an

0:26:23.920 --> 0:26:27.240
<v Speaker 1>eye on that too. I can't wait for it to

0:26:27.240 --> 0:26:31.000
<v Speaker 1>become some sort of Heinland novel. All right, now we're

0:26:31.040 --> 0:26:34.080
<v Speaker 1>toward the end of the episode, and occasionally I like

0:26:34.200 --> 0:26:37.800
<v Speaker 1>to end episodes with some suggested reading material for y'all.

0:26:38.000 --> 0:26:41.159
<v Speaker 1>So rather than go through all of this as a

0:26:41.200 --> 0:26:44.120
<v Speaker 1>news item, I thought I would talk about a few articles,

0:26:44.160 --> 0:26:46.280
<v Speaker 1>three of them in particular, that I think are worth

0:26:46.320 --> 0:26:49.960
<v Speaker 1>your time to read. Also, these articles tend to fall

0:26:50.000 --> 0:26:56.840
<v Speaker 1>more into investigative journalism or interesting experiences and less on

0:26:56.960 --> 0:27:00.439
<v Speaker 1>the news side. First up is an art article in

0:27:00.480 --> 0:27:05.760
<v Speaker 1>Ours Technica that Dan goodin ours Technica phenomenal resource. If

0:27:05.800 --> 0:27:08.320
<v Speaker 1>you are not visiting ours Technica on the rag to

0:27:08.920 --> 0:27:12.399
<v Speaker 1>read up on their journalism and tech, you need to

0:27:12.480 --> 0:27:16.520
<v Speaker 1>change that because Ours Technica is a fantastic resource. The

0:27:16.680 --> 0:27:21.200
<v Speaker 1>article I'm referencing is called inner workings revealed for Predator,

0:27:21.400 --> 0:27:26.680
<v Speaker 1>the Android malware that exploited five zero days, so zero

0:27:26.760 --> 0:27:32.119
<v Speaker 1>day being an exploit that the company that's behind the

0:27:32.160 --> 0:27:35.320
<v Speaker 1>software is unaware of, and that is in there front

0:27:35.359 --> 0:27:37.640
<v Speaker 1>the very beginning, and you can just if you find

0:27:37.680 --> 0:27:40.080
<v Speaker 1>out about it, you can exploit it to your heart's

0:27:40.080 --> 0:27:44.840
<v Speaker 1>content until someone notices what's going on. So the article

0:27:44.920 --> 0:27:48.520
<v Speaker 1>details a dramatic story about how companies specializing in a

0:27:48.560 --> 0:27:53.320
<v Speaker 1>double whammy of discovering and exploiting vulnerabilities as well as

0:27:53.359 --> 0:27:57.760
<v Speaker 1>turning mobile phones into remote surveillance devices are making an

0:27:57.800 --> 0:28:02.000
<v Speaker 1>awful lot of money selling those tools to very dangerous

0:28:02.040 --> 0:28:06.760
<v Speaker 1>customers who then employ the technology to target perceived threats.

0:28:07.119 --> 0:28:10.280
<v Speaker 1>We've seen this story play out in other areas as well.

0:28:11.200 --> 0:28:15.560
<v Speaker 1>There was obviously the case of the Israeli tech company

0:28:15.640 --> 0:28:20.879
<v Speaker 1>that was selling an exploit for iOS systems that took

0:28:21.080 --> 0:28:25.200
<v Speaker 1>advantage of a vulnerability and eye message. Very similar case,

0:28:25.320 --> 0:28:29.960
<v Speaker 1>and this article goes over something like that, but one

0:28:30.000 --> 0:28:36.240
<v Speaker 1>that affected Android devices as well. Highly recommended. CNBC has

0:28:36.320 --> 0:28:40.360
<v Speaker 1>an article titled Chinese apps remain hugely popular in the

0:28:40.480 --> 0:28:44.560
<v Speaker 1>US despite efforts to ban TikTok, and this one touches

0:28:44.600 --> 0:28:47.320
<v Speaker 1>on some stuff that I have mentioned on tech stuff

0:28:47.360 --> 0:28:51.440
<v Speaker 1>in the past, namely, TikTok represents a very high profile

0:28:51.560 --> 0:28:56.120
<v Speaker 1>example of a problem that actually goes well beyond TikTok,

0:28:56.480 --> 0:29:00.000
<v Speaker 1>and perhaps it might be better to take a step

0:29:00.200 --> 0:29:04.000
<v Speaker 1>back to consider whether or not TikTok is kind of

0:29:04.160 --> 0:29:08.400
<v Speaker 1>standing in as a scapegoat for a much bigger problem.

0:29:09.080 --> 0:29:13.640
<v Speaker 1>And it's a problem that even expands beyond the possibility

0:29:13.760 --> 0:29:17.920
<v Speaker 1>of a country like China harvesting all this information, because

0:29:17.920 --> 0:29:21.400
<v Speaker 1>obviously we've got all these other huge companies that are

0:29:21.400 --> 0:29:24.440
<v Speaker 1>in the United States that are also harvesting information, and

0:29:24.520 --> 0:29:29.360
<v Speaker 1>that maybe the problem isn't just with who is getting it,

0:29:29.400 --> 0:29:32.400
<v Speaker 1>but the fact that it's being done full stop. The

0:29:32.440 --> 0:29:34.760
<v Speaker 1>piece also points out something that a lot of others

0:29:34.760 --> 0:29:38.400
<v Speaker 1>have been saying for a while, that a lot of

0:29:38.400 --> 0:29:43.800
<v Speaker 1>the TikTok suspicion is being fueled by companies, primarily Meta,

0:29:43.920 --> 0:29:48.160
<v Speaker 1>that would stand to benefit tremendously if TikTok were to

0:29:48.280 --> 0:29:53.160
<v Speaker 1>go away. So knowing that Meta has a vested interest

0:29:53.160 --> 0:29:57.520
<v Speaker 1>in TikTok dying helps kind of put all this into

0:29:57.560 --> 0:30:00.840
<v Speaker 1>context as well. That's another reason why TikTok is so

0:30:01.080 --> 0:30:05.760
<v Speaker 1>prominent in this discussion because you've got companies that have

0:30:05.800 --> 0:30:09.760
<v Speaker 1>a lot of money that are very eager to support

0:30:09.800 --> 0:30:12.600
<v Speaker 1>the narrative that TikTok is a danger. That's not to

0:30:12.640 --> 0:30:14.760
<v Speaker 1>say that TikTok's not a danger. I'm not saying that.

0:30:14.800 --> 0:30:17.760
<v Speaker 1>I'm saying it's like, let's do a laser focus on

0:30:17.800 --> 0:30:22.960
<v Speaker 1>this one instance and ignore the larger problem that remains

0:30:23.040 --> 0:30:28.200
<v Speaker 1>unaddressed as long as we're only focusing on TikTok. Finally,

0:30:28.320 --> 0:30:33.080
<v Speaker 1>the third article I want to recommend is by Maxwell Stretchen,

0:30:33.400 --> 0:30:37.560
<v Speaker 1>and my apologies for that pronunciation of your name, Maxwell,

0:30:37.920 --> 0:30:41.240
<v Speaker 1>I'm sure I butchered it. But Maxwell has a piece

0:30:41.280 --> 0:30:45.600
<v Speaker 1>on Motherboard titled I asked Chat GPT to control My

0:30:45.720 --> 0:30:49.200
<v Speaker 1>life and it immediately fell apart. Now, this is a

0:30:49.240 --> 0:30:53.760
<v Speaker 1>pretty amusing story about Maxwell experimenting with chat GPT to

0:30:53.840 --> 0:30:58.640
<v Speaker 1>create a daily schedule. Like Maxwell just highlighted the things

0:30:58.640 --> 0:31:01.680
<v Speaker 1>that he needed to do and wanted to do and

0:31:01.880 --> 0:31:03.840
<v Speaker 1>gave it a chat gpt to tell them how to

0:31:03.880 --> 0:31:08.400
<v Speaker 1>do it. And it highlights a few interesting things, including

0:31:08.400 --> 0:31:11.960
<v Speaker 1>how open ai is trying to build in guardrails to

0:31:12.040 --> 0:31:14.920
<v Speaker 1>prevent bad stuff from happening, or at least to prevent

0:31:15.600 --> 0:31:19.880
<v Speaker 1>the optics from going bad. So like chat GPT saying hey,

0:31:20.680 --> 0:31:23.320
<v Speaker 1>autonomy is really important and you shouldn't just hand it

0:31:23.360 --> 0:31:27.200
<v Speaker 1>over to someone, which you know may or may not

0:31:27.320 --> 0:31:33.760
<v Speaker 1>have been a legitimate and earnest statement all the way

0:31:33.800 --> 0:31:36.800
<v Speaker 1>to how chat GPT has trouble meeting all of Maxwell's

0:31:36.880 --> 0:31:40.480
<v Speaker 1>daily goals reasonably. If you've played the sims, you know

0:31:40.520 --> 0:31:43.440
<v Speaker 1>how frustrating it is. There just aren't enough hours in

0:31:43.480 --> 0:31:45.400
<v Speaker 1>the day to do everything you need to do plus

0:31:45.440 --> 0:31:49.080
<v Speaker 1>everything you want to do. Turns out AI has that

0:31:49.160 --> 0:31:53.200
<v Speaker 1>same sort of problem, So yes, I recommend those three articles.

0:31:53.320 --> 0:31:57.520
<v Speaker 1>Check those out. All right, that's it for the news

0:31:57.600 --> 0:32:01.080
<v Speaker 1>for Tuesday, May thirtieth, twenty twenty three. I hope you

0:32:01.160 --> 0:32:05.400
<v Speaker 1>are all well and I'll talk to you again really soon.

0:32:11.640 --> 0:32:16.280
<v Speaker 1>Tech Stuff is an iHeartRadio production. For more podcasts from iHeartRadio,

0:32:16.600 --> 0:32:20.320
<v Speaker 1>visit the iHeartRadio app, Apple Podcasts, or wherever you listen

0:32:20.360 --> 0:32:21.400
<v Speaker 1>to your favorite shows.