3 ms·
I'm imagining the Github infrastructure folks cringing at this. The second-order effects of people reusing the infrastructure for a different purpose than initi
by AceJohnny2 9y ago
I'm imagining the Github infrastructure folks cringing at this. The second-order effects of people reusing the infrastructure for a different purpose than initially intended.
Like how they caved and provided github.io because people were using Raw (or some other feature of the repos) as a ad-hoc CDN anyhow.
In fact, I'm curious how much of their traffic is traditional git/repo view and how much is any of these "second-order" services.
- simonw 9y agoI bet they're fine with it. They have invested a great deal of engineering effort in building a notification system that scales - there are plenty of legitimate uses for that system that dwarf this clever hack in terms of traffic (issues with hundreds or even thousands of subscribers). If I were them I would be delighted at someone using my work in an unexpected and creative way like this - having users surprise you like this (provided it's not for abuse or spam) is one of the joys of software design. You could figure out the actual impact by counting the number of individual subscribers to all of the issues in this repo. My guess it's not even a hundred yet.
- tobylane 9y agoThey had problems with CocoaPods and Homebrew each using up several servers worth of CPU/network, and rather than ask those projects to change Github added functionality to make the workload lighter (an HTTP code for checking if there's an update to a repo).