Can I use my Stack Overflow profile to release the contents of my questions and answers under a secondary license? As I understand, when I post something on Stack Overflow (or other Stack Exchange sites), I have copyright on the contents of the post and I've licensed significant redistribution and re-licensing rights to Stack Overflow. Stack Overflow then releases that content to other netizens under an open license, but requires attribution in the form of a link to the original answer. I have occasionally seen users on Stack Overflow who update the 'bio' section of their profile page to say something like 'I hereby release all of my contributions to Stack Overflow, past, present, and future, into the public domain.'. Since those users do hold copyright, it seems to me this is valid. I.e., anyone using the content can choose to use it under the license offered by Stack Overflow (with attribution required) or as public domain content as offered by the user themself (without attribution required). Is it valid to use the 'bio' section of your Stack Overflow profile to release your Stack Overflow contributions under a secondary license? Does the answer differ if releasing to the public domain rather than under a secondary license?
You can licence your copyright under as many licences as you like to as many people as you like It's your copyright - you can do what you want with it. What you can't do is give someone an exclusive licence and then give licences to others - that would be a breach of contract with the exclusive licensee. How you let people know about the available licences is also up to you - your bio on Stack Exchange is fine.
It seems that you don’t understand what parody is. If you do understand, please explain how it’s even possible to parody computer code. What you can do with “open source” code depends on the licence the copyright holder(s) release it under. For some very permissive licences you can do what you suggest, for most, you can’t.
You can put anything you like in a ToS document, but not everything you might put there will be enforceable. By posting something on the web, you are inviting anyone to read it. In some jurisdictions that may include the right to make and store a personal copy, although not multiple copies or a copy for commercial use. You can taker technical measures to prevent automated access and automated downloads (scraping). There was a case (hiQ Labs, Inc. v. LinkedIn Corp, 938 F.3d 985 (9th Cir. 2019)) in which access restrictions were held binding in a US court, but in that case the site owner had notified the would-be reuser (a competitor) directly. The laws on this sort of thing may differ from country to country, and are not as well-settled as older parts of the law tend to be. The question asks: can I list in my terms of service that all users acknowledge I own their posts ... The only way in which the host could &quot;own&quot; the posts would be if the users transferred copyright to the host, or granted the host an exclusive license. Under US law this would take a written and signed document. Clicking an &quot;I agree&quot; box or button might constitute a valid signature. A statement that &quot;by using this site you agree ...&quot; would pretty clearly not. You might prohibit bots copying from your site and posting duplicates, but to prohibit users re-posting their own messages elsewhere is harder, legally, and leas reasonable in my view. Under US law you could not actually file suit for copyright infringement until you had registered the copyright, but that is not true in many other countries.
Probably not. There are potential problems on the levels of copyright, data protection, and the Youtube terms of service. You should assume that comments are typically covered by copyright. You do not have a license to these comments, only YouTube does. Therefore, YouTube can show the comments but you can't copy them – just like YouTube can stream your videos but others can't download them and host them on their own websites. To cover the copyright angle, you'd either need to obtain a license from the commenters, or get a sub-license from YouTube, or identify a suitable copyright exception. The comments are personal data within the meaning of the GDPR, so that your processing of these comments (including mere storage) would be subject to GDPR as well. You need a legal basis for processing personal data. Which legal basis is suitable would depend on the purpose of processing, and on your relationship with the commenters. Potentially applicable legal bases in this context: you have a contract with the commenters that requires you to show the comments on your website. For example, I could see such a contract if there were a “featured comment” perk for a Patreon subscription. But this is not going to fly with random commenters. you have a legitimate interest (LI) that allows the processing. A LI requires that you conduct a balancing test where you weigh this interest against the commenter's rights. This is very specific to the purposes for which you want to show the comments. However, a LI will generally only apply if you have an existing relationship with the commenters, making it possible for them to expect that this processing will occur – unlikely if you'll be scraping comments from YouTube. you have obtained consent from the data subject. Consent must be specific, informed, freely given, and unambiguous – you can't obtain consent by writing “by commenting under this video you consent to XXX” in the video description. Regardless of legal basis, you would have to inform the commenters under Art 14 GDPR when you scrape their comments from the platform. Finally, consider the platform terms of service. I have not read the YouTube ToS recently, so I don't know what their specific conditions are. But in general, such ToS will not allow you to scrape content from their platform in order to host it somewhere else. The ToS might allow certain actions like embedding a link/iframe to such videos on other sites, without allowing other actions such as copying other user's content to your site.
According to the current version of the TOS: You own the rights to the content you create and post on Medium. By posting content to Medium, you give us a nonexclusive license to publish it on Medium Services, including anything reasonably related to publishing it (like storing, displaying, reformatting, and distributing it). In consideration for Medium granting you access to and use of the Services, you agree that Medium may enable advertising on the Services, including in connection with the display of your content or other information. We may also use your content to promote Medium, including its products and content. We will never sell your content to third parties without your explicit permission. This explicitly says you own your content, although Medium has some rights to do some things. And they won't sell it without permission, so unless Medium itself is publishing this book, it would seem to be copyright infringement. (Of course, I don't know what the TOS said when you originally wrote the article.) If what was copied was not copyrightable (like a quote from the Constitution, or a simple uncreative graph of something obvious) then it wouldn't be infringement. But your article was probably more than that.
are there any safeguards you could take to preemptively block such behavior, such as a disclaimer inside the book cover that reads something like The safeguard you outline would be overridden as soon as the author enters any contract that requires assignment of copyright. (I would not delve in the differences between licensing and copyright assignment because that hypothetical author is dealing with a contract of adhesion which readily requires assignment; the author has no option to change the ToS to allow for licensing only) Under contract law, one of the essential prerequisites is that the conditions of a contract be entered knowingly and willfully. By deliberately clicking on a ToS page to move forward with the uploading a copyrighted work, the author is signaling his awareness and acceptance of the ToS. The fact that the author chose not to read the ToS is irrelevant and very unlikely to strike whatever entitlements the website owner formulated in the accepted ToS. For the same reason, the author's safeguard disclaimer does not bind the website owner: It cannot be said that the website owner was aware of that disclaimer at the time of the formation of contract between the author and the website owner. That is, the website owner did not knowingly and willfully accepted the author's safeguard. The website owner is not even expected to know about any safeguards which one of its potential user intends to establish. The length of a ToS document is also irrelevant because the website owner has the valid argument that "the user-author could have skimmed through the ToS or do a search (via Control-Find) of keywords such as 'copyright' or 'property', whence any allegation of 'inadvertent' assignment of copyright is untenable". Is there a way to protect your IP from inadvertently being licensed/stolen/assigned via TOS "agreements", without having to waste your life reading huge one-sided online "contracts" that are "subject to change without notice" anyway? Yes. That consists of not uploading one's works in such platforms. In contract law that would be expressed as "declining an exchange of considerations". There are many other alternatives for an author to promote his work without being required to assign copyright.
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.
It's not illegal to say things in your profile. SE requires you to license your content to them on a non-exclusive basis pursuant to CC BY-SA 4.0. &quot;Non-exclusive&quot; means that you can also license the material to others on some other basis, e.g. CC0. In that case, a person who uses your material can rely on the other license that you granted. If SE wanted to, it could prohibit putting licenses in a user profile, in which case you would have to promulgate your more generous license elsewhere.