eiii: On a second thought, could it be that I am not affected by this problem because I still use the last version of lgogdownloader before switching to the Galaxy API (
6f42fec)?
Is there any difference or advantage in using the Galaxy API or is it because GOG's non-Galaxy API will be switched off at some point?
There isn't much difference other than that --download-file doesn't work with Galaxy API at the moment but I'll see if I can also migrate that feature to Galaxy API in future.
My main reason for switching the downloader to Galaxy API was because the old API had some issues earlier.
Also the fact that the old API can be switched off any time was a major reason for switching to Galaxy API.
Yet another change to url formatting in "downlink" json response.
This time I knew it was coming thanks to my discussion with GOG support so I was prepared to fix any issues it would cause to lgogdownloader.
The reason for the change was issues that the previous formatting caused to Galaxy:
https://www.gog.com/forum/general/gog_galaxy_bug_1/page1 It was easier/faster for GOG to change the url formatting in API response than to release a patch for Galaxy.
eee1621 Galaxy: Fix getting file name (again)