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

Original Article ↗ Hacker News Discussion ↗

Mirrors, Archival, and What Was Lost

  • Several commenters mirrored the repo and shared bundle links; others noted issues and PRs are preserved via the Internet Archive.
  • Many say the real loss isn’t the code (now widely copied) but the “absurdist comedy” of issues, PRs, and commit history as the company tried to scrub proprietary bits.

Licensing Fiasco and “Openwashing” Debate

  • The custom “Winamp Collaborative License” called itself “free, copyleft” yet banned distribution of modified versions and concentrated all distribution rights with Winamp.
  • Many label this “source-available,” not open source, and describe it as “openwashing” and a bid for free community labor, citing the press release inviting global collaboration and assigning all contribution rights to the company.
  • A minority argues authors are free to choose any license, that contributors opt in voluntarily, and that “source-available” has value for learning and review.

GPL/LGPL and Third‑Party Code Violations

  • Thread links to prior analysis that Winamp contained modified LGPL/GPL components (e.g., libdiscid), implying historical non-compliance.
  • Discussion covers how GPL/LGPL actually work: derivative works, linking, static vs dynamic linking, Linux syscall exception, and obligations to release corresponding source or object files.
  • Many note the repo also shipped proprietary Microsoft/Intel binaries and other vendored tools whose redistribution was likely forbidden.

Community Behavior, Trolling, and Moderation

  • The GitHub issues were heavily spammed with memes and hostile comments; some found it hilarious, others “embarrassing” and toxic.
  • Debate over whether this dogpile pushed Winamp to delete the repo versus inevitable DMCA pressure from rights-holders.
  • Broader critique of GitHub’s weak moderation tools, the inevitability of trolls on ungated platforms, and the “well-kept gardens die by pacifism” dynamic.

Preservation vs Copyright Risk

  • Preservationists cite this as a cautionary tale: legacy code is riddled with codecs, fonts, and libraries with murky rights; non-profits cannot afford the legal risk of “just publishing” everything.
  • Others argue preservation should ignore copyright for abandoned/low-value IP and that pirates and archives effectively serve the public, though opponents stress real legal exposure and costs.

Impact on Future Source Releases

  • Some fear a chilling effect: companies will see this fiasco—license nitpicking, trolling, and legal scrutiny—and decide never to open legacy code.
  • Others counter that discouraging half-baked, rights-violating “releases” is good, and that proper, genuinely open-source releases with cleaned trees would fare better.

Value of the Codebase Itself

  • Many see the release as mainly historical/nostalgic; functional value is low given superior modern OSS players and Web-based clones (e.g., Webamp).
  • Still, people appreciated a “peek behind the curtain” at an old, widely used proprietary codebase—even if only briefly and under a flawed license.