> It sounds like DeVault let them know their proxy was hitting his service too hard, and they immediately responded by saying they could dial it down I'm not i

> It sounds like DeVault let them know their proxy was hitting his service too hard, and they immediately responded by saying they could dial it down I'm not ignoring that Drew complained and they offered to dial it down. That's a reasonable response if it were an isolated case. The problem is that it isn't an isolated case. This is how the module cache works, which means it is doing that kind of load against other module sources too. If you're going to impose these resource demands on others then they should be managed for everyone affected not just the one who complains about it. - Repeatedly pulling an entire repo over and over again is an antisocial act that is unfairly imposing bandwidth/CPU costs on third parties - They should not expect every impacted party to obtain an opt-out individually because of unasked-for extra resource demands - The system that excessively polls is broken, not its victims