@zero Well it's open-source (although definitely tainted so unlikely to be used in public projects for quite some time) so non-revocable and virtually non-removable.
@mangeurdenuage@zero No, I'm pretty sure you cannot revoke a public license, most licences explicitly mention this but I don't think it's required.
And with full rights ownership you can change the license at any time, regardless of whatever license the project is using, in fact the GPLv2→GPLv3 of GNU software hinges on this via copyright assignment to the FSF.
The only way to prevent things like arbitrary relicensing is to have a large community of contributors who never assigned copyright (which is part of why I don't sign CLAs). Or well do a fork prior to the relicensing, because public licensing.
@mangeurdenuage@zero At least if you'd need a license which would explicitly need a "non-recovable" clause, I'm pretty sure Oracle would have sued illumos, OpenZFS, … since the CDDL doesn't seems to have such a clause.
And there's no way Oracle wouldn't be like "Oh hey, we can sue!".
@zero None of these projects would be sueable if the people running them had the tiniest bit of fucking opsec skills. Step one is get the fuck off of glowcord
@get@the.asbestos.cafe@zero@strelizia.net it's not even illegal software the problem is that companies can file frivolous lawsuits in this country with no penalty and bleed normal people dry trying to get the cases dismissed
@anemone@zero Functionally it's illegal software if the government lets nintoddler ruin your life over it, these teams need to start treating it as such, ditch discord and get real
@anemone@zero Even an American can make themselves impossible to sue in a project like this, instead of using a service like Discord that needs your phone number to make an account and gathers god knows how much data on you, set up a damn gitea hidden service to develop your illegal software instead of being a literal retard.
@get@the.asbestos.cafe@zero@strelizia.net it's unfortunate these programs keep seemingly getting developed by americans or others within the reach of the west's corrupt legal system
@mangeurdenuage@zero Also this made me realize it'll soon be fifteen years since Oracle acquired Sun and then a bit more months until they destroyed it. It's been so long, yet I still remember it.
@zero@lanodan If I don't have the ownership of the MIT copyrighted software you are correct. The people who have ownership of the copyright do.
For example, In the case of the GPL software Yuzu, it was a corner case where nintendo shouldn't have been able but could do that, they bought back the project's ownership because they had a mountain of proof that illegal distribution of full video games under EULA were done, that and the developers broke DRM in a country where it was non legal to do it under a for profit organization.
But fortunately even tho all this, the GPL can't be retro actively removed so as long as you don't break someone's else copyright then it can be continued, that's why the suyu fork still exist, and other projects like dolphin still are.
@zero@lanodan "Open source" and "Free/libre" licensing are part of copyright. Copyright holders are what devs are when then license any piece of code, be it a chaos license like MIT/BSD, or Preserving license like the GPL. The difference is that with the GPL you can't retroactively revocate past source code.
@mangeurdenuage@lanodan@zero you can't retroactively revoke a license like MIT. sure they can switch to a different license anytime, but the code already published under the terms of the MIT license (or any open source) license remains available under those conditions of that license. while the GPL prevents non-copyright holders to redistribute under a non-free license, neither free nor open source licenses allow such bullshit as "revoking licenses" they'd have to explicitly say so and i doubt that'd work under most legal systems.
@lucy@anemone@lanodan@mangeurdenuage@zero there was some really good backup software on debian that was kept out of the free repo and languished because of license arcanery.
@lucy@mangeurdenuage@zero And pretty sure it would trigger a change in the distro policies and Open Source Definition to effectively consider a revocable license non-free / non-open-source. Otherwise you'd be building on sand.
@lucy@anemone@lanodan@mangeurdenuage@zero I wish I remembered the specifics, but iirc the original licence was held by some defunct entity due entirely to a screwup and it will never be free despite the entity no longer existing and never mattering
@lucy@mangeurdenuage@zero Also Free Software Definition explicitly states: > In order for these freedoms to be real, they must be permanent and irrevocable as long as you do nothing wrong; if the developer of the software has the power to revoke the license, or retroactively add restrictions to its terms, without your doing anything wrong to give cause, the software is not free.
@lanodan@lucy@zero >Otherwise you'd be building on sand. It's clearly what we're witnessing right now. Nintendo just removed all code from the ryujinx after acquiring it. And they'll probably go after anyone who has a fork of it.
@mangeurdenuage@lanodan@zero what actually happened is a bunch of soydevs published code they knew one of the most powerful companies in the world would be mad about, with zero opsec. it has nothing to do with the license.
@mangeurdenuage@lanodan@zero it's not about the license tho.. like i get you desperately shill GPL for the gnu jihad but you're just making up a narrative that never happened. what prevents you from taking your local copy of the last version of that switch emulator from before the relicensing, removing all the stuff that would allow nintendo to screw you over and publish that fork under whatever license you want?
@lucy@lanodan@zero > they'd go after you no matter what license you used Not really, they tried with dolphin and dolphin just removed all the stuff that allowed nintendo to fuck with them.
@mangeurdenuage@lucy@lanodan Nintendo didn't remove or acquire anything, they scared or paid off a guy to delete a repo he was the controller of, they don't have any leg to stand going after forks since it was not a DMCA and won't be.
@mangeurdenuage@lucy@zero Now you're just spewing shit that's entirely out of context. Yeah you can entirely take MIT and not release code, that's how a permissive license works, that's not what revocation means.
And your explanation horribly broken: Check an Android device for the GPL in the credits. :)
@zero@lanodan@lucy And I'll add a little reminder that such permissive licensing will and are already used to be sold under a proprietary format. If you have a console just check the terms and conditions and you'll stubble on a few of these. Even the wiiu already had these terms.
@zero@lucy@lanodan >Nintendo didn't remove or acquire anything, It's very known that such companies with armies of lawyers just throw money at people they don't want to see and don't acquire anything.
And to be clear if I remove any fucking tarball or my machines go down the license and all the permission granted are still entirely valid. Because upstream access doesn't matters, you just need someone with a copy, that's how all the floss licences works, otherwise distros wouldn't bother making mirrors. And for ryujinx I'm pretty sure a whole country worth of people have a copy.
@lanodan@lucy@zero >that's entirely out of context. How is it out of context ? Nintendo, buys back copyrhgt ownership, the repo/code is gone. So either they go money or nothing or they got employed.
>that's not what revocation means. How is it not revocation if people don't have access to the code ? Which is the case with ryujinx.
>Check an Android device for the GPL in the credits. You mean the GPLv2 loophole issue ? shame that almost all android distributors doesn't use any piece of GPLv3 code like coreutils and go with BusyBox instead.
@mangeurdenuage >The people who have ownership of the copyright do. Copyright is held and not owned.
If copyright was owned, it would never expire, just like how the house you own doesn't become public property after a set number of years.
MIT expat is a terrible license, so it doesn't say that it is irrevocable, so I'm unsure if such license is possible to revoke or not if it's followed.
@mangeurdenuage >You mean the GPLv2 loophole issue ? There is no loophole in the GPLv2.
It very clearly states; The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the *****executable*****.
Not "object code that doesn't run", EXECUT(E) ABLE.
That part is just a pain in the ass to enforce in court, as it's very difficult to get incompetent lawyers or judges to understand what is an executable is - so it's a better idea to just upgrade to the GPLv3-or-later.
>almost all android distributors doesn't use any piece of GPLv3 code like coreutils and go with BusyBox instead. Android doesn't ship BusyBox, as google hates even partial freedom - it ships toybox instead.
Of course, toybox is so garbage it's as useful as a box of toys for getting things done - so many 3rd party distributions include BusyBox and there are several BusyBox installers.
@lucy >you can't retroactively revoke a license like MIT. MIT expat doesn't mention revocation, so there's a good chance it *can* be retroactively revoked.
The GPLv2 does not say it's irrevocable, but it does note termination conditions; "4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.", which implies that those who follow the license will not have the licenses terminated.
The GPLv3 is irrevocable; "2. Basic Permissions. All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License explicitly affirms your unlimited permission to run the unmodified Program."
@mangeurdenuage >Yet another talk when powerpoint crashes. You have to be insane to use that unprofessional software, even if you can't care about your own freedom.
@sally@lanodan@lucy@zero >They have nothing .jpg > is only a legal problem in the US And the UK etc...
>so they could even distribute games and Nintendo can cope, seethe and dilate about it Only if they didn't do any of the common mistakes that tor users do. https://youtube.com/watch?v=tlxmUfnpr8w
@sally@lanodan@lucy@zero > hosted on gitlab They have their own git. >used Glowcord They host their own chat. >equally bad opsec No an issue if you don't distribute proprietary software or break drm in a country you aren't allowed to.
>maybe they finally learned the lesson. Hopefully they won't distribute copies of proprietary games, nor make a lucrative entity out of it yes.
@lucy@lanodan@zero You're partly describing suyu. >and publish that fork under whatever license you want? You can't do that, the part that are licensed are still owned by the new copyright holders. If that code doesn't hold any non legal part then it's ok. However all the new code you produce is under the license you choose.