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
- python-build-standalone enables full LTO for CPython 3.12+, modestly boosting runtime — charliermarsh · 2026-09-22
- Measured trade-offs of three REAP-pruned Qwen3.8-Flash-Next MLX builds on Apple Silicon — MensaProdigy · 2026-09-22
- Dev claims further-optimized DeepSeek V4 NVFP4 uses 190GB of 192GB VRAM — HankYeomans · 2026-09-22
- 'AWS made the industry soft': AI infra isn't mature enough to outsource the hard parts — mgill25 · 2026-09-22
- Grass network audited: 3M+ users, $32.1M revenue serving AI training data — Ronangmi · 2026-09-22
- SemiAnalysis: mapping MoE models onto inference hardware — zephyr_z9 · 2026-09-22