2 ms·
That is a very specific scenario, but agreements can be made to release software in exchange of loss of warranty and liability protection: I give you the code a
by squarefoot 9y ago
That is a very specific scenario, but agreements can be made to release software in exchange of loss of warranty and liability protection: I give you the code and from that moment (either if you use/modify it or not) you lose all warranties and can't sue me even if the product burns your house and kills all your kittens.
- ouid 9y agoyou can't release all liability.
- mikepurvis 9y agoLosing the warranty is a given once it's been modified. And obviously before electronic control, there were still a hundred ways you could break any given device and have it generate undeserved bad press for the manufacturer. But I contend that the scope of things that can go wrong when you mess with the software, and the degree of damage that can be done, are both worse than with purely mechanical modifications. There's huge potential for unintended consequences, and bad press puts the original manufacturer in the awkward position of having to disavow their own product, bearing their symbol, because "the user modified it in an unsupported manner." All this gets even worse if the manufacturer actively supplies source code and an SDK for making such modifications. How do you delineate supported vs. unsupported mods?