31–40 of 225 posts
Did you try go get in contact with them directly and clarify it? Did you talk to a moderator?
Besides that, you are hosting code right? How is 70gb of traffic a DDos?
I have to say, traffic numbers like you posted, would not concern me at all. I'm very curious why your underlying git usage can't do better caching.
Earlier quoted context omitted.
Yeah, but that's not an option according to the article. > I can’t blackhole their IP addresses, because that would make all Go modules hosted on git.sr.ht stop working for default Go configurations (i.e. without GOPROXY=direct)
That’s more of a “won’t” than a “can’t”
If 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, s…
(These kinds services are also supposed to rate-limit their requests.)
Earlier quoted context omitted.
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.
Have you not tried to get in concat with anyone else before? "mysterious reasons" Did you try go get in contact with them directly and clarify it? Did you talk to a moderator? Besides that, you are hosting code right? How is 70gb of traffic a DDos? I have to say, traffic numbers like you posted, would not concern me at all. I'm very curious why your underlying git usage can't do better caching.
As noted in the article, he did, and then Google banned him without warning.
There is a very simple way to get them to stop sending the .5 qps that is described as a ddos. The linked bug show another user successfully saying "please opt me out", and Google building the feature to do that in a week. Drew has for some reason chosen not to ask for an opt out, even though it appears trivial and would probably be fixed by the weekend if he asked for it.
Earlier quoted context omitted.
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.
Have you not tried to get in concat with anyone else before? "mysterious reasons" Did you try go get in contact with them directly and clarify it? Did you talk to a moderator? Besides that, you are hosting code right? How is 70gb of traffic a DDos? I have to say, traffic numbers like you posted, would not concern me at all. I'm very curious why your underlying git usage can't do better caching.
> Did you try go get in contact with them directly and clarify it? Did you talk to a moderator? As noted in the article, he did, and then Google banned him without warning.
Earlier quoted context omitted.
Yeah, but that's not an option according to the article. > I can’t blackhole their IP addresses, because that would make all Go modules hosted on git.sr.ht stop working for default Go configurations (i.e. without GOPROXY=direct)
That’s more of a “won’t” than a “can’t”
Earlier quoted context omitted.
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?
If you're pulling down a packge with npm that isn't part of the npm registry, the request isn't going through a Microsoft proxy.