WEBVTT - TechStuff Classic: TechStuff Goes for a Google Drive 0:00:04.240 --> 0:00:07.240 Welcome to tech Stuff, a production of I Heart Radios 0:00:07.320 --> 0:00:13.800 How Stuff Works. Hey there, and welcome to tech Stuff. 0:00:13.840 --> 0:00:17.200 I'm your host, Jonathan Strickland. I'm an executive producer with 0:00:17.239 --> 0:00:19.239 How Stuff Works and I Heeart Radio and I love 0:00:19.400 --> 0:00:23.200 all things tech and it's time for another classic episode. 0:00:23.239 --> 0:00:27.320 This episode originally published on May twenty three, two thousand twelve, 0:00:27.720 --> 0:00:30.920 and Chris and I decided to talk about Google Drive. 0:00:31.400 --> 0:00:34.360 It is called tech stuff goes for a Google Drive. Now, 0:00:34.400 --> 0:00:37.840 at the time that we recorded this, How stuff Works 0:00:37.880 --> 0:00:43.480 was not using Google Drive as a true storage, cloud computing, 0:00:43.880 --> 0:00:47.760 you know platform. We we had it personally, but we 0:00:47.760 --> 0:00:50.520 weren't using it as a company. That would change over 0:00:50.520 --> 0:00:53.279 the years. How stuff Works would adopt Google Drive at 0:00:53.280 --> 0:00:56.800 one point, and now we're in another transition phase, which 0:00:56.800 --> 0:00:59.240 is a lot of fun. I'm looking at my producer Tari, 0:00:59.480 --> 0:01:02.120 who is agreeing with me about how fun it is 0:01:02.320 --> 0:01:05.480 to try and transfer from one storage system to another. 0:01:05.520 --> 0:01:07.640 She's she's giving me a big I think it's a 0:01:07.760 --> 0:01:13.360 thumbs up. There's definitely there's definitely a finger up. I'm 0:01:13.360 --> 0:01:15.720 gonna say it's a thumb So I hope you guys 0:01:15.880 --> 0:01:19.360 enjoy this conversation. About Google Drive, and I'll talk to 0:01:19.400 --> 0:01:23.959 you again in just a moment. So today tech stuff fans, 0:01:24.040 --> 0:01:26.720 we're all gonna go on a little Google Drive. O. Cool. 0:01:26.760 --> 0:01:29.360 We're gonna talk about those robotic cars that don't need 0:01:29.480 --> 0:01:32.160 drivers except you know, when they're sitting in the seat 0:01:32.200 --> 0:01:36.199 and they watch the car where you're on somebody else. No, 0:01:36.400 --> 0:01:39.399 that's that's not what my notes are on. I was 0:01:39.440 --> 0:01:42.760 talking about Google Drive, you know, the cloud storage Google 0:01:42.840 --> 0:01:48.080 Drive announced on a Well, this will be a fun podcast. 0:01:48.080 --> 0:01:50.480 We're gonna see what our notes show. Um. No, really, 0:01:50.480 --> 0:01:53.080 we're gonna talk about Google Drive today and the day 0:01:53.080 --> 0:01:55.960 we're recording this podcast, just in case you guys are curious. 0:01:56.440 --> 0:01:58.000 I know that you'll be listening to it quite a 0:01:58.000 --> 0:02:00.240 while afterwards because we record so early and that ants. 0:02:00.280 --> 0:02:03.640 But it's April the day we're recording this, so it's 0:02:03.680 --> 0:02:08.000 just three days after Google finally officially announced and launched 0:02:08.080 --> 0:02:10.720 Google Drive. Right. It was sort of a one of 0:02:10.720 --> 0:02:13.799 those closely guarded secrets like that everyone knew about it, 0:02:13.840 --> 0:02:16.000 and everyone knew about like the iPad for two years 0:02:16.000 --> 0:02:17.880 before it was released. Right. Yeah, people have been talking 0:02:17.919 --> 0:02:21.320 about Google having a cloud storage service for for a 0:02:21.320 --> 0:02:24.200 couple of years now, so this was and even Google 0:02:24.280 --> 0:02:26.399 made reference to that. But before we really get into 0:02:26.440 --> 0:02:28.560 what Google Drive is, we should probably talk about what 0:02:28.639 --> 0:02:32.720 cloud storage is in general and why it's important. Uh, 0:02:32.919 --> 0:02:35.880 cloud storage is pretty it's a pretty simple concept. The 0:02:35.960 --> 0:02:40.000 idea is that you can store data on servers in 0:02:40.040 --> 0:02:44.000 the cloud. So you're talking about using someone else's computers 0:02:44.040 --> 0:02:47.120 to store your information, and you can access the information 0:02:47.280 --> 0:02:51.520 over the Internet using some sort of interface, usually web based, 0:02:52.639 --> 0:02:54.840 And they call it the cloud, of course, because the 0:02:54.880 --> 0:02:58.440 Internet is a nebulous group of machines and it's just 0:02:58.480 --> 0:03:01.320 sort of out there all is changing like a cloud. 0:03:01.919 --> 0:03:04.600 So yeah, so, and and the idea being that it's 0:03:04.639 --> 0:03:06.240 also kind of like a cloud in the sense that 0:03:06.880 --> 0:03:09.720 you can access it from any machine that has that 0:03:09.840 --> 0:03:14.040 Internet capability. Right. It may require a special app depending 0:03:14.120 --> 0:03:17.400 upon the type of cloud storage. Uh, because not everything 0:03:17.520 --> 0:03:20.560 is web based. There are a lot of different desktop 0:03:20.600 --> 0:03:22.960 clients that you can have that will allow you to 0:03:23.200 --> 0:03:27.280 store information to a cloud drive. So it lives on 0:03:27.400 --> 0:03:30.840 your computer's desktop as if it were a regular file folder. Right, 0:03:31.240 --> 0:03:34.480 So you think of your your regular hard drive folders 0:03:34.520 --> 0:03:37.080 that you would go into to look at various files, 0:03:37.080 --> 0:03:38.840 like you might store all your pictures in a in 0:03:38.880 --> 0:03:41.680 a pictures folder, and all your videos and a videos folder, 0:03:41.720 --> 0:03:44.960 that kind of thing. Um, a cloud storage drive might 0:03:45.000 --> 0:03:47.320 show up on your desktop as if it were a 0:03:47.320 --> 0:03:50.000 regular folder on your computer, but instead of living on 0:03:50.000 --> 0:03:53.800 your computer, the information gets sent over the Internet to 0:03:54.160 --> 0:03:59.080 a a remote machine and it's stored on that machine. 0:03:59.200 --> 0:04:03.440 And there is no identifier that links that particular file 0:04:03.560 --> 0:04:06.840 to you as a user, a registered user of that service. 0:04:07.520 --> 0:04:09.480 And uh, in fact, when I say it lives on 0:04:09.480 --> 0:04:13.400 one machine, that's not entirely true. Almost every cloud service, 0:04:13.400 --> 0:04:17.360 in fact, every reputable cloud service out there uses redundant 0:04:17.400 --> 0:04:20.720 measures so that the file is on several different machines 0:04:20.760 --> 0:04:24.200 in case one machine fails. I'm real sorry, I only 0:04:24.279 --> 0:04:27.440 had one machine and it went down. Yeah, that would 0:04:27.440 --> 0:04:31.600 not go over so well. Uh Jester's cloud service, Jester's 0:04:31.600 --> 0:04:35.000 cloud service. Yeah, there's never really been up on that whole. 0:04:35.120 --> 0:04:36.599 I think I need to I think I need to 0:04:36.680 --> 0:04:41.039 register that domain now, Chester's cloud service. We got hair 0:04:41.240 --> 0:04:45.680 a cumula nimbus um. So the Yeah, the idea is 0:04:45.720 --> 0:04:50.080 that obviously that you would be able to offload storage 0:04:50.120 --> 0:04:53.640 from your native device, especially if you are one of 0:04:53.640 --> 0:04:56.240 those people who has lots of different devices, and you 0:04:56.279 --> 0:04:58.719 want to be able to access the same information no 0:04:58.760 --> 0:05:02.120 matter which device you're using. Because in the old days, 0:05:02.440 --> 0:05:05.159 back before a cloud storage, a couple of years ago, yeah, 0:05:05.240 --> 0:05:07.680 not that long ago, you you only had a few 0:05:07.720 --> 0:05:13.080 different options. You could save something to a physical medium, 0:05:13.080 --> 0:05:16.520 so a disk for example, compact disc or a floppy 0:05:16.520 --> 0:05:18.880 disc way back in the day, or a thumb drive 0:05:19.000 --> 0:05:21.520 something like that, and then you could pourt that over 0:05:21.560 --> 0:05:25.120 to another device, pull it up from the physical medium, 0:05:25.160 --> 0:05:27.440 and then work on it that way, save it back 0:05:27.480 --> 0:05:29.600 to the physical medium, and then go back, and you 0:05:29.640 --> 0:05:31.840 know it. It was a little cumbersome. It also meant 0:05:31.880 --> 0:05:34.680 that you would often end up with lots of duplicate 0:05:34.839 --> 0:05:38.000 copies of a particular file, and if people made changes, 0:05:38.040 --> 0:05:39.520 then you had to figure out, all right, which one 0:05:39.560 --> 0:05:43.039 of these copies has the most recent, most relevant changes, 0:05:43.400 --> 0:05:44.680 and then I have to get rid of all the 0:05:44.720 --> 0:05:47.320 others or else I'm going to confuse them all. Yeah, 0:05:47.360 --> 0:05:48.719 you have to go through and you you end up 0:05:48.760 --> 0:05:51.719 looking at creation dates and when things were modified. Wait, 0:05:51.800 --> 0:05:55.919 that was done at nine, Okay, I can get rid 0:05:55.960 --> 0:05:57.839 of that one. And it takes forever, and and it's 0:05:57.920 --> 0:06:01.719 particularly difficult if you have more than one collaborator, Right, 0:06:01.760 --> 0:06:04.000 So if Chris and I were working on a document, 0:06:04.160 --> 0:06:06.839 it would be frustrating for us to try and and 0:06:06.880 --> 0:06:09.920 we're both working on copies of a document, we're both 0:06:09.920 --> 0:06:13.039 making changes, be very frustrating to cohlate those changes and 0:06:13.080 --> 0:06:15.880 figure out you know which ones are relevant and which 0:06:15.920 --> 0:06:18.400 ones are the most recent. Uh, and may very well 0:06:18.400 --> 0:06:21.160 be that a change I make makes a later change 0:06:21.160 --> 0:06:25.760 that Chris makes irrelevant. So the idea behind cloud storage 0:06:25.880 --> 0:06:28.880 is it's not and it's not always connected, but there's 0:06:28.920 --> 0:06:32.240 a lot of work around collaboration in cloud storage, so 0:06:32.320 --> 0:06:35.120 that if you have multiple people who need access to 0:06:35.120 --> 0:06:38.760 a particular file, you are able to share that file 0:06:38.839 --> 0:06:42.760 across several instances, and you might even be able to 0:06:42.760 --> 0:06:45.640 have multiple people work on that file at the same time, 0:06:45.720 --> 0:06:48.240 and those changes will be reflected more or less in 0:06:48.320 --> 0:06:51.159 real time for each person. So that way, if Chris 0:06:51.160 --> 0:06:54.119 Word did make a change to a sentence within that file, 0:06:54.200 --> 0:06:56.479 I could actually see him making that more or less 0:06:56.480 --> 0:06:59.839 in real time. This is particularly true with Google Service, 0:06:59.839 --> 0:07:03.560 but because Google Drive has been very tightly integrated with 0:07:03.640 --> 0:07:06.560 Google Docs, in fact, it's kind of superseded Google Docs 0:07:06.560 --> 0:07:10.680 in a way, but other services also offer similar features. 0:07:11.960 --> 0:07:14.240 Um And just to clear things up, my my joke 0:07:14.280 --> 0:07:16.480 about a couple of years ago, of course, the cloud 0:07:16.600 --> 0:07:20.600 is uh much older than that. We've been using variations 0:07:20.640 --> 0:07:24.720 on cloud services for many years now. Uh. In fact, 0:07:24.760 --> 0:07:28.880 I don't think I think it really proceeds labeling things 0:07:28.920 --> 0:07:33.120 as cloud, which is really sort of a convenient marketing 0:07:33.240 --> 0:07:36.520 term for for services such as these. Um, it gives 0:07:36.520 --> 0:07:40.440 you it when people mention the cloud. It basically serves 0:07:40.480 --> 0:07:43.600 as a a hint to say, hey, the materials or 0:07:43.760 --> 0:07:47.720 software is being stored on servers on the Internet, not 0:07:47.800 --> 0:07:49.960 on your computer. So it's it's sort of a short 0:07:50.080 --> 0:07:53.440 marketing shorthand for these services. But yeah, I mean we've 0:07:53.480 --> 0:07:57.320 talked about Google Docs many times. I mean it predates 0:07:57.360 --> 0:08:00.800 the beginning of our podcast, so um And there were 0:08:00.840 --> 0:08:04.080 many services using those kinds of uh, those kinds of 0:08:04.080 --> 0:08:07.560 technologies before, but in recent in recent years, there have 0:08:07.640 --> 0:08:13.720 been several services that take advantage of cloud storage. Specifically, um, 0:08:13.760 --> 0:08:18.720 not simply to store that the software as a service, 0:08:18.800 --> 0:08:21.320 you know, or or the documents that you say in 0:08:21.360 --> 0:08:25.360 Google Docs, um, but to upload and download your own 0:08:25.360 --> 0:08:27.640 file so that you don't have to use a physical medium. 0:08:28.000 --> 0:08:30.160 You don't have to worry about losing that that flash 0:08:30.280 --> 0:08:33.000 drive you carry in your pocket or your bag. Um, 0:08:33.040 --> 0:08:35.080 you don't have to walk a disk from one place 0:08:35.120 --> 0:08:38.439 to another or worry about it if you want to, say, 0:08:39.440 --> 0:08:41.480 work on a graduate school assignment on your lunch break 0:08:41.480 --> 0:08:43.480 at work. I don't know anyone who would have done 0:08:43.520 --> 0:08:46.240 that at how stuff works, except maybe me co fle 0:08:46.280 --> 0:08:48.280 of years ago. Or you just happen to have like 0:08:48.320 --> 0:08:50.559 a whole bunch of really powerful magnets nearby and you 0:08:50.600 --> 0:08:53.480 don't want to use magnetic storage. Turn it. I had 0:08:53.520 --> 0:08:55.240 my flash drive in my pocket when I went for 0:08:55.280 --> 0:08:57.040 the m R. I I was thinking. I was thinking 0:08:57.040 --> 0:08:59.880 of the old old floppy disk days. I actually did 0:09:00.080 --> 0:09:03.400 lose data on a floppy disk because uh, floppy disk 0:09:03.440 --> 0:09:04.920 had a little bit of a close encounter with a 0:09:04.960 --> 0:09:08.320 magnet and that was enough to ruin it. Oh yeah, 0:09:08.360 --> 0:09:12.559 but um yeah, I mean these these services were being 0:09:12.600 --> 0:09:16.160 marketed specifically as a hey, you can store stuff here, 0:09:16.200 --> 0:09:20.400 and and um, the services in question, many of them 0:09:20.440 --> 0:09:23.760 came from from the little guys. We're not talking about 0:09:23.760 --> 0:09:28.400 Apple or Google or Facebook or Amazon or Microsoft. These 0:09:28.440 --> 0:09:32.080 were all independent vendors and they would offer. They still 0:09:32.120 --> 0:09:34.880 do offer a free tier of service for a small 0:09:34.920 --> 0:09:37.360 amount of storage, and then you could upgrade for a 0:09:37.400 --> 0:09:39.680 certain price per month you could get more storage, and 0:09:39.800 --> 0:09:41.920 for more than that you get more storage, and they 0:09:42.400 --> 0:09:44.480 they basically would work that out in businesses. If you 0:09:44.520 --> 0:09:47.520 really needed a whole lot of cloud storage, um, you 0:09:47.559 --> 0:09:49.880 know you could do that. But gradually the big players 0:09:49.880 --> 0:09:52.319 have been getting into the game. And that's why, uh, 0:09:52.720 --> 0:09:55.280 everybody has been expecting Google to do it, because I mean, hey, 0:09:55.280 --> 0:09:59.200 if anybody's got server storage and data centers, it's Google. 0:10:00.000 --> 0:10:05.000 It turns out that storage is relatively inexpensive, so very 0:10:05.080 --> 0:10:07.800 very inexpensive over the last few years. So so for 0:10:07.840 --> 0:10:11.000 a business to enter into that and just purchase a 0:10:11.040 --> 0:10:17.160 lot of different servers specifically to save information from from users, uh, 0:10:17.280 --> 0:10:20.680 it's not as big a barrier as some other forms 0:10:20.679 --> 0:10:23.840 of internet based businesses. However, it does mean that you 0:10:23.880 --> 0:10:26.719 have to create these systems in place for things like security. 0:10:26.920 --> 0:10:29.320 You need to have you know, the important things for 0:10:29.360 --> 0:10:34.040 cloud computing involved security accessibility. So you want to make 0:10:34.040 --> 0:10:37.160 sure that whatever your system is, it's easy to access 0:10:37.200 --> 0:10:40.520 on multiple platforms. So that means you want people to 0:10:40.559 --> 0:10:45.240 be able to access it via PC, mac, smartphone, tablet. 0:10:45.640 --> 0:10:48.160 Lots of different devices can connect to the Internet now, 0:10:49.160 --> 0:10:51.640 so you want to be able to give your users 0:10:51.679 --> 0:10:54.400 the freedom to be able to access the information over 0:10:54.440 --> 0:10:57.560 as many of platforms as possible. You know, the more 0:10:57.600 --> 0:11:00.560 convenient your services, the more valuable it is to the customer. 0:11:01.160 --> 0:11:05.839 So so security and accessibility and uh, just that that 0:11:05.920 --> 0:11:09.840 whole accessibility slash convenience and just the whole idea of 0:11:09.920 --> 0:11:13.600 giving a certain tier for free so that you you 0:11:14.000 --> 0:11:18.400 show people how valuable the services now and and we 0:11:18.400 --> 0:11:23.000 should clear this up. Cloud storage is not necessarily all 0:11:23.080 --> 0:11:25.960 about backing up your data, although people have used it 0:11:26.000 --> 0:11:30.800 for that kind of purpose. It's really more about, well, 0:11:30.920 --> 0:11:34.600 there's certain documents or certain files that you may want 0:11:34.640 --> 0:11:36.920 to have stored in the cloud because you want to 0:11:36.960 --> 0:11:39.800 have easy access across multiple devices. You may want to 0:11:39.840 --> 0:11:42.720 share that with other people, and it's a lot easier 0:11:42.760 --> 0:11:45.360 to do that when it's on a web based drive 0:11:45.520 --> 0:11:48.040 than it would be on your own computers. So let's 0:11:48.040 --> 0:11:50.320 say that I've shot a video and I've got this 0:11:50.400 --> 0:11:53.920 video living on my computer, emailing that video out to 0:11:54.360 --> 0:11:57.560 all the different people I want to see it. Uh, 0:11:57.720 --> 0:11:59.880 maybe I don't want to upload it to something like YouTube. 0:12:00.120 --> 0:12:02.440 Maybe I just want to send that directly to a 0:12:02.480 --> 0:12:05.520 few people. Well, for example, what if you were trying 0:12:05.520 --> 0:12:07.880 to preview a video with the people you were working 0:12:08.040 --> 0:12:10.240 collaborating with it on right exactly, you're not ready to 0:12:10.240 --> 0:12:12.880 make it public? Yeah, yeah, you might need to still 0:12:12.920 --> 0:12:15.480 do some edits. You may you may just be looking 0:12:15.559 --> 0:12:19.000 at this with your friends and say, just just doesn't 0:12:19.040 --> 0:12:21.920 feel snappy enough. Do you have any suggestions? So in 0:12:21.920 --> 0:12:24.559 that case, yeah, you wouldn't want to necessarily upload to YouTube. 0:12:24.600 --> 0:12:26.960 I mean, you could upload YouTube and make it private 0:12:27.040 --> 0:12:29.400 and then send out the link. But but if you 0:12:29.520 --> 0:12:31.760 just would rather skip that stuff and and just keep 0:12:31.760 --> 0:12:35.240 it in pre production mode, um, then a cloud drive 0:12:35.280 --> 0:12:37.800 would be very useful. You could send out, you could 0:12:37.800 --> 0:12:40.640 share the link to that file within your cloud drive, 0:12:41.000 --> 0:12:43.160 and then other people could go to your cloud drive 0:12:43.240 --> 0:12:46.360 and view that one particular file without having access to 0:12:46.480 --> 0:12:49.280 anything else that's in your cloud drive. So all they 0:12:49.320 --> 0:12:53.280 would get is access to whatever file you you permitted 0:12:53.320 --> 0:12:56.120 them access to. Now you might be able to set 0:12:56.160 --> 0:12:59.520 some permissions on files so that they are publicly available. 0:12:59.760 --> 0:13:03.240 Would means that anyone who could visit your drive would 0:13:03.280 --> 0:13:06.920 be able to see that particular file. But in most cases, 0:13:06.960 --> 0:13:09.800 I think people just have special permissions for particular folks 0:13:10.000 --> 0:13:11.480 and then and of course you could always say that 0:13:11.559 --> 0:13:14.400 where only you have access to it, there's no need 0:13:14.480 --> 0:13:17.680 to you know, you're not forced to collaborate. Right, So 0:13:18.320 --> 0:13:20.599 those are the that's the basics around cloud drives. And 0:13:20.840 --> 0:13:23.240 one of the reasons why I think cloud drives are 0:13:23.280 --> 0:13:26.600 getting more important is that you're starting to see, right 0:13:26.640 --> 0:13:29.160 about the time we're recording this podcast, in particular, you're 0:13:29.160 --> 0:13:32.920 starting to see some some devices come out besides ones 0:13:32.960 --> 0:13:35.880 that come from a company company that rhymes with shmapple 0:13:36.440 --> 0:13:41.360 that that don't have expandable memory as a feature. So 0:13:41.360 --> 0:13:43.240 so in other words, there's no slot for you to 0:13:43.280 --> 0:13:46.040 put a memory card into. Oh well, we've already talked 0:13:46.080 --> 0:13:50.160 about ultra books, UM, which don't have in general, don't 0:13:50.200 --> 0:13:52.960 have optical drives. You know they they save space, save 0:13:53.080 --> 0:13:56.560 energy UM by not having that. And you know where 0:13:56.600 --> 0:13:59.240 you have a limited amount of storage on board, so 0:13:59.480 --> 0:14:01.719 you could you was something like a flash drive or 0:14:01.880 --> 0:14:05.120 a portable drive where you have a connection, um, but 0:14:05.320 --> 0:14:08.400 you you do need something to store files on otherwise 0:14:08.679 --> 0:14:09.960 you know, you're really not going to be able to 0:14:09.960 --> 0:14:14.520 create stuff. Well, although granted most ultrabooks probably have significantly 0:14:14.559 --> 0:14:17.240 more storage on board than your typical at least you're 0:14:17.320 --> 0:14:20.760 free tier of cloud storage out there. Oh yes, definitely. 0:14:20.800 --> 0:14:23.360 But things like smartphones, I mean, here's an example. I'll 0:14:23.360 --> 0:14:25.720 give a real world example, because again this is a 0:14:26.640 --> 0:14:29.520 recording this and this phone was just announced on T 0:14:29.720 --> 0:14:34.040 Mobile was the HTC one S. It's an Android based 0:14:34.040 --> 0:14:37.840 phone running ice cream Sandwich. It has sixteen gigabytes on 0:14:38.000 --> 0:14:42.000 board memory. Alright, sixteen gigs on board memory. No flash 0:14:42.080 --> 0:14:44.720 drive knows, no smart card drive at all, so you 0:14:44.760 --> 0:14:47.440 can't add more memory to it. That's sixteen gigs is 0:14:47.480 --> 0:14:52.120 all you get. However, ht C one S also comes 0:14:52.160 --> 0:14:56.480 with a trial period with Dropbox, which is another cloud 0:14:56.520 --> 0:14:59.360 based storage system. And we'll talk more about Dropbox a 0:14:59.400 --> 0:15:02.920 little bit later in this podcast. So in this case, 0:15:02.960 --> 0:15:07.280 you're talking about a smartphone that is encouraging you to 0:15:07.520 --> 0:15:12.000 use cloud based storage rather than some sort of physical media. 0:15:12.160 --> 0:15:14.720 So that way you have this this your information is 0:15:14.760 --> 0:15:17.800 backed up into the cloud. And theoretically, when you are 0:15:17.880 --> 0:15:20.920 ready to upgrade your phone or switch phones, or maybe 0:15:21.000 --> 0:15:22.720 you lose your phone you have to get a new phone, 0:15:22.920 --> 0:15:25.360 you would still have access to that information because it 0:15:25.400 --> 0:15:27.760 exists on the cloud, not on a physical device in 0:15:27.760 --> 0:15:30.080 your hand. I mean it's it's on a physical device, 0:15:30.080 --> 0:15:33.400 it's just that physical device belongs to some other company. 0:15:33.680 --> 0:15:36.400 So that's one of the other reasons why cloud storch 0:15:36.480 --> 0:15:39.760 is so important is that we're starting to see manufacturers 0:15:39.840 --> 0:15:44.400 kind of offload features onto the cloud so that they 0:15:44.440 --> 0:15:47.160 don't include them in the phone itself. It helps a 0:15:47.240 --> 0:15:50.320 little bit with phone design because it means that you 0:15:50.400 --> 0:15:53.440 don't need to build in that feature. You can actually 0:15:53.440 --> 0:15:56.600 make your phones slimmer and sleeker. I mean, Apple has 0:15:56.640 --> 0:15:59.800 been doing this for ages, but other companies are starting 0:15:59.800 --> 0:16:02.680 to do the same sort of thing. Now, that's enough 0:16:02.800 --> 0:16:05.840 about cloud storage in general, I think, unless is there 0:16:05.840 --> 0:16:08.200 anything else that we need to talk about. There was 0:16:08.240 --> 0:16:10.280 one other thing I didn't want to uh to pass 0:16:10.320 --> 0:16:13.040 over it too much is UM. And this is something 0:16:13.080 --> 0:16:17.280 we've visited several times too, is the aspect of privacy. UM. 0:16:17.320 --> 0:16:19.120 You know, a couple of years ago when we were 0:16:19.160 --> 0:16:21.840 talking about this UM, you know, when we was starting 0:16:21.880 --> 0:16:24.280 to become a public topic. You know, hey, what is 0:16:24.320 --> 0:16:28.120 cloud storage? What it was cloud computing? UM? You know, 0:16:28.160 --> 0:16:30.400 people didn't really get that and then when you explain it, 0:16:30.440 --> 0:16:33.200 they'd start thinking about the documents that you would store 0:16:33.280 --> 0:16:36.600 up there and privacy, what if somebody hacks in? Um. 0:16:36.640 --> 0:16:38.920 I think it's obvious at this point that the convenience, 0:16:39.560 --> 0:16:44.080 UM and accessibility of cloud storage has made it we 0:16:44.240 --> 0:16:46.400 were we've gone so far now that I don't think 0:16:46.400 --> 0:16:49.800 we're going to go back. Um, but it's obviously. I 0:16:49.880 --> 0:16:52.640 just think it's interesting to note that at this point 0:16:53.040 --> 0:16:55.240 we are you know, there are things that we look at, 0:16:55.280 --> 0:16:58.920 you know, whether this this particular company is more uh 0:16:58.960 --> 0:17:02.120 likely to have of good security and privacy then the 0:17:02.160 --> 0:17:06.040 other company. But um, yeah, that's it's the security of 0:17:06.440 --> 0:17:13.040 these cloud storage uh services has become sort of a given. 0:17:13.280 --> 0:17:15.000 Oh well, you know, if they're going to offer this, 0:17:15.440 --> 0:17:18.320 they better be offering security because I'm going to use 0:17:18.320 --> 0:17:21.080 the service, and you know, that's something I look for 0:17:21.160 --> 0:17:23.720 before I do that, so that that doesn't even seem 0:17:23.800 --> 0:17:26.240 that seems like a given now when before people are 0:17:26.240 --> 0:17:27.840 going I don't know if I want to do this 0:17:28.000 --> 0:17:30.560 or not. Yeah, we can talk a little bit about 0:17:30.560 --> 0:17:34.400 Google's approach to privacy and security. In fact, we will 0:17:34.440 --> 0:17:36.600 have to because there is a controversy that we we 0:17:36.640 --> 0:17:38.920 will have to address. But before we do that, let's 0:17:38.920 --> 0:17:41.879 get into the basics of Google Drive. So it is 0:17:41.920 --> 0:17:44.600 built directly into Google Docs. Now, so Google Docs. The 0:17:44.760 --> 0:17:47.040 if you were to open up a Google Docs account, 0:17:47.160 --> 0:17:49.240 so which is just your regular Google account, that's what 0:17:49.280 --> 0:17:52.320 it's attached to. So if you have a Google account, congratulations, 0:17:52.400 --> 0:17:54.399 you have a Google Docs account. You can go to 0:17:54.440 --> 0:17:58.040 Google Docs and create a document, whether that's a word document, 0:17:58.200 --> 0:18:00.680 word being, word processing document not where it is in 0:18:00.800 --> 0:18:05.960 Microsoft Word, but a word processing document, presentation spreadsheet, you know, 0:18:06.000 --> 0:18:09.040 all the basic types of office documents. Google has the 0:18:10.200 --> 0:18:12.960 those as features. If you were to create one and 0:18:13.040 --> 0:18:15.560 save it, it it would save it into your Google Drive 0:18:15.600 --> 0:18:20.480 account and you would automatically get the the base free tier, 0:18:21.119 --> 0:18:24.160 which for Google Drive is five gigabytes of free storage. 0:18:25.240 --> 0:18:27.760 And the nice thing about this is that that doesn't 0:18:27.840 --> 0:18:31.240 count any of the documents in your Google Docs, so 0:18:31.320 --> 0:18:34.400 it doesn't know I didn't know that. That's interesting. That's 0:18:34.400 --> 0:18:38.280 good to know. Uh the Now, what you can also 0:18:38.280 --> 0:18:41.400 do is you can download a client onto your desktop 0:18:41.560 --> 0:18:44.880 that allows you to drag and drop files from your 0:18:44.920 --> 0:18:48.920 computer into your Google Drive, so that you can easily 0:18:49.000 --> 0:18:52.560 port over if you've got say, uh, photo album on 0:18:52.680 --> 0:18:55.240 your computer and you like the photo album and you 0:18:55.280 --> 0:18:57.399 want to keep it, but you don't really want it 0:18:57.480 --> 0:19:00.440 taking up space on your local hard drive. You could 0:19:00.920 --> 0:19:03.440 copy it, or not copy it, but move it over 0:19:03.520 --> 0:19:05.960 to your Google Drive and it would store there. It 0:19:06.000 --> 0:19:08.480 would have you have a folder within your Google Drive 0:19:08.680 --> 0:19:10.480 where you could access that, and you could access it 0:19:10.480 --> 0:19:15.200 with any web connected device that at least any web 0:19:15.200 --> 0:19:19.480 connected device, either through the web system or depending on 0:19:19.560 --> 0:19:22.440 the device, you might have a dedicated app that would 0:19:22.520 --> 0:19:25.520 let you access it. So for example, Google Drive, you 0:19:25.560 --> 0:19:28.240 can do that on PCs and max uh and you 0:19:28.280 --> 0:19:31.520 can do it on Android phones. And they're working on 0:19:32.320 --> 0:19:34.600 the recording of this podcast. They were working on an 0:19:34.600 --> 0:19:37.920 iOS app so that you would be able to access 0:19:37.960 --> 0:19:42.360 it easily through your iPhone or iPod touch or iPad. 0:19:43.280 --> 0:19:45.880 And they also, from what I understand, I did see 0:19:45.880 --> 0:19:48.639 an article on a Linux website the other day that 0:19:48.800 --> 0:19:52.880 was quite upset that there was not compatibility built in 0:19:52.920 --> 0:19:56.720 for Linux as in as in a and a dedicated application. 0:19:56.840 --> 0:20:00.639 From what I understand, they're working too. Of course, you know, 0:20:00.760 --> 0:20:03.920 if you're using Linux now and and you've probably already 0:20:03.920 --> 0:20:07.199 tried to use your drive with it, if you're you know, 0:20:07.280 --> 0:20:09.879 a Google customer. Um, you can of course use the 0:20:09.920 --> 0:20:13.800 web version. Um. But but they're working on a dedicated app. 0:20:13.800 --> 0:20:17.000 From what I understand, that's that's the nice thing. Yeah, 0:20:17.200 --> 0:20:19.560 even if your your device doesn't have a dedicated app, 0:20:19.600 --> 0:20:22.639 you can still access Google Drive through the web portion, 0:20:22.720 --> 0:20:24.439 like you open up a browser and you can go 0:20:24.520 --> 0:20:26.920 to Google Drive that way. It's not quite as convenient, 0:20:27.000 --> 0:20:30.640 it's not as user friendly. Uh So, I mean that's 0:20:30.680 --> 0:20:33.560 why everyone wants the app, because then you know, you 0:20:33.960 --> 0:20:36.280 bypass that step of having to go through the web. 0:20:36.320 --> 0:20:38.800 It's just like having an app on your phone that 0:20:38.920 --> 0:20:41.800 access a web based email client, so that you don't 0:20:41.800 --> 0:20:44.439 actually have to open up a browser and navigate to 0:20:44.520 --> 0:20:46.520 the email. You just open up the app and there 0:20:46.520 --> 0:20:49.119 you are. Same sort of thing. Chris and I have 0:20:49.200 --> 0:20:51.320 more to say about Google Drive, but before we do, 0:20:51.520 --> 0:21:01.800 let's take a quick break to thank our sponsor. Well, 0:21:01.920 --> 0:21:06.520 there's some other interesting aspects that are unique to to 0:21:06.680 --> 0:21:10.120 the Google Cloud Drive. Because there's you know, like we said, 0:21:10.119 --> 0:21:12.280 there are a lot of different companies out there that 0:21:12.400 --> 0:21:15.680 offer comparable services, but they don't all have the same 0:21:15.720 --> 0:21:18.800 feature set. One of the things that sets Google apart 0:21:19.040 --> 0:21:23.200 is no surprise search. So let's say that you have 0:21:23.560 --> 0:21:25.800 a lot of files in your Google Drive. Let's say 0:21:25.840 --> 0:21:27.400 let's say that you are one of the people who 0:21:27.960 --> 0:21:30.440 you're you've got to upgrade your account because you've got 0:21:30.440 --> 0:21:32.760 a lot of data, and you've got lots of different 0:21:32.840 --> 0:21:36.600 kinds of files. You've got picture files, videos, text documents, 0:21:36.640 --> 0:21:41.160 all that kind of stuff, and scanned documents, so maybe 0:21:41.400 --> 0:21:44.040 PDFs or other forms of scanned documents. You have it 0:21:44.080 --> 0:21:46.959 all in your Google Drive, and then one day you 0:21:47.000 --> 0:21:50.080 need a specific file and for the life that you 0:21:50.160 --> 0:21:53.360 can't remember what folder you saved it in, and you've 0:21:53.359 --> 0:21:55.399 got so many folders in this drive, it's going to 0:21:55.480 --> 0:21:58.040 take you forever to find it. This is something that 0:21:58.080 --> 0:22:01.400 does not happen on an in free one basis at 0:22:01.440 --> 0:22:05.400 Shase Strickland Um, because I am very very good at 0:22:05.400 --> 0:22:08.800 filing things away safely, so safely I will never find 0:22:08.800 --> 0:22:13.240 them again. So Google Search is built into Google Drive, 0:22:13.520 --> 0:22:16.840 and they have gone so far as to start developing 0:22:17.840 --> 0:22:21.320 recognition software. So that let's say that you've scanned in 0:22:21.359 --> 0:22:24.879 a lot of documents. Maybe you've got some old documents 0:22:25.200 --> 0:22:29.840 that are important to you, perhaps they're old family journals, 0:22:30.080 --> 0:22:32.359 and you scanned the pictures and you put them into 0:22:32.359 --> 0:22:36.120 your Google Drive, and you think, there's this great document 0:22:36.200 --> 0:22:40.119 that my grandfather wrote that is pertinent to this blog 0:22:40.160 --> 0:22:42.360 post i'm posting. It would be awesome if I if 0:22:42.400 --> 0:22:46.359 I posted a picture of that page, but gosh, I 0:22:46.440 --> 0:22:50.400 can't remember where I saved it. Well, the image recognition software, 0:22:50.400 --> 0:22:55.040 it actually can scan the scanned documents and look for text. 0:22:55.480 --> 0:22:58.159 So if you type in an UM string, like you 0:22:58.200 --> 0:23:02.159 know that your grand father wrote about I'll give a 0:23:02.200 --> 0:23:05.040 real life example. Let's say my grandfather wrote about a 0:23:05.080 --> 0:23:10.400 massive tornado that completely devastated Gainesville, Georgia, which is true, 0:23:10.600 --> 0:23:13.280 really did happen. My grandfather was in a working in 0:23:13.280 --> 0:23:15.120 a mill at a time, and it ripped the roof 0:23:15.160 --> 0:23:17.320 off the mill. My grandfather was very lucky to get out. 0:23:18.000 --> 0:23:21.720 Um So, let's say that he wrote this great article 0:23:21.760 --> 0:23:24.120 about it, and I had scanned it in I could 0:23:24.160 --> 0:23:28.560 type in Gainesville tornado in my Google uh search for 0:23:28.560 --> 0:23:31.800 for the Google Drive, and it's going to actually look 0:23:31.880 --> 0:23:35.080 and scan the the physical documents, the ones that are 0:23:35.880 --> 0:23:39.880 just image files really and return those as well, which 0:23:39.920 --> 0:23:42.240 is kind of cool. It's not just scanning the text 0:23:42.400 --> 0:23:46.359 in your documents and scanning the images. They're also working 0:23:46.520 --> 0:23:50.159 on adding in the image recognition software that you can 0:23:50.240 --> 0:23:54.520 find in in products like Google Goggles. So with Google Goggles, 0:23:54.520 --> 0:23:57.560 you can hold up a smartphone with a camera to 0:23:57.800 --> 0:24:02.920 a particular kind of objects, sometimes like a landmark or whatever, 0:24:03.200 --> 0:24:05.879 and Google Goggles will use recognition software to try and 0:24:05.920 --> 0:24:09.400 identify what that is. Same sort of thing. Let's say 0:24:09.400 --> 0:24:11.760 that you've taken a bunch of pictures of the Washington 0:24:11.880 --> 0:24:15.080 Monument and then you think, oh, there's this great picture 0:24:15.080 --> 0:24:16.919 of the Washington Monument I want to use, and I 0:24:16.920 --> 0:24:19.560 don't remember where I put it. You could search Washington Monument, 0:24:20.080 --> 0:24:24.120 and that image recognition software will include any images that 0:24:24.400 --> 0:24:28.760 Google identifies as the Washington Monument uh and pulls it 0:24:28.800 --> 0:24:31.600 back even if you didn't title the picture that so 0:24:31.680 --> 0:24:33.840 the picture could be titled something different. It couldn't just 0:24:33.880 --> 0:24:37.280 have the date or some random string of letters and numbers. 0:24:38.080 --> 0:24:41.240 But because that image recognition software is part of Google Search, 0:24:41.960 --> 0:24:44.520 it can pull that up as well, which is a 0:24:44.560 --> 0:24:47.600 really powerful tool. Now, Google does stress that both the 0:24:47.640 --> 0:24:52.200 image recognition software and the the scanning of of scanned 0:24:52.240 --> 0:24:56.720 files software both of that those technologies are in their 0:24:56.760 --> 0:25:01.359 early phases and may not work flawlessly, so uh, you know, 0:25:01.480 --> 0:25:04.359 mileage may vary essentially is what comes out of that. 0:25:04.480 --> 0:25:07.120 But that that is a differentiator is that you've got 0:25:07.160 --> 0:25:10.159 this amazing search tool. It turns out Google knows a 0:25:10.280 --> 0:25:13.240 thing or two about search. They've picked up a couple 0:25:13.240 --> 0:25:16.080 of tricks that that's really cool. They needed to work 0:25:16.119 --> 0:25:18.600 on them. Yeah, no, they've they've got some good some 0:25:18.640 --> 0:25:21.360 good work there, and then they're also working there's there's 0:25:21.400 --> 0:25:25.000 all the collaborative features that you would get with Google Docs. 0:25:25.000 --> 0:25:28.800 So that's included with Google Drive. So assuming that people, 0:25:29.080 --> 0:25:32.119 uh you know that you give access to certain files 0:25:32.119 --> 0:25:35.480 to people, they should be able to make edits and 0:25:35.560 --> 0:25:39.760 everything they're working on, including some other features as well. 0:25:39.800 --> 0:25:42.719 They've actually opened up the platform and they've created an 0:25:42.760 --> 0:25:46.760 API for for companies to add in their own features, 0:25:46.800 --> 0:25:50.200 so extensions and things. So you might be vocation programming interface. Yes, 0:25:51.040 --> 0:25:53.080 so you might be able eventually to do things like 0:25:53.160 --> 0:25:56.280 send facts from your Google Drive to a fax machine 0:25:56.840 --> 0:26:00.600 or to actually have edit videos with in your Google 0:26:00.680 --> 0:26:04.080 Drive itself, so you're not just letting people view a video, 0:26:04.119 --> 0:26:08.080 but perhaps even edit videos within the drive using this 0:26:08.480 --> 0:26:14.880 third party application. But they're the the possibilities are nearly endless. Yeah. 0:26:15.119 --> 0:26:18.119 As a matter of fact, they have already made partnerships 0:26:18.359 --> 0:26:22.000 with some of these companies that that Jonathan is alluding 0:26:22.040 --> 0:26:26.359 to UM for the launch of Google Drive, and you 0:26:26.400 --> 0:26:28.679 can go. You can actually find it pretty easily when 0:26:28.720 --> 0:26:31.040 you go into your Google account that they have these uh, 0:26:31.080 --> 0:26:33.240 these applications that are ready to take advantage of this 0:26:33.640 --> 0:26:36.000 UM And as a matter of fact, um, there is 0:26:36.119 --> 0:26:40.159 ah some of them have UM special deals. Now that 0:26:40.280 --> 0:26:43.000 that's kind of important to note. Uh, just just quickly 0:26:43.040 --> 0:26:47.199 that these third party companies are probably still going to 0:26:47.280 --> 0:26:50.400 charge you for their services. UM. So you know, it's 0:26:50.400 --> 0:26:54.600 not necessarily free, but it does work very very easily, 0:26:54.680 --> 0:26:57.920 and it is uh you know, synchronized with Google Drive, 0:26:58.000 --> 0:27:00.840 so it makes it very easy to do one from 0:27:00.880 --> 0:27:04.800 the other. Right now, your mileage may vary again again. Yeah, 0:27:04.880 --> 0:27:07.199 so let's talk a little bit about the tears that 0:27:07.640 --> 0:27:12.160 the Google offers. No more tears. That's my Aussie Osborne 0:27:12.200 --> 0:27:15.080 reference for the day. Um, actually it's probably not. I'm 0:27:15.119 --> 0:27:17.760 sure I'll get a crazy train in there somewhere man 0:27:18.040 --> 0:27:21.560 or maybe war pigs. Maybe, I'm not sure how you're 0:27:21.560 --> 0:27:25.000 going to get that one. Maybe iron man. Uh, I mean, look, 0:27:25.400 --> 0:27:28.639 I can force a reference if I have to be 0:27:28.760 --> 0:27:33.600 the first time. Anyway, So the tears that Google offers, 0:27:33.840 --> 0:27:37.120 so you've got five gigabytes of free storage. Actually, let's 0:27:37.119 --> 0:27:40.359 back that up. Okay, Google makes its money. We're just 0:27:40.440 --> 0:27:43.880 a little bit deep. Google makes its money from advertising. Yes, 0:27:43.960 --> 0:27:46.800 that's true. Google is an advertising company when you get 0:27:46.840 --> 0:27:50.800 down to it, or at least they they run advertising, right, 0:27:50.960 --> 0:27:53.760 So let's let's kind of take one step back and 0:27:53.800 --> 0:27:57.679 look at Google services. Okay, Google Docs, the previous Google 0:27:57.720 --> 0:28:04.879 Docs free. Yeah, female, that's free. Searches free to the user. UM. 0:28:04.960 --> 0:28:08.040 Android is free for people to uh to install on 0:28:08.119 --> 0:28:13.080 cell phones. Um. All this stuff is offered more or 0:28:13.200 --> 0:28:16.320 less free to the consumer. This is one of the 0:28:16.320 --> 0:28:20.600 big changes. Because Google's competitors in this space, people like 0:28:21.160 --> 0:28:26.200 uh that Jonathan mentioned before, dropbox, Box formerly boxed, dot Net, 0:28:26.600 --> 0:28:30.679 Sugar Sinc. Sky Drive, sky Drive which is Microsoft's UM 0:28:31.200 --> 0:28:35.320 application for this. These guys all offer tears. There's an 0:28:35.359 --> 0:28:40.080 initial free smaller space, and then they are are tiered pricing. 0:28:40.160 --> 0:28:43.480 So you get uh, you know, small for free, you 0:28:43.560 --> 0:28:46.200 get medium for a few dollars a month, you get 0:28:46.280 --> 0:28:48.840 large for a few more dollars a month, etcetera, etcetera. 0:28:49.160 --> 0:28:53.200 So this is new. Google hasn't done this with other products. Really, 0:28:53.240 --> 0:28:57.000 I can't think of one, uh where it offers tiered 0:28:57.000 --> 0:29:02.400 pricing like this. Nothing's pop being the mind immediately. I mean, 0:29:02.440 --> 0:29:04.880 you could make some arguments about Google Voice, but that's 0:29:04.880 --> 0:29:08.640 a little different. That's a little different. Um. Yeah, so 0:29:08.680 --> 0:29:11.400 that's yeah, it is is something to make a call 0:29:11.440 --> 0:29:15.360 on Google Voice normally like over the phone. In general, 0:29:15.400 --> 0:29:17.400 it's free. Now, granted, what Google could have done is 0:29:17.400 --> 0:29:19.440 they could have offered the five gigabytes free storage, and 0:29:19.480 --> 0:29:22.240 that would have been it. But see for Google to 0:29:22.320 --> 0:29:26.200 offer huge amounts of storage for free would be well 0:29:26.200 --> 0:29:28.640 pretty soon Google, that would be eating into Google's revenue. 0:29:28.760 --> 0:29:32.040 So it's understandable why they did what they did. Um 0:29:32.360 --> 0:29:35.160 and really, when we get into the comparisons, you'll see 0:29:35.200 --> 0:29:39.240 it's fairly comparable to the other services. Some offer less 0:29:39.240 --> 0:29:42.840 space for free, some offer more. But um, Dropbox, for example, 0:29:43.000 --> 0:29:45.440 is I would say, the for what it's worth, the 0:29:45.480 --> 0:29:48.920 eight pound gorilla, and yet that offers two gigabytes and 0:29:49.080 --> 0:29:52.680 starts at two gigabytes for friends. For friends, you get 0:29:52.680 --> 0:29:57.280 five hundred megabytes per referral. And up to sixteen gigabytes 0:29:57.360 --> 0:30:00.600 extra storage, so you could have up to eight gigabytes 0:30:00.640 --> 0:30:03.320 for free if you referred that many friends to drop Box. 0:30:04.560 --> 0:30:08.400 Yeah so, uh but but getting back to it, the 0:30:08.440 --> 0:30:11.800 five gigabytes is free for any user. So if you 0:30:12.160 --> 0:30:14.320 have a Google account and you have five gigs free 0:30:14.360 --> 0:30:19.239 storage online right now, uh, if that's enough, then for 0:30:19.320 --> 0:30:22.440 about two dollars, and this is all at launch, I 0:30:22.480 --> 0:30:24.800 should say, because if you're listening to this podcast in 0:30:27.440 --> 0:30:31.000 I'm sure the prices may be different. But for twenty 0:30:31.040 --> 0:30:32.800 for two dollars and forty nine cents a month, you 0:30:32.840 --> 0:30:36.400 can get five gigabytes of storage. For four dollars and 0:30:36.480 --> 0:30:39.160 ninety nine cents a month, you get a hundred gigabytes 0:30:39.160 --> 0:30:42.160 of storage. And if you're really really data hungry, for 0:30:42.280 --> 0:30:46.000 a cool forty nine nine a month, for nine dollars 0:30:46.080 --> 0:30:49.840 nine cents, you can get a terrabyte of storage online. 0:30:50.200 --> 0:30:54.600 So uh so yeah, for people who need way more space. 0:30:54.680 --> 0:30:56.840 Let's say that you're that you do a lot of 0:30:57.240 --> 0:31:00.600 video editing, because you do a lot of liberation with 0:31:00.640 --> 0:31:03.400 other people with videos, and you want to have that 0:31:03.560 --> 0:31:05.920 ability for people to all look at it without it 0:31:06.000 --> 0:31:10.000 going live in any other way, Um, this would be 0:31:10.040 --> 0:31:15.280 pretty useful. And uh, again it's it's kind of comparable 0:31:15.320 --> 0:31:20.560 to what other companies offer. Uh, some of them don't 0:31:20.920 --> 0:31:27.240 have um as high amount of storage that actually, none 0:31:27.280 --> 0:31:29.640 of them offer as much storage as Google Drive does 0:31:29.640 --> 0:31:33.200 at its highest tier. The highest tier that Google Drive 0:31:33.280 --> 0:31:37.640 offers is sixteen terabytes of storage, which is for seven 0:31:39.640 --> 0:31:42.840 a month. Yeah. Well, I would say that some of 0:31:42.880 --> 0:31:46.760 them I've seen essentially say hey, if you need if 0:31:46.800 --> 0:31:48.680 you really need more storage than this, give us a 0:31:48.680 --> 0:31:52.000 call and we'll work something out. Um. But yeah, and 0:31:52.000 --> 0:31:55.240 and there are there are a few things. Um. One 0:31:55.320 --> 0:31:58.640 you know, this isn't completely new because Google docs has 0:31:58.680 --> 0:32:03.280 allowed you to upload files like word Microsoft Word documents 0:32:03.960 --> 0:32:06.080 for a little while now. But this is this is 0:32:06.120 --> 0:32:10.120 basically the formal, uh, the formal announcement that hey, we 0:32:10.160 --> 0:32:12.160 are going to offer you a certain amount of storage 0:32:12.200 --> 0:32:14.440 and this is how much it costs. So it's really 0:32:14.480 --> 0:32:18.600 a delineation of all of that. Um. Yeah. The maximum 0:32:18.600 --> 0:32:21.600 file size that you can upload to a Google Drive 0:32:21.880 --> 0:32:26.120 as assuming that you have that much space as ten gigabytes. Um. 0:32:26.200 --> 0:32:28.640 And uh, which is one of the larger actually, I 0:32:28.640 --> 0:32:31.800 think that's the largest file size among the the consumer 0:32:32.360 --> 0:32:37.360 cloud storage, there's enterprise cloud storage. To Amazon offers enterprise 0:32:37.440 --> 0:32:40.120 level cloud storage. That's a different animal. Well, in a 0:32:40.160 --> 0:32:41.680 way it is, and in a way it isn't, because 0:32:41.720 --> 0:32:44.600 some of the other cloud services are using Amazon as 0:32:44.720 --> 0:32:47.440 their right story. So in some cases you are using 0:32:47.480 --> 0:32:51.280 Amazon Cloud storage, you're just using it through another company. 0:32:51.760 --> 0:32:54.640 But yeah, we can genius business model right there. We 0:32:54.680 --> 0:32:57.760 can do some comparisons with the others. But first, before 0:32:57.760 --> 0:32:59.480 we did the comparisons, I wanted to talk a little 0:32:59.520 --> 0:33:02.720 bit about some controversy that popped up. So there are 0:33:02.720 --> 0:33:06.080 these things, these terms of service agreements that you know, 0:33:06.280 --> 0:33:10.600 standard across the web, and sometimes people read them, and 0:33:10.680 --> 0:33:14.600 when they do read them, sometimes they say, hey, that 0:33:14.720 --> 0:33:18.680 doesn't sound quite right. Um. So one of the problems 0:33:18.680 --> 0:33:20.320 that came up are not even a problem. One of 0:33:20.320 --> 0:33:22.360 the one of the questions that popped up all had 0:33:22.400 --> 0:33:24.960 to do with part of the Google Drive terms of service, 0:33:24.960 --> 0:33:28.320 which said that anyone who would upload or submit content 0:33:28.360 --> 0:33:32.440 to Google Drive would grant Google and I quote a 0:33:32.560 --> 0:33:38.760 worldwide license to use, host, store, reproduce, modify, create derivative 0:33:38.760 --> 0:33:42.040 works such as those resulting from translations, adaptations, or other 0:33:42.120 --> 0:33:44.040 changes we make so that your content works better with 0:33:44.040 --> 0:33:49.000 our services, communicate, published publicly, perform publicly, display, and distribute 0:33:49.040 --> 0:33:53.720 such content end quote, which gave some people the fear 0:33:54.240 --> 0:33:57.120 that perhaps what Google was saying is if you upload 0:33:57.200 --> 0:34:00.239 your content to our service, we can do whatever we 0:34:00.320 --> 0:34:05.400 want to it. Now. In truth, that's not what Google meant. No, 0:34:05.560 --> 0:34:08.120 and this is common. I actually found an article on 0:34:08.280 --> 0:34:10.760 c net where they had taken the terms of service 0:34:10.840 --> 0:34:15.560 from basically everybody, the major players in the cloud storage business, 0:34:16.000 --> 0:34:18.799 and there are clauses similar to that in many of them. 0:34:18.800 --> 0:34:24.000 And what they're basically saying is, um, you're giving us, Okay, 0:34:24.040 --> 0:34:25.680 you put the you put the file on the server. 0:34:26.440 --> 0:34:28.880 What they're saying is, you're going to allow us to 0:34:29.120 --> 0:34:32.640 make a thumbnail, a derivative work. You'll you'll let us 0:34:32.680 --> 0:34:34.520 capture the first page and make it small so you 0:34:34.560 --> 0:34:37.000 can see what it looks like. They they have you 0:34:37.040 --> 0:34:39.880 have to give them some of these rights to allow 0:34:39.920 --> 0:34:42.920 you to access it from other computers, right to share 0:34:42.920 --> 0:34:47.120 it with other collaborators with exactly. And that's what I 0:34:47.160 --> 0:34:49.560 think they were trying to accomplish. But the way it 0:34:49.680 --> 0:34:53.160 was worded freaked people right out right now, And when 0:34:53.160 --> 0:34:57.279 you think about a little bit you realize without this permission, 0:34:57.480 --> 0:35:00.040 Google drive would not work. Yeah, because you put it 0:35:00.040 --> 0:35:03.520 there and you couldn't get it back Google would Google 0:35:03.520 --> 0:35:06.080 wouldn't have the permission to display it in a way 0:35:06.120 --> 0:35:08.560 that would be useful to you. So, for example, let's 0:35:08.600 --> 0:35:10.680 go with the collaboration thing. Here's here's an example. And 0:35:10.680 --> 0:35:13.239 I think it was c net that wrote this example. Um, 0:35:13.600 --> 0:35:16.200 I want to say it was it was Google. I 0:35:16.239 --> 0:35:21.439 think that actually said here's here's what the h here's 0:35:21.440 --> 0:35:23.719 a use case scenario that will explain it. But I 0:35:23.760 --> 0:35:26.359 think it was seen that that reported it said. All right, 0:35:26.400 --> 0:35:31.400 so imagine that you are collaborating with a screenwriter in China, 0:35:32.280 --> 0:35:37.520 and the screenwriter is writing in Chinese characters and you 0:35:37.600 --> 0:35:41.320 don't read Chinese. So when you open up the file, 0:35:41.520 --> 0:35:45.200 Google Translate translates the document from Chinese into English so 0:35:45.239 --> 0:35:47.160 that you can read it and it's in a format 0:35:47.200 --> 0:35:51.560 that that makes sense to you. Well, those that's changing 0:35:51.600 --> 0:35:54.520 that work, it's adapting it in the form of translating it. 0:35:54.960 --> 0:35:57.839 And so this permission gives Google the rights to do 0:35:57.880 --> 0:36:00.600 that so that that document is actually used full to you. 0:36:01.040 --> 0:36:04.480 It's not Google says they're not planning on doing anything 0:36:04.520 --> 0:36:08.279 like taking your work that you have uploaded, changing it 0:36:08.320 --> 0:36:11.120 around and then selling it somewhere. That's that's not the 0:36:11.160 --> 0:36:13.680 purpose of this language. The purpose is just so that 0:36:13.760 --> 0:36:17.759 the features within Google Drive are legal because you have 0:36:17.920 --> 0:36:21.080 permitted Google to do it. Yeah, or or using it 0:36:21.120 --> 0:36:24.279 in ads. Now. I've seen some people say that they 0:36:24.320 --> 0:36:28.120 have seen their stuff being used in ads that are 0:36:28.160 --> 0:36:32.239 being shown to them, um, but that whether it goes 0:36:32.320 --> 0:36:35.319 beyond those people, I haven't heard anything about that, So 0:36:35.440 --> 0:36:40.240 I'm not certain exactly how accurate that is, um, because 0:36:40.280 --> 0:36:42.360 you know, they do collect quite a bit of information 0:36:42.400 --> 0:36:45.640 on you, and they really probably wouldn't need to look 0:36:45.680 --> 0:36:48.600 at your documents to be able to target advertising to 0:36:48.680 --> 0:36:51.120 you and your interests. Yeah, I mean, it's also it's 0:36:51.160 --> 0:36:54.640 also important that you know that these permissions also allow 0:36:54.680 --> 0:36:57.560 Google to do things like scan all your documents so 0:36:57.600 --> 0:37:00.279 that if you need to search them, they can turn 0:37:00.360 --> 0:37:03.719 results on those searches. Otherwise, again, you wouldn't be able 0:37:03.719 --> 0:37:06.520 to search anything. You would just have to go through 0:37:06.560 --> 0:37:09.719 all that huge pile of files and find what you needed. Again, 0:37:09.760 --> 0:37:12.239 it's useful, it's a useful feature, but in order to 0:37:12.239 --> 0:37:15.480 do that, you have to grant them those those those commissions. Yeah, 0:37:15.520 --> 0:37:18.239 because if you don't then uh then legally Google would 0:37:18.280 --> 0:37:22.640 be unable to provide that, at least not without breaking 0:37:22.680 --> 0:37:25.320 the law. We've got a little bit more about Google 0:37:25.400 --> 0:37:27.480 Drive to cover, but before we get there, let's take 0:37:27.520 --> 0:37:37.600 another quick break to thank our sponsor. I think in 0:37:37.640 --> 0:37:39.920 the last day or so, the tempers have cooled, but 0:37:40.040 --> 0:37:43.359 people are still saying, well, okay, fine, but the way 0:37:43.440 --> 0:37:47.040 it's written is very broad, and it could be allowed, 0:37:47.640 --> 0:37:51.320 It could allow opening the door to doing these things. 0:37:51.600 --> 0:37:54.600 So they're saying that Google was a little reckless is 0:37:54.640 --> 0:37:57.799 probably a strong word, but they were a little uh 0:37:58.800 --> 0:38:02.960 vague in terms, and and it does grant them those 0:38:02.960 --> 0:38:06.439 permissions where they could theoretically do that. But again, these 0:38:06.560 --> 0:38:09.120 terms are very similar to the ones used by just 0:38:09.200 --> 0:38:13.480 about everybody else out there. I remember almost identical story 0:38:13.719 --> 0:38:16.040 from a couple of years ago, and I can't remember 0:38:16.080 --> 0:38:19.960 what the company was. It might have even been Google again, 0:38:20.440 --> 0:38:24.680 but I remember distinctly that there was a discussion about 0:38:24.760 --> 0:38:27.360 this sort of thing and how people were worried that 0:38:27.400 --> 0:38:30.919 they were handing their rights over to another company, when 0:38:30.960 --> 0:38:33.160 in truth, what was going on was just like this. 0:38:33.280 --> 0:38:35.480 It was it was the permissions were there so that 0:38:35.960 --> 0:38:39.080 the service could display the work and the way it 0:38:39.160 --> 0:38:42.799 needed to be displayed for it to be useful and 0:38:42.960 --> 0:38:45.880 uh and so ultimately it just boiled down to know, 0:38:45.960 --> 0:38:48.760 we're not selling your stuff. We just need this permission 0:38:48.960 --> 0:38:52.600 or else there's no service. We we literally cannot do 0:38:52.719 --> 0:38:54.680 what we need to do for us to be useful. 0:38:55.400 --> 0:38:59.680 So um yeah, no need to panic, although it's always 0:38:59.680 --> 0:39:02.000 good to question just in case. I mean, you know, 0:39:02.160 --> 0:39:06.280 Google does still have that that motto of don't be evil, 0:39:06.760 --> 0:39:10.600 but you never know well or evil is kind of 0:39:10.640 --> 0:39:14.799 an interesting thing that itself is not entirely uh like 0:39:14.920 --> 0:39:18.040 one one man's definition of evil may be different from another's. 0:39:18.200 --> 0:39:22.120 And I've heard it clarified, um prime that that was 0:39:22.360 --> 0:39:27.840 really intended to mean, don't manipulate search results to facilitate advertising, 0:39:27.840 --> 0:39:31.279 and it was specifically geared towards that, So you know, 0:39:31.440 --> 0:39:33.640 keep your eyes it's always going to keep your eyes open. Yeah, No, 0:39:33.680 --> 0:39:36.480 it's it's always important to question. That's not what we meant. 0:39:36.760 --> 0:39:39.600 So let's go on to talking a little bit about 0:39:39.760 --> 0:39:43.840 how Google drives stacks up against other cloud storage services. 0:39:43.920 --> 0:39:47.240 So with the free storage with five gigabytes free storage, 0:39:47.480 --> 0:39:50.800 that puts it on the same playing ground as services 0:39:50.840 --> 0:39:53.399 like Box and Sugar Sinc. Both of those offer five 0:39:53.440 --> 0:39:56.680 gigs as well. Dropbox is a little less, is two gigabytes, 0:39:56.719 --> 0:39:59.080 but again, if you start referring other people and they 0:39:59.160 --> 0:40:02.960 joined the service, you get five megabytes per referral up 0:40:02.960 --> 0:40:06.760 to a maximum sixteen gigs, So you could in theory 0:40:06.960 --> 0:40:09.800 have way more storage for free on Dropbox than you 0:40:09.800 --> 0:40:13.319 would on these other services. Microsoft sky Drive is at 0:40:13.440 --> 0:40:17.760 seven gigabytes, but people who had sky Drive accounts previous 0:40:17.800 --> 0:40:24.719 to Google Drives Launch can have up to gigabytes for free. Yes, 0:40:24.920 --> 0:40:27.319 but that offer is being made for a limited time, 0:40:27.480 --> 0:40:29.480 so if you had that and you want to keep that, 0:40:29.560 --> 0:40:32.479 you might want to go quickly over there too. In fact, 0:40:32.480 --> 0:40:35.120 by the time this podcast publishes, there may very well 0:40:35.160 --> 0:40:38.120 be late, too late, very um so in that case 0:40:38.440 --> 0:40:44.719 we're sorry anyway. The the minimum upgrade, so the smallest 0:40:44.760 --> 0:40:47.480 step that you can make from free to a paid 0:40:47.560 --> 0:40:51.960 service is uh as a little different depending on the 0:40:51.960 --> 0:40:54.640 the service. So for Google Drive it's two dollars and 0:40:54.680 --> 0:40:59.320 forty nine cents per month for gigs of storage. For 0:40:59.320 --> 0:41:02.400 for drop Box, you get the lowest step is fifty 0:41:02.440 --> 0:41:05.480 gigabytes of storage for nine dollars and ninety nine cents 0:41:05.600 --> 0:41:09.360 a month, So if you're breaking it down per gig, 0:41:09.400 --> 0:41:14.680 then Google Drive is cheaper, although you get less storage. Uh. 0:41:14.960 --> 0:41:18.719 Box is twenty five gigabytes, so same amount as Google Drive, 0:41:19.000 --> 0:41:21.560 same amount storage, but for nine dollars nine nine cents 0:41:21.560 --> 0:41:25.160 a month, so it's more expensive. Sugar Sink is thirty 0:41:25.200 --> 0:41:28.400 gigabytes of storage for four dollars and ninety nine cents 0:41:28.520 --> 0:41:32.600 a month, so uh, it's you get you get five 0:41:32.640 --> 0:41:36.319 gigabytes more storage, but it's um it's essentially twice the 0:41:36.360 --> 0:41:41.360 price of Google Drive. And then um sky Drive is 0:41:41.360 --> 0:41:45.360 twenty gigabytes for ten dollars a year, which is actually, uh, 0:41:46.040 --> 0:41:49.240 it's a little less storage than Google Drive. But Google 0:41:49.280 --> 0:41:51.440 Drive at tot nine a month, you multiply that by 0:41:51.440 --> 0:41:54.480 twelve months, then you're like, oh well, Microsoft sky Drive 0:41:54.480 --> 0:41:57.920 in away is a little cheaper. Um. So that's how 0:41:57.960 --> 0:42:00.279 those stack up. And also the maximum file size limit 0:42:00.440 --> 0:42:03.880 Google Drive blows the others out of the water, except 0:42:03.880 --> 0:42:06.080 for Sugar Sink, which does not technically have a file 0:42:06.120 --> 0:42:10.239 size limit, but the but box is limit is a 0:42:10.320 --> 0:42:14.560 hundred megabytes, so that's that's not too big. Drop Box 0:42:14.680 --> 0:42:17.239 and sky Drive both have a limit of two gigabytes 0:42:17.320 --> 0:42:23.160 for a file size. UH. The UH, Sugar Sinc, drop Box, 0:42:23.200 --> 0:42:26.360 sky Drive, and Google Drive are all compatible both with 0:42:26.440 --> 0:42:33.920 Windows and Mac. Box is a business enterprise UM service, 0:42:34.120 --> 0:42:36.680 so primarily I mean you can you can get one 0:42:36.719 --> 0:42:41.320 if you want one. Uh. All of them have iPhone apps, 0:42:41.320 --> 0:42:45.120 except for Google Drive right now, but Google drives working 0:42:45.160 --> 0:42:49.040 on it. Uh. The only one that doesn't have an 0:42:49.080 --> 0:42:51.240 Android app out of the of the ones I've listed 0:42:51.280 --> 0:42:55.320 is sky Drive, Microsoft SkyDrive. Everything else has an Android 0:42:55.360 --> 0:42:59.760 app already out on the market. Windows Phone, well, here's 0:42:59.760 --> 0:43:02.479 a dock. Microsoft sky Drive has a Windows Phone app, 0:43:03.239 --> 0:43:09.200 but Google Drive doesn't, Dropbox doesn't, Box doesn't. Sugar Sinks 0:43:09.280 --> 0:43:11.719 is supposedly coming out, so maybe by the time this 0:43:11.760 --> 0:43:14.759 podcast because Live Sugar Sink will have THEIRS. UM. They 0:43:14.800 --> 0:43:18.040 all are. They all have web access, so you can 0:43:18.080 --> 0:43:20.799 access the service over the web, So even if your 0:43:21.000 --> 0:43:24.360 device does not have an application that is native to 0:43:24.360 --> 0:43:26.600 that device, you can still get there over the web, 0:43:27.680 --> 0:43:30.080 assuming you have a browser. UH. And all of them 0:43:30.080 --> 0:43:33.040 allow for public file sharing, so that you can actually 0:43:33.160 --> 0:43:36.600 let other folks see what's in your drive or see 0:43:36.719 --> 0:43:40.520 specific files that you have, you know, enabled public sharing. 0:43:41.080 --> 0:43:43.200 You can also do private file sharing with all of them, 0:43:43.480 --> 0:43:45.239 so that if you want to have just a group 0:43:45.280 --> 0:43:47.480 of collaborators, let's say you're all working on a project 0:43:47.480 --> 0:43:50.160 together and you want to be able to look at 0:43:50.200 --> 0:43:54.200 everyone else's UM information on a particular file, you can 0:43:54.239 --> 0:43:57.320 do that, and then the public itself would be shielded. 0:43:57.360 --> 0:44:00.680 They would not be able to see that UM and 0:44:00.840 --> 0:44:04.680 most of them offer some sort of collaborative document editing, 0:44:04.719 --> 0:44:09.359 although you might have to use proprietary apps in order 0:44:09.400 --> 0:44:11.800 to do it. Drop Bucks does not, it's more of 0:44:11.880 --> 0:44:15.120 a storage feature than collaboration. Sugar Sinc. Also doesn't, but 0:44:15.280 --> 0:44:18.759 sky Drive, Box and Google Drive all do UM. And 0:44:18.800 --> 0:44:23.960 then there are a couple of other UH features like 0:44:24.000 --> 0:44:28.480 the third party apps UM integration. That's that's pretty much 0:44:28.520 --> 0:44:31.480 standard across the board. Sky Drive is specifically going to 0:44:31.560 --> 0:44:35.640 be for Windows eight apps, so but others are you know, 0:44:36.120 --> 0:44:39.280 pretty much unfettered. So that's kind of how it boils 0:44:39.280 --> 0:44:42.960 down to the other major cloud services that are out there, 0:44:42.960 --> 0:44:45.279 and there's there's more than that. That's just that's just 0:44:45.360 --> 0:44:50.200 a handful of them. Oh yeah, I've I've got different 0:44:51.280 --> 0:44:55.640 applications for several of them, including UH A Bunto one, 0:44:55.880 --> 0:44:59.160 which is offered by Canonical primarily for Linux users. And 0:44:59.520 --> 0:45:01.080 you know, there are there are others out there they're 0:45:01.120 --> 0:45:04.560 trying UM and people have a question whether or not 0:45:04.600 --> 0:45:07.520 these services are going to continue into the future. UM. 0:45:07.560 --> 0:45:10.680 I think Google Drive may end up being a model 0:45:10.760 --> 0:45:14.319 for what's going to be happening. Google Drive and sky 0:45:14.440 --> 0:45:20.680 Drive basically are you know, sort of hybrids of online collaboration, 0:45:20.760 --> 0:45:25.080 software and storage. UM. So the pure storage players like 0:45:25.160 --> 0:45:28.719 Dropbox and Sugar Sink may have a difficult time competing 0:45:28.719 --> 0:45:32.120 with them in the future, especially since they're owned by uh, 0:45:32.160 --> 0:45:35.920 you know, sky Driving and um Google Driver are you know, 0:45:36.040 --> 0:45:38.879 big players, and they've got a whole lot of money 0:45:38.920 --> 0:45:43.080 to throw at these these um different applications, so you know, 0:45:43.280 --> 0:45:47.759 creating larger and larger file storage for free, offering those 0:45:47.800 --> 0:45:51.000 services for free. Um. You know, it may not be 0:45:51.120 --> 0:45:53.760 very long at all before Google and Microsoft are offering 0:45:53.840 --> 0:45:58.120 you ten gigabytes UM or you know, or more than that. 0:45:58.440 --> 0:46:00.520 And of course, you know, Apple is doing something very 0:46:00.520 --> 0:46:04.919 similar with the the um I work sweet too, So 0:46:05.480 --> 0:46:08.040 um it's very possible that the big players in the 0:46:08.080 --> 0:46:10.320 industry may run off with it and and the pure 0:46:10.400 --> 0:46:13.719 storage guys sort of followed by the wayside. I would 0:46:13.760 --> 0:46:17.040 say that is a very very real possibility, but probably 0:46:17.080 --> 0:46:19.600 not for another year or two at least. Um, just 0:46:19.680 --> 0:46:22.439 as people decide what it is they want to do 0:46:22.800 --> 0:46:25.520 with these systems. If they end up using just storage, 0:46:25.520 --> 0:46:27.960 you know, hey, I'd rather create a document on my 0:46:28.040 --> 0:46:31.520 desktop and then share it with my collaborators on the 0:46:31.640 --> 0:46:34.520 on the drive rather than you know, us working on 0:46:34.560 --> 0:46:38.320 a document in the cloud in my web browser. I think, Um, 0:46:38.360 --> 0:46:40.960 I think the real problem for the consumer in the 0:46:41.000 --> 0:46:44.239 short term is going to be, uh, figuring out where 0:46:44.280 --> 0:46:47.400 the heck your data is if you're using multiple, um, 0:46:47.520 --> 0:46:50.359 multiple services. I do have that problem, yeah, because if 0:46:50.400 --> 0:46:54.560 you I have Dropbox and I have Google Drive, those 0:46:54.560 --> 0:46:56.759 are the only two that I'm using. I've got like 0:46:56.840 --> 0:47:00.680 six or seven. Yeah. I resisted that temptation because I 0:47:00.760 --> 0:47:03.400 knew what would happen. But it's the problem you have. 0:47:03.640 --> 0:47:06.640 The problem you have within one drive is multiplied when 0:47:06.640 --> 0:47:09.160 you have multiple drives. So that's like that's like you 0:47:09.280 --> 0:47:12.640 come home and you don't know what which computer has 0:47:12.719 --> 0:47:15.200 the file that you need on it. So you've got 0:47:15.200 --> 0:47:18.520 four computers in your house for some reason. Uh, like 0:47:18.719 --> 0:47:20.879 you live in my house for example. Actually I think 0:47:20.880 --> 0:47:23.000 I've got more than four, but anyway, I think i've 0:47:23.000 --> 0:47:25.640 got five. Anyway, let's say that you've got five computers 0:47:25.640 --> 0:47:27.719 at your house. Then let's they got five computers in 0:47:27.800 --> 0:47:31.480 my house, and that I have a file saved on 0:47:31.480 --> 0:47:34.520 one of those computers. Then comes the fun part of 0:47:34.840 --> 0:47:37.560 going to each computer and figuring out where it is. 0:47:37.680 --> 0:47:41.560 The same problem. If you're using multiple cloud storage services, 0:47:42.320 --> 0:47:44.799 you're gonna have to go and do search for each one. 0:47:44.840 --> 0:47:46.880 That The benefit to it is that you can at 0:47:46.920 --> 0:47:49.680 least do that search from one machine, as long as 0:47:49.719 --> 0:47:52.600 that one machine can access each of the services you're using, 0:47:52.960 --> 0:47:55.759 and if they all have web based access and you've 0:47:55.760 --> 0:47:57.760 got a web browser, then you've got that problem solved, 0:47:57.760 --> 0:48:01.160 even if it's not the most elegant solution, but still 0:48:01.160 --> 0:48:02.880 means that you have to check each one of the 0:48:02.960 --> 0:48:04.879 drives and figure out where you have it, and then 0:48:04.920 --> 0:48:07.600 you might even fall into that same trap you had 0:48:07.640 --> 0:48:10.600 before where you might have duplicate files. You might have 0:48:10.760 --> 0:48:14.160 one instance on one drive and another instance on another drive. 0:48:14.680 --> 0:48:17.439 So um yeah, that's that's gonna be a problem too, 0:48:17.480 --> 0:48:19.400 is that if you use a lot of these services, 0:48:19.440 --> 0:48:23.800 then you still have to have some sort of discipline 0:48:23.840 --> 0:48:26.160 when it comes to data management. Maybe you only use 0:48:26.280 --> 0:48:28.800 one for one particular type of file and use another 0:48:28.840 --> 0:48:30.440 for a different one. In that way, at least you 0:48:30.719 --> 0:48:35.040 reduce that confusion. Me what I think I'm gonna end 0:48:35.120 --> 0:48:37.400 up doing is I'm going to pick one, and I 0:48:37.440 --> 0:48:40.919 haven't decided which yet, although let's be honest, Google Drive 0:48:41.000 --> 0:48:44.799 is probably the lead simply because I have a lot 0:48:44.840 --> 0:48:50.000 of products that run Android, so you know, I'm kind 0:48:50.040 --> 0:48:53.400 of locked into that in ecosystem already. But I haven't 0:48:53.440 --> 0:48:56.560 completely decided yet. So let's say, you know, whichever one 0:48:56.600 --> 0:49:00.400 I decide on, I'm going to eventually move all my things, 0:49:00.960 --> 0:49:02.960 all of the things. I'm going to move all of 0:49:03.000 --> 0:49:05.719 the things into that folder, and then I'm just gonna 0:49:05.800 --> 0:49:08.360 get rid of the others, so that way I don't 0:49:08.480 --> 0:49:12.600 have that issue. And that concludes this classic episode about 0:49:12.680 --> 0:49:14.799 Google Drive. I hope you guys enjoyed it. If you 0:49:14.840 --> 0:49:18.800 have any suggestions about future topics for tech Stuff, send 0:49:18.880 --> 0:49:21.680 me an email. The address is tech Stuff at how 0:49:21.760 --> 0:49:24.839 stuff works dot com, or pop on over to our 0:49:24.880 --> 0:49:27.839 website that's tech Stuff podcast dot com. You'll find an 0:49:27.920 --> 0:49:30.759 archive of all of our older shows. You'll find links 0:49:30.800 --> 0:49:33.759 to our presence on social media. You'll find a link 0:49:33.840 --> 0:49:36.600 to our online merchandise store. Every purchase you make there 0:49:36.640 --> 0:49:40.000 goes to help the show, which we greatly appreciate. And 0:49:40.080 --> 0:49:46.960 I will talk to you again and really soon. Text 0:49:47.000 --> 0:49:49.800 Stuff is a production of I Heart Radio's How Stuff Works. 0:49:49.800 --> 0:49:52.640 For more podcasts from my heart Radio, visit the i 0:49:52.760 --> 0:49:55.960 heart Radio app, Apple Podcasts, or wherever you listen to 0:49:56.040 --> 0:49:56.960 your favorite shows.