00:42 <ckanbot> [CKAN] HebaruSan commented on issue #1817: And some counter-evidence; I ran [a script to fetch 21 big mod releases from GitHub in parallel](https://github.com/HebaruSan/KSP_Tools/blob/master/github-downloads-test), and it works just fine, with no 403 errors, even with retries turned off. I got a sustained 2 MB/s download rate across all of them, which is about the max for my connection.... https://git.io/vblVy

15:31 <ckanbot> [CKAN] HebaruSan commented on issue #1817: Some corroboration that it's server-side, and that we're not the only ones to have this problem...... https://git.io/vblum

15:53 <ckanbot> [CKAN] HebaruSan commented on issue #1817: @techman83, Netkan uses the token to access the API, but as far as I can tell it does _not_ use it for downloads, which is what we would need to fix the client. Netkan's downloads are done by DownloadAttributeTransformer and CachingHttpService, which do not have any github-specific auth token logic. https://git.io/vb8oV

19:05 <ckanbot> [CKAN] HebaruSan opened issue #2210: CKAN's GitHub downloads are breaking the rules https://git.io/vb8h7

19:52 <ckanbot> [CKAN] politas commented on issue #2210: Well, we're already on track for a point release with a spec update, so it's a good time to do this. We've had projects before to go through old metadata and update it, so adding GitHub download info isn't impossible. (Though it may be impracticable) Even if we just force the current releases to be repopulated, and all new ones going forward, we'll be ahead of the game, and if our trigger for the different downl

20:14 <ckanbot> [CKAN] HebaruSan commented on issue #2210: I would love to give users more info, however right now there is no useful info to give.... https://git.io/vb4Lm