Google has been DDoSing Sourcehut for over a year
drewdevault.com
Google has been DDoSing Sourcehut for over a year
1–10 of 225 posts
Re: Google has been DDoSing Sourcehut for over a year
#2This is still occurring? I remember the original incident and just assumed that Google had sorted it out with Drew/Sourcehut.
This is absolutely shocking behaviour, and I’m mortified at the precedent that it sets.
Re: Google has been DDoSing Sourcehut for over a year
#3The fact that a programming language calls home to by Google by default should make it a non-starter for most sane developers. The fact that it calls home so it can DDoS other sites is low-key hilarious. And you'd think Google would know how to like... operate an efficient CDN, perhaps?
Like, if this was managed by a competent company, you'd think this service would be akin to putting Cloudflare in front of your servers: It should minimize the heck out of your traffic because Google is able to cache it and serve it to the masses more efficiently. But it's Google, so it Googles.
Being blocked from the issue tracker for not being okay with being DDoS'd is peak Google. I am sure you were accused of a Code of Conduct violation, because declaring a CoC violation is much, much cheaper than fixing their infrastructure.
Re: Google has been DDoSing Sourcehut for over a year
#4> The Go team holds that this service is not a crawler, and thus they do not obey robots.txt
This seems wrong. I guess I always assumed that robots.txt applied to non-humans.
Re: Google has been DDoSing Sourcehut for over a year
#5The fact that a programming language calls home to by Google by default should make it a non-starter for most sane developers. The fact that it calls home so it can DDoS other sites is low-key hilarious. And you'd think Google would know how to like... operate an efficient CDN, perhaps? Like, if this was managed by a competent company, you'd think this service would be akin to putting Cloudflare in front of your serv…
Are you going to get upset at node for calling home to Microsoft (npm owned by github owned by microsoft) when using the supplied package management too?
Re: Google has been DDoSing Sourcehut for over a year
#6The fact that a programming language calls home to by Google by default should make it a non-starter for most sane developers. The fact that it calls home so it can DDoS other sites is low-key hilarious. And you'd think Google would know how to like... operate an efficient CDN, perhaps? Like, if this was managed by a competent company, you'd think this service would be akin to putting Cloudflare in front of your serv…
Are you going to get upset at node for calling home to Microsoft (npm owned by github owned by microsoft) when using the supplied package management too?
I mean, I strongly just feel the npm ecosystem is a dumpster fire of sadness. Though there is a fundamental difference in that if you use NPM, you are choosing to download packages from NPM. But if you specify a bunch of repos you want to download Go packages from, and you get them from Google anyways, that's pretty uncomfortable. Especially if Google is in turn also DDoSing the repos in return.
Re: Google has been DDoSing Sourcehut for over a year
#7The fact that a programming language calls home to by Google by default should make it a non-starter for most sane developers. The fact that it calls home so it can DDoS other sites is low-key hilarious. And you'd think Google would know how to like... operate an efficient CDN, perhaps? Like, if this was managed by a competent company, you'd think this service would be akin to putting Cloudflare in front of your serv…
Are you going to get upset at node for calling home to Microsoft (npm owned by github owned by microsoft) when using the supplied package management too?
Yes. I find all of the modern "always connected, always call home" behaviors quite annoying in my programming tools.
But, to be fair, Node was a dumpster fire long before being bought by Microsoft.
Re: Google has been DDoSing Sourcehut for over a year
#8The fact that a programming language calls home to by Google by default should make it a non-starter for most sane developers. The fact that it calls home so it can DDoS other sites is low-key hilarious. And you'd think Google would know how to like... operate an efficient CDN, perhaps? Like, if this was managed by a competent company, you'd think this service would be akin to putting Cloudflare in front of your serv…
Are you going to get upset at node for calling home to Microsoft (npm owned by github owned by microsoft) when using the supplied package management too?
How could node not do that? NPM hosts all the packages so of course it does.
Re: Google has been DDoSing Sourcehut for over a year
#9Wait... Why not black hole them? Make it their problem and they'll eventually do the correct thing.
Re: Google has been DDoSing Sourcehut for over a year
#10If it were me, and I wasn't willing to just block the traffic, I might just set a 128 kbps limit on it and call it a day[1]. Eventually, the other side will figure out that their fetchers are all backed up and work out how to do their job without burning so much bandwidth.
[1] Yeah, that can be a bit of a pain to setup depending on the server settings, but some people have to pay for bandwidth and server resources, so it's probably worthwhile.