It appears that the Facebook redirect to browser problem is no longer happening here for me. Not enough testing of it to conclusively declare it as fixed or not though. From searching the forums it appears this problem comes up from time to time so I'm hesitant.
Either way, it appears to be asleep for now.
skeletonbow: With respect to the Facebook usage, the website links to GOG's Facebook page in the page footer, which doesn't show up in Galaxy specifically, but they are also apparently using the Facebook Connect service, which allows people to log on to one website using their login credentials of another website. An increasing number of websites are providing this single sign-on type service nowadays, so you can for example "log on to GOG using your Facebook account" or similar.
richlind33: Doesn't that diminish your security, like using the same pass on multiple accounts?
Yes, the nature of single sign-on as a technology is a compromise of gaining convenience at the expense of security. That is why it is generally offered as an option to people rather than something mandatory they have to use. The customer or web site visitor gets to decide for themselves whether they prefer the convenience of single sign-on, or the security of having separate logins on every website and maintaining them all.
I prefer separate logins almost everywhere, but there are some sites where you kind of are forced to use single sign-on, such as steamgifts for example.
I don't have a problem with GOG offering single sign-on feature on their website though as it is not an uncommon feature and nobody is forced to use it. It would be nice if any features added to the site or modified/changed in any way over time end up getting more internal and private external test coverage before being rolled out to the entire customer base though. IMHO the problem here isn't that GOG allows single sign-on with Facebook, or anything to do with Facebook at all, but rather that untested code or configuration or whatever got rolled out to everyone without enough quality/stability testing.
At the end of the day stuff happens though despite one's best intentions so they don't deserve to be raked over the coals for it either. :) I do hope that they make internal contingency plans for these things when they happen though and put measures in place to try to assure that the same problems can't occur again in the future. We all make mistakes after all, but if we can avoid making them more than once then that is a good thing. :)