Comment 96 for bug 1844453

(In reply to Xisco Faulí from comment #88)
> (In reply to daniel from comment #87)
> > This is not working in v7.2.2.2
> >
> > The key is not being properly stored, and the UI leaves a LOT to be desired.
> >
> > You may find that the way the tool rclone (rclone.org) handles this
> > authentication is much more graceful than the current solution.
> >
> > The dialog box is also misleading about what, when (at which step), and
> > where to paste the key from the OAuth process.
> >
> > There has to be a better way for users to be able to use this feature.
>
> hello,
> Please read comment 82 to allow storing the key

I have, but it is extremely user-unfriendly and unless you are looking up this bug report, you would never know how to do it. Even then, the notes in comment #87 are not the complete instructions.

Basically, this method is a dirty workaround of a patch job that needs to be truly fixed in both the backend and the UI. The method used to get and capture the key is not graceful, and the UI is plain incorrect.

I would fix it myself if it was something that had the skill to do (I love open source software for that!), but I do not feel comfortable in my skill level making those modifications. Instead, I have pointed this very skilled and talented community to another piece of open-source software that has done a very good job at tackling this issue for not only Google Drive, but also for numerous other cloud storage vendors. Their code base is mature, and the capabilities of that tool complement what users of this project need.

In reality, the project might even look at integrating that tool's functionality into this one, similar to how other modules have become standard within the software. Spell checking is one function that comes to mind.

I see this as an opportunity to potentially have one community help another, giving them both a way to learn from the other's work and experience. Isn't that one of the main benefits of being open source?