The Winamp source code is here!
(and it has a horrendous license that people are rightfully complaining about already)
So far:
* License was probably not lawyered, so it contradicts itself a lot, even though they probably meant "redistributions need to drop all branding and attachment to Winamp" which is fair
* The license violates GitHub terms of service, because the ToS grant the right to fork for every public repository
* The source includes commercial or non-distributable libraries
* SHOUTcast server side code is included in the repo (lol???)
* Published all codesigning utilities (and certs + pws, yikes)
Funniest bit:
"Forking is not allowed" vs. "Contributions encouraged"
On GitHub, that requires a fork however
or do they want us to use git send-email?
Our friends at Winamp do not seem to know git that much, do they?
Lection, the effectiveness of a "Remove closed source code" commit:
https://github.com/WinampDesktop/winamp/commit/0a4b7d32d090696e5aab8de9c61dda9dab76aabf
Jef is hard at work trying to remove the SHOUTcast code from the repository
after merging it back in again...
https://github.com/WinampDesktop/winamp/commit/1be04037cdba95396eef7728134043ba3ee6fbf4
Winamp, it really whips the authority of their executables.
They accidentally pushed all codesigning stuff, including signature passwords into the repo as well
Edit: The keys expired in June, so not that useful to cause trouble, but still quite the blunder I'd say.
https://github.com/WinampDesktop/winamp/tree/community/Src/codesign
Actually, I am highly doubting *accidental* at this point, but the poor employee who just remembered that Winamp wanted to release their code today just went and slapped EVERYTHING into git.
I'm a bit in a rollercoaster of emotions of thinking this is catastrophic and catastrophically hilarious.
More discoveries...Gracenote Client IDs? Not sure if they are still valid nor useful to any extent (they are used for client registration, I guess)
Looking at the repo a day after now...or more or less half a day, I guess...
i hate GitHub making stuff easily accessible, because even if they guy who maintains it did a lot of mishaps, the license sucks and doesn't really know git...that's not much of a reason to vandalise issues and PRs.
@pixel Oh dear... I really hope they're at least *considering* taking the entire thing offline while they're working out all the licensing kinks.
@pixel poor jef just doing their best
@pixel lmaaaaaaoooooooooo
@pixel wow, this has just been a catastrophe
@pixel@desu.social this is a fuckup of LEGENDARY amplitude, what the FUCK
@pixel I'm guessing that whoever is releasing this doesn't know their way around the codebase at all? Or, apparently, git
@tomw @pixel afaict the username that's doing it is the cto from when radionomy (which changed names a few times to end up as llama group last year) acquired winamp from aol in 2014.
considering they announced they were doing all of this 4 months ago & however many dev contact details they got from the interested sign-up page (not that I've seen anyone ever mention getting contacted in relation to that which isn't the first time with those pages it seems), someone has dropped the ball on this.
@pixel Looks like someone at Nullsoft was using a pirated copy of Ratatouille for testing.
Can't fault them - great movie!
@pixel oh my God what a mess......
@tabby absolute chaos, but to the benefit of all of us!
@pixel@desu.social open sourcing cryptographic keys and passwords goes hard
@pixel unfortunately not that useful for blackhat purposes
> Not After : Jun 12 23:59:59 2024 GMT
@jstatepost @pixel take a look at audacious-media-player.org