Earlier quoted context omitted.
Well, they're doing pretty heavy de-duping, but point well taken.
The de-duping is certainly more than the discount off list price, too -- I suspect they de-dupe 10-100x. I really doubt their discount off the lowest public S3 volume price is more than 50%.
Introducing Google Drive... yes, really
501–510 of 522 posts
Re: Introducing Google Drive... yes, really
#502Interesting... they are not just going after Dropbox with Google Drive, but also Evernote. "Search by keyword and filter by file type, owner and more. Drive can even recognize text in scanned documents using Optical Character Recognition (OCR) technology."
Is OCR really the feature that makes Evernote a popular product? I don't use it, but I have seen people use it, and it looks more like a notebook that syncs across all your devices. There is little notion of "files". I can't imagine this will have much effect on Evernote.
This way I have one place to store both typed and scanned stuff, and it gets me close to paperless at home.
Re: Introducing Google Drive... yes, really
#503Earlier quoted context omitted.
Dropbox possibly has better customer support compared to Google's possibly non-existent customer support.
My one experience with Dropbox support was not positive: http://news.ycombinator.com/item?id=3885618
Re: Introducing Google Drive... yes, really
#504Earlier quoted context omitted.
You seem to be referring to some othet Google auth system. The two-factor system used for Google accounts sends a code via SMS that you need to enter on the web page. It does not make you enter something on your phone.
There is an google authenticator app for android that you can register with your two factor auth so you can just open the app rather than wait for the text message.
Re: Introducing Google Drive... yes, really
#505Earlier quoted context omitted.
We should also have list going the other - things Dropbox has that GDrive doesn't: * Linux support * Headless (command line interface) * Public bug tracking and feature requests (votebox) Unsure about these * Shared folders I'm struggling to come up with more.
And Dropbox doesn't use/steal your data. So really that is an argument for Dropbox by it self. It also kinda of nulls "* 2-factor authentication!" because what is authentication if your data isn't safe? +1 Dropbox
[1] http://techcrunch.com/2011/06/20/dropbox-security-bug-made-p...
[2] http://dereknewton.com/2011/04/dropbox-authentication-static...
[3] http://www.informationweek.com/news/storage/security/2295006...
Re: Introducing Google Drive... yes, really
#506There is a huge economy of scale working in Google's favor: deduplication. The more users they can de-dupe across, the cheaper their raw storage becomes. To compete, perhaps smaller backup services could agree "reinsurance" contracts with each other, exchanging lists of file hashes...
Re: Introducing Google Drive... yes, really
#507Earlier quoted context omitted.
Ah, I see. Yes, looks like Google offers multiple phone-based two-factor systems. I was referring to the oAuth one, which uses time-based tokens rather than sending the code via SMS.
I see. But does that qualify as a two-factor auth? You need two independent "factors" for that, and while OAuth uses tokens internally, all it does is ensure a secure transport between Google's servers and the app that requests authorization. It doesn't actually obtain two different things from the user.
Re: Introducing Google Drive... yes, really
#508Earlier quoted context omitted.
You actually can get access to these apps in other browsers through the Chrome Web Store. Try adding any of the Drive enabled apps. The experience is a little odd right now, but it works.
I get a big scary message telling me that most apps won't work without Chrome.
So long as this is a temporary situation, which I think it is, I wouldn't be worried.
Re: Introducing Google Drive... yes, really
#509Earlier quoted context omitted.
I see. But does that qualify as a two-factor auth? You need two independent "factors" for that, and while OAuth uses tokens internally, all it does is ensure a secure transport between Google's servers and the app that requests authorization. It doesn't actually obtain two different things from the user.
No, that's not exactly what he means. The "token" isn't the OAuth native token, it's a 6-digit code that is based on the current time and a device secret embedded in the app on your phone.
The cached access token could also be considered a factor, although it depends on the token expiry policy. If the token doesn't require a refresh using a refresh token (which must prompt a password) often enough its security is compromised.
I don't know what kind of expiry Google's OAuth token has, but last time I tested this, it was a very long time. I believe Twitter's live forever. Facebook's offline access scope (which you will need for a normal app) lives forever until the user changes his/her password (see http://developers.facebook.com/blog/post/2011/05/13/how-to--...).
Re: Introducing Google Drive... yes, really
#510Earlier quoted context omitted.
The de-duping is certainly more than the discount off list price, too -- I suspect they de-dupe 10-100x. I really doubt their discount off the lowest public S3 volume price is more than 50%.
Personal photos take up a large fraction of people's cloud storage, and they are completely non-de-dupable. I doubt it's possible to get more than 3x on average.
I didn't realize people used it as a photo or video sharing solution -- that kind of content would be big and non-dedupeable.