alt Hacker News> What are the legal consequences of not releasing a functioning server if for some reason you can't?
How about "the government forces you to release the code"? That's seems fair.
Unless you hid your source code in USB drives under your bed, the government can probably just force GitHub (or similar )to release it. I bet they've got it backed up.
Replies
Ab1921 in california doesn't propose this. Its either an offline copy, a copy that works without servers, or 100% refund. Basically patch or refund.
I can't wait to see "you haven't met your patch obligations" on a balance sheet and a full indie game being underwater
So you're assuming game devs write every line of code in their server infrastructure. First, could be using a third party library you have license to use on a limited number of machines that make up your backend servers. Second you could be paying for third party API access to something like snowflake.
You either have to rip out the code (which may or may not break the server, but still requires developer time to do) or write replacement code which likely takes even more dev time to do or you would have done it instead of paying for the library/access to the service.
And how do they force release of all the proprietary dependencies? Overriding contract law is a hell of a lift, and a terrible precedent.
The whole "Stop Killing Games" movement is deeply misguided, and most of the people supporting it have absolutely no clue about how software or anything computer related actually works.
And you're... in favour of this kind of doctrine...?
The government will release it with all the copyrighted code and assets that's owned by a bunch of third-parties?
Ex. if I license my artwork, music, characters, code library, etc. to a game developer and they don't create a legally releasable version of their server, then the government will forcibly break our licensing agreement and I just get screwed?