3 ms·
The rate limit is unlikely to cause a problem. Google has been crawling the web since its very start, and the internal services which fetch resources from exter
by klodolph 4y ago
The rate limit is unlikely to cause a problem. Google has been crawling the web since its very start, and the internal services which fetch resources from external web servers are extremely resilient. Some request fails? Some request is slow? It's not going to slow down other requests. Maybe these services aren't being used for Go, but the expertise is on tap.
(These kinds services are also supposed to rate-limit their requests.)
- toast0 4y ago> The rate limit is unlikely to cause a problem. If that's the case, then great. It solves the DDoS issue without impacting the Google side, and everyone can be happy.
- verdverm 4y agoThis is completely different architecture and services, largely open sourced. This is limited to Go and the dev team. Most likely these errors would manifest down to the users of Go and those who've a dependency which lives on sourcehut
- klodolph 4y agoA big chunk of the Go core maintainers are Google employees, and they run Go services on top of Google infrastructure.
- verdverm 4y agoBeing tied to Google has very little impact on the technical implementation of go modules fetching, proxy, & sumdb. It is intentionally isolated so that request data is not part of Google's data business. Go uses git under the hood for these requests, so there are more complications. How do you cache or respect robots.txt when you don't actually talk to the servers?
- stefan_ 4y agoYou would think so, but has someone made a zip bomb with Git packs yet? ;)
- pwdisswordfish9 4y agohttps://kate.io/blog/making-your-own-exploding-git-repos/ https://kate.io/blog/making-your-own-exploding-git-repos/