It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
avatar
johnnygoging: It's a good thing I care enough about gog.com to start digging through the forums for things I'd missed.

Otherwise, I'd have thought gog had gone evil from the rap that this thing is now generating.
avatar
shmerl: Not evil (I suppose). Just not paying attention enough or too busy with other stuff. But if they won't answer soon enough, they'd be considered not caring about it (and that's just one step before switching to the wrong side in the whole DRM-free issue).
Games that were considered DRM-Free before all of this still had their code obfuscated so that they could not be run on Linux until someone started building something so that they could (Wine). Is that DRM too? Are all those DRM-Free games DRM'ed because they can't run on Linux?

gog has already explained this and it seems totally above board to me. I hope you get what you want and that gog makes the installers easy to use again. But really, I'd just be satisfied with it staying as it is, too. gog gets something and linux users do as well. experienced and motivated users can still use the installers with the workarounds, while someone who is likely to generate support requests and/or refund requests will use them the right way and know what they're getting into.

if you don't get a response, keep also in mind that gog must pick its battles and be wary of PR for things. if they don't respond it does not necessarily mean they are up to no good, but it could simply be a case of them not wanting to start pushing a new front when they still have the Galaxy client and the regional stuff to think about.
avatar
mqstout: Technically MaGOG and the Linux downloader client both violate that clause.
Exactly.
avatar
johnnygoging: Games that were considered DRM-Free before all of this still had their code obfuscated so that they could not be run on Linux until someone started building something so that they could (Wine). Is that DRM too?
No. Closed sourced-ness is not DRM. While closed sourced-ness as well limits what you can do, DRM is a limitation on top of that already. They are viewed as distinct types of limitations, even in the legal sense. While GOG claimed that they will remain DRM-free, they never claimed that they'll only sell open source games or make all their tools open source. And while there is a proposal for GOG to make their own Galaxy client open source to improve trust and security, they won't violate any promises if they won't do that. These topics can be somewhat related if you consider that it's easier to make such kind of client open source if it's DRM-free. DRM in such services by definition on the other hand requires hiding something from the user for limiting usability, that's why it as well relies on using something closed (i.e. you won't find any such thing open source DRM in anything like Steam or Netflix and etc. because of the very concept of it). But let's focus on the narrower issue of fixing the TOS.

avatar
johnnygoging: gog has already explained this
Explained what? There was no answer from GOG about this issue yet (TOS problems). So they didn't explain anything. Or if you mean installers, that wasn't a satisfactory explanation which can reconcile what was done with their DRM-free stance. In fact it didn't even talk about it at all. It only gave reasons why it was done. And GOG were proposed already how to address those reasons without resorting to any DRM-like methods.

avatar
johnnygoging: if you don't get a response, keep also in mind that gog must pick its battles and be wary of PR for things. if they don't respond it does not necessarily mean they are up to no good, but it could simply be a case of them not wanting to start pushing a new front when they still have the Galaxy client and the regional stuff to think about.
No response would mean some level of insincerity when their claims about DRM-free are used in their own PR. I.e. how can any of their words be trusted later if they avoid addressing criticism (either by resolving it or by refuting it as incorrect) which points out inconsistency with their own past claims about their core values?
Post edited January 07, 2015 by shmerl
avatar
shmerl: Not long ago you announced an upcoming update to your user policies and user agreement.

The new user agreement includes this paragraph about reverse engineering:

9.1 (b) We want you to be free to use your own GOG
content and back it up etc, but equally we need to have
legal rules to protect against misuse of the GOG content.
So (unless you have prior GOG permission) please don’t
modify, merge, distribute, translate, reverse engineer,
decompile, disassemble,
or create derivative works of
GOG services or GOG content – unless you’re allowed in
this Agreement or by the law in your country.
avatar
shmerl: It's quite problematic to reconcile with your official DRM-free stance in such form. Let me explain why. For that it's necessary to clarify some historic background about DRM and surrounding legal climate.

DRM proponents (such as and the like) weren't satisfied with the mere usage of DRM, since they quite quickly realized that it's completely ineffective to prevent any piracy. They devised a legal framework around it which forbids breaking DRM, and even publishing research on how to break it. Those are called anticircumvention laws ([url=https://en.wikipedia.org/wiki/Anti-circumvention]see here for the list of such laws in different countries). However they wanted much more than just preventing breaking DRM for infringing purposes. They wanted to forbid removing DRM for any legitimate purpose as well (research, interoperability, personal back ups, and other forms of fair use). I.e. they wanted indiscriminately to forbid it outright. Not that such framework prevented any piracy either - it didn't. But it gave them something else, read on.

When they attempted to present such laws to local parliaments, those initially refused since they could see that such laws are draconian and forbid legal fair use and as well can even violate common rights like free speech (when for example you publish research on breaking DRM). DRM proponents weren't deterred though. They turned to the World Intellectual Property Organization (WIPO) which was much easier to manipulate since it doesn't have a proper democratic process. They managed to put anticircumvention proposals into WIPO international treaties and agreements. Once they cemented those, they turned back to local parliaments and said: "Hey, you can't ignore your international obligations! You need to pass local anticircumvention laws!". And that undemocratic and corrupt backdoor scam worked. Most parliaments around the world passed those laws (like DMCA-1201 in USA). See here for historic overview of this corrupt process and those who were involved in that scheming.

Once DRM proponents got those laws in place, they started using them for all kind of nasty stuff from censorship to preventing competition, but that's really besides the point. The main point is that those corrupt laws are in place, and efforts to repeal them (like this one) are a very hard uphill battle.

So now with understanding the current legal climate around DRM, let's go back to GOG user agreement. It forbids to "reverse engineer, decompile, disassemble <...> GOG services or GOG content – unless you’re allowed in this Agreement or by the law in your country".

Now consider for example recent addition to GOG service - password on RAR packages in the installer. It hinders Linux users or anyone who would prefer to unpack them manually for example. So community looked into it, disassembling / reverse engineering the way to calculate those passwords. All that was fair use of those who pay GOG for these games. Sounds good? Not really according to this user agreement, and even the phrase about "allowed by laws in your country" doesn't help it, since as above laws in many countries forbid even fair use DRM breaking.

I hope you can see now that such language in the user agreement is problematic in the light of your DRM-free stance because of the sickening legal climate around DRM.

Can you please look into fixing that part of the user agreement somehow. For example add there "unless it's for the purpose of fair use" or anything like that, which would nullify restrictions placed by anticircumvention laws on such kind of activity?

It's somewhat ironic that you yourself benefited from reverse engineering and tinkering with old games, running them not in originally intended way and etc. Since it allowed you to bring them to modern platforms. Forbidding that now for your paying customers when it's fair use case would be strange at least, and not in the DRM-free spirit.

________________________
* Please vote for the corresponding wishlist entry.
100% agree.
http://www.gog.com/forum/general/release_bavernum_escape_from_the_pitb_629cb/post28

http://www.gog.com/forum/general/release_bavernum_escape_from_the_pitb_629cb/post30
It's good to see that GOG addressed the related issue of passwords in the installer. This makes this TOS problem less actual and more potential, but it's still something that should be addressed.
avatar
shmerl: This makes this TOS problem less actual and more potential, but it's still something that should be addressed.
Well, with the "modify" and "merge" terms it is for us already beyond potential implications & pretty real as these formulations prevents every user adaption like community patches and mods on the gog content, as also the creation of (legit) user created content.
avatar
shmerl: This makes this TOS problem less actual and more potential, but it's still something that should be addressed.
avatar
shaddim: Well, with the "modify" and "merge" terms it is for us already beyond potential implications & pretty real as these formulations prevents every user adaption like community patches and mods on the gog content, as also the creation of (legit) user created content.
Right, I was referring to the narrower scope. Modify and merge affect games (for example mods) more than GOG services really and I'm not sure what GOG can do exactly to fix that besides trying to argue with publishers (that's not going to be easy).

However clarifying the TOS with clearly marking areas related to GOG services and tools and areas related to publishers games and etc. is still useful. Right now it's all lumped together.
Post edited January 07, 2015 by shmerl
avatar
mqstout: Technically MaGOG and the Linux downloader client both violate that clause.
I don't know all the details re: MaGoG but, as far as I can see, all it seems to do is pull publicly available data that you could more than likely see via any browser's view source option :) I am not a lawyer or developer but I fail to see how MaGOG modifies or redistributes any GOG content :)
avatar
shmerl: I'm not sure what GOG can do exactly to fix that besides trying to argue with publishers (that's not going to be easy).
but then those publisher can have their own EULA's on top of the GOG one. Quite a few already have those anyway.

And then there are games like "Beneath A Steel Sky". A game which is freely available, which states in its readme that you are free to modify, even distribute, the game. And GOG still slaps its restrictive EULA on top of that.
That surely is fixable.
avatar
mqstout: Technically MaGOG and the Linux downloader client both violate that clause.
avatar
JudasIscariot: I don't know all the details re: MaGoG but, as far as I can see, all it seems to do is pull publicly available data that you could more than likely see via any browser's view source option :) I am not a lawyer or developer but I fail to see how MaGOG modifies or redistributes any GOG content :)
May be since GOG site's code isn't published under open permissive license, analyzing the code (i.e. parsing it and etc.) even if it's just HTML+JavaScript can be considered reverse engineering. But I'm not familiar with how it works for sites really.

We are mighty lucky that Internet was built on open formats like HTML. Imagine a world where closed source approach would have been used for it all way through... No MaGOG for you in such case. And some still attempt to poison HTML with DRM as well (Netflix and Co). But that's really a major off-topic.
Post edited January 07, 2015 by shmerl
avatar
shaddim: Well, with the "modify" and "merge" terms it is for us already beyond potential implications & pretty real as these formulations prevents every user adaption like community patches and mods on the gog content, as also the creation of (legit) user created content.
avatar
shmerl: I'm not sure what GOG can do exactly to fix that besides trying to argue with publishers (that's not going to be easy).
No, this is a misinterpretation, this has nothing to do with copyright holders, this are the TOS of GOG alone. The copyright holder specific formulations should be handled specifically per individual GOG content with a specificly adapted EULA (e.g. a EULA for the EA content, a EULA for Disney content etc).

avatar
shmerl: However clarifying the TOS with clearly marking areas related to GOG services and tools and areas related to publishers games and etc. is still useful. Right now it's all lumped together.
Yes, a separation of concerns (handling "GOG content" separated from "GOG services and software") would simplify this enourmously an is required & would allow mor specific better fitting formulations for both use cases.
Post edited January 07, 2015 by shaddim
avatar
immi101: but then those publisher can have their own EULA's on top of the GOG one. Quite a few already have those anyway.
Not just quite a few, nearly all of them actually (even Warsow actually :) ); I have to check BaSS but I suspect he probably have the same "default" EULA.
avatar
shmerl: I'm not sure what GOG can do exactly to fix that besides trying to argue with publishers (that's not going to be easy).
avatar
immi101: but then those publisher can have their own EULA's on top of the GOG one. Quite a few already have those anyway.

And then there are games like "Beneath A Steel Sky". A game which is freely available, which states in its readme that you are free to modify, even distribute, the game. And GOG still slaps its restrictive EULA on top of that.
That surely is fixable.
Yeah, right now it's somewhat confusing. There is service TOS, and individual EULA for each game. Yet what they are talking about is obviously overlapping now. More modular approach there could be helpful.
avatar
immi101: but then those publisher can have their own EULA's on top of the GOG one. Quite a few already have those anyway.
avatar
Gersen: Not just quite a few, nearly all of them actually (even Warsow actually :) );
i was speaking of games with different EULAs then the "default GOG" one. Games from EA for example.
avatar
immi101: i was speaking of games with different EULAs then the "default GOG" one. Games from EA for example.
Ok, I thought you are talking about "GoG new ToS" vs "Per games EULA".