Who is liable if software causes intentional errors when used in a pirated/unlicensed fashion? In this Academia question comments reads : cracked software has hard-to-detect anti-features bug (example cracked version of a engineering software may use in computations slight less material resistance, so that buildings created with it have a greater cost, or just more material resistance so that buildings you create with it just implodes because computations are wrong My question is: If a building collapses and the root cause is an intentional math error by unlicensed software can the software maker be charged with something? I'm also interested if the builder could use this as a defense.
I think this is a lot like this question Liability for poisoning food one expects to be stolen because you are causing harm to someone/something when they are using your things without permission. That question says that if you expect someone to do something with something that you have purposely made wrong then you are legally responsible for the effects.
Your question mixes up two different aspects of intellectual property. From a copyright point of view, it is perfectly legal to reproduce the features of a one piece of software in another. The functionlity of the software is not copyright (although the detailed look and feel of the user interface might be). However you ask if you, as an employee, can do this by &quot;looking into the code of software X&quot;. Presumably by doing this learn something of the organisation and algorithms used. Even if you avoid direct copying, you are likely to have learned trade secrets of your employer, and publishing these is at least a civil tort in the US, and in some states a crime.
Company B has created a derived work from company A's copyright-protected work, so yes, B has infringed on A's copyright. It might be difficult for A to prove it, however, so B might get away with it, but it's still infringement. On the other hand, if B creates software that behaves like A's through reverse engineering, that is, by examining the program's function without examining its code, then they will not have infringed the copyright in the code.
If you aren't including those libraries, then yes because it's entirely your own work. If you are publishing those libraries, then no because their licenses will limit how you can do that. GPL's and MIT's main features are restricting how you can distribute software that includes the licensed code, and they don't allow the &quot;do whatever you want&quot; of public domain.
That depends on how you get the ingredient list. If the list is published and not protected by a patent, then anyone is free to use it in making the same or a similar product. If the product is patented and the ingredient list is covered by the patent, and the patent is currently in force, then making a similar product would probably be patent infringement, and the patent holder could sue and collect damages. If the list is secret, and has been protected as a Trade Secret, and if the would-be imitator gets the formula improperly, then the owner of the formula would have valid grounds for a trade secret lawsuit and to collect damages in that suit. Improper means would include breaking into the owner's files, or inducing an employee or contractor to violate a confidentiality agreement. But analyzing the product and figuring out its composition, a form of reverse engineering would be perfectly proper, and would give the formula owner no claim. Similarly, if the owner was careless and allowed the formula to be disclosed, the imitator would have done nothing improper. So the outcome depends on the details of facts not stated in the question.
The idea for an app is not subject to copyright. Only the artifacts of the app itself (sourcecode, images, texts, sounds, etc.) can be. So if one only copies the idea and creates their own version of all the other assets, then they are not violating copyright. However, in some cases, ideas can be subject to patents. But patents on software are tricky. First of all, only new ideas can be patented. When a supposed new idea was already published before, then that's called &quot;prior art&quot; and you can not patent it. Then getting a patent means a lot of investment in money and time (which is very different from copyright which you get automatically the moment you make something copyright-worthy). So not everything that could theoretically be patented gets patented. And then, many jurisdictions do not recognize software patents at all, and those which do have different limits on what is and is not patentable when it comes to software. This means patents are rarely a concern when copying the app idea of someone else, but not never. And another possible concern is the third pillar of intellectual property: Trademarks. This protects the name of the app. Trademark law oversimplified forbids to create a competing product with a name which might confuse customers. So if you created StevesSuperCoolAppForCoolPeople and I create StevesSuperCoolAppForCoolPeople - Simplified Edition, then I would be violating your trademark, because my product name sounds as if it was your product, when it is in fact an unrelated product with a similar purpose.
There is no provision for automatically relicensing infringing works (for example, distributing a program that contains parts covered by the GNU GPL and that is therefore a derived work will not automatically place the infringing program under GPL, even if that is the expected way for derived works to comply with the license. Instead, the derived work becomes at the very least undistributable, as there are competing copyright holders that disagree.
The difference between commercial and non-commercial software use is about as clear as it gets, outlined by the definitions in the license above. One makes money, the other doesn't. There is no gray area. Your intent or expectations for a project may seem to alter the difference between the two and add a gray area in your mind, but they don't. Once you are a commercial user, buy a commercial license and/or upgrade the non-commercial license to commercial. That's the legal angle; and what is illegal and what is unethical are not always the same. If you still feel like your intent does make a difference and you feel unethical about using a non-commercial license - because you are building a community and hoping/planning on making money - buy the commercial license to begin with.