1 00:00:00,320 --> 00:00:02,880 Speaker 1: Brought to you by the reinvented two thousand twelve camera. 2 00:00:03,240 --> 00:00:08,800 Speaker 1: It's ready. Are you get in touch with technology? With 3 00:00:08,920 --> 00:00:13,200 Speaker 1: tech stuff from how stuff Works dot com. By there, 4 00:00:13,240 --> 00:00:15,880 Speaker 1: Welcome to the podcast. My name is Chris Paul Atam, 5 00:00:15,880 --> 00:00:18,239 Speaker 1: an editor here at how Stuff Works, and today I 6 00:00:18,320 --> 00:00:22,239 Speaker 1: have sitting next to me Jonathan Strickland, one of our writers, yes, 7 00:00:23,000 --> 00:00:25,960 Speaker 1: one of many, yep, yep. And you know he's always 8 00:00:25,960 --> 00:00:30,160 Speaker 1: someone who likes to look for that silver lining cloud. Yeah, 9 00:00:30,240 --> 00:00:32,440 Speaker 1: and this time we're actually looking at the cloud around 10 00:00:32,479 --> 00:00:36,040 Speaker 1: the silver lining. That's kind of funny you would say that. Yeah, 11 00:00:36,200 --> 00:00:38,680 Speaker 1: you know we uh, we've actually done a whole series 12 00:00:38,720 --> 00:00:43,320 Speaker 1: of articles on cloud computing and two podcasts and um, 13 00:00:43,360 --> 00:00:45,960 Speaker 1: that's because it's it's such a hot topic. Um. And 14 00:00:46,120 --> 00:00:49,160 Speaker 1: you know, it's very popular in the news right now 15 00:00:49,320 --> 00:00:52,960 Speaker 1: and something that I imagine many of our listeners were 16 00:00:53,000 --> 00:00:56,720 Speaker 1: probably familiar with even without having check those out. UM. 17 00:00:56,760 --> 00:00:58,960 Speaker 1: But what we're talking about when we say cloud computing, 18 00:00:58,960 --> 00:01:02,160 Speaker 1: for those of you who don't know, UM, is basically 19 00:01:02,440 --> 00:01:06,399 Speaker 1: in a in a very small nutshell, applications and storage 20 00:01:06,560 --> 00:01:10,280 Speaker 1: that is web based, so you you don't save files 21 00:01:10,280 --> 00:01:13,360 Speaker 1: on your hard drive, you don't access applications on your computer. Um, 22 00:01:13,400 --> 00:01:16,840 Speaker 1: they're all stored online so that you don't have to say, 23 00:01:16,880 --> 00:01:18,640 Speaker 1: carry a briefcase with a computer in it on the 24 00:01:18,640 --> 00:01:21,080 Speaker 1: way you know, to and from work, which is kind 25 00:01:21,080 --> 00:01:23,000 Speaker 1: of a neat idea when you think about it, you 26 00:01:23,040 --> 00:01:24,760 Speaker 1: know it's all going to be there no matter what 27 00:01:24,800 --> 00:01:27,039 Speaker 1: computer you're on. It also means that it makes it 28 00:01:27,120 --> 00:01:30,479 Speaker 1: much easier to share your information with with other people, 29 00:01:30,920 --> 00:01:33,399 Speaker 1: so that if you were to save something to a 30 00:01:33,440 --> 00:01:36,640 Speaker 1: network and allow other people access to that network, then 31 00:01:36,680 --> 00:01:41,120 Speaker 1: you can all work from the same foundation article or 32 00:01:41,240 --> 00:01:45,400 Speaker 1: or document. Um. For anyone who's ever done any collaboration, 33 00:01:46,319 --> 00:01:48,760 Speaker 1: it can It can be really frustrating to work with 34 00:01:48,800 --> 00:01:51,440 Speaker 1: computer files because if everyone has a copy of a 35 00:01:51,440 --> 00:01:55,640 Speaker 1: computer file and everyone's making changes to that to their copy, 36 00:01:55,880 --> 00:01:59,040 Speaker 1: getting all those copies back together and and and trying 37 00:01:59,080 --> 00:02:03,400 Speaker 1: to make them coalescent to a new document is very difficult. 38 00:02:03,840 --> 00:02:07,520 Speaker 1: So cloud computing gives you the opportunity to have multiple 39 00:02:07,520 --> 00:02:10,600 Speaker 1: people working on the same file at the same time 40 00:02:11,080 --> 00:02:16,000 Speaker 1: and uh and and avoid all those those superfluous copies. Yeah, 41 00:02:16,000 --> 00:02:18,280 Speaker 1: that's true, you can. It's gotten so sophisticated that you 42 00:02:18,280 --> 00:02:20,960 Speaker 1: can actually merge the documents together even if you are 43 00:02:21,000 --> 00:02:24,200 Speaker 1: working on at the same time, um, which is which 44 00:02:24,240 --> 00:02:27,360 Speaker 1: is a far cry from the way things used to be. Exactly, 45 00:02:27,800 --> 00:02:32,600 Speaker 1: But there is a dark side to cloud computing insert 46 00:02:32,760 --> 00:02:40,919 Speaker 1: thunder noise here. Yeah, um right, Because you're talking about 47 00:02:40,919 --> 00:02:43,920 Speaker 1: sharing files with other people, you know, there is the 48 00:02:43,960 --> 00:02:46,160 Speaker 1: possibility that you might share them with people that you 49 00:02:46,200 --> 00:02:48,760 Speaker 1: don't intend to share them with. Exactly. Yes, So if 50 00:02:48,800 --> 00:02:52,600 Speaker 1: you have all of these important files stored on someone 51 00:02:52,720 --> 00:02:56,639 Speaker 1: else's hardware, there's there's a lot of concern about who 52 00:02:56,680 --> 00:02:59,679 Speaker 1: else might have access to that, whether it's someone who 53 00:02:59,720 --> 00:03:04,600 Speaker 1: has is a motive to access that in a criminal way, 54 00:03:04,720 --> 00:03:08,200 Speaker 1: or if it's just someone who works for the system 55 00:03:08,280 --> 00:03:11,240 Speaker 1: that's storing the information. I mean, it could just be 56 00:03:11,280 --> 00:03:14,480 Speaker 1: as simple as well. Let's let's let's use some examples. 57 00:03:14,960 --> 00:03:19,000 Speaker 1: A very popular cloud computing platform right now, um is 58 00:03:19,080 --> 00:03:24,400 Speaker 1: Amazon Simple Storage Service or S three. So if you're 59 00:03:24,440 --> 00:03:30,200 Speaker 1: storing huge amounts of data on Amazon's servers, you probably 60 00:03:30,200 --> 00:03:33,360 Speaker 1: want to know who has access to that information, like 61 00:03:33,400 --> 00:03:38,080 Speaker 1: what administrators have access to it, and what what links 62 00:03:38,080 --> 00:03:41,400 Speaker 1: did Amazon go to to make sure that those people 63 00:03:41,440 --> 00:03:45,480 Speaker 1: are trustworthy and they're not going to you know, mind 64 00:03:45,560 --> 00:03:48,000 Speaker 1: that information to find stuff that they could sell to 65 00:03:48,040 --> 00:03:51,360 Speaker 1: other competitors or I mean, there's a whole host of 66 00:03:51,440 --> 00:03:53,800 Speaker 1: issues that you have to come to grips with when 67 00:03:53,800 --> 00:03:57,120 Speaker 1: you're talking about cloud computing. Yeah, that's true. And you know, 68 00:03:57,320 --> 00:03:59,960 Speaker 1: of course we're not accusing anybody here that it would. 69 00:04:00,080 --> 00:04:04,480 Speaker 1: It's just a concept, um that you know, something might 70 00:04:04,520 --> 00:04:07,160 Speaker 1: go wrong. I mean, you think about we we talked 71 00:04:07,160 --> 00:04:11,600 Speaker 1: about Google, who hosts a lot of different cloud computing applications, 72 00:04:11,640 --> 00:04:15,080 Speaker 1: including Google Docs, Gmail. Um. One of the things we 73 00:04:15,120 --> 00:04:19,039 Speaker 1: talked about that's really good about about that is that 74 00:04:19,279 --> 00:04:23,279 Speaker 1: Google makes backups, tons of backups of all the data, 75 00:04:23,320 --> 00:04:27,760 Speaker 1: so you shouldn't miss anything. But then again, if your 76 00:04:28,080 --> 00:04:32,360 Speaker 1: document is on say I'm picking a number from the cloud, 77 00:04:32,839 --> 00:04:36,680 Speaker 1: sixteen different computers with different backups, what happens if somebody, 78 00:04:36,920 --> 00:04:39,479 Speaker 1: you know, runs off with one of those machines, you know, 79 00:04:39,560 --> 00:04:42,200 Speaker 1: somebody You're not necessarily somebody from Google. Somebody just gets 80 00:04:42,240 --> 00:04:44,360 Speaker 1: hold of it, right, just gets hold of the physical 81 00:04:44,400 --> 00:04:46,480 Speaker 1: machine and not even the file. Yeah, I mean, there, 82 00:04:46,560 --> 00:04:48,839 Speaker 1: that's that's an issue. Not granted, these are issues that 83 00:04:48,880 --> 00:04:50,920 Speaker 1: you have to worry about, even if you're storing information 84 00:04:50,920 --> 00:04:53,080 Speaker 1: on your own computer. You have to worry about the 85 00:04:53,080 --> 00:04:56,480 Speaker 1: physical security of your own machines. But there's a lot 86 00:04:56,520 --> 00:05:00,279 Speaker 1: more apprehension when it's not under your direct control role. 87 00:05:00,400 --> 00:05:02,800 Speaker 1: It's it's a trust issue. Do you trust the person 88 00:05:02,880 --> 00:05:05,839 Speaker 1: who's providing that service to you, but that company that's 89 00:05:05,839 --> 00:05:08,719 Speaker 1: providing that service to you enough to to say, you 90 00:05:08,720 --> 00:05:11,320 Speaker 1: know what, they're going to go to all the necessary 91 00:05:11,400 --> 00:05:16,080 Speaker 1: links to protect my information. UM. Now, in most cases, 92 00:05:16,200 --> 00:05:18,840 Speaker 1: the answer to that is usually gonna be yes, because 93 00:05:19,160 --> 00:05:21,360 Speaker 1: if the company is not doing that, they're not going 94 00:05:21,400 --> 00:05:23,880 Speaker 1: to be in business very long. All it takes is 95 00:05:24,040 --> 00:05:27,360 Speaker 1: um uh, one screw up and and you're gonna see 96 00:05:27,360 --> 00:05:29,400 Speaker 1: all the clients just jump ship and they're either going 97 00:05:29,440 --> 00:05:32,200 Speaker 1: to go back to the traditional let's store everything on 98 00:05:32,200 --> 00:05:35,359 Speaker 1: our own machines model, or they'll go to a competitor. 99 00:05:35,640 --> 00:05:38,479 Speaker 1: So it's in the company's best interest to make sure 100 00:05:38,560 --> 00:05:45,560 Speaker 1: that security both physical and online are top notch. Absolutely um. 101 00:05:45,680 --> 00:05:49,279 Speaker 1: And there are other issues to uh, you know, you 102 00:05:49,320 --> 00:05:53,320 Speaker 1: could possibly have service outages. Oh yeah, we've had a 103 00:05:53,320 --> 00:05:55,960 Speaker 1: couple of those this summer. Actually. Yeah. In August eleven, 104 00:05:56,520 --> 00:05:59,760 Speaker 1: Google had a Gmail outage that affected a lot of 105 00:05:59,760 --> 00:06:03,680 Speaker 1: people basically North America and India. UM and it was 106 00:06:04,080 --> 00:06:07,359 Speaker 1: out for about two hours, I guess. Yeah. There's some 107 00:06:07,400 --> 00:06:11,960 Speaker 1: people reported having difficulty accessing Gmail for up to a day, 108 00:06:12,080 --> 00:06:14,360 Speaker 1: and there were other issues as well. Some people were 109 00:06:14,360 --> 00:06:18,560 Speaker 1: having problems accessing any Google apps at all. Um. I 110 00:06:18,600 --> 00:06:22,719 Speaker 1: have used Google Docs in the past for non work stuff, UM, 111 00:06:22,839 --> 00:06:26,080 Speaker 1: my own personal files, and there was I thought, hey, 112 00:06:26,120 --> 00:06:27,680 Speaker 1: you know what, I'm gonna do some work on this 113 00:06:27,760 --> 00:06:31,080 Speaker 1: script I'm writing, um and uh, so I tried to 114 00:06:31,120 --> 00:06:34,400 Speaker 1: access it, couldn't get to my Google Docs account at all. 115 00:06:34,480 --> 00:06:36,520 Speaker 1: It just wasn't gonna let me access it, and I 116 00:06:36,920 --> 00:06:40,039 Speaker 1: began to freak out a little bit. Now, my data 117 00:06:40,160 --> 00:06:43,240 Speaker 1: ended up being perfectly safe. There was you know, I 118 00:06:43,279 --> 00:06:45,440 Speaker 1: don't know if they had any crashes on their servers 119 00:06:45,520 --> 00:06:50,080 Speaker 1: or anything, but but it was completely intact um and 120 00:06:50,160 --> 00:06:52,720 Speaker 1: once I was able to access it again and uh 121 00:06:52,760 --> 00:06:55,520 Speaker 1: and really it wasn't an emergency issue for me, So 122 00:06:55,839 --> 00:06:58,280 Speaker 1: I really didn't have any reason to truly freak out. 123 00:06:58,320 --> 00:07:02,480 Speaker 1: But for people who are using goaldocs for uh mission 124 00:07:02,480 --> 00:07:06,920 Speaker 1: critical type applications, I'm sure that was a huge problem. Yeah, 125 00:07:07,000 --> 00:07:09,960 Speaker 1: like the going back to college and the computer lab 126 00:07:10,000 --> 00:07:12,360 Speaker 1: with everybody working on their term papers the night before 127 00:07:12,360 --> 00:07:14,360 Speaker 1: they're due, and the power goes out in the computer 128 00:07:14,400 --> 00:07:16,320 Speaker 1: lab and I have have you ever been in that 129 00:07:16,400 --> 00:07:19,520 Speaker 1: situation I had in the lab when it happened, I 130 00:07:19,560 --> 00:07:22,400 Speaker 1: actually finished before the and I and I used to 131 00:07:22,440 --> 00:07:25,840 Speaker 1: work in a company where where you, uh, we had 132 00:07:25,920 --> 00:07:28,960 Speaker 1: some power issues because the power company was putting in 133 00:07:29,040 --> 00:07:32,600 Speaker 1: new lines to the to the neighborhood that the company 134 00:07:32,640 --> 00:07:36,120 Speaker 1: was in. And yeah, to hear the groans and moans 135 00:07:36,120 --> 00:07:39,040 Speaker 1: and shrieks of people as the power flickered off for 136 00:07:39,120 --> 00:07:42,560 Speaker 1: the fifth time that day, and then to hear someone 137 00:07:42,880 --> 00:07:46,240 Speaker 1: pipe up, and often it was yours truly saying I 138 00:07:46,280 --> 00:07:50,120 Speaker 1: hope you just saved uh your data. Um, yeah, that 139 00:07:50,240 --> 00:07:52,360 Speaker 1: was that was a common occurrence. And that can happen 140 00:07:52,400 --> 00:07:54,480 Speaker 1: on the web. I mean, that's that's what we're talking 141 00:07:54,520 --> 00:07:57,000 Speaker 1: about here. That stuff can happen on on cloud computing. 142 00:07:57,040 --> 00:07:59,920 Speaker 1: Even if it doesn't hit the servers they're storing the information, 143 00:08:00,000 --> 00:08:02,200 Speaker 1: it might hit the traffic servers that are directing all 144 00:08:02,240 --> 00:08:07,200 Speaker 1: the traffic to and from those the storage devices. So 145 00:08:07,880 --> 00:08:10,000 Speaker 1: but there are other issues to worry about. Two Um 146 00:08:10,680 --> 00:08:14,400 Speaker 1: I was gonna mention. Another one is the location of 147 00:08:14,440 --> 00:08:18,320 Speaker 1: the servers where the servers are stored. Um. Not every 148 00:08:18,360 --> 00:08:23,240 Speaker 1: country has the same laws and regulations about data security 149 00:08:23,280 --> 00:08:26,560 Speaker 1: that the United States has so and because the cloud 150 00:08:26,760 --> 00:08:30,120 Speaker 1: isn't geographically oriented, I mean you could you could have 151 00:08:30,160 --> 00:08:32,839 Speaker 1: a cloud cloud network with servers that are in the 152 00:08:32,920 --> 00:08:36,800 Speaker 1: United States and servers in Venezuela and servers in Nantarcticle 153 00:08:36,840 --> 00:08:40,760 Speaker 1: if you really wanted to. Uh cool, be quite cool. Actually, 154 00:08:40,840 --> 00:08:43,880 Speaker 1: I bet they wouldn't have any problems with overheating. But anyway, 155 00:08:44,200 --> 00:08:46,920 Speaker 1: the important thing here is that the laws and regulations 156 00:08:47,080 --> 00:08:50,440 Speaker 1: might be different in the country that that actually houses 157 00:08:50,520 --> 00:08:54,920 Speaker 1: the physical machines your data lives on. That might be 158 00:08:55,000 --> 00:08:58,319 Speaker 1: something worth looking into. I mean, it could really compromise 159 00:08:58,360 --> 00:09:02,520 Speaker 1: the security of your data. That's true. That's true. Um. 160 00:09:02,600 --> 00:09:05,720 Speaker 1: And then there's another issue, which is sort of a 161 00:09:05,840 --> 00:09:08,040 Speaker 1: less pleasant issue in a way to to talk about, 162 00:09:08,080 --> 00:09:12,280 Speaker 1: and that's the end user license agreement. Oh, I'm so 163 00:09:12,320 --> 00:09:14,280 Speaker 1: glad you mentioned that. I totally forgot to write that 164 00:09:14,280 --> 00:09:18,199 Speaker 1: down in my notes. Well, um, it's this came to 165 00:09:18,320 --> 00:09:20,280 Speaker 1: light and uh, Google is going to send us a 166 00:09:20,320 --> 00:09:24,040 Speaker 1: nasty letter for picking on him today. But um, they 167 00:09:24,120 --> 00:09:27,360 Speaker 1: just released a new web browser right about the time 168 00:09:27,400 --> 00:09:29,240 Speaker 1: we record this, a few days before we recorded this, 169 00:09:29,760 --> 00:09:32,520 Speaker 1: um called Google Chrome, and that that's not really what 170 00:09:32,559 --> 00:09:34,800 Speaker 1: we're talking about here, But what it brought to light 171 00:09:35,000 --> 00:09:38,920 Speaker 1: was it pointed out again that Google and its end 172 00:09:39,000 --> 00:09:42,560 Speaker 1: User License Agreement or ULA for several of its products, 173 00:09:42,600 --> 00:09:48,520 Speaker 1: including Google Docs UM has information that is a little 174 00:09:49,440 --> 00:09:55,320 Speaker 1: interesting to UH to consider that they might actually own 175 00:09:55,440 --> 00:09:58,600 Speaker 1: the rights here information right. Well, they we should also 176 00:09:59,240 --> 00:10:02,400 Speaker 1: jump to mention and that they have addressed this, that 177 00:10:02,600 --> 00:10:05,720 Speaker 1: that's true, they have revised the ULA. But what what 178 00:10:05,840 --> 00:10:07,640 Speaker 1: Chris is talking about here is that there was a 179 00:10:07,760 --> 00:10:11,880 Speaker 1: clause in the ULA that essentially said anything that transmitted 180 00:10:11,920 --> 00:10:17,320 Speaker 1: across through using Google Chrome was Google had rights to 181 00:10:17,360 --> 00:10:20,280 Speaker 1: redistribute in just about any way they wanted to. And 182 00:10:20,320 --> 00:10:23,480 Speaker 1: the lawyers for Google UH explained that what they meant 183 00:10:23,480 --> 00:10:26,040 Speaker 1: by that was they had the right to display that, 184 00:10:26,520 --> 00:10:29,000 Speaker 1: to take your information from you, and if you were 185 00:10:29,040 --> 00:10:31,840 Speaker 1: collaborating with someone else, to display it on their computer 186 00:10:31,880 --> 00:10:34,400 Speaker 1: screen and let them make changes to it. So you 187 00:10:34,440 --> 00:10:36,440 Speaker 1: own the rights to this. And as one of their 188 00:10:36,480 --> 00:10:39,960 Speaker 1: representatives said, and I'm paraphrasing, basically, if you you know, 189 00:10:40,440 --> 00:10:44,000 Speaker 1: if you have your fantasy football stats on, nobody wants 190 00:10:44,000 --> 00:10:46,199 Speaker 1: to see that but you that's your information. We don't 191 00:10:46,320 --> 00:10:49,720 Speaker 1: you know, we don't own that. We don't own the content, 192 00:10:49,840 --> 00:10:52,080 Speaker 1: but we we reserve the right to be able to 193 00:10:52,120 --> 00:10:54,720 Speaker 1: display that if you want it displayed exactly that that 194 00:10:54,880 --> 00:10:57,720 Speaker 1: is part of the Google docs la. I mean, it's 195 00:10:57,760 --> 00:10:59,959 Speaker 1: it's and it just happened that they poured it over 196 00:11:00,120 --> 00:11:02,559 Speaker 1: to Google Chrome and then it's got a lot of 197 00:11:02,600 --> 00:11:05,360 Speaker 1: attention people read and then they interpret it to mean 198 00:11:05,440 --> 00:11:08,880 Speaker 1: that that anything I do on Google Chrome is going 199 00:11:08,920 --> 00:11:11,920 Speaker 1: to be Google's property forever and ever. Like I guess 200 00:11:11,920 --> 00:11:14,400 Speaker 1: it is a lot easier to index the world's information 201 00:11:14,440 --> 00:11:16,760 Speaker 1: if you own it all, well, that would be that 202 00:11:16,760 --> 00:11:19,640 Speaker 1: would make it a lot easier, yes, but that that's 203 00:11:19,760 --> 00:11:22,000 Speaker 1: you know, Google has has owned up to that. They've said, 204 00:11:22,120 --> 00:11:24,360 Speaker 1: you know, this is not what we meant. Let's clarify this, 205 00:11:24,440 --> 00:11:27,240 Speaker 1: and they they're taking the initiative to you know, go 206 00:11:27,280 --> 00:11:30,120 Speaker 1: ahead and restructure that for for their customers, which is 207 00:11:30,200 --> 00:11:32,280 Speaker 1: which is a good thing. But you should you know, 208 00:11:32,320 --> 00:11:34,120 Speaker 1: anytime you sign up for a service, and there are 209 00:11:34,160 --> 00:11:37,280 Speaker 1: lots of new services every day, believe me, because we 210 00:11:37,360 --> 00:11:39,400 Speaker 1: do a lot of checking into these and I sign 211 00:11:39,520 --> 00:11:40,840 Speaker 1: up for a lot of them just to see what 212 00:11:40,840 --> 00:11:43,200 Speaker 1: they're like. But you know, each one of them, when 213 00:11:43,240 --> 00:11:46,440 Speaker 1: you sign up, they give you the terms and conditions 214 00:11:46,600 --> 00:11:49,800 Speaker 1: of the service. And you know, it's a long legal document. 215 00:11:49,800 --> 00:11:51,760 Speaker 1: A lot of people don't read. Do they just click 216 00:11:51,840 --> 00:11:55,360 Speaker 1: I agree and sign up. So are you signing away 217 00:11:55,400 --> 00:11:59,480 Speaker 1: the rights to your spreadsheets or your uh you know, 218 00:11:59,559 --> 00:12:04,400 Speaker 1: screen a or whatever else your power point presentations? Uh? 219 00:12:04,520 --> 00:12:07,320 Speaker 1: You know by doing that? Yeah, you know you have 220 00:12:07,360 --> 00:12:09,320 Speaker 1: to check these things out otherwise, you know, all this 221 00:12:09,440 --> 00:12:12,240 Speaker 1: information that you store away might end up on somebody 222 00:12:12,280 --> 00:12:14,560 Speaker 1: else's computer. Yeah. That that kind of goes back to 223 00:12:14,559 --> 00:12:16,960 Speaker 1: to the first point we were making about, you know, 224 00:12:17,200 --> 00:12:21,240 Speaker 1: make sure you know who has access to your information. Um. 225 00:12:21,440 --> 00:12:26,360 Speaker 1: So these are all important issues. They're not they're not trivial. Uh. 226 00:12:26,840 --> 00:12:29,400 Speaker 1: But at the same time, do keep in mind that, 227 00:12:29,679 --> 00:12:31,640 Speaker 1: like we said before, it is in the company's best 228 00:12:31,679 --> 00:12:36,480 Speaker 1: interests to to make sure that your data remains safe 229 00:12:36,480 --> 00:12:39,800 Speaker 1: and secure. Otherwise they don't have a business model. So 230 00:12:41,240 --> 00:12:45,080 Speaker 1: hopefully we'll be able to say that this dark side 231 00:12:45,320 --> 00:12:48,120 Speaker 1: is more something that everyone's already thinking about and and 232 00:12:48,200 --> 00:12:53,160 Speaker 1: trying to address, and not a fundamental flaw in in 233 00:12:53,280 --> 00:12:57,120 Speaker 1: that in that model, because you know, you know, I 234 00:12:57,760 --> 00:13:00,120 Speaker 1: don't think I don't think anything's going to stop the 235 00:13:00,920 --> 00:13:05,200 Speaker 1: incable progress of cloud computing. It's got a lot of it. 236 00:13:05,200 --> 00:13:08,280 Speaker 1: It does have a lot of advantages over over storing 237 00:13:08,360 --> 00:13:11,400 Speaker 1: information on your own computer because honestly, a lot of 238 00:13:11,400 --> 00:13:14,319 Speaker 1: these places offer gigabytes and gigabytes of storage and it's 239 00:13:14,360 --> 00:13:17,960 Speaker 1: only going up. I mean, as as storage capacity increases 240 00:13:17,960 --> 00:13:20,200 Speaker 1: in the cost of it decreases, you're going to see 241 00:13:20,240 --> 00:13:24,280 Speaker 1: cloud computing services offering to give you, you know, tons 242 00:13:24,320 --> 00:13:26,680 Speaker 1: more space than you could ever have on your own 243 00:13:26,760 --> 00:13:28,920 Speaker 1: personal hard drive, which you could use for you know, 244 00:13:29,040 --> 00:13:31,240 Speaker 1: games and stuff like that if you don't want to 245 00:13:31,360 --> 00:13:34,760 Speaker 1: store a lease documents. So um, you know. I don't 246 00:13:34,760 --> 00:13:37,520 Speaker 1: think that there's any reason to uh to give up 247 00:13:37,600 --> 00:13:40,040 Speaker 1: on cloud computing based on these things, but there are 248 00:13:40,040 --> 00:13:41,599 Speaker 1: things to consider when you do sign up for a 249 00:13:41,640 --> 00:13:46,000 Speaker 1: service exactly. For more on this and thousands of other topics, 250 00:13:46,120 --> 00:13:49,120 Speaker 1: does it how stuff works dot Com? Let us know 251 00:13:49,160 --> 00:13:52,079 Speaker 1: what you think. Send an email to podcast at how 252 00:13:52,120 --> 00:13:58,400 Speaker 1: stuff works dot com. Brought to you by the reinvented 253 00:13:58,440 --> 00:14:01,080 Speaker 1: two thousand twelve camera. It's ready, are you