Posted June 06, 2014
shmerl: Now that GOG confirmed that the updater client is coming (including for Linux) it's time to vote for it to be open source:
https://secure.gog.com/wishlist/site/release_the_future_gog_updater_client_as_open_source
I'll create a separate thread and request to make the API of the client open as well. In the worst case if GOG won't open their client, community can create an alternative one. Without an open API that would be much harder.
gooberking: Can I ask for you to define specifically what you are requesting/hoping for? I'm not sure what the client being OS would accomplish. Partly because we don't really know anything about it. https://secure.gog.com/wishlist/site/release_the_future_gog_updater_client_as_open_source
I'll create a separate thread and request to make the API of the client open as well. In the worst case if GOG won't open their client, community can create an alternative one. Without an open API that would be much harder.
I feel a bit more interested in the concept of an open API for it. More so if there was some sort of push to try and create with it some sort of open specification for doing a lot of the common client tasks like achievements and social feature data. Sort of an Open Document style thing so general client tasks could be abstracted, and client agnostic, as well as defining some language to talk amongst themselves. I doubt any other client makers really care about working towards such a thing or how viable such a thing would be.
1. Source code I (or a Debian/Ubuntu package maintainer) can inspect and build myself to feel secure in the belief that it does exactly what it says on the can and nothing more.
2. The ability to patch away bugs and patch in features if we don't want to wait for GOG to do it.