Google Drive public file downloader when curl/wget fails.
bryanrafaelbueno/Synca
Synca is a sync client that automatically connects your local folders to Google Drive.
Write to Google Sheets from a local script via gcloud CLI authentication
Recently I needed to pull data from the GitHub API and publish to a Google Sheet so I could share...
gcloud.app.deploy Error Response: [13] Failed to create cloud build: invalid bucket
Suddenly, a few days ago gcloud app deploy for a Go app completely broke. Steps to reproduce: Enroll Google Cloud Platform for any gmail account and create a billing account there (there's a free ...
http2/errors.go - net - Git at Google
bliss-making-of - Google Drive
ForkLift 4 - most advanced file manager and FTP client for macOS
Manage your files quickly across local drives and remote servers with ease. ForkLift is a robust FTP/SFTP/WebDAV/Amazon S3/Backblaze B2/Google Drive/Rackspace Cloud Files client and a powerful and versatile file manager.
GCP Suspension Outage: May 19th 2026 - Railway Central Station
Update: May 20th, 2026 - 03:57 AM EST, latest post mortem pending updates from Google: https://blog.railway.com/p/incident-report-may-19-2026-gcp-account-outage Hello all, As part of our commitment to be as transparent as possible about the recent outage: https://status.railway.com/ (and any incident on the platform) we are summarizing what we know thus far- as well as some common questions that we have fielded thus far. _**We plan to update this thread with our official post-mortem once we have the details.**_ As it stands right now, we are working on getting everyone recovered. If not, a user can now redeploy and we will route your code to a healthy machine. We have our whole support team working getting workloads on Google Cloud hosts restored. Keep in mind, we are getting ratelimited by GH as our build pipeline is restoring to be fully healthy. **What we know:** Around 22:20 UTC, our Google Cloud account was placed into a "restricted" status hence removing all of our cloud overflow VMs, our CloudSQL instance, and our API. In removing our API, it removed a central dependency that affected all GCP host workloads, and then after our network route cache expired, then affecting all workloads hosted on the Railway platform. We don't have full knowledge as to why our account was suspended automatically. We got into contact at the start of incident and we remain in contact with the GCP engineering team as we root cause the issue. **FAQ:** **Q: "Doesn't Railway run it's own hardware?"** A: Yes, Railway runs hardware in 8 sites around 4 locations around the world. At the start of 2026, due to demand on our systems, we have bursted back onto the cloud on AWS and GCP. A subset of non-latency sensitive customers and Enterprise customers are using a public cloud for their hosts. However, when we migrated fully onto Metal in Mar. 2025, we kept our API and our DB on GCP as we felt that leaving that workload was well within our risk model. (Candidly: we didn't expect to get our cloud account to get removed via automated enforcement.) **Q: "Why does your API being down mean that my workload went down?"** A: Railway's API talks to our distributed edge which is a suite of proxies that we have all around the world. Each location at the edge maintains a routing table of DNS, however, the network team was in the middle of fully distributing the routing table to make it that each region was fully independent. Once the routing cache at the edge was expired, then all workloads were affected and not just GCP workloads. This is due to be rectified. **Q: "My workload is still down. What gives?"** A: We're seeing recovery in our API, builds, and deployments. If your service is having an issue, please try to give it a redeploy. We'll publish a public postmortem covering what happened when we're fully recovered. | Get Help with Railway
Google Drive - Virus scan warning
Cross-Origin Storage API: Stop Downloading Twice
The Cross-Origin Storage API lets sites share one cached copy of a file (a JS library, font, or AI model) across origins by SHA-256 hash. Here's how it works.
blooym.dev/porxie
[MIRROR ONLY] A correct and efficient ATProto blob proxy for secure content delivery.
Access Blocked: <project> has not completed the Google verification process
I am building a simple script which polls some data and then updates a spreadsheet that I am giving to my client. (It is a small project and I don't need anything fancy.) So I created a Google Cloud
Blooym/porxie
[Mirror] A correct and efficient ATProto blob proxy for secure content delivery.