What is the reason for this choice? :)

A sad day for gdrive users.

What are the alternatives?

Leaving the project unmaintained is one thing, but why did you remove the precompiled binaries from releases? It doesn't really make sense to do so, because someone could find use for them. I still use the latest version on Windows 8.1 for example. It makes it harder for people who want to redownload it in case of lost files.

Guess we won't hear any explanation even...

Leaving the project unmaintained is one thing, but why did you remove the precompiled binaries from releases? It doesn't really make sense to do so, because someone could find use for them. I still use the latest version on Windows 8.1 for example. It makes it harder for people who want to redownload it in case of lost files.

If you still have binaries can you mail them to me. (All you have). And how can i build for linux vs windows. Thanks in advance.

Does Google have a finger on this?

Does Google have a finger on this?

Probably yes. I have the old binary and Google blocks it from authenticating, saying that it's dangerous and they blocked it for my safety (thanks a lot). It looks like Google now requires you to let them review applications that want to access sensitive information through their API

If you want to use it for yourself, you will need to:

1. Go to https://console.developers.google.com and create a new project for yourself
2. Search for the Google Drive API in the search box at the top, and turn it on
3. Click OAuth consent screen on the left and set it up.
   • Assuming your account isn't part of an organization, you'll have to say your app is for external users and in testing
   • In the required scopes section, add .../auth/docs and .../auth/drive (I'm not sure which needed, it's probably only one of those). This will probably not be available if you didn't complete (2)
   • Add the accounts you want to use with your copy of gdrive as testers of your app. Only these accounts will be able to use your copy of gdrive, so everyone will have to compile their own (unless someone goes and gets theirs reviewed by Google)
4. Click Credentials on the left, then Create Credentials, then OAuth client ID. The application type is Desktop app
5. Copy the Client ID and Secret into handlers_drive.go lines 17 and 18 and compile the application

@TellowKrinkle Thanks for your valuabe guide. I will apply it. For step 6. what should I do to compile the complete repo? Will go build gdrive.go be enough? which returns following message: compile: version "go1.14" does not match go tool version "go1.13.8"

I can still use the binary (gdrive: 2.1.0) but I used have have an issue where after multiple requests in short time gdrive's response time became extremely slow to retrieve information of files and so on. I felt like when Google find out these requests, it just blocks it or make the response time slow as possible. I have switch into using gdown (https://github.com/wkentaro/gdown), but I believe some issue might be generated for this as well.

At this point, I am not sure should I continue using gdrive (where I implemented my project based on gdrive and not sure will I be able to use gdrive in the long run) or switch into another approach.

returns following message: compile: version "go1.14" does not match go tool version "go1.13.8"

Does this help? https://stackoverflow.com/a/53661370

@TellowKrinkle Thanks. I know here is not the right place to continue discussion but I am not able to generate token.json in order to use the gdrive. Google keep responding as This app is temporarily blocked from logging in with your Google account., which was not generated before. If I can able to overcome this barrier I believe I am able to use gdrive again.

I asked it on the stackoverflow How to handle “App is temporarily blocked from logging in with your Google account” barrier, hope I will find an answer.

Looks like you're using the old credentials, you need to follow step 5 in my directions