Isn’t that just a feature of github though? They don’t want to be used as a free CDN so they’re going to throttle download speeds. It just makes sense.
I think the biggest bottleneck is once again manpower. We don’t really have the free time to figure out how to set up a cdn, and how much it would cost, and how it would integrate into our stack.
If I had infinite time and money I’d love to do the following:
- Enable a CDN for patch distribution
- Fix our awfully inefficient distribution method so it only gives you the data you don’t already have
- Integrate a proper version manager into the client so you never have to download the same patch twice, even if you watch a lot of replays on different patch versions or on fafdevelop.
Sadly my money and time are only finite and already allocated to many FAF projects like TMM.