It was clear to me from the first half I read that the author completely misunderstood and was unaware of the Drive API scope changes that Google made. There is nothing I wrote that would have been contradicted by the rest of the blog post.
The definition of a well informed, happy, modern man: He reads a couple of lines and goes, "Yep, I know how this article ends. I'm right, he's wrong." Then he watches the first half of a game, switches off the TV, pumps his fist, and says, "My team WINS again." Writes the match report, gets in the shower, soaps himself up, and walks out, unrinsed, fully lathered, super clean.
Drive.file scope is not some secret sauce, it's the standard file picker loaded with UX trouble and bugs. Implementing it would lead to a flood of angry Play Store comments.
We know because we talk to our users for 14 years. We know their needs and their use cases. And we have the numbers to verify. We built this. You're an anonymous guy with a throwaway account on the Internet playing the expert. Your comment history shows that you have a lot of time to show that you're an expert on a wide range of topics.
You say that "we" shouldn't get access to Google Drive. It's not about us, our users demand Google Drive access. They want to decide what to do with their files. We couldn't care less about what is in their drive.
But what if we're hackers or if we get hacked? Yeah, that all or nothing access is not the best engineering from Google, is it?
CASA is trying to tape over that bricolage with the usual security theatre. Because guess what... after paying KPMG for a superficial scan, "we" still would get access to the Full Dive. Until recently we could have done the CASA scan in house and get full access. That's what's bullshit.
It's bullshit like almost all of Google. Bullshit Search that only gives you ads. Bullshit Maps that has become an unusable circus. Bullshit YouTube that is now just as ad infested than 80ties TV. Bullshit "log in for security reasons".
It was clear to me from the first half I read that the author completely misunderstood and was unaware of the Drive API scope changes that Google made. There is nothing I wrote that would have been contradicted by the rest of the blog post.