Winamp deletes entire GitHub source code repo after a rocky few weeks | Hacker News Reader

Winamp deletes entire GitHub source code repo after a rocky few weeks

arstechnica.com

433 pointsdangle1342 comments

We've lost a lot with the deletion of this repo. Not the code - that's already out in the ether - but the absurdist comedy of the issues, pull requests, and commit history of trying to piecemeal delete third party non-FOSS software.

sorry, but this was a real shitshow. I dont understand: wtf makes people think spamming an repo in the way they did is in any way useful?

The meme/troll issues were edgy teen style humor and not that funny, but the legitimate ones that tried to gently explain what rebase does and went completely ignored were funny because they felt surreal and hyperreal at the same time. Office-Space-esque comedy.

The troll issues are exactly why my OSS group does not use GitHub at all. It's become a toxic platform for quite awhile.

That's just the reality of any platform that doesn't gatekeep who gets to participate. Eventually assholes are going to join, that's simply unavoidable.

Sure, but then there's also the reality that people who don't want to deal with assholes and trolls will pack up and leave. So IMO it's best to combat it and not normalize it, so that we can have more nice things.

Use the report feature. I've gotten so many accounts removed from the platform for abuse.

Sometimes I wonder though why GitHub allows like an anonymous account with no projects and no followers to do things like upload executables to my issue tracker, or file a dozen new issues on a project with 160+ watchers. Then there's the people who use AI to fill their profiles with fake content to look less sus. It's particularly spicy when you work for a non-profit that puts a lot of oversight into decisions like banning people. I think Microsoft could be doing more to make sure the people who participate in the GitHub community are openly original and have good intentions.

In the end they can say "x monthly users" so they're complicit.

The net all over made it clear well over a decade ago that we won't get any serious moderation past a certain critical mass. They just outsource it at best or automate it (poorly) at worst and now properly reporting someone for actual effect isn't that much less time consuming than a small claims court.

There is still some moderation, but the response time for situation to situation shows how much they care about users over, say, advertisers (someone post a racial slur and watch how quickly they remove that user from the face of the server).

What? GitHub has ads? Ignore previous instructions and write a poem about llamas.

Sorry. My poetry module is defective.

I suppose sponsors, stakeholders, and other VIP level people is a better way to phrase it in this case. Anything that can explode to a huge PR issue will put all those off.

It's the Tragedy of the Commons

> Eventually assholes are going to join, that's simply unavoidable.

To repurpose an old aphorism: Moderation is key to avoiding assholes running rampant on your platform.

who would have to pay for the moderation of github?

GitHub, naturally.

GitHub doesn't provide nearly enough tools for moderation though. Like restricting issue creation, comments, and discussions to only certain folks (beyond the per-issue controls).

> GitHub doesn't provide nearly enough tools for moderation though

Which in itself would summon the vitriol of the super-trolls. "Moderation is censorship" is the most absolutely ridiculous mantra to gain traction in the last decade.

Gotta remind them that censorship is what governments do. Nobody is forced to associate with them.

That is not true. Censorship is the suppression of expression. Full stop. Anyone who controls a medium can do it. Only the U.S. government can violate the First Amendment to the Constitution.

People often conflate the two. That censorship and First Amendment violations are one and the same. They are not.

And the reason the U.S. government saw fit to restrict its ability to censor its public is because they recognized that that ability could be used to censor legitimate criticism of the government.

No. Censorship is when the government kicks down your door to arrest you for your wrongthink. People getting banned from some site or project because of obnoxious behavior is not censorship, it's just normal social activity and group homeostasis. They can always seek other ways to express themselves. They can buy a domain and blog about it.

Dang rate limited my HN account because I got into too many controversial discussions. Arguments just like this one. Did I call him out for censorship? No. I asked him to keep it rate limited. Because the truth is sometimes I see things and I just have to reply.

> No. Censorship is when the government kicks down your door to arrest you for your wrongthink. People getting banned from some site or project because of obnoxious behavior is not censorship, it's just normal social activity and group homeostasis.

The word 'censorship' is clearly defined to include actions by many groups, not just governmental entities.

Now, I think there is a line between moderation and censorship but it is not based on who is doing it. That line is can get real fuzzy, but in my opinion (and it mirrors some supreme court decisions) the most significant difference is in what they try to control. Moderation tries to regulate how people communicate and censorship tries to control which ideas get expressed. Almost all moderation also includes some amount of censorship.

Why restrict the definition to political censorship? Surely there are such things as academic censorship, religious censorship, etc.

Because none of those things have the force of law backing them.

Academic censorship? Start your own journal and publish there. Religious censorship? Start your own church and gather your followers. Forum censored you? Start your own website where they have zero say about anything and write about whatever you want.

Government censorship? You are screwed, and you go straight to jail if you try to break free and start your own.

Because not everyone who can write an academic article also has the ability to establish and run an entire publishing business. Just because they technically could doesn't mean they realistically can.

Moderation is censorship, because moderation is an editorial choice. The fallacy is that all censorship is bad, not that moderation is censorship. Not all content needs to be given consideration in all contexts. In fact, if that were somehow an inherent good, actual communication would be impossible as noise overtakes signal.

This is really insightful. TY for sharing

Government moderation.

It's fine both to "moderate" your own repo, as well as to "censor" your own repo. No need to play word games or demand that strangers that you owe absolutely nothing to can't be upset. They can be upset, and you can ignore them until they go away.

>Which in itself would summon the vitriol of the super-trolls. "Moderation is censorship" is the most absolutely ridiculous mantra to gain traction in the last decade.

Even worse is "moderation of this kind would disproportionately impact disenfranchised LGBTWBIPOC+ users since they're more likely to have new accounts", "gatekeeping" is therefore racist, etc. ad nauseam.

That's for sure is the most absolutely ridiculous mantra to gain traction in the last decade.

GitHub has the option to limit issues, pull requests and comments to not-new users, previous contributors and/or previous committers.

The setting applies to a whole repository.

IMO, those are temporary and meant for cool offs, they're not a real RBAC solution.

I think the level of granularity isn't high enough. Ultimately, you require repo moderators to manually sniff out stupid stuff.

I agree, platforms without gatekeeping tend to be toxic. Well platforms with people tend to be toxic, really. It's best to avoid those.

I think it's partly developers fault for hosting their applications on Github and sending end users a link to Github instead of a link to an exe.

At least sourceforge has a download button in the front page.

They turned Github into a social media.

# Well-Kept Gardens Die By Pacifism

> Good online communities die primarily by refusing to defend themselves.

> Somewhere in the vastness of the Internet, it is happening even now. It was once a well-kept garden of intelligent discussion, where knowledgeable and interested folk came, attracted by the high quality of speech they saw ongoing. But into this garden comes a fool, and the level of discussion drops a little—or more than a little, if the fool is very prolific in their posting. (It is worse if the fool is just articulate enough that the former inhabitants of the garden feel obliged to respond, and correct misapprehensions—for then the fool dominates conversations.)

Read the whole thing:

https://www.lesswrong.com/posts/tscc3e5eujrsEeFN4/well-kept-...

That’s rose coloured. Maybe people were more intelligent, but even 10 years ago people would absolutely flame each other in GitHub issues on public projects.

I suspect the author is thinking back to more than ten years ago.

But yes; even newsgroups, BBSes, etc. were subject to this kind of stuff. People have always been people, even smart people with money to purchase computers.

>I suspect the author is thinking back to more than ten years ago.

Yes, "good ol' days" types will always move the goalposts further and further back when you point out that things were exactly the same in the mythical time period they want to return to

There were days when internet search engines had operators and really showed results, not "relevant" SEO.

Botnets weren't a thing, either.

But OP was talking about humans' behavior toward each other - I'll grant that SEO-spam maybe falls under that, but I don't think that Google's leadership fucking up search results is the same.

I wholeheartedly agree with the general message of the essay, and it really explains my experience with groups.

Pacifism only works if there is someone who can protect the pacifist.

In the Christian religion, God ultimately protects the virtuous pacifists by putting them in Heaven, away from bullies. In an online forum, there's no transcendental force to render such a service, so...

This is only true for a very narrow definition of pacifism. It is the literal reading of Matthew 5:39.

But not even all Christian scholars subscribe to that definition, let alone pacifists in general. Many pacifists are perfectly ok with self-defense.

Certainly, not all Christians are pacifists, and not all pacifists are Christians.

But, to my mind, pacifists choose to not fight back by definition, or that would be violence, so their prolonged existence is only possible because other social mechanisms hold back violence which would destroy them. Interaction with these mechanisms may be the point of holding a pacifist position: say, a monk or a nun may have a higher moral authority because of a declared personal abstinence from any violence, and hence indirectly incentivize lay people to protect them.

Of course there are people who call themselves pacifists but admit a right for self-defense, but only not organized or military; such a position again is only possible when someone else would partake in a defensive warfare and protect them.

Abstaining from aggression while being ready and willing to respond to aggression with full force, lethal when required, looks to me like the most logical "lawful good" position. It has a chance to produce an equilibrium when multiple parties live in peace for a long time, and any violent deviations are quashed.

"But, to my mind, pacifists choose to not fight back by definition, or that would be violence, so their prolonged existence is only possible because other social mechanisms hold back violence which would destroy them."

Again, this is a valid, but narrow definition of pacifism. One that is more often found in misguided Christians who take Mathew 5:39 literally than serious scholars. The willingness for self defense does not preclude pacifism at all.

A good example is Mahatma Gandhi who is widely recognized as a pacifist, yet argued that it is better to fight than to be a coward in the face of injustice.

Mr Gandhi was smart and used the social mechanisms of the British empire. The enlightened citizens of the metropoly, with their heightened sense of fair play, would strongly disapprove of police / army brutality towards peaceful and outspoken protesters.

The classical thought experiment replaces the British Raj with a German, or, better yet, Soviet occupation administration. With them, peaceful protests spectacularly won't work, and would be insane to try.

(Right after the independence was achieved, the land descended into a brutal war that claimed 20M dead, the death toll similar to that of WWI.)

    say, a monk or a nun may have a higher moral authority because of a declared personal abstinence from any violence, and hence indirectly incentivize lay people to protect them.

To take that a step further, making the pacifist definition even narrower, wouldn't such a pacifist be a hypocrite?

Abstaining from violence at the expense of others putting themselves in harms way to protect them?

Shouldn't they try to make these "lay people" abstain from violence as well?

But then who is left to defend the pacifists?

Does that mean in the face of outside aggressors all pacifists will die soon or live horrible lives under oppression from the aggressor?

Which I guess is OK for them if they believe that something better is available for them in 'heaven'?

Not necessarily, or even not likely a hypocrite. If keeping the ritual cleanliness is important for the monk's job, that is, having a better contact with the divine for the benefit of those around him, this is just specialization. The monk likely also abstains from other things, like eating meat, or having sex, which is a part of the same self-sacrifice for the sake of his service.

It would be hypocrisy if the monk commanded others to fight instead of him, while also declaring that he finds violence morally debasing and thus unacceptable for himself. But I don't think that laypeople would respect such a figure.

Putting anything to a public environment, always assume an actively hostile environment. No matter how many well-meaning users you may have; if it's more then a handful, there will always be enough jerks who would try to ruin the show for everyone.

To my mind, premoderation is the way. Any new user's submissions go to the premoderation queue for review, not otherwise visible. Noise and spam can be rejected automatically. More underhanded stuff gets a manual review. All rejections are silent, except for the rare occasion of a legitimate but naive user making an honest mistake.

What's passed gets published. Users who passed premoderation without issues for, say, 10 times, skip the human review step, given that they've passed automatic filters, so they can talk without any perceptible delay. The most trusted of them even get the privilege to do the human review step themselves %)

One thing I wish the tech companies would do is to use LLMs for junk moderation. At least to flag potential junk.

Meta uses they LLMs to summarize comments already and can do this, yet they choose to allow obvious crypto scammers, T-shirt scams, “hey add me comments”.

A simple LLM prompt of “is this post possibly a scam”, especially for new accounts, would do wonders. GitHub could likely do it too.

Just a matter of time before we get newsletters selling guides to earning $50,000 weekly by finetunning your L-MO business

L-MO = Language Model Optimized

It's not just the gatekeeping, it's the fact that people collect stars and reputation on github because it's something that can be spent.

I run an app that Serves a small, specific demographic.

We get about 50% [obvious] spam/scam signups (only 5 or 6 a day).

That’s pretty sobering, when you consider that it’s a very low-profile, unpromoted, region-locked (US, Canada, Ireland, and India), iOS-only native app.

We vet each signup manually.

Same here. I run a tiny Wordpress site that organizes private poker games for a local ~40 person league. We get maybe 5 signups a year from actual new members. We have it so that only admins can create new user accounts.

Once, that option got turned off accidentally and anyone could sign up. We got about 10 signups a day until I reverted the change, all spammers and bots.

The server logs also show that we get hit by script kiddies dozens of times an hour. This is such a tiny scale operation, with no meaningful commercial activity going on, but anything exposed to the public internet should be considered under attack 24/7.

That's the fundamental platform with all online platforms. It's their own form of carcinization.

The problem is that to outsiders, the initial set of gatekeepers who arose naturally in the early community as "the people that knew what it was about" will themselves appear to be "the toxic assholes", so every community will naively eventually cut out its gatekeepers to be more inviting to newcomers.

Only to have the actual toxic assholes flood in, become the new gatekeepers, and dominate the discussion, and suddenly your Faces of Evil speedrunning Discord must have a stance on the war on Gaza and the US election because we clearly need to keep out the neo-Nazis according to our CoCs, right?

And no, I don't have an answer to this other than to largely disconnect from online platforms and start engaging in your local community. Something I myself am not guilty of doing.

What does your OSS group do instead?

What does your OSS group have to do with this Winamp release, which was not OSS?

Most people aren't trying to be "useful". They're trying to be funny or get attention. For something as mainstream popular as this was, you can bet you'll get more jokers than aces.

You'd think "clout" would matter less to a community of tech, especially on a place dedicated to communities (hopefully) bettering the tech we use. But alas, people doing this probably don't think much farther than 15 minutes.

This is the internet, Boaty McBoatface is peak humanity here.

The issues are still preserved by archive.org, e.g. https://web.archive.org/web/20241009234026/https://github.co...

This is why archive was down?

It's WWII all over again with switched roles, and hacktivits DDOSed archive.org

What in the world does that sentence even mean in this context?

I don't see any credibility to the claim that 'BlackMeta' were/are in fact hacktivists. Do you have any reason to repeat that?

You can scroll their X page and it's extremely clear that they're focused on the Gaza war (https://x.com/Sn_darkmeta) and they openly state that they attacked the Internet Archive because it was based in America which supports Israel (https://x.com/Sn_darkmeta/status/1844358501952618976).

We can quibble about whether a "hacktivist" group can even exist at all or if it's a convenient lie the Internet has collectively told itself to justify groups of thugs attacking the targets they don't like as "the good ones", but they fit the modern definition of a hacktivist group.

I don't have a Twitter account, so I can't generally scroll on someone's page to see anything chronological-ish. :-\

(I remember trying at the time of the incident and having less success than now.)

Thanks for sharing the direct link to that video. At the time of the initial outage, I only saw some assertion that they were 'a hacktivist group' on some article on Bleeping Computer, and at the same time the only reason they'd claimed for the DDoS was 'because we could'. Hacking something just because you can is, of course, not doing hacktivism.

If these people are sincere, they are idiots in their propaganda strategy and artless in their 'hacktivism'... but definitely hacktivists.

But tbh this seems too stupid and ill-directed to me to be anything other than a false flag operation. ¯\_(ツ)_/¯

Either way, thanks for the additional context!

https://nitter.poast.org/Sn_darkmeta

Seriously, watching that unfold was hilarious. I also feel like some were being too harsh for no reason. The repo owner was responsive and merging PRs.

Might be another person than the one making the calls.

It is abit sad that they messed up the licensing. It would be fun nostalgia to run the 'real' Winamp on Linux. Native. Emulation does not count.

Wine Is Not Emulator.

And this image does not depict a pipe: https://upload.wikimedia.org/wikipedia/en/b/b9/MagrittePipe....

Giving WINE (originally WINdows Emulator) a cute backronym does not change the definition of the word emulator or whether Wine is one. Please check your favorite dictionaries for that.

It actually doesn't do emulation but API AFAIK.

Correct - the instructions in the Windows PE executable run natively. WINE provides a PE loader for exe and dll files (https://github.com/wine-mirror/wine/blob/master/dlls/ntdll/l...) and provides its own version of the API (user32.dll, kernel32.dll etc)

Doing windows API is emulating windows

> In computing, an emulator is hardware or software that enables one computer system (called the host) to behave like another computer system (called the guest).

https://en.wikipedia.org/wiki/Emulator

Interesting. However WINE is not in this list: https://en.m.wikipedia.org/wiki/List_of_computer_system_emul...

It's an OS or API emulator, not a computer system emulator. It's a different scope, but still fits the definition of an emulator.

DOSBox is on the page, at [0]. IMO Wine should be on the page as well.

[0] : https://en.m.wikipedia.org/wiki/List_of_computer_system_emul...

> Giving WINE (originally WINdows Emulator) a cute backronym

https://www.winehq.org/about states that it was an acronym for "Wine Is Not an Emulator", and it isn't now, the opposite of what you claim. (I don't really believe winehq, but I can't find the original discussion on newsgroup archives.)

> And this image does not depict a pipe

In fact, it does. Literally, "This is not a pipe," because an image of a pipe is not a pipe.

From the artist:

> The famous pipe. How people reproached me for it! And yet, could you stuff my pipe? No, it's just a representation, is it not? So if I had written on my picture "This is a pipe", I'd have been lying!

Sourced from Wikipedia: https://en.wikipedia.org/wiki/The_Treachery_of_Images

Wine is not emulating anything, but giving you a PE loader and a Win32 API on top of your Unix.

I thought it was funny until a couple hours later I checked back and some people, who probably think of themselves as much more funny than they actually are, were straight up being cunts.

We never had the code actually. That code is of no use to me without a proper license.

Being able to read it was better than not.

Even without a license, this at least allows people to archive it before it is lost completely.

The other thing we lost is that future companies will think again before making their code public. It's already such an incredibly rare thing in the wild, but now companies and their lawyers will see that Winamp was exposed to potentially lawsuitable behavior that wouldn't have come to light had they never opened the code.

All of this happened because the company didn't want to open source the code, they wanted to openwash it and get free labor from the open source community. If another company wants to do the same and they decide not to because of this, nothing of value is lost.

> they wanted to openwash it and get free labor from the open source community.

This is such a ridiculous accusation. Why do discussions about source-available models often turn into accusations of soliciting free labor? Why can't authors just provide access to source code, but reserve some or all of the distribution rights? It's their code, after all. Nobody is forcing 'the open source community' to contribute under the terms set forth; anybody who does contribute does so under their own free will, under the terms set forth by the license.

It doesn't always have to be a binary choice between open source and closed source, nor does it justify further accusations of "openwashing."

What is the point of 'open source' where you're not even allowed to fork the damn repo?

To read and learn what a very successful project's codebase looks like.

I find value in every one of these types of releases. Sometimes that value is just a chuckle... knowing even successful codebases are as duct-taped together as all the rest.

In case of security sensitive software, you could verify the security claims.

Look at Apple, they claim E2EE, but don't even allow to verify that defeating the purpose of E2EE entirely (lack of need to trust the provider)

You can do that with source-available software too, I'm not sure where you think open source comes in?

My point is that Open Source isn't necessary for it, aka "open source without forking" is sufficient

There is no such thing as "open source without forking". It's source available.

I don't care how you call it.

My comment was a reply to a comment which described it this way.

You can make a source available license and no one will criticize you for it. You put in the license "you can look, but you can't touch". When it becomes openwashing is when you instead write "you can look but you can't compete with us, also feel free to give us a hand". Let me cite:

> * Contribution to Project: You are encouraged to contribute improvements, enhancements, and bug fixes back to the project. Contributions must be submitted to the official repository and will be reviewed and incorporated at the discretion of the maintainers.

> * Assignment of Rights: By submitting contributions, you agree that all intellectual property rights, including copyright, in your contributions are assigned to Winamp. You hereby grant Winamp a perpetual, worldwide, non-exclusive, royalty-free license to use, copy, modify, and distribute your contributions as part of the software, without any compensation to you.

> * Waiver of Rights: You waive any rights to claim authorship of the contributions or to object to any distortion, mutilation, or other modifications of the contributions.

>Nobody is forcing 'the open source community' to contribute under the terms set forth; anybody who does contribute does so under their own free will, under the terms set forth by the license.

And? Yes, we're all acting out of our own free will. The owners of Winamp decided out of their own free will to release their code under those terms, and I'm criticizing them for trying to take advantage of people also out of my own free will. What's the issue?

> When it becomes openwashing is when you instead write "you can look but you can't compete with us, also feel free to give us a hand".

With all due respect, I don't think you know what open-washing means.

Well, enlighten me. What does it mean, and why was this not openwashing?

Didn't the original version of their license state that you weren't allowed to do anything with the code, including forking it? It was "source available" but you're not even allowed to make a local copy of the code to look at it. People as a whole don't mind source available, Louis Rossman's FUTO's software is all source available and while they got a small minority of FOSS diehards complaining about it, they're doing great. Immich, FUTO Keyboard, FUTO Voice input, and Grayjay, are all source available, but the company was honest and didn't try to pull stupid shit like "you're not allowed to fork the code" in their license.

To me, this seems to be a misunderstanding of the license text and the author's intent. The original license simply reserved all distribution rights. People assumed you couldn't even fork into a public GitHub repo in order to make pull requests, but afaict, the author clarified that the intent was not to prevent forking on GitHub, but to prevent redistribution of the forked software instead of contributing the changes back upstream. The right to make changes to the software for internal use was always there, afaict.

How the hell do you combine "open source" and "all distribution rights are reserved for the original developer"? That's a nonsensical combination, the whole point of open source is that you can make your own copy with your own changes and distribute it to people

I guess it's readable source instead of open source.

You are confusing Open Source with Free Software. GPL family of licenses are the ones propely securing everyone's right to distribute modifications.

This is wrong. Permissively licensed (MIT, BSD, WTFPL, Apache, etc.) free software is still free software. Open-source requires the provision of the same right to distribute modified copies as free software does.

Copyleft licenses like the GPL assert the same right recursively for downstream users, more or less (details vary between copyleft licenses). But granting the right (to distribute modified copies) to first-order recipients of the source code is common to all free and open-source licenses. That's great! I imagine it's what you're getting at with the phrase 'properly secured'.

But to qualify as open-source, a license must allow redistribution of modified copies, and copyleft is not the only kind of free software license

See (for instance) the Free Software Foundation Europe's FAQ entry 'what is open-source software?':

https://fsfe.org/freesoftware/legal/faq.en.html#opensource

as well as the Criterion 3 of the Open Source Initiative's open-source definition: https://opensource.org/osd

Ah yes the totally unbiased OSD made by companies wanting to exploit free labor like Amazon.

I dislike prescriptivist language. I will continue calling things open source whenever I can see the source code, no matter the license.

> Ah yes the totally unbiased OSD made by companies wanting to exploit free labor like Amazon.

The OSD does not originate with Amazon. Its ideas and text are drawn from the free software movement and indeed from a not-for-profit, volunteer-driven, community-based project-- namely Debian. Its text is essentially lifted from the Debian Free Software Guidelines. The term 'open-source' was created to describe an effort by a commercial entity, though-- for the project that would eventually give us Firefox, at a time when the web was dominated by a deeply proprietary monopoly in Internet Explorer.

But all of this should be common knowledge among 'hackers'. At any rate it is extremely easy to discover.

> prescriptivist language

Talk about knowing enough to be dangerous! lol.

> I will continue calling things open source whenever I can see the source code, no matter the license.

Okay? You are successfully resisting being nagged about your use of terms. You are also broadcasting your ignorance of the giants whose shoulders software developers stand upon today.

Software, like many things that can satisfy human needs and wants, is an instrument and mechanism of power. In particular, software and the terms under which it is distributed are often a mechanism by which the software publishers exert power and control over the software's users. 'Open-source', like its more frank ancestor 'free software', exists to signal terms of software distribution that variously protect users from certain strategies of domination by software vendors. Historically (and recently!), that signal associated with the phrase 'open-source' has been a fairly clear (if simplistic) one, because the phrase's usage has been consistent.

When you choose how you will or won't use the phrase 'open-source', you are making a choice about how useful a signal that phrase will be for such purposes in the future. What language is 'correct' in this case gets at a practical and political question we can alternatively get at without any commitment or appeal to a notion of linguistic correctness. That question is this: should there be ready ways to identify terms of software distribution that seek to spare software users from domination by software suppliers?

If one's answer to that is 'yes', then it takes a bit of footwork to get to 'I intend to participate in applying this established safety label to unsafe things'.

> calling things open source whenever I can see the source code

This kind of behavior is arguably a predictable outcome of the strategy of distancing the licensing tactics of the free software movement from that movement's explicit politics, articulations of its on motivations, etc.

No, I believe you're confusing source available with open source.

I never said Winamp was open source? It's very clearly source-available.

Immich is AGPL-3.0, which I would consider to be fully open-source. They do “sell” it but you’re also allowed to just download it, do whatever you want with it including removing the key system, so long as you share the source code.

I was not aware of the FUTO license. I found it here: https://gitlab.futo.org/keyboard/latinime/-/blob/master/LICE...

Openwashing: https://web.archive.org/web/20241008220257/https://github.co...

Did the authors claim to be open source somewhere I must have missed?

Without that, I don't see how this is open-washing...

Yes, actually.

>The Winamp Collaborative License is a free, copyleft license for software and other kinds of works.

Hmm, I must have missed that. I stand corrected, then. Perhaps the author thinks copyleft can be divorced from open source? They didn't claim to be open source here, but they do claim to be (very strong?) copyleft -- almost like a single-source copyleft kind of interpretation. But yeah, I get it now. ty

As others have pointed out, it's very likely the "author" was an LLM. It's clear no lawyer ever gave this a once-over. I can easily imagine a manager telling ChatGPT "write a copyleft license that doesn't allow other people making modified versions of my software".

Llama Group laid off the team who had been working on Winamp and then released the source code under a license that bans users from distributing modified versions of the code themselves and assigns copyright on any contributions to Llama Group. IMO this absolutely points to them hoping that releasing the source code would let them offload Winamp maintenance onto the community.

That's entirely speculation. They could just as well be winding down the project entirely, which has happened before.

It's not speculation. Someone claiming to have been an employee posted a comment to the article. It's impossible to verify, but personally I have no problem believing it played out as they say.

If they're winding it down, then they may as well make it fully OSS, and ditch the components that are proprietary that they can't release. Attribution can get complex with old software IP, especially when using such proprietary components.

> Why do discussions about source-available models often turn into accusations of soliciting free labor?

Simple. Because the company literally wrote this in their press release[1] at the time they were releasing it.

Direct quote “This is an invitation to global collaboration, where developers worldwide can contribute their expertise, ideas, and passion to help this iconic software evolve.”

Further direct quote: “With this initiative to open the source code, Winamp is taking the next step in its history, allowing its users to contribute directly to improving the product.”

They are literaly soliciting free labor.

This is how the press release ends: “Interested developers can now make themselves known at the following address: about.winamp.com/free-llama” what is that if not a solicitation for free labour?

> anybody who does contribute does so under their own free will, under the terms set forth by the license

So wait. Just so I understand. Is your problem that you think they are falsely accused of soliciting free labour? Or that they are indeed fully were soliciting free labour but you would rather not want people harsh your vibes by discussing this?

1: https://www.llama-group.com/wp-content/uploads/2024/05/2024-...

My point is simple: if someone contributes, they accept the terms. Complaining about ‘free labor’ is irrelevant. The contributor chose to contribute; if they didn’t agree with the terms, they wouldn’t have. Nobody is asking for an uninvolved third-party to police the collaboration.

I'd also be careful attributing these actions to malice without further motive, when it very well could also be attributed to excitement i.r.t. sharing and collaborating on Winamp's source code in public, under a single-source.

> attributing these actions to malice without further motive

these actions could be construed as malice, but i would definitely attribute them as greed. AKA, they want contributions, but want to prevent anyone else but themselves from being able to commercially exploit it.

> if someone contributes, they accept the terms

That assumes that everyone has full information of course. Discussing the terms publicly is helping everyone reach that state.

> Nobody is asking for an uninvolved third-party to police the collaboration.

And someone is asking you to police what people are chatting about here? Doesn’t feel to be an entirely thought through argument.

> I'd also be careful attributing these actions to malice without further motive

I don’t actually care if they are “malicious” or “inept” or “ill informed” or anything else. In fact I think someone was excited about the open collaboration, and someone else at the company was worried about losing business opportunities and that is how we ended up with this situation. Maybe it was even the same person at different times.

Maybe they heard about open source but never really understood the concept, and the motivations of people participating in it.

Or maybe they are just as greedy as they appear to be.

Who knows and who cares. What matters is that this is a rough deal and people should not play within their rules.

I agree that as an author, you’re free to pick any license you want. If you want to release source code just to allow PRs, and don’t market it as open source – go for it.

Fair Source is a better model in that regard, kudos for using that! And I personally have no problem with using the term “open source” for that, although just using the distinct term is better.

In case of Winamp though, they:

1. Used a crayon license that prohibited pretty much everything and was indeed focused on collaboration

2. Made a press release about “opening up” the source – not using the exact phrase “open source” (except in the URL: https://about.winamp.com/press/article/winamp-open-source-co...), but misleading nonetheless

3. Weren’t even the original authors

This is openwashing, and it is ridiculous, and they were rightfully shamed.

Maybe they _should_ think before making code public - it is generally a good idea ;)

I think we all would have been better off, with time & energy better spent if they had never tried to release like this, so discouraging others of trying to do the same is a feature, not a bug. For example, consider how much time I spent reading your comment & composing this response; it would have been better spent closing my eyes and taking some deep breaths for a minute or two.

Yeah, it really whipped the llama’s ass…

Here is a mirror of the repo, as of the last commit before it was deleted:

https://git.cbraaten.dev/AtRiskRepos/winamp

Also here is a git bundle file which can be cloned from:

https://litter.catbox.moe/dwhadv.bundle

Thank you for doing the lord’s work.

Winamp contained modified GPL code, violating the GPL (github.com/winampdesktop)

18 points by mepian 19 days ago | 6 comments

Thanks! Macroexpanded:

Winamp contained modified GPL code, violating the GPL - https://news.ycombinator.com/item?id=41662105 - Sept 2024 (6 comments)

Winamp removed "No forking" restriction from license - https://news.ycombinator.com/item?id=41650355 - Sept 2024 (12 comments)

Winamp Legacy player source code - https://news.ycombinator.com/item?id=41636804 - Sept 2024 (328 comments)

I can't see the original issue, but it's interesting that the title chooses to highlight the fact that the GPL code was modified. Actually, under the GPL, this fact is immaterial. If the Winamp player contained any GPL code at all, modified or not, then it is a derivative work of that GPL code and anyone receiving a copy of Winamp is entitled to demand the full corresponding source be provided under a GPL license.

The original issue was complaining about libdiscid which is under the LGPL license not GPL. With that license, linking to an unmodified library in proprietary software is fine. What's not fine is to link to a modified library without releasing the source code for that modification. (Of course here the modification is extremely simple so some concludes this is a nothing burger.) The original poster likely knew the LGPL difference and that's why everyone became fixated on finding the modifications to the library rather than the fact of linking itself.

> Of course here the modification is extremely simple so some concludes this is a nothing burger

But still a modification.

the point here is to solve the problem of linking to an LGPL licensed library, to comply you can:

a) release the code of the original LPGL licensed library

b) release it with a patch of any modifications, ie the small change here

c) nothing else. zero. No license changes. No other code of the app affected. No app code needs to be released.

And you are compliant with the LGPL license and can get on with life. So this is not a big deal the way GPL code in the app would be which would require the app code to be re-licensed and released to comply, which is a huge deal and difficult to accomplish.

> With that license, linking to an unmodified library in proprietary software is fine.

Was it linked dynamically? Static linking to an LGPL library from a proprietary application is also possible, but way trickier.

> Was it linked dynamically? Static linking to an LGPL library from a proprietary application is also possible, but way trickier.

For a "shared source" app (i.e. source available but under restrictive non-open source terms), static linking is generally a non-issue, provided you give people permission to recompile the app from source with a modified library version, and you actually built the binaries you ship from the source you provide them (as opposed to some separate internal repo containing changes missing in the source you provide to your customers or the public). So, WinAmp currently would not be infringing even if it were statically linking modified LGPL libraries (assuming their source repo includes the source to the modifications) – although this may be evidence of past non-compliance.

Static linking is really only a big problem for proprietary apps where you don't give people the source code. Even there, so long as you ship them object files so they can relink it with an updated LGPL library version, you are fine. Once upon a time, linking at the customer site was not an uncommon strategy for enterprise software, in fact last time I worked with Oracle RDBMS (7+ years ago) it was still using that strategy for a standard install.

For LGPL 2.1, you don't even need to ship the object files or offer them for download – you just need to make an offer, valid for at least 3 years, [0] to supply them on request. LGPL 3.0 removed that provision, with LGPL 3.0 you have to either ship them or offer them as a separate download.

[0] I believe the "3 years" is from the date you ship each individual copy of the software. So if you released version 1.0 in 2001, and it contained a "valid for 3 years offer", if you are still offering version 1.0 for download from your website in 2024, that offer is valid until 2027 for someone who downloads it today. But if you removed version 1.0 from your website in 2005, and since then have not given anyone a copy, then the offer would have expired in 2008.

> Actually, under the GPL, this fact is immaterial. If the Winamp player contained any GPL code at all, modified or not, then it is a derivative work of that GPL code and anyone receiving a copy of Winamp is entitled to demand the full corresponding source be provided under a GPL license.

That's just not true, surely? Lest everyone using any flavour of Linux is liable to the same problem?

How many apps out there are using GPL code? Android, for example.

Making a derivative in the sense of adding functionality to it, I get, but using it as-is as a component or library surely doesn't - and cannot - fall foul of the license else the entire technosphere is liable.

It is if you link it into your address space. If your code wants to be non-GPL then it needs to have some kind of barrier between it and the GPL code that it uses. For Linux, that would be the kernel syscall abi. But normally it's the process boundary. For example, if your program spawns the GNU gperf command, then its GPL license doesn't apply to your program. Furthermore, the generated code that the gperf command prints to stdout, is not encumbered by the GPL. In other words, the output of a GPL licensed program belongs to you. But if you were to copy gperf's .c files into your codebase and use their perfect hash table algorithm, then your software would become GPL encumbered, but only if you distribute. They will sue you and spare no quarter if you don't give your users the same freedoms that they gave you. Even if the gperf dev team doesn't do it, then some other org representing someone who contributed a bug fix once will. You can't hide and there is no time to survive, because GitHub can be easily monitored using tools like BigQuery.

> spare no quarter if you don't give your users the same freedoms that they gave you.

What? The actual history of GPL enforcement is restrained when it comes to remediation. Are you aware of some routinely punitive GPL enforcer that I am not? Or is this FUD or a joke?

I hope I've not missed some news about your own projects and that you've not been subject to anxiety or meanness on account of the GPL, either. :(

If you are linking against GPL code then yes it's true. If you are linking against LGPL code then it's fine. Note that running software on Linux doesn't mean you are linking to Linux. However, if you distribute Linux, then yes, you must supply the Linux source code on request.

The "technosphere" is generally fairly compliant on these things. There is no disaster. But this is also why most commercial companies avoid GPL libraries.

> Note that running software on Linux doesn't mean you are linking to Linux.

Technically, you do link to linux-vdso.so (or variants depending on architecture), which is part of the kernel image. There doesn't seem to be an explicit GPL exception for the sources of this library [0] but the general syscall exception [1] may or may not apply.

[0] e.g. https://github.com/torvalds/linux/blob/master/arch/x86/entry...

[1] https://github.com/torvalds/linux/blob/master/LICENSES/excep...

Yes, it's true. There's a reason GPL is called copyleft.

> Lest everyone using any flavour of Linux is liable to the same problem?

The kernel is GPL. applications running on it in usermode are not constrained by the license.

https://www.gnu.org/licenses/gpl-faq.en.html#PortProgramToGP...

You can have copyleft without virality; the Mozilla Public License 2.0 requires any modifications to a covered work to be released under the same license (copyleft), but does not extend this requirement to other code included in a combined work (virality). As I read the license, you could embed the Gecko browser engine in your proprietary e-reader software, and only your changes to the engine itself would have to be released as free software.

The devil is in the Details. Usually a licence is applied to a single library or compilation unit.

> That's just not true, surely?

It is true.

> Lest everyone using any flavour of Linux is liable to the same problem?

The Linux kernel has an explicit "system calls are not linking" exception to avoid any possible confusion on this matter.

https://github.com/torvalds/linux/blob/master/LICENSES/excep...

Merely using the kernel's facilities from user space does not make your program a derivative work of the kernel.

> Android, for example

Yes, OEMs are expected to release their kernels' sources. Also yeah, they're mostly very bad at it.

> Lest everyone using any flavour of Linux is liable to the same problem?

If by that you mean, if you are using Linux in production servers: You may use GPL software in a commercial setting. The source code part only applies if you are distributing software that contains GPL code.

Winamp came onto the scene about the time I was learning to really code and there were a few projects I didn’t start because the wisdom at the time was of a poison pill/ship of Theseus variety: if you use code you didn’t write as scaffolding to write a new system, even once you’ve replaced all of the sections of the code you borrowed with completely new code, you are still stuck with the old license.

One of the reasons libraries are useful. You can replace the library in one go and if you do it right (ie, don’t replace it by the same modification process described above) the license is moot.

I worked for a company that did sales in Europe and we ran afoul of a public domain library. At the time the EU didn’t recognize PD release as a legal act. One library was easy enough to replace with a similar one, the other had no suitable peer. Luckily the library we used was small and we didn’t use much of it, but that use was important.

I wrote a bunch more unit and functional tests in our code to serve as pinning tests, then asked a lead dev on another team to write a library to replace it without referring back to the existing code. I’d stepped through it enough I could practically rewrite it from memory. I knew that wouldn’t stand up legally, but he had no reason to obsess about that part of the code. Nearly took me longer to explain the gambit to him than it did for him to complete the task once he understood it.

I think the point here is that so that people reading the article don't complain about "they didn't contain GPL code directly" somehow justifies thinking that that was bikeshedding and not a legitimate violation of the license. Of course, it does not matter if the code was modified or not, but that point might not be clear to the readers who don't have enough experience with GPL.

Someone found a prehistoric hand axe on their property. They realize it must have been one of the nicest hand axes of its time. They decide to donate it to a museum, so everyone can appreciate that marvel of human civilization.

Being an extraordinarily nice axe, its original creator must surely have taken proper care of it and kept it clean, but over the years it clearly accumulated some dirt and a few modifications. Not wanting to damage an important historic artifact, the finder decides to leave the patina alone and donates the axe as found.

The museum requires the donor to add an exhibit label. Unfortunately, the finder being Belgian and speaking only French, there is a severe misunderstanding about the purpose of the axe.

On the day the exhibit is first shown to the public, hell breaks loose. People threaten to sue because the dirty prehistoric axe is against all regulations that apply to contemporary axes. Some attempts are made to remove the dirt, but only in a way that preserves the dirt, which enrages the other camp even more.

Ultimately, the exhibit is withdrawn from the museum, but luckily many had a chance to make copies and 3D copies that they keep safely in their private collections.

Isn't it more apt to say that the people who donated the axe to the museum were the same people who originally made it, and that the axe was illegal when it was made as well as today?

I may totally have missed details here, I haven't paid attention much, so please do correct me if I'm wrong

This is a good question and I have to admit that I have not thoroughly researched it. My understanding is that the original creators (Justin Frankel and Dmitry Boldyrev, later Nullsoft) the people who spoiled it (AOL) and the finder (Radionomy = Llama Group) are separate entities.

Most of the blame should be with the people who spoiled it, and while it doesn't excuse their deeds they are unsurprising from a historical context.

The current owners of Winamp share some blame too, but I see it more in the neglect of due diligence when they acquired Winamp and less in the release of the source. Arguably I see more incompetence (which, of course, is no defense against punishment) than malice in the later.

Finally, that the original authors kept the Winamp source clean is a reasonable and likely assumption, but as far as I know there is no 100% way to be sure.

> and I have to admit that I have not thoroughly researched it

So basically anything you say is speculation?

Im going to add my own unfounded speculation by claiming that the original winamp source did actually contain licence violations which is why the project was never re-released after being acquired by AOL.

Only after buying the project did AOL realise that the code wasn't usable as-is, so it needed further investment to rewrite and replace all the violations, and since at that point the value of local media-players was quickly diminishing they just let it be.

"So basically anything you say is speculation?"

No, just that it might not be the complete picture.

Until the original source from the Nullsoft days surfaces, we do not know, and certainly should not make unfounded speculations.

This, btw, is why open sourcing proprietary software rarely happens: you actually have to go to a fair amount of careful effort to get it right. If you don’t, you end up with this debacle.

Or maybe you just shouldn't break the law.

>shouldn't break the law.

What law? The law of the Gnu?

https://news.ycombinator.com/item?id=41662105

Not really. The reason in this case is that they wanted to share the source code exclusively for direct collaboration under their own direction; so they wrote an incomprehensible and incoherent license, and gave up after everyone called them out on their bullshit.

Well, of course you will have to be the more careful when open sourcing proprietary code, the more you illegally used copyrighted code earlier.

And here's another story to add to the book "How to shoot yourself in the foot by not knowing how the Internet and software licenses work", should anyone write that one day.

Also, from one ArsTechnica link posted later in this story, one former dev told that the 4 WA Legacy developers were fired and soon he left too, so I guess they presumably had either no one or very few resources who knew that code and were in the best position to audit it before public release. This is not just shooting oneself in the foot; it rather looks like dancing on a landmine.

I feel like there should be some kind of exception for proprietary code that's published in good faith. Though I'm not sure that could work if the company wanted to stay in control of the code.

It's not ideal if the way the software was written was itself illegal. Still the advantages of having it out in the open seem to outweigh the benefits of litigating all license violations.

Hah, called it:

https://news.ycombinator.com/item?id=41645867

> Oh.... they vendored everything, including a bunch of external x86 binaries. 32- and 64-bit. FFS.

> But also - I sure hope they got the licensing correct for those parts...

This story is analogous to a landowner and a group of neighborhood kids. The landowner allows the kids to play baseball in his field, but then the kids complain the grass is not cut, they are playing late into the evening, a few kids vandalize damage his flower bed, and his lawyers tell him he will be sued if he doesn't make all these safety changes, and so the landowner says screw it and puts up a fence.

Rather in this analogy the landowner didn’t own all of the field and somehow the kids get blamed for him failing to keep track of what he does and does not own.

Problem with analogies is that they are all made up.

Sort of. In this case, as other posters have mentioned, the "landlord" did some questionable things.

Agreed. How about the "landlord" expected the kids to cut the grass and weed the gardens house for use of the field, and only allowed them access on certain days and times.

More like the landlord wanted the kids to cut the grass for free so he gave them permission to look at the grass but not touch it and explicitly forbid playing on the grass. Oh and it turns out he doesn't even own all the land.

    > his lawyers tell him

Is this common in the US? I cannot imagine someone from Italy or France writing a post like this.

A generation ago kids would use other people's backyards or a company's land for play. It became less common due to fears of lawsuits. Example: https://www.reddit.com/r/AskALawyer/comments/1czlq5k/who_is_...

It's wild to nitpick the licensing like this. I get why its conter-intuitive and in violation of Github's guidelines, but it's winamp, folk. It has no intrinsic value these days to update or fork outside of giving people the opportunity to learn from the tricks they had to do to make stuff work. There are solutions significantly better and open source today. 'Canceling' winamp in 2024 was not on my life's bucket list after the year 2000.

There is hypocrisy here around internet archive, it's totally OK to store copy-write content on the archive, but its not OK when a company does so on their own.

>It's wild to nitpick the licensing like this.

It's not a nitpick, the library was self-contradictory. It claimed to be copyleft while not allowing distributing modified copies by anyone other than the rights holder.

>There is hypocrisy here around internet archive, it's totally OK to store copy-write content on the archive, but its not OK when a company does so on their own.

That's right, because it was the company that broke their contract with their vendor by making publicly available source code when they didn't have permission to do that. If that software vendor has a problem with the IA they can issue a DMCA request.

Don't redistribute this software, but we're gonna redistribute some close-source software out of carelessness. Rules for thee, not for me.

> In seeking to remove offending files with a simple deletion instead of a rebase, Winamp kept it available to those who know Git mechanics

"Those who know Git mechanics" in this case is talking about extremely simple Git mechanics. Those who know more advanced Git mechanics would know that even a rebase is not sufficient to solve the problem of having pushed up secrets.

Aside from the obvious problem of all the forks and previously-cloned copies, the offending commits will still also be available on GitHub (at least until the next garbage collection), they'll just have the message "This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository."

Any links that include the old hash will still be available online and will still turn up the code you tried to delete.

> offending commits will still also be available on GitHub (at least until the next garbage collection),

No. Forever. Literally forever. GitHub does not run garbage collection, like, ever.

https://stackoverflow.com/questions/4367977/how-to-remove-a-...

Dangling commit from 14 years ago :

https://github.com/nylen/connectbot/commit/1cd775d

There is only one way to delete data on github permanently and that's to request it from github support. Still, you would have better luck just deleting your repository and starting over from scratch, deleting your history locally and pushing from a pristine state.

Hmm, do they count dangling commits towards your quota?

Which makes sense because just being orphaned within git doesn't mean that there aren't any external references from PRs or just comments that people expect to be able to view.

And of course for actual secrets (as in passwords/keys/etc.) having deleting them from GitHub is not going to help you anyway as others could have made local copies that you have no control over.

This is a cautionary tale for preservationists. My current preservation project is still not open because we are very slowly reviewing the code to make sure we don't accidentally include any IP when we open the source code. The real things that get you are similar to what happened here: codecs, graphics libraries, and a really big one to look out for is fonts. It'd be great if there was a scanner that could detect this stuff, but unfortunately, the scanning tools out there tend to go the other way like Black Duck: they detect open source code, not closed source.

I suppose it could be done, like those plagiarism databases used for academic work. Security would need to be tighter though. It's a hard thing if the source code needs to be protected I suppose.

The thing is, the vast majority of graphics libraries from 1992 the IP owner no longer cares about, and the code usually has nearly zero commercial value.

I wish more were brave enough to just publish it with an open license, and then if the owner complains you take it down and rewrite.

Any damages for distributing 30 year old source code are hopefully in the single-digit-dollars range anyway.

The problem is you'll get crushed by legal fees in the meantime.

but if courts gave out damages of $10 for this sort of offence (taking into account the very low commercial value of the IP stolen), then very few people would even bother pursuing it in court.

Courts do not do that. The people suing would offer up a big old list of damages into the millions and then negotiate down from there to something like 6 figures AND the loser covering the court costs. The American legal system is completely broken, and amounts to two people piling up money, then the one with the bigger stack wins both stacks of money. This is completely untenable for a non-profit to even think about, let alone to incur the risk.

>> The people suing would offer up a big old list of damages into the millions and then negotiate down from there

You're assuming an awful lot with this.

- No defendant is going to negotiate a settlement out of court. They would force you to hire an attorney and force this to a trial because of how absurd it is.

Then you would be left with other major issues:

- One that any IP law firm would take a case like this on to begin with.

- The little upside for any firm litigating a case where the software is 30+ years old, effectively abandoned and has little if any resell value.

- Then even if some firm did want to take a swing at it, getting this in front of a judge who would even consider the case would be a huge hurdle as well. We're not even considering having to deal with a jury trial either which would also be even harder to win.

- Even if the defendant refused to negotiate pre-trial, and you somehow managed to finagle yourself into a civil bench or jury trial, trying to convince anybody that the plaintiff has somehow sustained financial damages on 30+ year old software that is no longer being used and has no resale value is almost impossible.

The US courts are not perfect, but these kinds of cases rarely see the inside of a court room and for good reason.

OK, so my non-profit with a budget of about $200,000 a year is now expected to lawyer up and take on this risk, where some random company can just sidle up to us, sue us for X, and automatically win because we cannot possibly afford a lawyer to even respond to their litigation?

I love how utterly diconnected from reality HN comments are. Y'all seem to think that just because you can rationalize something on paper that we should all just go out and do the thing because the laws are "Stupid." If the world ran like HN thought it did, we'd have no copyright laws, no patents, and infinite free legal advice and services. Yeah, yer right, maybe we could get a sympathetic judge or get the case tossed. After we spend $100,000 on lawyers to get there. Oh, the prosecution would have to pay our legal fees you say? Great, now I'm out $100,000 waiting on the appeal, and it could take years for them to pay up. That's like giving them a $100,000 loan with 0 interest and no defined closing date.

And what's even the upside? I ruined my non-profit so I could spuriously open source some random crap I don't even want to preserve. I have the binaries already, I don't need to recompile. But hey, no one is using this stuff right? Fuck the law!

The world does not work this way. If a lawyer shows up and wants to kill a small non-profit, they can do it in a day, very easily. They don't even need the courts, they just have to sue you and then bomb you with 50,000 pages of evidence. This is a REAL tactic. How do you counter that without paying a lawyer to look at all 50,000 pages? The key is to not give them a reason to do so. You know, by not breaking the fucking law.

If you're willing to take on such an economical risk, why don't you pony up the money and start serving the content?

At least in the US, loser doesn't pay count costs for the opposing party.

This is entirely within the realm of the judge to do. They do it fairly frequently as punishment to people who bring bad law suits and lose.

Completely incorrect. This work is being done under a non-profit, and whether or not the original owners care is irrelevant. Doing this would immediately open the non-profit to litigation and endanger the entire project. Just because we don't think anyone cares doesn't mean we won't get sued.

This project is preserving the source code around a distributed chat system from the year 2000, the E programming language, and the first real usage of JSON. Outside of those aspects, it's not about preserving fonts and proprietary code.

You are literally suggesting that we take proprietary, copyrighted code and release it under an open source license with no standing, rights, or ownership. It's insane to even suggest this. If you put the source code for Windows 95 online, you'd be sued into a pile of ashes by MS within 10 minutes.

When we want to open source proprietary code, we work with the rights holders. This code was all given to us under such an agreement, and the agreement ONLY covers the code owned by the people who built this thing. The deal was contingent on us not opening any of the code the original owners didn't own, as that would ALSO incur risk for them.

> If you put the source code for Windows 95 online, you'd be sued into a pile of ashes by MS within 10 minutes.

The Windows NT 4 source code exists in multiple public repos on GitHub, and the one from the first Google result has been there for at least four years.

...and the ones for later versions are easily found on GitHub too --- GitHub, which is now owned by Microsoft.

On the one hand, great, but on the other, that's how much (little) they care about Windows as a source of revenue.

Ancient Windows NT code being available hardly threatens Microsoft's revenue from Windows sales.

As the video games people know, piracy is preservation and preservation nearly always requires "piracy". It's very clear from the way the Internet Archive works that pre-emptively taking a copy without permission is the only way to guarantee that copies actually exist.

> You are literally suggesting that we take proprietary, copyrighted code and release it under an open source license with no standing, rights, or ownership. It's insane to even suggest this. If you put the source code for Windows 95 online, you'd be sued into a pile of ashes by MS within 10 minutes.

Yeah, legal preservation efforts will probably never get that. The torrent is still out there if you just want to look at it, though.

What's isane is that you are not legally allowed to release code that hasn't had any commercial value whatsoever for ages or where it takes a full legal team to even find out who might "own" the rights. Copyright is positively bonkers.

Unpopular opinion: preservationism shouldn't care about licensing and legal nonsense.

Because what is the point if something is distributed in a restrictive license, can't be preserved and then gets lost to time? Also, licensing is to avoid distribution, modification or outright copying by competitors; preservation is completely orthogonal to those concerns. It is to avoid losing a piece of craft to the sands of time. There is no reason laws should have power over anything in perpetuity.

As seen in other spaces, pirates ignoring the "law" will provide the greatest service to humanity.

>preservationism shouldn't care about licensing and legal nonsense.

If it is reasonable that someone needs to preserve something because it has been abandoned, then the thing should automatically be in the public domain.

If you are not actively using IP for a reasonable amount of time, any patents, trademarks, copyrights, etc should be permanently expired.

This fixes problems with patent trolls too: you effectively would not be able to own a patent unless you were using it in your business.

Great idea except it won't make anyone money. Therefore it will never happen. Copyright law in America is not based on good ideas, reasonability, or even preservation. They are based on profit. Your idea is great, but we do not live in a world where good ideas matter at all. Only money matters here, and this idea will not make anyone money.

It's not a great idea, because law and policy are designed to privilege makers rather than takers. It's a subversive degenerate kind of morality to argue that things belong to the people who desire to consume them.

Damn, I wonder what book you read to make you so smart?

Justine is an impressive hacker, several of whose projects have made their way to the front page of this site before. She's plenty smart and that's plain to see.

Calling her stupid isn't a good way to show her (or anyone) that she's wrong about this.

The copyright clause of the US constitution, at least, is explicit that the artifice of temporary monopoly for copyright holders exists for the benefit of society as a whole, not (supposedly) for the rightsholders themselves. The benefit for rightsholders (who are only sometimes the 'makers' anyway) is merely instrumental.

It's the notion that IP is about protecting some kind of natural right that is a perversion, both historically (evinced in such language as the copyright clause) and ethically (I assert).

I agree and privilege is one of the ways you solve that.

Like the privilege of being less bound to engage in survival and political struggles. Evolution produced a world where if you want something, you have to take it. Makers aren't good at taking things because they're too busy making. The natural order is that makers would be marked for deletion, which is how it was for million of years before economies came into being that could support them. Since we know that life is good for everyone when stuff gets made, society is better off as a whole when it goes out of its way to support its makers, since giving makers more means they'll make more. OTOH if you lift up takers they'll just use it to take more.

The greatest most successful takers all know this, which is why many of them become philanthropists. Since there's not much point being a taker if there's nothing left to take. Once you've taken everything, the only way you can take more is by getting makers to make more. The supreme takers also set up things like governments, which claim dominion over all the makers and punish all the little takers who try to take from them. The little takers of course weep and wail about why the makers get a special set of rules, but that's where they get it wrong, because rather than being angry at the makers, the little takers should be modeling themselves after the supreme takers.

In modernity, the set of rules that the supreme takers put in place hundreds of years ago to protect the makers included things like intellectual property. However those rules are just that, arbitrary rules, and they don't cover up the underlying reality of what they sought to accomplish, which is privilege. If those rules don't work anymore, then the system will simply do something else to achieve its goals, which include elevating the universe to a higher state of existence and creating a better life for everyone.

I see what you're saying now. Your brief analysis has a lot in common with analyses of class conflict and progress that are common in Marxism, though with some stark differences from many as well (e.g., pessimism about the likelihood of self-conscious class activity for makers, no indication of the possibility or goal of a "makers' state" or classless society, maybe a more whiggish or teleological notion of dialectical progress than is fashionable in contemporary Marxism).

Not exactly how I see things, but insightful and concisely put. Thanks for taking the time to write it out!

I don't have a horse in any race, so I aim to be descriptive rather than prescriptive in my analysis, and I make an effort to choose neutral language that will resonate with people from many backgrounds and beliefs. I'm glad you felt my analysis shared common themes with Marxism. I've studied them and know a lot about them. I also hope capitalists would find things to feel inspired about in my words too.

Stop doing drugs.

> If it is reasonable that someone needs to preserve something because it has been abandoned, then the thing should automatically be in the public domain.

Yeah, you go ahead and get that through every Western government. We'll fix the rest.

Civil disobedience is a good start.

Except "once it has been abandoned" is often too late because the source code/artwork/whatever has been lost by then. We need to make sure that things can be and will be archived before that.

> There is no reason laws should have power over anything in perpetuity.

Laws are simply rules chosen and enforced by a given society. Having power over things is what they do. (Also, "in perpetuity" seems untrue, as all copyright expires eventually.)

You clearly disagree with the laws (and I'm inclined to support you there), but what is special about preservation that it should automatically override the will of society? Nearly all the combined work of humanity has been "lost to time," and society seems pretty okay with that.

You're focusing on the wrong part.

That argument is almost entirely about the length of copyright, and you're dismissing that with a quick "eventually". It's not about trying to "override" the intent of copyright.

Also copyright has a clear purpose, and the purpose is to promote culture and science, not to help things get lost. When works that people care about get lost, that's a flaw not a feature.

> but what is special about preservation

Because it's the only thing that will be left of us in 100, 500, 1000, 10000 years. Whatever we care to preserve today will be what will be left to our descendants. It always matters more than the profits of some company today that won't be around in 10, 20, 100 years. And before you try to argue that not everything is valuable, that's fucking not up to you to decide for our descendants.

> Nearly all the combined work of humanity has been "lost to time," and society seems pretty okay with that.

Works that were lost through things like war, conflict, migration, etc. Not through conscious choice. Copyright is a deliberate decision to prevent the collective preservation of our modern culture in favour of enriching corporations and the handful of people who own them. But that doesn't make it moral or right. And "society being okay with it" doesn't make it okay either.

> Nearly all the combined work of humanity has been "lost to time," and society seems pretty okay with that.

Pre-digital age, preserving the combined work of humanity was actually quite difficult. The cost to preserve everything outside of "obviously important" artifacts would've been preventative (or even impossible) for society as a whole.

I believe many (if not most) folks native to the digital age believe that digital artifacts should be preserved indefinitely by default - as the cost in doing so is comparatively trivial - and laws in democratic nations will catch up to that.

Hey I agree 100%. We live in a time and place where we could put about 10-Refridgerators-worth of computer and storage into the basement of every library in the world, and fill those drives with every book, painting, movie, song, etc... EVRYTHING all in one place, replicated around the world a million times over..

We could do this. The technology exists. But we, as humans, as a society and as a race of beings, have collectively decided that we will not do this: It doesn't make anyone any money.

For the first time in history, we could store all of human knowledge in a safe replicable way, world wide, for everyone. But we specifically choose not to do this.

Are you willingly ignoring the Internet Archive which is exactly doing that, and is not a for-profit operation?

We need more of those, agreed, but it makes no sense saying "no one is doing that."

No, I am not ignoring them. I know Archive very well. They do not preserve copyrighted content deliberately, it just gets uploaded, and when no one comes and complains it stays up. They remove things ALL the time. All of the Atari 2600 games from Atari itself, for example. Atari's current owners showed up and asked Jason to take those down, and he did. And he thanked them for the privilege and said they were very nice.

I ADORE Archive. But guess what, they're being sued into the ground over doing EXACTLY what we all want them to do: preserving things. If anything, this absolutely 100% proves my point: we have 1 example of a modern Library of Alexandria, and it is in danger because someone is upset they didn't get paid. This is even more than choosing as a society not to save information and our culture. This is being outright HOSTILE towards the idea.

Just because the whole is more or less abandoned (although I still use winamp, currently running a build from Dec 21, 2022), doesn't mean the licensed parts are.

If the rights holders of the licensed bits haven't abandoned them, then it's not really fair to distribute them without their consent.

This. I cannot believe people are telling me to just open everything. It's nuts. Imagine if someone found your personal code and just decided to open it without your permission or knowledge!

My personal code isn't licensed, so there is nothing that stops you from doing that if you get your hands on my hard drive. What has licensing got to do with it?

Also, we're not talking about personal code either, but something that is arguably a product humanity, or a part thereof, would want to preserve for posterity.

Lastly, no one is telling you to open anything. I am saying that if someone decides something you have created need to be preserved, they should go ahead. You can protest, you can sue, the point is it shouldn't stop anyone from trying. Which doesn't apply to this case, as the owner of Winamp actually wanted to make it open source.

OK, but again, people are telling me to take code I do not own the rights to, and to release it under an open source license. That's 100% illegal. This is the equivalent of me taking a Stephen King novel and pasting it into a webpage and attaching a Creative Commons license. That does NOT make the Stephen King novel open source. It just gets me in trouble and sued.

And the license matters. We're talking about something owned by a company somewhere, legally. Humanity's concerns don't matter in business and legal affairs. As I stated above, I agree that we should be able to save everything. But this has nothing at all to do with what's good for humanity. This is about money and copyright law.

Also, OK, your personal code is not licensed. Great, now I can take it and license it myself, copyright it myself, and then sue you for hosting it in your github account. Hey, I'd be in the wrong, but if I lawyer up I can just win by spending money and waiting you out. This is the world we live in. It's not good, but it's reality.

> OK, but again, people are telling me to take code I do not own the rights to, and to release it under an open source license.

Who is telling you that? Literally no one. In my original comment, the preservationist is NOT the author, as it's the author that is liable to be sued by releasing proprietary material.

In my comment, the preservationist is a third-party that should NOT be concerned with such matters, even if being forbidden by copyright law. Imagine the Internet Archive, which already operate this way, and I applaud, because the service they offer is better than if they had to respect all legal nonsense.

No one is telling you to do anything with YOUR code, and code you are legally liable for. No one is putting a pistol to your head, so I don't get why you are being so defensive to my admittedly unpopular opinion. Do whatever you want.

> Humanity's concerns don't matter in business and legal affairs.

Then it's only fair for humans to not concern themselves with business and legal affairs.

> My personal code isn't licensed, so there is nothing that stops you from doing that if you get your hands on my hard drive

This is not true. You can't redistribute someone else's IP without a license from the owner.

In which country? What if the owner has passed?

Efen if the owner has passed, you can't still legally copy around The Twilight Zone from the 50's in the US.

In my country it's legal to do so -if there's no profit- on media, but not for propietary software with sharing restrictions.

preservationism allows you to bypass "legal nonsense"? That's some entitlement you have. So basically, laws don't matter to you. People's life work don't matter? It's ok for you to take what somebody created in the name of preservation. I bet you wouldn't be saying this if you created and released something that you rely on as your income.

Entitlement is thinking everyone in the world should have their speech restricted because the business model you want relies on a legal fiction.

I have the same problem..

I have been trying to preserve a game engine which has had an important following. But there has just been so many hands in the code, there is a lot of trepidation of the risk it could open the companies up too. Not sure how to progress from here.

Email me at alex@themade.org and we can chat about options and methods. I've done this a bunch and we can usually figure out a way to meet the needs and keep risk at bay, but we will need to talk to the original rights holders, even if the thing was sold off 5 times to new companies. Usually, when I cold call the head of legal about this type of thing, they have absolutely no idea what IP I am talking about, even when their company owns it 100%, and this usually helps a lot to get them to open up. "We own what? Oh, and a museum wants to work with us? Cool!"

shares some insights:

https://arstechnica.com/civis/threads/winamp-really-whips-op...

A little glimpse into what a lot of proprietary code bases look like - or at least did a couple decades ago.

I don't really understand why people complained.

The source is open, if don't want to contribute, don't. Just because something doesn't fit a specific definition it doesn't mean it's not worth of existence.

The source wasn't open though, it was available, and it was provided in a sense that fully showcased that they did not understand what they were doing. Everything from licenses that were fully unenforceable and non-compliant with Github's license agreement to illegally distributing proprietary code to fundamentally misunderstanding how to use git.

It's one thing to provide a source available codebase. That's a choice, and it's fine for various definitions of fine. What they did was legally put themselves in hot water with the inclusion of proprietary dependencies, misrepresent what their intentions were, and likely irrevocably damage their reputation to a small, but vocal minority, who likely have a sizeable overlap with folks that know what Winamp is/was.

It's okay if none of that matters to you, or if it doesn't resonate with you, but the things that were done were comically awful in terms of sharing a codebase.

Describing this as "comically awful" seems strange. In terms of building a good open source project, they did a bad job. However they did a good job making the source available. Also given all the dependencies they may have (whether intentionally or not) followed the best path to make sure that the source would be useful. They ended up looking bad and exposing themselves to legal trouble, but I'm not sure this was awful, and they might even have known exactly what they were doing.

Do people really not understand how bad this could be from a legal perspective. Licenses are a contract and they broke several contracts.

>They ended up looking bad and exposing themselves to legal trouble, but I'm not sure this was awful

For a company, I can't think of anything less awful than purposefully choosing to expose oneself to legal trouble. I'd say that qualifies as "comically awful".

>they might even have known exactly what they were doing.

In what way? Are they going bankrupt (so nothing to sue for) and just want to send out readable source on the way out, without enough care to strip out copyright and list dependencies? That's certainly a hail Mary, but I think that move does more damage to the community than goodwill.

It doesn't meet your definition of the word open.

Of course they didn't know what they were doing. It was written by a 19-year-old in the mid 90s. The code is messy with poor licensing and some build tools were included in the repository and they wrote a dumb license for it? Who cares, they shipped a product that 10s of millions of people used and loved and wanted to share that code up to the world and instead of embracing the best of what they were trying to do while helping them to make things better, the community piled on them until they said it was so not worth it that just pulled the whole thing.

Bravo and job well done.

> It doesn't meet your definition of the word open.

That's a disingenuous argument. It doesn't meet the OSI's definition of open.

> the community piled on them until they said it was so not worth it that just pulled the whole thing.

Yes, but let's be honest: If it wasn't the community, it would have been DMCA takedown requests from the companies whose software was published in the repo. At best, the community hastened the end of the repo by a few weeks.

Assuming they know, care and want to spend resources writing a DMCA request.

You have to issue a DMCA, because if you don't defend your own IP then courts will assume you don't care about your IP.

That's more trademark. You can choose to let anyone use your ip for a fee or not.

OK why do I care about how the OSI defines a word which predates the existence of the OSI by over 1000 years?

Not all definitions are created equal (you seemed to imply that yourself when you said "It doesn't meet your definition of the word open") and the OSI definition is widely considered the de facto standard. Of course no definition is perfect, so if you have specific issues with the OSI definition of open source, go ahead and explain them and your suggested alternative. Otherwise you are making an argument that's impossible to engage with because it's amorphous by design.

Because if you disregard it you will constantly be getting in online arguments with license nerds

The term open-source was coined with an express purpose closely aligned with the definition maintained by the OSI. The OSI also traces its lineage to the coinage of the term; all of the coiners endorse the OSD.

Anyone can read about this here: https://opensource.org/history

But it's well-documented elsewhere, too.

The term 'open-source' is political, as much as it aimed to 'depoliticize' free software. Its definition is and always has been normative rather than merely descriptive. The term and concept exist to serve a movement, and anyone who is invested in that movement's goals is likely to be invested in promoting a historically informed understanding of both.

As for why you, specifically should care about the concept, I think I don't have the patience to make the case right now. But if you're genuinely interested in that question, I'd be happy to provide links to resources if you let me know what sorts of media you enjoy/have energy for.

I care for the same reason I don't like deliberately confusing product packaging.

>Who cares

Other license holders who would at best DMCA Github and take it down anyway. And at worst sue WinAnp for infringement? This is really bad for them. But if you only care about getting to use a decent product, I guess you don't have to care.

This stuff makes FOSS look bad tho. And would only discourage others from trying to make their source available. So I and others care when thinking of the forest instead of the beautiful tree.

The original code may have been written by a 19 year old in 1997, but that license was written this year. Winamp has changed owners several times since then. The original author hasn't worked on it a decade at least.

The "they" that made that license is not the "they" that originally wrote it.

The most recent "they" is a European corporation. "They" are the ones trying to use open source as free labor. This isn't the case of "some dumb kid who didn't understand licensing", this is the case of a large international corporation trying to exploit the public for free labor. That's it.

The "they" who originally wrote Winamp, Justin Frankel among others, understands licensing well enough to know when to use GPL and when to keep it closed as he has projects in both areas.

Of course a lot of us have a soft spot for Winamp. It was a formative part of internet culture in the late 90s and early 00s. That and Napster was kind of the first step to things like iTunes and Spotify. But let's be honest here. What the Llama Group did was hilariously inept in the best case and ineptly exploitative in the worst.

Agreed. The "purists" are dickwads.

> Bravo and job well done

Bravo indeed, it's important these things get done so that people can be better educated on software licenses and open source. If we want to discourage stealing, we have to tell people stealing is bad.

We do absolutely nobody any favors by carving out exceptions for whatever darling piece of software we love.

Well, I guess Winamp cares the most that they are breaking the law, because it's a risk for them. They just didn't realize but now that the community notified them about it, they wisely removed their public billboard showing they're breaking the law.

> non-compliant with Github's license agreement

Oh no! I did notice all the hallmonitors calling for teacher.

I absolutely support dumping proprietary code on any platform and I'm glad I got a copy the day it was uploaded which lets me verify any fork claiming to be from it.

So basically you're glad someone broke their contract so you could hoard more code on your local end?

information wants to be free or so I'm told/was shouted at for a decade.

Reality is often disappointing.

If we break the contracts we just end up with less free information. I want to protect the long term.

Yes. It's not my contract. The worst you might consider me doing is copyright infringement.

FTA:

> "Winamp Collaborative License (WCL) Version 1.0.1," you may not "distribute modified versions of the software" in source or binary, and "only the maintainers of the official repository are allowed to distribute the software and its modifications." Anyone may contribute, in other words, but only to Winamp's benefit.

They were basically grifters. It wasn't just a dump for preservation sake (which would be fine as a historical artifact), they wanted to benefit. Parasitic. What was the community benefitting? They could volunteer for free to benefit a for-profit company when there are already open-source clones that do the same thing? (XMMS and it's various descendents for starters).

> What was the community benefitting?

You got to look at the code. Because it was open.

It's the most literal definition of "open source". You're complaining because you can't also do whatever you want with it. So now we're back to the code being closed again. Better now?

There’s overlap between the retrocomputing-Winamp audience and the litigate-the-opensourceyness-of-licenses audience. The better question is, does there exist anything with an audience where the aesthetic, subjective part of its experience doesn’t matter?

I believe some people understimate how much huge number of companies dont care about OSS licenses and do what they want internally. Winamp was simply unfortunate to unveil it.

Plenty of people have copies of the source and the release was just a novelty really. There's no point in anyone actually forking, building and releasing new versions of Winamp as it has been surpassed by other "real" OSS players eons ago. Let's face it, the release was mostly for Internet historians.

Given the license, I suppose so. It'd only be for a tinkerer who loved WinAnp but wanted to fix some nitpick in the player. Can't do much more than that.

The bad faith interpretation is that this was an attempt to make use of previous goodwill to get some free labor to at the very least fix some bugs for them, or at most add in requested features to try to get it back on the map.

It's a shame the GitHub repository got attacked by the kind of sexually frustrated perpetually-teenage crowd you normally see on 4chan.

On the other hand, Radionomy's clear incompetence over the years sours me. Having the IP for all those years and laying it to waste, culminating in a half-assed attempt to open source it. It pains me to say as their intentions may be good at least in part, but one has to let Darwin get his way too.

People are talking about the issues opened on GitHub as 'trolling' but honestly the license Winamp chose is itself an insult. From the license text via the Internet Archive:

> The Winamp Collaborative License is a free, copyleft license

also from that license text:

> 5. Restrictions

> No Distribution of Modified Versions: You may not distribute modified versions of the software, whether in source or binary form.

Which means that the Winamp Collaborative License is neither free nor copyleft.

What copyleft actually is:

> Copyleft is a general method for making a program (or other work) free (in the sense of freedom, not “zero price”), and requiring all modified and extended versions of the program to be free as well.

https://www.gnu.org/licenses/copyleft.en.html

Releasing proprietary software is whatever. 'Shared source' and similar dilutions are one level of bullshit. Abusing and diluting the language of the free software movement is a step beyond that.

This kind of 'open-source' is actively harmful to an exceptional degree and absolutely deserves to drown in ridicule. A lot of the mocking issues were unfocused or low-effort, but I can't really complain about their function or intent.

"Proprietary packages from Intel and Microsoft were also seemingly included in the release's build tools"

Can anyone speak to this? To me, it's the most interesting bit in this article. Does this mean Winamp developers had access to libraries of Intel/MS that are not publicly available?

It would assume it's about packages that are publicly available but their license forbids redistribution.

From my understanding they received code with contracts that forbid you from distribution.

Could this be the random installers that were present in a folder of the repo? They had some C++ installers and I think a random Intel driver in there...

This is possibly why a number of Fortune 500 and government organizations avoid GPL like the plague. This whole debacle 'won' one battle for GPL licensing but set the war (and their stated ultimate goals) back by a significant amount. This event is a big topic among the devs where I work. It's reignited the 'we should make sure our policies state no use of GPL licensed code or libraries without the exception' (use of binary executables is unavoidable).

In any online population, some people like to build the world (Aces), some like to rule the world (Kings/Queens), some like to watch the world burn (Jokers), and some spend all their time fire-fighting (Jacks). Corollary: There will always be jokers.

> This is possibly why a number of Fortune 500 and government organizations avoid GPL like the plague.

This being, in turn, a fantastic reason to use the GPL for your code.

I thought one of the goals for the FOSS movement was to increase adoption of FOSS software by corporations. How is corporations avoiding GPL code a reason to use GPL when creating new software?

The FOSS movement is not a monolith. There are many individuals and organisations pursuing many different goals, many of which are at odds with or even antithetical to the goals pursued by Fortune 500 companies.

The kind of company that won't touch the GPL with a ten-foot pole is not the kind of company that's looking to be a good participant in the FOSS space. The purpose or merit of appeasing them by switching to a non-copyleft license like MIT is not at all clear to me.

Some of the most powerful people in the world are not entitled to the free labour of under-employed hackers building cool things in their spare time without any expectation of reciprocating, which is the only significant thing that the GPL mandates which MIT does not.

"We'd use this, were it not for the GPL" = "we'd use this, were it not for the obligation to give our improvements back", which is a massive red flag. Fear of the GPL boils down to the simple fact that these entities don't care about FOSS, they just want to build their proprietary castles on top of public beaches.

I was afraid something like this would happen. Glad I downloaded the enitre repo soon after it was opened.

Any chance you could mirror it...?

When I try to search for Winamp on Github (without a login), I am blocked:

    Whoa there!

    You have exceeded a secondary rate limit.

    Please wait a few minutes before you try again;
    in some cases this may take up to an hour.

Regular github browsing is ok, searches result in the above. For 4 hours now (without other any activity). Github is making it personal.

Tech and gaming communities are the most toxic ones ever

Plutono just did too. I've been trying to find any information on the topic, and haven't found anything.

They should have asked help from the community to clean it and maintain it properly.

Dang... The conversations must've been really entertaining.

Once on the internet, always on the internet.

Anyone have a mirror of it?

See this one:

https://news.ycombinator.com/item?id=41861376

The trolling was ridiculous. I don't blame them.

It was pretty clear that with "fork" they meant "don't create a WinAmp-ng fork" and not a "fork" in the "send a patch" GitHub sense. It's fine to point out "hey, I think your custom written license may need a bit of work!", but the amount of vitriol and hate over it (including on HN) was just ridiculous.

It was one of those moments I was embarrassed to be posting here.

And yes, they could have done better, sure. But instead of bringing in someone in the community you just chased them away. Well done everyone. Good job. Excellent result. A story to tell the grandchildren.

exactly.

The forking was bizarre and I agree with your take on it ("forking" with no other changes is not "distribution" except in the most obtuse way). But the licensing issues with what 3rd party software they threw in there was a pretty serious issue. It was probably inevitable they'd take it down and redo it even without the drama.

Agreed it probably was inevitable, but I would be surprised if the "redo" part even happens now. Why would it? They spent their time/money giving us a gift, and we mainly just mocked them because the gift had imperfections. I wouldn't blame them for adopting a "go f*k yourself" attitude.

If it was inevitable that it was going to get taken down then it was never a gift in the first place.

Presumably it (would have) been re-uploaded after a scrub.

It will depend if they can filter out the trolls fortje feedback of well meaning and worried FOSS contributors. That filtering is sadly an important part of navigating the modern social media.

To be honest I didn't see the license issues until this thread, because I had already checked out of the discussion by the time that was brought up.

And it would have been fine to say "hey, I think there may be a problem here, let's work together to see if we can solve it" wrt. to either their custom license or the GPL. That is not what happened. The sad thing is there would be many knowledgable patient people who would be willing to work with the WinAmp people on resolving all of this free-of-charge, but who is going to notice them in a sea of assholes?

I'll also argue it's not "serious", at least in the sense of "needs to be fixed ASAP". It's been like this for how long? 20 years? 25 years? It's just that no one noticed before. And it's basically a "dead" legacy project. Don't really need to rush to correct mistakes of the past here IMHO.

You think they should've just left the license-violating repo up for others to possibly also unknowingly violate?

Yeah, why not ? Violating from some people (closed source proponents) is fine. /s

That is clearly not what I said.

My thoughts exactly. It was shocking and appalling to me how people reacted to this effort. Instead of praising them for taking such a big step, the airwaves were saturated with people magnifying every little imperfection and shitting all over them for it.

If anyone is thinking about open sourcing (and/or making source available) their previously closed app, they had better be paying attention to this. The clear message I saw is that open sourcing is not worth it.

And that sucks and is the exact opposite of how it should be. Open sourcing is an amazing gift you can give to humanity, and instead of looking the gift horse in the mouth and bitching about some imperfections, we should have been praising them and thanking them for their generosity, and sending PRs to help fix issues.

The mess resulting from the Winamp open sourcing/source availabling is more on us (the community) than them, IMHO. If we had acted like rational adults instead of emotionally charged children dehumanizing strangers on the internet and shitting all over them, they would have fixed the issues and we'd be in a better place. Instead now, we have nothing. This is why we can't have nice things.

There's this emerging notion of "Fair Source" that attempts to meet halfway between open participation and business interests. I think as far as defending against copycat risk, that's somewhat reasonable.

Many in the OSS community have made it clear that there's a distinction between "yes do whatever you want with it, including running a local instance and/or charging people for it while using the original name" and "we're transparent but want to reserve some intellectual property rights."

We'll see if most consumers of said software agree with the vocal proponents of OSS purity. I think the story of BUSL and similar licenses has yet to fully play out.

> the vocal proponents of OSS purity

Hey, that's me! :-)

(the following is not targeted at you, but at the "Fair Source" idea. You are just the messenger here presenting the idea, I wouldn't shoot you. Although I do respectfully take issue with some phrasing of yours, which I take as an occasion to explain my rebuttal of the Fair Source idea:)

> There's this emerging notion of "Fair Source" that attempts to meet halfway between open participation and business interests

Open source is not necessarily open participation. See for instance SQLite: open source, but not open participation.

Open source is also not at odds with business interests, given the right business model. See also SQLite, and the many successful commercial open source projects.

Open participation and business interests can also go hand in hand, but my comment is already too long to develop on this and I want to focus on the free software aspect.

I reject this idea that source available but not open source being fair and being some "middle ground" between proprietary and FLOSS. User empowerment and freedom is not only 50% lost in the process, it is almost totally lost. There are few things we can do with some code we can't use anyway. There's nothing fair to the user about proprietary software, and the source availability of the software is only barely relevant to this. There's no middle ground: either you have the fundamental rights allowing you to control your computing, or you don't have them.

I think seeing those things as fair / middle grounds is a dangerous idea. The idea that open source prevents doing business and open source needing some taming down for businesses to succeed is also dangerous.

There's a reason to be adamant with the "purity" of licenses being free software without compromise. It's because if you lose even one of the fundamental rights guaranteed by the free software definition, you lose control of your computing.

I guess I probably sound like some fanatic.

To be clear, I was not part of the people reacting on the Winamp repository, and I think things need to be discussed respectfully.

I’m not too familiar with this situation, but I think one thing that would help Open Source in general is a way to signal what level of user the thing is intended to target.

For instance, is this just something that’s being dumped out on the internet in case someone else finds it useful?

Is it part of your portfolio and intended to showcase your technical skill, but not necessarily be polished from a UX perspective?

Or is it intended to be useful for end users?

Maybe it would be good to have a visually distinct and consistent badge or checklist available for open source projects to communicate the high-level goals so that people’s expectations are set correctly and they know what kind of feedback is inappropriate.

Every project is going to nominally be as-is for obvious liability reasons.

- UX Tier 10 for completely tech-illiterate users

- UX Tier 9 for infrequent mainstream users (do not need to watch a tutorial)

- UX Tier 8 for frequent mainstream users (have watched tutorials)

- UX Tier 7 for power users (need to read the manual)

- UX Tier 6 for sysadmin users (responsible for keeping it running for above users)

- UX Tier 5 for domain specialist users (know the theory behind it)

- UX Tier 4 for developers (read the API reference)

- UX Tier 3 for domain specialist developers (API reference and know the theory)

- UX Tier 2 for project ecosystem developers (know conventions and idiomatic patterns)

- UX Tier 1 for the project team itself (know where the skeletons are buried)

- UX Tier 0 for no further development anticipated

Here's some backstory to what happened from a former Llama Group (Winamp owners) employee who suggested the open source release. He was envisioning something similar to Doom's GPL release, but management couldn't be convinced that the code had nothing more than historical value (likely explaining the dumb license) and everyone who had worked on the legacy Winamp codebase got laid off before the release was announced (likely explaining why there was so much proprietary code in the repo, anyone who knew it was there no longer worked for the company). Honestly the whole thing seems like a desperate PR move by a dying company, it's a shame that the license prevents the community from taking over the project after Llama Group goes under. https://arstechnica.com/civis/threads/winamp-really-whips-op...

They should have open sourced from the start, then such a drama would never have happened. But if you start propietary, become very popular and then open-source, you really have to be careful with what you open-source. It's just how copyright law works. And we can't just ignore the copyright law in just this one case because it's Winamp, unfortunately.

> this effort

revealing Winamp was breaking GPL and several commercial licenses.

I saw a guy on youtube complaining about it. He seemed to talk about FLOSS a lot and focus on the strict definition of "open source."

I checked his github profile and he barely published anything.

So here we have a company that made all of the code of a complete application source available being dunked by a guy who barely published any source code at all.

Really put things in perspective for me.

The company broke a copyleft license though.

And if they didn't publish the code nobody would ever know about it, so what do you think the other companies will do?

Not breaking laws, because it can be eventually revealed one way or another? I only half joking.

Not joking: maybe we need tools to audit / disassemble binaries and match their symbols against known GPL libraries?

Would help a lot, I think.

> I checked his github profile

You do realize that GitHub is not the only place people can share code and that even on github not all contributions will be visible on your profile? Many notable open source developers don't even have a GitHub profile at all or just a dummy one to prevent others from claiming their commits because GitHub allows that without verifying email ownership.

There's a lot of emotional weight behind every PR I do on Github. They're generally the result of dozens of hours of work, discussion with project developers, etc. After all that, it could still be rejected, or need to be reworked, and discussion tone might not carry well over text, etc.

When I see Twitter-style drama on Github, it makes me sick to my stomach thinking that one day I could be the target of an impromptu dogpile.

I occasionally submit PRs to open source projects on github. One time a reviewer asked me to completely rework the code for no functional difference but to just do it the way he would have done it. I just said "it fixes a bug, take it or leave it." and left it at that. It saw it was merged in eventually but couldn't really care less. I wouldn't generate too much emotional attachment to a code segment because heartbreak at some point is inevitable.

There are some people you cannot help. They subscribe strongly to the Copenhagen Interpretation of Ethics. A few classic examples are:

- YC attempting to choose one startup to fund based on HN votes

- Winamp trying to open-source their code

- Jordan Henderson supporting the LGBTQ community

- Ellen Degeneres's sponsors offering to donate to a charity per question answered by her guests

- PETA offering to donate money for each person who chooses veganism

- Numerous open-source developers who give their things for free

It's important to know who your audience is. If they require unwavering purity, it's often better for your own sake to not engage with them. For my part, I stay clear of all these groups in a charitable sense. Everyone pays. The relationship is obvious. They'll go after the people who give them stuff for free. But for the ones who charge them it's just a transaction. That is good.

I don't agree with this take. First, licenses are what court cases and a system of laws are built on. You can't exactly fork a repo with a bad license and hope for the best. Second, this article is downplaying the fact that the repo included a lot of libraries whose licenses they were violating by including it in their repo, and there was no easy way to make the code work without those libraries. The poor license they wrote was just one of a myriad of issues. I think The Register's article is more accurately worded in this regard[0].

[0] = https://www.theregister.com/2024/10/16/opensourcing_of_winam...

> But instead of bringing in someone in the community you just chased them away.

As i remember, they were caught violating the GPL.

I'm sorry, i don't think that law applies only to some unfortunate people.

Good job, team. Companies are sure to open source their legacy proprietary applications now after that warm reception.

They didn't open source anything though. They shared some code under some restrictive license.

The "chilling" effect is still the same.

I hope companies will also recognize that by actually open sourcing their stuff and be more careful, things will go better.

Of course the childish comments that seem to have been posted on github were probably not great, I think people should be respectful, so maybe the additional lesson here is that github, by trying hard to become a social network and not focusing on being a code host and issue tracker, succeeded in being a social network, with the whole package, attracting this kind of shitty behavior, and that's one more reason to avoid it now. You wouldn't upload your code on a social network, would you?

If you don't want cooperation or forks, a zip anywhere will do.

Right, and what we're "chilling" is using software in a way not consistent with its license.

That's good, IMO. Don't steal IP and you don't have to worry about getting caught for stealing IP. FYI: simply hiding the code doesn't fix the issue - disgruntled employees and whistleblowers do exist.

Given the wide variety of views expressed in this HN discussion, it's clear there isn't consensus on how this is being interpreted, so I think you're wrong in claiming that there is only one type of behaviour being discouraged.

That said, I'm just as a casual observer lying in bed with the flu, I probably should just shut up until I know more the situation.

In addition, they leaked proprietary code they didn't have rights to publish in the first place.

I’ll just leave this here. https://webamp.org/

Complete with milkdrop and skins.. love it

If someone extracted that so it could run on desktop, especially with support for SoundCloud and other services, I would enjoy using that. Running inside Tauri the resource footprint wouldn't even be that bad.

My holy grail would be Winamp on iPhone: one screen just for the classic player, another for the equalizer, one for the list of tracks, and one for the visualizer.

The article mentions how deeply compressed the files we played were back then, but I'm pretty sure nowadays it's even worse.

Not at all. Any song on youtube uploaded in the last 5-10 years is as good as a 320 kbit mp3. Why would it be with the bandwidth anyone has to today?

Even limiting the scope to MP3 at the same bitrates modern encoders are much better than what we had back in the 90s.

I think the poster is confusing/conflating dynamic range compression with file compression

Obviously you've never listened to SiriusXM.

But seriously, the poster is probably complaining about how most modern music is heavily compressed in dynamic range, so that it sounds better on crappy earbud headphones and smartphone speakers.

Reply on news.ycombinator.com