Allow custom API key for Google Drive

[Gunny]

If you let us specify our own api key for google drive, it would reduce load on your api key as well as provide better and more consistent performance, especially regarding rate limits.

How to make your own google drive api key.

1. Log into the Google API Console with your Google account. It doesn’t matter what Google account you use. (It need not be the same account as the Google Drive you want to access)
2. Select a project or create a new project.
3. Under Overview, Google APIs, Google Apps APIs, click “Drive API”, then “Enable”.
4. Click “Credentials” in the left-side panel (not “Go to credentials”, which opens the wizard), then “Create credentials”, then “OAuth client ID”. It will prompt you to set the OAuth consent screen product name, if you haven’t set one already.
5. Choose an application type of “other”, and click “Create”. (the default name is fine)
6. It will show you a client ID and client secret. Use these values in rclone config to add a new remote or edit an existing remote.

[Gunny]

Any thoughts from the devs on this?

[Kostas]

Hi,

It's a good idea but we are concerned that it may violate the Google APIs Terms of Service as mentioned in https://developers.google.com/terms

Thanks,
Kostas

[Gunny]

Hi,

It's a good idea but we are concerned that it may violate the Google APIs Terms of Service as mentioned in https://developers.google.com/terms

Thanks,
Kostas

I don't see where that would violate their ToS, and other programs already allowing this (rsync is extremely popular for instance). People using their own API key would already have to signup and agree to the Google API ToS and actions performed using that API key would be their responsibility, not yours which would actually reduce 2BrightSparks liability footprint in those instances.

[Kostas]

Hi,

It's a good idea but we are concerned that it may violate the Google APIs Terms of Service as mentioned in https://developers.google.com/terms

Thanks,
Kostas

I don't see where that would violate their ToS, and other programs already allowing this (rsync is extremely popular for instance). People using their own API key would already have to signup and agree to the Google API ToS and actions performed using that API key would be their responsibility, not yours which would actually reduce 2BrightSparks liability footprint in those instances.

Hi,

Please send us an email at [email protected] so we can discuss the details about this.

Thanks,
Kostas

[IMTheNachoMan]

For the record, I don't think this violates their ToS. Many other products, like rclone, let you specify your own key.