Live data from Hacker News

End of the road for Google Drive in Transmit

blog.panic.com

191–196 of 196 posts

Re: End of the road for Google Drive in Transmit

#191
post #168

ELI5: I’m not familiar with the Google Drive API, but does this mean that even if I try to build my own tool as an individual, I have to go through all these steps? I'm asking because, with many API services, you have to declare an app during setup, even if it’s just for personal use.

Compile to apk and sideload; Google won't even know. The audit gate in TFA is a gate to get into the play store.

Re: End of the road for Google Drive in Transmit

#192

I don't use Google Drive and probably never will but FWIW Transmit is still one of the best all-around data transfer apps that exist. I always miss it when I am on my Linux workstation. Being able to quickly connect to an S3 bucket and dump files and edit their permissions is a huge plus. Not to mention basic SFTP access like Cyberduck or Filezilla would do. I have never regretted my purchase of Transmit, it's great!

Yeah Transmit is one of the OG Mac apps (OS X) that were great at a reasonable price. Sadly, they don't make them like this anymore.

Re: End of the road for Google Drive in Transmit

#193
post #90

Any idea what this means for Google Drive support in rclone and similar tools?

rclone strongly recommends users create their own individual API key:

> It is strongly recommended to use your own client ID as the default rclone ID is heavily used. If you have multiple services running, it is recommended to use an API key for each service. The default Google quota is 10 transactions per second so it is recommended to stay under that number as if you use more than that, it will cause rclone to rate limit and make things slower.

https://rclone.org/drive/#making-your-own-client-id

Re: End of the road for Google Drive in Transmit

#194
post #110

I wrote this response to another front page HN article on a similar topic: https://news.ycombinator.com/item?id=41664753 I know everyone loves to dunk on Google, and I definitely agree their communication and customer service to app developers is shite, but this change to permissions scope is a good thing. If you have full, unfettered access to large number of people's Google Drive data, you're a huge target for male…

> if you want complete, unfettered access to my entire Drive account, Panic never got complete or unfettered (or any) access to my Google Drive. I got access. I used their application, which can easily be supervised with Little Snitch or other software to prove that is not sending a copy of my credentials or my files to Panic. If it were OSS it would be even more categorically provable that it's not giving access to…

> The point is, Google is telling THEIR users, not Panic, that they aren't qualified to use their own judgment to select a client. It woudl be just as bad as Microsoft saying that if you want to check your email or access SharePoint you can't use anything but Edge (insert jokes about how they basically did do that 20 years ago with MSIE, but let's be serious, that sort of thing would be rightfully mocked today).

Isn't Google doing the same thing today with YouTube? Isn't that what led MS to give up on EdgeHTML and adopt Blink instead?

Re: End of the road for Google Drive in Transmit

#195
post #90

Any idea what this means for Google Drive support in rclone and similar tools?

rclone strongly recommends users create their own individual API key: > It is strongly recommended to use your own client ID as the default rclone ID is heavily used. If you have multiple services running, it is recommended to use an API key for each service. The default Google quota is 10 transactions per second so it is recommended to stay under that number as if you use more than that, it will cause rclone to rate…

I'm worried that such API keys won't be usable anymore because even API keys for personal use with a single account require that application security review.

Furthermore, the Google Cloud console is not included in the typical Workspace subscription (for obvious reasons).

Re: End of the road for Google Drive in Transmit

#196
post #179
post #88

Earlier quoted context omitted.

> Smells downright anti-competitive The EU will have fun with this when it catches up What? The EU wants to introduce certifications for all products and services, further kneecapping local innovation through regulation and costly certifications. https://digital-strategy.ec.europa.eu/en/policies/cybersecur...

Seems more like a harmonization effort than what Google is proposing here? Or maybe I'm reading it wrong. If I don't get one of these mandarin-approved certifications, will I no longer be able to do business? [The Google audits are a hard barrier to connecting to their cloud platform] It's perhaps a difference between prescriptive and descriptive.

I suspect interference from European industry groups coupled with EU bureaucrats' failure to understand technology and willingness to make software 'secure' by doing paperwork.
Post reply on HN