Releasing WinAmp source goes badly – for its owners, anyway
www.theregister.com
As badly as the later development of the player itself, really
  • gomp@lemmy.ml
    24·
    19 hours ago

    I must say, this whole shitshow has been pretty funny to watch :)

    • taanegl@beehaw.org
      14·
      15 hours ago

      This, and the WordPress mess, are two contenders for this years “wtf are u even doing” award.

      • Supermariofan67@programming.dev
        39·
        12 hours ago

        Winamp published their code as “open source”. Problem is…

        1. It wasn’t open source, it was proprietary but you can see the source code.
        2. Their custom license didn’t even allow forks, which is against GitHub TOS
        3. The codebase apparently contains proprietary code from third parties that they don’t have the right to relicense.
        4. The codebase apparently contains GPL code from third parties that they probably didn’t have the right to make proprietary in the first place
      • TranquilTurbulence@lemmy.zip
        7·
        13 hours ago

        Winamp source code was published on github, but the license said you can’t fork or share the code. Such a license isn’t compatible with github, which is all about forking and sharing.

    • a1studmuffin@aussie.zoneEnglish
      12·
      17 hours ago

      Sometimes the real value of a project isn’t its proposed worth, but the schadenfreude it offers instead. I’ve backed a few failed Kickstarters that I absolutely got my money’s worth on.