What are the rights of the software owners if their software is used to make money? Let's assume that I have an iPhone and I tell how to use it (e.g. how an app is downloaded, how a photo is taken), I mention about its functions, features (e.g. how a contact is created, how Wi-Fi is disconnected), I tell use, functions, features of another downloaded software from App Store, I show built-in and downloaded software's screens, screen images, screen video records, symbols, logos, functions, features etc. in my blog webpage which made money via Google AdSense and/or affiliate marketing or on YouTube which made money via Google AdSense and/or affiliate marketing or on Udemy which made money by selling courses. Or, let's assume, I have a Windows 10 on my desktop and I do same thing (e.g. selling C language course on Udemy by using Code::Blocks or selling complete Windows 10 course on Udemy). Or, let's assume, I have a Linux disto on my laptop and I do same thing (e.g. publishing how a virtual machine is created by using VirtualBox on the blog which made money or selling complete VirtualBox course on Udemy). As you predict, much more combinations can be produced. Can you please explain what the rights are of the software owners in this case? EDIT: You can think that I buy the software if it requires something like a key and if I want to handle them on the platforms as in the way I mentioned. E.g. Windows 10 EDIT 2: I mean people or companies who provide a software, such as PuTTY, VirtualBox or WhatsApp, by software owners.
You are absolutely allowed to discuss or describe or criticizes software (or books or other copyrighted or trademarked things) without any permission from the copyright holder or trademark holder. This includes teaching people how to use those things. You may not, however, copy protected software without permission. For example you could not include a CD with a copy of Windows 10 as part of a course you taught on using Windows 10, without permission from Microsoft. Also, you may not use a trademark in such a way as to imply that your course is approved or endorsed by the trade mark holder, or by the maker of the trademarked item. If reasonable people could think that your Windows course was approved by Microsoft, you are probably infringing their trademark. Use of screenshots is more of a grey area. Such use, for purposes of teaching or of commentary, is probably covered by fair use (in the US) or fair dealing (in any of several other countries). But that is always a case-by-case determination, and depends on the exact facts, such as how extensive the use is, and whether it in any way harms the market for the original. If in doubt consulting a lawyer experienced in IP issues is wise. But aside from the issues of screenshots, the makers or copyright or trademark holders of software have no right to grant or withhold permission to one who teaches about the softrware, nor to demand any fee from any such person.
Not the free version Your use is commercial so you have to buy the software which (presumably) allows commercial use.
In general, the output of a program is not copyrighted by the author of the program. When you write a novel in Word, Microsoft doesn't own any copyright in your novel. When you prepare financial statements with Excel, Microsoft doesn't own any copyright in those either. There can be exceptions. Some programs (like GNU Bison, a parser generator) actually do output parts of their own source code, and their source code is copyright to the author. To clarify things, GNU made a statement in the license for Bison that officially says they don't have copyright to what it outputs. You should expect programs of this type to have such an exception, and if they don't, maybe ask the author or don't use them.
No, you can't The last paragraph of the MIT License explicitly says the author is not responsible for damages (emphasis mine): THE SOFTWARE IS PROVIDED &quot;AS IS&quot;, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE. A software license is not a contract. You didn't enter a contract with the developer or team. You found software online and decided to use the software. When you install paid software you are almost always presented with the EULA and check-box saying you agree to it. You took an action and agreed to the EULA. You didn’t have to agree to anything before getting access to the code under the MIT license. The software is offered &quot;as-is&quot; which is further protects the author. You'd have to show the author convinced you to use the software fraudulently. You're unlikely to talk to the author at all, and since the entire source code is available for review, it would be very difficult if not impossible to claim fraud. Finally, in the U.S. people have been sued using the Computer Fraud and Abuse Act. None of the notable cases involve embedding a virus in an open-source project. Of interest is how the CFAA defines a virus (emphasis mine) (A) knowingly causes the transmission of a program, information, code, or command, and as a result of such conduct, intentionally causes damage without authorization, to a protected computer; Simply writing bad code wouldn't be enough. You'd have to prove the developer acted maliciously. Hobbyists working for free don't usually have much money. The other major contributors to open source are large companies like IBM and Google, which have lawyers on retainer and deal with frivolous lawsuits frequently.
Yes A software license is just a contract and parties to a contract are free to agree whatever terms they wish under the doctrine of freedom to contract. Government can restrict what terms can be used in a contract either in general (e.g. for being against public policy) or specifically (e.g. by requiring wages be paid in money). None of the terms you mention fall foul of any restrictions I know of.
At least in theory an end user could be sued for infringing on a patent, especially a method claim. Given the cost of a patent lawsuit, this strikes me as extremely unlikely to happen though, unless the user in question were an extremely large company, or something on that order. Theoretically, the only difference between open-source software and proprietary software would be that availability of the source code makes it easier to prove use of a patent in open-source software. Releasing the software as open-source doesn't confer any immunity from patent law or anything like that though. Realistically, however, the chances of being sued for infringement if you're basically giving away the software in question are fairly remote. It rarely makes sense for a patent holder to spend millions of dollars on a lawsuit where they stand no chance of even recovering their cost (but no, that certainly should not be taken as legal advice that you're free to infringe on patents, or anything similar--in fact, none of this should be taken as legal advice at all). If you can actually prove that a technique was published or publicly known and used (e.g., in a product that was offered for sale) well before the patent was applied for, the patent is probably invalid (and if proven so in court, the case would normally be dismissed with prejudice, which basically means the patent holder wouldn't be able to sue anybody else for infringement of that patent). I'd note, however, that in my experience this is much less common than most people imagine--many look at (for example) the title of a patent, and assume it lacks originality because it refers to some well-known technique, and ignore the claims where it details the precise differences between the previously known technique and what the patent really covers. Just for example, the EFF used to have a web page talking about a (now long-since expired) patent on how to draw a cursor on screen. In an apparent attempt at scaring the unwary, they showed code they claimed infringed in the patent--despite the fact that the patent's "background of the invention" specifically cited the technique they showed as being previously known, and not covered by the patent.
As long as you own the copyright to the works, you can even publish the source code itself under two different licenses, which can be radically different. For example, MySQL is licensed under both a commercial and an open-source license. Given that you can publish a single piece of work as multiple licenses, it is your choice which one you wish to grant to the book or the code, as long as you own the copyright.
If I make a working prototype and upload it on youtube will it prevent others from getting a patent on the idea? Generally yes. If the core information is accessible to the public, it becomes &quot;prior art&quot; and cannot be patented anymore by someone else. That includes you. Depending on local legislation, you have a small time window to apply for a patent (after disclosure) but if you don't, it's public domain and everybody is free to use it. If it's mainly code, you may be able to upload to Github and attach a license to it but that offers only limited protection. Globally? That depends on local legislation which there are too many of, to answer this here.