WEBVTT - Covidwise: The First Coronavirus 'Exposure Notification' App Has Launched in Virginia

0:00:00.080 --> 0:00:03.880
<v Speaker 1>It's Tuesday, August eighteen. I'm Oscar Ramirez from the Daily

0:00:03.920 --> 0:00:08.080
<v Speaker 1>Dive podcast in Los Angeles, and this is reopening America.

0:00:08.760 --> 0:00:12.280
<v Speaker 1>The first bluetooth exposure notification app has launched in Virginia,

0:00:12.480 --> 0:00:16.440
<v Speaker 1>and it's called covid wise. The app uses Bluetooth chirps

0:00:16.480 --> 0:00:19.119
<v Speaker 1>to detect if you've been in close contact with someone

0:00:19.160 --> 0:00:22.200
<v Speaker 1>who has tested a positive. While it's very easy to use,

0:00:22.480 --> 0:00:25.600
<v Speaker 1>for it to really be effective and needs a widespread adoption,

0:00:26.400 --> 0:00:30.200
<v Speaker 1>Jeffrey Fowler, tech columnists at The Washington Post joins us

0:00:30.200 --> 0:00:33.280
<v Speaker 1>for this useful app with very little privacy risk. Thanks

0:00:33.320 --> 0:00:36.919
<v Speaker 1>for joining us, Jeffrey bet I wanted to talk about

0:00:37.320 --> 0:00:42.239
<v Speaker 1>this app out of Virginia. It's called covid wise. It's

0:00:42.240 --> 0:00:46.320
<v Speaker 1>an exposure notification app using Bluetooth on your phone. So

0:00:46.440 --> 0:00:48.760
<v Speaker 1>you might have heard some other contact tracing apps with

0:00:48.760 --> 0:00:52.200
<v Speaker 1>regards to coronavirus, this one is a little different. Your

0:00:52.200 --> 0:00:55.320
<v Speaker 1>Bluetooth sends out pings basically, and if you've come into

0:00:55.320 --> 0:00:58.080
<v Speaker 1>contact with somebody for more than fifteen minutes and you're

0:00:58.440 --> 0:01:01.680
<v Speaker 1>within six feet distance, the app might tell you you've

0:01:01.720 --> 0:01:03.760
<v Speaker 1>been exposed. Then you can go get a test. All

0:01:03.760 --> 0:01:06.960
<v Speaker 1>that usually we bring you on on the podcast, Jeff,

0:01:06.959 --> 0:01:09.959
<v Speaker 1>when we're talking about privacy with apps and things like that,

0:01:10.080 --> 0:01:12.520
<v Speaker 1>and in this case, you've kind of runed this thing

0:01:12.560 --> 0:01:14.520
<v Speaker 1>through many tests and you've kind of come to the

0:01:14.560 --> 0:01:18.119
<v Speaker 1>conclusion that your privacy really isn't at risk and it

0:01:18.120 --> 0:01:20.760
<v Speaker 1>would actually be a benefit if people, a lot of

0:01:20.760 --> 0:01:22.920
<v Speaker 1>people downloaded this thing so we can try to keep

0:01:22.959 --> 0:01:25.119
<v Speaker 1>this thing under control. So Jeff, tell us a little

0:01:25.120 --> 0:01:28.240
<v Speaker 1>bit about COVID wise and the tests you ran through

0:01:28.240 --> 0:01:31.720
<v Speaker 1>it and what your conclusions were. Nobody was more surprised

0:01:31.840 --> 0:01:35.280
<v Speaker 1>than me. The big problem that a lot of these

0:01:35.360 --> 0:01:38.440
<v Speaker 1>apps and the idea of using our phones to help

0:01:38.720 --> 0:01:42.920
<v Speaker 1>track exposure to the coronavirus has had is that people, frankly,

0:01:43.000 --> 0:01:46.280
<v Speaker 1>just don't trust tech companies and that they just don't

0:01:46.319 --> 0:01:49.480
<v Speaker 1>trust the government. And I can't blame you. Companies have

0:01:49.520 --> 0:01:52.360
<v Speaker 1>done very little to earn that trust in Edward Snowden

0:01:52.400 --> 0:01:55.280
<v Speaker 1>taught us all that the government really can't be trusted either.

0:01:55.600 --> 0:01:59.240
<v Speaker 1>But that said, when Google and Apple the spring got

0:01:59.280 --> 0:02:01.640
<v Speaker 1>together and said, hey, they thought that they had figured

0:02:01.640 --> 0:02:05.520
<v Speaker 1>out a way to make our phones useful for figuring

0:02:05.520 --> 0:02:08.440
<v Speaker 1>out if we were exposed to someone with coronavirus, you know,

0:02:08.480 --> 0:02:10.520
<v Speaker 1>I was intrigued because they said that they were going

0:02:10.520 --> 0:02:13.239
<v Speaker 1>to build it from the ground up with privacy in mind.

0:02:13.520 --> 0:02:16.120
<v Speaker 1>So we finally got the first of these in the US,

0:02:16.160 --> 0:02:19.160
<v Speaker 1>in the state of Virginia called COVID Wise, and it

0:02:19.240 --> 0:02:21.679
<v Speaker 1>came out earlier in August, and the moment it was there,

0:02:21.760 --> 0:02:23.600
<v Speaker 1>I was like, we gotta test this, we gotta see

0:02:23.800 --> 0:02:26.240
<v Speaker 1>if they really live up to the promises. And from

0:02:26.280 --> 0:02:29.000
<v Speaker 1>everything we've been able to tell so far from our testing,

0:02:29.040 --> 0:02:31.640
<v Speaker 1>I had thirty five colleagues at the Post who live

0:02:31.680 --> 0:02:33.960
<v Speaker 1>in Virginia and they're all testing it for me. We

0:02:34.040 --> 0:02:36.840
<v Speaker 1>learned two things. First thing we learned is that it

0:02:36.960 --> 0:02:39.720
<v Speaker 1>doesn't seem to be really much of a privacy risk

0:02:39.800 --> 0:02:44.320
<v Speaker 1>here these apps. He's bluetooth to communicate two phones nearby.

0:02:44.360 --> 0:02:47.560
<v Speaker 1>They don't collect your location, they don't send information about

0:02:47.800 --> 0:02:49.680
<v Speaker 1>where you've been or her you've been in contact with

0:02:49.919 --> 0:02:52.480
<v Speaker 1>to the government. Is actually a pretty clever system. We

0:02:52.520 --> 0:02:55.120
<v Speaker 1>looked under the hood as well, just just a double check.

0:02:55.680 --> 0:02:58.080
<v Speaker 1>But they weren't sending out more information and then than

0:02:58.160 --> 0:03:00.800
<v Speaker 1>they claimed, and they weren't those first thing we learned.

0:03:00.880 --> 0:03:03.400
<v Speaker 1>The second thing we learned is we still don't know

0:03:03.480 --> 0:03:05.560
<v Speaker 1>actually if this idea is going to work very well.

0:03:05.919 --> 0:03:09.040
<v Speaker 1>Those thirty five Washington Post colleagues who are testing them,

0:03:09.320 --> 0:03:13.040
<v Speaker 1>none of them got an exposure notification from this app

0:03:13.160 --> 0:03:15.920
<v Speaker 1>over a candy period. Now that could be for many reasons.

0:03:15.960 --> 0:03:18.000
<v Speaker 1>It could be like they were just being really good

0:03:18.240 --> 0:03:21.440
<v Speaker 1>at social distancing. It could mean that not many people

0:03:21.440 --> 0:03:23.399
<v Speaker 1>around them we're using it, or it could mean that

0:03:23.560 --> 0:03:26.360
<v Speaker 1>there's some problems with the idea that the phones can

0:03:26.440 --> 0:03:28.120
<v Speaker 1>do this. But I don't think we were going to

0:03:28.160 --> 0:03:29.919
<v Speaker 1>really figure that out. Is if a lot more people

0:03:29.960 --> 0:03:32.760
<v Speaker 1>try it, And that's one of the interesting parts. Experts

0:03:32.880 --> 0:03:35.400
<v Speaker 1>estimate that up to sixty of a population needs to

0:03:35.440 --> 0:03:37.880
<v Speaker 1>be using these exposure apps for them to be effective.

0:03:38.280 --> 0:03:41.720
<v Speaker 1>So in Virginia that means they need about five million

0:03:41.800 --> 0:03:44.320
<v Speaker 1>people to download it. But in its first week's covid

0:03:44.360 --> 0:03:48.120
<v Speaker 1>wise got three hundred and eighty thousand downloads, so very

0:03:48.160 --> 0:03:51.240
<v Speaker 1>far short of that number needed. But there's other things

0:03:51.400 --> 0:03:53.000
<v Speaker 1>that are kind of become a problem with is this

0:03:53.080 --> 0:03:55.880
<v Speaker 1>is in Virginia just by itself, but there's no big

0:03:55.960 --> 0:04:00.000
<v Speaker 1>national system. So let's say you travel between states or

0:04:00.160 --> 0:04:02.800
<v Speaker 1>just whatever, you come into contact with somebody else, maybe

0:04:02.880 --> 0:04:05.720
<v Speaker 1>using a different app. It's not this COVID wise one,

0:04:06.160 --> 0:04:08.160
<v Speaker 1>you know, it's not all going to work so seamlessly.

0:04:08.400 --> 0:04:12.880
<v Speaker 1>America's app exposure unification strategy suffers from stame of the

0:04:13.120 --> 0:04:14.880
<v Speaker 1>some of the same problems as the rest of our

0:04:14.920 --> 0:04:18.880
<v Speaker 1>coronavirus strategy, and that it's very local based, very state based,

0:04:19.120 --> 0:04:21.640
<v Speaker 1>so as it's set up right now in the United States,

0:04:21.680 --> 0:04:23.640
<v Speaker 1>every state health department would have to make their own

0:04:23.720 --> 0:04:25.640
<v Speaker 1>version of one of these apps. The Feds have not

0:04:25.720 --> 0:04:28.440
<v Speaker 1>expressed any interest, even though in other countries it is

0:04:28.560 --> 0:04:30.840
<v Speaker 1>kind of the national government that's been working on these

0:04:30.920 --> 0:04:34.159
<v Speaker 1>kinds of apps. The good news is that about twenty

0:04:34.320 --> 0:04:37.360
<v Speaker 1>states now have said that they're working on these kinds

0:04:37.360 --> 0:04:39.960
<v Speaker 1>of apps. After Virginia, three more joined it, so we

0:04:40.000 --> 0:04:42.520
<v Speaker 1>already have four out there in the wild. And there

0:04:42.560 --> 0:04:44.880
<v Speaker 1>has been announced an effort that would make these apps

0:04:44.920 --> 0:04:47.880
<v Speaker 1>sort of communicate with each other a little bit so

0:04:47.960 --> 0:04:50.800
<v Speaker 1>that you could cross state borders with it. So that's

0:04:50.800 --> 0:04:53.120
<v Speaker 1>a work in progress, but not there yet. How does

0:04:53.160 --> 0:04:55.680
<v Speaker 1>the bluetooth aspect of it work, Because you said it

0:04:55.680 --> 0:04:59.400
<v Speaker 1>doesn't really necessarily spy on you. The data is anonymized

0:04:59.440 --> 0:05:01.600
<v Speaker 1>as well, So tell us how that works, just so

0:05:01.680 --> 0:05:03.479
<v Speaker 1>we can have peace of mind. With it at least

0:05:03.960 --> 0:05:06.800
<v Speaker 1>this is kind of a fascinating idea that they use

0:05:06.880 --> 0:05:09.360
<v Speaker 1>with this technology. So, first of all, Bluetooth most people

0:05:09.480 --> 0:05:13.240
<v Speaker 1>might have associate with like headphones or like music play

0:05:13.279 --> 0:05:15.400
<v Speaker 1>in your car, and that was really the reason this

0:05:15.839 --> 0:05:18.520
<v Speaker 1>wireless technology was invented for these sort of very short

0:05:18.640 --> 0:05:22.960
<v Speaker 1>range transmissions. Well, turns out that Bluetooth also has the

0:05:23.000 --> 0:05:27.080
<v Speaker 1>capability of being able to roughly tell how far away

0:05:27.160 --> 0:05:30.520
<v Speaker 1>something is based on the strength of the signal. So

0:05:30.600 --> 0:05:34.160
<v Speaker 1>these engineers at Apple and Google got together and they said, hey,

0:05:34.160 --> 0:05:37.400
<v Speaker 1>what if we got made phones listened out for other

0:05:37.440 --> 0:05:41.039
<v Speaker 1>phones that they're nearby, and record something about the ones

0:05:41.120 --> 0:05:43.480
<v Speaker 1>that got six ft are closer. From Morgan fifteen minutes

0:05:43.720 --> 0:05:46.920
<v Speaker 1>to develop this system that they pushed out into recent

0:05:47.000 --> 0:05:50.120
<v Speaker 1>updates to Android and to iOS. So if you've updated

0:05:50.160 --> 0:05:52.280
<v Speaker 1>your phone software was somely you've got it on your

0:05:52.279 --> 0:05:55.479
<v Speaker 1>phone already that they're able to in the background send

0:05:55.480 --> 0:05:58.280
<v Speaker 1>out these little chirps a couple times a second that

0:05:58.480 --> 0:06:01.080
<v Speaker 1>just a very short anonymous codes. And the way it

0:06:01.080 --> 0:06:03.599
<v Speaker 1>works basically is you know when you're near someone for

0:06:03.920 --> 0:06:05.960
<v Speaker 1>sturing the period of time, your phone makes note of

0:06:06.000 --> 0:06:07.960
<v Speaker 1>that anonymous code of the phone that you're in the year,

0:06:08.360 --> 0:06:11.400
<v Speaker 1>and then if that person later has a coronavirus test

0:06:11.440 --> 0:06:14.880
<v Speaker 1>and and has the disease, their health department can give

0:06:14.960 --> 0:06:17.680
<v Speaker 1>them a code to enter into their app, and that

0:06:17.720 --> 0:06:20.920
<v Speaker 1>will signal the system to let everybody else know who's

0:06:21.040 --> 0:06:23.960
<v Speaker 1>come into contact with that patient's code that they should

0:06:24.000 --> 0:06:26.440
<v Speaker 1>go get tested for coronavirus as well. So throughout this

0:06:26.520 --> 0:06:29.920
<v Speaker 1>process the government doesn't know where you were or even

0:06:30.160 --> 0:06:32.960
<v Speaker 1>when or how you might have contracted the disease, and

0:06:33.000 --> 0:06:35.160
<v Speaker 1>in fact, the government doesn't like that about it. They

0:06:35.200 --> 0:06:37.400
<v Speaker 1>wish they had more information, and so that's been one

0:06:37.440 --> 0:06:39.520
<v Speaker 1>of the things that's made it so slow. But at

0:06:39.520 --> 0:06:41.400
<v Speaker 1>no point can they really use it to track you

0:06:41.680 --> 0:06:43.640
<v Speaker 1>as the interesting part to me, well, as you said,

0:06:43.640 --> 0:06:46.520
<v Speaker 1>the biggest concern with these things is trust, and at

0:06:46.600 --> 0:06:49.800
<v Speaker 1>least it's a little reassuring that they built these apps

0:06:49.880 --> 0:06:52.440
<v Speaker 1>with that in mind, that your privacy is not really

0:06:52.480 --> 0:06:55.200
<v Speaker 1>at risk, and the risk overall to anybody downloading these

0:06:55.600 --> 0:06:58.320
<v Speaker 1>is pretty low. The biggest problem, it seems like, is

0:06:58.360 --> 0:07:00.960
<v Speaker 1>the widespread adoption. You need so many people to buy

0:07:00.960 --> 0:07:03.840
<v Speaker 1>into this and then put themselves into the apple if

0:07:03.839 --> 0:07:06.719
<v Speaker 1>they do have a positive test that other people can know.

0:07:06.839 --> 0:07:08.560
<v Speaker 1>I mean, that's really going to be the biggest problem

0:07:08.600 --> 0:07:11.160
<v Speaker 1>with all of these, but at least for now, you know,

0:07:11.200 --> 0:07:13.920
<v Speaker 1>at least we have some type of working framework for this,

0:07:14.160 --> 0:07:16.600
<v Speaker 1>and if we do get into these apps, it could

0:07:16.640 --> 0:07:18.920
<v Speaker 1>be a benefit for a lot of people. The biggest

0:07:18.960 --> 0:07:21.320
<v Speaker 1>risk to you as an individual is you can get

0:07:21.320 --> 0:07:24.400
<v Speaker 1>a false positive because maybe sometimes the bluetooth signals don't

0:07:24.440 --> 0:07:26.520
<v Speaker 1>work super well and maybe you're picking up on the

0:07:26.520 --> 0:07:28.360
<v Speaker 1>guy who lives next door who you've not actually been

0:07:28.400 --> 0:07:31.200
<v Speaker 1>in contact with. So that is one thing that could happen.

0:07:31.360 --> 0:07:33.440
<v Speaker 1>Worst case scenario there you take a COVID test you

0:07:33.440 --> 0:07:37.120
<v Speaker 1>didn't need, Okay. The other risk really is that you

0:07:37.120 --> 0:07:40.320
<v Speaker 1>could get false negatives, which means that you think you're

0:07:40.360 --> 0:07:43.600
<v Speaker 1>safe even if you've not been. And so definitely anybody

0:07:43.640 --> 0:07:46.080
<v Speaker 1>installs one of these should take it with a grain

0:07:46.120 --> 0:07:50.040
<v Speaker 1>of salt. Is not magic. It won't shield you from

0:07:50.120 --> 0:07:53.360
<v Speaker 1>the virus, but it could give you some important information

0:07:53.440 --> 0:07:55.200
<v Speaker 1>to help you know when you might need to take

0:07:55.200 --> 0:07:57.239
<v Speaker 1>a test, and I think that's worth trying for everyone.

0:07:57.920 --> 0:08:01.080
<v Speaker 1>Jeffrey Fowler tech calumnists at the way Shington Post, thank

0:08:01.120 --> 0:08:06.400
<v Speaker 1>you very much for joining us. You bet, I'm Oscar

0:08:06.480 --> 0:08:10.119
<v Speaker 1>Ramirez and this has been reopening America. Don't forget effort

0:08:10.160 --> 0:08:11.880
<v Speaker 1>today's big news stories. You can check me out on

0:08:11.920 --> 0:08:15.040
<v Speaker 1>the Daily Dive podcast every Monday through Friday, so follow

0:08:15.120 --> 0:08:17.240
<v Speaker 1>us on I Heart Radio or wherever you get your

0:08:17.280 --> 0:08:17.760
<v Speaker 1>podcast