Live data from Hacker News

Google has been DDoSing Sourcehut for over a year

drewdevault.com

221–225 of 225 posts

Re: Google has been DDoSing Sourcehut for over a year

#221
post #82

Earlier quoted context omitted.

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 the…

You would think so, but has someone made a zip bomb with Git packs yet? ;)

https://kate.io/blog/making-your-own-exploding-git-repos/

Re: Google has been DDoSing Sourcehut for over a year

#222
post #157

Earlier quoted context omitted.

Or you could mess with a random percentage of the requests: tarpit them, drop random packets, reply with malformed answers etc. If you keep the percentage low they might have a fun time debugging :)

While amusing, responding in this way seems overly antagonistic/escalatory. i.e. the behaviour of a poor citizen of the web. It also would be likely to result in an increased number of requests? Drew's actions so far (as far as I can tell) are not only inoffensive/reasonable but overtly good-willed and presumably result from a considerable amount of effort.

As if Google's response (that they, the largest tech company in the world, can do nothing about it) wasn't antagonistic…

Re: Google has been DDoSing Sourcehut for over a year

#223

Earlier quoted context omitted.

That’s more of a “won’t” than a “can’t”

You could easily proxy around it. It's inconvenient to set up, but it can definitely be a set it and forget it thing.

You can set GOPROXY=direct in your environment and not have to deal with Google's scumbag proxy service in the first place, but nobody seems interested in making this the default behaviour.

Re: Google has been DDoSing Sourcehut for over a year

#224

Earlier quoted context omitted.

It speaks to why he might have been banned, which is the context of this thread.

We shouldn't have to speculate as to why he was banned, as the CoC requires communication to him about why. If they're breaking CoC to get rid of the guy (and likely because the CoC prevented them from doing so in the past), it's hard to justify no matter the reason. And to be frank, filippo's contribution to this thread places a clear reason why- drew was incredibly rude in the second link, but his arguments were no…

Because Google's full of assholes who just don't give a damn that the rest of the world doesn't have the unlimited bandwidth and storage of the Big G.

Re: Google has been DDoSing Sourcehut for over a year

#225
Athens, a self-hosted free Go proxy implementation, implements rate-limiting for GitHub (with a pretty horrific Github-specific behavior). This means GitHub does implement rate-limiting to cope with aggressive Go proxies.

https://github.com/gomods/athens/blob/723c06bd8c13cc7bd238e6...

Food for thoughts.

Post reply on HN