shmerl: What's the story with Linux games then? Will you start supporting Galaxy for them on the backend (i.e. provide Linux builds through Galaxy API) or you will again treat Linux users as second class citizens, forcing us to only use the browser (since lgogdownloader won't work either for Linux versions if I understand correctly, once you decommission the downloader Web API).
lgogdownloader supports Galaxy API already, but it's now only exposed for Windows builds of games. Linux builds are excluded from it. So if you don't plan to enable Galaxy API on the server for Linux builds, this announcement sounds like a pure regression for Linux users.
Removal of downloader api shouldn't affect lgogdownloader much.
lgogdownloader has used galaxy api for getting the download links since version 3.3 (only --update-check and --download-file options were using the old api)
I really need to make a new release sometime soon so people using "stable" versions of lgogdownloader won't be affected in any way.
Currently version 3.5 still uses old api for --download-file option but this has been changed to galaxy api in git.
I switched the last parts of downloader api usage to galaxy api in
a884e8c And then removed the downloader api and all references to it in
42c7188 and
8829f44 so the current git version uses only galaxy api.
The api for "installing" games (downloading individual game files) doesn't have server side support for Linux at the momen but lgogdownloader should start using without much problems as soon as GOG enables it.
That is if my assumption about the platform name used in the url is correct (using "linux" in url for linux builds)
edit: gog forum formatting for urls really sucks