News for hackers. Stuff that matters.
Re:Medium's Policies and Guidelines by sandworm101 on Friday February 26, 2016 @11:15PM (#11186038)
>> Arguably, if your code is hosted by a third-party, the legal document is the least of your problems.

It depends on who you talk to. The legal dept would say that code can be replaced. The coding people similarly look down on contracts as paper anachronisms. Which matters more depends on the situation. The one that matter in any moment is whichever has been attacked most recently.

I would say that errors in a contract are more expensive to fix than code. A change to code can be patched once detected. But drop a key line from a contract, perhaps the limitation on jurisdiction or arbitration, and you might be stuck with costly litigation even if you make a change asap.

Re:Medium's Policies and Guidelines by lazaroclapp on Friday February 26, 2016 @11:44PM (#11186105)
But would you be actually responsible for it if someone changes your contract without your knowledge? Even if you are the one serving it?

So, if I went to a car dealership with my own modified contract in hand, and surreptitiously changed it for the one being put forth by the dealer and got him to sign it, would he be bound by that contract? (independent of whether or not I am committing a crime in that scenario)

Re: The code can be replaced. Sure, I am not worried about losing code at rest, for anything non-trivial you should have plenty of copies of a git repository anyways. But if modified code gets deployed, then suddenly you can take actions that might cost human lives or leak sensitive data and that genie can't be put back in the bottle, at any cost.