WEBVTT - TechStuff Goes for a Google Drive

0:00:00.320 --> 0:00:02.880
<v Speaker 1>Brought to you by the reinvented two thousand twelve camera.

0:00:03.200 --> 0:00:08.960
<v Speaker 1>It's ready. Are you get in touch with technology? With

0:00:09.039 --> 0:00:17.640
<v Speaker 1>tech Stuff from how stuff works dot com. Hello everybody,

0:00:17.640 --> 0:00:20.080
<v Speaker 1>and welcome to tech stuff. My name is Chris Poulette

0:00:20.079 --> 0:00:23.040
<v Speaker 1>and I am an editor at how stuff works dot com.

0:00:23.079 --> 0:00:27.120
<v Speaker 1>Sitting across from me, as usual, is senior writer Jonathan Strickland, Mr.

0:00:27.120 --> 0:00:30.160
<v Speaker 1>And Mrs Dursley of Number four Private Drive. We're proud

0:00:30.200 --> 0:00:32.840
<v Speaker 1>to say that they were perfectly normal. Thank you very much.

0:00:33.880 --> 0:00:36.360
<v Speaker 1>You know that quote was positively magical. Thank you. I

0:00:36.479 --> 0:00:40.159
<v Speaker 1>just joined Potter Moore, so I had to. I know,

0:00:40.200 --> 0:00:45.200
<v Speaker 1>I just gave it away Chucks. So today, tech stuff fans,

0:00:45.240 --> 0:00:47.920
<v Speaker 1>we're all gonna go on a little Google Drive. Oh cool?

0:00:47.920 --> 0:00:50.400
<v Speaker 1>Are We're gonna talk about those robotic cars that don't

0:00:50.440 --> 0:00:53.000
<v Speaker 1>need drivers except you know, when they're sitting in the

0:00:53.080 --> 0:00:57.200
<v Speaker 1>seat and they watched the car where you're in somebody else. No,

0:00:57.640 --> 0:01:00.640
<v Speaker 1>that's that's not what my notes are on. I was

0:01:00.640 --> 0:01:03.960
<v Speaker 1>talking about Google Drive, you know, the cloud storage Google

0:01:04.080 --> 0:01:09.280
<v Speaker 1>Drive announced on a Well, this will be a fun podcast.

0:01:09.319 --> 0:01:11.679
<v Speaker 1>We're gonna see what our notes show. Um No, really,

0:01:11.720 --> 0:01:14.280
<v Speaker 1>we're gonna talk about Google Drive today. And the day

0:01:14.280 --> 0:01:17.200
<v Speaker 1>we're recording this podcast. Just in case you guys are curious,

0:01:17.680 --> 0:01:19.200
<v Speaker 1>I know that you'll be listening to it quite a

0:01:19.200 --> 0:01:21.520
<v Speaker 1>while afterwards because we record so early in advance. But

0:01:21.560 --> 0:01:24.840
<v Speaker 1>it's April seven, the day we're recording this, So it's

0:01:24.920 --> 0:01:29.240
<v Speaker 1>just three days after Google finally officially announced and launched

0:01:29.280 --> 0:01:31.920
<v Speaker 1>Google Drive. Right. It was sort of a one of

0:01:31.959 --> 0:01:35.080
<v Speaker 1>those closely guarded secrets like that everyone knew about, and

0:01:35.280 --> 0:01:37.440
<v Speaker 1>everyone knew about like the iPad for two years before

0:01:37.440 --> 0:01:39.479
<v Speaker 1>it was released. Right. Yeah, people have been talking about

0:01:39.520 --> 0:01:42.800
<v Speaker 1>Google having a cloud storage service for for a couple

0:01:42.800 --> 0:01:45.680
<v Speaker 1>of years now, so this was and even Google made

0:01:45.720 --> 0:01:47.720
<v Speaker 1>reference to that. But before we really get into what

0:01:47.800 --> 0:01:50.200
<v Speaker 1>Google Drive is, we should probably talk about what cloud

0:01:50.240 --> 0:01:54.440
<v Speaker 1>storage is in general and why it's important. Uh, cloud

0:01:54.480 --> 0:01:57.560
<v Speaker 1>storage is pretty it's a pretty simple concept. The idea

0:01:57.720 --> 0:02:01.800
<v Speaker 1>is that you can store data on servers in the cloud.

0:02:02.040 --> 0:02:05.680
<v Speaker 1>So you're talking about using someone else's computers to store

0:02:05.760 --> 0:02:08.799
<v Speaker 1>your information, and you can access the information over the

0:02:09.280 --> 0:02:13.960
<v Speaker 1>Internet using some sort of interface, usually web based, and

0:02:14.000 --> 0:02:16.600
<v Speaker 1>they call it the cloud, of course, because the Internet

0:02:16.680 --> 0:02:19.960
<v Speaker 1>is a nebulous group of machines and it's just sort

0:02:20.000 --> 0:02:24.080
<v Speaker 1>of out there, always changing like a cloud. So yeah, so,

0:02:24.200 --> 0:02:26.400
<v Speaker 1>and and the idea being that it's also kind of

0:02:26.400 --> 0:02:28.840
<v Speaker 1>like a cloud in the sense that you can access

0:02:28.880 --> 0:02:32.400
<v Speaker 1>it from any machine that has that Internet capability. Right,

0:02:32.800 --> 0:02:36.080
<v Speaker 1>it may require a special app depending upon the type

0:02:36.080 --> 0:02:39.480
<v Speaker 1>of cloud storage. Uh, because not everything is web based.

0:02:39.680 --> 0:02:42.440
<v Speaker 1>There are a lot of different desktop clients that you

0:02:42.440 --> 0:02:45.720
<v Speaker 1>can have that will allow you to store information to

0:02:45.960 --> 0:02:49.840
<v Speaker 1>a cloud drive. So it lives on your computer's desktop

0:02:49.919 --> 0:02:52.679
<v Speaker 1>as if it were a regular file folder. Right, So

0:02:52.919 --> 0:02:55.799
<v Speaker 1>you think of your your regular hard drive folders that

0:02:55.880 --> 0:02:58.359
<v Speaker 1>you would go into to look at various files, like

0:02:58.400 --> 0:03:00.640
<v Speaker 1>you might store all your pictures in in a pictures

0:03:00.639 --> 0:03:03.000
<v Speaker 1>folder and all your videos and a videos folder, that

0:03:03.080 --> 0:03:06.440
<v Speaker 1>kind of thing. Um, a cloud storage drive might show

0:03:06.520 --> 0:03:09.040
<v Speaker 1>up on your desktop as if it were a regular

0:03:09.080 --> 0:03:11.760
<v Speaker 1>folder on your computer, but instead of living on your computer,

0:03:12.080 --> 0:03:16.360
<v Speaker 1>the information gets sent over the Internet to a a

0:03:16.480 --> 0:03:20.919
<v Speaker 1>remote machine and it's stored on that machine. And there

0:03:21.000 --> 0:03:25.280
<v Speaker 1>is an identifier that links that particular file to you

0:03:25.400 --> 0:03:29.240
<v Speaker 1>as a user, a registered user of that service. And uh,

0:03:29.280 --> 0:03:31.239
<v Speaker 1>in fact, when I say it lives on one machine,

0:03:31.280 --> 0:03:34.960
<v Speaker 1>that's not entirely true. Almost every cloud service, in fact,

0:03:35.080 --> 0:03:39.240
<v Speaker 1>every reputable cloud service out there uses redundant measures so

0:03:39.280 --> 0:03:42.320
<v Speaker 1>that the file is on several different machines in case

0:03:42.360 --> 0:03:45.920
<v Speaker 1>one machine fails. I'm real sorry, I only had one

0:03:46.000 --> 0:03:49.000
<v Speaker 1>machine and it went down. Yeah, that would not go

0:03:49.120 --> 0:03:53.600
<v Speaker 1>over so well. Uh. Jester's cloud service, Jester's cloud service. Yea,

0:03:54.280 --> 0:03:56.640
<v Speaker 1>Sester's never really been up on that whole. I think

0:03:56.640 --> 0:03:58.520
<v Speaker 1>I need to. I think I need to register that

0:03:58.600 --> 0:04:04.680
<v Speaker 1>domain now, Chester's clouds. We gotta hair a cumula nimbus um.

0:04:04.720 --> 0:04:08.400
<v Speaker 1>So the yeah, the idea is that obviously that you

0:04:08.400 --> 0:04:12.960
<v Speaker 1>would be able to offload storage from your native device,

0:04:13.600 --> 0:04:15.760
<v Speaker 1>especially if you are one of those people who has

0:04:15.880 --> 0:04:18.120
<v Speaker 1>lots of different devices and you want to be able

0:04:18.160 --> 0:04:21.320
<v Speaker 1>to access the same information no matter which device you're using.

0:04:21.839 --> 0:04:25.160
<v Speaker 1>Because in the old days, back before a cloud storage

0:04:25.240 --> 0:04:27.200
<v Speaker 1>a couple of years ago, yeah, not that long ago,

0:04:27.720 --> 0:04:30.000
<v Speaker 1>you you only had a few different options. You could

0:04:30.040 --> 0:04:35.640
<v Speaker 1>save something to a physical medium, so a disk for example,

0:04:35.640 --> 0:04:39.160
<v Speaker 1>compact disc or a floppy disc way back in the day,

0:04:39.279 --> 0:04:41.599
<v Speaker 1>or a thumb drive something like that, and then you

0:04:41.640 --> 0:04:44.640
<v Speaker 1>could pour that over to another device, pull it up

0:04:44.720 --> 0:04:47.880
<v Speaker 1>from the physical medium, and then work on it that way,

0:04:47.960 --> 0:04:50.280
<v Speaker 1>save it back to the physical medium and then go

0:04:50.320 --> 0:04:52.279
<v Speaker 1>back and you know, it, it was a little cumbersome.

0:04:52.440 --> 0:04:54.400
<v Speaker 1>It also meant that you would often end up with

0:04:54.440 --> 0:04:58.240
<v Speaker 1>lots of duplicate copies of a particular file, and if

0:04:58.240 --> 0:05:00.360
<v Speaker 1>people made changes, then you had to figure all, right,

0:05:00.400 --> 0:05:03.280
<v Speaker 1>which one of these copies has the most recent, most

0:05:03.320 --> 0:05:05.640
<v Speaker 1>relevant changes, and then I have to get rid of

0:05:05.680 --> 0:05:08.520
<v Speaker 1>all the others or else I'm going to confuse them. All. Yeah,

0:05:08.560 --> 0:05:09.960
<v Speaker 1>you have to go through and you you end up

0:05:09.960 --> 0:05:12.960
<v Speaker 1>looking at creation dates and when things are modified. Wait,

0:05:13.000 --> 0:05:17.160
<v Speaker 1>that was done at nine, Okay, I can get rid

0:05:17.200 --> 0:05:19.080
<v Speaker 1>of that one. And it takes forever, and and it's

0:05:19.120 --> 0:05:23.120
<v Speaker 1>particularly difficult if you have more than one collaborator. Right, So,

0:05:23.160 --> 0:05:25.440
<v Speaker 1>if Chris and I were working on a document, it

0:05:25.480 --> 0:05:28.280
<v Speaker 1>would be frustrating for us to try and and we're

0:05:28.279 --> 0:05:31.840
<v Speaker 1>both working on copies of a document, we're both making changes,

0:05:32.200 --> 0:05:34.880
<v Speaker 1>be very frustrating to cohlate those changes and figure out

0:05:35.240 --> 0:05:37.480
<v Speaker 1>you know, which ones are relevant and which ones are

0:05:37.480 --> 0:05:39.880
<v Speaker 1>the most recent. Uh, and may very well be that

0:05:40.000 --> 0:05:42.839
<v Speaker 1>a change I make makes a later change that Chris

0:05:42.920 --> 0:05:48.039
<v Speaker 1>makes irrelevant. So the idea behind cloud storage is it's

0:05:48.080 --> 0:05:50.440
<v Speaker 1>not and it's not always connected, but there's a lot

0:05:50.480 --> 0:05:54.640
<v Speaker 1>of work around collaboration in cloud storage so that if

0:05:54.680 --> 0:05:57.320
<v Speaker 1>you have multiple people who need access to a particular file,

0:05:57.760 --> 0:06:02.200
<v Speaker 1>you are able to share that file across several instances,

0:06:02.760 --> 0:06:04.799
<v Speaker 1>and you might even be able to have multiple people

0:06:04.880 --> 0:06:07.240
<v Speaker 1>work on that file at the same time, and those

0:06:07.320 --> 0:06:10.159
<v Speaker 1>changes will be reflected more or less in real time

0:06:10.400 --> 0:06:12.760
<v Speaker 1>for each person. So that way, if Chris Word did

0:06:12.800 --> 0:06:15.479
<v Speaker 1>make a change to a sentence within that file, I

0:06:15.480 --> 0:06:17.800
<v Speaker 1>could actually see him making that more or less in

0:06:17.839 --> 0:06:21.480
<v Speaker 1>real time. This is particularly true with Google Service because

0:06:21.520 --> 0:06:25.520
<v Speaker 1>Google Drive has been very tightly integrated with Google Docs.

0:06:25.560 --> 0:06:28.520
<v Speaker 1>In fact, it's kind of superseded Google Docs in a way.

0:06:29.000 --> 0:06:33.719
<v Speaker 1>But other services also offer similar features. UM And just

0:06:33.800 --> 0:06:36.120
<v Speaker 1>to clear things up my my joke about a couple

0:06:36.080 --> 0:06:38.400
<v Speaker 1>of years ago, of course that the cloud is uh

0:06:38.680 --> 0:06:42.560
<v Speaker 1>much older than that. We've been using variations on cloud

0:06:42.640 --> 0:06:46.760
<v Speaker 1>services for many years now. UM. In fact, I don't

0:06:46.800 --> 0:06:50.839
<v Speaker 1>think I think it really proceeds labeling things as cloud,

0:06:51.880 --> 0:06:55.080
<v Speaker 1>which is really sort of a convenient marketing term for

0:06:55.080 --> 0:06:58.359
<v Speaker 1>for services such as these. UM it gives you it

0:06:58.560 --> 0:07:01.800
<v Speaker 1>when people mention the cloud. It it basically serves as

0:07:01.880 --> 0:07:05.600
<v Speaker 1>a a hint to say, hey, the materials or software

0:07:05.880 --> 0:07:09.120
<v Speaker 1>is being stored on servers on the Internet, not on

0:07:09.160 --> 0:07:11.679
<v Speaker 1>your computer. So it's it's sort of a short marketing

0:07:11.680 --> 0:07:14.920
<v Speaker 1>shorthand for these services. But yeah, I mean we've talked

0:07:14.920 --> 0:07:18.640
<v Speaker 1>about Google Docs many times. I mean it predates the

0:07:19.040 --> 0:07:22.280
<v Speaker 1>beginning of our podcast, so um. And there were many

0:07:22.320 --> 0:07:26.239
<v Speaker 1>services using those kinds of uh, those kinds of technologies before,

0:07:26.320 --> 0:07:29.080
<v Speaker 1>but in recent uh, in recent years, there have been

0:07:29.480 --> 0:07:34.920
<v Speaker 1>several services that take advantage of cloud storage. Specifically, um,

0:07:34.960 --> 0:07:40.240
<v Speaker 1>not simply to store the software as a service, you know,

0:07:40.440 --> 0:07:44.240
<v Speaker 1>or or the documents that you use, say in Google Docs, um,

0:07:44.280 --> 0:07:47.160
<v Speaker 1>but to upload and download your own file so that

0:07:47.200 --> 0:07:49.480
<v Speaker 1>you don't have to use a physical medium. You don't

0:07:49.480 --> 0:07:51.800
<v Speaker 1>have to worry about losing that that flash drive you

0:07:51.840 --> 0:07:54.600
<v Speaker 1>carry in your pocket or your bag. Um, you don't

0:07:54.640 --> 0:07:56.800
<v Speaker 1>have to walk a disk from one place to another

0:07:56.960 --> 0:08:00.880
<v Speaker 1>or worry about it if you want to, say, work

0:08:00.880 --> 0:08:03.040
<v Speaker 1>on a graduate school assignment on your lunch break at work.

0:08:03.200 --> 0:08:04.920
<v Speaker 1>I don't know anyone who would have done that at

0:08:04.920 --> 0:08:08.000
<v Speaker 1>how stuff works, except maybe me a couple of years ago.

0:08:08.160 --> 0:08:10.040
<v Speaker 1>Or you just happen to have like a whole bunch

0:08:10.080 --> 0:08:12.200
<v Speaker 1>of really powerful magnets nearby and you don't want to

0:08:12.240 --> 0:08:15.119
<v Speaker 1>use magnetic storage on turn it, I had my flash

0:08:15.200 --> 0:08:16.720
<v Speaker 1>drive in my pocket when I went for the m

0:08:16.840 --> 0:08:18.600
<v Speaker 1>R I I was thinking, I was thinking of the

0:08:18.640 --> 0:08:22.000
<v Speaker 1>old old floppy disk days. I actually did lose data

0:08:22.000 --> 0:08:24.840
<v Speaker 1>on a floppy disk because uh, floppy disk had a

0:08:24.880 --> 0:08:26.760
<v Speaker 1>little bit of a close encounter with a magnet and

0:08:26.800 --> 0:08:30.560
<v Speaker 1>that was enough to ruin it. Yeah. But um, yeah,

0:08:30.600 --> 0:08:35.520
<v Speaker 1>I mean these these services were being marketed specifically as

0:08:35.559 --> 0:08:39.080
<v Speaker 1>a hey, you can store stuff here, and and um,

0:08:39.200 --> 0:08:42.880
<v Speaker 1>the services in question, many of them came from from

0:08:42.960 --> 0:08:45.840
<v Speaker 1>the little guys. We're not talking about Apple or Google

0:08:45.920 --> 0:08:50.679
<v Speaker 1>or Facebook or Amazon or Microsoft. These were all independent

0:08:50.840 --> 0:08:54.080
<v Speaker 1>vendors and they would offer and they still do offer

0:08:54.280 --> 0:08:56.840
<v Speaker 1>a free tier of service for a small amount of storage,

0:08:56.840 --> 0:08:59.439
<v Speaker 1>and then you could upgrade for a certain price per

0:08:59.480 --> 0:09:01.520
<v Speaker 1>month you could get more storage, and for more than

0:09:01.559 --> 0:09:04.400
<v Speaker 1>that you get more storage. And they they basically would

0:09:04.400 --> 0:09:06.360
<v Speaker 1>work that out in businesses. If you really needed a

0:09:06.360 --> 0:09:09.240
<v Speaker 1>whole lot of cloud storage, um, you know, you could

0:09:09.240 --> 0:09:11.640
<v Speaker 1>do that. But gradually the big players have been getting

0:09:11.679 --> 0:09:14.680
<v Speaker 1>into the game. And that's why, uh, everybody has been

0:09:14.760 --> 0:09:16.640
<v Speaker 1>expecting Google to do it, because I mean, hey, if

0:09:16.640 --> 0:09:21.280
<v Speaker 1>anybody's got server storage and data centers, it's Google. Yeah.

0:09:21.280 --> 0:09:26.240
<v Speaker 1>It turns out that storage is relatively inexpensive, so very

0:09:26.320 --> 0:09:28.760
<v Speaker 1>very inexpensive over the last few years, right, So, so

0:09:28.920 --> 0:09:32.000
<v Speaker 1>for a business to enter into that and just purchase

0:09:32.120 --> 0:09:36.640
<v Speaker 1>a lot of different servers specifically to save information from

0:09:36.640 --> 0:09:40.880
<v Speaker 1>from users, Uh, it's not as big a barrier as

0:09:41.000 --> 0:09:44.640
<v Speaker 1>some other forms of internet based businesses. However, it does

0:09:44.679 --> 0:09:46.760
<v Speaker 1>mean that you have to create these systems in place

0:09:46.800 --> 0:09:49.080
<v Speaker 1>for things like security. You need to have you know,

0:09:49.240 --> 0:09:54.640
<v Speaker 1>the important things for cloud computing involved security accessibility. So

0:09:54.679 --> 0:09:56.960
<v Speaker 1>you want to make sure that whatever your system is,

0:09:57.240 --> 0:10:00.640
<v Speaker 1>it's easy to access on multiple platforms. So that means

0:10:01.040 --> 0:10:06.480
<v Speaker 1>you want people to be able to access it via PC, mac, smartphone, tablet,

0:10:06.880 --> 0:10:09.400
<v Speaker 1>lots of different devices can connect to the Internet now,

0:10:10.400 --> 0:10:12.880
<v Speaker 1>so you want to be able to give your users

0:10:12.920 --> 0:10:15.640
<v Speaker 1>the freedom to be able to access the information over

0:10:15.679 --> 0:10:18.760
<v Speaker 1>as many of platforms as possible. You know, the more

0:10:18.800 --> 0:10:21.800
<v Speaker 1>convenient your services, the more valuable it is to the customer.

0:10:22.400 --> 0:10:27.040
<v Speaker 1>So so security and accessibility and uh, just that that

0:10:27.120 --> 0:10:31.079
<v Speaker 1>whole accessibility slash convenience and just the whole idea of

0:10:31.120 --> 0:10:34.839
<v Speaker 1>giving a certain tier for free so that you you

0:10:35.240 --> 0:10:39.640
<v Speaker 1>show people how valuable the services now and and we

0:10:39.640 --> 0:10:44.240
<v Speaker 1>should clear this up. Cloud storage is not necessarily all

0:10:44.280 --> 0:10:47.200
<v Speaker 1>about backing up your data. Although people have used it

0:10:47.240 --> 0:10:52.000
<v Speaker 1>for that kind of purpose, it's really more about, well,

0:10:52.160 --> 0:10:55.760
<v Speaker 1>there's certain documents or certain files that you may want

0:10:55.880 --> 0:10:58.120
<v Speaker 1>to have stored in the cloud because you want to

0:10:58.160 --> 0:11:01.040
<v Speaker 1>have easy access across multiple devices. You may want to

0:11:01.040 --> 0:11:03.960
<v Speaker 1>share that with other people, and it's a lot easier

0:11:03.960 --> 0:11:06.600
<v Speaker 1>to do that when it's on a web based drive

0:11:06.760 --> 0:11:09.240
<v Speaker 1>than it would be on your own computers. So let's

0:11:09.280 --> 0:11:11.520
<v Speaker 1>say that I've shot a video and I've got this

0:11:11.640 --> 0:11:15.120
<v Speaker 1>video living on my computer, emailing that video out to

0:11:15.559 --> 0:11:18.800
<v Speaker 1>all the different people I want to see it. Uh,

0:11:18.960 --> 0:11:21.200
<v Speaker 1>maybe I don't want to upload it to something like YouTube.

0:11:21.320 --> 0:11:23.679
<v Speaker 1>Maybe I just want to send that directly to a

0:11:23.720 --> 0:11:26.720
<v Speaker 1>few people. Well, for example, what if you were trying

0:11:26.760 --> 0:11:29.120
<v Speaker 1>to preview a video with the people you were working

0:11:29.280 --> 0:11:31.439
<v Speaker 1>collaborating with it on, right, exactly, you're not ready to

0:11:31.480 --> 0:11:33.840
<v Speaker 1>make a public yeah exactly. Yeah, you might need to

0:11:33.880 --> 0:11:36.240
<v Speaker 1>still do some edits. You may you may just be

0:11:36.360 --> 0:11:39.920
<v Speaker 1>looking at this with your friends and say just just

0:11:39.960 --> 0:11:42.839
<v Speaker 1>doesn't feel snappy enough. Do you have any suggestions? So

0:11:43.040 --> 0:11:45.280
<v Speaker 1>in that case, yeah, you wouldn't want to necessarily uploaded

0:11:45.280 --> 0:11:47.560
<v Speaker 1>to YouTube. I mean you could upload YouTube and make

0:11:47.600 --> 0:11:50.080
<v Speaker 1>it private and then send out the link. But but

0:11:50.320 --> 0:11:52.560
<v Speaker 1>if you just would rather skip that step and and

0:11:52.600 --> 0:11:55.880
<v Speaker 1>just keep it in pre production mode, UM, then a

0:11:55.920 --> 0:11:58.480
<v Speaker 1>cloud drive would be very useful. You could send out,

0:11:58.679 --> 0:12:01.199
<v Speaker 1>you could share the link to that file within your

0:12:01.200 --> 0:12:03.760
<v Speaker 1>cloud drive, and then other people could go to your

0:12:03.760 --> 0:12:07.040
<v Speaker 1>cloud drive and view that one particular file without having

0:12:07.120 --> 0:12:10.160
<v Speaker 1>access to anything else that's in your cloud drive. So

0:12:10.200 --> 0:12:13.560
<v Speaker 1>all they would get is access to whatever file you

0:12:13.960 --> 0:12:16.920
<v Speaker 1>permitted them access to. Now, you might be able to

0:12:17.040 --> 0:12:20.760
<v Speaker 1>set some permissions on files so that they are publicly available,

0:12:21.000 --> 0:12:24.480
<v Speaker 1>which means that anyone who could visit your drive would

0:12:24.480 --> 0:12:28.160
<v Speaker 1>be able to see that particular file, But in most cases,

0:12:28.200 --> 0:12:31.000
<v Speaker 1>I think people just have special permissions for particular folks.

0:12:31.200 --> 0:12:32.719
<v Speaker 1>And then and of course you can always say that

0:12:32.800 --> 0:12:35.640
<v Speaker 1>where only you have access to it, there's no need

0:12:35.720 --> 0:12:38.839
<v Speaker 1>to you know, you're not forced to collaborate, right. So

0:12:39.559 --> 0:12:41.839
<v Speaker 1>those are the that's the basics around cloud drives. And

0:12:42.040 --> 0:12:44.480
<v Speaker 1>one of the reasons why I think cloud drives are

0:12:44.520 --> 0:12:47.840
<v Speaker 1>getting more important is that you're starting to see, right

0:12:47.880 --> 0:12:50.360
<v Speaker 1>about the time we're recording this podcast, in particular, you're

0:12:50.400 --> 0:12:54.120
<v Speaker 1>starting to see some some devices come out besides ones

0:12:54.200 --> 0:12:57.160
<v Speaker 1>that come from a company company that rhymes with Shmapple

0:12:57.679 --> 0:13:02.600
<v Speaker 1>that that don't have expand memory as a feature. So

0:13:02.600 --> 0:13:04.480
<v Speaker 1>so in other words, there's no slot for you to

0:13:04.520 --> 0:13:07.520
<v Speaker 1>put a memory card into. Well, we've already talked about

0:13:07.840 --> 0:13:11.520
<v Speaker 1>ultra books, um, which don't have in general, don't have

0:13:11.559 --> 0:13:15.040
<v Speaker 1>optical drives. You know they they save space, save energy

0:13:15.360 --> 0:13:17.920
<v Speaker 1>um by not having that. And you know where you

0:13:17.960 --> 0:13:20.800
<v Speaker 1>have a limited amount of storage on board. So you

0:13:20.840 --> 0:13:23.600
<v Speaker 1>could use something like a flash drive or a portable

0:13:23.640 --> 0:13:26.880
<v Speaker 1>drive where you have a connection, um, but you you

0:13:26.960 --> 0:13:30.120
<v Speaker 1>do need something to store files on otherwise you know

0:13:30.160 --> 0:13:32.000
<v Speaker 1>you're really not going to be able to create stuff. Well,

0:13:32.280 --> 0:13:36.480
<v Speaker 1>although granted most ultra books probably have significantly more storage

0:13:36.520 --> 0:13:39.120
<v Speaker 1>on board than your typical at least you're free tier

0:13:39.240 --> 0:13:42.440
<v Speaker 1>of cloud storage out there. Oh yes, definitely. But things

0:13:42.440 --> 0:13:44.840
<v Speaker 1>like smartphones, I mean, here's an example. I'll give a

0:13:44.840 --> 0:13:48.400
<v Speaker 1>real world example because again this is a recording this

0:13:48.520 --> 0:13:51.760
<v Speaker 1>and this phone was just announced on T Mobile was

0:13:51.800 --> 0:13:56.200
<v Speaker 1>the HTC one S. It's an Android based phone running

0:13:56.200 --> 0:14:00.920
<v Speaker 1>ice Cream Sandwich. It has sixteen gigabytes on board memory. Alright,

0:14:00.960 --> 0:14:04.200
<v Speaker 1>sixteen gigs on board memory, No flash drive, no, no

0:14:04.280 --> 0:14:06.920
<v Speaker 1>smart card drive at all, So you can't add more

0:14:07.000 --> 0:14:10.160
<v Speaker 1>memory to it. That sixteen gigs is all you get. However,

0:14:11.000 --> 0:14:15.160
<v Speaker 1>ht C one S also comes with a trial period

0:14:15.480 --> 0:14:19.160
<v Speaker 1>with Dropbox, which is another cloud based storage system, and

0:14:19.200 --> 0:14:21.280
<v Speaker 1>we'll talk more about Dropbox a little bit later in

0:14:21.320 --> 0:14:25.120
<v Speaker 1>this podcast. So in this case, you're talking about a

0:14:25.200 --> 0:14:29.800
<v Speaker 1>smart phone that is encouraging you to use cloud based

0:14:29.840 --> 0:14:33.680
<v Speaker 1>storage rather than some sort of physical media. So that

0:14:33.720 --> 0:14:36.360
<v Speaker 1>way you have this this your information is backed up

0:14:36.360 --> 0:14:39.600
<v Speaker 1>into the cloud, and theoretically when you are ready to

0:14:40.040 --> 0:14:42.600
<v Speaker 1>upgrade your phone or switch phones, or maybe you lose

0:14:42.640 --> 0:14:44.200
<v Speaker 1>your phone you have to get a new phone, you

0:14:44.200 --> 0:14:46.920
<v Speaker 1>would still have access to that information because it exists

0:14:46.960 --> 0:14:49.440
<v Speaker 1>on the cloud, not on a physical device in your hand.

0:14:49.760 --> 0:14:51.560
<v Speaker 1>I mean it's it's on a physical device, it's just

0:14:51.600 --> 0:14:56.160
<v Speaker 1>that physical device belongs to some other company. So that's

0:14:56.200 --> 0:14:57.920
<v Speaker 1>one of the other reasons why cloud storch is so

0:14:57.960 --> 0:15:01.360
<v Speaker 1>important is that we're starting to see manufacturers kind of

0:15:01.360 --> 0:15:06.360
<v Speaker 1>offload features onto the cloud so that they don't include

0:15:06.400 --> 0:15:08.880
<v Speaker 1>them in the phone itself. It helps a little bit

0:15:08.920 --> 0:15:12.080
<v Speaker 1>with phone design because it means that you don't need

0:15:12.160 --> 0:15:14.960
<v Speaker 1>to build in that feature. You can actually make your

0:15:15.000 --> 0:15:18.200
<v Speaker 1>phones slimmer and sleeker. I mean, Apple has been doing

0:15:18.200 --> 0:15:21.240
<v Speaker 1>this for ages, but other companies are starting to do

0:15:21.320 --> 0:15:24.920
<v Speaker 1>the same sort of thing. Now, that's enough about cloud

0:15:24.920 --> 0:15:27.520
<v Speaker 1>storage in general, I think, unless is there anything else

0:15:27.520 --> 0:15:29.840
<v Speaker 1>that we need to talk about. There was one other

0:15:29.880 --> 0:15:31.800
<v Speaker 1>thing I didn't want to uh to pass over it

0:15:31.880 --> 0:15:35.080
<v Speaker 1>too much is UM. And this is something we've visited

0:15:35.080 --> 0:15:38.720
<v Speaker 1>several times too, is the aspect of privacy. UM. You know,

0:15:38.800 --> 0:15:41.000
<v Speaker 1>a couple of years ago when we were talking about

0:15:41.040 --> 0:15:43.400
<v Speaker 1>this UM, you know, when it was starting to become

0:15:43.560 --> 0:15:46.240
<v Speaker 1>a public topic. You know, hey, what is cloud storage?

0:15:46.280 --> 0:15:49.920
<v Speaker 1>What it was cloud computing? UM. You know, people didn't

0:15:49.920 --> 0:15:51.880
<v Speaker 1>really get that, and then when you explain it, they'd

0:15:51.880 --> 0:15:54.600
<v Speaker 1>start thinking about the documents that you would store up

0:15:54.640 --> 0:15:57.880
<v Speaker 1>there and privacy what if somebody hacks in UM. I

0:15:57.920 --> 0:16:01.400
<v Speaker 1>think it's obvious at this point that the convenience, UM

0:16:01.600 --> 0:16:05.680
<v Speaker 1>and accessibility of cloud storage has made it we were

0:16:05.840 --> 0:16:07.760
<v Speaker 1>We've gone so far now that I don't think we're

0:16:07.760 --> 0:16:11.120
<v Speaker 1>going to go back UM. But it's obviously. I just

0:16:11.200 --> 0:16:14.400
<v Speaker 1>think it's interesting to note that at this point we

0:16:14.440 --> 0:16:16.480
<v Speaker 1>are you know, there are things that we look at,

0:16:16.520 --> 0:16:20.560
<v Speaker 1>you know, whether this this particular company is more likely

0:16:20.640 --> 0:16:24.040
<v Speaker 1>to have good security and privacy than the other company.

0:16:24.080 --> 0:16:28.760
<v Speaker 1>But um, yeah, that's it's the security of these cloud

0:16:28.960 --> 0:16:35.040
<v Speaker 1>storage uh services has become sort of a given. Oh well,

0:16:35.080 --> 0:16:37.200
<v Speaker 1>you know, if they're going to offer this, they better

0:16:37.240 --> 0:16:40.040
<v Speaker 1>be offering security because I'm going to use the service

0:16:40.120 --> 0:16:42.760
<v Speaker 1>and you know, that's something I look for before I

0:16:42.800 --> 0:16:45.480
<v Speaker 1>do that, so that that doesn't even seem that seems

0:16:45.480 --> 0:16:47.680
<v Speaker 1>like a given now when before people are going I

0:16:47.720 --> 0:16:50.400
<v Speaker 1>don't know if I want to do this or not. Yeah,

0:16:50.440 --> 0:16:52.720
<v Speaker 1>we can talk a little bit about Google's approach to

0:16:53.560 --> 0:16:56.240
<v Speaker 1>privacy and security. In fact, we will have to because

0:16:56.280 --> 0:16:58.760
<v Speaker 1>there is a controversy that we we will have to address.

0:16:59.120 --> 0:17:01.160
<v Speaker 1>But before we do that, let's get into the basics

0:17:01.240 --> 0:17:04.840
<v Speaker 1>of Google Drive. So it is built directly into Google Docs. Now,

0:17:04.880 --> 0:17:07.119
<v Speaker 1>so Google Docs the if you were to open up

0:17:07.119 --> 0:17:09.520
<v Speaker 1>a Google Docs account, so which is just your regular

0:17:09.560 --> 0:17:11.560
<v Speaker 1>Google account, that's what it's attached to. So if you

0:17:11.560 --> 0:17:14.800
<v Speaker 1>have a Google account, congratulations, you have a Google Docs account.

0:17:15.240 --> 0:17:17.520
<v Speaker 1>You can go to Google Docs and create a document,

0:17:17.680 --> 0:17:21.240
<v Speaker 1>whether that's a word document, word being, word processing document

0:17:21.280 --> 0:17:23.600
<v Speaker 1>not where it is in Microsoft word, but a word

0:17:23.640 --> 0:17:28.200
<v Speaker 1>processing document, presentation, spreadsheet, you know, all the basic types

0:17:28.240 --> 0:17:33.199
<v Speaker 1>of office documents. Google has the those as features. If

0:17:33.200 --> 0:17:34.920
<v Speaker 1>you were to create one and save it, it would

0:17:34.920 --> 0:17:37.960
<v Speaker 1>save it into your Google Drive account and you would

0:17:38.160 --> 0:17:43.320
<v Speaker 1>automatically get the the base free tier, which for Google

0:17:43.400 --> 0:17:47.160
<v Speaker 1>Drive is five gigabytes of free storage. And the nice

0:17:47.200 --> 0:17:49.840
<v Speaker 1>thing about this is that that doesn't count any of

0:17:49.880 --> 0:17:53.280
<v Speaker 1>the documents in your Google Docs, so it doesn't know

0:17:53.480 --> 0:17:56.000
<v Speaker 1>I didn't know that. That's interesting. That's good to know,

0:17:56.480 --> 0:17:59.800
<v Speaker 1>uh the now. What you can also do is you

0:17:59.840 --> 0:18:03.439
<v Speaker 1>can download a client onto your desktop that allows you

0:18:03.480 --> 0:18:07.720
<v Speaker 1>to drag and drop files from your computer into your

0:18:07.760 --> 0:18:11.040
<v Speaker 1>Google Drive so that you can easily port over. If

0:18:11.080 --> 0:18:15.159
<v Speaker 1>you've got, say, uh, photo album on your computer, and

0:18:15.200 --> 0:18:17.200
<v Speaker 1>you like the photo album and you want to keep it,

0:18:17.240 --> 0:18:19.600
<v Speaker 1>but you don't really want it taking up space on

0:18:19.680 --> 0:18:23.320
<v Speaker 1>your local hard drive, you could copy it, or not

0:18:23.359 --> 0:18:25.960
<v Speaker 1>copy it, but move it over to your Google Drive

0:18:26.080 --> 0:18:28.000
<v Speaker 1>and it would store there. It would have you have

0:18:28.080 --> 0:18:30.879
<v Speaker 1>a folder within your Google Drive where you could access that,

0:18:30.880 --> 0:18:34.200
<v Speaker 1>and you could access it with any web connected device.

0:18:34.880 --> 0:18:38.000
<v Speaker 1>That at least any web connected device, either through the

0:18:38.000 --> 0:18:41.640
<v Speaker 1>the web system or depending on the device, you might

0:18:41.680 --> 0:18:44.560
<v Speaker 1>have a dedicated app that would let you access it.

0:18:45.400 --> 0:18:47.359
<v Speaker 1>So for example, Google Drive, you can do that on

0:18:47.520 --> 0:18:49.960
<v Speaker 1>PCs and max uh, and you can do it on

0:18:50.000 --> 0:18:54.080
<v Speaker 1>Android phones and they're working on but at the recording

0:18:54.080 --> 0:18:57.200
<v Speaker 1>of this podcast, they were working on an iOS app

0:18:57.680 --> 0:18:59.720
<v Speaker 1>so that you would be able to access it easily

0:18:59.800 --> 0:19:04.760
<v Speaker 1>through your iPhone or iPod Touch or iPad. And they

0:19:04.800 --> 0:19:07.600
<v Speaker 1>also from what I understand, I did see an article

0:19:08.040 --> 0:19:10.720
<v Speaker 1>on a Linux website the other day that was quite

0:19:10.840 --> 0:19:14.840
<v Speaker 1>upset that there was not compatibility built in for Linux

0:19:14.880 --> 0:19:18.200
<v Speaker 1>as in as in a and a dedicated application. From

0:19:18.200 --> 0:19:21.480
<v Speaker 1>what I understand, they're working well too. Um. Of course,

0:19:21.680 --> 0:19:24.280
<v Speaker 1>you know, if you're using Linux now and and you've

0:19:24.280 --> 0:19:27.479
<v Speaker 1>probably already tried to use your your Drive with it.

0:19:27.560 --> 0:19:30.320
<v Speaker 1>If you're you know, a Google customer, um, you can

0:19:30.480 --> 0:19:33.880
<v Speaker 1>of course use the web version. Um. But but they're

0:19:33.880 --> 0:19:36.159
<v Speaker 1>working on a dedicated app. From what I understand, that's

0:19:36.280 --> 0:19:39.720
<v Speaker 1>that's the nice thing. Yeah, even if your your device

0:19:39.720 --> 0:19:42.120
<v Speaker 1>doesn't have a dedicated app, you can still access Google

0:19:42.200 --> 0:19:44.639
<v Speaker 1>Drive through the web portion like you open up a

0:19:44.680 --> 0:19:46.760
<v Speaker 1>browser and you can go to Google Drive that way.

0:19:46.880 --> 0:19:49.399
<v Speaker 1>It's not quite as convenient, it's not as user friendly.

0:19:50.080 --> 0:19:53.119
<v Speaker 1>Uh So, I mean that's why everyone wants the app,

0:19:53.560 --> 0:19:56.440
<v Speaker 1>because then you know, you bypass that step of having

0:19:56.480 --> 0:19:58.679
<v Speaker 1>to go through the web. It's just like having an

0:19:58.680 --> 0:20:02.280
<v Speaker 1>app on your phone access a web based email client

0:20:02.440 --> 0:20:04.159
<v Speaker 1>so that you don't actually have to open up a

0:20:04.200 --> 0:20:07.159
<v Speaker 1>browser and navigate to the email. You just open up

0:20:07.160 --> 0:20:10.520
<v Speaker 1>the app and there you are, same sort of thing. Well,

0:20:10.560 --> 0:20:15.159
<v Speaker 1>there's some other interesting aspects that are unique to to

0:20:15.320 --> 0:20:18.760
<v Speaker 1>the Google Clown Drive because there's you know, like we said,

0:20:18.760 --> 0:20:20.919
<v Speaker 1>there are a lot of different companies out there that

0:20:21.000 --> 0:20:24.320
<v Speaker 1>offer comparable services, but they don't all have the same

0:20:24.359 --> 0:20:27.399
<v Speaker 1>feature set. One of the things that sets Google apart

0:20:27.640 --> 0:20:31.840
<v Speaker 1>is no surprise search. So let's say that you have

0:20:32.160 --> 0:20:34.399
<v Speaker 1>a lot of files in your Google Drive. Let's say

0:20:34.440 --> 0:20:36.399
<v Speaker 1>let's say that you are one of the people who, uh,

0:20:36.560 --> 0:20:39.080
<v Speaker 1>you're you've got to upgrade your account because you've got

0:20:39.080 --> 0:20:41.399
<v Speaker 1>a lot of data, and you've got lots of different

0:20:41.440 --> 0:20:45.240
<v Speaker 1>kinds of files. You've got picture files, videos, text documents,

0:20:45.280 --> 0:20:49.800
<v Speaker 1>all that kind of stuff, and scanned documents so maybe

0:20:50.000 --> 0:20:52.679
<v Speaker 1>PDFs or other forms of scanned documents. You have it

0:20:52.720 --> 0:20:55.600
<v Speaker 1>all in your Google Drive, and then one day you

0:20:55.640 --> 0:20:58.720
<v Speaker 1>need a specific file and for the life that you

0:20:58.800 --> 0:21:01.960
<v Speaker 1>can't remember why folder you saved it in, and you've

0:21:02.000 --> 0:21:04.000
<v Speaker 1>got so many folders in this drive. It's going to

0:21:04.080 --> 0:21:06.679
<v Speaker 1>take you forever to find it. This is something that

0:21:06.720 --> 0:21:12.240
<v Speaker 1>does not happen on an infrequent basis at Shase Strickland Um,

0:21:12.280 --> 0:21:15.480
<v Speaker 1>because I am very very good at filing things away safely,

0:21:15.720 --> 0:21:19.639
<v Speaker 1>so safely I will never find them again. So Google

0:21:19.720 --> 0:21:23.240
<v Speaker 1>Search is built into Google Drive, and they have gone

0:21:23.280 --> 0:21:28.520
<v Speaker 1>so far as to start developing recognition software so that

0:21:28.680 --> 0:21:30.919
<v Speaker 1>let's say that you've scanned in a lot of documents.

0:21:31.040 --> 0:21:35.880
<v Speaker 1>Maybe you've got some old documents that are important to you,

0:21:36.119 --> 0:21:40.040
<v Speaker 1>perhaps they're old family journals, and you've scanned the pictures

0:21:40.040 --> 0:21:43.200
<v Speaker 1>and you put them into your Google Drive, and you think,

0:21:43.520 --> 0:21:47.280
<v Speaker 1>there's this great document that my grandfather wrote that is

0:21:47.359 --> 0:21:49.840
<v Speaker 1>pertinent to this blog post i'm posting. It would be

0:21:49.880 --> 0:21:53.600
<v Speaker 1>awesome if I if I posted a picture of that page,

0:21:54.080 --> 0:21:57.280
<v Speaker 1>but gosh, I can't remember where I saved it. Well,

0:21:57.400 --> 0:22:02.119
<v Speaker 1>the image recognition software, it actually can scan the scanned

0:22:02.160 --> 0:22:05.000
<v Speaker 1>documents and look for text. So if you type in

0:22:05.200 --> 0:22:08.880
<v Speaker 1>and um string like you know that your your grandfather

0:22:08.960 --> 0:22:12.240
<v Speaker 1>wrote about I'll give a real life example. Let's say

0:22:12.240 --> 0:22:17.760
<v Speaker 1>my grandfather wrote about a massive tornado that completely devastated Gainesville, Georgia,

0:22:18.440 --> 0:22:21.040
<v Speaker 1>which is true, really did happen? My grandfather was in

0:22:21.080 --> 0:22:22.919
<v Speaker 1>a working in a mill at a time, and it

0:22:23.080 --> 0:22:25.199
<v Speaker 1>ripped the roof off the mill. My grandfather was very

0:22:25.240 --> 0:22:28.520
<v Speaker 1>lucky to get out. Um. So let's say that he

0:22:28.560 --> 0:22:31.840
<v Speaker 1>wrote this great article about it, and I had scanned

0:22:31.840 --> 0:22:34.959
<v Speaker 1>it in I could type in Gainesville, Tornado in my

0:22:35.000 --> 0:22:39.000
<v Speaker 1>Google uh search for for the Google Drive, and it's

0:22:39.000 --> 0:22:43.160
<v Speaker 1>going to actually look and scan the the physical documents,

0:22:43.200 --> 0:22:46.879
<v Speaker 1>the ones that are just image files really and return

0:22:46.960 --> 0:22:49.479
<v Speaker 1>those as well, which is kind of cool. It's not

0:22:49.600 --> 0:22:53.280
<v Speaker 1>just scanning the text in your documents and scanning the images.

0:22:54.000 --> 0:22:58.200
<v Speaker 1>They're also working on adding in the image recognition software

0:22:58.200 --> 0:23:00.280
<v Speaker 1>that you can find it in in pro. It's like

0:23:00.280 --> 0:23:03.920
<v Speaker 1>Google Goggles. So with Google Goggles, you can hold up

0:23:04.320 --> 0:23:07.920
<v Speaker 1>a smartphone with a camera to a particular kind of

0:23:08.640 --> 0:23:12.320
<v Speaker 1>uh objects sometimes like a landmark or whatever, and Google

0:23:12.320 --> 0:23:15.679
<v Speaker 1>Goggles will use recognition software to try and identify what

0:23:15.880 --> 0:23:18.320
<v Speaker 1>that is. Same sort of thing. Let's say that you've

0:23:18.320 --> 0:23:21.679
<v Speaker 1>taken a bunch of pictures of the Washington Monument and

0:23:21.720 --> 0:23:23.840
<v Speaker 1>then you think, oh, there's this great picture of the

0:23:23.840 --> 0:23:26.000
<v Speaker 1>Washington Monument I want to use, and I don't remember

0:23:26.040 --> 0:23:28.880
<v Speaker 1>where I put it. You can search Washington Monument and

0:23:28.960 --> 0:23:33.400
<v Speaker 1>that image recognition software will include any images that Google

0:23:33.480 --> 0:23:37.600
<v Speaker 1>identifies as the Washington Monument, uh and pulls it back

0:23:37.640 --> 0:23:40.359
<v Speaker 1>even if you didn't title the picture that, So the

0:23:40.560 --> 0:23:42.520
<v Speaker 1>picture could be titled something different. It couldn't just have

0:23:42.640 --> 0:23:45.879
<v Speaker 1>the date or some random string of letters and numbers.

0:23:46.720 --> 0:23:49.879
<v Speaker 1>But because that image recognition software is part of Google Search,

0:23:50.600 --> 0:23:53.159
<v Speaker 1>it can pull that up as well, which is a

0:23:53.160 --> 0:23:56.239
<v Speaker 1>really powerful tool. Now, Google does stress that both the

0:23:56.280 --> 0:24:00.840
<v Speaker 1>image recognition software and the the scanning of of scanned

0:24:00.840 --> 0:24:05.360
<v Speaker 1>files software both of that those technologies are in their

0:24:05.359 --> 0:24:10.000
<v Speaker 1>early phases and may not work flawlessly. So uh, you know,

0:24:10.080 --> 0:24:13.000
<v Speaker 1>mileage may vary essentially is what comes out of that.

0:24:13.119 --> 0:24:15.760
<v Speaker 1>But that that is a differentiator is that you've got

0:24:15.760 --> 0:24:18.800
<v Speaker 1>this amazing search tool. It turns out Google knows a

0:24:18.880 --> 0:24:21.880
<v Speaker 1>thing or two about search. They've picked up a couple

0:24:21.880 --> 0:24:24.720
<v Speaker 1>of tricks that that's really cool. They needed to work

0:24:24.720 --> 0:24:27.240
<v Speaker 1>on that. Yeah, no, they've they've got some good some

0:24:27.280 --> 0:24:30.000
<v Speaker 1>good work there, and then they're also working there's there's

0:24:30.000 --> 0:24:33.600
<v Speaker 1>all the collaborative features that you would get with Google Docs.

0:24:33.640 --> 0:24:37.880
<v Speaker 1>So that's included with Google Drive. So assuming that people, uh,

0:24:38.200 --> 0:24:41.120
<v Speaker 1>you know that you give access to certain files to people,

0:24:41.400 --> 0:24:44.760
<v Speaker 1>they should be able to make edits and everything they're

0:24:44.760 --> 0:24:49.000
<v Speaker 1>working on, including some other features as well. They've actually

0:24:49.000 --> 0:24:52.400
<v Speaker 1>opened up the platform and they've created an API for

0:24:52.400 --> 0:24:56.240
<v Speaker 1>for companies to add in their own features, so extensions

0:24:56.240 --> 0:24:58.840
<v Speaker 1>and things. So you might be vocation programming interface. Yes,

0:24:59.640 --> 0:25:01.719
<v Speaker 1>so you might be able eventually to do things like

0:25:01.800 --> 0:25:04.920
<v Speaker 1>send facts from your Google Drive to a fax machine

0:25:05.480 --> 0:25:10.080
<v Speaker 1>or to actually have edit videos within your Google Drive itself,

0:25:10.280 --> 0:25:12.840
<v Speaker 1>so you're not just letting people view a video, but

0:25:12.920 --> 0:25:17.399
<v Speaker 1>perhaps even edit videos within the drive using this third

0:25:17.440 --> 0:25:23.520
<v Speaker 1>party application. But they're the the possibilities are nearly endless. Yeah,

0:25:23.720 --> 0:25:25.840
<v Speaker 1>as a matter of fact, they they have already made

0:25:26.000 --> 0:25:30.159
<v Speaker 1>partnerships with some of these companies that that Jonathan is

0:25:30.200 --> 0:25:34.600
<v Speaker 1>alluding to UM for the launch of Google Drive and

0:25:34.920 --> 0:25:37.200
<v Speaker 1>you can go. You can actually find it pretty easily

0:25:37.200 --> 0:25:39.080
<v Speaker 1>when you go into your Google account that they have

0:25:39.200 --> 0:25:41.680
<v Speaker 1>these uh, these applications that are ready to take advantage

0:25:41.680 --> 0:25:44.159
<v Speaker 1>of this um it. As a matter of fact, UM

0:25:44.200 --> 0:25:48.440
<v Speaker 1>there is ah some of them have UM special deals.

0:25:48.480 --> 0:25:51.040
<v Speaker 1>Now that that's kind of important to note. Uh, just

0:25:51.040 --> 0:25:55.560
<v Speaker 1>just quickly that these third party companies are probably still

0:25:55.560 --> 0:25:58.840
<v Speaker 1>going to charge you for their services. UM. So you know,

0:25:58.880 --> 0:26:03.240
<v Speaker 1>it's not necessarily free, but it does work very very easily,

0:26:03.320 --> 0:26:06.560
<v Speaker 1>and it is uh you know, synchronized with Google Drive,

0:26:06.640 --> 0:26:09.440
<v Speaker 1>so it makes it very easy to do one from

0:26:09.480 --> 0:26:13.280
<v Speaker 1>the other. Now your mileage may vary again again. Yeah,

0:26:13.520 --> 0:26:15.800
<v Speaker 1>so let's talk a little bit about the tears that

0:26:16.280 --> 0:26:20.840
<v Speaker 1>the Google offers. No more tears. That's my AUSSI Osborne

0:26:20.840 --> 0:26:23.719
<v Speaker 1>reference for the day. Um, Actually it's probably not. I'm

0:26:23.720 --> 0:26:26.360
<v Speaker 1>sure I'll get a crazy train in there somewhere man,

0:26:26.680 --> 0:26:30.159
<v Speaker 1>or maybe war pigs. Maybe. I'm not sure how you're

0:26:30.160 --> 0:26:33.639
<v Speaker 1>going to get that one. Maybe iron Man. I mean, look,

0:26:34.040 --> 0:26:36.879
<v Speaker 1>I can force a reference if I have to. It

0:26:36.960 --> 0:26:41.080
<v Speaker 1>would be the first time anyway. So the tears that

0:26:41.280 --> 0:26:45.200
<v Speaker 1>Google offers, so you've got five gigabytes of free storage. Actually,

0:26:45.520 --> 0:26:48.920
<v Speaker 1>let's back that up. Okay, Google makes its money, well

0:26:48.960 --> 0:26:52.520
<v Speaker 1>just a little bit deep. Google makes its money from advertising. Yes,

0:26:52.600 --> 0:26:55.440
<v Speaker 1>that's true. Google is an advertising company when you get

0:26:55.440 --> 0:26:59.440
<v Speaker 1>downe to it, or at least they they run advertising, right,

0:26:59.600 --> 0:27:02.280
<v Speaker 1>So let's let's let's kind of take one step back

0:27:02.320 --> 0:27:05.920
<v Speaker 1>and look at Google services. Okay, Google Docs, the previous

0:27:05.960 --> 0:27:12.159
<v Speaker 1>Google docs free. Gmail that's free, uh searches free to

0:27:12.240 --> 0:27:15.960
<v Speaker 1>the user. Um. Android is free for people to uh

0:27:16.000 --> 0:27:20.199
<v Speaker 1>to install on cell phones. Um, all this stuff is

0:27:20.680 --> 0:27:24.600
<v Speaker 1>offered more or less free to the consumer. This is

0:27:24.600 --> 0:27:28.040
<v Speaker 1>one of the big changes because Google's competitors in this

0:27:28.119 --> 0:27:33.360
<v Speaker 1>space people like uh that Jonathan mentioned before, dropbox, Box

0:27:33.600 --> 0:27:37.680
<v Speaker 1>formerly boxed, dot Net, Sugar Sinc. Sky Drive, sky Drive,

0:27:37.720 --> 0:27:41.920
<v Speaker 1>which is Microsoft's um application for this. These guys all

0:27:42.000 --> 0:27:46.920
<v Speaker 1>offer tears. There's an initial free smaller space, and then

0:27:46.960 --> 0:27:50.119
<v Speaker 1>they are are tiered pricing, so you get uh, you know,

0:27:50.240 --> 0:27:54.160
<v Speaker 1>small for free, you get medium for a few dollars

0:27:54.200 --> 0:27:56.480
<v Speaker 1>a month, you get large for a few more dollars

0:27:56.480 --> 0:27:59.960
<v Speaker 1>a month, etcetera, etcetera. So this is new. Google has

0:28:00.000 --> 0:28:02.440
<v Speaker 1>haven't done this with other products. Really, I can't think

0:28:02.480 --> 0:28:06.280
<v Speaker 1>of one, uh where it offers tiered pricing like this.

0:28:06.480 --> 0:28:11.119
<v Speaker 1>You know, nothing's popping the mind immediately. I mean, you

0:28:11.160 --> 0:28:13.560
<v Speaker 1>could make some arguments about Google Voice, but that's a

0:28:13.560 --> 0:28:17.840
<v Speaker 1>little different. That's a little different. Um yeah, so that's yeah,

0:28:17.920 --> 0:28:20.520
<v Speaker 1>it is is something to make a call on Google

0:28:20.600 --> 0:28:24.840
<v Speaker 1>Voice normally, like over the phone. In general, it's free. Now. Grant,

0:28:24.960 --> 0:28:26.720
<v Speaker 1>what Google could have done is they could have offered

0:28:26.760 --> 0:28:28.720
<v Speaker 1>the five gigabytes free storage and that would have been it.

0:28:29.560 --> 0:28:33.000
<v Speaker 1>But see for Google to offer huge amounts of storage

0:28:33.040 --> 0:28:35.960
<v Speaker 1>for free would be well pretty soon Google, that would

0:28:35.960 --> 0:28:39.320
<v Speaker 1>be eating into Google's revenue. So it's understandable why they

0:28:39.320 --> 0:28:42.280
<v Speaker 1>did what they did. Um and and really when we

0:28:42.320 --> 0:28:45.560
<v Speaker 1>get into the comparisons, you'll see it's fairly comparable to

0:28:45.720 --> 0:28:48.840
<v Speaker 1>the other services. Some offer less space for free, some

0:28:48.920 --> 0:28:52.440
<v Speaker 1>offer more. But Dropbox, for example, is I would say,

0:28:52.480 --> 0:28:55.880
<v Speaker 1>the for what it's worth, the eight pound gorilla, and

0:28:55.960 --> 0:28:58.640
<v Speaker 1>yet that offers two gig and starts at two gigabytes

0:28:59.160 --> 0:29:01.440
<v Speaker 1>for our friends to feel for friends, you get five

0:29:01.520 --> 0:29:05.880
<v Speaker 1>hundred megabytes per referral and uh up to sixteen gigabytes

0:29:05.960 --> 0:29:09.240
<v Speaker 1>extra storage, so you could have up to eighteen gigabytes

0:29:09.240 --> 0:29:11.920
<v Speaker 1>for free if you referred that many friends to drop Box.

0:29:13.200 --> 0:29:17.000
<v Speaker 1>Yeah so uh but but getting back to it, the

0:29:17.080 --> 0:29:20.400
<v Speaker 1>five gigabytes is free for any user. So if you

0:29:20.760 --> 0:29:22.960
<v Speaker 1>have a Google account and you have five gigs free

0:29:22.960 --> 0:29:27.840
<v Speaker 1>storage online right now, uh, if that's enough, then for

0:29:27.960 --> 0:29:31.080
<v Speaker 1>about two dollars, and this is all at launch, I

0:29:31.120 --> 0:29:33.440
<v Speaker 1>should say, because if you're listening to this podcast in

0:29:36.040 --> 0:29:39.640
<v Speaker 1>I'm sure the prices may be different, but for twenty

0:29:39.640 --> 0:29:41.440
<v Speaker 1>for two dollars and forty nine cents a month, you

0:29:41.440 --> 0:29:45.000
<v Speaker 1>can get twenty five gigabytes of storage. For four dollars

0:29:45.000 --> 0:29:47.200
<v Speaker 1>and ninety nine cents a month, you get a hundred

0:29:47.200 --> 0:29:50.600
<v Speaker 1>gigabytes of storage. And if you're really really data hungry,

0:29:50.680 --> 0:29:53.960
<v Speaker 1>for a cool forty nine nine nine a month for

0:29:54.160 --> 0:29:56.800
<v Speaker 1>nine dollars nine cents, you can get a terrabyte of

0:29:56.880 --> 0:30:01.800
<v Speaker 1>storage online. So uh so, yeah, for people who need

0:30:02.240 --> 0:30:04.800
<v Speaker 1>way more space. Let's say that you're that you do

0:30:04.840 --> 0:30:07.840
<v Speaker 1>a lot of video editing, that you do a lot

0:30:07.880 --> 0:30:10.560
<v Speaker 1>of a collaboration with other people with videos, and you

0:30:10.600 --> 0:30:13.880
<v Speaker 1>want to have that ability for people to all look

0:30:13.880 --> 0:30:18.080
<v Speaker 1>at it without it going live in any other way. Um,

0:30:18.160 --> 0:30:23.080
<v Speaker 1>this would be pretty useful. And uh again it's it's

0:30:23.120 --> 0:30:27.600
<v Speaker 1>kind of comparable to what other companies offer. Uh some

0:30:27.720 --> 0:30:35.080
<v Speaker 1>of them don't have um as high amount of storage

0:30:35.120 --> 0:30:37.400
<v Speaker 1>that actually, none of them offer as much storage as

0:30:37.400 --> 0:30:40.880
<v Speaker 1>Google Drive does at its highest tier. The highest tier

0:30:40.880 --> 0:30:45.640
<v Speaker 1>that Google Drive offers is sixteen terabytes of storage, which

0:30:45.680 --> 0:30:50.840
<v Speaker 1>is for sevens a month. Yeah, well, I would say

0:30:50.840 --> 0:30:54.800
<v Speaker 1>that some of them I've seen essentially say hey, if

0:30:54.800 --> 0:30:56.600
<v Speaker 1>you need if you really need more storage in this,

0:30:56.880 --> 0:31:00.000
<v Speaker 1>give us a call and we'll work something out. Um.

0:31:00.080 --> 0:31:03.520
<v Speaker 1>But yeah, and and there are there are a few things. Um,

0:31:03.640 --> 0:31:07.160
<v Speaker 1>one you know this isn't completely new, because Google Docs

0:31:07.160 --> 0:31:11.440
<v Speaker 1>has allowed you to upload files like word Microsoft Word

0:31:11.440 --> 0:31:14.600
<v Speaker 1>documents for a little while now. But this is this

0:31:14.640 --> 0:31:18.560
<v Speaker 1>is basically the formal, uh, the formal announcement that hey,

0:31:18.640 --> 0:31:20.800
<v Speaker 1>we are going to offer you a certain amount of storage,

0:31:20.800 --> 0:31:23.080
<v Speaker 1>and this is how much it costs. So it's really

0:31:23.080 --> 0:31:27.200
<v Speaker 1>a delineation of all of that. Um. Yeah, the maximum

0:31:27.240 --> 0:31:30.240
<v Speaker 1>file size that you can upload to a Google Drive

0:31:30.520 --> 0:31:33.680
<v Speaker 1>as assuming that you have that much space as ten gigabytes,

0:31:34.280 --> 0:31:37.160
<v Speaker 1>um and uh, which is one of the larger actually,

0:31:37.200 --> 0:31:39.800
<v Speaker 1>I think that's the largest file size. Among the the

0:31:39.840 --> 0:31:44.880
<v Speaker 1>consumer cloud storage, there's enterprise cloud storage. To Amazon offers

0:31:45.560 --> 0:31:48.640
<v Speaker 1>enterprise level cloud storage. That's a different animal. Well, in

0:31:48.680 --> 0:31:49.960
<v Speaker 1>a way it is, and in a way it isn't,

0:31:50.000 --> 0:31:52.920
<v Speaker 1>because some of the other cloud services are using Amazon

0:31:53.040 --> 0:31:55.760
<v Speaker 1>as their right story. So in some cases you are

0:31:55.840 --> 0:31:59.840
<v Speaker 1>using Amazon Cloud Storage, you're just using it through another company.

0:32:00.400 --> 0:32:03.280
<v Speaker 1>But yeah, we can genius business model right there. We

0:32:03.280 --> 0:32:06.360
<v Speaker 1>can do some comparisons with the others. But first, before

0:32:06.400 --> 0:32:08.120
<v Speaker 1>we did the comparisons, I wanted to talk a little

0:32:08.160 --> 0:32:11.320
<v Speaker 1>bit about some controversy that popped up. So there are

0:32:11.360 --> 0:32:14.719
<v Speaker 1>these things, these terms of service agreements that you know,

0:32:14.880 --> 0:32:19.239
<v Speaker 1>standard across the web, and sometimes people read them, and

0:32:19.320 --> 0:32:23.280
<v Speaker 1>when they do read them, sometimes they say, hey, that

0:32:23.360 --> 0:32:27.280
<v Speaker 1>doesn't sound quite right. Um, So one of the problems

0:32:27.280 --> 0:32:28.920
<v Speaker 1>that came up are not even a problem. One of

0:32:28.960 --> 0:32:31.000
<v Speaker 1>the one of the questions that popped up all had

0:32:31.040 --> 0:32:33.600
<v Speaker 1>to do with part of the Google Drive terms of service,

0:32:33.600 --> 0:32:36.960
<v Speaker 1>which said that anyone who would upload or submit content

0:32:37.000 --> 0:32:41.080
<v Speaker 1>to Google Drive would grant Google and I quote, a

0:32:41.160 --> 0:32:47.360
<v Speaker 1>worldwide license to use, host, store, reproduce, modify, create, derivative

0:32:47.400 --> 0:32:50.680
<v Speaker 1>works such as those resulting from translations, adaptations, or other

0:32:50.760 --> 0:32:52.640
<v Speaker 1>changes we make so that your content works better with

0:32:52.680 --> 0:32:57.640
<v Speaker 1>our services, communicate, published, publicly, perform, publicly, display, and distribute

0:32:57.640 --> 0:33:02.360
<v Speaker 1>such content end quote, which gave some people the fear

0:33:02.880 --> 0:33:05.720
<v Speaker 1>that perhaps what Google was saying is if you upload

0:33:05.840 --> 0:33:08.840
<v Speaker 1>your content to our service, we can do whatever we

0:33:08.920 --> 0:33:14.000
<v Speaker 1>want to it now. In truth, that's not what Google meant. No,

0:33:14.200 --> 0:33:16.760
<v Speaker 1>and this is common. I actually found an article on

0:33:16.920 --> 0:33:19.400
<v Speaker 1>c net where they had taken the terms of service

0:33:19.440 --> 0:33:24.200
<v Speaker 1>from basically everybody the major players in the cloud storage business,

0:33:24.600 --> 0:33:27.440
<v Speaker 1>and there are clauses similar to that in many of them,

0:33:27.440 --> 0:33:32.640
<v Speaker 1>and what they're basically saying is, um, you're giving us, Okay,

0:33:32.640 --> 0:33:34.280
<v Speaker 1>you put the you put the file on the server.

0:33:35.040 --> 0:33:37.520
<v Speaker 1>What they're saying is, you're going to allow us to

0:33:37.760 --> 0:33:41.280
<v Speaker 1>make a thumbnail, a derivative work. You'll you'll let us

0:33:41.320 --> 0:33:43.160
<v Speaker 1>capture the first page and make it small so you

0:33:43.160 --> 0:33:45.640
<v Speaker 1>can see what it looks like. They they have you

0:33:45.640 --> 0:33:48.480
<v Speaker 1>have to give them some of these rights to allow

0:33:48.560 --> 0:33:51.520
<v Speaker 1>you to access it from other computers, right to share

0:33:51.560 --> 0:33:55.560
<v Speaker 1>it with other collaborators with exactly. And and that's what

0:33:55.600 --> 0:33:58.040
<v Speaker 1>I think they were trying to accomplish. But the way

0:33:58.040 --> 0:34:02.120
<v Speaker 1>it was worded freaked right now. And when you think

0:34:02.160 --> 0:34:05.920
<v Speaker 1>about a little bit, you realize, Uh, without this permission,

0:34:06.120 --> 0:34:10.000
<v Speaker 1>Google drive would not work because there and you couldn't

0:34:10.239 --> 0:34:12.719
<v Speaker 1>get it back because Google wouldn't. Google wouldn't have the

0:34:12.760 --> 0:34:15.160
<v Speaker 1>permission to display it in a way that would be

0:34:15.200 --> 0:34:17.520
<v Speaker 1>useful to you. So, for example, let's go with the

0:34:17.520 --> 0:34:19.600
<v Speaker 1>collaboration thing. Here's here's an example. And I think it

0:34:19.680 --> 0:34:22.560
<v Speaker 1>was c net that wrote this example. Um, I want

0:34:22.560 --> 0:34:25.360
<v Speaker 1>to say it was it was Google. I think that

0:34:25.440 --> 0:34:30.399
<v Speaker 1>actually said here's here's what the uh, here's a use

0:34:30.440 --> 0:34:32.600
<v Speaker 1>case scenario that will explain it. But I think it

0:34:32.640 --> 0:34:35.080
<v Speaker 1>was seen at that reported it said, all right, so

0:34:35.080 --> 0:34:40.040
<v Speaker 1>imagine that you are collaborating with a screenwriter in China,

0:34:40.920 --> 0:34:46.120
<v Speaker 1>and the screenwriter is writing in Chinese characters, and you

0:34:46.239 --> 0:34:49.960
<v Speaker 1>don't read Chinese. So when you open up the file,

0:34:50.160 --> 0:34:53.799
<v Speaker 1>Google Translate translates the document from Chinese into English so

0:34:53.880 --> 0:34:55.760
<v Speaker 1>that you can read it and it's in a format

0:34:55.800 --> 0:34:59.879
<v Speaker 1>that that makes sense to you. Well, those that's chain

0:35:00.040 --> 0:35:02.319
<v Speaker 1>gene that work. It's adapting it in the form of

0:35:02.320 --> 0:35:06.120
<v Speaker 1>translating it. And so this permission gives Google the rights

0:35:06.160 --> 0:35:08.840
<v Speaker 1>to do that so that that document is actually useful

0:35:08.880 --> 0:35:12.400
<v Speaker 1>to you. It's not. Google says they're not planning on

0:35:12.480 --> 0:35:16.040
<v Speaker 1>doing anything like taking your work that you have uploaded,

0:35:16.440 --> 0:35:19.399
<v Speaker 1>changing it around and then selling it somewhere. That's that's

0:35:19.440 --> 0:35:21.839
<v Speaker 1>not the purpose of this language. The purpose is just

0:35:21.960 --> 0:35:26.120
<v Speaker 1>so that the features within Google Drive are legal because

0:35:26.160 --> 0:35:29.319
<v Speaker 1>you have permitted Google to do it. Yeah, or or

0:35:29.400 --> 0:35:32.120
<v Speaker 1>using it in ads. Now, I've seen some people say

0:35:32.160 --> 0:35:36.240
<v Speaker 1>that they have seen their stuff being used in ads

0:35:36.239 --> 0:35:40.399
<v Speaker 1>that are being shown to them, um, but that whether

0:35:40.480 --> 0:35:43.399
<v Speaker 1>it goes beyond those people, I haven't heard anything about that,

0:35:43.880 --> 0:35:48.480
<v Speaker 1>So I'm not certain exactly how accurate that is, um,

0:35:48.520 --> 0:35:50.400
<v Speaker 1>Because you know, they do collect quite a bit of

0:35:50.440 --> 0:35:54.000
<v Speaker 1>information on you, and they really probably wouldn't need to

0:35:54.080 --> 0:35:57.120
<v Speaker 1>look at your documents to be able to target advertising

0:35:57.160 --> 0:35:59.040
<v Speaker 1>to you and your interests. Yeah, I mean it's also

0:35:59.560 --> 0:36:02.800
<v Speaker 1>it's also so important that you know that these permissions

0:36:02.800 --> 0:36:05.640
<v Speaker 1>also allow Google to do things like scan all your

0:36:05.680 --> 0:36:07.960
<v Speaker 1>documents so that if you need to search them, that

0:36:08.200 --> 0:36:11.719
<v Speaker 1>they can return results on those searches. Otherwise, again, you

0:36:11.719 --> 0:36:13.600
<v Speaker 1>wouldn't be able to search anything. You would just have

0:36:13.680 --> 0:36:16.960
<v Speaker 1>to go through all that huge pile of files and

0:36:17.000 --> 0:36:20.120
<v Speaker 1>find what you needed. Again, it's useful, it's a useful feature.

0:36:20.200 --> 0:36:21.720
<v Speaker 1>But in order to do that, you have to grant

0:36:21.760 --> 0:36:25.120
<v Speaker 1>them those those those permissions. Yeah, because if you don't then,

0:36:25.280 --> 0:36:29.719
<v Speaker 1>uh then legally Google would be unable to provide that,

0:36:29.880 --> 0:36:32.360
<v Speaker 1>at least not without breaking the law. Right. And of

0:36:32.400 --> 0:36:34.959
<v Speaker 1>course this is all happening this week. It launched this week.

0:36:35.440 --> 0:36:37.560
<v Speaker 1>I think in the last day or so, the tempers

0:36:37.560 --> 0:36:40.280
<v Speaker 1>have cooled, but people are still saying, well, okay, fine,

0:36:40.440 --> 0:36:43.719
<v Speaker 1>but the way it's written is very broad and it

0:36:43.760 --> 0:36:48.080
<v Speaker 1>could be allowed, it could allow opening the door to

0:36:48.560 --> 0:36:51.040
<v Speaker 1>doing these things. So they're saying that Google was a

0:36:51.040 --> 0:36:55.280
<v Speaker 1>little reckless is probably a strong word, but they were

0:36:55.320 --> 0:36:59.600
<v Speaker 1>a little uhum vague in their terms and uh and

0:36:59.600 --> 0:37:03.759
<v Speaker 1>it grant them those permissions where they could theoretically do that.

0:37:03.800 --> 0:37:06.480
<v Speaker 1>But again, these terms are very similar to the ones

0:37:06.600 --> 0:37:09.840
<v Speaker 1>used by just about everybody else out there. I remember

0:37:10.000 --> 0:37:13.400
<v Speaker 1>almost identical story from a couple of years ago, and

0:37:13.480 --> 0:37:17.000
<v Speaker 1>I can't remember what the company was. It might have

0:37:17.040 --> 0:37:21.200
<v Speaker 1>even been Google again, but I remember distinctly that there

0:37:21.360 --> 0:37:24.560
<v Speaker 1>was a discussion about this sort of thing and how

0:37:24.680 --> 0:37:27.400
<v Speaker 1>people were worried that they were handing their rights over

0:37:28.000 --> 0:37:30.520
<v Speaker 1>to another company, when in truth, what was going on

0:37:30.640 --> 0:37:33.000
<v Speaker 1>was just like this. It was it was the permissions

0:37:33.000 --> 0:37:36.440
<v Speaker 1>were there so that the service could display the work

0:37:36.840 --> 0:37:39.279
<v Speaker 1>and the way it needed to be displayed for it

0:37:39.320 --> 0:37:43.400
<v Speaker 1>to be useful, and uh and so ultimately it just

0:37:43.440 --> 0:37:45.960
<v Speaker 1>boiled down to know, we're not selling your stuff. We

0:37:46.080 --> 0:37:49.319
<v Speaker 1>just need this permission or else there's no service. We

0:37:49.320 --> 0:37:52.000
<v Speaker 1>we literally cannot do what we need to do for

0:37:52.080 --> 0:37:56.600
<v Speaker 1>us to be useful. So um, yeah, no need to panic,

0:37:57.200 --> 0:37:59.600
<v Speaker 1>although it's always good to question just in case. I mean,

0:38:00.080 --> 0:38:03.600
<v Speaker 1>you know, Google does still have that that motto of

0:38:03.719 --> 0:38:08.719
<v Speaker 1>don't be evil, but you never know where. Evil's kind

0:38:08.760 --> 0:38:12.760
<v Speaker 1>of an interesting thing that itself is not entirely uh

0:38:12.880 --> 0:38:15.279
<v Speaker 1>like one from one man's definition of evil may be

0:38:15.320 --> 0:38:19.360
<v Speaker 1>different from another's. And I've heard it clarified um Prime

0:38:19.520 --> 0:38:23.720
<v Speaker 1>that that was really intended to mean, don't manipulate search

0:38:23.760 --> 0:38:28.399
<v Speaker 1>results to facilitate advertising, and it was specifically geared towards that.

0:38:28.560 --> 0:38:31.200
<v Speaker 1>So keep your eyes it's always going to keep your

0:38:31.200 --> 0:38:35.200
<v Speaker 1>eyes open. No, it's it's always important to question. So

0:38:35.280 --> 0:38:38.200
<v Speaker 1>let's go on to talking a little bit about how

0:38:38.239 --> 0:38:42.319
<v Speaker 1>Google Drives stacks up against other cloud storage services. So

0:38:42.840 --> 0:38:45.799
<v Speaker 1>with the free storage, with five gigabytes free storage, that

0:38:45.880 --> 0:38:49.160
<v Speaker 1>puts it on the same playing ground as services like

0:38:49.239 --> 0:38:51.960
<v Speaker 1>Box and sugar Sink. Both of those offer five gigs

0:38:51.960 --> 0:38:54.920
<v Speaker 1>as well. Drop Boxes a little less is two gigabytes.

0:38:54.960 --> 0:38:57.319
<v Speaker 1>But again, if you start referring other people and they

0:38:57.400 --> 0:39:00.920
<v Speaker 1>joined the service, you get five hundred megabytes per referral,

0:39:01.040 --> 0:39:05.000
<v Speaker 1>up to a maximum sixteen gigs. So you could, in theory,

0:39:05.200 --> 0:39:08.040
<v Speaker 1>have way more storage for free on Dropbox than you

0:39:08.040 --> 0:39:11.560
<v Speaker 1>would on these other services. Microsoft sky Drive is at

0:39:11.680 --> 0:39:16.000
<v Speaker 1>seven gigabytes, but people who had sky Drive accounts previous

0:39:16.040 --> 0:39:21.320
<v Speaker 1>to Google Drives launch can have up to hi gigabytes

0:39:21.800 --> 0:39:24.799
<v Speaker 1>for free. Yes, but that offers being made for a

0:39:24.880 --> 0:39:27.160
<v Speaker 1>limited time. So if you have that and you want

0:39:27.239 --> 0:39:29.520
<v Speaker 1>to keep that, you might want to go quickly over

0:39:29.560 --> 0:39:32.480
<v Speaker 1>there too. In fact, by the time this podcast publishes

0:39:32.520 --> 0:39:35.680
<v Speaker 1>it may very well be late too late. UM, so

0:39:35.760 --> 0:39:41.760
<v Speaker 1>in that case we're sorry anyway. The the minimum upgrade,

0:39:41.800 --> 0:39:44.960
<v Speaker 1>so the smallest step that you can make from free

0:39:45.040 --> 0:39:48.520
<v Speaker 1>to a paid service is uh as a little different

0:39:48.600 --> 0:39:52.319
<v Speaker 1>depending on them the service. So for Google Drive it's

0:39:52.360 --> 0:39:55.440
<v Speaker 1>two dollars and forty nine cents per month for gigs

0:39:55.440 --> 0:40:00.200
<v Speaker 1>of storage. For for Dropbox, you get the lowest up

0:40:00.239 --> 0:40:03.040
<v Speaker 1>is fifty gigabytes of storage for nine dollars and ninety

0:40:03.160 --> 0:40:06.839
<v Speaker 1>nine cents a month, So if you're breaking it down

0:40:06.920 --> 0:40:11.160
<v Speaker 1>per gig then Google Drive is cheaper, although you get

0:40:11.239 --> 0:40:15.600
<v Speaker 1>less storage. Uh Box is twenty five gigabytes, so same

0:40:15.640 --> 0:40:18.799
<v Speaker 1>amount as Google Drive, same amount storage, but for nine

0:40:18.840 --> 0:40:21.400
<v Speaker 1>dollars nine nine cents a month, so it's more expensive.

0:40:22.120 --> 0:40:25.640
<v Speaker 1>Sugar Sinc. Is thirty gigabytes of storage for four dollars

0:40:25.640 --> 0:40:29.920
<v Speaker 1>and ninety nine cents a month, so uh it's you

0:40:29.960 --> 0:40:33.240
<v Speaker 1>get you get five gigabytes more storage, but it's um

0:40:33.280 --> 0:40:37.640
<v Speaker 1>it's essentially twice the price of Google Drive. UH And

0:40:37.680 --> 0:40:41.560
<v Speaker 1>then um sky Drive is twenty gigabytes for ten dollars

0:40:41.600 --> 0:40:45.080
<v Speaker 1>a year, which is actually uh it's a little less

0:40:45.080 --> 0:40:48.600
<v Speaker 1>storage than Google Drive, but Google Drive at tot nine

0:40:48.600 --> 0:40:50.840
<v Speaker 1>a month, you multiply that by twelve months, then you're like,

0:40:50.920 --> 0:40:55.040
<v Speaker 1>oh well, Microsoft sky Driving away is a little cheaper UM.

0:40:55.120 --> 0:40:57.720
<v Speaker 1>So that's how those stack up. And also the maximum

0:40:57.760 --> 0:41:00.719
<v Speaker 1>file size limit. Google Drive knows the others out of

0:41:00.719 --> 0:41:03.840
<v Speaker 1>the water, except for Sugar Sinc. Which does not technically

0:41:03.840 --> 0:41:07.640
<v Speaker 1>have a file size limit, but the but box is

0:41:07.760 --> 0:41:11.560
<v Speaker 1>limit is a hundred megabytes, so that's that's not too big.

0:41:12.160 --> 0:41:14.640
<v Speaker 1>Drop Box and sky Drive both have a limit of

0:41:14.640 --> 0:41:20.799
<v Speaker 1>two gigabytes for a file size. Uh. The uh. Sugar Sinc,

0:41:20.920 --> 0:41:24.239
<v Speaker 1>drop Box, sky Drive, and Google Driver are all compatible

0:41:24.280 --> 0:41:30.000
<v Speaker 1>both with Windows and Mac. Box is a business enterprise

0:41:30.320 --> 0:41:34.520
<v Speaker 1>UM service, so primarily I mean you can you can

0:41:34.560 --> 0:41:38.600
<v Speaker 1>get one if you want one. Uh. All of them

0:41:38.640 --> 0:41:42.400
<v Speaker 1>have iPhone apps except for Google Drive right now, but

0:41:42.480 --> 0:41:46.719
<v Speaker 1>Google drives working on it. Uh. The only one that

0:41:46.760 --> 0:41:48.680
<v Speaker 1>doesn't have an Android app out of the of the

0:41:48.719 --> 0:41:52.520
<v Speaker 1>ones I've listed is sky Drive, Microsoft sky Drive. Everything

0:41:52.560 --> 0:41:55.080
<v Speaker 1>else has an Android app already out on the market.

0:41:55.680 --> 0:41:59.799
<v Speaker 1>Windows Phone. Well, here's a shock. Microsoft sky Drive has

0:41:59.840 --> 0:42:04.960
<v Speaker 1>a does phone app, but Google Drive doesn't, Dropbox doesn't,

0:42:05.280 --> 0:42:09.479
<v Speaker 1>Box doesn't Sugar Sinks is supposedly coming out, so maybe

0:42:09.480 --> 0:42:11.359
<v Speaker 1>by the time this podcast, because Live Sugar Sink will

0:42:11.400 --> 0:42:15.560
<v Speaker 1>have theirs UM. They all are. They all have web access,

0:42:15.640 --> 0:42:18.359
<v Speaker 1>so you can access the service over the web, so

0:42:18.400 --> 0:42:21.359
<v Speaker 1>even if your device does not have an application that

0:42:21.840 --> 0:42:24.200
<v Speaker 1>is native to that device, you can still get there

0:42:24.280 --> 0:42:27.799
<v Speaker 1>over the web, assuming you have a browser. UH, and

0:42:27.880 --> 0:42:30.319
<v Speaker 1>all of them allow for public file sharing, so that

0:42:30.360 --> 0:42:33.759
<v Speaker 1>you can actually let other folks see what's in your

0:42:33.880 --> 0:42:36.799
<v Speaker 1>drive or see specific files that you have you know,

0:42:37.560 --> 0:42:40.800
<v Speaker 1>enabled public sharing. You can also do private file sharing

0:42:40.800 --> 0:42:42.880
<v Speaker 1>with all of them, so that if you want to

0:42:42.920 --> 0:42:44.799
<v Speaker 1>have just a group of collaborators, Let's say you're all

0:42:44.840 --> 0:42:47.080
<v Speaker 1>working on a project together and you want to be

0:42:47.160 --> 0:42:50.920
<v Speaker 1>able to look at everyone else's UM information on a

0:42:50.960 --> 0:42:54.160
<v Speaker 1>particular file, you can do that, and then the public

0:42:54.239 --> 0:42:56.440
<v Speaker 1>itself would be shielded. They would not be able to

0:42:56.440 --> 0:43:00.520
<v Speaker 1>see that UM. And most of them off first some

0:43:00.800 --> 0:43:04.600
<v Speaker 1>sort of collaborative document editing, although you might have to

0:43:04.680 --> 0:43:09.440
<v Speaker 1>use proprietary apps in order to do it. Dropbox does not,

0:43:09.640 --> 0:43:12.200
<v Speaker 1>it's more of a storage feature than collaboration. Sugar Sync

0:43:12.280 --> 0:43:15.359
<v Speaker 1>also doesn't, but sky Drive, Box and Google Drive all

0:43:15.440 --> 0:43:18.640
<v Speaker 1>do UM. And then there are a couple of other

0:43:19.440 --> 0:43:26.040
<v Speaker 1>uh features like the third party apps, UM integration. That's

0:43:26.080 --> 0:43:28.960
<v Speaker 1>that's pretty much standard across the board. Sky Drive is

0:43:29.000 --> 0:43:32.600
<v Speaker 1>specifically going to be for Windows eight apps, so, but

0:43:32.760 --> 0:43:36.759
<v Speaker 1>others are you know, pretty much unfettered. So that's kind

0:43:36.800 --> 0:43:40.160
<v Speaker 1>of how it boils down to the other major cloud

0:43:40.200 --> 0:43:42.399
<v Speaker 1>services that are out there, and there's there's more than that.

0:43:42.760 --> 0:43:46.200
<v Speaker 1>That's just that's just a handful of them. Oh yeah,

0:43:46.280 --> 0:43:52.200
<v Speaker 1>I've I've got different applications for several of them, including

0:43:52.320 --> 0:43:56.320
<v Speaker 1>uh a Bunto one which is offered by Canonical primarily

0:43:56.320 --> 0:43:58.480
<v Speaker 1>for Linux users. And uh, you know, they're there are

0:43:58.480 --> 0:44:02.360
<v Speaker 1>others out there they're trying um and people have questioned

0:44:02.360 --> 0:44:04.480
<v Speaker 1>whether or not these services are going to continue into

0:44:04.520 --> 0:44:08.040
<v Speaker 1>the future. UM, I think Google Drive may end up

0:44:08.080 --> 0:44:12.000
<v Speaker 1>being a model for what's going to be happening. Google

0:44:12.080 --> 0:44:16.239
<v Speaker 1>Drive and sky Drive basically are you know, sort of

0:44:16.480 --> 0:44:21.799
<v Speaker 1>hybrids of online collaboration, software and storage. UM. So the

0:44:21.840 --> 0:44:25.040
<v Speaker 1>pure storage players like Dropbox and sugar Sink may have

0:44:25.360 --> 0:44:28.480
<v Speaker 1>a difficult time competing with them in the future, especially

0:44:28.560 --> 0:44:31.600
<v Speaker 1>since they're owned by uh, you know, sky Driving and

0:44:31.960 --> 0:44:35.480
<v Speaker 1>um Google Driver are you know, big players, and they've

0:44:36.239 --> 0:44:38.000
<v Speaker 1>got a whole lot of money to throw at these

0:44:38.040 --> 0:44:42.719
<v Speaker 1>these UM different applications, so you know, creating larger and

0:44:42.800 --> 0:44:47.920
<v Speaker 1>larger file storage for free, offering those services for free. UM.

0:44:47.960 --> 0:44:50.000
<v Speaker 1>You know, it may not be very long at all

0:44:50.040 --> 0:44:53.160
<v Speaker 1>before Google and Microsoft are offering you know, ten gigabytes

0:44:53.840 --> 0:44:56.920
<v Speaker 1>UM or you know, or more than that. And of

0:44:56.920 --> 0:44:59.239
<v Speaker 1>course you know, Apple is doing something very similar with

0:44:59.280 --> 0:45:04.799
<v Speaker 1>the the um I work sweet too, So UM it's

0:45:04.880 --> 0:45:06.839
<v Speaker 1>very possible that the big players in the industry may

0:45:06.960 --> 0:45:10.120
<v Speaker 1>run off with it and and the pure storage guys

0:45:10.360 --> 0:45:12.400
<v Speaker 1>sort of followed by the wayside. I would say that

0:45:12.760 --> 0:45:15.520
<v Speaker 1>is a very very real possibility, but probably not for

0:45:15.520 --> 0:45:18.640
<v Speaker 1>another year or two at least. UM. Just as people

0:45:18.680 --> 0:45:21.800
<v Speaker 1>decide what it is they want to do with these systems,

0:45:21.840 --> 0:45:24.320
<v Speaker 1>if they end up using just storage, you know, hey,

0:45:24.440 --> 0:45:27.279
<v Speaker 1>I'd rather create a document on my desktop and then

0:45:27.280 --> 0:45:30.520
<v Speaker 1>share it with my collaborators on the on the drive

0:45:31.120 --> 0:45:33.400
<v Speaker 1>rather than you know us working on a document in

0:45:33.440 --> 0:45:36.719
<v Speaker 1>the cloud in my web browser. I think. UM, I

0:45:36.760 --> 0:45:39.479
<v Speaker 1>think the real problem for the consumer in the short

0:45:39.560 --> 0:45:42.560
<v Speaker 1>term is going to be uh, figuring out where the

0:45:42.600 --> 0:45:46.640
<v Speaker 1>heck your data is if you're using multiple um multiple services.

0:45:46.719 --> 0:45:49.640
<v Speaker 1>I do have that problem, Yeah, because if you have

0:45:49.640 --> 0:45:53.040
<v Speaker 1>a Dropbox and I have Google Drive. Those are the

0:45:53.040 --> 0:45:55.959
<v Speaker 1>only two that I'm using. I've got like six or seven. Yeah,

0:45:55.920 --> 0:45:59.840
<v Speaker 1>I resisted that temptation because I knew what would happen.

0:46:00.040 --> 0:46:03.000
<v Speaker 1>It's the problem you have. The problem you have within

0:46:03.160 --> 0:46:05.960
<v Speaker 1>one drive is multiplied when you have multiple drives. So

0:46:06.040 --> 0:46:08.799
<v Speaker 1>that's like, that's like you come home and you don't

0:46:08.800 --> 0:46:12.040
<v Speaker 1>know what which computer has the file that you need

0:46:12.160 --> 0:46:14.680
<v Speaker 1>on it. So you've got four computers in your house

0:46:14.680 --> 0:46:17.799
<v Speaker 1>for some reason, Uh, like you live in my house

0:46:17.840 --> 0:46:19.960
<v Speaker 1>for example. Actually I think I've got more than four,

0:46:20.440 --> 0:46:22.839
<v Speaker 1>but anyway, I think I've got five. Anyway, let's say

0:46:22.840 --> 0:46:24.920
<v Speaker 1>that you've got five computers at your house. Then let's

0:46:24.920 --> 0:46:27.880
<v Speaker 1>say you've got five computers in my house, and that

0:46:28.000 --> 0:46:30.839
<v Speaker 1>I have a file saved on one of those computers.

0:46:31.320 --> 0:46:34.320
<v Speaker 1>Then comes the fun part of going to each computer

0:46:34.360 --> 0:46:36.839
<v Speaker 1>and figuring out where it is. The same problem. If

0:46:36.880 --> 0:46:41.239
<v Speaker 1>you're using multiple cloud storage services, you're gonna have to

0:46:41.239 --> 0:46:44.000
<v Speaker 1>go and do search for each one. That the benefit

0:46:44.080 --> 0:46:45.600
<v Speaker 1>to it is that you can at least do that

0:46:45.680 --> 0:46:48.680
<v Speaker 1>search from one machine, as long as that one machine

0:46:48.719 --> 0:46:51.480
<v Speaker 1>can access each of the services you're using, and if

0:46:51.480 --> 0:46:54.200
<v Speaker 1>they all have web based access, and you've got a

0:46:54.200 --> 0:46:56.359
<v Speaker 1>web browser, then you've got that problem solved, even if

0:46:56.360 --> 0:46:59.640
<v Speaker 1>it's not the most elegant solution, but still means that

0:46:59.680 --> 0:47:01.600
<v Speaker 1>you have to check each one of the drives and

0:47:01.640 --> 0:47:03.520
<v Speaker 1>figure out where you have it, and then you might

0:47:03.640 --> 0:47:06.480
<v Speaker 1>even fall into that same trap you had before where

0:47:06.480 --> 0:47:09.680
<v Speaker 1>you might have duplicate files. You might have one instance

0:47:09.880 --> 0:47:13.240
<v Speaker 1>on one drive and another instance on another drive. So

0:47:13.440 --> 0:47:15.759
<v Speaker 1>um yeah, that's that's gonna be a problem too, is

0:47:15.800 --> 0:47:17.879
<v Speaker 1>that if you use a lot of these services, then

0:47:18.480 --> 0:47:22.200
<v Speaker 1>you still have to have some sort of discipline when

0:47:22.239 --> 0:47:24.719
<v Speaker 1>it comes to data management. Maybe you only use one

0:47:24.800 --> 0:47:27.160
<v Speaker 1>for one particular type of file and use another for

0:47:27.200 --> 0:47:29.480
<v Speaker 1>a different one. In that way, at least you reduce

0:47:29.719 --> 0:47:33.480
<v Speaker 1>that confusion. Me what I think I'm gonna end up

0:47:33.520 --> 0:47:36.000
<v Speaker 1>doing is I'm going to pick one, and I haven't

0:47:36.040 --> 0:47:39.279
<v Speaker 1>decided which yet, although let's be honest, Google Drive is

0:47:39.320 --> 0:47:43.160
<v Speaker 1>probably the lead, simply because I have a lot of

0:47:43.160 --> 0:47:48.360
<v Speaker 1>products that run Android, so you know, I'm kind of

0:47:48.360 --> 0:47:52.160
<v Speaker 1>locked into that in ecosystem already, but I haven't completely

0:47:52.160 --> 0:47:54.920
<v Speaker 1>decided yet. So let's say, you know, whichever one I

0:47:54.960 --> 0:47:58.760
<v Speaker 1>decide on, I'm going to eventually move all my things,

0:47:59.200 --> 0:48:01.200
<v Speaker 1>all of the things. I'm going to move all of

0:48:01.239 --> 0:48:04.279
<v Speaker 1>the things into that folder and I'm just gonna get

0:48:04.360 --> 0:48:06.959
<v Speaker 1>rid of the others, so that way I don't have

0:48:07.080 --> 0:48:10.960
<v Speaker 1>that issue. Is there anything else you want to say

0:48:10.960 --> 0:48:12.560
<v Speaker 1>about this before we wrap up? No, I think we

0:48:12.560 --> 0:48:15.800
<v Speaker 1>should close it up. Let's do that. Then let's close

0:48:15.960 --> 0:48:19.520
<v Speaker 1>this crazy thing. Let's drive it home. Ladies and gentlemen.

0:48:20.200 --> 0:48:24.480
<v Speaker 1>If you have any suggestions for any podcast topics we

0:48:24.520 --> 0:48:28.920
<v Speaker 1>should cover in the future, I invite you, nay, I

0:48:29.120 --> 0:48:33.440
<v Speaker 1>compel you to contact us with those suggestions. You may

0:48:33.520 --> 0:48:37.879
<v Speaker 1>do so either over email our addresses tech stuff at

0:48:38.080 --> 0:48:43.680
<v Speaker 1>Discovery dot com or hither the to the uh the

0:48:43.920 --> 0:48:47.279
<v Speaker 1>Facebook or Twitter thing and use that to let us

0:48:47.360 --> 0:48:49.240
<v Speaker 1>know our handle at both of those is tech Stuff

0:48:49.360 --> 0:48:54.080
<v Speaker 1>hs W. You've been working at the Renaissance first board game. Huzzah.

0:48:54.640 --> 0:48:58.879
<v Speaker 1>Let us conclude this day's event, and narrowly we shall

0:48:59.000 --> 0:49:02.239
<v Speaker 1>go and take to break and verily Chris and I

0:49:02.440 --> 0:49:07.600
<v Speaker 1>shall speak with thee again Anon. For more on this

0:49:07.800 --> 0:49:10.719
<v Speaker 1>and thousands of other topics, visit how Stuff works dot com,

0:49:15.080 --> 0:49:17.640
<v Speaker 1>brought to you by the reinvented two thousand twelve camera.

0:49:17.960 --> 0:49:19.000
<v Speaker 1>It's ready, are you