google drive – Bram.us

Upload files to Google Drive from the command line with gput

npm install gput googleauth -g
googleauth
# authenticate with google, then
gput foo.jpg

Super simple streaming uploads into google drive from the command line

gput →

The Culture of Free and The Future of Google

Anyone who still believes that Google is all about giving everything away for free, hasn’t really paid attention to just how much Google has changed. Google is not a free service anymore. It’s a premium service where you pay for what you use via Google Drive.

Lengthy article definitely worth your time; Highly recommended read.

The Culture of Free and The Future of Google →

(via @netlash)

Google Drive Application Data Folders

The ‘Application Data folder’ is a special folder that is only accessible by your application. Its content is hidden from the user, and from other apps. Despite being hidden from the user, the Application Data folder is stored on the user’s Drive and therefore uses the user’s Drive storage quota. The Application Data folder can be used to store configuration files, saved games data, or any other types of files that the user should not tamper with.

Google Drive Application Data Folders →

Lucidchart and Google Drive

At the school I teach at, we’ve been using Lucidchart to create our website wireframes. What caught my eye today is that they’ve launched a tight Google Drive integration

With Lucidchart installed for Google Drive, you can:

Create, open and share Lucidchart documents from Drive

View, open and edit Microsoft Visio documents from Drive

Export Lucidchart documents as a PNG, JPG or PDF to be stored in Drive

Initiate daily or weekly backups of all of your Lucidchart documents to be stored in Drive

I think this will be one of the features that could set out Google Drive from its competitors: an early on and direct integration of webapps, directly accessible from within Google Drive.

Introducing Lucidchart integration with Google Drive →

Google Drive’s Privacy Policy

Google Drive’s Privacy Policy compared to the other players out there.

In short, Google is giving itself all the permissions it could possibly need to run all of Google services, with the specific limitations that it doesn’t own anything you upload and it can’t use your data beyond running its services.

Also:

Dropbox’s language is definitely friendlier than Google’s, but it’s actually more expansive, since it’s more vague. Where Google specifically lists the rights and permissions it needs to run its services using precise legal terminology like “create derivative works,” Dropbox just says you’re giving it “the permissions we need” to run its services.

Lots of cruft has been circulating, because most people some to neglect/not mention this little part from Google’s policy:

You retain ownership of any intellectual property rights that you hold in that content. In short, what belongs to you stays yours.

Is Google Drive worse for privacy than iCloud, Skydrive, and Dropbox? →