WEBVTT - The Dark Side of Cloud Computing

0:00:00.320 --> 0:00:02.880
<v Speaker 1>Brought to you by the reinvented two thousand twelve camera.

0:00:03.240 --> 0:00:08.800
<v Speaker 1>It's ready. Are you get in touch with technology? With

0:00:08.920 --> 0:00:13.200
<v Speaker 1>tech stuff from how stuff Works dot com. By there,

0:00:13.240 --> 0:00:15.880
<v Speaker 1>Welcome to the podcast. My name is Chris Paul Atam,

0:00:15.880 --> 0:00:18.239
<v Speaker 1>an editor here at how Stuff Works, and today I

0:00:18.320 --> 0:00:22.239
<v Speaker 1>have sitting next to me Jonathan Strickland, one of our writers, yes,

0:00:23.000 --> 0:00:25.960
<v Speaker 1>one of many, yep, yep. And you know he's always

0:00:25.960 --> 0:00:30.160
<v Speaker 1>someone who likes to look for that silver lining cloud. Yeah,

0:00:30.240 --> 0:00:32.440
<v Speaker 1>and this time we're actually looking at the cloud around

0:00:32.479 --> 0:00:36.040
<v Speaker 1>the silver lining. That's kind of funny you would say that. Yeah,

0:00:36.200 --> 0:00:38.680
<v Speaker 1>you know we uh, we've actually done a whole series

0:00:38.720 --> 0:00:43.320
<v Speaker 1>of articles on cloud computing and two podcasts and um,

0:00:43.360 --> 0:00:45.960
<v Speaker 1>that's because it's it's such a hot topic. Um. And

0:00:46.120 --> 0:00:49.160
<v Speaker 1>you know, it's very popular in the news right now

0:00:49.320 --> 0:00:52.960
<v Speaker 1>and something that I imagine many of our listeners were

0:00:53.000 --> 0:00:56.720
<v Speaker 1>probably familiar with even without having check those out. UM.

0:00:56.760 --> 0:00:58.960
<v Speaker 1>But what we're talking about when we say cloud computing,

0:00:58.960 --> 0:01:02.160
<v Speaker 1>for those of you who don't know, UM, is basically

0:01:02.440 --> 0:01:06.399
<v Speaker 1>in a in a very small nutshell, applications and storage

0:01:06.560 --> 0:01:10.280
<v Speaker 1>that is web based, so you you don't save files

0:01:10.280 --> 0:01:13.360
<v Speaker 1>on your hard drive, you don't access applications on your computer. Um,

0:01:13.400 --> 0:01:16.840
<v Speaker 1>they're all stored online so that you don't have to say,

0:01:16.880 --> 0:01:18.640
<v Speaker 1>carry a briefcase with a computer in it on the

0:01:18.640 --> 0:01:21.080
<v Speaker 1>way you know, to and from work, which is kind

0:01:21.080 --> 0:01:23.000
<v Speaker 1>of a neat idea when you think about it, you

0:01:23.040 --> 0:01:24.760
<v Speaker 1>know it's all going to be there no matter what

0:01:24.800 --> 0:01:27.039
<v Speaker 1>computer you're on. It also means that it makes it

0:01:27.120 --> 0:01:30.479
<v Speaker 1>much easier to share your information with with other people,

0:01:30.920 --> 0:01:33.399
<v Speaker 1>so that if you were to save something to a

0:01:33.440 --> 0:01:36.640
<v Speaker 1>network and allow other people access to that network, then

0:01:36.680 --> 0:01:41.120
<v Speaker 1>you can all work from the same foundation article or

0:01:41.240 --> 0:01:45.400
<v Speaker 1>or document. Um. For anyone who's ever done any collaboration,

0:01:46.319 --> 0:01:48.760
<v Speaker 1>it can It can be really frustrating to work with

0:01:48.800 --> 0:01:51.440
<v Speaker 1>computer files because if everyone has a copy of a

0:01:51.440 --> 0:01:55.640
<v Speaker 1>computer file and everyone's making changes to that to their copy,

0:01:55.880 --> 0:01:59.040
<v Speaker 1>getting all those copies back together and and and trying

0:01:59.080 --> 0:02:03.400
<v Speaker 1>to make them coalescent to a new document is very difficult.

0:02:03.840 --> 0:02:07.520
<v Speaker 1>So cloud computing gives you the opportunity to have multiple

0:02:07.520 --> 0:02:10.600
<v Speaker 1>people working on the same file at the same time

0:02:11.080 --> 0:02:16.000
<v Speaker 1>and uh and and avoid all those those superfluous copies. Yeah,

0:02:16.000 --> 0:02:18.280
<v Speaker 1>that's true, you can. It's gotten so sophisticated that you

0:02:18.280 --> 0:02:20.960
<v Speaker 1>can actually merge the documents together even if you are

0:02:21.000 --> 0:02:24.200
<v Speaker 1>working on at the same time, um, which is which

0:02:24.240 --> 0:02:27.360
<v Speaker 1>is a far cry from the way things used to be. Exactly,

0:02:27.800 --> 0:02:32.600
<v Speaker 1>But there is a dark side to cloud computing insert

0:02:32.760 --> 0:02:40.919
<v Speaker 1>thunder noise here. Yeah, um right, Because you're talking about

0:02:40.919 --> 0:02:43.920
<v Speaker 1>sharing files with other people, you know, there is the

0:02:43.960 --> 0:02:46.160
<v Speaker 1>possibility that you might share them with people that you

0:02:46.200 --> 0:02:48.760
<v Speaker 1>don't intend to share them with. Exactly. Yes, So if

0:02:48.800 --> 0:02:52.600
<v Speaker 1>you have all of these important files stored on someone

0:02:52.720 --> 0:02:56.639
<v Speaker 1>else's hardware, there's there's a lot of concern about who

0:02:56.680 --> 0:02:59.679
<v Speaker 1>else might have access to that, whether it's someone who

0:02:59.720 --> 0:03:04.600
<v Speaker 1>has is a motive to access that in a criminal way,

0:03:04.720 --> 0:03:08.200
<v Speaker 1>or if it's just someone who works for the system

0:03:08.280 --> 0:03:11.240
<v Speaker 1>that's storing the information. I mean, it could just be

0:03:11.280 --> 0:03:14.480
<v Speaker 1>as simple as well. Let's let's let's use some examples.

0:03:14.960 --> 0:03:19.000
<v Speaker 1>A very popular cloud computing platform right now, um is

0:03:19.080 --> 0:03:24.400
<v Speaker 1>Amazon Simple Storage Service or S three. So if you're

0:03:24.440 --> 0:03:30.200
<v Speaker 1>storing huge amounts of data on Amazon's servers, you probably

0:03:30.200 --> 0:03:33.360
<v Speaker 1>want to know who has access to that information, like

0:03:33.400 --> 0:03:38.080
<v Speaker 1>what administrators have access to it, and what what links

0:03:38.080 --> 0:03:41.400
<v Speaker 1>did Amazon go to to make sure that those people

0:03:41.440 --> 0:03:45.480
<v Speaker 1>are trustworthy and they're not going to you know, mind

0:03:45.560 --> 0:03:48.000
<v Speaker 1>that information to find stuff that they could sell to

0:03:48.040 --> 0:03:51.360
<v Speaker 1>other competitors or I mean, there's a whole host of

0:03:51.440 --> 0:03:53.800
<v Speaker 1>issues that you have to come to grips with when

0:03:53.800 --> 0:03:57.120
<v Speaker 1>you're talking about cloud computing. Yeah, that's true. And you know,

0:03:57.320 --> 0:03:59.960
<v Speaker 1>of course we're not accusing anybody here that it would.

0:04:00.080 --> 0:04:04.480
<v Speaker 1>It's just a concept, um that you know, something might

0:04:04.520 --> 0:04:07.160
<v Speaker 1>go wrong. I mean, you think about we we talked

0:04:07.160 --> 0:04:11.600
<v Speaker 1>about Google, who hosts a lot of different cloud computing applications,

0:04:11.640 --> 0:04:15.080
<v Speaker 1>including Google Docs, Gmail. Um. One of the things we

0:04:15.120 --> 0:04:19.039
<v Speaker 1>talked about that's really good about about that is that

0:04:19.279 --> 0:04:23.279
<v Speaker 1>Google makes backups, tons of backups of all the data,

0:04:23.320 --> 0:04:27.760
<v Speaker 1>so you shouldn't miss anything. But then again, if your

0:04:28.080 --> 0:04:32.360
<v Speaker 1>document is on say I'm picking a number from the cloud,

0:04:32.839 --> 0:04:36.680
<v Speaker 1>sixteen different computers with different backups, what happens if somebody,

0:04:36.920 --> 0:04:39.479
<v Speaker 1>you know, runs off with one of those machines, you know,

0:04:39.560 --> 0:04:42.200
<v Speaker 1>somebody You're not necessarily somebody from Google. Somebody just gets

0:04:42.240 --> 0:04:44.360
<v Speaker 1>hold of it, right, just gets hold of the physical

0:04:44.400 --> 0:04:46.480
<v Speaker 1>machine and not even the file. Yeah, I mean, there,

0:04:46.560 --> 0:04:48.839
<v Speaker 1>that's that's an issue. Not granted, these are issues that

0:04:48.880 --> 0:04:50.920
<v Speaker 1>you have to worry about, even if you're storing information

0:04:50.920 --> 0:04:53.080
<v Speaker 1>on your own computer. You have to worry about the

0:04:53.080 --> 0:04:56.480
<v Speaker 1>physical security of your own machines. But there's a lot

0:04:56.520 --> 0:05:00.279
<v Speaker 1>more apprehension when it's not under your direct control role.

0:05:00.400 --> 0:05:02.800
<v Speaker 1>It's it's a trust issue. Do you trust the person

0:05:02.880 --> 0:05:05.839
<v Speaker 1>who's providing that service to you, but that company that's

0:05:05.839 --> 0:05:08.719
<v Speaker 1>providing that service to you enough to to say, you

0:05:08.720 --> 0:05:11.320
<v Speaker 1>know what, they're going to go to all the necessary

0:05:11.400 --> 0:05:16.080
<v Speaker 1>links to protect my information. UM. Now, in most cases,

0:05:16.200 --> 0:05:18.840
<v Speaker 1>the answer to that is usually gonna be yes, because

0:05:19.160 --> 0:05:21.360
<v Speaker 1>if the company is not doing that, they're not going

0:05:21.400 --> 0:05:23.880
<v Speaker 1>to be in business very long. All it takes is

0:05:24.040 --> 0:05:27.360
<v Speaker 1>um uh, one screw up and and you're gonna see

0:05:27.360 --> 0:05:29.400
<v Speaker 1>all the clients just jump ship and they're either going

0:05:29.440 --> 0:05:32.200
<v Speaker 1>to go back to the traditional let's store everything on

0:05:32.200 --> 0:05:35.359
<v Speaker 1>our own machines model, or they'll go to a competitor.

0:05:35.640 --> 0:05:38.479
<v Speaker 1>So it's in the company's best interest to make sure

0:05:38.560 --> 0:05:45.560
<v Speaker 1>that security both physical and online are top notch. Absolutely um.

0:05:45.680 --> 0:05:49.279
<v Speaker 1>And there are other issues to uh, you know, you

0:05:49.320 --> 0:05:53.320
<v Speaker 1>could possibly have service outages. Oh yeah, we've had a

0:05:53.320 --> 0:05:55.960
<v Speaker 1>couple of those this summer. Actually. Yeah. In August eleven,

0:05:56.520 --> 0:05:59.760
<v Speaker 1>Google had a Gmail outage that affected a lot of

0:05:59.760 --> 0:06:03.680
<v Speaker 1>people basically North America and India. UM and it was

0:06:04.080 --> 0:06:07.359
<v Speaker 1>out for about two hours, I guess. Yeah. There's some

0:06:07.400 --> 0:06:11.960
<v Speaker 1>people reported having difficulty accessing Gmail for up to a day,

0:06:12.080 --> 0:06:14.360
<v Speaker 1>and there were other issues as well. Some people were

0:06:14.360 --> 0:06:18.560
<v Speaker 1>having problems accessing any Google apps at all. Um. I

0:06:18.600 --> 0:06:22.719
<v Speaker 1>have used Google Docs in the past for non work stuff, UM,

0:06:22.839 --> 0:06:26.080
<v Speaker 1>my own personal files, and there was I thought, hey,

0:06:26.120 --> 0:06:27.680
<v Speaker 1>you know what, I'm gonna do some work on this

0:06:27.760 --> 0:06:31.080
<v Speaker 1>script I'm writing, um and uh, so I tried to

0:06:31.120 --> 0:06:34.400
<v Speaker 1>access it, couldn't get to my Google Docs account at all.

0:06:34.480 --> 0:06:36.520
<v Speaker 1>It just wasn't gonna let me access it, and I

0:06:36.920 --> 0:06:40.039
<v Speaker 1>began to freak out a little bit. Now, my data

0:06:40.160 --> 0:06:43.240
<v Speaker 1>ended up being perfectly safe. There was you know, I

0:06:43.279 --> 0:06:45.440
<v Speaker 1>don't know if they had any crashes on their servers

0:06:45.520 --> 0:06:50.080
<v Speaker 1>or anything, but but it was completely intact um and

0:06:50.160 --> 0:06:52.720
<v Speaker 1>once I was able to access it again and uh

0:06:52.760 --> 0:06:55.520
<v Speaker 1>and really it wasn't an emergency issue for me, So

0:06:55.839 --> 0:06:58.280
<v Speaker 1>I really didn't have any reason to truly freak out.

0:06:58.320 --> 0:07:02.480
<v Speaker 1>But for people who are using goaldocs for uh mission

0:07:02.480 --> 0:07:06.920
<v Speaker 1>critical type applications, I'm sure that was a huge problem. Yeah,

0:07:07.000 --> 0:07:09.960
<v Speaker 1>like the going back to college and the computer lab

0:07:10.000 --> 0:07:12.360
<v Speaker 1>with everybody working on their term papers the night before

0:07:12.360 --> 0:07:14.360
<v Speaker 1>they're due, and the power goes out in the computer

0:07:14.400 --> 0:07:16.320
<v Speaker 1>lab and I have have you ever been in that

0:07:16.400 --> 0:07:19.520
<v Speaker 1>situation I had in the lab when it happened, I

0:07:19.560 --> 0:07:22.400
<v Speaker 1>actually finished before the and I and I used to

0:07:22.440 --> 0:07:25.840
<v Speaker 1>work in a company where where you, uh, we had

0:07:25.920 --> 0:07:28.960
<v Speaker 1>some power issues because the power company was putting in

0:07:29.040 --> 0:07:32.600
<v Speaker 1>new lines to the to the neighborhood that the company

0:07:32.640 --> 0:07:36.120
<v Speaker 1>was in. And yeah, to hear the groans and moans

0:07:36.120 --> 0:07:39.040
<v Speaker 1>and shrieks of people as the power flickered off for

0:07:39.120 --> 0:07:42.560
<v Speaker 1>the fifth time that day, and then to hear someone

0:07:42.880 --> 0:07:46.240
<v Speaker 1>pipe up, and often it was yours truly saying I

0:07:46.280 --> 0:07:50.120
<v Speaker 1>hope you just saved uh your data. Um, yeah, that

0:07:50.240 --> 0:07:52.360
<v Speaker 1>was that was a common occurrence. And that can happen

0:07:52.400 --> 0:07:54.480
<v Speaker 1>on the web. I mean, that's that's what we're talking

0:07:54.520 --> 0:07:57.000
<v Speaker 1>about here. That stuff can happen on on cloud computing.

0:07:57.040 --> 0:07:59.920
<v Speaker 1>Even if it doesn't hit the servers they're storing the information,

0:08:00.000 --> 0:08:02.200
<v Speaker 1>it might hit the traffic servers that are directing all

0:08:02.240 --> 0:08:07.200
<v Speaker 1>the traffic to and from those the storage devices. So

0:08:07.880 --> 0:08:10.000
<v Speaker 1>but there are other issues to worry about. Two Um

0:08:10.680 --> 0:08:14.400
<v Speaker 1>I was gonna mention. Another one is the location of

0:08:14.440 --> 0:08:18.320
<v Speaker 1>the servers where the servers are stored. Um. Not every

0:08:18.360 --> 0:08:23.240
<v Speaker 1>country has the same laws and regulations about data security

0:08:23.280 --> 0:08:26.560
<v Speaker 1>that the United States has so and because the cloud

0:08:26.760 --> 0:08:30.120
<v Speaker 1>isn't geographically oriented, I mean you could you could have

0:08:30.160 --> 0:08:32.839
<v Speaker 1>a cloud cloud network with servers that are in the

0:08:32.920 --> 0:08:36.800
<v Speaker 1>United States and servers in Venezuela and servers in Nantarcticle

0:08:36.840 --> 0:08:40.760
<v Speaker 1>if you really wanted to. Uh cool, be quite cool. Actually,

0:08:40.840 --> 0:08:43.880
<v Speaker 1>I bet they wouldn't have any problems with overheating. But anyway,

0:08:44.200 --> 0:08:46.920
<v Speaker 1>the important thing here is that the laws and regulations

0:08:47.080 --> 0:08:50.440
<v Speaker 1>might be different in the country that that actually houses

0:08:50.520 --> 0:08:54.920
<v Speaker 1>the physical machines your data lives on. That might be

0:08:55.000 --> 0:08:58.319
<v Speaker 1>something worth looking into. I mean, it could really compromise

0:08:58.360 --> 0:09:02.520
<v Speaker 1>the security of your data. That's true. That's true. Um.

0:09:02.600 --> 0:09:05.720
<v Speaker 1>And then there's another issue, which is sort of a

0:09:05.840 --> 0:09:08.040
<v Speaker 1>less pleasant issue in a way to to talk about,

0:09:08.080 --> 0:09:12.280
<v Speaker 1>and that's the end user license agreement. Oh, I'm so

0:09:12.320 --> 0:09:14.280
<v Speaker 1>glad you mentioned that. I totally forgot to write that

0:09:14.280 --> 0:09:18.199
<v Speaker 1>down in my notes. Well, um, it's this came to

0:09:18.320 --> 0:09:20.280
<v Speaker 1>light and uh, Google is going to send us a

0:09:20.320 --> 0:09:24.040
<v Speaker 1>nasty letter for picking on him today. But um, they

0:09:24.120 --> 0:09:27.360
<v Speaker 1>just released a new web browser right about the time

0:09:27.400 --> 0:09:29.240
<v Speaker 1>we record this, a few days before we recorded this,

0:09:29.760 --> 0:09:32.520
<v Speaker 1>um called Google Chrome, and that that's not really what

0:09:32.559 --> 0:09:34.800
<v Speaker 1>we're talking about here, But what it brought to light

0:09:35.000 --> 0:09:38.920
<v Speaker 1>was it pointed out again that Google and its end

0:09:39.000 --> 0:09:42.560
<v Speaker 1>User License Agreement or ULA for several of its products,

0:09:42.600 --> 0:09:48.520
<v Speaker 1>including Google Docs UM has information that is a little

0:09:49.440 --> 0:09:55.320
<v Speaker 1>interesting to UH to consider that they might actually own

0:09:55.440 --> 0:09:58.600
<v Speaker 1>the rights here information right. Well, they we should also

0:09:59.240 --> 0:10:02.400
<v Speaker 1>jump to mention and that they have addressed this, that

0:10:02.600 --> 0:10:05.720
<v Speaker 1>that's true, they have revised the ULA. But what what

0:10:05.840 --> 0:10:07.640
<v Speaker 1>Chris is talking about here is that there was a

0:10:07.760 --> 0:10:11.880
<v Speaker 1>clause in the ULA that essentially said anything that transmitted

0:10:11.920 --> 0:10:17.320
<v Speaker 1>across through using Google Chrome was Google had rights to

0:10:17.360 --> 0:10:20.280
<v Speaker 1>redistribute in just about any way they wanted to. And

0:10:20.320 --> 0:10:23.480
<v Speaker 1>the lawyers for Google UH explained that what they meant

0:10:23.480 --> 0:10:26.040
<v Speaker 1>by that was they had the right to display that,

0:10:26.520 --> 0:10:29.000
<v Speaker 1>to take your information from you, and if you were

0:10:29.040 --> 0:10:31.840
<v Speaker 1>collaborating with someone else, to display it on their computer

0:10:31.880 --> 0:10:34.400
<v Speaker 1>screen and let them make changes to it. So you

0:10:34.440 --> 0:10:36.440
<v Speaker 1>own the rights to this. And as one of their

0:10:36.480 --> 0:10:39.960
<v Speaker 1>representatives said, and I'm paraphrasing, basically, if you you know,

0:10:40.440 --> 0:10:44.000
<v Speaker 1>if you have your fantasy football stats on, nobody wants

0:10:44.000 --> 0:10:46.199
<v Speaker 1>to see that but you that's your information. We don't

0:10:46.320 --> 0:10:49.720
<v Speaker 1>you know, we don't own that. We don't own the content,

0:10:49.840 --> 0:10:52.080
<v Speaker 1>but we we reserve the right to be able to

0:10:52.120 --> 0:10:54.720
<v Speaker 1>display that if you want it displayed exactly that that

0:10:54.880 --> 0:10:57.720
<v Speaker 1>is part of the Google docs la. I mean, it's

0:10:57.760 --> 0:10:59.959
<v Speaker 1>it's and it just happened that they poured it over

0:11:00.120 --> 0:11:02.559
<v Speaker 1>to Google Chrome and then it's got a lot of

0:11:02.600 --> 0:11:05.360
<v Speaker 1>attention people read and then they interpret it to mean

0:11:05.440 --> 0:11:08.880
<v Speaker 1>that that anything I do on Google Chrome is going

0:11:08.920 --> 0:11:11.920
<v Speaker 1>to be Google's property forever and ever. Like I guess

0:11:11.920 --> 0:11:14.400
<v Speaker 1>it is a lot easier to index the world's information

0:11:14.440 --> 0:11:16.760
<v Speaker 1>if you own it all, well, that would be that

0:11:16.760 --> 0:11:19.640
<v Speaker 1>would make it a lot easier, yes, but that that's

0:11:19.760 --> 0:11:22.000
<v Speaker 1>you know, Google has has owned up to that. They've said,

0:11:22.120 --> 0:11:24.360
<v Speaker 1>you know, this is not what we meant. Let's clarify this,

0:11:24.440 --> 0:11:27.240
<v Speaker 1>and they they're taking the initiative to you know, go

0:11:27.280 --> 0:11:30.120
<v Speaker 1>ahead and restructure that for for their customers, which is

0:11:30.200 --> 0:11:32.280
<v Speaker 1>which is a good thing. But you should you know,

0:11:32.320 --> 0:11:34.120
<v Speaker 1>anytime you sign up for a service, and there are

0:11:34.160 --> 0:11:37.280
<v Speaker 1>lots of new services every day, believe me, because we

0:11:37.360 --> 0:11:39.400
<v Speaker 1>do a lot of checking into these and I sign

0:11:39.520 --> 0:11:40.840
<v Speaker 1>up for a lot of them just to see what

0:11:40.840 --> 0:11:43.200
<v Speaker 1>they're like. But you know, each one of them, when

0:11:43.240 --> 0:11:46.440
<v Speaker 1>you sign up, they give you the terms and conditions

0:11:46.600 --> 0:11:49.800
<v Speaker 1>of the service. And you know, it's a long legal document.

0:11:49.800 --> 0:11:51.760
<v Speaker 1>A lot of people don't read. Do they just click

0:11:51.840 --> 0:11:55.360
<v Speaker 1>I agree and sign up. So are you signing away

0:11:55.400 --> 0:11:59.480
<v Speaker 1>the rights to your spreadsheets or your uh you know,

0:11:59.559 --> 0:12:04.400
<v Speaker 1>screen a or whatever else your power point presentations? Uh?

0:12:04.520 --> 0:12:07.320
<v Speaker 1>You know by doing that? Yeah, you know you have

0:12:07.360 --> 0:12:09.320
<v Speaker 1>to check these things out otherwise, you know, all this

0:12:09.440 --> 0:12:12.240
<v Speaker 1>information that you store away might end up on somebody

0:12:12.280 --> 0:12:14.560
<v Speaker 1>else's computer. Yeah. That that kind of goes back to

0:12:14.559 --> 0:12:16.960
<v Speaker 1>to the first point we were making about, you know,

0:12:17.200 --> 0:12:21.240
<v Speaker 1>make sure you know who has access to your information. Um.

0:12:21.440 --> 0:12:26.360
<v Speaker 1>So these are all important issues. They're not they're not trivial. Uh.

0:12:26.840 --> 0:12:29.400
<v Speaker 1>But at the same time, do keep in mind that,

0:12:29.679 --> 0:12:31.640
<v Speaker 1>like we said before, it is in the company's best

0:12:31.679 --> 0:12:36.480
<v Speaker 1>interests to to make sure that your data remains safe

0:12:36.480 --> 0:12:39.800
<v Speaker 1>and secure. Otherwise they don't have a business model. So

0:12:41.240 --> 0:12:45.080
<v Speaker 1>hopefully we'll be able to say that this dark side

0:12:45.320 --> 0:12:48.120
<v Speaker 1>is more something that everyone's already thinking about and and

0:12:48.200 --> 0:12:53.160
<v Speaker 1>trying to address, and not a fundamental flaw in in

0:12:53.280 --> 0:12:57.120
<v Speaker 1>that in that model, because you know, you know, I

0:12:57.760 --> 0:13:00.120
<v Speaker 1>don't think I don't think anything's going to stop the

0:13:00.920 --> 0:13:05.200
<v Speaker 1>incable progress of cloud computing. It's got a lot of it.

0:13:05.200 --> 0:13:08.280
<v Speaker 1>It does have a lot of advantages over over storing

0:13:08.360 --> 0:13:11.400
<v Speaker 1>information on your own computer because honestly, a lot of

0:13:11.400 --> 0:13:14.319
<v Speaker 1>these places offer gigabytes and gigabytes of storage and it's

0:13:14.360 --> 0:13:17.960
<v Speaker 1>only going up. I mean, as as storage capacity increases

0:13:17.960 --> 0:13:20.200
<v Speaker 1>in the cost of it decreases, you're going to see

0:13:20.240 --> 0:13:24.280
<v Speaker 1>cloud computing services offering to give you, you know, tons

0:13:24.320 --> 0:13:26.680
<v Speaker 1>more space than you could ever have on your own

0:13:26.760 --> 0:13:28.920
<v Speaker 1>personal hard drive, which you could use for you know,

0:13:29.040 --> 0:13:31.240
<v Speaker 1>games and stuff like that if you don't want to

0:13:31.360 --> 0:13:34.760
<v Speaker 1>store a lease documents. So um, you know. I don't

0:13:34.760 --> 0:13:37.520
<v Speaker 1>think that there's any reason to uh to give up

0:13:37.600 --> 0:13:40.040
<v Speaker 1>on cloud computing based on these things, but there are

0:13:40.040 --> 0:13:41.599
<v Speaker 1>things to consider when you do sign up for a

0:13:41.640 --> 0:13:46.000
<v Speaker 1>service exactly. For more on this and thousands of other topics,

0:13:46.120 --> 0:13:49.120
<v Speaker 1>does it how stuff works dot Com? Let us know

0:13:49.160 --> 0:13:52.079
<v Speaker 1>what you think. Send an email to podcast at how

0:13:52.120 --> 0:13:58.400
<v Speaker 1>stuff works dot com. Brought to you by the reinvented

0:13:58.440 --> 0:14:01.080
<v Speaker 1>two thousand twelve camera. It's ready, are you