fr33kSh0w2012: Well good for you, I suppose (Pretty bad when customers have to make something FOR their store of choice)

rtcvb32: That almost sounds like 'It's pretty bad when customers/gamers have to mod xyz Bethesda game to make it work correctly'....

fr33kSh0w2012: Well good for you, I suppose (Pretty bad when customers have to make something FOR their store of choice)

paladin181: You realize that GOG 2.0 is almost entirely dependent on customer created additions for library integration with other services? GOG isn't competent enough to program it themselves. So we get community integrations that may or may not be maintained, that may or may not work efficiently, and may or may not contain gigantic security risks that no one is actually verifying before they are made available for use.

muntdefems: The downloaded installers don't keep the original filenames and are renamed to their library titles (e.g. "Momodora: Reverie Under the Moonlight" instead of "momodora_reverie_under_the_moonlight_1_062_24682.sh". Is that intentional?

Gekko_Dekko: Is it still a thing, or there is an option to toggle such behavior now?

Gekko_Dekko: did anybody already compare this with gogrepopy, in terms of speed?
Also it could be quite handy to have ability to handle already existing gogrepopy library (in case its not a thing yet).

Another question - how does it handle login information? E.g you need to type it in manually each time, or it remembers login/password (if yes - does it happen in hashed form or as plaintext?) or cookie, or...?
Do all connections happen only via https, or there are exceptions?

hickmannico: There is an option now, yes. -O toggles preserving the original file name.
hickmannico: Everything should be happening over HTTPS, and you can log in either by pasting in a token from your browser or with username/password, although the latter is unreliable. The only thing that gets stored is an Oauth token, which is remembered.