#gnuposting
Explore tagged Tumblr posts
Text
Did Winamp accidentally just provide proof that they were violating GPL for decades? Yes!
Have they potentially GPL poisoned their entire codebase as well as proprietary Dolby algorithms? Also yes!
Can you download this code today? You guessed it, yes!!!
Orphaned commits containing all of these issues after they tried to hide their crimes are waiting for you to download them!
#0954e03b3acbc11b6c90298598db6b6469568d72#gnuposting#retro tech#free software#winamp#gplposting#they also leaked the entire source to shoutcast server
86 notes
·
View notes
Text
Funnily enough this repo can teach you how to use github by showing you all of what NOT to do with one. Lmao.
A short list of mistakes as I understand them:
-Created a custom code license that forbids forking of the repo, which if your repo is public is against github TOS.
-Uses paid for proprietary, commercial code from at minimum, both shoutcast server and dolby, which is code that should not be in a public repo.
-Contains Code from at *least* the gplv2 license, which requires your code to be gplv2 licensed as well, and therefore open source for forking, meaning that custom code license and the proprietary code in the public repo is a double mistake as well as showing the old owners of the code were violating the terms of the gplv2 for at least a couple decades now.
-Contained (now expired) Certifications for code signing which proves to your OS that the code/program you run is from who it says it is and is therefore trustworthy (usually)
-Contained multiple instances of the compiled 7zip binaries which it does not have permission to share.
-Every attempt to fix these mistakes in this dumpster fire has been a public commit, which still allows anyone to see the old/removed/illegal code and download it. What they should have done instead was immediately private the repo, remove ALL of the infringing code, switch to the gplv2 license, rebase their code so that nobody can see the changes to the code base, and then reopen the repo to the public. For anyone who says they are trying to make it source available, not open source, they kind of lost the privilege to do that when they used gplv2 complianr libraries to develop the app, and I dont think these people know how to both remove the dependencies on those libraries and still have a functioning app, which seems to be their intent.
-and finally, they deleted a commit that added the entirety of quake 2 into the repo. honestly this one is just sad. cringe repoless behavior if im being honest.
Now to be fair to them, they are not the people who made winamp, they just bought the rights to the codebase, and its pretty clear they dont know what they are doing. but also this is very funny and a masterclass in how not to run a repo so point, laugh, download the original codebase and stick it into a private repo if you want. the lawsuits will hit them sooner or later and youll lose the chance.
Did Winamp accidentally just provide proof that they were violating GPL for decades? Yes!
Have they potentially GPL poisoned their entire codebase as well as proprietary Dolby algorithms? Also yes!
Can you download this code today? You guessed it, yes!!!
Orphaned commits containing all of these issues after they tried to hide their crimes are waiting for you to download them!
86 notes
·
View notes