If you want a free copy of the SHOUTcast server software, they illegally share that code in their repo ..
Winamp Legacy player source code
171–180 of 345 posts
Re: Winamp Legacy player source code
#172Open sourcing is always good, because maybe you can learn some things by reading it. Also, Winamp Legacy is a fairly important piece of software, so having an archive of its source is a great thing. But the restrictions on the source are interesting. To quote the license file: * No Distribution of Modified Versions: You may not distribute modified versions of the software, whether in source or binary form. * No Forki…
Yeah the license self-refers as "copyleft" (an unregulated term afaik), and they have been very careful to avoid usage of the term "open source" rather preferring to say things like "the source is open". Regulated or not the use of "copyleft" still seems deliberately misleading to me - I don't think the restrictions you've listed are in line with the intent of the copyleft movement.
While "copyleft" is just a word like any other word, and subject to the same descriptivist drift as any other, in this case it is a specific word coined by a specific org, with a pretty specific definition. One that this license does not meet.
Re: Winamp Legacy player source code
#173Earlier quoted context omitted.
Yeah the license self-refers as "copyleft" (an unregulated term afaik), and they have been very careful to avoid usage of the term "open source" rather preferring to say things like "the source is open". Regulated or not the use of "copyleft" still seems deliberately misleading to me - I don't think the restrictions you've listed are in line with the intent of the copyleft movement.
Copyleft just means you lose license privileges and revert to unlicensed copyright rules when violating its terms. There's no reason you can't use that principle in a more restrictive way than GPL.
That's not at all what copyleft means.
Re: Winamp Legacy player source code
#174Open sourcing is always good, because maybe you can learn some things by reading it. Also, Winamp Legacy is a fairly important piece of software, so having an archive of its source is a great thing. But the restrictions on the source are interesting. To quote the license file: * No Distribution of Modified Versions: You may not distribute modified versions of the software, whether in source or binary form. * No Forki…
This license prohibits maintenance. If the official copy had a single bit that prevents it from compiling on your local machine, you cannot make that change. Only the "maintainers of the official repository" are permitted to do that.
Re: Winamp Legacy player source code
#175Earlier quoted context omitted.
This seems to go against GitHub's own ToS[1]: > By setting your repositories to be viewed publicly, you agree to allow others to view and "fork" your repositories (this means that others may make their own copies of Content from your repositories in repositories they control). [1] https://docs.github.com/en/site-policy/github-terms/github-t...
It is interesting that in a hypothetical scenario if someone did fork it and then thes goes to court. Which licence would take precedence here?
> Which licence would take precedence here?
Whichever one runs up the attorney's bill the highest.
Re: Winamp Legacy player source code
#176Earlier quoted context omitted.
Their official blog post does https://winamp.com/press/winamp-open-source-code
It does not. It open-source only in it's URL which has no semantic value if you read the article.
It's still misleading and they're obviously trying to imply marketing value that doesn't exist.
Re: Winamp Legacy player source code
#177Earlier quoted context omitted.
The Github ToS gives users the right to fork any public repos.
On Github. Doesn't give them a license to fork it to their workstation.
One of the many bad things that Github did was to name the button that does the `git clone` action `Fork`.
Like, I get why they did it, but (as we can see) it resulted in this stupid terminology confusion.
Re: Winamp Legacy player source code
#178Are there any tools that can receive an entire code base like this, then analyze and answer questions about the code, structure, functionality?
Cursor can do it.
Re: Winamp Legacy player source code
#179Re: Winamp Legacy player source code
#180sorry but why does old winamp code still matter? there are plenty open source audio libraries these days along with different open source players.
It's still one of the best simple media players (sadly). If it had better HiDPI support, it'd still be my go to on Windows (if I still used Windows).
I wonder if anyone there still has the source to the failed Linux Alpha. It crashed all the time, but it did exist, for a very short while.