Is there like an anti-copyright license ? reddit / BSD ---------------------------------------------------------------------- puke_of_edinbruh · 2021-08-23 09:08 So basically think of AGPL , BUT instead of requiring the code to remain libre , the only requirement is that anyone can redistribute it however they want and you can place no other restrictions on what they can do , that also applies for anything you include the code in and even server side usage (which is why i said Affero GPL) So if you take code under that license you can do whatever you want except add more restrictions to it . If it is closed source , then e.g. anyone can still take the binary form and try to reverse engineer and redistribute whatever comes out of that . ---------------------------------------------------------------------- northrupthebandgeek · 2021-08-23 09:41 I feel like you're just describing ordinary (A)GPL-style copyleft, though I don't know of any licenses that explicitly protect reverse- engineering binaries like you describe. The Artistic License 2.0 (as used by Perl 6 / Raku) comes to mind as one that allows reuse under any other copyleft license, which might be closer to what you mean by "whatever you want except add more restrictions to it". ---------------------------------------------------------------------- jaypatelani · 2021-08-23 09:56 https://paritylicense.com/ https://www.netbsd.org/about/redistribution.html ---------------------------------------------------------------------- [deleted] · 2021-08-23 12:45 [deleted] ---------------------------------------------------------------------- roarde · 2021-08-23 16:28 *License*, per se, requires copyright. The author claims a supposed right of control, then announces permission to use in a specified way; a license. Permission and license are thus opposites of freedom. If you need permission for it, it's not free. Instead of a license, why not announce truly unencumbered code with the [Unlicense](https://unlicense.org)? Does magic things with the word **any**. WTFPL can't be beat for succinctness, but it's obviously not suitable for many contexts. ---------------------------------------------------------------------- PunishedRaion · 2021-08-23 18:36 It's a bit of a myth that someone can just take the BSD licensed code and slap GPL on it. That's called license revocation, and that's illegal under US law. No, BSD license is required to stay in place either on its own, or under a similar license set of terms (i.e. MIT) or else you can sue someone for code theft. ---------------------------------------------------------------------- Fearless_Process · 2021-08-24 01:49 A lot of people would argue that copyleft license are more "free" than truly unencumbered code since it guarantees modifications and sometimes derivative work will continue to remain "free". I'm not sure how I feel personally, but I do like the unlicense quite a lot. ---------------------------------------------------------------------- roarde · 2021-08-24 03:08 Guarantee? ---------------------------------------------------------------------- puke_of_edinbruh · 2021-08-24 03:54 guys im not sure i explained myself right . Basically the license would say there are no restrictions except adding more restrictions or including it into something that has more restrictions . So that would mean you can redistribute , reverse engineer , make modifications closed source , whatever . ---------------------------------------------------------------------- puke_of_edinbruh · 2021-08-24 03:56 Yes but there can still be an anti-copyright license . Putting something into public domain will allow others to include that in a work that does things that restrict e.g. redistribution , therefore a license that does not permit more restrictions is more anti-copyright ---------------------------------------------------------------------- deux3xmachina · 2021-08-24 03:57 One of the conditions is usually that derivative works must be published under tte same or a compatible license and that your changes be made available. Whether or not that constitutes greater freedom is up to a degree of sometimes heated debate. ---------------------------------------------------------------------- roarde · 2021-08-24 04:01 Still looking for that guarantee. ---------------------------------------------------------------------- BlindTreeFrog · 2021-08-24 04:04 So you want the original code to always be available but don't care what they do past that really? sounds like you just want it released to public domain ---------------------------------------------------------------------- MrRichBOB · 2021-08-24 04:05 ... GPL 3.0... or GPL 2.0. AGPL is used for API's, right? Richard Stallman et al.'s point in their _Copyleft_ licenses, is that it is abusing the Copyright system to ensure that the Copyright system cannot be used to oppress people. IIRC, the only difference between GPL 3 and 2 are that with 2, you can add all the code you want to a project under any license you want, the only thing is, you must turn over _all_ code, regardless of license, to the maintainer of the project you've forked so that they can choose what they want to implement. In otherwords, tithing at a Pentecostal Church—you need to report your yearly salary and dependents so they can properly shake you down. GPL 3, however, is Software Communism, and I do love the license with much of my heart, and you may NOT extend the project with non-GPL code, it must all be GPL-3. - - - - In short, the only difference between GPL-2.0 and BSD-2-clause is that GPL forces you to give back code when asked, though you are expected to give it back anyway. And BSD-2-clause does not shake down your intellectual property. In fact, you aren't even expected to give back, and you don't even have to make the source public on request, you just must say, “Hey, I use _X_ 2-clause software.” ---------------------------------------------------------------------- deux3xmachina · 2021-08-24 04:14 Sic lawyers at 'em. Best you can do. ---------------------------------------------------------------------- puke_of_edinbruh · 2021-08-24 04:34 AGPL : GPL doesnt actually apply to servers , if you take a gpl licensed software , modify it , but make users interact with through a server only , you dont need to share the code . AGPL makes it so that even then , you have to share code . GPLv3 also doesnt allow tivoization , which is providing copylefted software in locked down hardware . >GPLv3 is software communism good , im an anarcho-communist Oh and by the way , IIRC you can put GPLv3 inside AGPLv3 projects . That difference between GPL and BSD-2-Clause is a VERY big difference tho . Still BSD-2-Clause is not what im asking for , because it will allow you to include it in a project that has more restrictions than the license does . (btw , im just wondering if such a license exists , if i had to use a license id use AGPL) ---------------------------------------------------------------------- puke_of_edinbruh · 2021-08-24 04:34 if its released into public domain it can be included in a work that has more restrictions ---------------------------------------------------------------------- MrRichBOB · 2021-08-24 04:36 > im an anarcho-communist Both of my mortal enemies... rolled into one! I am just a GPL tech commie simp. ---------------------------------------------------------------------- BlindTreeFrog · 2021-08-24 04:45 but the original code is still out there wit h the original license. You say above you are fine with modifications have further restrictions, you just don't want the original to be restricted. ---------------------------------------------------------------------- puke_of_edinbruh · 2021-08-24 04:52 im not fine with modifications have more restrictions that are added through copyright law , e.g. banning redistribution . Closed source is not a restriction through copyright law . ---------------------------------------------------------------------- Michaelmrose · 2021-08-24 07:35 If you can't put restrictions on its usage then you can't by definition do whatever you want with it. Whatever you want includes actions that will reduce downstream users freedom. You basically want the AGPL. ---------------------------------------------------------------------- Michaelmrose · 2021-08-24 07:36 What specifically do you think the GPL forbids that you would like to support? ---------------------------------------------------------------------- Michaelmrose · 2021-08-24 07:43 How can someone who can't inspect the source know if they have any legal ability to distribute it? It could well contain 3rd party code that you only find out about 2 years later when you are getting sued. Furthermore once its closed source your rights are completely irrelevant because you can't extend it, you can't fix it, you can't change it you can just use it without paying for it. Furthermore a license server that doesn't let you actually use the software unless you have paid for permission wouldn't be a copyright restriction but it would still make even the limited freedom above meaningless. ---------------------------------------------------------------------- Michaelmrose · 2021-08-24 07:45 What again is stopping me from creating a derived work of your bsd code wherein the only things I change are the name and logos? Next specifically what is stopping me from starting with a combined work which contains 2 source files one blank save for the text of the GPL and another under the BSD license that contains all the code from your project. As time goes by I delete functions from the BSD file and rewrite the functionality in the GPL side. At what point does this become a problem? Can I not simply delete the bsd file as soon as all functionality is ported? Can you give an example of someone suing over usage of BSD code used in GPL software? ---------------------------------------------------------------------- Michaelmrose · 2021-08-24 07:46 It seems more likely that you don't understand the AGPL than it not basically doing what you want. ---------------------------------------------------------------------- PunishedRaion · 2021-08-24 15:37 > What again is stopping me from creating a derived work of your bsd code wherein the only things I change are the name and logos? At least under US law, license agreements are treated as contractual under law. If you revoke my code's license or terms, or modify my property in ways without written consent from me, if I find out you did so I could take you to court. If you're in the UK or another country I'm not sure. > Next specifically what is stopping me from starting with a combined work which contains 2 source files one blank save for the text of the GPL and another under the BSD license that contains all the code from your project. As time goes by I delete functions from the BSD file and rewrite the functionality in the GPL side. At what point does this become a problem? Can I not simply delete the bsd file as soon as all functionality is ported? So this is legal with pretty much any system. Let's say you take my BSD 3 clause licensed project libxg (a library designed to augment the functionality of a proprietary OS I do work on) and you replace, say, the asprintf functions with your own code. You could technically license that file under GPL, and then wrap the entire project in GPL. HOWEVER, you must still keep the BSD-licensed files in your notices, and if I saw you doing this, I would first respectfully ask you to go "Hey, this is derived from libxg, a BSD-licensed app, you can find it here: ; the original code is still under the BSD licensed." If you changed the name of the project, and rewrote every function, sure, at that point you could remove any reference, attribution etc. and I'd personally tell you "Good job!" and have nothing mean to say about it. > Can you give an example of someone suing over usage of BSD code used in GPL software? No, but there's been threats over it. Look up MicroBSD. ---------------------------------------------------------------------- Michaelmrose · 2021-08-24 17:00 In the US its often hard to tell the difference between competing ideas of how the law works without having a judge actually rule on the matter due to the law as it were being a function of both the literal text of the law and prior decisions. I think part of what is confusing is that you can literally take the code and give nothing back giving the idea that permissive licenses don't require any obligation whatsoever so intuitively if you only read OF the license instead of reading the very short text it appears as if no obligation exists when in fact providing the source triggers the additional obligation to retain the license. Thanks for the explanation. ---------------------------------------------------------------------- cajunman4life · 2021-08-25 13:02 Not sure it quite fits, but I was inspired many years ago by a Buddhist writer who uncopyrighted his work (at the time, not sure if his more recent works fall under the same). Some more information: - [uncopyright and the minimalist mindset](https://mnmlist.com/uncopyright-and-a-minimalist-mindset/) - [his actual uncopyright “license”](https://mnmlist.com/uncopyright/)