{"id":45312,"date":"2024-10-09T15:16:57","date_gmt":"2024-10-09T19:16:57","guid":{"rendered":"https:\/\/mjtsai.com\/blog\/?p=45312"},"modified":"2024-10-10T09:24:37","modified_gmt":"2024-10-10T13:24:37","slug":"panic-drops-google-drive-access","status":"publish","type":"post","link":"https:\/\/mjtsai.com\/blog\/2024\/10\/09\/panic-drops-google-drive-access\/","title":{"rendered":"Panic Drops Google Drive Access"},"content":{"rendered":"

Michael Buckley<\/a> (Mastodon<\/a>, Hacker News<\/a>):<\/p>\n

\n

At some unknown point in the future, Google will revoke Transmit’s access to Google Drive. Sometime after that, we’ll be releasing updates to Transmit and Nova that remove the ability to create Google Drive connections.<\/p>\n

[…]<\/p>\n

In March, Transmit was re-approved for Google Drive access — but we were told we would now need to pass this check annually. At this point, we began to question whether this yearly process was worth it.<\/p>\n

Between the weeks of waiting, submitting the required documentation and the process of scanning the code, it took a significant amount of time from our engineers. For example, Google provided a Docker image for running the scanner, but it didn’t work. We had to spend more than a week debugging and fixing it. And because the scanner found no problems, it didn’t result in any improvements to Transmit. No one benefitted from this process. Not Google, not Panic, and not our users.<\/p>\n

[…]<\/p>\n

Google completely removed the option for us to scan our own code<\/a>. Instead, to keep access to Google Drive, we would now have to pay one of Google’s business partners to conduct the review. […] These ever-shifting requirements and expenses are finally catching up to third parties.<\/p>\n<\/blockquote>\n\n

Damien Petrilli<\/a>:<\/p>\n

\n

I have the feeling that Google Drive is going to be useless very soon. Most indie apps are going to stop supporting it.<\/p>\n<\/blockquote>\n\n

Previously:<\/p>\n