WEBVTT - TechStuff Tidbits: Biometrics

0:00:04.440 --> 0:00:12.320
<v Speaker 1>Welcome to tech Stuff, a production from iHeartRadio. Hey there,

0:00:12.360 --> 0:00:16.120
<v Speaker 1>and welcome to tech Stuff. I'm your host, Jonathan Strickland.

0:00:16.160 --> 0:00:19.639
<v Speaker 1>I'm an executive producer with iHeartRadio. And how the tech

0:00:19.720 --> 0:00:22.639
<v Speaker 1>are you? You know, I'm sure you've all seen movies

0:00:22.800 --> 0:00:25.920
<v Speaker 1>which someone has to get past a security system by

0:00:26.040 --> 0:00:29.960
<v Speaker 1>having an eye scan, and maybe they have an unconscious

0:00:30.080 --> 0:00:35.440
<v Speaker 1>or potentially unalive security guard laying nearby and they hold

0:00:35.440 --> 0:00:38.320
<v Speaker 1>the person's head up to the scanner to gain access

0:00:38.360 --> 0:00:42.199
<v Speaker 1>to the security door. Or maybe the main character has

0:00:42.280 --> 0:00:47.280
<v Speaker 1>undergone some sort of incredibly disturbing surgical procedure to have

0:00:47.360 --> 0:00:50.559
<v Speaker 1>their own eyes altered to give them access. But you

0:00:50.600 --> 0:00:53.320
<v Speaker 1>get the idea. The eye scan verifies that the person

0:00:53.400 --> 0:00:57.320
<v Speaker 1>trying to open the door has the authorization to do that.

0:00:57.880 --> 0:01:01.600
<v Speaker 1>This is a form a biometric and I'm sure we're

0:01:01.640 --> 0:01:06.600
<v Speaker 1>all familiar with biometrics. You probably use them regularly. If

0:01:06.600 --> 0:01:09.679
<v Speaker 1>you have a phone that has a fingerprint scanner or

0:01:09.720 --> 0:01:14.440
<v Speaker 1>a face scanner to unlock the phone, that's biometrics. I

0:01:14.520 --> 0:01:17.039
<v Speaker 1>used to use a laptop that had a fingerprint scanner,

0:01:17.440 --> 0:01:20.120
<v Speaker 1>which was kind of cool. It made it really easy

0:01:20.200 --> 0:01:25.600
<v Speaker 1>for me to log in. Not necessarily the most secure technology. However,

0:01:25.760 --> 0:01:30.080
<v Speaker 1>as I remember reading about how that particular fingerprint scanner

0:01:30.160 --> 0:01:34.240
<v Speaker 1>had some issues, but it's still sure made logging into

0:01:34.240 --> 0:01:36.800
<v Speaker 1>my computer easy back in those days. My current one

0:01:36.840 --> 0:01:40.200
<v Speaker 1>does not have that. And there are actually a couple

0:01:40.240 --> 0:01:44.039
<v Speaker 1>of different definitions for biometrics, but the one we're concerned

0:01:44.080 --> 0:01:49.000
<v Speaker 1>about involves body and behavioral measurements for the purposes of

0:01:49.200 --> 0:01:55.240
<v Speaker 1>authentication and verification or identification, because these are all related

0:01:55.320 --> 0:01:58.680
<v Speaker 1>but different things. So for this to work, the stuff

0:01:58.840 --> 0:02:02.280
<v Speaker 1>what we're measuring has to be unique to an individual.

0:02:02.680 --> 0:02:05.800
<v Speaker 1>It needs to be something that cannot be easily replicated.

0:02:06.440 --> 0:02:08.679
<v Speaker 1>That's the whole point, right. If it could be replicated,

0:02:09.600 --> 0:02:13.360
<v Speaker 1>then it's no good for verifying someone or identifying someone

0:02:13.560 --> 0:02:16.960
<v Speaker 1>because it could be one of many people. So you

0:02:17.000 --> 0:02:20.040
<v Speaker 1>need to have something that is unique to that person.

0:02:20.760 --> 0:02:23.920
<v Speaker 1>Spoiler alert. While biometrics can be used for the purposes

0:02:23.919 --> 0:02:28.760
<v Speaker 1>of security, for verification or identification, it's also pretty darn

0:02:28.800 --> 0:02:32.320
<v Speaker 1>handy if you just want to keep track of someone, right,

0:02:33.000 --> 0:02:35.720
<v Speaker 1>so you get enough biometric data on a person, it

0:02:35.720 --> 0:02:38.600
<v Speaker 1>becomes easier to track that person down to keep track

0:02:38.600 --> 0:02:42.000
<v Speaker 1>of what they're doing, assuming that they're not like hold

0:02:42.080 --> 0:02:44.560
<v Speaker 1>up in some off grid shack in the middle of

0:02:44.600 --> 0:02:47.840
<v Speaker 1>nowhere and they never venture out of there, in which case, yeah,

0:02:47.960 --> 0:02:50.400
<v Speaker 1>they can be under the radar then, but otherwise it

0:02:50.440 --> 0:02:54.000
<v Speaker 1>gets pretty tricky. But before we get into all that

0:02:54.280 --> 0:02:57.280
<v Speaker 1>and the concerns around biometrics, let's talk a little bit

0:02:57.440 --> 0:03:02.840
<v Speaker 1>about the history of biometrics. This history is varied, It

0:03:02.880 --> 0:03:05.840
<v Speaker 1>goes all over the place. It has lots of starts

0:03:05.840 --> 0:03:09.880
<v Speaker 1>and stops and stutters, and that's because biometrics focuses on

0:03:09.960 --> 0:03:12.880
<v Speaker 1>lots of different things, right Like, it's not all just

0:03:13.520 --> 0:03:16.720
<v Speaker 1>one area of study. Typically we're talking about things that

0:03:16.760 --> 0:03:22.840
<v Speaker 1>people were interested in studying or advancing that collectively we

0:03:22.919 --> 0:03:26.040
<v Speaker 1>would categorize under biometrics, but they were looking at a

0:03:26.120 --> 0:03:30.079
<v Speaker 1>very specific version of it. So you could argue that

0:03:30.280 --> 0:03:33.680
<v Speaker 1>biometrics traces its history to more than twenty five hundred

0:03:33.720 --> 0:03:38.000
<v Speaker 1>years ago. Because Babylonians back in the day, which I'm

0:03:38.040 --> 0:03:42.240
<v Speaker 1>told was a Tuesday, would sign off on business transactions

0:03:42.600 --> 0:03:46.440
<v Speaker 1>by placing a thumb print on a clay tablet. Right

0:03:46.600 --> 0:03:50.480
<v Speaker 1>that the clay tablet would be pliable, you would PLoP

0:03:50.480 --> 0:03:53.560
<v Speaker 1>your thumb down and make an impression. The tablet would

0:03:53.640 --> 0:03:56.000
<v Speaker 1>dry and your print would be there to authenticate that

0:03:56.040 --> 0:04:00.080
<v Speaker 1>you had, in fact completed whatever the transaction was. Bo

0:04:00.640 --> 0:04:04.440
<v Speaker 1>that's biometrics, and Tom Cruise wasn't even involved a little bit.

0:04:05.080 --> 0:04:07.280
<v Speaker 1>I always think of Tom Cruise in movies like the

0:04:07.320 --> 0:04:10.800
<v Speaker 1>Mission Impossible series, or even in Minority Report. When I

0:04:10.840 --> 0:04:13.080
<v Speaker 1>think about biometrics, those are the ones that pop up

0:04:13.080 --> 0:04:16.280
<v Speaker 1>in my head. Of course, it's not like there was

0:04:16.320 --> 0:04:20.720
<v Speaker 1>a direct line of evolution from the ancient Babylonians to

0:04:20.720 --> 0:04:23.440
<v Speaker 1>Tom Cruise, at least not that I am aware of.

0:04:23.960 --> 0:04:27.560
<v Speaker 1>Biometrics weren't always a common means of marking documents or

0:04:27.560 --> 0:04:31.600
<v Speaker 1>anything like that. But by the late nineteenth century, some

0:04:31.640 --> 0:04:34.760
<v Speaker 1>folks started to figure out that the Babylonians could have

0:04:34.800 --> 0:04:38.720
<v Speaker 1>really been onto something. Actually, I'm kidding. They probably didn't

0:04:38.720 --> 0:04:41.160
<v Speaker 1>even know about the Babylonian stuff. They just thought they

0:04:41.200 --> 0:04:44.359
<v Speaker 1>came up with it themselves. Because typically that's how we

0:04:44.440 --> 0:04:48.640
<v Speaker 1>see the smarty pants of the eighteenth and nineteenth centuries.

0:04:49.200 --> 0:04:52.080
<v Speaker 1>Some of them were a little more humble than that,

0:04:52.600 --> 0:04:56.560
<v Speaker 1>but not all of them. Anyway, Folks in the late

0:04:56.640 --> 0:04:59.440
<v Speaker 1>nineteenth century, so we're talking the eighteen hundreds here, they

0:04:59.480 --> 0:05:02.720
<v Speaker 1>observe that fingerprints appeared to be unique to the individual,

0:05:03.040 --> 0:05:05.640
<v Speaker 1>and if you got two different people to make prints

0:05:05.680 --> 0:05:08.680
<v Speaker 1>of their fingertips. You would see the differences in the

0:05:08.720 --> 0:05:11.200
<v Speaker 1>patterns of those fingerprints, and you would be able to

0:05:11.240 --> 0:05:14.960
<v Speaker 1>tell which person made which set of prints, assuming that

0:05:15.000 --> 0:05:17.360
<v Speaker 1>you had a reference right, as long as you're able

0:05:17.400 --> 0:05:20.919
<v Speaker 1>to refer it back to something on record. This logically

0:05:21.480 --> 0:05:24.200
<v Speaker 1>led to the concept of using fingerprints as a way

0:05:24.240 --> 0:05:27.200
<v Speaker 1>to identify if a suspect had been present at the

0:05:27.240 --> 0:05:29.760
<v Speaker 1>scene of a crime. Of course, folks had to figure

0:05:29.800 --> 0:05:34.159
<v Speaker 1>out how to detect and lift prints at the scene. Typically,

0:05:34.240 --> 0:05:38.000
<v Speaker 1>they would use a very fine powder or dust which

0:05:38.000 --> 0:05:41.840
<v Speaker 1>would adhere to the oils left behind from the fingertips

0:05:41.880 --> 0:05:44.960
<v Speaker 1>on different surfaces, and then they would lift those prints

0:05:45.000 --> 0:05:49.080
<v Speaker 1>and then compare that to a record of fingerprints so

0:05:49.080 --> 0:05:51.480
<v Speaker 1>that they could reference the prints that were lifted at

0:05:51.480 --> 0:05:55.160
<v Speaker 1>the scene with ones that were in their database the

0:05:55.279 --> 0:05:58.799
<v Speaker 1>reference system, or if they had the suspect in custody,

0:05:59.040 --> 0:06:02.599
<v Speaker 1>they would have the suspect, you know, get printed, and

0:06:02.600 --> 0:06:04.880
<v Speaker 1>they would compare the prints against whatever was found at

0:06:04.880 --> 0:06:07.440
<v Speaker 1>the scene and then try to determine if the suspect

0:06:07.480 --> 0:06:10.520
<v Speaker 1>was actually present at the scene of the crime. You

0:06:10.600 --> 0:06:14.840
<v Speaker 1>know how this works, But the science of that and

0:06:14.960 --> 0:06:18.040
<v Speaker 1>the systems based around that took a while to develop.

0:06:18.720 --> 0:06:21.440
<v Speaker 1>Folks had to identify the elements and fingerprints that are

0:06:21.560 --> 0:06:27.280
<v Speaker 1>definable and identifiable. They had to make classifications and taxonomies.

0:06:27.440 --> 0:06:29.560
<v Speaker 1>You know, you had to have a way to communicate

0:06:30.240 --> 0:06:33.400
<v Speaker 1>the qualities of a print when talking with someone else,

0:06:33.720 --> 0:06:35.640
<v Speaker 1>or to be able to look for a match or

0:06:35.720 --> 0:06:38.880
<v Speaker 1>even just a partial match. And it took a couple

0:06:38.880 --> 0:06:42.880
<v Speaker 1>of decades to really catch on. And while fingerprints are

0:06:43.080 --> 0:06:47.320
<v Speaker 1>the most famous example of early biometrics and law enforcement,

0:06:47.720 --> 0:06:50.880
<v Speaker 1>police were trying different stuff too. In France, around the

0:06:50.880 --> 0:06:54.159
<v Speaker 1>same time as fingerprints coming into vogue, there was a

0:06:54.200 --> 0:06:59.880
<v Speaker 1>system called the Bertilline process or Bertillion process. The police

0:07:00.120 --> 0:07:04.120
<v Speaker 1>would measure suspects and they would write down their measurements

0:07:04.160 --> 0:07:07.120
<v Speaker 1>on a card and keep that in an index. And

0:07:07.200 --> 0:07:09.880
<v Speaker 1>I'm talking all sorts of measurements. You know. It's kind

0:07:09.880 --> 0:07:12.120
<v Speaker 1>of like if you were to go and get fitted

0:07:12.200 --> 0:07:16.720
<v Speaker 1>for custom clothing, except you're being fitted for crimes, I guess.

0:07:16.880 --> 0:07:19.680
<v Speaker 1>So the police would take down stuff like how tall

0:07:19.720 --> 0:07:22.680
<v Speaker 1>you were, you know, how wide were your shoulders, how

0:07:22.760 --> 0:07:26.440
<v Speaker 1>long are your arms, all that kind of stuff. This

0:07:26.560 --> 0:07:30.000
<v Speaker 1>approach had some big drawbacks, however, the biggest one being

0:07:30.000 --> 0:07:33.440
<v Speaker 1>that there was a lack of standardization in technique and metrics,

0:07:33.960 --> 0:07:37.520
<v Speaker 1>which meant it wasn't terribly useful. Because if one police

0:07:37.520 --> 0:07:42.240
<v Speaker 1>officer measures arm length one way, let's say, like they

0:07:42.280 --> 0:07:45.960
<v Speaker 1>measure the arm just hanging down from the shoulder, and

0:07:46.040 --> 0:07:48.000
<v Speaker 1>someone else measures it in a different way, like you're

0:07:48.000 --> 0:07:51.160
<v Speaker 1>holding your arm up at an angle, then you might

0:07:51.240 --> 0:07:55.280
<v Speaker 1>end up getting very different you know, metrics measurements. And

0:07:55.320 --> 0:07:57.720
<v Speaker 1>that meant that you would look at the index card

0:07:57.720 --> 0:07:59.680
<v Speaker 1>and say, oh, well, this person's not a match. That's

0:07:59.720 --> 0:08:02.720
<v Speaker 1>not who who this person is or whatever, And so

0:08:03.240 --> 0:08:07.040
<v Speaker 1>it was not terribly useful, and you could get false

0:08:07.080 --> 0:08:11.000
<v Speaker 1>positives or false negatives. So this particular method wouldn't stand

0:08:11.000 --> 0:08:15.680
<v Speaker 1>the test of time. Fingerprints definitely did. In the nineteen thirties,

0:08:15.880 --> 0:08:18.520
<v Speaker 1>a guy named Frank Birch had another idea for using

0:08:18.560 --> 0:08:23.400
<v Speaker 1>biometrics as a way to identify people. He was an ophthalmologist, that,

0:08:23.440 --> 0:08:25.360
<v Speaker 1>by the way, is a great word that trips me

0:08:25.440 --> 0:08:29.520
<v Speaker 1>up in spelling bees, and you might imagine. His idea

0:08:29.720 --> 0:08:34.280
<v Speaker 1>was that an individual's iris contains complex patterns, and those

0:08:34.320 --> 0:08:37.479
<v Speaker 1>patterns are unique to that person. It's like a fingerprint,

0:08:37.480 --> 0:08:40.280
<v Speaker 1>but it's the pattern that's in the iris of your eye,

0:08:40.800 --> 0:08:43.840
<v Speaker 1>and so like a fingerprint, a person's iris could serve

0:08:43.920 --> 0:08:47.280
<v Speaker 1>as a way to identify that person and subsequently verify

0:08:47.320 --> 0:08:50.120
<v Speaker 1>their identity in the future. You just needed a way

0:08:50.160 --> 0:08:53.640
<v Speaker 1>to capture those patterns and then a technology capable of

0:08:53.720 --> 0:08:58.160
<v Speaker 1>scanning and matching patterns against those that are stored in

0:08:58.160 --> 0:09:02.120
<v Speaker 1>a database. So in twenty six when Frank Birch came

0:09:02.200 --> 0:09:05.080
<v Speaker 1>up with this idea, none of that was really practical

0:09:05.160 --> 0:09:09.480
<v Speaker 1>or possible, but his basic concept using the eye as

0:09:09.480 --> 0:09:13.959
<v Speaker 1>a way to verify identity, that was solid. Now, it

0:09:13.960 --> 0:09:16.520
<v Speaker 1>would take more than fifty years before someone would come

0:09:16.559 --> 0:09:19.880
<v Speaker 1>up with a computer algorithm that could identify iris patterns

0:09:20.360 --> 0:09:23.920
<v Speaker 1>and moreover, match an IRIS pattern that is collected to

0:09:24.000 --> 0:09:27.120
<v Speaker 1>one in a database. That came to us courtesy of

0:09:27.200 --> 0:09:32.160
<v Speaker 1>Cambridge University professor John Dogman in nineteen eighty seven, and

0:09:32.240 --> 0:09:35.400
<v Speaker 1>it took a few more years to actually capitalize on

0:09:35.440 --> 0:09:38.640
<v Speaker 1>that development. It wasn't until the mid nineteen nineties that

0:09:38.720 --> 0:09:42.760
<v Speaker 1>a company called Iridium Technologies became the first to commercialize

0:09:42.800 --> 0:09:46.720
<v Speaker 1>iris scanning. Now there are lots of companies that do this,

0:09:47.160 --> 0:09:49.920
<v Speaker 1>many with their own proprietary approach to doing it, but

0:09:50.160 --> 0:09:53.360
<v Speaker 1>it's all rooted in Frank Birch's suggestions back in the

0:09:53.440 --> 0:09:57.080
<v Speaker 1>nineteen thirties. Okay, we've got a lot more to talk

0:09:57.120 --> 0:10:00.240
<v Speaker 1>about with biometrics before we get into that. Let's take

0:10:00.280 --> 0:10:13.439
<v Speaker 1>a quick break. You know, not long ago I talked

0:10:13.440 --> 0:10:15.720
<v Speaker 1>a little bit about the early days of researchers trying

0:10:15.760 --> 0:10:21.720
<v Speaker 1>to use computers to develop facial recognition technology, another example

0:10:21.760 --> 0:10:26.160
<v Speaker 1>of biometrics. So the pioneers in that space included Woody Bledsoe,

0:10:26.440 --> 0:10:31.000
<v Speaker 1>a mathematician and computer scientist, Helen chan Wolf, a scientist

0:10:31.080 --> 0:10:35.360
<v Speaker 1>specializing in early artificial intelligence work, and Charles Bisson, another

0:10:35.640 --> 0:10:40.320
<v Speaker 1>computer scientist and the three word for panoramic research in California.

0:10:40.440 --> 0:10:42.200
<v Speaker 1>And they set about trying to figure out how to

0:10:42.320 --> 0:10:46.200
<v Speaker 1>break down facial features into data points that a computer

0:10:46.320 --> 0:10:50.040
<v Speaker 1>could analyze and match. So, you know, you imagined that

0:10:50.080 --> 0:10:52.760
<v Speaker 1>at first, this just looks and involves looking at pictures

0:10:52.760 --> 0:10:56.280
<v Speaker 1>of people and saying, well, where are some ways that

0:10:56.320 --> 0:10:59.320
<v Speaker 1>we can we can point out, like landmarks that a

0:10:59.400 --> 0:11:03.480
<v Speaker 1>computer would be able to recognize and measure against, right,

0:11:04.080 --> 0:11:07.080
<v Speaker 1>like the corners of eyes compared to the bridge of

0:11:07.080 --> 0:11:09.160
<v Speaker 1>the nose, that kind of stuff. And there are all

0:11:09.200 --> 0:11:12.480
<v Speaker 1>these different images of pictures of people with all these

0:11:12.559 --> 0:11:16.439
<v Speaker 1>different lines geometric lines drawn on the faces in an

0:11:16.440 --> 0:11:21.480
<v Speaker 1>effort to kind of establish these standards. And as you

0:11:21.520 --> 0:11:24.560
<v Speaker 1>might imagine, in the early days, this technology hit some

0:11:24.600 --> 0:11:28.960
<v Speaker 1>pretty tough limitations. A computer couldn't necessarily match two different

0:11:28.960 --> 0:11:32.880
<v Speaker 1>pictures of the same person's face. If the lighting and

0:11:32.920 --> 0:11:36.040
<v Speaker 1>the shadows or the angle of the picture were different enough,

0:11:36.360 --> 0:11:38.920
<v Speaker 1>the computer system would have trouble determining that both images

0:11:38.920 --> 0:11:41.360
<v Speaker 1>were of the same face. Yes, if you had two

0:11:41.400 --> 0:11:45.000
<v Speaker 1>pictures of the same person where it was under identical

0:11:45.080 --> 0:11:48.240
<v Speaker 1>lighting conditions and the camera was at the same distance

0:11:48.280 --> 0:11:51.680
<v Speaker 1>in the same angle, then it was easier, But with

0:11:51.840 --> 0:11:55.880
<v Speaker 1>any deviation from that it became much more difficult. It

0:11:55.880 --> 0:11:59.920
<v Speaker 1>would take many years for the algorithms, the computer technology,

0:12:00.160 --> 0:12:03.280
<v Speaker 1>camera technologies to improve to a point that made facial

0:12:03.320 --> 0:12:07.840
<v Speaker 1>recognition a possibility. So we're going to skip way up

0:12:07.880 --> 0:12:10.719
<v Speaker 1>to the present day, and we've talked extensively on this

0:12:10.840 --> 0:12:14.360
<v Speaker 1>show about how facial recognition technology often has major issues,

0:12:14.400 --> 0:12:18.000
<v Speaker 1>particularly when it comes to false positives and false negatives

0:12:18.000 --> 0:12:21.319
<v Speaker 1>with certain populations. Now, I'm not going to dive into

0:12:21.320 --> 0:12:23.280
<v Speaker 1>that whole can of worms yet again, because I'm sure

0:12:23.280 --> 0:12:24.960
<v Speaker 1>most of you have heard me talk about it a lot,

0:12:25.440 --> 0:12:30.080
<v Speaker 1>but it is an inescapable fact that most facial recognition

0:12:30.160 --> 0:12:33.680
<v Speaker 1>systems are prone to making errors due to biases that

0:12:33.720 --> 0:12:35.840
<v Speaker 1>are in the system. And just to be clear, I

0:12:35.880 --> 0:12:39.800
<v Speaker 1>don't mean to imply that there was ever any intentional bias,

0:12:40.400 --> 0:12:45.920
<v Speaker 1>but intentional or not, that bias still has an effect. Meanwhile,

0:12:45.960 --> 0:12:49.760
<v Speaker 1>other computer scientists were working in the mid twentieth century

0:12:50.120 --> 0:12:54.520
<v Speaker 1>on the challenge of developing speech recognition technologies. Now, like

0:12:54.600 --> 0:12:58.800
<v Speaker 1>facial recognition, this tech had a steep barrier of entry.

0:12:59.320 --> 0:13:04.599
<v Speaker 1>Voices come in all sorts of timbers, volumes, pitches, dialects,

0:13:04.679 --> 0:13:08.240
<v Speaker 1>or accents. So two people might say the very same

0:13:08.280 --> 0:13:12.600
<v Speaker 1>word in very different ways. You know, it may sound

0:13:12.760 --> 0:13:14.640
<v Speaker 1>very different, and yet it's the same word, And that

0:13:14.760 --> 0:13:18.520
<v Speaker 1>means the system needs to be capable of recognizing that

0:13:18.559 --> 0:13:21.480
<v Speaker 1>word no matter who says it or how they say it.

0:13:21.720 --> 0:13:25.079
<v Speaker 1>Otherwise you're not going to have a satisfying experience. Well,

0:13:25.080 --> 0:13:27.760
<v Speaker 1>folks in Bell Labs were working on speech recognition tech

0:13:27.800 --> 0:13:30.880
<v Speaker 1>as early as the nineteen fifties, but that work focused

0:13:30.880 --> 0:13:34.119
<v Speaker 1>on training a machine to recognize when someone was speaking

0:13:34.320 --> 0:13:38.640
<v Speaker 1>out numbers. It took a decade of hard work to

0:13:38.679 --> 0:13:41.800
<v Speaker 1>get to a point where the computer systems could recognize

0:13:42.000 --> 0:13:45.600
<v Speaker 1>words of a certain complexity. The nineteen seventies would see

0:13:45.600 --> 0:13:49.360
<v Speaker 1>the technology advanced significantly, helped in large part by a

0:13:49.559 --> 0:13:53.600
<v Speaker 1>DARPA initiative. Y'all remember DARPA, right, that's the division within

0:13:53.679 --> 0:13:56.679
<v Speaker 1>the US Department of Defense that awards contracts to companies

0:13:56.960 --> 0:13:59.800
<v Speaker 1>that engage in R and D, and it's all in

0:13:59.840 --> 0:14:03.359
<v Speaker 1>the purpose of trying to fund projects that could potentially

0:14:03.400 --> 0:14:07.559
<v Speaker 1>benefit US defense initiatives in the future. DARPA has funded

0:14:07.640 --> 0:14:12.560
<v Speaker 1>research into everything from autonomous vehicles to robots capable of

0:14:12.559 --> 0:14:16.040
<v Speaker 1>performing half a dozen different tasks, and in the seventies,

0:14:16.320 --> 0:14:21.440
<v Speaker 1>the division funded work in speech recognition. But speech recognition

0:14:22.000 --> 0:14:28.680
<v Speaker 1>is really related to using voice technology for the purposes

0:14:28.720 --> 0:14:32.960
<v Speaker 1>of a computer understanding what someone is saying. There's also

0:14:33.880 --> 0:14:40.200
<v Speaker 1>voice recognition, or some people prefer speaker recognition, because that's

0:14:40.240 --> 0:14:46.480
<v Speaker 1>all about recognizing a specific person. So speech recognition is

0:14:46.520 --> 0:14:49.800
<v Speaker 1>really more about computer systems that can parse what you're

0:14:49.840 --> 0:14:53.880
<v Speaker 1>saying and glean instructions from that and respond properly so

0:14:53.920 --> 0:14:56.960
<v Speaker 1>that when you ask your smart speaker about the weather,

0:14:57.120 --> 0:14:59.160
<v Speaker 1>it can give you the information you want instead of

0:14:59.200 --> 0:15:01.640
<v Speaker 1>I don't knowtaneously turning off all the lights in your

0:15:01.640 --> 0:15:07.040
<v Speaker 1>house or whatever, not that I've had that experience. Voice

0:15:07.080 --> 0:15:11.240
<v Speaker 1>recognition or speaker recognition involves breaking a specific voice into

0:15:11.320 --> 0:15:14.360
<v Speaker 1>data points for the purposes of identification, just like with

0:15:14.480 --> 0:15:18.000
<v Speaker 1>facial recognition. Right. So, the idea of developing a system

0:15:18.040 --> 0:15:22.440
<v Speaker 1>to do serious analysis on voices dates back to the

0:15:22.560 --> 0:15:26.400
<v Speaker 1>early twentieth century. However, a lot of that early work

0:15:26.520 --> 0:15:31.840
<v Speaker 1>lacked scientific value or rigor. So while you had people saying, yes,

0:15:31.880 --> 0:15:35.920
<v Speaker 1>I can get a print out of what someone's voices

0:15:36.000 --> 0:15:38.040
<v Speaker 1>and thus be able to compare two print outs and

0:15:38.040 --> 0:15:39.960
<v Speaker 1>tell you if it's the same person speaking or not,

0:15:40.440 --> 0:15:43.520
<v Speaker 1>in truth, it was a bit more complicated than that.

0:15:43.720 --> 0:15:46.760
<v Speaker 1>I mean, you know, it required more than just having

0:15:46.880 --> 0:15:54.600
<v Speaker 1>a long strip of paper tape pulled across a pencil that,

0:15:54.720 --> 0:15:58.080
<v Speaker 1>in turn was connected to a diaphragm that would cause

0:15:58.160 --> 0:16:01.720
<v Speaker 1>vibrations to move through when sound would go through like

0:16:02.880 --> 0:16:07.800
<v Speaker 1>a horn or a microphone. Yeah, you could create a

0:16:07.920 --> 0:16:11.280
<v Speaker 1>visual representation of someone's voice that way, but it wasn't

0:16:11.480 --> 0:16:14.320
<v Speaker 1>something that was specific enough for you to be able

0:16:14.360 --> 0:16:19.320
<v Speaker 1>to differentiate that voice from another voice or even sometimes

0:16:19.400 --> 0:16:23.440
<v Speaker 1>other noises entirely, like you might get a record of

0:16:23.960 --> 0:16:26.520
<v Speaker 1>noise that is not a voice at all, but because

0:16:26.560 --> 0:16:30.160
<v Speaker 1>it looks kind of like what someone else produced when

0:16:30.160 --> 0:16:31.720
<v Speaker 1>they were speaking into it, you might think, oh, it

0:16:31.760 --> 0:16:35.600
<v Speaker 1>was this person. It would take years to get to

0:16:35.680 --> 0:16:39.920
<v Speaker 1>a more sophisticated approach to speech analysis and voice analysis

0:16:40.440 --> 0:16:45.480
<v Speaker 1>to approach the possibility of identifying someone based on their voice.

0:16:45.920 --> 0:16:50.280
<v Speaker 1>In the nineteen forties, folks learned about a sound spectrograph technology.

0:16:50.440 --> 0:16:52.680
<v Speaker 1>So this is a device that would create a visual

0:16:52.720 --> 0:16:56.880
<v Speaker 1>representation of a signal. Sound spectrograph being sound. We're talking

0:16:56.880 --> 0:16:59.280
<v Speaker 1>about audio in this case, but you can have spectrographs

0:16:59.280 --> 0:17:02.440
<v Speaker 1>that create a visual representation of lots of different types

0:17:02.480 --> 0:17:06.320
<v Speaker 1>of signals. This is just specifically about audio. Some people

0:17:06.359 --> 0:17:09.400
<v Speaker 1>would refer to these as voice prints. They would compare

0:17:09.440 --> 0:17:13.159
<v Speaker 1>this to a fingerprint, saying, oh, this representation shows the

0:17:13.240 --> 0:17:15.920
<v Speaker 1>quality of this person's voice. If we find a match,

0:17:16.040 --> 0:17:18.080
<v Speaker 1>then that's the same person. It's just like a fingerprint.

0:17:18.440 --> 0:17:21.600
<v Speaker 1>The people who were actually working in the field really

0:17:21.640 --> 0:17:24.640
<v Speaker 1>didn't use the term voice print very much, if at all,

0:17:25.040 --> 0:17:26.600
<v Speaker 1>but it was a term that was used a lot

0:17:26.640 --> 0:17:30.280
<v Speaker 1>in the media, and I think a lot of folks

0:17:30.320 --> 0:17:33.159
<v Speaker 1>who were working in the field were frustrated because they

0:17:33.160 --> 0:17:36.040
<v Speaker 1>felt it was a bit reductive and an oversimplification of

0:17:36.080 --> 0:17:39.640
<v Speaker 1>what they were doing. So a slightly more acceptable term

0:17:39.760 --> 0:17:43.679
<v Speaker 1>is what I've referenced earlier, speaker recognition. This implies the

0:17:43.680 --> 0:17:47.560
<v Speaker 1>technology isn't necessarily trying to understand what someone is saying.

0:17:48.320 --> 0:17:52.200
<v Speaker 1>Instead is trying to identify the person who is saying it,

0:17:52.760 --> 0:17:55.359
<v Speaker 1>or verifying that the person who is saying it is

0:17:55.400 --> 0:17:58.400
<v Speaker 1>who they claimed to be. You might use this technology

0:17:59.119 --> 0:18:04.159
<v Speaker 1>to have someone get access to something secret, right, like

0:18:04.520 --> 0:18:07.000
<v Speaker 1>the voice print analysis. You've seen this in movies too,

0:18:07.000 --> 0:18:09.880
<v Speaker 1>where someone walks up to a door and they say

0:18:09.920 --> 0:18:14.920
<v Speaker 1>a phrase and then apparently the computer inside the door

0:18:15.359 --> 0:18:18.600
<v Speaker 1>and analyzes the voice and then either allows entry or

0:18:18.640 --> 0:18:21.760
<v Speaker 1>denies it. Or you might use it to try and

0:18:21.800 --> 0:18:25.560
<v Speaker 1>identify somebody, right, maybe you've got a recording of someone.

0:18:25.600 --> 0:18:29.439
<v Speaker 1>Maybe someone calls into a television station and makes a threat.

0:18:29.880 --> 0:18:33.199
<v Speaker 1>This has happened, and then what you're trying to do

0:18:33.320 --> 0:18:37.480
<v Speaker 1>is identify a suspect you have found and to determine

0:18:37.480 --> 0:18:39.000
<v Speaker 1>whether or not they were the person who made the

0:18:39.040 --> 0:18:41.240
<v Speaker 1>phone call, and you're trying to match the voices together.

0:18:41.800 --> 0:18:44.440
<v Speaker 1>This is something that's been going on in law enforcement

0:18:44.520 --> 0:18:48.320
<v Speaker 1>for decades and for a very long time. Courts would

0:18:48.800 --> 0:18:55.760
<v Speaker 1>reject the evidence presented because there was a lack of

0:18:55.800 --> 0:19:00.920
<v Speaker 1>scientific studies showing the accuracy and reliability of this kind

0:19:00.920 --> 0:19:04.119
<v Speaker 1>of approach, and you needed to show that there was

0:19:04.160 --> 0:19:09.439
<v Speaker 1>a scientific basis for this and not just a claim

0:19:09.600 --> 0:19:13.800
<v Speaker 1>that these two voices must be identical. The technology involves

0:19:14.000 --> 0:19:18.960
<v Speaker 1>sophisticated pattern analysis and it is really tricky. So those

0:19:19.040 --> 0:19:21.520
<v Speaker 1>early court cases, it's probably a good idea to throw

0:19:21.560 --> 0:19:25.640
<v Speaker 1>those cases out. Now, maybe some guilty people went free.

0:19:26.160 --> 0:19:30.359
<v Speaker 1>It's hard to say, but the fact is we just

0:19:30.400 --> 0:19:33.359
<v Speaker 1>weren't at a level of sophistication a pattern analysis to

0:19:33.359 --> 0:19:37.560
<v Speaker 1>be able to have really reliable identification. These days, there

0:19:37.560 --> 0:19:41.920
<v Speaker 1>are examples of speaker recognition technology built into consumer products.

0:19:42.359 --> 0:19:47.840
<v Speaker 1>My smart speaker at home supposedly recognizes my voice, for example,

0:19:48.080 --> 0:19:50.160
<v Speaker 1>and this should make it possible for me to ask

0:19:50.200 --> 0:19:54.640
<v Speaker 1>about my daily schedule, and because the speaker recognizes that

0:19:54.680 --> 0:19:58.359
<v Speaker 1>the user is yours, truly, it could then cross reference

0:19:58.440 --> 0:20:01.520
<v Speaker 1>my calendar and then tell me what my schedule is,

0:20:01.960 --> 0:20:03.679
<v Speaker 1>or at least it's supposed to be able to do that.

0:20:04.200 --> 0:20:06.720
<v Speaker 1>I don't know. I mean, it's probably because I never

0:20:06.760 --> 0:20:09.000
<v Speaker 1>put anything in my calendar. I'm really bad about doing that.

0:20:09.160 --> 0:20:11.600
<v Speaker 1>So really, my speaker just gets fed up with me

0:20:11.840 --> 0:20:15.760
<v Speaker 1>because I'm asking it to do something it really cannot do.

0:20:16.560 --> 0:20:18.359
<v Speaker 1>All right, we're gonna take another quick break. When we

0:20:18.400 --> 0:20:20.200
<v Speaker 1>come back, I'm going to talk a little bit more

0:20:20.200 --> 0:20:25.760
<v Speaker 1>about some other biometric approaches and also about a current

0:20:25.840 --> 0:20:30.720
<v Speaker 1>story that really inspired this entire episode and the different

0:20:30.880 --> 0:20:34.600
<v Speaker 1>sides to that story. But first let's take another quick break.

0:20:43.720 --> 0:20:45.720
<v Speaker 1>Before the break, I alluded to the fact that there

0:20:45.760 --> 0:20:50.639
<v Speaker 1>are other approaches to biometric verification or identification. So another

0:20:50.680 --> 0:20:55.679
<v Speaker 1>one is gate recognition GAI. This is the way someone

0:20:55.800 --> 0:20:59.760
<v Speaker 1>moves through a space, like things like the length of

0:20:59.800 --> 0:21:04.480
<v Speaker 1>their stride, the position of their body as they are walking,

0:21:05.040 --> 0:21:08.000
<v Speaker 1>the location of various body parts in relation to one another,

0:21:08.119 --> 0:21:12.119
<v Speaker 1>like how far are your hips from your knees or

0:21:12.160 --> 0:21:14.919
<v Speaker 1>your knees from your ankles, that sort of thing, what

0:21:15.080 --> 0:21:18.119
<v Speaker 1>sort of how much do you bend when you're moving.

0:21:19.280 --> 0:21:22.600
<v Speaker 1>So it is possible to analyze how a person naturally

0:21:22.800 --> 0:21:27.560
<v Speaker 1>walks or moves through space and then to use that

0:21:27.600 --> 0:21:32.880
<v Speaker 1>information to identify someone. So if you have reference data

0:21:33.119 --> 0:21:36.800
<v Speaker 1>where you know how a person typically walks, then you

0:21:36.880 --> 0:21:39.639
<v Speaker 1>might be able to use that in when you're searching

0:21:39.640 --> 0:21:42.520
<v Speaker 1>for somebody. A person could be trying to evade surveillance,

0:21:42.560 --> 0:21:46.359
<v Speaker 1>for example, through the use of disguises, but gate analysis

0:21:46.440 --> 0:21:49.359
<v Speaker 1>might reveal who they really are, assuming you've got reference

0:21:49.480 --> 0:21:52.720
<v Speaker 1>data as well. I've seen movies that do this where

0:21:52.720 --> 0:21:55.960
<v Speaker 1>it's a person who's just watching like a video feed.

0:21:56.000 --> 0:21:58.720
<v Speaker 1>They're saying, ah, I see they have a limp, and

0:21:59.040 --> 0:22:01.679
<v Speaker 1>you know, we know so and so favors their right legs,

0:22:01.680 --> 0:22:04.240
<v Speaker 1>so I think we've got the person here. Like we've

0:22:04.240 --> 0:22:06.639
<v Speaker 1>seen that sort of thing. It's the same basic idea,

0:22:06.680 --> 0:22:08.800
<v Speaker 1>except you don't have to have a limp. It's really

0:22:08.920 --> 0:22:13.040
<v Speaker 1>just all the basic movements you make that end up

0:22:13.280 --> 0:22:16.600
<v Speaker 1>kind of being unique to you. You can try and

0:22:16.640 --> 0:22:20.000
<v Speaker 1>disguise that. Obviously, you can purposefully give yourself like a

0:22:20.119 --> 0:22:23.800
<v Speaker 1>limp or something in an effort to throw off any

0:22:24.600 --> 0:22:27.640
<v Speaker 1>surveillance techniques that would be looking to match your GIT

0:22:27.880 --> 0:22:33.120
<v Speaker 1>with you. And that's a possibility, but this is an

0:22:33.160 --> 0:22:38.560
<v Speaker 1>actual thing that's being used, this gate analysis and gait verification. Really,

0:22:38.600 --> 0:22:41.239
<v Speaker 1>when it comes to biometrics, again, as I said at

0:22:41.240 --> 0:22:43.959
<v Speaker 1>the beginning, the important quality is that whatever thing you

0:22:44.000 --> 0:22:48.719
<v Speaker 1>are measuring needs to be unique to individuals. So it

0:22:48.720 --> 0:22:51.119
<v Speaker 1>could be physical, it could be behavioral. It could be

0:22:51.160 --> 0:22:53.040
<v Speaker 1>a combination of the two, but it has to be

0:22:53.160 --> 0:22:56.600
<v Speaker 1>unique or else it doesn't do you any good whether

0:22:56.720 --> 0:23:00.159
<v Speaker 1>you're using this technology to verify someone's identity before or

0:23:00.200 --> 0:23:02.840
<v Speaker 1>letting them through a secure checkpoint, or if you're just

0:23:02.880 --> 0:23:06.240
<v Speaker 1>trying to use it to determine an unknown person's identity

0:23:06.240 --> 0:23:09.960
<v Speaker 1>by comparing it against the database of known individuals. Now,

0:23:11.080 --> 0:23:14.600
<v Speaker 1>there are a lot of reasonable concerns about biometrics. It's

0:23:14.600 --> 0:23:18.440
<v Speaker 1>totally understandable, right, like, this is information that is unique

0:23:18.480 --> 0:23:22.240
<v Speaker 1>to you, that is a very private info. And we're

0:23:22.680 --> 0:23:27.600
<v Speaker 1>seeing more and more implementations of biometric systems around us.

0:23:27.600 --> 0:23:30.920
<v Speaker 1>Like I mentioned before, your very phone may rely on it.

0:23:31.400 --> 0:23:34.919
<v Speaker 1>Mine has a fingerprint sensor for example. A lot of

0:23:34.920 --> 0:23:38.960
<v Speaker 1>iPhones use facial recognition to activate, to turn on without

0:23:39.000 --> 0:23:41.239
<v Speaker 1>you having to put in some sort of code. So

0:23:41.560 --> 0:23:46.840
<v Speaker 1>we're seeing biometrics rolled out very in very wide deployments

0:23:46.960 --> 0:23:50.600
<v Speaker 1>in all sorts of different applications. We also have seen

0:23:50.640 --> 0:23:53.480
<v Speaker 1>it for things that are very official, not just use

0:23:53.520 --> 0:23:56.600
<v Speaker 1>of consumer products, but things like you know, maybe getting

0:23:56.640 --> 0:23:59.600
<v Speaker 1>an iris scan as part of identification like in a

0:23:59.640 --> 0:24:03.520
<v Speaker 1>past or or something, or you might have a biometric

0:24:03.600 --> 0:24:07.840
<v Speaker 1>scan that allows you to bypass the normal process of

0:24:07.880 --> 0:24:11.040
<v Speaker 1>getting on a plane. I've had that happen a couple

0:24:11.040 --> 0:24:12.640
<v Speaker 1>of times, and it freaked me out the first time

0:24:12.680 --> 0:24:17.080
<v Speaker 1>because I don't remember ever submitting to the initial scan,

0:24:18.560 --> 0:24:21.240
<v Speaker 1>but it knew who I was when I walked up,

0:24:21.280 --> 0:24:23.680
<v Speaker 1>and I thought, well, that's weird because I didn't actually

0:24:24.400 --> 0:24:26.840
<v Speaker 1>I didn't do I didn't sit down or agree to

0:24:26.880 --> 0:24:31.439
<v Speaker 1>do a process I didn't knowingly agree. I probably did agree,

0:24:31.640 --> 0:24:34.560
<v Speaker 1>I just didn't read the fine print, because nobody ever does, right,

0:24:35.119 --> 0:24:37.919
<v Speaker 1>But that I walked up to the gate and it

0:24:37.960 --> 0:24:40.080
<v Speaker 1>recognized who I was and I didn't even have to

0:24:40.080 --> 0:24:43.400
<v Speaker 1>present a boarding pass or anything. I just got waved in.

0:24:43.960 --> 0:24:48.520
<v Speaker 1>And that's a little creepy, and I can see why

0:24:48.560 --> 0:24:53.439
<v Speaker 1>people would be hesitant about it. And you think about

0:24:53.520 --> 0:24:57.000
<v Speaker 1>the possibilities of this technology and the possibilities of abusing

0:24:57.000 --> 0:24:59.800
<v Speaker 1>that technology, and it quickly does get into that dis

0:25:00.040 --> 0:25:03.879
<v Speaker 1>stopian kind of a vibe. But we're still seeing it

0:25:03.960 --> 0:25:06.679
<v Speaker 1>rolled out every place. There are a lot of sports

0:25:06.680 --> 0:25:11.200
<v Speaker 1>stadiums out there that now use biometric systems in order

0:25:11.240 --> 0:25:14.400
<v Speaker 1>to scan someone, and that way you have a ticketless approach.

0:25:14.480 --> 0:25:18.040
<v Speaker 1>Right you walk up to the stadium, you scan your

0:25:18.080 --> 0:25:21.240
<v Speaker 1>palm and it identifies who you are and the fact

0:25:21.280 --> 0:25:23.880
<v Speaker 1>that you already have tickets to that event and you're

0:25:23.920 --> 0:25:27.600
<v Speaker 1>just you're waved in. This is being deployed more and

0:25:27.640 --> 0:25:32.119
<v Speaker 1>more around the world. And as I record this, Amazon

0:25:32.200 --> 0:25:36.360
<v Speaker 1>is rolling out It's Amazon One technology. This is it's

0:25:36.600 --> 0:25:40.640
<v Speaker 1>palm scanning technology, which was already being used in things

0:25:40.680 --> 0:25:43.920
<v Speaker 1>like Amazon Go storefronts. It's now rolling those out to

0:25:44.200 --> 0:25:47.840
<v Speaker 1>Whole Foods grocery stores here in the United States, and

0:25:47.960 --> 0:25:50.159
<v Speaker 1>it's already in several hundred of them. It's going to

0:25:50.200 --> 0:25:51.840
<v Speaker 1>be put into the rest of them before the end

0:25:51.840 --> 0:25:55.920
<v Speaker 1>of the year. And the value proposition that Amazon is

0:25:55.960 --> 0:25:59.800
<v Speaker 1>giving customers is this, It's mainly one of convenience that

0:26:00.000 --> 0:26:04.840
<v Speaker 1>customers can opt to scan their palm, which then will

0:26:04.880 --> 0:26:09.960
<v Speaker 1>create a unique identifier associated with that person. That identifier

0:26:10.040 --> 0:26:13.240
<v Speaker 1>then in turn must be linked to the customer's Amazon

0:26:13.280 --> 0:26:17.119
<v Speaker 1>account and then whatever payment options they have linked to

0:26:17.320 --> 0:26:20.320
<v Speaker 1>that Amazon account. So you go to Whole food so

0:26:20.359 --> 0:26:23.040
<v Speaker 1>you do your grocery shopping, you scan all your items

0:26:23.040 --> 0:26:28.080
<v Speaker 1>at the self scan cashier area, and then you scan

0:26:28.200 --> 0:26:32.600
<v Speaker 1>your palm and it automatically deducts however much the groceries

0:26:32.640 --> 0:26:35.159
<v Speaker 1>were from your account and you're done. You don't have

0:26:35.200 --> 0:26:37.920
<v Speaker 1>to carry credit cards. You don't even need a smartphone

0:26:37.920 --> 0:26:40.840
<v Speaker 1>with a digital card on it. You literally have your

0:26:40.880 --> 0:26:45.440
<v Speaker 1>payment on hand. It is your hand. The scanner, meanwhile,

0:26:45.960 --> 0:26:48.119
<v Speaker 1>is looking not just at the skin of the palm.

0:26:48.200 --> 0:26:51.960
<v Speaker 1>It's actually using wavelengths of light that let it see

0:26:52.520 --> 0:26:56.560
<v Speaker 1>below the skin level to the pattern of veins in

0:26:56.600 --> 0:27:00.000
<v Speaker 1>your palm. That ends up being part of the information

0:27:00.200 --> 0:27:04.159
<v Speaker 1>that ultimately generates this identifier that it's associated with you.

0:27:04.760 --> 0:27:09.560
<v Speaker 1>Amazon says they're not actually saving the palm scans themselves,

0:27:10.040 --> 0:27:13.160
<v Speaker 1>so it's not like there's some According to Amazon, it's

0:27:13.160 --> 0:27:15.760
<v Speaker 1>not like there's some sort of massive database that has

0:27:16.160 --> 0:27:19.200
<v Speaker 1>all these different palm scans in it. Instead, what they're

0:27:19.240 --> 0:27:22.960
<v Speaker 1>saying is that when you scan your palm, the scanner

0:27:23.080 --> 0:27:27.480
<v Speaker 1>essentially reduces all the features of your palm into data points,

0:27:28.160 --> 0:27:32.440
<v Speaker 1>which then end up generating this unique identifier. So really

0:27:32.440 --> 0:27:34.680
<v Speaker 1>what you're doing is verifying every single time right you

0:27:35.040 --> 0:27:38.960
<v Speaker 1>hold your palm up, it scans it, it generates this number,

0:27:39.080 --> 0:27:42.760
<v Speaker 1>it compares that to the number on file, and if

0:27:42.800 --> 0:27:45.400
<v Speaker 1>the two numbers match, yay, you're who you say you are,

0:27:46.040 --> 0:27:49.200
<v Speaker 1>and then you can be charged for your very expensive

0:27:50.000 --> 0:27:53.480
<v Speaker 1>groceries and then you can go on your merry way.

0:27:53.840 --> 0:27:56.159
<v Speaker 1>What they what they're saying is not happening is that

0:27:56.200 --> 0:27:59.240
<v Speaker 1>it's scanning your hand and then comparing the physical scan

0:27:59.720 --> 0:28:02.919
<v Speaker 1>again and stay previous physical scan that has to be

0:28:03.000 --> 0:28:06.880
<v Speaker 1>saved somewhere. That's important because all the information that Amazon

0:28:06.960 --> 0:28:09.960
<v Speaker 1>is storing is in the cloud. They say that they've

0:28:10.000 --> 0:28:12.480
<v Speaker 1>put a lot of security on this because people are

0:28:12.640 --> 0:28:18.680
<v Speaker 1>understandably concerned about having very personal and personally identifiable information

0:28:19.440 --> 0:28:23.560
<v Speaker 1>stored on the company systems, and if it's on the cloud,

0:28:23.640 --> 0:28:27.040
<v Speaker 1>that means that potentially you could have hackers target it.

0:28:27.560 --> 0:28:31.240
<v Speaker 1>Maybe you could have law enforcement agencies try to force

0:28:31.280 --> 0:28:36.639
<v Speaker 1>Amazon to share information as they go through some form

0:28:36.680 --> 0:28:41.440
<v Speaker 1>of investigation. So people are understandably concerned. If Amazon's telling

0:28:41.480 --> 0:28:45.200
<v Speaker 1>the truth and the only information it's storing is a

0:28:45.280 --> 0:28:49.560
<v Speaker 1>unique identifier, then if hackers were to get access to that,

0:28:49.600 --> 0:28:52.680
<v Speaker 1>then it arguably wouldn't be very useful. It'd be kind

0:28:52.680 --> 0:28:54.880
<v Speaker 1>of like you got the answer to a math question,

0:28:55.120 --> 0:28:59.120
<v Speaker 1>but you don't know what the math question was, or

0:28:59.160 --> 0:29:02.240
<v Speaker 1>in the case of hitching Guide to the Galaxy. They

0:29:03.080 --> 0:29:06.600
<v Speaker 1>the part of the story is that these people build

0:29:06.800 --> 0:29:10.560
<v Speaker 1>this massively powerful computer to give the answer to life,

0:29:10.600 --> 0:29:13.560
<v Speaker 1>the universe, and everything, and the answer ends up being

0:29:13.600 --> 0:29:17.480
<v Speaker 1>forty two, and they say, how's that? What does that

0:29:17.600 --> 0:29:20.400
<v Speaker 1>mean forty two? Well, you need to know the question.

0:29:21.280 --> 0:29:23.520
<v Speaker 1>You need to know what the question is for forty

0:29:23.520 --> 0:29:27.080
<v Speaker 1>two to make sense. You just said the answer to life,

0:29:27.080 --> 0:29:30.680
<v Speaker 1>the universe, and everything. And so you see that you

0:29:30.720 --> 0:29:32.720
<v Speaker 1>need to know both the question and the answer. If

0:29:32.720 --> 0:29:34.080
<v Speaker 1>you only have the answer, you don't know what the

0:29:34.160 --> 0:29:39.040
<v Speaker 1>question was. So if Amazon's just storing these numbers and

0:29:39.120 --> 0:29:41.320
<v Speaker 1>hackers got access to it, they wouldn't be able to

0:29:41.320 --> 0:29:44.880
<v Speaker 1>backtrack and figure out your scan What they could do, however, potentially,

0:29:45.720 --> 0:29:49.960
<v Speaker 1>is find out every single time you used that technology,

0:29:50.040 --> 0:29:52.720
<v Speaker 1>whether it was when you were grocery shopping or going

0:29:52.800 --> 0:29:56.360
<v Speaker 1>to a sporting event, or going to any other place

0:29:56.400 --> 0:30:02.880
<v Speaker 1>that has opted to use AMI Amazon's palm scanning technology

0:30:02.960 --> 0:30:05.880
<v Speaker 1>in their business. It would become a way of tracking

0:30:05.920 --> 0:30:09.840
<v Speaker 1>your movements and potentially also seeing what it was you

0:30:09.920 --> 0:30:14.000
<v Speaker 1>were using the scanner for, you know, maybe getting access

0:30:14.040 --> 0:30:15.960
<v Speaker 1>to stuff or whatever, like going to a sporting event

0:30:16.080 --> 0:30:18.720
<v Speaker 1>or a concert. And that's where you start to see

0:30:19.880 --> 0:30:23.680
<v Speaker 1>real security and privacy issues. Even if Amazon's super super

0:30:23.720 --> 0:30:26.479
<v Speaker 1>careful with this, Amazon itself still has access to all

0:30:26.520 --> 0:30:29.480
<v Speaker 1>of that right, So of course, if you go to

0:30:29.560 --> 0:30:33.240
<v Speaker 1>Amazon dot com and buy something, Amazon knows what you bought,

0:30:33.360 --> 0:30:36.160
<v Speaker 1>and it can use that information to try and target

0:30:36.840 --> 0:30:41.000
<v Speaker 1>you for advertising and to give suggestions for products you

0:30:41.080 --> 0:30:44.920
<v Speaker 1>might find useful based upon your past purchases. If you're

0:30:45.000 --> 0:30:50.120
<v Speaker 1>using Amazon's palm scanning system out in the wild, then

0:30:50.160 --> 0:30:54.000
<v Speaker 1>Amazon also knows all that information out in the real world,

0:30:54.080 --> 0:30:56.320
<v Speaker 1>not just on Amazon dot Com. So you go to

0:30:56.360 --> 0:30:58.160
<v Speaker 1>Whole Foods and you buy a whole bunch of groceries,

0:30:58.200 --> 0:31:01.640
<v Speaker 1>you scan your palm. Now Amazon knows exactly what things

0:31:01.680 --> 0:31:04.640
<v Speaker 1>you bought, and they know it's you. They've got the

0:31:04.680 --> 0:31:07.840
<v Speaker 1>identifier it's connected to your Amazon account that could be

0:31:07.920 --> 0:31:11.400
<v Speaker 1>used for the purposes of targeted advertising. Amazon has said

0:31:11.440 --> 0:31:16.560
<v Speaker 1>they're not sharing the palm data with advertisers, which is fine,

0:31:17.040 --> 0:31:20.160
<v Speaker 1>but they didn't say anything like all the stuff I read.

0:31:20.720 --> 0:31:24.040
<v Speaker 1>They very carefully did not say they weren't sharing purchase

0:31:24.120 --> 0:31:28.800
<v Speaker 1>history or use history. And sure they might keep your

0:31:28.880 --> 0:31:33.360
<v Speaker 1>actual palm scan private, but if they're sharing with advertisers

0:31:33.400 --> 0:31:36.200
<v Speaker 1>what it is you're buying or where you are going,

0:31:37.520 --> 0:31:40.360
<v Speaker 1>the palm scan thing ends up being kind of moot, Like,

0:31:40.400 --> 0:31:46.000
<v Speaker 1>that's not that important. Your activities are telling the advertisers

0:31:46.040 --> 0:31:50.560
<v Speaker 1>and Amazon a lot about you beyond just what your

0:31:50.680 --> 0:31:54.479
<v Speaker 1>palm is like it. Yeah, knowing where the veins are

0:31:54.520 --> 0:31:59.200
<v Speaker 1>in your palm is potentially disastrous if someone's trying to

0:31:59.480 --> 0:32:03.320
<v Speaker 1>somehow replicate you and run up a bunch of charges

0:32:03.320 --> 0:32:07.160
<v Speaker 1>on your account. But to me, the more disturbing thing

0:32:08.440 --> 0:32:11.040
<v Speaker 1>is that every time you use a point of sale

0:32:11.160 --> 0:32:16.520
<v Speaker 1>or point of access that relies on this technology, it's

0:32:16.560 --> 0:32:20.080
<v Speaker 1>another data point that associates you with a specific action,

0:32:20.760 --> 0:32:24.600
<v Speaker 1>and collectively that ends up really mattering a whole lot,

0:32:25.680 --> 0:32:30.280
<v Speaker 1>both to Amazon and to potential advertisers. So I have

0:32:30.360 --> 0:32:33.239
<v Speaker 1>real concerns about using this kind of technology. I mean,

0:32:33.240 --> 0:32:35.400
<v Speaker 1>you could argue the same thing is true if you're

0:32:35.480 --> 0:32:39.880
<v Speaker 1>using the same credit cards or the same payment systems.

0:32:40.880 --> 0:32:45.240
<v Speaker 1>It's the same issue, right, Like, Honestly, the big issue

0:32:45.280 --> 0:32:48.760
<v Speaker 1>I have, and I'm not like a conspiracy minded person,

0:32:48.840 --> 0:32:51.000
<v Speaker 1>but the big issue I have is that we are

0:32:51.080 --> 0:32:53.080
<v Speaker 1>past the days where you would do things like cash

0:32:53.160 --> 0:32:57.000
<v Speaker 1>transactions for a lot of stuff, and cash transactions could

0:32:57.000 --> 0:32:59.080
<v Speaker 1>be really useful if you need to make a transaction

0:32:59.160 --> 0:33:03.240
<v Speaker 1>that you didn't want to be associated with you for

0:33:03.320 --> 0:33:05.480
<v Speaker 1>the rest of your life. Right if you need to

0:33:05.480 --> 0:33:08.800
<v Speaker 1>buy something, Maybe you need to buy some medication and

0:33:08.840 --> 0:33:12.240
<v Speaker 1>it's nobody businesses but your own that you need this medication,

0:33:12.680 --> 0:33:15.040
<v Speaker 1>and you normally would use cash to do it, but

0:33:15.120 --> 0:33:18.920
<v Speaker 1>now you're using some other method that is linked to you,

0:33:19.200 --> 0:33:21.880
<v Speaker 1>which means other people know that you're having to get

0:33:21.880 --> 0:33:24.880
<v Speaker 1>this medication beyond you and the pharmacist and your doctor,

0:33:25.880 --> 0:33:31.200
<v Speaker 1>and that becomes a potential privacy issue, and you could

0:33:31.480 --> 0:33:34.480
<v Speaker 1>apply that to all sorts of different stuff. So to me,

0:33:34.880 --> 0:33:38.560
<v Speaker 1>the biometrics approach, especially in a consumer use for things

0:33:38.600 --> 0:33:44.280
<v Speaker 1>like access to events or a way of paying, doesn't

0:33:44.320 --> 0:33:47.080
<v Speaker 1>appeal to me. But you could argue that it's really

0:33:47.120 --> 0:33:51.200
<v Speaker 1>just an extension of how we already interact in the world.

0:33:51.800 --> 0:33:53.520
<v Speaker 1>I guess the more I talk about this, the more

0:33:53.520 --> 0:33:58.520
<v Speaker 1>I can see why some cryptocurrency enthusiasts really like cryptocurrency.

0:33:58.560 --> 0:34:01.440
<v Speaker 1>They like the idea of being able to use currency

0:34:01.480 --> 0:34:04.840
<v Speaker 1>in a way that doesn't immediately associate them as a

0:34:04.840 --> 0:34:07.840
<v Speaker 1>person with their purchases or the way they're spending their money.

0:34:08.200 --> 0:34:10.880
<v Speaker 1>I kind of get that. I don't think cryptocurrency is

0:34:11.320 --> 0:34:15.080
<v Speaker 1>still the solution for that personally. That's my own personal belief,

0:34:16.120 --> 0:34:19.040
<v Speaker 1>but I can understand the tendency because I feel the

0:34:19.080 --> 0:34:24.200
<v Speaker 1>same way about biometrics and other forms of credit and

0:34:24.239 --> 0:34:27.640
<v Speaker 1>debit cards and stuff too. But really, biometrics just takes

0:34:27.680 --> 0:34:31.120
<v Speaker 1>it to a degree that's so personal that I think

0:34:31.120 --> 0:34:35.520
<v Speaker 1>it's impossible to deny. So anyway, that's just a quick

0:34:35.560 --> 0:34:39.480
<v Speaker 1>overview of biometrics. There's clearly tons more we can talk about,

0:34:39.640 --> 0:34:42.800
<v Speaker 1>and lots of different applications that have really valid uses,

0:34:43.400 --> 0:34:46.759
<v Speaker 1>including ones where you could argue, yeah, I understand that,

0:34:47.000 --> 0:34:50.520
<v Speaker 1>you know, I'm giving up my privacy, but in return,

0:34:50.560 --> 0:34:54.359
<v Speaker 1>I'm getting this additional convenience and maybe even some other

0:34:54.480 --> 0:34:57.680
<v Speaker 1>features that normally wouldn't be available to me if I

0:34:57.680 --> 0:35:00.080
<v Speaker 1>were using other methods of payments. So I'm willing to

0:35:00.160 --> 0:35:04.040
<v Speaker 1>make that trade. That's valid if that's who you are.

0:35:04.520 --> 0:35:07.160
<v Speaker 1>There is nothing invalid about that. I think the important

0:35:07.160 --> 0:35:10.800
<v Speaker 1>thing is just making the decision with as much information

0:35:10.840 --> 0:35:13.520
<v Speaker 1>as possible so that you feel good about it. And

0:35:13.680 --> 0:35:16.359
<v Speaker 1>even though I don't feel good about that for myself,

0:35:16.760 --> 0:35:20.279
<v Speaker 1>I wouldn't fault someone else for opting into it. If

0:35:20.600 --> 0:35:23.080
<v Speaker 1>to them they're like, no, this is what matters most

0:35:23.080 --> 0:35:28.640
<v Speaker 1>to me. That to me is a perfectly cromulent thing

0:35:28.719 --> 0:35:33.080
<v Speaker 1>to say. Okay, I've rambled enough. Like I said, we'll

0:35:33.080 --> 0:35:36.840
<v Speaker 1>probably do episodes where we focus more on specific types

0:35:36.880 --> 0:35:40.759
<v Speaker 1>of biometrics in the future. I have done one on

0:35:40.840 --> 0:35:43.439
<v Speaker 1>ones on things like fingerprints, and I think I've even

0:35:43.520 --> 0:35:49.120
<v Speaker 1>done some on voice recognition. All they think I was

0:35:49.360 --> 0:35:53.120
<v Speaker 1>focusing more on speech recognition as opposed to speaker recognition.

0:35:53.800 --> 0:35:56.160
<v Speaker 1>But maybe I'll do some more specifics and talk about

0:35:56.239 --> 0:36:00.640
<v Speaker 1>the actual development of the technologies and the algorith needed

0:36:00.680 --> 0:36:03.880
<v Speaker 1>to make that possible. Because you know, I summarized it

0:36:03.920 --> 0:36:06.479
<v Speaker 1>in this episode, but you have to understand it took

0:36:07.000 --> 0:36:10.799
<v Speaker 1>decades of work and tons of very smart people and

0:36:10.960 --> 0:36:13.960
<v Speaker 1>a lot of advancements in technology to make it a

0:36:14.040 --> 0:36:20.800
<v Speaker 1>really feasible possibility. So very interesting stuff. Lots of concerns

0:36:20.840 --> 0:36:23.799
<v Speaker 1>around it, not necessarily about the technology itself but how

0:36:23.800 --> 0:36:27.520
<v Speaker 1>we apply it. And yeah, there's plenty more to talk about,

0:36:27.880 --> 0:36:30.359
<v Speaker 1>but for now, let's wrap up. I hope you are

0:36:30.400 --> 0:36:33.440
<v Speaker 1>all well. This Tech Stuff Tidbits ended up being sub

0:36:33.600 --> 0:36:35.919
<v Speaker 1>forty minutes, so I'm going to call that a win,

0:36:36.560 --> 0:36:46.400
<v Speaker 1>and I'll talk to you again really soon. Tech Stuff

0:36:46.480 --> 0:36:51.000
<v Speaker 1>is an iHeartRadio production. For more podcasts from iHeartRadio, visit

0:36:51.040 --> 0:36:54.560
<v Speaker 1>the iHeartRadio app, Apple podcasts, or wherever you listen to

0:36:54.600 --> 0:36:59.279
<v Speaker 1>your favorite shows.