timppu: Well, what others have said, apparently Galaxy uses static.akamaitechnologies.com, even for offline installer downloads.
This is the first I have heard about that, or at least don't recall it. Thanks for the information.
timppu: I am unsure why GOG wants to use two different sets of servers, it feels silly to keep also the same offline installers on two CDN providers' servers. Maybe the browser downloads interact so differently with the servers than Galaxy so it was better to separate them, or Galaxy needs extra features that Fastly doesn't support, or something.
Doesn't make much sense to me, unless GOG are deliberately providing a poorer downloading experience outside of Galaxy to encourage its use. Seems odd to pay extra to do that though.
And I wonder if it is always the case that Galaxy uses that different service rather than Fastly, or whether it can also use Fastly, and does that depending on where you live etc.
EDIT - I am now having a recollection, that during the CDN crash (or whatever it was), that GOG mentioned something about a fallback service, and maybe that is what Fastly is for. They may also use it to spread the load I guess or to keep that service actively in use or both. timppu: Do I recall right that with e.g. lgogdownloader (which is a bit similar mass download tool as gogrepoc.py) it was possible to download offline installers using the "Galaxy API", possibly meaning it would use the Akamai servers for download, as if you were downloading with Galaxy? And gogrepoc.py (still) uses the older browser API, ie. GOG thinks it is a web browser?
Maybe I should try out if lgogdownloader gives me much faster download speeds than gogrepoc, I think that might prove it right.
I think that would be an interesting exercise, so please share the results of your testing.
I don't have a current Linux distro to test for myself, only a somewhat ancient Live version of Mint on a USB stick. I have thought about attempting to compile lgogdownloader into an executable (Python script to EXE file), but not yet bothered. I've done that before with Legendary, to some success, and even with a script for calibre more recently, that works well.
What I have tried out though, is curl.exe on its own (single thread), though using the browser links, so still using Fastly, and that is no faster than using gogcli.exe or my browser. I've also paired curl.exe with aria2c.exe and managed to get a much better speed due to aria2 supporting multiple threads per file, though it seems 5 threads are the maximum. I've had better success with Free Download Manager 5, either on its own using browser clicks and an addon, or more recently coupled with curl.exe, once again using browser links. I get those browser links via a manifest created and updated by gogcli.exe.
I've even had better speeds using curl.exe to simultaneously download a file in separate parts, which I then combined afterward. That is not probably recommended though, as it means doubling drive space use during that process.
