WEBVTT - Tech News: Apple Says AR Will Make You a Better Conversationalist

0:00:04.400 --> 0:00:07.800
<v Speaker 1>Welcome to tech Stuff, a production from I Heart Radio.

0:00:12.080 --> 0:00:14.880
<v Speaker 1>Hey there, and welcome to tech Stuff. I'm your host,

0:00:15.040 --> 0:00:18.280
<v Speaker 1>Jonathan Strickland. I'm an executive producer with I Heart Radio

0:00:18.400 --> 0:00:21.639
<v Speaker 1>and I love all things tech and it is time

0:00:21.840 --> 0:00:27.000
<v Speaker 1>for the tech news for Tuesday, April six, twenty one.

0:00:27.640 --> 0:00:31.720
<v Speaker 1>Let's get at it. In the ongoing story about Amazon

0:00:31.920 --> 0:00:36.120
<v Speaker 1>and the company's efforts to fight against unionization, the US

0:00:36.280 --> 0:00:41.560
<v Speaker 1>National Labor Relations Board ruled against Amazon in a recent claim,

0:00:41.600 --> 0:00:45.319
<v Speaker 1>stating that the company illegally fired two employees who had

0:00:45.360 --> 0:00:48.600
<v Speaker 1>advocated for workers rights and to call the company to

0:00:48.640 --> 0:00:54.160
<v Speaker 1>account for its environmental impact. Marin Costa and Emily Cunningham

0:00:54.400 --> 0:00:58.640
<v Speaker 1>had both criticized their employer publicly before the company fired

0:00:58.880 --> 0:01:03.720
<v Speaker 1>both women, a move that the Labor Board identified as retaliatory.

0:01:03.800 --> 0:01:06.959
<v Speaker 1>Amazon representative J. C. Anderson said that the reason the

0:01:07.000 --> 0:01:10.920
<v Speaker 1>company handed the employees their walking papers wasn't to punish

0:01:10.920 --> 0:01:15.120
<v Speaker 1>them for criticizing Amazon, but rather for a quote, repeatedly

0:01:15.319 --> 0:01:20.120
<v Speaker 1>violating internal policies end quote. However, since at least one

0:01:20.120 --> 0:01:24.120
<v Speaker 1>of those policies seems to be about speaking publicly about

0:01:24.240 --> 0:01:27.720
<v Speaker 1>the business, according to The New York Times, this seems

0:01:27.760 --> 0:01:31.319
<v Speaker 1>like circular logic to me almost like a catch twenty two.

0:01:31.920 --> 0:01:35.200
<v Speaker 1>Sure you can criticize Amazon, it seems to say, but

0:01:35.280 --> 0:01:38.679
<v Speaker 1>if you speak publicly about the business, you've violated an

0:01:38.720 --> 0:01:42.440
<v Speaker 1>internal policy. Criticizing is not against the rules. It's then

0:01:42.760 --> 0:01:46.360
<v Speaker 1>that speaking about the business that is. But that internal

0:01:46.400 --> 0:01:50.120
<v Speaker 1>policy sounds like it is partly designed to protect the

0:01:50.160 --> 0:01:56.640
<v Speaker 1>company from employees criticizing it publicly, at least in any detail. Anyway,

0:01:56.800 --> 0:01:59.680
<v Speaker 1>I admit as always that I am biased when it

0:01:59.720 --> 0:02:01.840
<v Speaker 1>comes to this sort of stuff, as I am pro

0:02:02.080 --> 0:02:06.160
<v Speaker 1>union and in favor of protections that benefit the employee

0:02:06.240 --> 0:02:09.880
<v Speaker 1>over those that cater to the corporation. A couple of

0:02:09.880 --> 0:02:13.320
<v Speaker 1>weeks ago we saw reports about LG getting out of

0:02:13.360 --> 0:02:16.800
<v Speaker 1>the phone business. Now it's official. The company is shutting

0:02:16.800 --> 0:02:20.680
<v Speaker 1>down its smartphone division worldwide. It will continue to sell

0:02:20.680 --> 0:02:23.800
<v Speaker 1>off the inventory that it does have, so all those

0:02:23.840 --> 0:02:26.080
<v Speaker 1>phones made for this year will have to go. And

0:02:26.120 --> 0:02:28.320
<v Speaker 1>it sounds like we are never going to see production

0:02:28.400 --> 0:02:31.959
<v Speaker 1>models of phones like the rollable that was the c

0:02:32.160 --> 0:02:35.320
<v Speaker 1>e s reveal of a smartphone that had a flexible

0:02:35.360 --> 0:02:39.080
<v Speaker 1>oh lad screen, and the rollable could change size. It

0:02:39.120 --> 0:02:41.880
<v Speaker 1>could extend the width of the phone and go from

0:02:42.160 --> 0:02:47.360
<v Speaker 1>a sort of smartphone form factor to fablet sized or

0:02:47.480 --> 0:02:50.960
<v Speaker 1>tablet if you prefer, I definitely prefer The screen could

0:02:51.000 --> 0:02:54.960
<v Speaker 1>actually expand by unrolling from underneath the display you're looking at,

0:02:55.320 --> 0:02:59.280
<v Speaker 1>as these different sides would extend. It was a nifty design,

0:02:59.560 --> 0:03:03.079
<v Speaker 1>but I'm not sure that it was terribly practical. Moving

0:03:03.120 --> 0:03:06.760
<v Speaker 1>parts always represent a potential failure point, and for phones

0:03:07.280 --> 0:03:10.680
<v Speaker 1>which occasionally suffer bumps and falls, I think it would

0:03:10.680 --> 0:03:13.320
<v Speaker 1>have been a bit risky. Plus, if you wanted to

0:03:13.440 --> 0:03:17.240
<v Speaker 1>use the shape changing feature, you presumably wouldn't be able

0:03:17.320 --> 0:03:19.960
<v Speaker 1>to put your phone in a case because the case

0:03:19.960 --> 0:03:22.360
<v Speaker 1>wouldn't be able to change shape. But it was still

0:03:22.400 --> 0:03:25.839
<v Speaker 1>a very neat innovation in the phone space. And now

0:03:25.880 --> 0:03:28.120
<v Speaker 1>we're not really going to see it, but if you

0:03:28.160 --> 0:03:30.520
<v Speaker 1>are in the market for an LG phone, you should

0:03:30.600 --> 0:03:32.960
<v Speaker 1>keep your eyes peeled because we could see some pretty

0:03:33.000 --> 0:03:36.480
<v Speaker 1>aggressive sales in the very near future as they try

0:03:36.480 --> 0:03:40.160
<v Speaker 1>to get rid of that inventory. The Mars Perseverance rover

0:03:40.280 --> 0:03:43.560
<v Speaker 1>has dropped off the Ingenuity copter on the surface of

0:03:43.560 --> 0:03:47.760
<v Speaker 1>the Red planet. You might remember that Ingenuity piggybacked or

0:03:47.880 --> 0:03:52.080
<v Speaker 1>I guess really piggy bellied on the Perseverance and it

0:03:52.160 --> 0:03:56.720
<v Speaker 1>represents a high risk, high reward experiment. Mars is a

0:03:56.720 --> 0:04:00.920
<v Speaker 1>tough neighborhood. The atmosphere is thin, which means the rotors

0:04:01.000 --> 0:04:03.400
<v Speaker 1>on the Ingenuity will have to rotate at a rate

0:04:03.520 --> 0:04:06.680
<v Speaker 1>much higher than would be necessary here on Earth in

0:04:06.800 --> 0:04:09.920
<v Speaker 1>order to generate sufficient lift to get the copter off

0:04:09.960 --> 0:04:13.040
<v Speaker 1>the surface. It will also need to continue to charge

0:04:13.040 --> 0:04:16.919
<v Speaker 1>its batteries. The Perseverance had been providing juice to Ingenuity

0:04:17.000 --> 0:04:21.280
<v Speaker 1>since the Perseverance first touchdown, but now Ingenuity is gonna

0:04:21.279 --> 0:04:23.480
<v Speaker 1>have to use its own solar panels to do the same.

0:04:23.960 --> 0:04:27.279
<v Speaker 1>That electricity isn't just going to power the rotors motor,

0:04:28.160 --> 0:04:31.560
<v Speaker 1>which is a fun thing to say, rotors motor. We

0:04:31.640 --> 0:04:35.000
<v Speaker 1>go ahead, try it anyway. The electricity will also go

0:04:35.160 --> 0:04:39.240
<v Speaker 1>to powering Ingenuitys onboard heater as the temperature on Mars

0:04:39.640 --> 0:04:43.440
<v Speaker 1>plummets at night, it dips down to negative nineties celsius

0:04:43.680 --> 0:04:47.760
<v Speaker 1>or negative one thirty fahrenheit, whichever is greater. I kid,

0:04:47.800 --> 0:04:51.880
<v Speaker 1>they're the same thing. The heater ensures that Ingenuity's mechanical

0:04:51.960 --> 0:04:54.960
<v Speaker 1>parts don't freeze tight, which, as I understand it would

0:04:54.960 --> 0:04:59.719
<v Speaker 1>be somewhat you know, impede flight soon, but no sooner

0:04:59.760 --> 0:05:03.719
<v Speaker 1>than in April eleven, the Ingenuity will attempt its first flight.

0:05:04.200 --> 0:05:07.440
<v Speaker 1>This is really a proof of concept experiment with no

0:05:07.520 --> 0:05:11.480
<v Speaker 1>guarantee of success, but if that first flight does succeed,

0:05:11.760 --> 0:05:14.120
<v Speaker 1>NASA hopes to do a few more, as many as

0:05:14.200 --> 0:05:17.919
<v Speaker 1>four more before ingenuityes batteries are drained to the point

0:05:18.000 --> 0:05:20.920
<v Speaker 1>that it will just need to settle down on Mars

0:05:21.040 --> 0:05:23.960
<v Speaker 1>make a life for itself however it can, or rather

0:05:24.040 --> 0:05:27.200
<v Speaker 1>it'll sit on Mars and rest in a job well

0:05:27.240 --> 0:05:31.320
<v Speaker 1>done and collect dust for the rest of Eternity. Will

0:05:31.360 --> 0:05:34.440
<v Speaker 1>follow up on this once we hear about the first

0:05:34.480 --> 0:05:38.640
<v Speaker 1>attempts and how they panned out. Sticking with space, a

0:05:38.680 --> 0:05:41.760
<v Speaker 1>farmer in the United States and fact in the state

0:05:41.760 --> 0:05:44.880
<v Speaker 1>of Washington got a surprise last week when a piece

0:05:44.960 --> 0:05:49.039
<v Speaker 1>of a rocket ship landed on their farm. Last Thursday,

0:05:49.240 --> 0:05:53.039
<v Speaker 1>the second stage from a SpaceX Falcon nine entered into

0:05:53.080 --> 0:05:57.480
<v Speaker 1>an uncontrolled descent into the Earth's atmosphere after an otherwise

0:05:57.520 --> 0:06:02.360
<v Speaker 1>successful launch. The Falcon nine is a two stage launch vehicle,

0:06:02.720 --> 0:06:05.800
<v Speaker 1>and the first stage, the lower stage, is the one

0:06:05.880 --> 0:06:08.120
<v Speaker 1>that is supposed to return to Earth in a controlled

0:06:08.200 --> 0:06:11.920
<v Speaker 1>landing procedure, so that the stage can then be refurbished

0:06:11.960 --> 0:06:15.400
<v Speaker 1>and reused, which cuts way down on launch costs, But

0:06:15.560 --> 0:06:20.039
<v Speaker 1>the upper stage, the second stage, isn't so lucky. Typically

0:06:20.360 --> 0:06:23.120
<v Speaker 1>it has one of two fates. It's either pushed into

0:06:23.160 --> 0:06:25.680
<v Speaker 1>an orbit where it's going to stick around in orbit

0:06:25.760 --> 0:06:31.400
<v Speaker 1>for a while before eventually falling to Earth, or more frequently,

0:06:31.760 --> 0:06:34.400
<v Speaker 1>it is pushed so it de orbits in a controlled

0:06:34.520 --> 0:06:37.799
<v Speaker 1>manner and breaks up over the ocean. But this time

0:06:37.920 --> 0:06:41.279
<v Speaker 1>the second stage lacked enough fuel to do the ocean thing,

0:06:41.720 --> 0:06:44.760
<v Speaker 1>so instead it fell a bit short and broke up

0:06:44.760 --> 0:06:48.200
<v Speaker 1>over the Pacific Northwest. In the US. It was quite

0:06:48.240 --> 0:06:51.599
<v Speaker 1>the display, and people all in the northwestern part of

0:06:51.640 --> 0:06:56.280
<v Speaker 1>North America reported seeing multiple shooting stars. These were pieces

0:06:56.279 --> 0:06:59.120
<v Speaker 1>of the second stage glowing as they fell back to Earth,

0:06:59.560 --> 0:07:02.200
<v Speaker 1>and one such piece made it intact all the way

0:07:02.240 --> 0:07:05.839
<v Speaker 1>down to the ground on this farm in Washington. While

0:07:05.880 --> 0:07:08.680
<v Speaker 1>we knew about the re entry from last week, this

0:07:08.720 --> 0:07:12.400
<v Speaker 1>bit about the piece making it down to the surface

0:07:12.400 --> 0:07:15.560
<v Speaker 1>of Earth is new now. Apparently it's part of a

0:07:15.600 --> 0:07:19.400
<v Speaker 1>pressurized tank which is no longer pressurized. I guess I

0:07:19.400 --> 0:07:22.880
<v Speaker 1>should add it landed in Grant County, Washington, and that

0:07:23.080 --> 0:07:26.200
<v Speaker 1>is as specific as we can get about it. Because

0:07:26.200 --> 0:07:29.800
<v Speaker 1>the Sheriff's office wisely decided to leave out more details

0:07:30.040 --> 0:07:34.040
<v Speaker 1>in order to spare the farmer from locky lose. Google

0:07:34.080 --> 0:07:37.840
<v Speaker 1>has made a big change to its policy regarding Android apps,

0:07:37.960 --> 0:07:41.040
<v Speaker 1>but it might surprise some folks like like me to

0:07:41.160 --> 0:07:44.880
<v Speaker 1>learn about the implications of it. So there's a command

0:07:45.080 --> 0:07:49.520
<v Speaker 1>called query all packages, and this allows an app that's

0:07:49.560 --> 0:07:52.320
<v Speaker 1>installed on an Android device to get a list of

0:07:52.360 --> 0:07:55.280
<v Speaker 1>all the other apps that are installed on that device.

0:07:55.920 --> 0:07:58.520
<v Speaker 1>And that seems like that could be a little excessive

0:07:58.560 --> 0:08:00.840
<v Speaker 1>at least in some cases, right I mean, for example,

0:08:01.240 --> 0:08:04.080
<v Speaker 1>if you have an app that gives you a weather report,

0:08:04.480 --> 0:08:08.160
<v Speaker 1>should that weather report app also see which games you

0:08:08.200 --> 0:08:11.440
<v Speaker 1>have on your phone? Or if your apps related to

0:08:11.520 --> 0:08:14.760
<v Speaker 1>stuff like banking or your personal health or a real

0:08:14.920 --> 0:08:18.080
<v Speaker 1>estate app or whatever are also on that phone? Because

0:08:18.080 --> 0:08:22.480
<v Speaker 1>that that seems like that that's probably not necessary, right Well, Google,

0:08:22.520 --> 0:08:24.960
<v Speaker 1>after more than a decade, seems to have reached the

0:08:25.080 --> 0:08:29.600
<v Speaker 1>same conclusion. Now for devices running on Android eleven or later,

0:08:29.840 --> 0:08:32.400
<v Speaker 1>and all apps coming out from this point forward half

0:08:32.480 --> 0:08:36.400
<v Speaker 1>to target Android eleven or later. These apps can't just

0:08:36.480 --> 0:08:41.640
<v Speaker 1>have blanket access to the query all packages command. Developers

0:08:41.840 --> 0:08:44.679
<v Speaker 1>will have to defend why their app would need that

0:08:44.800 --> 0:08:47.640
<v Speaker 1>level of access, and in some cases you can make

0:08:47.679 --> 0:08:51.239
<v Speaker 1>an argument for it. For example, I have a password

0:08:51.360 --> 0:08:54.320
<v Speaker 1>vault app on my phone, and if I want that

0:08:54.360 --> 0:08:57.880
<v Speaker 1>app to work alongside other apps so that when I

0:08:57.880 --> 0:09:00.320
<v Speaker 1>open up some other app that requires a pass I

0:09:00.320 --> 0:09:04.360
<v Speaker 1>can use this little option to just fill it out automatically,

0:09:04.920 --> 0:09:07.800
<v Speaker 1>like say a banking app. Well, then the password vault

0:09:07.920 --> 0:09:09.640
<v Speaker 1>is going to need to know what other apps are

0:09:09.720 --> 0:09:13.280
<v Speaker 1>running on my device so that that interoperability will work.

0:09:13.840 --> 0:09:17.120
<v Speaker 1>But I probably don't need a food delivery service app

0:09:17.240 --> 0:09:20.880
<v Speaker 1>and a podcatching app to know about each other. That's

0:09:20.880 --> 0:09:24.600
<v Speaker 1>probably not necessary. So this change means that developers will

0:09:24.840 --> 0:09:28.200
<v Speaker 1>no longer know quite as much about the apps that

0:09:28.240 --> 0:09:31.800
<v Speaker 1>their users have on their phones, which isn't necessarily a

0:09:31.840 --> 0:09:35.400
<v Speaker 1>bad thing for the users. It cuts down opportunities for

0:09:35.440 --> 0:09:39.080
<v Speaker 1>developers to target people directly without their permission, or sell

0:09:39.120 --> 0:09:41.880
<v Speaker 1>information about them, and so forth. I think it's a

0:09:41.920 --> 0:09:45.520
<v Speaker 1>long overdue move on Google's part, and I am glad

0:09:45.559 --> 0:09:48.200
<v Speaker 1>that it's finally happening. I'm just surprised it took this

0:09:48.280 --> 0:09:52.080
<v Speaker 1>long to happen. Kara Swisher conducted an interview with Apple

0:09:52.200 --> 0:09:55.440
<v Speaker 1>CEO Tim Cook for The New York Times recently, and

0:09:55.640 --> 0:09:59.160
<v Speaker 1>in that interview, Cook talked a bit about how Apple

0:09:59.360 --> 0:10:02.400
<v Speaker 1>used the proces spect of augmented reality. He said that

0:10:02.800 --> 0:10:06.640
<v Speaker 1>a R could enhance conversations and give people the chance

0:10:06.679 --> 0:10:11.400
<v Speaker 1>to integrate other stuff into live conversation. For example, maybe

0:10:11.400 --> 0:10:13.840
<v Speaker 1>you're arguing with that friend of yours who just refuses

0:10:13.880 --> 0:10:16.559
<v Speaker 1>to admit that they are totally full of crap, and

0:10:16.640 --> 0:10:19.480
<v Speaker 1>you could pull up charts and graphs to back up

0:10:19.480 --> 0:10:22.520
<v Speaker 1>your point showing that they are in fact full of crap.

0:10:22.960 --> 0:10:24.839
<v Speaker 1>It sounds like a lot of fun to me that

0:10:25.000 --> 0:10:28.200
<v Speaker 1>conversations will be way better in the future. I also

0:10:28.240 --> 0:10:31.840
<v Speaker 1>don't anticipate a ARE applications being a threat to security

0:10:32.000 --> 0:10:36.880
<v Speaker 1>or privacy at all. I'm sure they're perfectly safe. Now.

0:10:36.920 --> 0:10:39.720
<v Speaker 1>I've been on the record as being pro a R,

0:10:40.000 --> 0:10:43.559
<v Speaker 1>but it's within specific contexts. I actually get a bit

0:10:43.640 --> 0:10:46.280
<v Speaker 1>squeamish when we talk about a R as a component

0:10:46.840 --> 0:10:50.480
<v Speaker 1>in person to person interactions. Sure, it could be helpful

0:10:50.520 --> 0:10:53.079
<v Speaker 1>if while chatting with a friend, I get a little

0:10:53.120 --> 0:10:57.520
<v Speaker 1>digital reminder in my view that says that this friend's

0:10:57.520 --> 0:11:01.319
<v Speaker 1>birthday is coming up, or maybe they've got a dietary sensitivity,

0:11:01.360 --> 0:11:04.959
<v Speaker 1>and since we're talking about restaurants, it's just reminding me

0:11:05.000 --> 0:11:06.960
<v Speaker 1>of that, so I don't end up making, you know,

0:11:07.240 --> 0:11:11.760
<v Speaker 1>suggestions that wouldn't apply or whatever. But you could see

0:11:11.760 --> 0:11:16.000
<v Speaker 1>where that stuff could actually really go wrong very quickly. Granted,

0:11:16.440 --> 0:11:19.800
<v Speaker 1>this is not the use case that Cook was making

0:11:19.880 --> 0:11:22.680
<v Speaker 1>to care Swisher, and you can make a very valid

0:11:22.760 --> 0:11:26.800
<v Speaker 1>argument that I am creating a sort of straw man argument.

0:11:27.160 --> 0:11:31.120
<v Speaker 1>I just see it as a potential slippery slope. And

0:11:31.280 --> 0:11:34.320
<v Speaker 1>let's face it, having a conversation with me is already

0:11:34.360 --> 0:11:38.120
<v Speaker 1>boring enough without me bringing charts and a bibliography into it.

0:11:38.880 --> 0:11:41.520
<v Speaker 1>I just think of all those online message boards that

0:11:41.559 --> 0:11:44.520
<v Speaker 1>are full of people demanding that other folks cite their

0:11:44.559 --> 0:11:47.760
<v Speaker 1>sources and stuff like that, and how that could become

0:11:48.280 --> 0:11:50.959
<v Speaker 1>a part of conversations moving forward, and that all of

0:11:51.000 --> 0:11:52.560
<v Speaker 1>that just makes me want to go back to bed.

0:11:53.720 --> 0:11:57.200
<v Speaker 1>A blind woman will receive one point one million dollars

0:11:57.240 --> 0:12:01.040
<v Speaker 1>in damages after having Uber driver's ditcher and her service

0:12:01.080 --> 0:12:05.480
<v Speaker 1>dog on fourteen different occasions, leaving her stranded and preventing

0:12:05.480 --> 0:12:09.520
<v Speaker 1>her from getting to important events and destinations, including just

0:12:09.600 --> 0:12:13.800
<v Speaker 1>getting to her office to do work. In sixteen, Uber

0:12:13.880 --> 0:12:16.719
<v Speaker 1>reached a two point six million dollar settlement for a

0:12:16.800 --> 0:12:20.600
<v Speaker 1>similar legal case, but some of the incidents that this

0:12:20.640 --> 0:12:26.439
<v Speaker 1>particular woman, Lisa Irving experienced happened after that settlement was reached,

0:12:26.640 --> 0:12:31.200
<v Speaker 1>which showed that Uber hadn't actually addressed the underlying problem.

0:12:31.240 --> 0:12:34.880
<v Speaker 1>It represents discrimination against Irving because of her blindness, which

0:12:35.000 --> 0:12:39.240
<v Speaker 1>is against the law. Irving will receive around three twenty

0:12:39.320 --> 0:12:42.319
<v Speaker 1>four thousand dollars. The rest of that one point one

0:12:42.360 --> 0:12:48.080
<v Speaker 1>million is going to cover legal fees. This illustrates why

0:12:48.200 --> 0:12:51.960
<v Speaker 1>the system in America is kind of screwy, because big

0:12:52.000 --> 0:12:55.200
<v Speaker 1>companies can afford to go through this sort of thing.

0:12:55.320 --> 0:12:58.920
<v Speaker 1>It takes a lot for a private citizen to take

0:12:58.920 --> 0:13:02.560
<v Speaker 1>on a big company a lawsuit. Uber has since created

0:13:02.640 --> 0:13:05.360
<v Speaker 1>a support form that customers can fill out should they

0:13:05.400 --> 0:13:08.800
<v Speaker 1>experience similar issues in the future. Doesn't prevent it from happening,

0:13:09.120 --> 0:13:14.360
<v Speaker 1>but it gives customers a chance to specifically address UH

0:13:15.080 --> 0:13:18.160
<v Speaker 1>an instance of the problem. And the very first question

0:13:18.200 --> 0:13:20.960
<v Speaker 1>asks if a writer was denied a ride because of

0:13:21.000 --> 0:13:25.480
<v Speaker 1>a service animal. So not truly a solution, but at

0:13:25.520 --> 0:13:30.560
<v Speaker 1>least a move to try and address the issue. And finally,

0:13:30.760 --> 0:13:35.520
<v Speaker 1>The Independent reports that researchers at Brown University have created

0:13:35.600 --> 0:13:39.920
<v Speaker 1>a brain computer interface with wireless connectivity. And what's more,

0:13:40.200 --> 0:13:44.520
<v Speaker 1>they say that this interface provides quote single neuron resolution

0:13:44.640 --> 0:13:49.719
<v Speaker 1>and full broadband fidelity end quote. Brain computer interfaces are

0:13:49.800 --> 0:13:53.440
<v Speaker 1>fascinating devices now. As the name indicates, this is a

0:13:53.440 --> 0:13:56.720
<v Speaker 1>technology that allows a person to interact with a computer

0:13:56.800 --> 0:14:01.640
<v Speaker 1>system through thought alone. It's like having telepathy that works

0:14:01.640 --> 0:14:07.880
<v Speaker 1>with computers. And typically this procedure includes intercranial surgery and

0:14:08.440 --> 0:14:13.080
<v Speaker 1>doctors have to implant electrodes into the brain of the recipient,

0:14:13.520 --> 0:14:16.920
<v Speaker 1>which is an incredibly invasive procedure obviously, and it has

0:14:16.960 --> 0:14:21.280
<v Speaker 1>its own set of risks, including potential infection, which is

0:14:21.280 --> 0:14:25.600
<v Speaker 1>a huge risk factor. So this process is required in

0:14:25.680 --> 0:14:29.000
<v Speaker 1>order to get very precise readings on brain activity, because

0:14:29.000 --> 0:14:32.040
<v Speaker 1>our skulls make it a bit tricky to detect brain

0:14:32.080 --> 0:14:35.880
<v Speaker 1>waves with accuracy unless we're actively in an f M

0:14:36.040 --> 0:14:40.240
<v Speaker 1>R I machine or something like that. In addition, we

0:14:40.360 --> 0:14:44.160
<v Speaker 1>usually see these technologies in the form of wired connections

0:14:44.200 --> 0:14:48.640
<v Speaker 1>between the interface that's attached to a patient and the

0:14:48.720 --> 0:14:53.560
<v Speaker 1>related computer system they communicate with, and that creates more limitations.

0:14:53.600 --> 0:14:56.760
<v Speaker 1>So this new approach removes the need for those physical wires.

0:14:56.760 --> 0:15:00.480
<v Speaker 1>There could be wireless communication between patient and computer, which

0:15:00.560 --> 0:15:04.200
<v Speaker 1>the researchers say opens up new possibilities and use cases.

0:15:04.680 --> 0:15:07.760
<v Speaker 1>Getting a system like this to work requires a lot

0:15:07.800 --> 0:15:11.560
<v Speaker 1>of adjustments because you're training a patient on how to

0:15:11.640 --> 0:15:16.400
<v Speaker 1>use the technology, but you're simultaneously training the technology to

0:15:16.600 --> 0:15:20.440
<v Speaker 1>learn how the patient thinks. The interface software has to

0:15:20.520 --> 0:15:24.120
<v Speaker 1>learn how to interpret brain waves and map those brain

0:15:24.200 --> 0:15:28.080
<v Speaker 1>waves to specific outcomes. It's a fascinating area of research

0:15:28.120 --> 0:15:31.200
<v Speaker 1>and development, and the researchers hope that by removing these

0:15:31.240 --> 0:15:34.000
<v Speaker 1>tethers they will be able to create more scenarios in

0:15:34.040 --> 0:15:37.960
<v Speaker 1>which they can have more examples and gather more data

0:15:38.040 --> 0:15:42.040
<v Speaker 1>and learn more about brain computer interactions and thus designed

0:15:42.080 --> 0:15:47.400
<v Speaker 1>better algorithms to create more seamless connectivity, ultimately giving paralyzed

0:15:47.400 --> 0:15:52.280
<v Speaker 1>patients more agency and communication capabilities. By the way, there

0:15:52.280 --> 0:15:55.080
<v Speaker 1>are also private companies and a lot of business folks

0:15:55.280 --> 0:15:59.360
<v Speaker 1>who are also researching this technology, though arguably for less

0:15:59.400 --> 0:16:03.800
<v Speaker 1>noble reasons. I personally remain convinced that Elon Musk is

0:16:03.840 --> 0:16:07.360
<v Speaker 1>mostly looking to find some sort of electronic means to

0:16:07.440 --> 0:16:12.160
<v Speaker 1>preserve his consciousness indefinitely. For example, it's just a feeling

0:16:12.200 --> 0:16:15.240
<v Speaker 1>I get and again, I have a bias, and it

0:16:15.320 --> 0:16:17.720
<v Speaker 1>really comes out in these New News episodes, doesn't it.

0:16:17.800 --> 0:16:22.040
<v Speaker 1>I make no apologies for it. It's who I am,

0:16:22.080 --> 0:16:25.160
<v Speaker 1>but draw your own conclusions. I'm not saying that I

0:16:25.200 --> 0:16:28.240
<v Speaker 1>am correct in this, It's just the feeling I get,

0:16:28.760 --> 0:16:32.880
<v Speaker 1>and I fully admit I could be wrong. But that

0:16:32.920 --> 0:16:37.240
<v Speaker 1>wraps up the news for April six one, and I

0:16:37.280 --> 0:16:39.840
<v Speaker 1>hope you are all doing well. If you have any

0:16:39.920 --> 0:16:42.760
<v Speaker 1>suggestions for things I should cover on future episodes of

0:16:42.800 --> 0:16:45.560
<v Speaker 1>tech Stuff, reach out to me on Twitter. The handle

0:16:45.600 --> 0:16:49.000
<v Speaker 1>we use is text stuff H s W and I'll

0:16:49.000 --> 0:16:57.840
<v Speaker 1>talk to you again really soon. Text Stuff is an

0:16:57.840 --> 0:17:01.520
<v Speaker 1>I Heart Radio production. For more podcasts from my Heart Radio,

0:17:01.880 --> 0:17:05.040
<v Speaker 1>visit the i Heart Radio app, Apple Podcasts, or wherever

0:17:05.119 --> 0:17:11.200
<v Speaker 1>you listen to your favorite shows. H