Google locking down unauthenticated Chromium access; gsync pulls hit rate limits
uwukko · x · 2026-09-22
A developer reports that Google is locking down public, unauthenticated access to Chromium-adjacent resources. Pulling the Chromium source via gsync from googlesource hit timeouts and rate-limit errors, succeeding only after several retries, and tarball source releases have been broken for weeks. The cause is unclear, but the change could be bad news for anyone working with Chromium.
Related event: Google Restricts Anonymous Access to Chromium Source(2 posts)→
More from Infra
- Cloudflare Talk: Swapping Some Agent LLM Calls for Fast Models Like Jev Gives Big Speedups — michellechen · 2026-11-12
- Cloudflare Trains Its Own Clef and Clairic Models to Complete Its Agent Stack — michellechen · 2026-11-12
- AWS open-sources 23 production-ready GenAI assets, cutting build time from months to weeks — AWS ML Blog · 2026-11-12
- Sixth Street CEO: ~$200B of Chips Sitting in Warehouses as Data Centers Lag Behind — SumitGup · 2026-11-12
- AWS CEO Matt Garman: Space Data Centers Are 10-20 Years Away, Likely Not Economically Feasible — rohanpaul_ai · 2026-11-12
- CoreWeave Database Goes GA: Managed PostgreSQL Running Inside Your CKS Cluster Next to GPUs — _ScottCondron · 2026-11-12