Hacker News Reader

Comment by tssva | Hacker News Reader

There is a refresh exclusion list which you can request your site to be added to. The proxy will continue to process requests for modules from your site but will not perform the automatic refresh which caused issues for Sourcehut. The Go team extended an offer to add Sourcehut to the list if a request to do so was made. The request never came and instead Sourcehut blocked the proxy.

View on HN

"Opt out of me DoSing" you is not legit behavior -- especially when the victim has raised it with you multiple times, suggested fixes, and you have then blocked them from communicating in your issue tracker.

That's some really entitled thinking on the part of the Go team at Google, and it's sad to see people stanning for them.

They should have them add a file to their web service at a path of "/i_want_to_live.txt" to indicate not to DoS the server.

If an amount of traffic that nobody else even notices brings you to your knees, you're doing something wrong. Go could be far more efficient but pointing at this and calling it a DDoS is silly.

I called it a DoS, not a DDoS.

Technically it'd be a DDoS, but however distributed it is makes no difference to what we're talking about here. If you could respond to substance, it'd be appreciated.

You are correct, it was more a complaint about resource usage and costs, as opposed to a breakage of the src.ht service.

Does every site need to personally request they not be DoS attacked?

Reply on news.ycombinator.com