Master spec-repo rate limiting post‑mortem

I also find this usage to probably be viewable as abuse, but clearly GitHub has chosen to continue allowing it, even as it has caused them issues like this. I think for them, it has provided some interesting insights about their infrastructure and areas they can optimize (not necessarily because they are lacking). Besides the work they put into this, I can think of at least one other noticeable change they made, which was how the repo pages displayed huge file lists (CocoaPods used to have a massive list of files at the root).

So yes, it's probably not great, but it has given GitHub some fun inf. challenges to build to. If it was something they felt like they couldn't handle, I'm sure they'd politely ask them to hop off their platform ;)

One could assume that they are either simply lazy or incapable of designing such a system on their own. By taking a look at their "index" which consists of one giant directory in a single GitHub Repo, one could indeed argue that it's a mixture of both.

There are so many (big) companies out there using cocoapads for their app development, getting a few to sponsor the hosting bills should be more than doable. A lack of funding is really no excuse.