• 🅿🅸🆇🅴🅻@lemmy.world
    link
    fedilink
    English
    arrow-up
    75
    ·
    edit-2
    1 month ago

    At first I was… wow, no shit! Open source Winamp!

    But then I went through the Github issues (because, 6 hours since first commit and already 5 issues open?). As someone else put it, “This has got to be the most embarrassing open-sourcing i’ve seen to date.”. The licensing is a mess, the coverup is a dumpster fire. By tomorrow this is going to be as viral as Twitter’s “open sourcing” of its recommendation algorithm they did last year. Not sure if I should make coffee or popcorn in the morning.

      • rottingleaf@lemmy.world
        link
        fedilink
        English
        arrow-up
        3
        ·
        1 month ago

        The latter hints that it’s an error and not a mistake, and maybe it’ll get fixed, and maybe even with a better license.

        That said, there are a few “winamps” I can install right now (audacious, qmmp, xmms if I bother to compile it and gtk-1.2, bmp if I bother to compile it).

        Something like milkdrop I’d love, but … nah.

        And nah, getting back to MPD with an ed-like “client” (script with mpc) that jumps to the right entry and position by number, by name regex, by “:”-separated time format.

  • Andrew@piefed.social
    link
    fedilink
    English
    arrow-up
    31
    ·
    1 month ago

    Crikey - it was only added a few hours ago and it’s already all kicking off on their GitHub’s Issues page.

  • db2@lemmy.world
    link
    fedilink
    English
    arrow-up
    27
    arrow-down
    1
    ·
    1 month ago

    That license is an absolute clusterfuck. It was embarrassing to even read it.

  • ZILtoid1991@lemmy.world
    link
    fedilink
    English
    arrow-up
    19
    ·
    1 month ago

    If they don’t want the Winamp name and/or logo used in forks, they can just add a branding guideline that tells people to rename any forked product and to not distribute any graphical or audio elements associated with Winamp.

  • barkingspiders@infosec.pub
    link
    fedilink
    English
    arrow-up
    11
    ·
    1 month ago

    Such a neat piece of software, I remember streaming internet radio (somafm) and trying out different skins on my windows xp laptop back in the early 2000’s and just feeling like the cyberpunk future had arrived. Milkdrop was my gateway drug. Fun seeing it make a comeback, I hope it develops a healthy community and we get some good software out of it. Internet drama be damned.

    • tal@lemmy.today
      link
      fedilink
      English
      arrow-up
      15
      arrow-down
      2
      ·
      1 month ago

      I remember streaming internet radio (somafm) and trying out different skins on my windows xp laptop back in the early 2000’s and just feeling like the cyberpunk future had arrived.

      SomaFM is still around.

      It looks like Qmmp can use WinAMP skins.

      Apparently archive.org has a library of WinAMP skins.

      Milkdrop was my gateway drug.

      That was reimplemented as projectM, and there’s apparently a Qmmp plugin.

  • deathmetal27@lemmy.world
    link
    fedilink
    English
    arrow-up
    8
    ·
    1 month ago

    Kind of disappointed that it’s not a permissive license but still glad that it’s at least somewhat available to the community.

  • palordrolap@fedia.io
    link
    fedilink
    arrow-up
    8
    arrow-down
    1
    ·
    1 month ago

    Edit: I’ve just noticed that there’s an active QMMP project. That would be an even better option.

    With that licensing, I think it might be better for anyone wanting to contribute time and effort to be looking to resurrect XMMS or XMMS2* instead. Heck, they even supported Winamp skins.

    * There were apparently two unrelated projects called XMMS2. Take your pick.

      • kingthrillgore@lemmy.ml
        link
        fedilink
        English
        arrow-up
        3
        arrow-down
        1
        ·
        1 month ago

        See, I would argue (and I think the OSI agrees), restrictions on distribution or access would count as not open source due to restraining how it can be accessed, examined, and run; but shared source. And that can fuck right off

  • HighlyRegardedArtist@lemmy.world
    link
    fedilink
    English
    arrow-up
    4
    arrow-down
    2
    ·
    1 month ago

    Frankly, I’m baffled to see such negativity here and in the github comments.

    Sure, winamp could have handled this better and just referred to the release as “source available” instead of “open source”. Then again, calling it “open source” is not that far fetched and is likely only going to annoy those who want to find fault in any case.

    It’s almost like “open source” has become a religion unto itself, with fanatic zealots defining what is and what isn’t acceptable - I kindly ask you to stop that bullshit, we have enough of these already.

    Having source available is infinitely better than not having it, so let’s keep that in mind. Obviously, this doesn’t mean that people cannot give constructive criticism on how to improve the situation, but most of the shit on display here make my eyes roll hard enough to cause strain: https://github.com/WinampDesktop/winamp/issues/6