WEBVTT - Geotagging and Privacy

0:00:00.280 --> 0:00:02.840
<v Speaker 1>Brought to you by the reinvented two thousand twelve camera.

0:00:03.160 --> 0:00:08.920
<v Speaker 1>It's ready. Are you get in touch with technology? With

0:00:09.039 --> 0:00:18.079
<v Speaker 1>tech stuff from how stuff works dot com. Hello again, everyone,

0:00:18.400 --> 0:00:21.480
<v Speaker 1>Welcome to tex Stuff. My name is Chris Poette. I'm

0:00:21.520 --> 0:00:24.160
<v Speaker 1>an editor at how stuff works dot com and sittre

0:00:24.200 --> 0:00:26.920
<v Speaker 1>across from me, as he is typically on these occasions,

0:00:27.120 --> 0:00:30.040
<v Speaker 1>his senior writer, Jonathan Strickland. I kicked the map into

0:00:30.040 --> 0:00:35.000
<v Speaker 1>the creek. That was a short quote, and if you

0:00:35.040 --> 0:00:38.120
<v Speaker 1>know the genesis of that quote, please let us know.

0:00:38.640 --> 0:00:43.599
<v Speaker 1>And if you don't, I'm so scared. Okay, all right,

0:00:43.640 --> 0:00:46.199
<v Speaker 1>I give it away. Now. We're going to talk today

0:00:46.240 --> 0:00:51.280
<v Speaker 1>about geo tagging and its relationship to privacy and how

0:00:51.840 --> 0:00:54.080
<v Speaker 1>how geo tagging can be a really cool thing and

0:00:54.120 --> 0:00:56.480
<v Speaker 1>can be a really neat way to interact with people

0:00:56.560 --> 0:00:59.720
<v Speaker 1>online as well as to keep track of things that

0:00:59.760 --> 0:01:04.040
<v Speaker 1>you've on, and also how sometimes it can be a

0:01:04.160 --> 0:01:07.760
<v Speaker 1>bad thing, like you can give tools to people you

0:01:07.800 --> 0:01:10.720
<v Speaker 1>may not want to associate with ways to harass you

0:01:10.800 --> 0:01:14.160
<v Speaker 1>and make your life miserable. Yeah, I'd like to uh

0:01:14.440 --> 0:01:16.760
<v Speaker 1>to make it clear to we we bring these kinds

0:01:16.760 --> 0:01:18.679
<v Speaker 1>of things up a lot, and we get criticized on

0:01:18.720 --> 0:01:24.440
<v Speaker 1>occasion from people who seem to feel that we're unequivocally

0:01:24.560 --> 0:01:29.039
<v Speaker 1>saying that these computerized tools are dangerous and scary and

0:01:29.080 --> 0:01:32.040
<v Speaker 1>therefore you should turn off all technology. And that's that's

0:01:32.080 --> 0:01:36.039
<v Speaker 1>not what we're saying. Um, like just about every technology

0:01:36.080 --> 0:01:38.399
<v Speaker 1>we've ever mentioned on the podcast, not all of them,

0:01:38.440 --> 0:01:41.600
<v Speaker 1>but the vast majority of them. Um, you can use

0:01:41.760 --> 0:01:44.039
<v Speaker 1>tools for all kinds of purposes. I mean, you could

0:01:44.080 --> 0:01:45.520
<v Speaker 1>hit somebody in the head with a hammer, but it's

0:01:45.560 --> 0:01:48.960
<v Speaker 1>really great for pounding in nails. Uh man, wait what

0:01:49.560 --> 0:01:51.920
<v Speaker 1>I have been using the hammer in a very limited way.

0:01:52.000 --> 0:01:56.400
<v Speaker 1>I shouldn't know that what's gonna happen? So bang, Thanks Maxwell,

0:01:56.520 --> 0:02:02.760
<v Speaker 1>thank you. Um yeah, doesn't that beat all? Um, No,

0:02:03.000 --> 0:02:07.640
<v Speaker 1>we're off to our rollicking stuff. No. Geo tagging is

0:02:08.240 --> 0:02:11.000
<v Speaker 1>one of those things that that can be really really

0:02:11.160 --> 0:02:15.320
<v Speaker 1>useful for all kinds of informational purposes. It can be

0:02:15.400 --> 0:02:19.680
<v Speaker 1>used for fun. Um. But if you give like you know,

0:02:19.880 --> 0:02:23.200
<v Speaker 1>put your phone number up on on a billboard, and

0:02:23.400 --> 0:02:25.440
<v Speaker 1>some people you like, we'll call, and other people you

0:02:25.480 --> 0:02:28.480
<v Speaker 1>don't will, so so just be careful how you use that.

0:02:28.520 --> 0:02:30.639
<v Speaker 1>And that's that's the essential message. But let's get into

0:02:30.680 --> 0:02:34.320
<v Speaker 1>geo tagging and what it is and maybe you know

0:02:34.400 --> 0:02:36.800
<v Speaker 1>and and great much greater detail will get into the

0:02:36.800 --> 0:02:39.880
<v Speaker 1>privacy issue here. Sure. Yeah, so geo tagging is exactly

0:02:39.919 --> 0:02:43.040
<v Speaker 1>what it sounds like. It is tagging some sort of

0:02:43.080 --> 0:02:48.560
<v Speaker 1>information with geographical a layer of geographical information. Yeah, we're

0:02:48.600 --> 0:02:53.120
<v Speaker 1>we're talking about metadata here, and metadata is information about

0:02:53.720 --> 0:02:56.919
<v Speaker 1>some information. Well yeah, information about information. That's usually how

0:02:56.919 --> 0:03:00.480
<v Speaker 1>it's described. But um, you know you have a a

0:03:00.480 --> 0:03:03.119
<v Speaker 1>book in front of you. Well, it's got a title. Um,

0:03:03.240 --> 0:03:05.359
<v Speaker 1>you can talk about the publisher, You could talk about

0:03:05.400 --> 0:03:07.000
<v Speaker 1>what kind of paper it was printed on. You can

0:03:07.000 --> 0:03:09.280
<v Speaker 1>get into all kinds of information about how many pages

0:03:09.320 --> 0:03:12.120
<v Speaker 1>it has, how many words per page on average. But

0:03:12.120 --> 0:03:14.160
<v Speaker 1>when we talk about geo tagging, you could geo tag

0:03:14.160 --> 0:03:16.519
<v Speaker 1>a book. Heyes, you know it came from London. Look

0:03:16.520 --> 0:03:17.920
<v Speaker 1>it says that right there on the page. It's on

0:03:17.960 --> 0:03:22.000
<v Speaker 1>my shelf exactly. But yeah. You take a photo on

0:03:22.080 --> 0:03:27.560
<v Speaker 1>your smartphone and it may include information from the GPS

0:03:27.760 --> 0:03:31.120
<v Speaker 1>device that you have also in your smartphone. So you

0:03:31.160 --> 0:03:35.280
<v Speaker 1>can say, go to the Grand Canyon and take photos

0:03:35.800 --> 0:03:39.080
<v Speaker 1>of your your summer vacation, and you could say this

0:03:39.160 --> 0:03:41.960
<v Speaker 1>is specifically where this photo was shot. So if somebody,

0:03:42.560 --> 0:03:44.560
<v Speaker 1>one of your friends. You post this on your photo

0:03:44.600 --> 0:03:47.000
<v Speaker 1>sharing account on the web. When of your friends wants

0:03:47.000 --> 0:03:49.480
<v Speaker 1>to go, oh, man, I'm going into the Grand Canyon

0:03:49.480 --> 0:03:52.320
<v Speaker 1>this summer too. Where where did you take that picture?

0:03:52.320 --> 0:03:54.680
<v Speaker 1>I want to see that for myself, we could say, well,

0:03:54.720 --> 0:03:57.520
<v Speaker 1>these are the coordinates, So there you go, geo tagging. Yeah,

0:03:57.520 --> 0:04:01.160
<v Speaker 1>there's actually a lot of different potential all applications for this.

0:04:01.520 --> 0:04:05.480
<v Speaker 1>There's the the fun vacation sort of version that you

0:04:05.520 --> 0:04:07.400
<v Speaker 1>were talking about. For example, let's say that you go

0:04:07.520 --> 0:04:10.200
<v Speaker 1>on a road trip and along the road trip, you

0:04:10.240 --> 0:04:12.360
<v Speaker 1>take all these different photos and then you want to

0:04:12.480 --> 0:04:17.320
<v Speaker 1>organize the photos into a online photo album, maybe even

0:04:17.440 --> 0:04:21.320
<v Speaker 1>something that's more like an interactive scrapbook, and you want

0:04:21.320 --> 0:04:24.320
<v Speaker 1>to go and create that. Well, there are programs that

0:04:24.400 --> 0:04:26.760
<v Speaker 1>will allow you to do that, and they what they

0:04:26.760 --> 0:04:29.760
<v Speaker 1>do is they read the meta data connected to those images.

0:04:30.279 --> 0:04:32.840
<v Speaker 1>So let's say that you're using a smartphone or you're

0:04:32.920 --> 0:04:35.440
<v Speaker 1>using a digital camera that has a GPS receiver built

0:04:35.480 --> 0:04:37.480
<v Speaker 1>into it, because there are some out there, not all

0:04:37.520 --> 0:04:40.120
<v Speaker 1>of them, but there are some, and you take photos.

0:04:41.640 --> 0:04:44.520
<v Speaker 1>What's cool is that most cameras, now almost all of them,

0:04:44.680 --> 0:04:48.200
<v Speaker 1>will time stamp a photo yes, so it'll give you

0:04:48.240 --> 0:04:51.159
<v Speaker 1>an exact date and time that that photo was taken.

0:04:51.200 --> 0:04:53.440
<v Speaker 1>So as long as the cameras you know, clock is

0:04:53.440 --> 0:04:56.520
<v Speaker 1>correct and calendar is correct, you're gonna have that information

0:04:56.560 --> 0:04:59.680
<v Speaker 1>included on the image. Then you have the additional information

0:04:59.680 --> 0:05:04.400
<v Speaker 1>of the GPS UH coordinates, so you've got longitude and

0:05:04.440 --> 0:05:07.520
<v Speaker 1>latitude that gets thrown in there. With the right program,

0:05:07.720 --> 0:05:11.920
<v Speaker 1>you could dump a ton of digital not really a

0:05:11.920 --> 0:05:14.040
<v Speaker 1>ton because they don't wear anything, but you can throw

0:05:14.080 --> 0:05:16.880
<v Speaker 1>up a lot of digital photos into that and have

0:05:17.000 --> 0:05:21.240
<v Speaker 1>it arranged those photos by date and time and by location,

0:05:21.320 --> 0:05:24.280
<v Speaker 1>so you could create an interactive map where someone could

0:05:24.279 --> 0:05:27.640
<v Speaker 1>then go and look at how you went from on

0:05:27.680 --> 0:05:31.120
<v Speaker 1>your vacation, like from following the photos, they can retrace

0:05:31.200 --> 0:05:35.080
<v Speaker 1>your steps, see the sites you saw, and sort of

0:05:35.320 --> 0:05:38.839
<v Speaker 1>live your vacation just by going through these links. And

0:05:38.920 --> 0:05:41.720
<v Speaker 1>you know, that's just a basic application of geotagging. There

0:05:41.720 --> 0:05:43.120
<v Speaker 1>are a lot of other ones. I mean, there's there

0:05:43.160 --> 0:05:45.760
<v Speaker 1>are tons of reasons to use it for marketing. I

0:05:45.880 --> 0:05:48.480
<v Speaker 1>used an example recently when I was talking about this

0:05:49.160 --> 0:05:53.480
<v Speaker 1>on on a local news program. For example, let's see

0:05:53.480 --> 0:05:56.719
<v Speaker 1>you have a food truck and let's say there's maybe

0:05:56.880 --> 0:05:59.560
<v Speaker 1>four or five locations that you take this food truck

0:05:59.600 --> 0:06:02.599
<v Speaker 1>to reag liarly throughout the week, and as a way

0:06:02.680 --> 0:06:06.280
<v Speaker 1>of showing people where this is, you may take photos

0:06:06.320 --> 0:06:07.880
<v Speaker 1>of your food truck so one they know what it

0:06:07.920 --> 0:06:10.640
<v Speaker 1>looks like, but you include geotagging information and a and

0:06:10.760 --> 0:06:14.719
<v Speaker 1>a a map application so it shows exactly where that

0:06:14.760 --> 0:06:18.719
<v Speaker 1>truck is located when it's you know, when it's operating hours,

0:06:18.880 --> 0:06:22.920
<v Speaker 1>have it at that particular spot exactly, so then you've

0:06:22.920 --> 0:06:27.400
<v Speaker 1>got a map that pops up. There are applications that

0:06:27.560 --> 0:06:31.240
<v Speaker 1>incorporate this in such a seamless way that you really

0:06:31.240 --> 0:06:33.240
<v Speaker 1>don't have to do anything other than make sure that

0:06:33.360 --> 0:06:37.760
<v Speaker 1>GPS setting is turned on. Once you've done that, it

0:06:37.839 --> 0:06:40.680
<v Speaker 1>does all the work for you. For example, twit pick

0:06:40.760 --> 0:06:44.200
<v Speaker 1>does this if I take a photo with my my

0:06:44.279 --> 0:06:47.880
<v Speaker 1>Android phone and I have the GPS feature turned on

0:06:47.920 --> 0:06:51.039
<v Speaker 1>when I'm taking photos so it shares location data, and

0:06:51.320 --> 0:06:54.600
<v Speaker 1>I enable the location data on twit pick. So there

0:06:54.600 --> 0:06:58.600
<v Speaker 1>are two spots where I have to agree to do this. Um,

0:06:58.640 --> 0:07:00.440
<v Speaker 1>if I do both of those things and I take

0:07:00.440 --> 0:07:03.360
<v Speaker 1>a photo using my camera and then upload it to

0:07:03.400 --> 0:07:06.599
<v Speaker 1>twit pick, not only will it include that geographic location,

0:07:06.600 --> 0:07:10.280
<v Speaker 1>it will actually pull up a Google Maps image and

0:07:10.320 --> 0:07:12.960
<v Speaker 1>show where that photo was taken. And if you want,

0:07:13.000 --> 0:07:15.720
<v Speaker 1>you can switch map from map view mode to satellite

0:07:15.800 --> 0:07:19.840
<v Speaker 1>view mode and see a satellite picture of where you know,

0:07:19.880 --> 0:07:21.920
<v Speaker 1>where I was standing when I took that photo. We

0:07:22.040 --> 0:07:25.400
<v Speaker 1>tried this on camera and it worked so well. We

0:07:25.440 --> 0:07:27.920
<v Speaker 1>actually I took a photo from uh we have a

0:07:28.240 --> 0:07:32.080
<v Speaker 1>balcony here at how stuff works in a nice deck really, um,

0:07:32.120 --> 0:07:33.880
<v Speaker 1>that I stood out on and I took photos of

0:07:34.160 --> 0:07:36.440
<v Speaker 1>and using the satellite you could see the exact location

0:07:36.480 --> 0:07:39.880
<v Speaker 1>I stood where I took those photos, and it was,

0:07:39.960 --> 0:07:41.480
<v Speaker 1>you know, a satellite photo of it, not just a

0:07:41.480 --> 0:07:44.760
<v Speaker 1>map location. So that's kind of cool. You can use

0:07:44.800 --> 0:07:48.640
<v Speaker 1>that for all sorts of reasons. Um. But here's the

0:07:48.640 --> 0:07:51.600
<v Speaker 1>thing about data, about data people, if people know how

0:07:51.640 --> 0:07:58.120
<v Speaker 1>to access it, they can exploit it. Um. Yeah, it's

0:07:58.280 --> 0:08:03.720
<v Speaker 1>it's a bad idea. Uh uh well okay, before ideeah,

0:08:03.800 --> 0:08:07.040
<v Speaker 1>well yeah, I was gonna say this in a specific instance,

0:08:07.200 --> 0:08:10.160
<v Speaker 1>but let me back up for just one second. You

0:08:10.200 --> 0:08:14.560
<v Speaker 1>can there, Uh. Geo tagging is something that you know.

0:08:14.600 --> 0:08:18.600
<v Speaker 1>Of course I knew about it. It's it's pretty common today,

0:08:19.000 --> 0:08:23.080
<v Speaker 1>especially for people with with smartphones. Um. But when I

0:08:23.120 --> 0:08:25.480
<v Speaker 1>when I looked into it looking for a little history,

0:08:25.720 --> 0:08:27.880
<v Speaker 1>as we were wont to do on this show. UM.

0:08:28.440 --> 0:08:31.520
<v Speaker 1>I think the first mentions I saw when they were

0:08:31.520 --> 0:08:33.240
<v Speaker 1>still people were still talking about it as though it

0:08:33.280 --> 0:08:36.360
<v Speaker 1>were a new phenomenon. We're around two thousand seven, two eight,

0:08:37.160 --> 0:08:42.000
<v Speaker 1>and that's when uh, consumer smartphones started becoming more popular.

0:08:42.400 --> 0:08:44.560
<v Speaker 1>The iPhone had come out in two thousand seven, and

0:08:44.600 --> 0:08:47.199
<v Speaker 1>that really launched the smartphone craze, at least in the

0:08:47.280 --> 0:08:51.200
<v Speaker 1>United States. Yeah, for consumers, of course, you know, UM

0:08:51.600 --> 0:08:56.960
<v Speaker 1>and UH, of course there were the uh the memory

0:08:56.960 --> 0:09:01.240
<v Speaker 1>cards used in digital cameras like the I Fi that well,

0:09:01.280 --> 0:09:04.240
<v Speaker 1>even if you don't have a GPS enabled camera will

0:09:04.280 --> 0:09:10.160
<v Speaker 1>store GPS information in the an images metadata UM, which

0:09:10.160 --> 0:09:12.280
<v Speaker 1>is pretty cool because you don't have to have a

0:09:12.320 --> 0:09:15.679
<v Speaker 1>GPS a camera would built in GPS to use that UM.

0:09:15.720 --> 0:09:18.720
<v Speaker 1>And I've read pretty good reviews of that. UM. So

0:09:18.840 --> 0:09:21.240
<v Speaker 1>this is something coming on and now that we can

0:09:21.320 --> 0:09:25.600
<v Speaker 1>do this UM, all sorts of other opportunities have sprung up.

0:09:25.640 --> 0:09:29.880
<v Speaker 1>People use services like UM, like go Wala or four square.

0:09:30.440 --> 0:09:32.880
<v Speaker 1>They want to tag where they are and not necessarily images.

0:09:33.400 --> 0:09:35.640
<v Speaker 1>They'll say, you know, hey, I'm at the pub, you know,

0:09:35.720 --> 0:09:38.200
<v Speaker 1>on the corner and come hang out if you're in

0:09:38.200 --> 0:09:41.840
<v Speaker 1>the neighborhood exactly. UM. Twitter and Twitter is the same way,

0:09:41.880 --> 0:09:44.480
<v Speaker 1>and Facebook as well. They have there's Facebook places and

0:09:44.520 --> 0:09:47.160
<v Speaker 1>there's also that you can turn location data on on

0:09:47.200 --> 0:09:49.840
<v Speaker 1>Twitter if you want to. Yes, that's right, And that's

0:09:49.840 --> 0:09:53.120
<v Speaker 1>exactly where I was going to go with this, UM,

0:09:53.160 --> 0:09:56.000
<v Speaker 1>because you know you can you can say this. You

0:09:56.000 --> 0:09:59.400
<v Speaker 1>can tell people on Twitter and Facebook and UM through

0:09:59.520 --> 0:10:01.959
<v Speaker 1>images you shoot with your phone or your digital camera

0:10:02.000 --> 0:10:05.320
<v Speaker 1>where you are, UM, and that can be great if

0:10:05.320 --> 0:10:07.560
<v Speaker 1>you want to share details about your vacation. Maybe you're

0:10:07.600 --> 0:10:10.360
<v Speaker 1>on a business trip and you're somebody who likes to

0:10:10.480 --> 0:10:15.520
<v Speaker 1>use social media to um point out how you're different

0:10:15.559 --> 0:10:18.120
<v Speaker 1>from everybody else in your colleagues, and that's how you

0:10:18.160 --> 0:10:20.880
<v Speaker 1>network with your colleagues and UM, it shows that you're

0:10:20.920 --> 0:10:24.440
<v Speaker 1>really valuable in your field. Well, maybe you're on a

0:10:24.480 --> 0:10:27.800
<v Speaker 1>business trip and you're taking photos and you're tagging everything

0:10:27.880 --> 0:10:31.199
<v Speaker 1>and you're showing people your exact location, and then people

0:10:31.240 --> 0:10:33.560
<v Speaker 1>realize you're not home. And somebody who happens to know

0:10:33.640 --> 0:10:36.719
<v Speaker 1>who you are, particularly who you are, and maybe they

0:10:36.720 --> 0:10:39.400
<v Speaker 1>know where you live, they go way out. They're not home.

0:10:40.880 --> 0:10:44.400
<v Speaker 1>So if I went to their house, maybe no one

0:10:44.559 --> 0:10:48.360
<v Speaker 1>is there, um, and that can be dangerous. And it's

0:10:48.400 --> 0:10:52.600
<v Speaker 1>it's possible if you don't use your real name on

0:10:52.600 --> 0:10:56.400
<v Speaker 1>on the social network and you're just taking photos, um,

0:10:56.440 --> 0:10:58.079
<v Speaker 1>and you could you could take photos of your summer

0:10:58.120 --> 0:11:00.440
<v Speaker 1>vacation and post them when you get home, and so

0:11:00.520 --> 0:11:04.640
<v Speaker 1>you have your GEO tagged photos and you haven't revealed

0:11:04.640 --> 0:11:07.520
<v Speaker 1>to everybody that you are out last week. It's like, well,

0:11:07.520 --> 0:11:10.800
<v Speaker 1>I'm home now, so I went on a vacation to

0:11:10.880 --> 0:11:12.960
<v Speaker 1>so and so. Here are the photos. Yea, And that's

0:11:13.040 --> 0:11:15.560
<v Speaker 1>that's great. But if you're if you're not careful and

0:11:15.600 --> 0:11:18.880
<v Speaker 1>you post the wrong information, the right the exact right

0:11:18.920 --> 0:11:22.079
<v Speaker 1>information at the wrong time, if you could clue people

0:11:22.080 --> 0:11:24.840
<v Speaker 1>in that you're not home, or if you have people

0:11:24.920 --> 0:11:29.160
<v Speaker 1>that might want to do you harm. I hope that's

0:11:29.200 --> 0:11:32.120
<v Speaker 1>not the case, but yeah, if you have somebody that

0:11:32.240 --> 0:11:35.800
<v Speaker 1>you've upset and they are following you and know exactly

0:11:35.800 --> 0:11:38.160
<v Speaker 1>where you are, then they can come find you. That

0:11:38.200 --> 0:11:40.360
<v Speaker 1>could be a little nerve wracking. We can dive into

0:11:40.400 --> 0:11:42.520
<v Speaker 1>this even a little deeper because there are there are

0:11:42.679 --> 0:11:45.920
<v Speaker 1>very easy ways where people can find out where you

0:11:46.000 --> 0:11:48.920
<v Speaker 1>live that some some of which would be under your

0:11:48.960 --> 0:11:52.040
<v Speaker 1>control and some of which may not. For example, let's

0:11:52.080 --> 0:11:55.880
<v Speaker 1>say that you've taken a photo of either your home

0:11:56.080 --> 0:11:58.240
<v Speaker 1>or your inside your home. Maybe you're throwing a party

0:11:58.280 --> 0:12:00.719
<v Speaker 1>and you're taking pictures of the party, and let's say

0:12:00.720 --> 0:12:03.840
<v Speaker 1>you've got the location data turned on there. Well, that

0:12:03.920 --> 0:12:06.520
<v Speaker 1>metadata is going to be connected to those those images,

0:12:06.640 --> 0:12:11.480
<v Speaker 1>and if you upload those images to certain uh photo albums,

0:12:11.520 --> 0:12:15.280
<v Speaker 1>online photo albums, especially if you have it arranged that

0:12:15.280 --> 0:12:18.840
<v Speaker 1>it's public uh, there's the possibility someone could then pull

0:12:18.880 --> 0:12:21.920
<v Speaker 1>that image, look at the metadata and say, ah, this

0:12:22.000 --> 0:12:24.480
<v Speaker 1>is where this person's houses. I did not know that before.

0:12:24.520 --> 0:12:26.800
<v Speaker 1>But because they've posted these pictures of an event that

0:12:26.840 --> 0:12:29.280
<v Speaker 1>they weren't thinking about, like oh, this shows where my

0:12:29.320 --> 0:12:32.920
<v Speaker 1>house is, they're thinking this was Bob's party as surprise party.

0:12:32.920 --> 0:12:34.360
<v Speaker 1>It was great's a lot of fun. We took all

0:12:34.400 --> 0:12:37.400
<v Speaker 1>these photos. That could be that could lead to be

0:12:37.480 --> 0:12:38.960
<v Speaker 1>a problem. It could also be a problem if you

0:12:39.480 --> 0:12:43.880
<v Speaker 1>if someone who's visiting you takes photos and then they

0:12:44.000 --> 0:12:48.320
<v Speaker 1>upload it into some public online UH photo album and

0:12:48.360 --> 0:12:50.400
<v Speaker 1>their metadata is turned on. In that case, it's not

0:12:50.440 --> 0:12:52.240
<v Speaker 1>even under your control. You're not the one who took

0:12:52.240 --> 0:12:55.040
<v Speaker 1>the photos. But if they tag you in those photos,

0:12:55.160 --> 0:12:57.560
<v Speaker 1>or they mentioned that they're at your house and that

0:12:57.679 --> 0:13:01.040
<v Speaker 1>data is in that if that metadata connected to the photo,

0:13:01.720 --> 0:13:05.040
<v Speaker 1>someone could learn where you live. And this might not

0:13:05.120 --> 0:13:06.680
<v Speaker 1>be a big deal for some of you may not

0:13:06.760 --> 0:13:11.040
<v Speaker 1>think that that's a that scary a notion and and

0:13:11.080 --> 0:13:13.720
<v Speaker 1>for most of it's probably not um but if you

0:13:13.800 --> 0:13:16.280
<v Speaker 1>happen to do things like use Twitter or Facebook to

0:13:16.440 --> 0:13:19.400
<v Speaker 1>post when you go on vacation, like you're saying, I'm

0:13:19.440 --> 0:13:22.600
<v Speaker 1>leaving tonight, I'm so excited, Well, then that you've just

0:13:22.679 --> 0:13:24.920
<v Speaker 1>given the clue that all right, I know where this

0:13:24.960 --> 0:13:26.679
<v Speaker 1>person lives, I know they're not going to be home,

0:13:27.000 --> 0:13:31.960
<v Speaker 1>that this is the perfect opportunity to try and rob them. Now. Uh,

0:13:32.080 --> 0:13:33.920
<v Speaker 1>you know, if you're careful about it and you don't

0:13:33.960 --> 0:13:37.960
<v Speaker 1>share your your address, then there's less danger of that happening.

0:13:38.000 --> 0:13:39.959
<v Speaker 1>If it does happen, you can pretty much narrow it

0:13:40.000 --> 0:13:43.200
<v Speaker 1>down to the people who know you. And then you're thinking, well,

0:13:43.520 --> 0:13:46.120
<v Speaker 1>there's gonna be a reckoning because I know it's one

0:13:46.120 --> 0:13:49.240
<v Speaker 1>of you jerks, and I'm gonna narrow it down. But

0:13:49.240 --> 0:13:51.800
<v Speaker 1>but yeah, like I said, with these these systems, it

0:13:51.840 --> 0:13:54.400
<v Speaker 1>can it can really come back and haunt you. It's

0:13:54.440 --> 0:13:58.320
<v Speaker 1>kind of interesting too, also to see which services preserve

0:13:58.679 --> 0:14:02.160
<v Speaker 1>the meta data and which ones strip it out. So,

0:14:02.240 --> 0:14:05.959
<v Speaker 1>for example, twit pick, the meta data is preserved if

0:14:05.960 --> 0:14:09.440
<v Speaker 1>you turn your location on in whatever device you're using

0:14:09.440 --> 0:14:12.000
<v Speaker 1>to capture the photo, and you turn it on on

0:14:12.080 --> 0:14:14.040
<v Speaker 1>twit pick. Now, granted, like I said, you have to

0:14:14.160 --> 0:14:17.360
<v Speaker 1>choose to share it. Um so that's an opt in,

0:14:17.520 --> 0:14:19.960
<v Speaker 1>which is good. We we like opt in, we don't

0:14:20.000 --> 0:14:22.800
<v Speaker 1>like opt out. You know, where you make the conscious

0:14:22.880 --> 0:14:27.240
<v Speaker 1>choice to share the information as a default. Yes, if

0:14:27.240 --> 0:14:29.920
<v Speaker 1>you if that's the if it's default, to opt into it,

0:14:30.040 --> 0:14:33.640
<v Speaker 1>that's good. Um So if you so, let's say that

0:14:33.760 --> 0:14:35.640
<v Speaker 1>you have all that you share it, that meta data

0:14:35.640 --> 0:14:39.440
<v Speaker 1>will be preserved. What's interesting to me is one major

0:14:39.920 --> 0:14:43.200
<v Speaker 1>place where people store photos that strips the meta data out,

0:14:43.280 --> 0:14:46.360
<v Speaker 1>and I would have never guessed it is it Facebook.

0:14:46.400 --> 0:14:50.160
<v Speaker 1>It is if you upload an image that has meta

0:14:50.240 --> 0:14:52.840
<v Speaker 1>data in it that that connects it to a location,

0:14:53.400 --> 0:14:56.360
<v Speaker 1>and you upload it to your Facebook profile, and then

0:14:56.400 --> 0:14:59.440
<v Speaker 1>someone were to go into that photo album, download the

0:14:59.440 --> 0:15:01.760
<v Speaker 1>image and open it up in some sort of editor

0:15:01.800 --> 0:15:04.280
<v Speaker 1>software to kind of see what the metadata is, they

0:15:04.320 --> 0:15:06.960
<v Speaker 1>are not going to find location data in there. Interested

0:15:07.040 --> 0:15:11.160
<v Speaker 1>strips it out. So Facebook actually does not support geo

0:15:11.200 --> 0:15:13.720
<v Speaker 1>tagging right now as of the recording of this podcast.

0:15:14.120 --> 0:15:17.160
<v Speaker 1>Now could that change? It could and maybe that they

0:15:17.200 --> 0:15:21.800
<v Speaker 1>incorporate pictures in their places. Uh. Feature in places, of course,

0:15:21.880 --> 0:15:26.120
<v Speaker 1>is where you virtually check into locations capital places, yes,

0:15:26.160 --> 0:15:28.840
<v Speaker 1>and and other people can check you into there as well.

0:15:28.960 --> 0:15:31.920
<v Speaker 1>You have to improve it, but other people, like let's

0:15:31.920 --> 0:15:34.640
<v Speaker 1>say that you're at a restaurant and your friends are there,

0:15:34.840 --> 0:15:36.880
<v Speaker 1>and your friends are on you know, going through the

0:15:36.920 --> 0:15:39.480
<v Speaker 1>Facebook places to check in, they can check you in

0:15:39.600 --> 0:15:41.680
<v Speaker 1>as well, but you have to approve it before it

0:15:41.720 --> 0:15:45.360
<v Speaker 1>will pop up everywhere. Um, there may come a time

0:15:45.360 --> 0:15:48.840
<v Speaker 1>where photographs are also supported by this feature. Right now

0:15:48.880 --> 0:15:52.320
<v Speaker 1>they are not again as of the recording of this podcast.

0:15:52.840 --> 0:15:55.560
<v Speaker 1>So that was interesting to me that Facebook does not

0:15:55.720 --> 0:15:59.080
<v Speaker 1>actually support geo tagging. Now you could still tell people

0:15:59.080 --> 0:16:01.800
<v Speaker 1>where that was like if you wanted to. I mean,

0:16:01.800 --> 0:16:03.840
<v Speaker 1>there's nothing stopping you from putting it in the caption.

0:16:04.240 --> 0:16:07.480
<v Speaker 1>And there are also services out there that allow you

0:16:07.520 --> 0:16:11.280
<v Speaker 1>to upload photos and then you put them on a map.

0:16:11.640 --> 0:16:15.400
<v Speaker 1>Like you you you physically in input the address into

0:16:16.000 --> 0:16:19.480
<v Speaker 1>the service, so it's not pulling from the meta data

0:16:19.560 --> 0:16:24.680
<v Speaker 1>of the picture. It's requiring user input to geographically placed photos.

0:16:24.680 --> 0:16:26.760
<v Speaker 1>That's a little different. It still can come back and

0:16:26.800 --> 0:16:31.000
<v Speaker 1>haunt you. Yeah. Yeah, Now, I mean another example of

0:16:31.600 --> 0:16:35.280
<v Speaker 1>something there. There have been a number of articles, uh

0:16:35.320 --> 0:16:40.320
<v Speaker 1>in the media recently about geotagging and the possibility that

0:16:40.360 --> 0:16:44.720
<v Speaker 1>it could lead to trouble if you're not careful, and

0:16:45.000 --> 0:16:46.800
<v Speaker 1>one of those was, you know, if you have a

0:16:46.800 --> 0:16:50.720
<v Speaker 1>lot of maybe you're taking you finally splurged and got

0:16:50.720 --> 0:16:54.120
<v Speaker 1>that home entertainment system that you've always been wanting, and

0:16:54.120 --> 0:16:56.680
<v Speaker 1>then you take photos of it and you know, share

0:16:56.720 --> 0:16:59.920
<v Speaker 1>that in public with people, and you didn't turn off

0:16:59.920 --> 0:17:03.200
<v Speaker 1>the geo tagging on your phone, and some random person

0:17:03.280 --> 0:17:04.960
<v Speaker 1>happens on it and goes, well, it is a really

0:17:05.080 --> 0:17:08.920
<v Speaker 1>nice new entertainment system. I wonder if they're home during

0:17:08.920 --> 0:17:11.359
<v Speaker 1>the week during normal business hours where most people are

0:17:11.359 --> 0:17:16.800
<v Speaker 1>out working, and I have their exact location, so yeah,

0:17:16.800 --> 0:17:19.200
<v Speaker 1>that that could be that could be hazardous. So yeah,

0:17:19.240 --> 0:17:21.160
<v Speaker 1>I mean, there are so many things that you could

0:17:21.200 --> 0:17:26.400
<v Speaker 1>use it for, uh, for good purposes, um, you know research, um,

0:17:26.440 --> 0:17:31.199
<v Speaker 1>you know, personal research, geneal genealogical research. Um. You can

0:17:31.280 --> 0:17:34.960
<v Speaker 1>use it for geocashing purposes too. We had that that

0:17:35.080 --> 0:17:38.960
<v Speaker 1>great podcast a long time ago. Now it seems like, um,

0:17:39.000 --> 0:17:40.560
<v Speaker 1>but yeah, I mean they're there are games that you

0:17:40.600 --> 0:17:44.440
<v Speaker 1>can play with geographical information. Um, you just have to

0:17:44.480 --> 0:17:47.679
<v Speaker 1>be careful what you what you're sharing, and don't forget

0:17:47.720 --> 0:17:50.000
<v Speaker 1>that there may be some kinds of information you do

0:17:50.040 --> 0:17:52.320
<v Speaker 1>want to tag in some that you don't. Yeah, if

0:17:52.320 --> 0:17:54.840
<v Speaker 1>you're making a travel guide for someone and you're giving

0:17:54.880 --> 0:17:57.440
<v Speaker 1>them suggestions of where to go within a certain city,

0:17:57.720 --> 0:17:59.879
<v Speaker 1>geo tagging is a great tool. If you're using a

0:18:00.119 --> 0:18:03.320
<v Speaker 1>website and interactive website to show people, Look, you know,

0:18:03.440 --> 0:18:05.520
<v Speaker 1>just down the street from this one museum, is this

0:18:05.600 --> 0:18:09.359
<v Speaker 1>really cool restaurant that, uh that I recommend because of

0:18:09.359 --> 0:18:11.399
<v Speaker 1>blah blah blah. You know that sort of stuff. It

0:18:11.400 --> 0:18:14.560
<v Speaker 1>comes in really handy. But yeah, there are other besides

0:18:14.640 --> 0:18:19.840
<v Speaker 1>the whole burglary uh possibility. There's also the question of

0:18:19.880 --> 0:18:23.240
<v Speaker 1>things like attracting the wrong sort of attention, like stalkers.

0:18:23.800 --> 0:18:28.040
<v Speaker 1>That's a very real concern, um, especially if you're using

0:18:28.080 --> 0:18:32.240
<v Speaker 1>something like Twitter and you don't have a protected uh feed,

0:18:32.560 --> 0:18:35.159
<v Speaker 1>Like if you if you have a public feed, that

0:18:35.200 --> 0:18:38.359
<v Speaker 1>means every single thing you publish is going to be

0:18:38.440 --> 0:18:41.560
<v Speaker 1>published on the public feed and theoretically anyone can see it.

0:18:42.240 --> 0:18:45.359
<v Speaker 1>So let's say that you are, I don't know, a

0:18:45.560 --> 0:18:50.679
<v Speaker 1>dashingly handsome co host of a technology podcast, and you

0:18:50.760 --> 0:18:53.280
<v Speaker 1>take pictures of all your favorite places that you like

0:18:53.359 --> 0:18:57.879
<v Speaker 1>to go. And then some uh incredibly attractive young lady

0:18:58.240 --> 0:19:03.760
<v Speaker 1>who has desires upon this bald, handsome co host of

0:19:03.800 --> 0:19:06.399
<v Speaker 1>a technology podcast where to look at those photos and

0:19:06.440 --> 0:19:09.280
<v Speaker 1>that meta data and say, hey, these are his favorite spots.

0:19:09.560 --> 0:19:11.359
<v Speaker 1>All I have to do is go to one of these,

0:19:11.480 --> 0:19:13.119
<v Speaker 1>and sooner or later he's going to show up, and

0:19:13.119 --> 0:19:15.120
<v Speaker 1>then I can tell him how much I love him.

0:19:15.200 --> 0:19:18.520
<v Speaker 1>Why has that not happened yet? I guess I haven't

0:19:18.560 --> 0:19:21.920
<v Speaker 1>turned that GPS information on. That's the problem. I haven't,

0:19:22.119 --> 0:19:25.840
<v Speaker 1>dang it. You know, there's always something, but no, no, seriously, though,

0:19:25.840 --> 0:19:28.119
<v Speaker 1>to be to be, I'm making light of it, but

0:19:28.160 --> 0:19:31.159
<v Speaker 1>this is really a very serious situation, and that you know,

0:19:31.240 --> 0:19:33.520
<v Speaker 1>you you need to be aware that the information you're

0:19:33.520 --> 0:19:37.240
<v Speaker 1>sharing could, if you're not careful with it, be used

0:19:37.280 --> 0:19:40.800
<v Speaker 1>by other people to to harass you, and uh, you know,

0:19:41.920 --> 0:19:45.200
<v Speaker 1>and that we don't want to see that happen. Now Again,

0:19:45.359 --> 0:19:49.399
<v Speaker 1>we are not telling you don't use geotagging, just be

0:19:49.560 --> 0:19:53.120
<v Speaker 1>aware of when you're using it, the situations you're using

0:19:53.119 --> 0:19:56.280
<v Speaker 1>it in and the purpose you're using it. Um, Because

0:19:56.400 --> 0:19:58.440
<v Speaker 1>again it could be a really fun way to share

0:19:58.440 --> 0:20:03.600
<v Speaker 1>information about yourself, but you may not want to share everything. Yeah, yeah,

0:20:03.680 --> 0:20:07.160
<v Speaker 1>I think that's a that's a good point. Um. It's

0:20:07.200 --> 0:20:08.879
<v Speaker 1>just it's just one of those things where we're not

0:20:08.920 --> 0:20:13.240
<v Speaker 1>saying no, don't ever do it. Just um, you know,

0:20:13.359 --> 0:20:16.080
<v Speaker 1>just think about it. And yeah, the odds someone will

0:20:16.440 --> 0:20:21.280
<v Speaker 1>someone when someone will invariably right in and say, you know,

0:20:21.400 --> 0:20:25.040
<v Speaker 1>you said geotagging was bad and I shouldn't do it, well, yeah,

0:20:25.119 --> 0:20:27.480
<v Speaker 1>the odds are pretty slim that some of this is

0:20:27.480 --> 0:20:31.440
<v Speaker 1>going to happen. Um, But you know, just think about it.

0:20:31.440 --> 0:20:33.960
<v Speaker 1>It's just like, just like if you live in uh,

0:20:34.000 --> 0:20:39.160
<v Speaker 1>you know, a pretty heavily um popular popularized area. Right.

0:20:39.400 --> 0:20:41.719
<v Speaker 1>Let's say like you live in a in a big city, right,

0:20:42.160 --> 0:20:45.600
<v Speaker 1>you don't normally leave your car unlocked, or you'll leave

0:20:45.680 --> 0:20:50.400
<v Speaker 1>your house or apartment unlocked, because even though the likelihood

0:20:50.600 --> 0:20:53.200
<v Speaker 1>that you'll be targeted or for a home invasion or

0:20:53.280 --> 0:20:57.040
<v Speaker 1>a car burglary is low, you don't go tempting fate.

0:20:57.760 --> 0:21:01.040
<v Speaker 1>Same sort of thing, and again, you know their ties

0:21:01.080 --> 0:21:03.399
<v Speaker 1>when you using geo tagging is perfectly fine. You just

0:21:03.720 --> 0:21:05.600
<v Speaker 1>you may not want to use it all the time.

0:21:05.640 --> 0:21:08.600
<v Speaker 1>Like you're visiting your buddy and you're taking pictures, you

0:21:08.680 --> 0:21:10.560
<v Speaker 1>might want to You might want to at least ask

0:21:10.960 --> 0:21:13.840
<v Speaker 1>your friend, like should I turn GEO tagging off? Because

0:21:14.160 --> 0:21:17.400
<v Speaker 1>otherwise people are gonna know exactly where this place is. Well, yeah,

0:21:17.400 --> 0:21:19.400
<v Speaker 1>and that's funny because that you would say that, because

0:21:19.400 --> 0:21:23.560
<v Speaker 1>I was thinking specifically of the rash of um break

0:21:23.600 --> 0:21:26.360
<v Speaker 1>ins that has been happening in businesses here in Atlanta

0:21:26.560 --> 0:21:29.320
<v Speaker 1>over the past few months. A lot of there have

0:21:29.359 --> 0:21:32.000
<v Speaker 1>been a lot of break ins and smallish businesses like

0:21:32.760 --> 0:21:36.000
<v Speaker 1>strip malls, uh, from people who are breaking in to

0:21:36.200 --> 0:21:40.440
<v Speaker 1>steal flat screen TVs off the walls, places that are

0:21:40.520 --> 0:21:44.040
<v Speaker 1>that are offering TV for their customers in waiting rooms

0:21:44.040 --> 0:21:47.120
<v Speaker 1>and things like that. Um. And you know, if you're

0:21:47.119 --> 0:21:51.000
<v Speaker 1>taking a picture of some place while you're out, UM

0:21:51.000 --> 0:21:55.320
<v Speaker 1>what GEO tagging information? It's not necessarily your information, or

0:21:55.400 --> 0:21:57.960
<v Speaker 1>you might be the business owner and people are you know, Hey,

0:21:58.000 --> 0:22:00.159
<v Speaker 1>this is the cool place where I like to go

0:22:00.240 --> 0:22:02.439
<v Speaker 1>on on Thursdays. You know everybody who's here we have

0:22:02.480 --> 0:22:05.359
<v Speaker 1>trivia night or whatever. And uh, if you happen to

0:22:05.400 --> 0:22:09.080
<v Speaker 1>tag that information and uh, it gets posted to the net.

0:22:09.320 --> 0:22:14.200
<v Speaker 1>It could reveal information about your establishment with the kind

0:22:14.200 --> 0:22:17.520
<v Speaker 1>of equipment that you have available, and it could inadvertently

0:22:18.359 --> 0:22:21.879
<v Speaker 1>make it known to uh, to thieves. So that's you know,

0:22:22.119 --> 0:22:25.840
<v Speaker 1>of course, some businesses go ahead and advertise that you

0:22:25.920 --> 0:22:29.640
<v Speaker 1>want to yeah, and I'm not saying that, Yeah, I'm sorry,

0:22:29.680 --> 0:22:31.680
<v Speaker 1>I didn't mean to uh, I don't mean to intimate

0:22:31.760 --> 0:22:34.879
<v Speaker 1>that that's the reason that that happened, but it could.

0:22:34.920 --> 0:22:38.520
<v Speaker 1>It could give people clues. And again, if you're the

0:22:38.560 --> 0:22:41.040
<v Speaker 1>business owner, then you're gonna say, hey, look, I've got

0:22:41.040 --> 0:22:44.160
<v Speaker 1>this great entertainment. You're gonna advertise that. You're not necessarily

0:22:44.160 --> 0:22:46.880
<v Speaker 1>going to stop somebody from taking a photo of uh,

0:22:46.920 --> 0:22:49.160
<v Speaker 1>their friends having a good time at this place, because

0:22:49.160 --> 0:22:51.360
<v Speaker 1>they're gonna say, well, yeah, I want that will build bell,

0:22:51.440 --> 0:22:55.199
<v Speaker 1>build word of mouth. You know, it's it's it's a

0:22:55.200 --> 0:22:58.080
<v Speaker 1>tricky situation. I mean, it's one of those things where, uh,

0:22:58.119 --> 0:23:00.320
<v Speaker 1>you know, you weren't you wouldn't necessarily think of it.

0:23:01.160 --> 0:23:03.720
<v Speaker 1>Even a few years ago. I wanted to kind of

0:23:03.920 --> 0:23:07.280
<v Speaker 1>segue this into a discussion about privacy in the web

0:23:07.359 --> 0:23:11.320
<v Speaker 1>in general, in the sense that I recently read an

0:23:11.480 --> 0:23:14.840
<v Speaker 1>essay and then responded to it. The essay was Your

0:23:14.920 --> 0:23:18.680
<v Speaker 1>Life torn? Open Sharing is a Trap written by Andrew Keene.

0:23:18.720 --> 0:23:23.119
<v Speaker 1>It was published on Wired dot co dot UK on

0:23:23.200 --> 0:23:30.160
<v Speaker 1>February three eleven, and in it, Keen bemoans the fact

0:23:30.280 --> 0:23:33.919
<v Speaker 1>that we are reaching a point where everyone is sharing

0:23:34.160 --> 0:23:37.840
<v Speaker 1>lots of information about themselves, not just geotagging, but that

0:23:37.960 --> 0:23:40.320
<v Speaker 1>is an element of it, but everything like you know,

0:23:40.520 --> 0:23:46.760
<v Speaker 1>thoughts and uh and relationships, and that privacy is becoming

0:23:47.080 --> 0:23:53.520
<v Speaker 1>decreasingly important. So Keen's point was that this is going

0:23:53.600 --> 0:23:57.600
<v Speaker 1>to mean that humanity itself will change, because privacy is

0:23:57.680 --> 0:24:01.200
<v Speaker 1>part of being human, and if we are adicate privacy,

0:24:01.320 --> 0:24:03.879
<v Speaker 1>then we're eradicating part of what it is to be human.

0:24:04.680 --> 0:24:08.679
<v Speaker 1>H and I took Umbridge to a couple of his points,

0:24:08.680 --> 0:24:12.400
<v Speaker 1>one of which was that I don't feel that that

0:24:12.800 --> 0:24:17.200
<v Speaker 1>social networking necessarily means that you lose all your privacy

0:24:17.920 --> 0:24:20.879
<v Speaker 1>because in most of these situations you have, First of all,

0:24:20.920 --> 0:24:22.680
<v Speaker 1>you have the choice of whether or not to use

0:24:22.720 --> 0:24:25.520
<v Speaker 1>the social networking at all. Yes, and that is an

0:24:25.560 --> 0:24:29.560
<v Speaker 1>important thing to note. It's not compulsory. Yeah, there's no

0:24:29.640 --> 0:24:32.760
<v Speaker 1>there's no law that says you have to be on Twitter, Facebook,

0:24:33.440 --> 0:24:37.680
<v Speaker 1>etcetera right. And second of all, you most of these

0:24:37.680 --> 0:24:41.240
<v Speaker 1>services have levels of protection that you can choose to

0:24:41.400 --> 0:24:45.280
<v Speaker 1>either initiate or turn off. For example, with the twit

0:24:45.359 --> 0:24:47.840
<v Speaker 1>pick thing that I mentioned, you know, again you have

0:24:47.920 --> 0:24:51.040
<v Speaker 1>to have the GPS location stuff turned on your smartphone

0:24:51.119 --> 0:24:53.520
<v Speaker 1>or camera and you have to have it turned on

0:24:53.520 --> 0:24:56.000
<v Speaker 1>on twit pick for that to take effect. If it's

0:24:56.000 --> 0:24:58.480
<v Speaker 1>not turned on on twit pick, that metadata will not

0:24:58.520 --> 0:25:01.840
<v Speaker 1>be included. And so you don't you know, you have

0:25:01.960 --> 0:25:06.280
<v Speaker 1>to choose to to share this information. So it's not

0:25:06.359 --> 0:25:09.520
<v Speaker 1>like it's something where Big Brother has appeared and we're

0:25:09.560 --> 0:25:11.560
<v Speaker 1>all four. He was making a lot of nineteen eight

0:25:11.680 --> 0:25:14.640
<v Speaker 1>four references. And here's the thing is that in nineteen four,

0:25:14.680 --> 0:25:17.800
<v Speaker 1>if you don't know that story into it's a government

0:25:17.920 --> 0:25:22.280
<v Speaker 1>mandated society where people are under observation all the time

0:25:22.840 --> 0:25:28.200
<v Speaker 1>by a very oppressive, very invasive government. There's no choice there.

0:25:28.760 --> 0:25:31.800
<v Speaker 1>But with with social networking there is. It's all choice.

0:25:32.000 --> 0:25:33.919
<v Speaker 1>You can choose. You know, how much you share and

0:25:33.920 --> 0:25:37.680
<v Speaker 1>how little you share. And uh, I also just don't

0:25:37.720 --> 0:25:40.360
<v Speaker 1>think that it's going to lead to the downfall of mankind.

0:25:40.480 --> 0:25:43.800
<v Speaker 1>So I had some some things to say about that,

0:25:43.880 --> 0:25:45.560
<v Speaker 1>and if you want to read more, I wrote a

0:25:45.560 --> 0:25:48.639
<v Speaker 1>blog post about and if you want to read keynes essay,

0:25:48.720 --> 0:25:50.920
<v Speaker 1>I do recommend reading it. He makes some good points

0:25:51.000 --> 0:25:53.200
<v Speaker 1>things that I do not disagree with. I just felt

0:25:53.240 --> 0:25:57.200
<v Speaker 1>that some of his central premises were a little faulty. Um.

0:25:57.280 --> 0:26:01.760
<v Speaker 1>And the other element is the idea between using the

0:26:01.800 --> 0:26:05.800
<v Speaker 1>internet to share this information versus using your memory to

0:26:05.920 --> 0:26:09.480
<v Speaker 1>remember stuff. Because we've talked about that in the past.

0:26:09.520 --> 0:26:13.480
<v Speaker 1>We talked about Nicholas cars famous article is Google making

0:26:13.480 --> 0:26:18.240
<v Speaker 1>as stupid? We did a whole episode about that. Um.

0:26:18.320 --> 0:26:22.479
<v Speaker 1>The idea being that we are using computers and the

0:26:22.520 --> 0:26:26.879
<v Speaker 1>cloud to store information that normally we would just store

0:26:26.920 --> 0:26:30.760
<v Speaker 1>in our own memories. Uh. Nicolas cars point was that

0:26:31.359 --> 0:26:34.600
<v Speaker 1>he he felt he was losing This was very anecdotal,

0:26:34.680 --> 0:26:37.200
<v Speaker 1>but he felt he was losing the ability to retain

0:26:37.359 --> 0:26:42.679
<v Speaker 1>information that he couldn't even maintain focus on anything that

0:26:42.840 --> 0:26:46.680
<v Speaker 1>took longer than a few minutes because the Internet had

0:26:47.000 --> 0:26:51.200
<v Speaker 1>conditioned him, right, the web had conditioned him to accept

0:26:51.200 --> 0:26:55.560
<v Speaker 1>information in in website like a web page sized amount

0:26:55.640 --> 0:26:57.760
<v Speaker 1>and then that's it. You can't go more than that.

0:26:57.800 --> 0:27:00.200
<v Speaker 1>So he couldn't read a book anymore. Yeah, I think

0:27:00.200 --> 0:27:03.880
<v Speaker 1>that's funny because that's that's one of the points that

0:27:04.000 --> 0:27:08.640
<v Speaker 1>David Allen makes in his Getting Things Done is life

0:27:08.640 --> 0:27:10.280
<v Speaker 1>can be very stressful if you have a lot of

0:27:10.320 --> 0:27:14.000
<v Speaker 1>things to manage. So writing things down or recording them

0:27:14.000 --> 0:27:16.800
<v Speaker 1>in some fashion it doesn't necessarily had to be written,

0:27:17.280 --> 0:27:20.679
<v Speaker 1>UM is as a good way to take the stress

0:27:20.720 --> 0:27:22.320
<v Speaker 1>off because once you have it written down in a

0:27:22.359 --> 0:27:24.760
<v Speaker 1>place where you're going to go back and look you,

0:27:24.760 --> 0:27:28.280
<v Speaker 1>you're less likely to forget to do that thing, to

0:27:28.320 --> 0:27:30.000
<v Speaker 1>accomplish that thing. And that's just one of the points

0:27:30.000 --> 0:27:31.440
<v Speaker 1>he made. It's one of many points he makes in

0:27:31.480 --> 0:27:34.760
<v Speaker 1>the book. UM The important thing again to notice he

0:27:34.840 --> 0:27:38.119
<v Speaker 1>suggests writing it down like on a paper planner is

0:27:38.240 --> 0:27:39.960
<v Speaker 1>sort of where he started. He said, well, you know,

0:27:40.000 --> 0:27:42.160
<v Speaker 1>if you have an electronic system that you prefer to use,

0:27:42.359 --> 0:27:46.159
<v Speaker 1>but it's not the technology specific. It's not because we

0:27:46.240 --> 0:27:50.920
<v Speaker 1>have Twitter and geotagging that we're giving away our privacy.

0:27:50.960 --> 0:27:53.960
<v Speaker 1>It's what we're what we're doing with the technology as

0:27:54.000 --> 0:27:57.720
<v Speaker 1>individuals and making our individual choices on what to do

0:27:57.800 --> 0:28:01.120
<v Speaker 1>with that technology, no matter. I mean, could write your

0:28:01.400 --> 0:28:04.320
<v Speaker 1>location down on a piece of paper and yeah, you know,

0:28:04.400 --> 0:28:06.560
<v Speaker 1>copy it five times and give it out to people,

0:28:07.200 --> 0:28:08.639
<v Speaker 1>you wouldn't have the same reach as you would if

0:28:08.640 --> 0:28:10.440
<v Speaker 1>you were doing this on the Internet, but you're still

0:28:10.520 --> 0:28:14.440
<v Speaker 1>giving away important information about you. So yeah, I mean

0:28:14.560 --> 0:28:18.520
<v Speaker 1>it's it's not the technology per se, it's what you're

0:28:18.520 --> 0:28:20.240
<v Speaker 1>doing with it, and then what you're sharing with it.

0:28:20.400 --> 0:28:25.240
<v Speaker 1>It matters. And and I really find cars point interesting

0:28:25.280 --> 0:28:28.320
<v Speaker 1>and the idea that he thinks it's it's a scary

0:28:28.400 --> 0:28:32.040
<v Speaker 1>thing to be to lose that ability to retain information,

0:28:32.560 --> 0:28:34.960
<v Speaker 1>you know, because we essentially feel like we've offloaded that

0:28:35.040 --> 0:28:36.879
<v Speaker 1>off our brains so we can free up our brains.

0:28:36.920 --> 0:28:38.920
<v Speaker 1>We don't need to remember stuff because it's somewhere else.

0:28:39.000 --> 0:28:41.440
<v Speaker 1>For example, I used to be able to rattle off

0:28:41.640 --> 0:28:44.840
<v Speaker 1>the phone numbers of all of my close friends and

0:28:44.880 --> 0:28:48.000
<v Speaker 1>my family members, and now I'm able to remember about

0:28:48.160 --> 0:28:50.160
<v Speaker 1>four of them. Yes, because you have them in your

0:28:50.160 --> 0:28:52.520
<v Speaker 1>smart exactly, They're all in my context list. I don't

0:28:52.520 --> 0:28:54.080
<v Speaker 1>have to remember. I just go to the picture of

0:28:54.120 --> 0:28:56.240
<v Speaker 1>the person, say, Hey, there's the dude I want to

0:28:56.280 --> 0:28:59.800
<v Speaker 1>talk to, click on his picture, and there I go. Um, So, yeah,

0:29:00.200 --> 0:29:02.920
<v Speaker 1>is something to his argument. What I thought was interesting

0:29:03.000 --> 0:29:07.360
<v Speaker 1>is I read another point where this seems like, uh,

0:29:07.480 --> 0:29:10.920
<v Speaker 1>it's almost the opposite. Take A fellow by the name

0:29:10.960 --> 0:29:14.600
<v Speaker 1>of Kevin Slaven wrote an essay called the Ebb of Memory.

0:29:15.000 --> 0:29:17.600
<v Speaker 1>This was part of a book called This Will Change

0:29:17.640 --> 0:29:21.920
<v Speaker 1>Everything's a series of essays from various experts in various fields,

0:29:21.960 --> 0:29:24.800
<v Speaker 1>kind of giving their take on what will change everything.

0:29:25.160 --> 0:29:27.240
<v Speaker 1>As a matter of fact, several copies have been floating

0:29:27.280 --> 0:29:33.959
<v Speaker 1>around the Yes. So Slavens point was that it was,

0:29:34.120 --> 0:29:36.000
<v Speaker 1>like I said, kind of the opposite. He said that

0:29:36.120 --> 0:29:39.160
<v Speaker 1>human memory, the fact that human memory degrades over time

0:29:39.800 --> 0:29:43.160
<v Speaker 1>is a good thing. That that the typical person, they

0:29:43.240 --> 0:29:46.400
<v Speaker 1>will experience something, they will remember it, and over time

0:29:46.880 --> 0:29:50.880
<v Speaker 1>aspects of that memory will change. We will drop certain details,

0:29:50.920 --> 0:29:53.760
<v Speaker 1>we may add certain things that did not happen into

0:29:53.800 --> 0:29:57.120
<v Speaker 1>the memory, and we will misremember. I mean, this is

0:29:57.160 --> 0:30:02.080
<v Speaker 1>why anecdotal evidence is not entirely uh, you know, reliable.

0:30:02.480 --> 0:30:06.320
<v Speaker 1>It's why when you bring witnesses in court cases, especially

0:30:06.360 --> 0:30:10.160
<v Speaker 1>for something that happened years and years ago, the testimonial

0:30:10.760 --> 0:30:15.400
<v Speaker 1>uh evidence is sometimes less reliable than any physical evidence

0:30:15.440 --> 0:30:19.240
<v Speaker 1>you found, right, because we don't remember things exactly the

0:30:19.240 --> 0:30:22.080
<v Speaker 1>way they happen necessarily uh. And he says this is

0:30:22.120 --> 0:30:24.880
<v Speaker 1>a good thing because if something tragic happens in our lives,

0:30:24.960 --> 0:30:28.680
<v Speaker 1>over time, we are able to distance ourselves. We forget

0:30:28.720 --> 0:30:32.040
<v Speaker 1>certain things. We don't feel that pain the same way

0:30:32.040 --> 0:30:34.560
<v Speaker 1>when we think back as we did when it happened.

0:30:34.880 --> 0:30:39.800
<v Speaker 1>There are people who have perfect memory, total recall, where

0:30:39.840 --> 0:30:43.080
<v Speaker 1>they are able to remember every single thing that they've

0:30:43.160 --> 0:30:49.320
<v Speaker 1>encountered with absolute clarity. And they explained they described their situation,

0:30:49.360 --> 0:30:53.240
<v Speaker 1>their their their experiences as being just as raw as

0:30:53.280 --> 0:30:56.120
<v Speaker 1>when it first happened. So the happiest moments of their lives,

0:30:56.360 --> 0:30:59.200
<v Speaker 1>when they think on those moments, they experience those emotions

0:30:59.200 --> 0:31:01.240
<v Speaker 1>as if it had just happen. Same thing with the

0:31:01.280 --> 0:31:05.040
<v Speaker 1>most tragic things. And Slaven's point is that that is

0:31:05.240 --> 0:31:08.120
<v Speaker 1>that is really a tough life. It is hard to

0:31:08.160 --> 0:31:10.200
<v Speaker 1>live that life where you can think back on the

0:31:10.240 --> 0:31:13.200
<v Speaker 1>things that happened that maybe you're ashamed of, or maybe

0:31:13.520 --> 0:31:15.880
<v Speaker 1>something that just hurt your feelings, and to experience that

0:31:15.920 --> 0:31:17.640
<v Speaker 1>all over again, it's really hard to live with that.

0:31:18.320 --> 0:31:20.840
<v Speaker 1>His point was that by offloading all this on the web,

0:31:21.600 --> 0:31:25.719
<v Speaker 1>we are preserving that information. All the information exists on

0:31:25.800 --> 0:31:28.560
<v Speaker 1>computers or in the cloud, we can access it at

0:31:28.600 --> 0:31:32.560
<v Speaker 1>any time. And then because information on computers and in

0:31:32.600 --> 0:31:36.480
<v Speaker 1>the cloud does not change, it's not like computers forget things.

0:31:36.760 --> 0:31:39.640
<v Speaker 1>We're going to see the details exactly as how we

0:31:39.720 --> 0:31:42.479
<v Speaker 1>it we first put them in when we recorded them

0:31:42.480 --> 0:31:47.960
<v Speaker 1>the first time. And so Slaven's argument was that that this,

0:31:47.960 --> 0:31:52.040
<v Speaker 1>this this sharing that we're doing, this disregard of privacy,

0:31:52.400 --> 0:31:54.880
<v Speaker 1>will ultimately mean that we will live as if we

0:31:54.960 --> 0:31:58.120
<v Speaker 1>have perfect memories, and that as a result, we will

0:31:58.160 --> 0:32:02.440
<v Speaker 1>always be endanger of feeling the highest of highs and

0:32:02.440 --> 0:32:06.360
<v Speaker 1>the lowest of lows because we are not giving our

0:32:06.400 --> 0:32:09.520
<v Speaker 1>memory the chance to incorporate these things into our experience

0:32:09.600 --> 0:32:13.040
<v Speaker 1>and then just uh and and and evolve over time.

0:32:14.080 --> 0:32:16.440
<v Speaker 1>So that's kind of fascinating too. And again it it

0:32:16.480 --> 0:32:21.040
<v Speaker 1>relates back to geotagging, because we can now record the

0:32:21.040 --> 0:32:23.760
<v Speaker 1>events of our lives on with a level of detail

0:32:24.000 --> 0:32:26.520
<v Speaker 1>that is far beyond anything that anyone else has been

0:32:26.560 --> 0:32:29.640
<v Speaker 1>able to do automatically, right, Like, I mean, you could

0:32:29.680 --> 0:32:32.000
<v Speaker 1>have done it in the past, but it took more work.

0:32:32.240 --> 0:32:35.600
<v Speaker 1>It took your work to do that. Yeah. Yeah, it's

0:32:35.600 --> 0:32:38.680
<v Speaker 1>funny because one of the articles that I read in preparation,

0:32:39.160 --> 0:32:43.120
<v Speaker 1>uh for the podcast was an older piece that Charlie

0:32:43.200 --> 0:32:46.400
<v Speaker 1>Sorrel did for Wired. I mean this was this was

0:32:46.440 --> 0:32:51.200
<v Speaker 1>really before there were automated systems. I mean, I'm sure

0:32:51.240 --> 0:32:53.520
<v Speaker 1>there were things that that you could do, but he

0:32:53.640 --> 0:32:57.240
<v Speaker 1>was relying on the then new memory cards that had

0:32:57.480 --> 0:33:01.440
<v Speaker 1>built in GPS system. UM. So he said, you know,

0:33:01.640 --> 0:33:05.320
<v Speaker 1>basically that the the technology hadn't been made popular at

0:33:05.360 --> 0:33:09.880
<v Speaker 1>that point to automatically geotag and send photos. UM. So

0:33:09.880 --> 0:33:12.960
<v Speaker 1>it's still sort of a new thing. And you know,

0:33:13.080 --> 0:33:14.960
<v Speaker 1>you could use if you could sync up the date

0:33:15.800 --> 0:33:19.200
<v Speaker 1>or the time actually the time on your GPS receiver

0:33:19.400 --> 0:33:22.480
<v Speaker 1>and your your camera. If you have the timestamp, then

0:33:22.480 --> 0:33:24.239
<v Speaker 1>it's you know, easy to sync up. As you were

0:33:24.240 --> 0:33:28.480
<v Speaker 1>saying before, Um, you may not necessarily have the information stored. Uh,

0:33:28.520 --> 0:33:30.440
<v Speaker 1>you may have to write it down, but at least

0:33:30.480 --> 0:33:34.000
<v Speaker 1>you had some sort of record of doing that. Um.

0:33:34.040 --> 0:33:36.360
<v Speaker 1>You know, so there there were ways to do that

0:33:36.440 --> 0:33:40.360
<v Speaker 1>even before it became a popular technology to build right

0:33:40.400 --> 0:33:43.320
<v Speaker 1>in of course those of us with smartphones. UM. You know,

0:33:43.360 --> 0:33:45.240
<v Speaker 1>I've been playing around with that since I got an

0:33:45.280 --> 0:33:48.640
<v Speaker 1>Android found myself. UM and it's uh, you know, it's

0:33:48.680 --> 0:33:52.520
<v Speaker 1>so much easier now to automatically do it. Um. And

0:33:52.560 --> 0:33:54.840
<v Speaker 1>I think that that can be the problem if you're

0:33:55.080 --> 0:33:57.880
<v Speaker 1>somebody who wants to do it sometimes but not other times.

0:33:57.920 --> 0:34:01.440
<v Speaker 1>If you just leave it enabled, you may inadvertently uh

0:34:01.520 --> 0:34:03.960
<v Speaker 1>save information, or if you leave it off all the time,

0:34:04.000 --> 0:34:06.800
<v Speaker 1>you may wish you had done it later, you know. Yeah,

0:34:07.120 --> 0:34:09.040
<v Speaker 1>and we should point out that. You know, I talked

0:34:09.040 --> 0:34:11.560
<v Speaker 1>to a lot about the services that automatically incorporate the

0:34:11.600 --> 0:34:15.160
<v Speaker 1>meta data into them. You don't even if you aren't

0:34:15.200 --> 0:34:17.400
<v Speaker 1>using a service that does that. If there, if the

0:34:17.440 --> 0:34:19.880
<v Speaker 1>metadata is there, it is possible to see it. It

0:34:19.960 --> 0:34:22.080
<v Speaker 1>just means that the person who's looking at the photo

0:34:22.160 --> 0:34:25.040
<v Speaker 1>has to open it in an application that will show

0:34:25.080 --> 0:34:28.040
<v Speaker 1>that metadata. So a lot of photo editors do it.

0:34:28.120 --> 0:34:31.640
<v Speaker 1>Even photo viewers in the more recent operating systems will

0:34:31.719 --> 0:34:34.360
<v Speaker 1>let you see that. If you have an older operating system,

0:34:34.560 --> 0:34:37.000
<v Speaker 1>like I don't know people who are using certain computers

0:34:37.000 --> 0:34:40.440
<v Speaker 1>for certain companies, um, you may not be able to

0:34:40.480 --> 0:34:44.279
<v Speaker 1>see that metadata because the operating system came into being

0:34:44.320 --> 0:34:48.080
<v Speaker 1>and the applications came into being before GPS metadata was

0:34:48.120 --> 0:34:52.160
<v Speaker 1>included with photos popular, right, So you don't have that

0:34:52.320 --> 0:34:55.239
<v Speaker 1>X that I found that out. I went through all

0:34:55.280 --> 0:34:58.040
<v Speaker 1>of the programs I have where I can manipulate photos,

0:34:58.440 --> 0:35:00.279
<v Speaker 1>and I tried to see which ones would let me

0:35:00.360 --> 0:35:03.560
<v Speaker 1>see the meta data that included GPS location, which ones don't.

0:35:04.160 --> 0:35:06.560
<v Speaker 1>I have one program on this computer that lets me

0:35:06.600 --> 0:35:09.840
<v Speaker 1>see meta data. Well, it's definitely, it's definitely becoming more popular.

0:35:10.520 --> 0:35:14.240
<v Speaker 1>Just about every editing software now. It's you know, designed

0:35:14.280 --> 0:35:17.719
<v Speaker 1>for the consumer um and if you're using really high

0:35:17.800 --> 0:35:20.080
<v Speaker 1>end stuff, well they may include it, but it's not

0:35:20.120 --> 0:35:23.160
<v Speaker 1>necessarily something that you know, even things like Windows Picture

0:35:23.239 --> 0:35:26.319
<v Speaker 1>Viewer and in the more recent operating systems you can

0:35:26.360 --> 0:35:28.719
<v Speaker 1>find the meta data there and I Photo for the

0:35:28.760 --> 0:35:31.200
<v Speaker 1>Mac with its know it's got features, right, So yeah,

0:35:31.440 --> 0:35:33.319
<v Speaker 1>so yeah, if you have a newer machine, if you

0:35:33.360 --> 0:35:37.960
<v Speaker 1>have like Windows seven or I believe even Windows Vista, UM,

0:35:38.000 --> 0:35:40.680
<v Speaker 1>you would be able to view this information pretty simply

0:35:40.719 --> 0:35:43.040
<v Speaker 1>just by looking at the properties and looking for that

0:35:43.040 --> 0:35:46.600
<v Speaker 1>that location data might be in longitude and latitude. But

0:35:46.880 --> 0:35:49.000
<v Speaker 1>all you have to do there is copy and paste

0:35:49.000 --> 0:35:52.000
<v Speaker 1>it into a program like just like Google Maps, and

0:35:52.040 --> 0:35:54.879
<v Speaker 1>that'll that'll show you exactly where that location is. Yeah.

0:35:55.280 --> 0:35:57.520
<v Speaker 1>So yeah, I mean it's a really interesting technology. It

0:35:57.560 --> 0:36:00.279
<v Speaker 1>has a lot of legitimate uses, a lot of fun uses. Sure,

0:36:00.480 --> 0:36:03.040
<v Speaker 1>they're just just like any other tool. There are good

0:36:03.040 --> 0:36:04.640
<v Speaker 1>ways to use it and bad ways to use it,

0:36:04.680 --> 0:36:06.560
<v Speaker 1>and you should be aware of both before you just

0:36:06.600 --> 0:36:10.040
<v Speaker 1>go out there and start clicking pictures of everything. Yeah,

0:36:10.360 --> 0:36:13.840
<v Speaker 1>So that was a good discussion, and I apologize for

0:36:13.880 --> 0:36:16.480
<v Speaker 1>getting very philosophical towards the end of it, but I

0:36:16.520 --> 0:36:18.000
<v Speaker 1>just felt that that was one of those things that,

0:36:18.080 --> 0:36:20.359
<v Speaker 1>you know, it's really interesting to me and I wanted

0:36:20.400 --> 0:36:23.439
<v Speaker 1>to dive into it. And again, it's it's like anything else.

0:36:23.440 --> 0:36:27.080
<v Speaker 1>There are good points and bad points to to recording

0:36:27.080 --> 0:36:30.560
<v Speaker 1>that information. Yep, yep, yep. So, if you guys have

0:36:30.600 --> 0:36:33.520
<v Speaker 1>any stories you want to share or any thoughts about

0:36:33.920 --> 0:36:36.640
<v Speaker 1>privacy and the web and what its role is. Do

0:36:36.680 --> 0:36:38.640
<v Speaker 1>you think privacy is a thing of the past. Do

0:36:38.680 --> 0:36:40.120
<v Speaker 1>you think we're actually going to get to a point

0:36:40.160 --> 0:36:45.320
<v Speaker 1>where we will all, either by choice or perhaps by force,

0:36:45.680 --> 0:36:48.719
<v Speaker 1>no longer have privacy? Let's know. You can let's know

0:36:48.840 --> 0:36:52.280
<v Speaker 1>on Twitter and Facebook the handle there is tech Stuff

0:36:52.520 --> 0:36:55.319
<v Speaker 1>hs W, or you can shoot us an email. That

0:36:55.360 --> 0:36:58.400
<v Speaker 1>address is tech stuff at how stuffworks dot com and

0:36:58.480 --> 0:37:02.840
<v Speaker 1>Chris and I will talk to you again soon. For

0:37:02.960 --> 0:37:05.319
<v Speaker 1>more on this and thousands of other topics, visit how

0:37:05.400 --> 0:37:08.040
<v Speaker 1>stuff works dot com. To learn more about the podcast,

0:37:08.239 --> 0:37:10.760
<v Speaker 1>click on the podcast icon in the upper right corner

0:37:10.800 --> 0:37:14.920
<v Speaker 1>of our homepage. The How Stuff Works iPhone app has arrived.

0:37:15.040 --> 0:37:22.319
<v Speaker 1>Download it today on iTunes. Brought to you by the

0:37:22.360 --> 0:37:25.680
<v Speaker 1>reinvented two thousand twelve camera. It's ready, are you