@neo@shork.comfysnug.space @lamp@kitty.haus @EdBoatConnoisseur@poa.st @TheMadPirate@detroitriotcity.com TL;DR: this turned into a rant but I plan to use AGPLv3 for most of the stuff I do, and if I'm making a recommendation, it's that. Your mileage may vary. Trivial stuff, I'm just shoving onto the internet. Anal-retentive people get all flustered if you download a .c file and then compile it and you don't know what the license is, but really, nobody's going after a dude hacking at home and intellectual property is a spook and cramming SPDX identifiers into every file in a repo is batshit insane. So if you think in practical terms, like, the situation on the ground, only businesses and organizations are really bound by licensing terms. You don't really need a "personal use" exception, people just do stuff. Especially businesses, though, Oracle or Microsoft or Google or even some dipshit "NFT but it's AI" startup raising a Series C, they drag in all of the MIT/BSD-licensed code they can, and they won't touch AGPLv3. OpenSSL and xz and all of these projects that come down to one broke guy hacking for free, and these businesses exploit that code. In general, this has been a problem: finance psychopaths have eaten the entire tech industry. It used to be safe for nerds and spergs to say all their insane shit and show up for work some time after lunch and work until 5 a.m. and those are now the people being pushed out in favor of people that the business guys like, and the business guys fucking hate hackers and they have been doing their best to make the industry hostile. (I really should clip out that thing Hamming said in his lecture, that was great shit.) They push rms out, they browbeat Linus for 20 years until he lets their CoC in, they lead the charge when some poor bastard's Github Issues are raided. Those are the people that are spooked by licensing terms, and they are the people that can write a check or fuck off. There is no organization to assign a copyright to, because I want to horrify anyone that considers a license change. I don't expect to make a huge dent, but I do intend to ignore fuckers that see a house I have built and then complain that the AGPLv3 prevents them from using the design for tract homes: they have given me no reason to care what they think and plenty of reasons not to. Some asshole thought-leader is at a summit, looking down his nose at engineers, and I don't intend to support his bottom line. Anything I make, I make for myself, for other hackers, and to advance things that I want advanced: freedom of speech is a big one. I want Google and Twitter and Oracle and Microsoft and the rest of the Silicon Valley Data Cartel dead. I want censorship dead, along with any organization that has ever tried to force someone to shut up. I sure as fuck don't want to end up doing work for them for free.

@Suiseiseki@freesoftwareextremist.com > As per US copyright law, what makes license grants possible is a law called copyright law Copyright law is a specific case of IP law. Copyright is a special case of intellectual property. There is no room to dispute this. WIPO (spit) is concerned with copyright, because copyright is within the purview of the World Intellectual Property Organization (spit). > copyright is clearly stated to be something different to property. The term "intellectual property" did not exist when the British pushed the US to adopt copyright law, which we did not have for a long time: anyone could copy books here. If I reject intellectual property as a concept, I have also rejected copyright; there is not a way to reject intellectual property without rejecting copyright. This is one of the reasons the copyleft is clever: if you accept the concept of copyright, then the license explicitly grants the right to copy, while if you do not, the license does not matter. > You ought to explicitly license AGPLv3-or-later, It is funny that you mention this, because I see this notification right after another from a different thread I am participating in: they are trying to kick rms and Sussman off the board of the FSF. Do you trust that the FSF is impossible to corrupt, and also that they will never make a mistake? I do not trust hypothetical future licenses; if there is an "or later" version of the AGPLv3 that is compatible with the AGPLv3, then that is fine. But imagine Drew DeVault seizes control of the FSF and AGPLv4 fails to respect the four freedoms: I will regret saying "And anything this organization decides to call a later version of the AGPL is fine." The AGPLv3 is a concrete thing: I can look at it and make a decision. I cannot look at later versions, because they do not exist, and thus cannot decide anything about them.

@p@fsebugoutzone.org >Copyright law is a specific case of IP law. Copyright was a thing long before someone imagined up such proprietary brain damage term. Even people in the "WIPO" has realized that many people don't buy their name and has recommended that the name has been changed. >because copyright is within the purview of the World Imaginary Property Organization Copyright is in the purview of each countries governments, although most governments follow their beck and call. >The term "intellectual property" did not exist when the British pushed the US to adopt copyright law, which we did not have for a long time: anyone could copy books here. At the time I believe anyone could copy books in Britain by hand and it was a matter that restricted printing presses only. Even when the USA adopted copyright, initially it did not apply to works from other countries. >If I reject intellectual property as a concept, I have also rejected copyright; there is not a way to reject intellectual property without rejecting copyright. If you reject imaginary property as the false concept that it is, that does not mean you could have possibly rejected an actual law that actually exists. >if you accept the concept of copyright, then the license explicitly grants the right to copy, while if you do not, the license does not matter. There is no choice whether to accept the concept of copyright or not, the law exists and restricts copying and the government enforces it - if you make a copy, you need to follow the license whether or not you accept it. >they are trying to kick rms and Sussman off the board of the FSF. Do you trust that the FSF is impossible to corrupt, and also that they will never make a mistake? The FSF has very carefully set up a voting scheme that ensures that it is impossible to corrupt and still have the Free Software Foundation and that any mistakes can be resolved, so yes I do trust them. As per the AGPLv3; "The Free Software Foundation may publish revised and/or new versions of the GNU Affero General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.", only the Free Software Foundation may publish revised versions and such versions need to be similar in spirit to be valid. Most other software licenses that offer an ability to fix license bugs simply give permission for an easily corrupted committee to release new versions that could contain anything. >But imagine Drew DeVault seizes control of the FSF and AGPLv4 fails to respect the four freedoms He cannot - nobody will vote that freedom hater in. >I cannot look at later versions, because they do not exist, and thus cannot decide anything about them. I can feel that if later versions need to exist, they will certainly be free, as unlike how other organizations bugfix licenses, the FSF license bugfix process is public. If you have misplaced doubt, please assign a proxy; "If the Program specifies that a proxy can decide which future versions of the GNU Affero General Public License can be used, that proxy's public statement of acceptance of a version permanently authorizes you to choose that version for the Program.".

@Suiseiseki@freesoftwareextremist.com > Copyright was a thing long before someone imagined up such proprietary brain damage term. For the same reason the phrase "freedom of expression" was created to encompass freedom of speech, of the press, etc., and the various new media that came into being, a term "intellectual property" was coined to encompass copyrights, patents, etc. You can argue that it's a bad term, but "copyright" is a bad term: anyone has the right to copy something, as there is no victim when a piece of information is copied and there are plenty of benefactors. > Even people in the "WIPO" has realized that many people don't buy their name and has recommended that the name has been changed. It's just the international version of the BSA; I don't care what they're called, I would like them to stop. > Copyright is in the purview of each countries governments > At the time I believe anyone could copy books in Britain by hand and it was a matter that restricted printing presses only. The British threatened trade sanctions against the US, as books that were covered by local copyright were taken to the US and then copied and reprinted. I think books ought to be copied. Here, here's a copy of a book. My copy is transferred to the server, where it is copied, and you can save it and create a copy and have your own copy. This book, which everyone loved, and which was used in offices and classrooms, was killed by AT&T because it violated their copyright on the Unix source code. So people started using Xerox machines to copy it and pass it around. And I am directing some machines to make a copy and you can make a copy of it. Anyone can make a copy of it. > If you reject imaginary property as the false concept that it is, that does not mean you could have possibly rejected an actual law that actually exists. You have said something absurd. Rejecting a concept as valid does not mean the same thing as rejecting the existence of a body of law. I reject the concept but I know the laws still exist; this is no different from software patents. I reject the concept: software patents are not reasonable. You agree with me on that concept, unless I'm mistaken. However, the laws protecting them do still exist. > There is no choice whether to accept the concept of copyright or not, Then I have done the impossible--before breakfast, even! > if you make a copy, you need to follow the license whether or not you accept it. I am a pirate. > The FSF has very carefully set up a voting scheme that ensures that it is impossible to corrupt There exists no voting scheme that can do this, but let's say I'll play: it is possible for the FSF to amend its bylaws and thus introduce a scheme that allows corruption. The members of the board are only humans and humans are replaced with other humans and ultimately the board can do what it wants. You also cannot discount a black swan: Sulla can march on Rome. You cannot say that the future is certain. If you can show me the text of all future versions of the AGPL, then I can make a decision. If you cannot, then you must make an argument based on trust. If I do not have to rely on trust, then I will not. Especially the FSF, which has, in my view, been compromised since the first attempt to remove rms. > only the Free Software Foundation may publish revised versions and such versions need to be similar in spirit to be valid. What guarantee do I have of this besides trust? I do not need trust to say "This is the license." I can read the words on the page. I cannot read future versions of it. > He cannot - nobody will vote that freedom hater in. Jim Salter appears to be on their side: https://fosstodon.org/jimsalter/113330555018293763 . > the FSF license bugfix process is public. Would you commit to eating something and all later versions of it, as decided by a committee that you have no control of? If I say I'll eat a burger, that's fine: I know what I am eating. If some day the committee decides that ketchup must be added, I hate ketchup, I'll be upset. > If you have misplaced doubt I have nothing but doubt, but as licenses exist only to provide limited grants of (legal) rights organizations that fear the law. It is a ward, a sigil, it repels people that would exploit the software, which represents my work, and provides some peace to people that are concerned about the law but wish to use the software. I am giving proper weight to licensing: "I'll agree to this and will not agree to write a blank check" and until there is new information, that's the decision. In order for this decision to cause me problems in the future, the code would have to be important enough, and it would also have to have enough contributors that there would be difficulty getting them to agree to relicense. Now, I have no control over the FSF, but I do decide whose patches I merge and whose I do not. I am not obligated to trust the FSF, but I must trust people whose patches are merged. Because Linux was delegated to a foundation, so that businesses could be comfortable using Linux, Linux acquired the ability to be coopted, taken from its creator. Because GNU projects typically (though not necessarily) assign copyright to the FSF, the FSF can take things away. You can seize control of a foundation. I do not trust a foundation: I trust individual people that I know, I trust machines, I trust that if there are words on a page that those words do not move.

@hazlin@shortstacksran.ch > Most recently spending lots of time getting comfortable with godot. And, I am disturbed by the rot that has been uncovered there. I figured how the product is licensed would save me from having to abandon it. Maybe I can continue with it? Yeah, that really sucks. I have seen the furor over Godot; I think you can still keep using it, I don't think they can do much to change that. But if they're fracturing it and someone's not allowed to use the bug tracker because of something they think, that's a mess. (Unreal Engine sleeper cell plot.) But like, bitrot ruins enough shit, right? There's no need to ruin it with politics. > My history of software development is, like a story of someone who keeps trying to build a house, but the sea devours more and more of the land every year. Speaking of Sussman, that's one of the issues I have; he seemed more resigned to it than excited about it, but the story I told up the thread was after a lecture, someone asked him about letting 6.001 (MIT's introduction to computer science) move from Scheme to Python and he said that like hardware, software moved from making your own everything from scratch (synthesis) to grabbing a library from the internet and looking to see if you could prod it to make it do what you want (analysis). I think the catastrophe was predectable and we're living in it and maybe we can kind of roll back the catastrophe. > I really despise copyright and licensing. Yeah, seconded. So I used to just dump shit into the public domain or think "Fuck it, MIT license" and I saw the huge push from all of these organizations that want to exploit software without contributing. There was this optimism when businesses first started talking positively about open source, right, and there was this kind of expectation that they'd be sending things back, but all that happened was they used Github (or sometimes the Apache Foundation) as a dumping ground for abandonware while exploiting useful software that they got for free, and then they tried to install HR departments in open-source projects. Now the "rewrite it in Rust!" brigade is dedicated to porting GPL'd software to another language and coincidentally always MIT-licensing it. I'm opting out, I'm gonna just AGPLv3 things unless I've got a good reason. > As the rot spreads though the tools that are easy to use, I end up learning more, maybe at some point I'll be able to just make a game, without using any visual editor, without any libraries xD Ha, yeah, I think that's the right way to do it, I think your head's on straight there. You know, it's actually easier to learn how to do this stuff on, like, GBA. GBA is kind of a sweet spot: it's ARM, it's beefy enough that you don't need any clever tricks to operate it, and then instead of worrying which library, it's just "put the sprite in this memory address, write to this address to control its X position and this address to control its Y". Even SDL is kind of complicated by comparison. And, you know, I go look at old PC hardware, or stuff like the C64, it's kind of amazing how easy it was to get up and running, you know?