Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

google drive OAuth lockdown #29

Open
joeyh opened this issue Jun 27, 2019 · 0 comments

Comments

Projects
None yet
1 participant
@joeyh
Copy link

commented Jun 27, 2019

https://arstechnica.com/gadgets/2019/06/gmails-api-lockdown-will-kill-some-third-party-app-access-starting-july-15/

Based on that article, something similar will happen to google drive OAuth "early next year ". I have not been able to find a confirming statement from Google, but I didn't look very hard.

The "app" review process is apparently rather expensive: $15k+. I should note that, if Google wants to verify git-annex as part of a review of this special remote, I will not cooperate with their review, beyond typical free software development norms.

Anyway, if this API lockdown is going to prevent git-annex users from accessing their data in google drive, I feel we should work to help them move the data to other storage before it happens.

One idea is, write some documentation about it, and this special remote can use INFO to display a message to the user pointing at a transition guide.

Another idea is you could run "git annex untrust $googleuuid". (But see https://git-annex.branchable.com/todo/way_to_untrust_without_unncessary_branch_update/ )

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.