In the past you said that you plan to publish Galaxy protocol specification, to enable creating community implementations of the client. Do you have any ETA when that will happen? With Galaxy entering beta, the protocol is probably already quite ironed out?

Thanks.
________________________
* Wishlist entry.
* Previous wishlist entry
* Galaxy bug tracker ticket.

Uh, Galaxy is still in alpha...

I think, maybe, you missed it.

Indeed I did. Mea culpa.

I kinda expected that they would automatically update the alpha client to beta at the same time though. Which hasn't happened for me.

I second this concern.

I own over 2/3rds of GOG's catalog (and, as the opportunity presents itself, I've been re-buying stuff I already had from Humble Bundles to bring that total closer and closer to 3/4 of GOG's catalog) but I have a very strict policy that:

1. Only games may be closed-source on my Linux box, since their development model hasn't been proven profitably compatible with open-source yet.
2. I must have a DVD+R (soon to be BD-R) backup of the exact build of a game I'm playing which can be successfully used to install and play the game to completion on an airgapped PC or LAN.
3. Package managers (like Galaxy) must be open-source because they, by their very nature, it's expected that they'll need access with more potential for abuse.

As such, since it's unlikely Galaxy will be made open-source, I need assurance that Sude will have the information he needs to update LGOGDownloader for the new API.

Hasn't really happened for anyone yet. It seems alpha users may not get the beta update until sometime tomorrow, according to blue posts in the alpha client thread.

I'm also interested in experimenting, and writing an open GOG manager client (with at least some Galaxy functions) from scratch in Rust (it's a good exercise for learning the language). For that, protocol spec is needed at least. Otherwise one will have to spend a lot of time reverse engineering the closed Galaxy client.

I don't think I'll delve into any purchasing functionality, to avoid messing with more security sensitive issues. But something for downloading and incremental updates (of already purchased content) would definitely be an interesting thing to make. If anyone is interested in participating in this project - feel free to comment.

I'd definitely be interested once I can find the time and I can contribute some algorithms (to be translated from their Python implementations) for heuristically adding already-on-disk games to the launcher.

(At the moment, my Rust experiment project is a Rust port of gif.py to see whether the Python overhead is statistically significant in a simple I/O-bound application.)

I support this as I did it in the past. But of course open sourcing Galaxy would be the best approach.

"The Galaxy Protocol" is a good name for something.

According to GOG support, it's better to use Galaxy bug tracker for this: http://mantis.gog.com since that's where Galaxy developers discuss its progress. I'll file an issue there about publishing the protocol spec.

http://www.gog.com/forum/general/phrases_seen_in_gog_forums_that_would_make_good_band_names

I submitted the issue here: http://mantis.gog.com/view.php?id=1922
(you need to participate in the beta program to use the issue tracker).

Was thinking of a story or movie, but band name is fine.

I also opened a wishlist entry: https://www.gog.com/wishlist/galaxy/publish_galaxy_protocol_specification