• yannic@lemmy.ca
    link
    fedilink
    arrow-up
    4
    ·
    1 hour ago

    There are many examples of this, but one that comes immediately to mind is the evolution of my favourite LDAP-enabled music player, airsonic-advanced

    Subsonic begat libresonic Libresonic begat airsonic as well as a whole bunch of other projects. Airsonic begat airsonic-advanced Airsonic-advanced begat kagemomiji/airsonic-advanced, however the maintainer of the parent codebase, randomnicode, wants to do the right thing and get their code up to snuff with the opensubsonic API (not sure where that fits in to thr history) so kagemomji can take over.

  • Quetzalcutlass@lemmy.world
    link
    fedilink
    English
    arrow-up
    32
    ·
    5 hours ago

    CyanogenMod, which was the base of most custom Android ROMs at one point. After taking venture funding, incompetent business majors crashed and burned the project trying to commercialize it. It was then forked and LineageOS was born.

    • Otter@lemmy.ca
      link
      fedilink
      English
      arrow-up
      3
      ·
      2 hours ago

      I remember hearing about Cyanogen way back when, didn’t realize LineageOS was forked from it

    • Lemminary@lemmy.world
      link
      fedilink
      arrow-up
      11
      arrow-down
      1
      ·
      4 hours ago

      My big question is, why not fork the original first and commercialize that instead. So much forking around the wrong ways! /s

      • Comment105@lemm.ee
        link
        fedilink
        arrow-up
        4
        ·
        2 hours ago

        Because business majors only know how to exploit good things that would be better off without them.

        If the good thing is left to just be better off without them – while they fuck around with a separate thing – then people will never be interested in the business majors’ product.

      • barsquid@lemmy.world
        link
        fedilink
        arrow-up
        7
        ·
        3 hours ago

        MBAs love taking an existing brand and sucking whatever value they can extract. Like chupacabras but for functioning and useful products.

  • Refurbished Refurbisher@lemmy.sdf.org
    link
    fedilink
    arrow-up
    19
    ·
    edit-2
    6 hours ago

    DuckStation recently changed to a source-available license that prohibits distributing modified versions of the software and prohibits commercial use. Before, it was GPLv3.

    Also OpenOffice, Emby, Audacity, Android (AOSP) (soft forked to LineageOS and GrapheneOS, but no hard fork)

      • Brahvim Bhaktvatsal@lemmy.kde.social
        link
        fedilink
        isiZulu
        arrow-up
        1
        ·
        edit-2
        50 seconds ago

        DuckStation recently changed to a source-available license that prohibits distributing modified versions of the software and prohibits commercial use. Before, it was GPLv3.

        DuckStation is an emulator for some Sony PlayStation console. PS2, I think. This software used to be given to users under the GPLv3 license, which grants freedoms such as distribution of the source code of the software (DuckStation) for no extra cost (well, DuckStation also costs no money! …so, you get to eat the cake and know its recipe too, for free!).

        …Now they’ve switched to a license which allows you to see the source code, but does not grant you rights over the source code that GPLv3 did (which is essentially ANYTHING as long as you publicize everything you make with the source code, under the GPLv3 license also - changes to the code, new software that uses any portion of the code, anything you make with it).

        OpenOffice, Emby, Audacity, and Android (the “Android Open-Source Project”) have also done this in the past.

        Knowing this stuff on Free, Libre, and Open-Source (“FLOSS”) platforms like Lemmy is almost necessary given that they’re built on these principles. Please get acquainted with them.

    • Pumpkin Escobar@lemmy.world
      link
      fedilink
      English
      arrow-up
      7
      ·
      7 hours ago

      It has been on my list to figure out how to move to forgejo, need to do it soon before the migration process breaks or gets awful.

      • Opisek@lemmy.world
        link
        fedilink
        arrow-up
        8
        ·
        4 hours ago

        If you’re using docker: change your image name from gitea to forgejo. Repull. Done. Baremetal should be just as simple. Migrations are as easy as leaving all the data in-place and changing the binary at this moment in time.

  • Zangoose@lemmy.world
    link
    fedilink
    arrow-up
    60
    ·
    12 hours ago

    Audacity was the first one I thought of.

    Or MultiMC, PolyMC, the Sodium mod, or the original Minecraft Forge.

    (Minecraft community devs need to stop having drama lmao)

      • Zangoose@lemmy.world
        link
        fedilink
        arrow-up
        6
        ·
        4 hours ago

        The lead developer changed the license to a much less permissive one because of drama surrounding being credited in modpacks. The dev thinks there are forks that exist solely to sidestep crediting the original mod, I’m not up to date enough on Minecraft modding lore to know if this is true or not.

        I’m pretty sure there’s also a fork that branches off of the last GPL commit but I forget what it’s called.

        • Opisek@lemmy.world
          link
          fedilink
          arrow-up
          1
          ·
          4 hours ago

          Doesn’t GPL technically require you to attribute the upstream anyway?

          The work must carry prominent notices stating that you modified it, and giving a relevant date.

          • hendrik@palaver.p3x.de
            link
            fedilink
            English
            arrow-up
            1
            ·
            edit-2
            2 hours ago

            Most open sorce licenses do, not just the GPL. I’m not sure what Minecraft modpackers do. But in the free and open source world, you’ll always find that attribution. Sometimes they have a list who wrote the software and who maintained it for what timespan.

    • Korne127@lemmy.world
      link
      fedilink
      arrow-up
      28
      ·
      11 hours ago

      I love how well the PolyMC -> PrismLauncher transition went. It’s great that the asshole owning it didn’t just spew transphobic hate, but also removed the contribution rights to all other people, leading them to immediately flock to an alternative.

  • azthec@feddit.nl
    link
    fedilink
    arrow-up
    4
    ·
    7 hours ago

    Maybe a bit niche, but if you’re in the Scala ecosystem and seen what happened with Akka -> Apache Pekko. Version one of Pekko was a 1-1 rename of Akka

  • devilish666@lemmy.world
    link
    fedilink
    arrow-up
    4
    ·
    8 hours ago

    I hope someone made STACER (a.k.a Bleachbit on roids) remastered
    The owner of that project already abandoned it, it’s sad STACER already had so…much potential compared to Bleachbit but no one wants to revive it

      • cm0002@lemmy.world
        link
        fedilink
        arrow-up
        9
        ·
        8 hours ago

        Here’s a comment about it I made a few weeks back in the context of why Jellyfin came to be and why I only ever recommend Plex or Jellyfin

        This is going to go back quite a ways, and much of my knowledge is old at this point so some details might be off.

        ~15 years ago Plex as we know it started out as an OSX fork of the 0G Xbox homebrew software XBMC (Later renamed Kodi (For those who don’t know, XBMC was XBox Media Center and would turn the 0g Xbox into the cheapest Home Theater PC you could get at the time, man those were the days lol))

        Plex was only briefly open source and then was quickly closed when they incorporated a year or so after they had something functional. They never made any promises about not charging or being open source or anything, so that’s why I’m generally fine with Plex

        Sometime around 2012ish Emby came along as THE open source alternative to Plex and things were good. MOST of it was supposed to stay open source as was promised. From the beginning they kept build scripts n such closed source, probably should have caught on them, but heh ya know hindsight and all that.

        Then around 2014/5 they took it all closed source, relicensed it and introduced their paywall including locking away already existing features. This is what pissed me and many others off and this is when and why Jellyfin split off promising to be truly fully open source forever. (There was a ton of drama about it at the time, but it looks like Embys Q&A thing a bit back doesn’t even bother to mention it, imagine that lol)

        I don’t have a problem with subscriptions on open source software myself, but the way they went about it…yea. fuck em

    • superkret@feddit.org
      link
      fedilink
      arrow-up
      3
      ·
      edit-2
      2 hours ago

      Any good alternatives that use the same engine, but aren’t just “Firefox after rustling the about:config a bit”?

    • cm0002@lemmy.world
      link
      fedilink
      arrow-up
      25
      arrow-down
      1
      ·
      11 hours ago

      It’s Mozilla that’s slowly enshittifying, Firefox itself is theoretically insulated from the worst decisions they could make, but those safeguards are going to be put to the test real soon I bet.

      • 21Cabbage@lemmynsfw.com
        link
        fedilink
        English
        arrow-up
        1
        arrow-down
        3
        ·
        10 hours ago

        Well to that end chromium is still around and I’m sure there’s deshittified builds of that floating around too but it is going to quickly become harder to find not shitty browsers the way things are going over at Mozilla.

        • cm0002@lemmy.world
          link
          fedilink
          arrow-up
          15
          ·
          10 hours ago

          The big problem is the browser engine at the heart of all browsers, all the FF or Chromium forks very rarely modify the core. When they do, it’s minor stuff. That’s why AFAIK not a single chromium fork is maintaining manifest v2 in defiance of Google.

          If Mozilla goes full tilt enshittification, all the FF forks will suffer a similar fate, they’ll make changes all over, custom interface, cool little features here and there etc; but they’ll never make major changes to the core and that’s assuming they keep the core open source. If they take the core closed source and the forks can no longer get upstream updates for it they’ll wither and die

          A browser engine is kinda like the Linux kernel, it’s large, complex and takes a lot of time and effort to make and keep it usable. I’ve seen estimates that if we needed to start from scratch on the Linux kernel it’d take 2-4 years just to get something decently usable.

          Browser engines are similar, Ladybird for example, is a new open source browser AND engine from scratch that’s been in development for about 2 years, they’re estimating to have something “generally usable” in 2026

          • andyburke@fedia.io
            link
            fedilink
            arrow-up
            1
            ·
            9 hours ago

            Timelines change based on interest.

            Servo is a new browser rendering engine in Rust - seems interesting and gathering steam.

            Don’t be too fatalistic - every time the corpos have come for the internet they have been circumvented. I don’t see it stopping now - especially since people like us are tired of this brand of bullshit.

            • cm0002@lemmy.world
              link
              fedilink
              arrow-up
              3
              ·
              8 hours ago

              I try not to be, but attention does need to be called to it, and I see a lot of handwaving away in regards to Mozilla. People should be demanding more answers from them to at least delay enshittification a little to give more time to the alternatives like Ladybird and Servo to develop and refine for widespread usage

              Which thanks for pointing me towards Servo, I missed that one lol, but I still don’t think it has yet achieved feature parity with Gecko or Chromium