Johny.: [...].
Secondly - Cloudfront is a "cloud" service to store assets and a lot of developers use it. GOG.com may have a lot more dependencies from external domains in the future, because why not?
[...].
HypersomniacLive: Must admit, that's one hell of an irrefutable argument - yay, why not have our site and service working properly depend more and more on the uptime and proper functioning of third parties?
It's a normal and good thing that you use third party stuff in your projects - on web backend, on web frontend and in native applications.
Here, with this single one, the difference is just the domain on which it is hosted.
(it's considered faster to load assets asynchronously from common domains, but not everybody agrees on that)
Johny.: [...]
Third thing is log-in doesn't work because whole JavaScript init crashes, not because exactly "log in" function needs this cloudfront script.
[...]
HypersomniacLive: That still sounds like the failure has something to do with the transition to cloudfront though.
Do you have an ETA for fixing this?
If you'll block our javascripts - they can't run. :)
Logging in (opening the modal) requires javascript to run properly, and they'll crash if you block part of them.
Johny.: [...].
I'd advise you to not block it. :)
[...]
HypersomniacLive: I'm sorry, is that serious advice? Because I'm sure we're all aware that blocking it makes logging in impossible, aka deprives one access to their account and collection.
Yes - it's a serious advice. I don't see any reason to block it personally.
If you decide to block scripts, you should know that you won't be able to use any scripts until you unblock them.
edit: If you wish, you can always chat me about that.