Google blocked Blot?

I switched to git because of this. (It stopped working for a day and a half, but seems to be okay now even though my support email was never answered.)

I'm not sure if it's an out of date cert from blot or that blot was never an approved app and Google made a change on their end.

is g.drive working now at all for anyone? my site is not updating...

I've been resyncing my folder every time I update--it works, but it's a pain in the ass. Would love to get this resolved sooner than later.

Working on a fix for this, sorry for the delay

Any update on this? I really, really need to update my site, but I haven't been able to for months!

I need to rewrite the Google Drive client, unfortunately.

Google is currently blocking new users from granting Blot access to its API because I refused to pay thousands of dollars per year to a third-party company to "audit" our code. This audit used to be possible using a free, self-hosted tool, but Google recently changed their already convoluted rules with little notice, making this option impossible.

What’s especially absurd is that the Google Drive API permissions themselves are inherently dangerous. They grant Blot access to all of your files, even though all we need is access to a single folder. This is a serious security risk, as it unnecessarily exposes far more of your data than required. By comparison, Dropbox has a much safer system called "App folders," which restricts an app’s access to a single, dedicated folder. Google Drive, however, doesn’t provide this option. Instead of developing a safer, more granular permissions model, Google requires you to give Blot blanket access to your entire Drive and then forces developers to pay for expensive third-party audits to enable this access.

I have a plan to work around this and still allow people to use Google Drive with Blot, but it requires rewriting the client. My solution is to bypass the API entirely. Instead of connecting directly to Blot, you will create a folder in your Drive and share it with Blot’s Google Drive account, using an email address we’ll provide on the setup page.

I'll follow up here and respond to your emails once this is ready to go

iA wrote about the same issue with Google, they included screenshots of the same sort of infuriating emails we received. Unlike iA I will try and workaround this, although perhaps its wiser just to move on and ignore Google.

Hi all, I managed to find a temporary workaround (available to Google Workspace admins) struggling with Blot integration in light of Google's sudden policy change:

1. Log in as admin: Go to admin.google.com, and log in with administrator rights.

2. Access API Controls: Navigate to Security > API Controls > Manage Third-Party App Access.

3. Configure App: Select Configured Apps. Click Configure New App, search for “Blot,” and choose the verified Blot app.

4. Set Permissions: Configure app access as Trusted.

5. Assign Access: Apply settings to the specific user(s), group(s), or organization(s) of your choice.

6. Save Changes: Confirm to apply changes.

Note: I did experiment quite abit with different settings like App-Specific Passwords and Less Secure Apps prior to the fix above, so the solution may lie in a combination of settings, but this change is what eventually did the trick for me.

Hopefully, it can provide some temporary relief to any users reliant on Google Drive integration until a viable long-term solution is in place. It has worked seamlessly for me so far—no sync interruptions or limitations.

– J