Re: Issue 573 in googlecl: GoogleCL: OAuth1/AuthSub is being deprecated on April 20th, 2015. Please migrate to OAuth2

[goog...@googlecode.com]

Comment #41 on issue 573 by p...@voltar.org: GoogleCL: OAuth1/AuthSub is
being deprecated on April 20th, 2015. Please migrate to OAuth2
https://code.google.com/p/googlecl/issues/detail?id=573

So this needs a reboot from the ground up? Peachy. Seems about right for
something based on Google APIs. Everything is great until they change
everything completely every few years.

--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings

[goog...@googlecode.com]

Comment #42 on issue 573 by avswal...@gmail.com: GoogleCL: OAuth1/AuthSub

is being deprecated on April 20th, 2015. Please migrate to OAuth2
https://code.google.com/p/googlecl/issues/detail?id=573

The developer probably should have started to look at Oauth2 in 2013 when
Google said they were deprecating it.

Looking at Google's developer APIs, it wouldn't be impossible to build
something like GoogleCL with a very clean codebase. On their website, they
show how implementing OAuth2.0 only requires three or four lines of code.
Their libraries do implement every GoogleCL function.

It would be possible in my view to create something in node or Go, with the
updated Google libraries as codebase. If somebody is willing to work with
me on this (hopefully including the original development team) then I will
open a project on GitHub where we can work on it.

[goog...@googlecode.com]

Comment #43 on issue 573 by p...@voltar.org: GoogleCL: OAuth1/AuthSub is

being deprecated on April 20th, 2015. Please migrate to OAuth2
https://code.google.com/p/googlecl/issues/detail?id=573

I would say: start it and link to it here.

I doubt you'll get anyone that'll agree to work on it like a team mate or
whatever, but if the project exists and you can add little plugins for
whatever tasks and interfaces people need; then people will surely jump in.

I pretty much intended to jump in on this one, but it seems to need a
complete re-do and I'm not that great with python — oh, and time. Where do
you buy freetime?

[goog...@googlecode.com]

Comment #44 on issue 573 by avswal...@gmail.com: GoogleCL: OAuth1/AuthSub

is being deprecated on April 20th, 2015. Please migrate to OAuth2
https://code.google.com/p/googlecl/issues/detail?id=573

I agree, unfortunately the situation seems to be that either people really
do want to contribute but cannot by way of lack of experience, or they can
contribute but won't for one reason or another - the banes of opensource.

Anyhow, I'm extremely busy with LXC/LXD. I will get to the stage with the
software I'm programming where application abstraction will be important
(after all, this is the whole point of containers). I think a GoogleCL
revival or rewrite would fit in there for me. But, I'm happy to start
something now provided I'm not on my lonesome; you're quite right, if free
time could be bought I'd be an even poorer man than I already am lol. --swr

[goog...@googlecode.com]

Comment #45 on issue 573 by p...@voltar.org: GoogleCL: OAuth1/AuthSub is

being deprecated on April 20th, 2015. Please migrate to OAuth2
https://code.google.com/p/googlecl/issues/detail?id=573

I remember being encouraged once: nobody else is working on this. You're
qualified because you're willing to work on it... just work on it. Only
they said it very eloquently.

My point was that if it's time to start with a new language or a new
design, then it's doubly perfect because this one needs to be re-written
(more or less) anyway. On the other hand, it's probably fastest to just
fix this one or if people really prefer python, then it's probably the way
to go to fix this.

So I keep the ticket tab pinned and wish for time to work on it... but I'd
prolly pin your github project too.

[goog...@googlecode.com]

Comment #46 on issue 573 by harid...@gmail.com: GoogleCL: OAuth1/AuthSub is

being deprecated on April 20th, 2015. Please migrate to OAuth2
https://code.google.com/p/googlecl/issues/detail?id=573

Perhaps something based on the official JS library that runs in node.js
will be a better bet?

https://github.com/google/google-api-nodejs-client/

Since this uses the same JS library that is also used for browsers, there
is a better chance for such a solution to survive in future.