WEBVTT - Tech News: AI Versus The Pope

0:00:04.440 --> 0:00:12.280
<v Speaker 1>Welcome to tech Stuff, a production from iHeartRadio. Hey there,

0:00:12.280 --> 0:00:15.920
<v Speaker 1>and welcome to tech Stuff. I'm your host, Jonathan Strickland.

0:00:15.960 --> 0:00:18.960
<v Speaker 1>I'm an executive producer with iHeartRadio. And how the tech

0:00:19.000 --> 0:00:22.160
<v Speaker 1>are you. It's time for the tech news for Tuesday,

0:00:22.320 --> 0:00:28.320
<v Speaker 1>August eighth, twenty twenty three. And despite my voice catching there,

0:00:28.400 --> 0:00:31.200
<v Speaker 1>I feel a lot better than I did yesterday. Thanks

0:00:31.200 --> 0:00:31.800
<v Speaker 1>for asking.

0:00:32.159 --> 0:00:33.640
<v Speaker 2>Let's get to the tech news.

0:00:34.159 --> 0:00:37.120
<v Speaker 1>And we've got a lot of AI related stories today.

0:00:37.320 --> 0:00:40.879
<v Speaker 1>No big surprise there. It has been the topic of

0:00:41.000 --> 0:00:46.479
<v Speaker 1>twenty twenty three, at least whenever Elon Musk isn't demanding

0:00:46.520 --> 0:00:50.680
<v Speaker 1>all the headlines. And it's also sadly no surprise that

0:00:50.720 --> 0:00:53.199
<v Speaker 1>one of the AI stories we're covering today has to

0:00:53.240 --> 0:00:57.360
<v Speaker 1>do with faulty facial recognition technology and the mistake of

0:00:57.440 --> 0:01:01.040
<v Speaker 1>relying on that tech for the purposes of law enforcement.

0:01:01.760 --> 0:01:06.200
<v Speaker 1>Porsche Woodruff, a black woman in Detroit, found herself arrested

0:01:06.280 --> 0:01:10.560
<v Speaker 1>and attained for eleven hours when police acted on an

0:01:10.680 --> 0:01:14.680
<v Speaker 1>incorrect facial recognition match while seeking a suspect in a

0:01:14.720 --> 0:01:19.600
<v Speaker 1>carjacking and robbery crime. Not only that Portiae is eight

0:01:19.680 --> 0:01:23.200
<v Speaker 1>months pregnant, and the surveillance footage from the crime in

0:01:23.280 --> 0:01:27.319
<v Speaker 1>question showed a woman who very much was not eight

0:01:27.360 --> 0:01:30.160
<v Speaker 1>months pregnant. So not only was this a case of

0:01:30.200 --> 0:01:34.200
<v Speaker 1>facial recognition software giving a false positive, it's also a

0:01:34.240 --> 0:01:37.840
<v Speaker 1>case of cops apparently working under the assumption that a

0:01:37.880 --> 0:01:41.839
<v Speaker 1>woman can go from not visibly pregnant to eight months

0:01:41.840 --> 0:01:45.600
<v Speaker 1>pregnant in a very short amount of time, which is wild.

0:01:45.840 --> 0:01:50.040
<v Speaker 1>So here's kind of what unfolded. A man reported being

0:01:50.080 --> 0:01:53.920
<v Speaker 1>the victim of a robbery and carjacking. The police were

0:01:53.920 --> 0:01:57.080
<v Speaker 1>able to secure surveillance footage, and they used a tool

0:01:57.200 --> 0:02:02.720
<v Speaker 1>called data works plus to unmatches against mug shots that

0:02:02.800 --> 0:02:06.680
<v Speaker 1>were stored in a police database. Woodroff had been arrested

0:02:06.680 --> 0:02:09.840
<v Speaker 1>back in twenty fifteen, so her mugshot was one of

0:02:09.880 --> 0:02:13.440
<v Speaker 1>the images in that database. This tool pulled a match

0:02:13.600 --> 0:02:16.959
<v Speaker 1>between her mugshot and the surveillance footage, and the guy

0:02:16.960 --> 0:02:20.880
<v Speaker 1>who was robbed also mistook a photo of Woodroff her

0:02:20.919 --> 0:02:24.320
<v Speaker 1>mugshot as that as the same person as the perpetrator.

0:02:24.720 --> 0:02:27.840
<v Speaker 1>So the police go and they arrest Woodroff, and of

0:02:27.840 --> 0:02:30.400
<v Speaker 1>course she was not involved in the crime, could not

0:02:30.560 --> 0:02:33.080
<v Speaker 1>have been, and just the fact that she was, you know,

0:02:33.160 --> 0:02:36.919
<v Speaker 1>eight months pregnant should have been the immediate giveaway that

0:02:36.960 --> 0:02:40.000
<v Speaker 1>this is not the same person. The New York Times

0:02:40.040 --> 0:02:44.040
<v Speaker 1>subsequently reported that Woodroff's case was the third in the

0:02:44.080 --> 0:02:48.800
<v Speaker 1>city of Detroit alone that resulted in a wrongful arrest

0:02:49.040 --> 0:02:53.360
<v Speaker 1>due to incorrect facial recognition matches, and that all three

0:02:53.400 --> 0:02:56.400
<v Speaker 1>of those cases, as well as three other cases that

0:02:56.480 --> 0:03:01.359
<v Speaker 1>were not in Detroit, all involved black people. I think

0:03:01.400 --> 0:03:05.040
<v Speaker 1>it's safe to say that even the faulty facial recognition

0:03:05.080 --> 0:03:08.520
<v Speaker 1>technology is able to see a pattern emerging here, and

0:03:08.560 --> 0:03:13.320
<v Speaker 1>it's one of racial bias in surveillance and identification tools. Now,

0:03:13.360 --> 0:03:16.720
<v Speaker 1>as we have covered on this podcast, several cities and

0:03:16.840 --> 0:03:20.760
<v Speaker 1>jurisdictions have banned the use of facial recognition for law

0:03:20.840 --> 0:03:25.239
<v Speaker 1>enforcement purposes. Personally, I think that is merited. I can't

0:03:25.280 --> 0:03:29.440
<v Speaker 1>help but imagine what being wrongfully arrested must be like.

0:03:29.560 --> 0:03:33.440
<v Speaker 1>It's got to be incredibly traumatic and disruptive and.

0:03:33.360 --> 0:03:36.520
<v Speaker 2>Potentially cause lots of issues.

0:03:36.040 --> 0:03:39.480
<v Speaker 1>In your life, and you at no point were at

0:03:39.520 --> 0:03:42.720
<v Speaker 1>fault for any of it. And if a technology is

0:03:42.800 --> 0:03:49.000
<v Speaker 1>disproportionately leading to that kind of thing, we should not

0:03:49.320 --> 0:03:54.880
<v Speaker 1>be using that technology for those purposes. I don't know

0:03:54.920 --> 0:03:58.160
<v Speaker 1>how there's any argument against that. If the tool is

0:03:58.480 --> 0:04:01.640
<v Speaker 1>leading to innocent people getting arrested and their lives getting

0:04:01.680 --> 0:04:02.840
<v Speaker 1>up ended in the process.

0:04:03.320 --> 0:04:04.800
<v Speaker 2>You got to stop using the tool.

0:04:05.560 --> 0:04:09.400
<v Speaker 1>British researchers showed how a deep learning algorithm, once trained,

0:04:09.400 --> 0:04:13.640
<v Speaker 1>would be able to decode keystrokes just from the sound

0:04:14.040 --> 0:04:18.400
<v Speaker 1>of typing. This isn't totally new. I've heard of these

0:04:18.480 --> 0:04:22.040
<v Speaker 1>kinds of attacks before. But imagine for a moment that

0:04:22.520 --> 0:04:25.880
<v Speaker 1>you are set up in some public space and someone

0:04:25.880 --> 0:04:29.160
<v Speaker 1>else happens to have their phone out and you know,

0:04:29.240 --> 0:04:31.800
<v Speaker 1>you don't know this, but what they're actually doing is

0:04:31.839 --> 0:04:35.240
<v Speaker 1>activating the phone's microphone, and they're picking up on the

0:04:35.279 --> 0:04:39.359
<v Speaker 1>sound of you tippity tappany typing away, and you're oblivious

0:04:39.360 --> 0:04:41.400
<v Speaker 1>to any threats. So like maybe you're you're like being

0:04:41.400 --> 0:04:43.479
<v Speaker 1>careful with your screen or whatever, but you're not thinking

0:04:43.480 --> 0:04:48.039
<v Speaker 1>about the actual keystrokes. And meanwhile, a computer program on

0:04:48.080 --> 0:04:51.240
<v Speaker 1>the other end of that microphone is effectively transcribing everything

0:04:51.240 --> 0:04:55.880
<v Speaker 1>you've typed, potentially including your login information. This is an

0:04:55.920 --> 0:04:59.919
<v Speaker 1>acoustic attack, and I bet that makes all those mechanical

0:05:00.120 --> 0:05:03.600
<v Speaker 1>keyboard clackie clackie types out there a little nervous. So

0:05:04.040 --> 0:05:06.400
<v Speaker 1>is it possible that some hacker out there could get

0:05:06.440 --> 0:05:09.920
<v Speaker 1>your log in credentials just by having a computer listen

0:05:09.960 --> 0:05:14.040
<v Speaker 1>to you type. Technically, yes, it is possible. It is

0:05:14.080 --> 0:05:18.120
<v Speaker 1>not necessarily straightforward or easy to do. It is possible.

0:05:18.760 --> 0:05:23.320
<v Speaker 1>So if you're at a location, then you need to

0:05:23.360 --> 0:05:26.240
<v Speaker 1>know that is a possibility. But like a lot of

0:05:26.240 --> 0:05:28.479
<v Speaker 1>locations have a lot of other noise, it's hard to

0:05:28.480 --> 0:05:31.400
<v Speaker 1>set up a microphone in such a way that you're

0:05:31.440 --> 0:05:34.599
<v Speaker 1>going to get a very clear recording of that sound.

0:05:35.160 --> 0:05:36.960
<v Speaker 1>Maybe if you're at a coffee shop, you should just

0:05:36.960 --> 0:05:39.480
<v Speaker 1>start making CLACKI clacky noises with your mouth at the

0:05:39.520 --> 0:05:41.960
<v Speaker 1>same time as you type, you know, to throw off

0:05:42.000 --> 0:05:45.320
<v Speaker 1>any potential batties who are trying to listen in on you.

0:05:45.800 --> 0:05:46.280
<v Speaker 2>I don't know.

0:05:46.720 --> 0:05:49.919
<v Speaker 1>It's a wild world out there. Reuter's reports that the

0:05:49.920 --> 0:05:53.560
<v Speaker 1>Walt Disney Company has created a task force to research

0:05:53.600 --> 0:05:57.560
<v Speaker 1>how artificial intelligence could be used within that company, which

0:05:57.600 --> 0:06:01.159
<v Speaker 1>of course encompasses lots of different divisions. You've got the

0:06:01.279 --> 0:06:05.080
<v Speaker 1>entertainment division, You've got theme parks, You've got merchandising, you've

0:06:05.120 --> 0:06:10.080
<v Speaker 1>got advertising. There's tons of businesses underneath the umbrella of

0:06:10.120 --> 0:06:14.719
<v Speaker 1>Walt Disney. Well, the company currently has nearly a dozen

0:06:14.839 --> 0:06:19.200
<v Speaker 1>job openings that mention artificial intelligence research and development. So

0:06:20.040 --> 0:06:21.960
<v Speaker 1>this does look like it's a big push and could

0:06:21.960 --> 0:06:25.960
<v Speaker 1>include things like imagineering, but it also ranges to other stuff,

0:06:26.000 --> 0:06:30.240
<v Speaker 1>you know, theme parks to advertising to also Disney television.

0:06:30.440 --> 0:06:33.400
<v Speaker 1>And that last one is pretty notable because many of

0:06:33.400 --> 0:06:36.320
<v Speaker 1>the contentious elements that are at the center of the

0:06:36.600 --> 0:06:41.120
<v Speaker 1>ongoing strikes in Hollywood, which if you weren't aware, involves

0:06:41.160 --> 0:06:45.280
<v Speaker 1>both writers and actors. They're both on strike in Hollywood

0:06:45.320 --> 0:06:47.880
<v Speaker 1>right now. Well, one of the things they're striking about

0:06:48.560 --> 0:06:51.760
<v Speaker 1>is all about how studios should or should not use

0:06:51.880 --> 0:06:57.880
<v Speaker 1>artificial intelligence moving forward. Reuter's cites some unnamed folks connected

0:06:57.920 --> 0:07:00.560
<v Speaker 1>to Disney, no people who didn't want to have this

0:07:00.640 --> 0:07:03.400
<v Speaker 1>get back to them, but they said that the company

0:07:03.440 --> 0:07:06.400
<v Speaker 1>really has little choice here, that if it doesn't incorporate

0:07:06.480 --> 0:07:10.760
<v Speaker 1>AI into its strategy, it runs the risk of becoming obsolete.

0:07:11.840 --> 0:07:13.840
<v Speaker 2>Maybe that's true.

0:07:13.960 --> 0:07:17.400
<v Speaker 1>But my knee jerk reaction kind of is triggered because

0:07:17.440 --> 0:07:20.640
<v Speaker 1>back in two thousand and four, Disney famously shut down

0:07:20.680 --> 0:07:25.520
<v Speaker 1>its two D animation studios, and it was unthinkable for

0:07:25.600 --> 0:07:30.400
<v Speaker 1>a company that had built its reputation on traditional two

0:07:30.480 --> 0:07:34.000
<v Speaker 1>D animation to suddenly turn its back on it. It

0:07:34.040 --> 0:07:37.520
<v Speaker 1>has subsequently changed that, But for a while, it looked

0:07:37.560 --> 0:07:39.880
<v Speaker 1>like two D animation and Disney were just things of

0:07:39.920 --> 0:07:42.880
<v Speaker 1>the past, and it just seemed like there was this

0:07:43.000 --> 0:07:47.120
<v Speaker 1>attitude among Disney executive leadership that computer animation was somehow

0:07:47.480 --> 0:07:50.840
<v Speaker 1>not just different from traditional hand drawn two D animation,

0:07:51.320 --> 0:07:55.600
<v Speaker 1>but innately better than two D animated films. Like, audiences

0:07:55.640 --> 0:07:58.680
<v Speaker 1>didn't want to see two D animation, they just wanted

0:07:58.720 --> 0:08:01.720
<v Speaker 1>computer animation, and for proof of that you would look

0:08:01.760 --> 0:08:06.720
<v Speaker 1>at Pixar. Here's the problem. Pixar was investing heavily in

0:08:06.880 --> 0:08:11.720
<v Speaker 1>developing great stories to tell, and yes, the computer animation

0:08:12.240 --> 0:08:15.040
<v Speaker 1>was getting more and more impressive with every single film,

0:08:15.800 --> 0:08:19.960
<v Speaker 1>but they were really putting story first, whereas the animated

0:08:20.040 --> 0:08:23.480
<v Speaker 1>side over at Disney had fallen a long way since

0:08:23.520 --> 0:08:26.560
<v Speaker 1>the early days of the so called Disney Renaissance, which

0:08:26.600 --> 0:08:29.560
<v Speaker 1>included movies like The Little Mermaid and Beauty and the

0:08:29.560 --> 0:08:32.640
<v Speaker 1>Beast in Aladdin. You know, if you look at nineteen

0:08:32.679 --> 0:08:35.319
<v Speaker 1>ninety five, for example, I would say I don't think

0:08:35.360 --> 0:08:38.160
<v Speaker 1>Toy Story, which came out in nineteen ninety five, was

0:08:38.640 --> 0:08:41.920
<v Speaker 1>a better movie than Pocahontas, which also came out in

0:08:42.040 --> 0:08:45.679
<v Speaker 1>ninety five, just because Toy Story was computer animated and

0:08:45.720 --> 0:08:48.680
<v Speaker 1>Pocahontas was hand drawn. I think Toy Story was a

0:08:48.679 --> 0:08:51.839
<v Speaker 1>better movie because the script was better. But you know,

0:08:52.040 --> 0:08:54.280
<v Speaker 1>Pocahontas also had to follow up on the amazing work

0:08:54.280 --> 0:08:56.800
<v Speaker 1>of Ashman and Mancoln and Ashman had passed away in

0:08:56.880 --> 0:08:59.680
<v Speaker 1>nineteen ninety one, so there are a lot of other

0:09:00.080 --> 0:09:03.920
<v Speaker 1>to getting factors there. Anyway, Disney hasn't really commented on

0:09:04.240 --> 0:09:08.000
<v Speaker 1>how it plans to incorporate AI into its processes. It's

0:09:08.440 --> 0:09:11.560
<v Speaker 1>planning on doing it, but it hasn't talked about what

0:09:11.720 --> 0:09:14.600
<v Speaker 1>that might look like. So you know, you could have

0:09:14.679 --> 0:09:18.720
<v Speaker 1>AI incorporated into very mundane stuff, right, like automating things

0:09:18.720 --> 0:09:22.640
<v Speaker 1>like scheduling and finding the most efficient means to do that,

0:09:23.200 --> 0:09:28.199
<v Speaker 1>which isn't necessarily impacting the creative side of the business

0:09:28.200 --> 0:09:31.439
<v Speaker 1>that much. Right, if you're using it to handle stuff

0:09:31.960 --> 0:09:35.520
<v Speaker 1>that is otherwise tedious and takes up a lot of

0:09:35.559 --> 0:09:40.359
<v Speaker 1>time but is easy enough to automate, that's not necessarily

0:09:40.400 --> 0:09:42.840
<v Speaker 1>a bad thing. That can end up making a company

0:09:42.840 --> 0:09:47.439
<v Speaker 1>more efficient without also displacing employees in the process, or

0:09:47.440 --> 0:09:50.839
<v Speaker 1>at least freeing those employees up to do more rewarding

0:09:50.960 --> 0:09:54.760
<v Speaker 1>work instead of something that's really tedious. The concern is

0:09:54.800 --> 0:09:57.959
<v Speaker 1>whether or not that use of AI could end up

0:09:58.920 --> 0:10:04.120
<v Speaker 1>replacing very important and creative roles for people, whether it's

0:10:04.200 --> 0:10:09.600
<v Speaker 1>actors or writers or imagineers or whomever. So yeah, big

0:10:09.640 --> 0:10:15.480
<v Speaker 1>concern in AI with Disney. Yesterday, Zoom made a change

0:10:15.520 --> 0:10:18.280
<v Speaker 1>to its terms of service after receiving some pretty harsh

0:10:18.280 --> 0:10:23.040
<v Speaker 1>criticism from customers over the weekend. So around Sunday, people

0:10:23.080 --> 0:10:26.160
<v Speaker 1>who were paying attention to zoom terms of service started

0:10:26.200 --> 0:10:29.560
<v Speaker 1>to post screenshots of those terms, and they included a

0:10:29.600 --> 0:10:32.600
<v Speaker 1>passage saying the company has the right to collect, store,

0:10:32.920 --> 0:10:37.400
<v Speaker 1>and use quote unquote service generated data. Now that alone

0:10:38.120 --> 0:10:41.360
<v Speaker 1>seems a bit concerning. Right. Let's say your company uses

0:10:41.440 --> 0:10:44.800
<v Speaker 1>Zoom for business meetings. You probably don't like the idea

0:10:45.280 --> 0:10:49.480
<v Speaker 1>of Zoom potentially snooping in on your calls. On top

0:10:49.520 --> 0:10:51.400
<v Speaker 1>of that, the term said that Zoom could use that

0:10:51.520 --> 0:10:55.839
<v Speaker 1>data essentially to train AI, and that really got people upset.

0:10:56.200 --> 0:10:58.640
<v Speaker 1>The thought that their video calls could be used as

0:10:58.720 --> 0:11:03.559
<v Speaker 1>material to train another aimodel seemed invasive. Now, a Zoom

0:11:03.600 --> 0:11:06.559
<v Speaker 1>rep explained that the collection features are part of an

0:11:06.559 --> 0:11:10.960
<v Speaker 1>opt in system users can choose to enable generative AI

0:11:11.040 --> 0:11:14.840
<v Speaker 1>features such as transcription services, and the company does not

0:11:15.120 --> 0:11:19.959
<v Speaker 1>use any customer content without first gaining the consent from

0:11:20.000 --> 0:11:23.559
<v Speaker 1>the customer. To that end, now, Zoom has updated its

0:11:23.640 --> 0:11:26.880
<v Speaker 1>terms of use to clearly say it will only collect

0:11:26.920 --> 0:11:31.319
<v Speaker 1>audio and video data with consent from the user first.

0:11:31.920 --> 0:11:35.560
<v Speaker 1>In related news, Zoom leadership has also called on Zoom

0:11:35.559 --> 0:11:39.240
<v Speaker 1>employees who live within fifty miles of a Zoom office

0:11:39.960 --> 0:11:43.760
<v Speaker 1>to actually attend work in person at least two days

0:11:43.800 --> 0:11:44.120
<v Speaker 1>a week.

0:11:44.320 --> 0:11:44.920
<v Speaker 2>So that's right.

0:11:45.000 --> 0:11:48.600
<v Speaker 1>The company that made the tool talented as one of

0:11:48.600 --> 0:11:53.600
<v Speaker 1>the most important during lockdown, the one that enabled remote work,

0:11:54.520 --> 0:11:59.720
<v Speaker 1>is now restricting remote work at the corporate level at Zoom,

0:12:00.280 --> 0:12:04.240
<v Speaker 1>which is you know how the tables have turned. I

0:12:04.280 --> 0:12:07.800
<v Speaker 1>guess okay, we're going to take a quick break. When

0:12:07.800 --> 0:12:19.400
<v Speaker 1>we come back, we've got some more tech news. We're back,

0:12:19.480 --> 0:12:23.720
<v Speaker 1>and actually have a couple of other AI stories to

0:12:23.880 --> 0:12:26.880
<v Speaker 1>finish up with before we move on to other tech news,

0:12:27.320 --> 0:12:29.680
<v Speaker 1>so we're not done with AI just yet. AP News

0:12:29.720 --> 0:12:32.520
<v Speaker 1>reports that the folks over at Dungeons and Dragons, you know,

0:12:32.559 --> 0:12:34.840
<v Speaker 1>Wizards of the Coast, which in turn is part of Hasbro,

0:12:35.520 --> 0:12:40.000
<v Speaker 1>are now telling their artists not to use artificial intelligence

0:12:40.360 --> 0:12:43.920
<v Speaker 1>as part of the generative process to create fantasy arts,

0:12:43.920 --> 0:12:47.439
<v Speaker 1>so they're telling the artists, hey, don't use AI when

0:12:47.480 --> 0:12:50.440
<v Speaker 1>you're making art for us. This comes after several D

0:12:50.480 --> 0:12:53.480
<v Speaker 1>and D fans raised questions about an illustration that included

0:12:53.520 --> 0:12:57.520
<v Speaker 1>a giant that they said looked a little weird, like

0:12:57.840 --> 0:13:00.400
<v Speaker 1>perhaps it had not been made by a human being,

0:13:00.960 --> 0:13:03.360
<v Speaker 1>and they asked, hey, was this made by a robot?

0:13:03.600 --> 0:13:04.959
<v Speaker 2>So D and D reached.

0:13:04.679 --> 0:13:08.240
<v Speaker 1>Out and contacted the artist, talked with them, found out

0:13:08.240 --> 0:13:12.280
<v Speaker 1>that yes, there was some use of AI generative features

0:13:12.320 --> 0:13:16.880
<v Speaker 1>to collaborate and make this art, and the company now

0:13:16.960 --> 0:13:19.800
<v Speaker 1>is clarifying rules on what can and cannot be used

0:13:19.800 --> 0:13:23.920
<v Speaker 1>to make fantasy art for the games. The particular piece

0:13:24.160 --> 0:13:28.240
<v Speaker 1>that triggered you folks to ask, is this AI generated

0:13:28.600 --> 0:13:32.079
<v Speaker 1>is actually going to be appearing soon in an expansion

0:13:32.080 --> 0:13:35.560
<v Speaker 1>book called Big Bie Presents Glory of the Giants. I

0:13:35.559 --> 0:13:39.520
<v Speaker 1>think it comes out next week in fact, so maybe

0:13:39.520 --> 0:13:41.640
<v Speaker 1>collectors will rush out and grab a copy in case

0:13:41.679 --> 0:13:45.680
<v Speaker 1>future editions will remove the AI generated giant person. But

0:13:45.760 --> 0:13:48.680
<v Speaker 1>you might ask why is D and D, Why is

0:13:48.720 --> 0:13:52.640
<v Speaker 1>Wizard of the Coast, And perhaps by extension, Hasbro saying

0:13:53.240 --> 0:13:56.080
<v Speaker 1>don't use AI to generate fantasy art. Why is that

0:13:56.120 --> 0:13:59.640
<v Speaker 1>a big deal? Well, part of it is about copyright

0:13:59.720 --> 0:14:03.880
<v Speaker 1>quest like who owns the copyright to a machine generated

0:14:03.920 --> 0:14:07.640
<v Speaker 1>piece of work. Obviously, Wizards of the Coast want to

0:14:07.640 --> 0:14:10.640
<v Speaker 1>be able to copyright their their stuff and not have

0:14:10.760 --> 0:14:14.720
<v Speaker 1>some other party claim ownership of something that's featured in

0:14:14.960 --> 0:14:19.080
<v Speaker 1>a Wizards of the Coast work. But also there's the

0:14:19.240 --> 0:14:25.320
<v Speaker 1>issue of you know, copying another person's style. Right. If

0:14:25.440 --> 0:14:29.600
<v Speaker 1>artist A produces a ton of fantasy art and then

0:14:29.720 --> 0:14:34.800
<v Speaker 1>artist B uses a generative tool that coincidentally is referencing

0:14:35.120 --> 0:14:39.840
<v Speaker 1>artists a work and it's doing so extensively, and then

0:14:39.880 --> 0:14:43.000
<v Speaker 1>creates a new piece in the style of artist A,

0:14:43.200 --> 0:14:46.040
<v Speaker 1>well then it's almost like artist B is copying Artist A.

0:14:46.720 --> 0:14:49.400
<v Speaker 1>And you could argue, well, then that means artist A

0:14:49.480 --> 0:14:52.320
<v Speaker 1>could have landed this gig and gotten a paying gig

0:14:52.320 --> 0:14:56.680
<v Speaker 1>out of it, but instead their work was then you know,

0:14:56.720 --> 0:15:00.920
<v Speaker 1>sort of repurposed and reimagined without their consent. This is

0:15:00.920 --> 0:15:05.560
<v Speaker 1>an ongoing issue with generative AI in the visual arts realm.

0:15:05.800 --> 0:15:09.120
<v Speaker 1>There's also a very similar effect, the same problem that's

0:15:09.160 --> 0:15:13.800
<v Speaker 1>going on within the written word. Right. There are authors

0:15:13.840 --> 0:15:17.640
<v Speaker 1>and poets who are arguing that AI models being trained

0:15:17.720 --> 0:15:24.600
<v Speaker 1>on published works are effectively copying these folks without their consent. So,

0:15:25.400 --> 0:15:29.200
<v Speaker 1>if you'll excuse me, I need to roll to see

0:15:29.200 --> 0:15:33.040
<v Speaker 1>if my AI generated image of an elf will deceive

0:15:33.280 --> 0:15:41.640
<v Speaker 1>Wizards of the Coast and oh, critical fail. Okay, well,

0:15:42.480 --> 0:15:45.640
<v Speaker 1>I guess the fingers are all nudely and there's like

0:15:45.720 --> 0:15:48.440
<v Speaker 1>fifteen of them, so I guess that's a dead giveaway.

0:15:49.120 --> 0:15:49.480
<v Speaker 2>Okay.

0:15:49.960 --> 0:15:52.560
<v Speaker 1>You know a lot of folks have voiced concerns about

0:15:52.600 --> 0:15:56.680
<v Speaker 1>AI and the possible dangers that it could bring, and

0:15:56.760 --> 0:16:00.480
<v Speaker 1>we can now count the Pope as one of those voices.

0:16:00.560 --> 0:16:05.200
<v Speaker 1>Pope Francis has called on a global reflection today that

0:16:05.400 --> 0:16:09.680
<v Speaker 1>is all about how AI could be really dangerous. Pope

0:16:09.680 --> 0:16:12.720
<v Speaker 1>Francis has said in the past he is largely unfamiliar

0:16:12.800 --> 0:16:16.240
<v Speaker 1>with modern technology, including stuff like computers and the Internet,

0:16:16.680 --> 0:16:19.160
<v Speaker 1>but that he also sees that these tools can be

0:16:19.320 --> 0:16:23.400
<v Speaker 1>incredibly helpful when they are put to appropriate use, which

0:16:23.680 --> 0:16:26.560
<v Speaker 1>you know, is a refreshing take from someone who is

0:16:26.680 --> 0:16:31.760
<v Speaker 1>unfamiliar with technology that they recognize tools aren't necessarily good

0:16:31.880 --> 0:16:35.400
<v Speaker 1>or bad in of themselves. It's really all in how

0:16:35.440 --> 0:16:37.840
<v Speaker 1>we make use of those tools, and if we commit

0:16:38.040 --> 0:16:41.400
<v Speaker 1>to using them. In ways that aren't harmful, we can

0:16:41.440 --> 0:16:44.960
<v Speaker 1>see great benefit. But some of these tools like AI,

0:16:45.160 --> 0:16:48.480
<v Speaker 1>for example, have the potential to be very dangerous if

0:16:48.520 --> 0:16:51.960
<v Speaker 1>we are using them improperly or if we don't have

0:16:51.960 --> 0:16:55.040
<v Speaker 1>a full understanding of the consequences before we use them,

0:16:55.280 --> 0:16:58.600
<v Speaker 1>so we have to take extra care when we're working

0:16:58.680 --> 0:17:02.440
<v Speaker 1>with them. It's not that AI is not worthwhile or

0:17:02.640 --> 0:17:07.800
<v Speaker 1>could never do anything positive. That's clearly not the case.

0:17:08.440 --> 0:17:12.000
<v Speaker 1>We just have to be very very methodical in our

0:17:12.080 --> 0:17:14.919
<v Speaker 1>approach to using AI, and right now you could argue

0:17:14.960 --> 0:17:19.199
<v Speaker 1>that is not what we're seeing. Apple has reportedly struck

0:17:19.240 --> 0:17:23.880
<v Speaker 1>a huge deal with chip manufacturer TSMC out of Taiwan

0:17:24.480 --> 0:17:29.040
<v Speaker 1>that will see Apple purchase essentially all of TSMC's chips

0:17:29.080 --> 0:17:33.240
<v Speaker 1>made with their next generation manufacturing process, which is called

0:17:33.240 --> 0:17:38.000
<v Speaker 1>the three nanometer manufacturing process. Just as a reminder, once

0:17:38.080 --> 0:17:41.680
<v Speaker 1>upon a time, when we would use things like nanometer

0:17:41.840 --> 0:17:46.280
<v Speaker 1>to describe the chip manufacturing process that actually referenced the

0:17:46.320 --> 0:17:49.399
<v Speaker 1>size of individual components found on the chips, that you

0:17:49.400 --> 0:17:53.119
<v Speaker 1>would actually see stuff on the chips that measured at

0:17:52.800 --> 0:17:57.240
<v Speaker 1>that unit. But these days it's really just a naming convention.

0:17:57.440 --> 0:18:00.920
<v Speaker 1>It's really just to designate the generation of the chip

0:18:00.960 --> 0:18:04.399
<v Speaker 1>manufacturing process, the individual elements on the chips are not

0:18:04.800 --> 0:18:08.000
<v Speaker 1>three nanometers in size. That would end up being a

0:18:08.040 --> 0:18:12.440
<v Speaker 1>big disaster because of the way quantum physics works. So yeah,

0:18:12.520 --> 0:18:15.879
<v Speaker 1>just a reminder that the whole nanometer thing, it's just

0:18:15.920 --> 0:18:19.160
<v Speaker 1>a naming convention now. It doesn't actually reference anything other

0:18:19.280 --> 0:18:21.560
<v Speaker 1>than this is the newest one and it has to

0:18:21.640 --> 0:18:25.879
<v Speaker 1>keep getting smaller. So it does raise questions of do

0:18:25.960 --> 0:18:29.720
<v Speaker 1>we go down to the atomic scale once we get

0:18:29.760 --> 0:18:35.280
<v Speaker 1>past one nanometer. Anyway, according to the information, Apple has

0:18:35.359 --> 0:18:40.920
<v Speaker 1>essentially ordered every single TSMC three nanometer chip at least

0:18:40.920 --> 0:18:43.600
<v Speaker 1>in the short term, and by short term I mean

0:18:43.760 --> 0:18:48.119
<v Speaker 1>Apple will have exclusive use of chips made by that

0:18:48.160 --> 0:18:52.280
<v Speaker 1>manufacturing process from TSMC for about a year, and that

0:18:52.359 --> 0:18:55.959
<v Speaker 1>definitely gives Apple a leg up on the competition that

0:18:56.080 --> 0:18:59.800
<v Speaker 1>wants to use TSMC's chips. There are other fabricators out there.

0:19:00.119 --> 0:19:02.720
<v Speaker 1>TSMC is not the only game in town. It's just

0:19:02.800 --> 0:19:07.080
<v Speaker 1>the biggest one. Meanwhile, there is a political battle surrounding

0:19:07.119 --> 0:19:11.800
<v Speaker 1>TSMC's planned fabrication facility that would be here in the

0:19:11.880 --> 0:19:16.320
<v Speaker 1>United States, in Arizona. So the Taiwan based company plans

0:19:16.400 --> 0:19:20.000
<v Speaker 1>this fabrication plant in Arizona, but just last month announced

0:19:20.040 --> 0:19:22.800
<v Speaker 1>that there was going to be a construction delay that

0:19:22.920 --> 0:19:27.000
<v Speaker 1>would last until twenty twenty five. The reason being, according

0:19:27.040 --> 0:19:29.639
<v Speaker 1>to the company, is that there are a lack of

0:19:29.800 --> 0:19:32.840
<v Speaker 1>skilled workers here in the US who would be needed

0:19:32.960 --> 0:19:36.760
<v Speaker 1>to prepare and open the facility, not to work once

0:19:36.800 --> 0:19:39.879
<v Speaker 1>it is open, but to actually get everything in place

0:19:39.960 --> 0:19:44.400
<v Speaker 1>as well. They're just the talent isn't here, and instead

0:19:44.480 --> 0:19:48.200
<v Speaker 1>TSMC wants to bring around five hundred employees from Taiwan

0:19:48.800 --> 0:19:52.000
<v Speaker 1>to the United States to do that work instead. That

0:19:52.080 --> 0:19:55.159
<v Speaker 1>has led to US politicians weighing in and they have

0:19:55.359 --> 0:19:59.359
<v Speaker 1>argued that these jobs should go to US workers. Now

0:20:00.359 --> 0:20:03.240
<v Speaker 1>there's a lot going on here, and it gets very

0:20:03.280 --> 0:20:07.119
<v Speaker 1>messy and it gets very political. But from a high level,

0:20:07.520 --> 0:20:12.639
<v Speaker 1>the US decades ago seeded as in got rid of

0:20:12.800 --> 0:20:18.199
<v Speaker 1>pretty much all major chip fabrication because it's expensive. It

0:20:18.280 --> 0:20:21.679
<v Speaker 1>is very expensive to build chip fabrication plants. You have

0:20:21.720 --> 0:20:24.919
<v Speaker 1>to update them constantly because as we were just talking about,

0:20:25.000 --> 0:20:30.320
<v Speaker 1>you're always evolving the technology to make more powerful chips,

0:20:30.880 --> 0:20:33.879
<v Speaker 1>which means you got to retool everything. Sometimes you have

0:20:33.920 --> 0:20:38.240
<v Speaker 1>to build totally new facilities and that's a huge investment

0:20:38.280 --> 0:20:40.439
<v Speaker 1>and a lot of US companies got out of that

0:20:40.520 --> 0:20:44.760
<v Speaker 1>game ages ago, and instead that work went to places

0:20:44.840 --> 0:20:51.800
<v Speaker 1>like Taiwan and TSMC in particular. So because America got

0:20:51.920 --> 0:20:56.239
<v Speaker 1>rid of didn't totally get rid of chip fabrication, but

0:20:56.400 --> 0:20:59.200
<v Speaker 1>largely pushed that out to other places in the world,

0:21:00.280 --> 0:21:03.159
<v Speaker 1>you might say that TSMC could at least have a

0:21:03.200 --> 0:21:06.679
<v Speaker 1>partly legit point to make that the US lacks the

0:21:06.720 --> 0:21:12.040
<v Speaker 1>experts needed to open an advanced fabrication facility simply because

0:21:12.520 --> 0:21:15.320
<v Speaker 1>the US hasn't really been focused on that part of

0:21:15.440 --> 0:21:19.159
<v Speaker 1>chip manufacturing for a while. Yes, in the US you

0:21:19.200 --> 0:21:22.760
<v Speaker 1>have a lot of people developing the next chips, designing

0:21:22.800 --> 0:21:27.159
<v Speaker 1>the next generation of chips, but the actual fabrication is

0:21:27.200 --> 0:21:31.240
<v Speaker 1>taking place elsewhere. So while the expertise is definitely in design,

0:21:32.200 --> 0:21:36.320
<v Speaker 1>the argument is it's not in creating the fabrication facilities,

0:21:36.480 --> 0:21:40.080
<v Speaker 1>and that's where the problem is. On the flip side,

0:21:41.040 --> 0:21:44.520
<v Speaker 1>there's a concern that the reason TSMC really wants to

0:21:44.520 --> 0:21:47.879
<v Speaker 1>bring in Taiwanese workers to the US is not just

0:21:47.960 --> 0:21:51.280
<v Speaker 1>because they have expertise in the area, but also because

0:21:51.280 --> 0:21:55.040
<v Speaker 1>they're less likely to resist a push to work really

0:21:55.119 --> 0:21:59.879
<v Speaker 1>long hours, including working weekends and stuff, whereas US workers

0:22:00.200 --> 0:22:04.240
<v Speaker 1>have this pesky habit of arguing that they need to

0:22:04.280 --> 0:22:07.840
<v Speaker 1>be you know, fairly compensated and have work life balance.

0:22:08.320 --> 0:22:11.239
<v Speaker 1>So in other words, there's a concern that TSMC is

0:22:11.280 --> 0:22:14.560
<v Speaker 1>really looking to exploit a workforce in an effort to

0:22:14.640 --> 0:22:18.520
<v Speaker 1>keep costs down and to speed up building out the facilities.

0:22:19.400 --> 0:22:22.760
<v Speaker 1>As for what happens once the facility opens, TSMC says

0:22:22.800 --> 0:22:26.359
<v Speaker 1>it's committed to providing around twelve thousand jobs and that

0:22:26.520 --> 0:22:29.879
<v Speaker 1>US employees will fill those roles, so that like the

0:22:29.920 --> 0:22:34.119
<v Speaker 1>actual jobs of working at the facility will go to

0:22:34.280 --> 0:22:38.280
<v Speaker 1>US citizens, not you know, it won't be Taiwanese workers

0:22:38.280 --> 0:22:42.119
<v Speaker 1>brought over to do that particular work. So yeah, like

0:22:42.160 --> 0:22:45.240
<v Speaker 1>I said, it is political. There is a technical side

0:22:45.240 --> 0:22:49.480
<v Speaker 1>to it too, but it's messy. And this is why

0:22:49.560 --> 0:22:53.080
<v Speaker 1>you can't just leave politics out of discussions of technology,

0:22:53.440 --> 0:22:57.199
<v Speaker 1>because politics affects us and it affects the tech sector

0:22:57.640 --> 0:23:01.080
<v Speaker 1>a lot. In fact, you know, we can often see

0:23:01.119 --> 0:23:04.120
<v Speaker 1>it most acutely in the tech sector. Not that it's

0:23:04.160 --> 0:23:07.359
<v Speaker 1>not impacting other sectors as well, it's just when it

0:23:07.440 --> 0:23:12.040
<v Speaker 1>hits tech, people take notice because it's high profile stuff.

0:23:12.200 --> 0:23:15.080
<v Speaker 1>So we can't really avoid it here. I don't know

0:23:15.800 --> 0:23:18.080
<v Speaker 1>what the actual story is back here. I mean, it

0:23:18.119 --> 0:23:21.720
<v Speaker 1>may very well be that TSMC could not find the

0:23:21.800 --> 0:23:25.359
<v Speaker 1>talent they needed in order to prepare the fabrication facility

0:23:25.359 --> 0:23:29.040
<v Speaker 1>properly here in the US. Maybe that's true, or maybe

0:23:29.040 --> 0:23:32.800
<v Speaker 1>it's not. I just don't know, but I do know

0:23:32.880 --> 0:23:36.000
<v Speaker 1>that it is an ongoing issue right now. So we'll

0:23:36.040 --> 0:23:40.320
<v Speaker 1>have to see how that plays out in the short term. Okay,

0:23:40.880 --> 0:23:44.080
<v Speaker 1>I got a few more stories to cover, but before

0:23:44.119 --> 0:23:47.080
<v Speaker 1>I can get to that, let's take another quick break.

0:23:56.560 --> 0:23:57.240
<v Speaker 2>We're back.

0:23:57.960 --> 0:24:00.960
<v Speaker 1>Ours Technica has an article about how scientists at the

0:24:01.040 --> 0:24:04.920
<v Speaker 1>Lawrence Livermore National Lab in California have, for the second

0:24:05.000 --> 0:24:10.080
<v Speaker 1>time now, produced a fusion reaction that generated more energy

0:24:10.680 --> 0:24:14.920
<v Speaker 1>than was needed to initiate the reaction. We're gonna put

0:24:14.920 --> 0:24:17.320
<v Speaker 1>an asterisk on that because we're gonna come back to

0:24:17.359 --> 0:24:20.240
<v Speaker 1>it now. I have talked about fusion a lot on

0:24:20.280 --> 0:24:23.479
<v Speaker 1>the show, but just as a quick reminder, fusion occurs

0:24:23.480 --> 0:24:28.000
<v Speaker 1>when you take two lightweight atoms, like hydrogen atoms, for example,

0:24:29.280 --> 0:24:32.000
<v Speaker 1>and then you blast those atoms with enough pressure and

0:24:32.400 --> 0:24:36.040
<v Speaker 1>or energy like heat, in order to.

0:24:35.960 --> 0:24:38.159
<v Speaker 2>Fuse them into a new.

0:24:38.040 --> 0:24:41.919
<v Speaker 1>Atom, helium. In this case, this is what happens in

0:24:42.000 --> 0:24:46.280
<v Speaker 1>the sun. You know, hydrogen is forged into helium at

0:24:46.320 --> 0:24:50.920
<v Speaker 1>a temperature of millions of degrees as how does or

0:24:50.960 --> 0:24:54.480
<v Speaker 1>why does the sunshine would tell us anyway, in this process,

0:24:55.040 --> 0:24:57.480
<v Speaker 1>you also end up with a release of energy, right,

0:24:57.480 --> 0:25:00.320
<v Speaker 1>That's why the sun actually does shine. It's releasing it energy,

0:25:00.359 --> 0:25:03.679
<v Speaker 1>it's not just doing this process. So if you end

0:25:03.760 --> 0:25:07.880
<v Speaker 1>up with more energy than you used to start the reaction,

0:25:08.000 --> 0:25:11.359
<v Speaker 1>you've got a potentially viable alternative to other kinds of

0:25:11.359 --> 0:25:14.200
<v Speaker 1>power facilities, you know, like coal power plants, or even

0:25:14.280 --> 0:25:17.800
<v Speaker 1>things like solar and wind farms, or traditional nuclear power

0:25:17.800 --> 0:25:22.159
<v Speaker 1>plants which rely on nuclear fission. That's the process of

0:25:22.240 --> 0:25:26.840
<v Speaker 1>splitting heavy atoms into lighter atoms, and that also releases

0:25:26.840 --> 0:25:28.720
<v Speaker 1>a huge amount of energy in the process, but that

0:25:29.720 --> 0:25:31.960
<v Speaker 1>also creates things like nuclear waste, which you have to

0:25:31.960 --> 0:25:34.639
<v Speaker 1>figure out how do you process that or deal with

0:25:34.680 --> 0:25:37.239
<v Speaker 1>it or store it. It comes with a lot of

0:25:37.760 --> 0:25:44.679
<v Speaker 1>again political issues that make that technology difficult to pursue.

0:25:45.000 --> 0:25:47.320
<v Speaker 1>Here in Georgia, we actually had a nuclear power plant

0:25:47.320 --> 0:25:50.880
<v Speaker 1>come online for the first time in decades, and it

0:25:50.920 --> 0:25:54.240
<v Speaker 1>was supposed to have been built like fifteen years ago,

0:25:54.280 --> 0:25:57.600
<v Speaker 1>I think at this point somewhere around there. But there

0:25:57.600 --> 0:26:01.840
<v Speaker 1>were so many different delays and then the the cost

0:26:02.040 --> 0:26:06.280
<v Speaker 1>of building out the facility exploded as a result of that.

0:26:06.440 --> 0:26:09.840
<v Speaker 1>So even though the technology is proven, there are a

0:26:09.840 --> 0:26:14.359
<v Speaker 1>lot of drawbacks to nuclear fission. So nuclear fusion could

0:26:15.200 --> 0:26:18.720
<v Speaker 1>be a way to have an alternative that doesn't have

0:26:18.800 --> 0:26:26.960
<v Speaker 1>the same issues that nuclear fission has, but it's hard

0:26:27.000 --> 0:26:29.720
<v Speaker 1>to do so. Researchers have managed to create a few

0:26:29.720 --> 0:26:33.720
<v Speaker 1>fusion reactions over the years, including some uncontrolled ones in

0:26:33.760 --> 0:26:37.840
<v Speaker 1>the testing of the fusion bomb, but typically when you

0:26:37.880 --> 0:26:40.320
<v Speaker 1>were trying to make a fusion reactor for the purposes

0:26:40.320 --> 0:26:43.560
<v Speaker 1>of power generation, the result was that you were getting

0:26:43.720 --> 0:26:46.879
<v Speaker 1>an energy output that was less than the amount of

0:26:47.000 --> 0:26:49.760
<v Speaker 1>energy you were using to initiate the reaction, meaning you're

0:26:49.800 --> 0:26:53.639
<v Speaker 1>operating at a net loss. Right, you're using more energy

0:26:53.680 --> 0:26:56.720
<v Speaker 1>to start a reaction, then you're getting out of the reaction.

0:26:57.160 --> 0:27:00.400
<v Speaker 1>That is not a viable way to generate power lose

0:27:00.520 --> 0:27:05.440
<v Speaker 1>energy in the process. This most recent experiment generated three

0:27:05.560 --> 0:27:09.800
<v Speaker 1>point one five megadewels of energy, and the laser that

0:27:09.920 --> 0:27:14.960
<v Speaker 1>was lasers that were used to initiate this reaction. We're

0:27:15.000 --> 0:27:19.760
<v Speaker 1>blasting a two point oh five megadules amount of energy

0:27:19.880 --> 0:27:22.879
<v Speaker 1>at the fuel, So two point oh five energy is

0:27:22.920 --> 0:27:26.880
<v Speaker 1>hitting the fuel, the reaction generates three point one five

0:27:26.880 --> 0:27:30.119
<v Speaker 1>megadels of energy. That means you're getting about one and

0:27:30.119 --> 0:27:33.880
<v Speaker 1>a half times more energy out than you're putting in

0:27:34.480 --> 0:27:37.199
<v Speaker 1>with the laser. Now, let's go back to that asterisk

0:27:37.280 --> 0:27:41.920
<v Speaker 1>I said about, you know, creating more energy, or not creating,

0:27:41.960 --> 0:27:45.800
<v Speaker 1>but releasing more energy than you're pouring into it. Now,

0:27:45.800 --> 0:27:49.680
<v Speaker 1>the lasers did emit two point oh five megadels of energy. However,

0:27:50.119 --> 0:27:53.440
<v Speaker 1>the draw from the power grid to create those lasers

0:27:54.160 --> 0:27:58.480
<v Speaker 1>was much, much, much larger. So when you step back

0:27:58.520 --> 0:28:00.200
<v Speaker 1>and you say, all right, well how much energy did

0:28:00.200 --> 0:28:02.679
<v Speaker 1>it take for me to make a laser that could

0:28:02.720 --> 0:28:06.440
<v Speaker 1>emit two point zero five megadels of energy, that's where

0:28:06.440 --> 0:28:08.159
<v Speaker 1>you start to see that you're having to use a

0:28:08.160 --> 0:28:11.440
<v Speaker 1>lot more power to get that three point one five

0:28:11.480 --> 0:28:14.520
<v Speaker 1>mega jewels out of the reaction. So that means ultimately

0:28:14.520 --> 0:28:16.360
<v Speaker 1>it's a net loss when you look at it from

0:28:16.400 --> 0:28:21.600
<v Speaker 1>a big picture standpoint. According to Ours Technica, scientists think

0:28:21.640 --> 0:28:24.399
<v Speaker 1>we're going to have to hit energy generation that's around

0:28:24.400 --> 0:28:28.360
<v Speaker 1>thirty to one hundred times more than what the lasers

0:28:28.359 --> 0:28:30.720
<v Speaker 1>are blasting out in order for fusion to be a

0:28:30.840 --> 0:28:31.879
<v Speaker 1>viable power source.

0:28:32.400 --> 0:28:34.400
<v Speaker 2>That is a huge leap from.

0:28:34.200 --> 0:28:35.919
<v Speaker 1>One and a half time, so, which is what we

0:28:35.960 --> 0:28:38.120
<v Speaker 1>saw in this most recent experiment. You know, we have

0:28:38.120 --> 0:28:40.680
<v Speaker 1>to get up to thirty to one hundred times in

0:28:40.760 --> 0:28:44.600
<v Speaker 1>order to reach efficiencies where we're able to get more

0:28:44.720 --> 0:28:47.160
<v Speaker 1>energy out than we put in. Plus we have to

0:28:47.200 --> 0:28:50.760
<v Speaker 1>make it something that can be repeatable rapidly. Right now,

0:28:50.920 --> 0:28:54.720
<v Speaker 1>you're talking about months between experiments at this laboratory. A

0:28:54.840 --> 0:28:56.760
<v Speaker 1>power plant is going to need to do this many

0:28:56.800 --> 0:29:01.400
<v Speaker 1>times a second in order to continue lead generate energy

0:29:01.920 --> 0:29:04.720
<v Speaker 1>for the purposes or release energy. I keep saying generate.

0:29:04.760 --> 0:29:07.200
<v Speaker 1>You know, energy can be neither created nor destroyed. It's

0:29:07.240 --> 0:29:10.800
<v Speaker 1>really just released or converted from one form to another.

0:29:11.280 --> 0:29:11.720
<v Speaker 2>Anyway.

0:29:11.880 --> 0:29:15.160
<v Speaker 1>You would have to make that sustainable in order to

0:29:15.200 --> 0:29:18.440
<v Speaker 1>do things like create electricity for people. Otherwise you would

0:29:18.440 --> 0:29:21.760
<v Speaker 1>just have these spikes and they wouldn't be useful for anything. Yeah,

0:29:21.960 --> 0:29:23.560
<v Speaker 1>you could say like, wow, we generated a ton of

0:29:23.640 --> 0:29:26.800
<v Speaker 1>energy there. We released a huge amount of energy, But

0:29:26.920 --> 0:29:31.120
<v Speaker 1>unless you can make that something that can consistently provide electricity,

0:29:31.480 --> 0:29:34.960
<v Speaker 1>it's not really that useful. However, if we are able

0:29:35.000 --> 0:29:38.200
<v Speaker 1>to crack that code, we would have an incredible future

0:29:38.240 --> 0:29:40.920
<v Speaker 1>ahead of us. So let's hope for it, and let's

0:29:40.960 --> 0:29:43.920
<v Speaker 1>also hope that it's not a perpetual twenty to thirty

0:29:44.000 --> 0:29:47.560
<v Speaker 1>years situation. You know, that's where scientists say we're twenty

0:29:47.560 --> 0:29:50.760
<v Speaker 1>to thirty years out from a technology maturing, but then

0:29:50.880 --> 0:29:53.280
<v Speaker 1>we never get there, like ten years later, we're still

0:29:53.320 --> 0:29:56.000
<v Speaker 1>twenty to thirty years out. Let's hope it's not one

0:29:56.040 --> 0:29:58.760
<v Speaker 1>of those cases. A while back, I talked about how

0:29:58.800 --> 0:30:02.320
<v Speaker 1>Boeing has had to delay testing its Starliner crew vehicle

0:30:03.040 --> 0:30:06.840
<v Speaker 1>with actual, you know, human astronauts after discovering some issues

0:30:07.040 --> 0:30:10.520
<v Speaker 1>with the capsule's design. So, the purpose of the star

0:30:10.680 --> 0:30:14.480
<v Speaker 1>Liner capsule, it's a spacecraft but looks a lot like,

0:30:14.600 --> 0:30:17.560
<v Speaker 1>you know, like the old Apollo capsules. The purpose of

0:30:17.560 --> 0:30:19.880
<v Speaker 1>the star Liner is to serve as a vehicle that

0:30:19.920 --> 0:30:23.600
<v Speaker 1>will take astronauts to and from stuff like the International

0:30:23.600 --> 0:30:27.200
<v Speaker 1>Space Station. Then you would have like the Orion capsule,

0:30:27.240 --> 0:30:30.520
<v Speaker 1>which is larger. This is the one NASA plans to

0:30:30.720 --> 0:30:34.800
<v Speaker 1>use for future Moon missions. However, last month, Boeing had

0:30:34.840 --> 0:30:38.000
<v Speaker 1>to scrap test plans for the star Liner after review

0:30:38.040 --> 0:30:41.200
<v Speaker 1>showed that the capsule's quote unquote soft links in its

0:30:41.200 --> 0:30:45.320
<v Speaker 1>parachute system failed to measure up to NASA's safety requirements.

0:30:45.360 --> 0:30:47.720
<v Speaker 1>So they had to go back to the design board

0:30:47.760 --> 0:30:52.280
<v Speaker 1>and fix that and to replace those soft links, which

0:30:52.560 --> 0:30:56.960
<v Speaker 1>they now have said they've done. Plus, Boeing had used

0:30:57.000 --> 0:31:00.680
<v Speaker 1>some tape in the star Liner's wirings this ms that

0:31:00.840 --> 0:31:03.640
<v Speaker 1>have been flagged as a potential fire hazard that under

0:31:03.680 --> 0:31:09.480
<v Speaker 1>certain conditions they can become flammable. So Boeing has subsequently,

0:31:10.120 --> 0:31:13.240
<v Speaker 1>you know, started to remove all that tape and replace

0:31:13.280 --> 0:31:16.040
<v Speaker 1>it with other stuff. There are a few areas where

0:31:16.080 --> 0:31:19.080
<v Speaker 1>Boeing says that's not feasible to be able to actually

0:31:19.080 --> 0:31:22.080
<v Speaker 1>remove the tape because doing so would damage the vehicle

0:31:22.080 --> 0:31:26.640
<v Speaker 1>in the process. So instead they're coating the tape with

0:31:26.800 --> 0:31:31.120
<v Speaker 1>material that will be fire resistant so that you know,

0:31:31.160 --> 0:31:34.880
<v Speaker 1>it still won't end up causing a potential disastrous fire

0:31:35.120 --> 0:31:39.000
<v Speaker 1>inside the capsule. Now, all of this means that we're

0:31:39.040 --> 0:31:41.440
<v Speaker 1>looking at twenty twenty four at the earliest for a

0:31:41.480 --> 0:31:43.560
<v Speaker 1>test of the Starliner with a crew aboard. That is

0:31:44.160 --> 0:31:47.680
<v Speaker 1>disappointing news for Boeing as well as for NASA, but

0:31:47.760 --> 0:31:51.440
<v Speaker 1>NASA can continue to depend heavily on SpaceX's Dragon two

0:31:51.600 --> 0:31:56.240
<v Speaker 1>vehicle in the meantime. In more optimistic space related news,

0:31:56.600 --> 0:31:59.880
<v Speaker 1>NASA and the Department of Defense performed a recovery test

0:32:00.160 --> 0:32:04.720
<v Speaker 1>for the Orion crew module. So the Orion, like the

0:32:04.920 --> 0:32:09.520
<v Speaker 1>Apollo spacecraft of decades ago, is meant to splash down

0:32:10.040 --> 0:32:13.720
<v Speaker 1>in the ocean, specifically the Pacific Ocean upon returning to Earth.

0:32:14.360 --> 0:32:17.760
<v Speaker 1>Once it splashes down, a retrieval team will then maneuver

0:32:18.240 --> 0:32:22.800
<v Speaker 1>to a few thousand yards of the spacecraft and then

0:32:22.920 --> 0:32:27.080
<v Speaker 1>send retrieval teams to help the four astronauts exit the

0:32:27.160 --> 0:32:30.760
<v Speaker 1>vehicle safely. So this particular test is part of the

0:32:30.920 --> 0:32:34.280
<v Speaker 1>Artemis two mission. Artomis two will send astronauts around the

0:32:34.280 --> 0:32:35.880
<v Speaker 1>back side of the Moon for the first time in

0:32:35.960 --> 0:32:39.640
<v Speaker 1>many many decades. Artemis three is the one where astronauts

0:32:39.680 --> 0:32:42.200
<v Speaker 1>will actually set boots on the Moon for the first

0:32:42.200 --> 0:32:45.240
<v Speaker 1>time in ages. So the goal is to retrieve the

0:32:45.280 --> 0:32:48.360
<v Speaker 1>crew safely in less than two hours after the capsule

0:32:48.360 --> 0:32:51.960
<v Speaker 1>has splashed down in the ocean. The process involves Navy

0:32:52.000 --> 0:32:54.520
<v Speaker 1>divers who first go and check the capsule to make

0:32:54.560 --> 0:32:59.920
<v Speaker 1>sure that it's safe to deploy the raft that's around

0:33:00.240 --> 0:33:04.360
<v Speaker 1>the capsule and for the crew to emerge from the capsule.

0:33:04.920 --> 0:33:08.600
<v Speaker 1>The raft is called the front porch, and it serves

0:33:08.600 --> 0:33:12.040
<v Speaker 1>as a platform for the crew to step out on

0:33:12.040 --> 0:33:15.400
<v Speaker 1>once they leave the capsule, and from that point a

0:33:15.800 --> 0:33:20.280
<v Speaker 1>different retrieval crew will actually fly out to the splash

0:33:20.320 --> 0:33:23.760
<v Speaker 1>site and airlift the Orion crew and then transport them

0:33:23.800 --> 0:33:26.720
<v Speaker 1>back to a recovery ship. Once the crew is safely

0:33:26.760 --> 0:33:31.360
<v Speaker 1>aboard the recovery ship, then engineering teams will connect the

0:33:31.360 --> 0:33:33.920
<v Speaker 1>Orion capsule to the ship so it can be towed

0:33:34.000 --> 0:33:37.280
<v Speaker 1>back to land. So the test was successful, which is

0:33:37.320 --> 0:33:40.560
<v Speaker 1>a good step toward Artemis two. I got a couple

0:33:40.560 --> 0:33:44.320
<v Speaker 1>of article recommendations for you before I sign off. One

0:33:44.560 --> 0:33:48.560
<v Speaker 1>is in the Verge. The article is titled why thread

0:33:48.800 --> 0:33:52.960
<v Speaker 1>is Matter's biggest problem right now, and Jennifer Patson two

0:33:53.000 --> 0:33:56.280
<v Speaker 1>A wrote the piece. This deals with the technologies that

0:33:56.360 --> 0:34:00.840
<v Speaker 1>serve as the foundation for home automation tech and explains

0:34:00.840 --> 0:34:03.280
<v Speaker 1>how some high level decisions are making things perhaps a

0:34:03.280 --> 0:34:07.120
<v Speaker 1>little more complicated instead of simplifying them, which is what

0:34:07.400 --> 0:34:09.960
<v Speaker 1>Matter was really supposed to do. I'll have to do

0:34:10.000 --> 0:34:12.960
<v Speaker 1>a full episode about this in the future, but meanwhile,

0:34:13.040 --> 0:34:15.560
<v Speaker 1>this is a great start if you're wondering why is

0:34:15.600 --> 0:34:19.160
<v Speaker 1>home automation so darn complicated? Why are there so many

0:34:19.560 --> 0:34:24.719
<v Speaker 1>competing different systems using proprietary approaches where you can't have

0:34:24.840 --> 0:34:28.919
<v Speaker 1>interoperability between everything. This is a good way to kind

0:34:28.920 --> 0:34:33.840
<v Speaker 1>of get a ground understanding for that. The second article

0:34:33.880 --> 0:34:37.560
<v Speaker 1>I want to recommend is by Gregory Barber of Wired,

0:34:38.040 --> 0:34:41.680
<v Speaker 1>and it's titled The Cloud is a Prison? Can the

0:34:41.800 --> 0:34:45.520
<v Speaker 1>Local First Software Movement set us Free? So this piece

0:34:45.560 --> 0:34:49.000
<v Speaker 1>talks about how developers and consumers and corporations are grappling

0:34:49.080 --> 0:34:53.239
<v Speaker 1>with issues related to cloud platforms and a movement that

0:34:53.280 --> 0:34:57.400
<v Speaker 1>could potentially bring about an alternative to cloud computing. And

0:34:57.440 --> 0:35:00.640
<v Speaker 1>spoiler alert, it relies on technology that it has actually

0:35:00.719 --> 0:35:04.360
<v Speaker 1>been around for quite some time. But really interesting because

0:35:04.440 --> 0:35:09.000
<v Speaker 1>you know, seeing this this sort of seesaw movement between

0:35:09.280 --> 0:35:15.680
<v Speaker 1>centralized computing, decentralized computing, local computing versus cloud computing. It's

0:35:15.760 --> 0:35:18.160
<v Speaker 1>it's kind of you can start to see patterns in

0:35:18.200 --> 0:35:21.480
<v Speaker 1>the way people are using computers and what they do

0:35:21.560 --> 0:35:25.840
<v Speaker 1>when they encounter challenges in one model versus another. So

0:35:26.200 --> 0:35:28.520
<v Speaker 1>I highly recommend both those articles. As always, I have

0:35:28.600 --> 0:35:31.880
<v Speaker 1>no connection to either of those publications or the authors

0:35:31.920 --> 0:35:32.840
<v Speaker 1>behind those pieces.

0:35:33.200 --> 0:35:34.160
<v Speaker 2>I do not know them.

0:35:34.400 --> 0:35:36.640
<v Speaker 1>I just thought they were interesting and that if you

0:35:36.719 --> 0:35:38.960
<v Speaker 1>are into tech and you really want to learn more,

0:35:39.000 --> 0:35:42.799
<v Speaker 1>those are two good articles to read. Okay, that's it.

0:35:42.840 --> 0:35:45.720
<v Speaker 1>This was a long episode for a news episode. Probably

0:35:45.719 --> 0:35:49.160
<v Speaker 1>means Thursdays will be short. Here's hoping. I hope all

0:35:49.160 --> 0:35:51.560
<v Speaker 1>of you are well and I'll talk to you again

0:35:52.360 --> 0:36:01.640
<v Speaker 1>really soon. Tech Stuff is an eye iHeartRadio production. For

0:36:01.719 --> 0:36:06.600
<v Speaker 1>more podcasts from iHeartRadio, visit the iHeartRadio app, Apple Podcasts,

0:36:06.680 --> 0:36:08.720
<v Speaker 1>or wherever you listen to your favorite shows.