• Blue_Morpho@lemmy.world
    link
    fedilink
    English
    arrow-up
    135
    arrow-down
    3
    ·
    edit-2
    8 months ago

    This has been going on for decades. CDDB, IMDB, Redhat.

    Anything you volunteer for will be monetized and you will get cut off from your own contributions.

    Even here on Lemmy people post Twitter images and Reddit reader apps which only helps those platforms retain mindshare even if they aren’t directly profiting with ads.

    • fidodo@lemmy.world
      link
      fedilink
      English
      arrow-up
      40
      ·
      8 months ago

      Google has a volunteer program to make their AI better. Fucking one of the biggest corporations in the world asking for free labor and apparently people do it?

    • lad@programming.dev
      link
      fedilink
      English
      arrow-up
      32
      arrow-down
      1
      ·
      8 months ago

      This is a bit of “no true Scotsman” fallacy. If something you volunteer for hasn’t been monetized you can always say ‘yet’

      FOSS is something people volunteer for and it mostly doesn’t get monetized and cut off. Sometimes this means that the original is cut off but a fork lives on, so I would rather say that volunteering for a closed product is dangerous in that regard, not volunteering forany product

      • BreakDecks@lemmy.ml
        link
        fedilink
        English
        arrow-up
        11
        ·
        8 months ago

        This is where licensing is important. If you want to contribute your time to something you think is important, make sure that your contributions are licensed to be open and free.

        If a for-profit company violates the license, the contributors can fight back. If there is no license, you’re just giving them free labor that they can exploit however they please.

    • theherk@lemmy.world
      link
      fedilink
      English
      arrow-up
      25
      ·
      8 months ago

      Hashicorp recently commandeered its community built products from thousands of contributors by changing open source projects to an ambiguous if not hostile BSL. Opentofu for any current terraform users out there.

      • Cyber Yuki@lemmy.world
        link
        fedilink
        English
        arrow-up
        15
        arrow-down
        2
        ·
        8 months ago

        Previously named OpenTF, OpenTofu is a fork of Terraform…

        🤭 LOL @ the name change.

      • nickwitha_k (he/him)@lemmy.sdf.org
        link
        fedilink
        English
        arrow-up
        1
        ·
        8 months ago

        Definitely in two minds on Hashicorp’s license change. I understand why they did it, even if I don’t agree. Other for-profit companies were screwing them and the community over by taking, competing, and seldom contributing.

        • theherk@lemmy.world
          link
          fedilink
          English
          arrow-up
          2
          ·
          8 months ago

          I have heard this point of view and truly don’t understand it. There were companies making money with an open source tool. That’s what some companies do, and the license allowed for that. They weren’t taking; they were using a tool, and providing a service upon it. If anybody is taking, it is Hashicorp from their own community that contributed thousands of hours to their business for free.

          And those companies you refer to tried often to push upstream but Hashicorp just refused contribution time after time.

          That said I understand it too. Insofar as capital investment demanded the cornering of a market and miscalculated the likelihood of a well backed fork. As a result I think, they probably sealed their fate even if it takes many years. How many people remember Hudson?

    • Cyber Yuki@lemmy.world
      link
      fedilink
      English
      arrow-up
      19
      arrow-down
      1
      ·
      8 months ago

      Good callout. Even Twitter images shouldn’t be hot linked but copied and pasted for preservation purposes; if a copyright takedown happens, then it happens. But at least we don’t risk having access cut because of a corporate killswitch.

    • afraid_of_zombies@lemmy.world
      link
      fedilink
      English
      arrow-up
      11
      arrow-down
      1
      ·
      8 months ago

      Meh Rehat gets a pass in my mind at least. They give back to the community enough. We are never going to get perfect people or groups. Microsoft is a totally different story.

    • stoly@lemmy.world
      link
      fedilink
      English
      arrow-up
      16
      arrow-down
      6
      ·
      8 months ago

      It never stops shocking me that people think they can trust corporations which are run by upper middle class entitled business bros who never worked an honest day in their lives.

    • skulkingaround@sh.itjust.works
      link
      fedilink
      English
      arrow-up
      8
      ·
      8 months ago

      To be fair every FOSS license will prevent a company from having exclusive rights to use your work. Even if you get a bit lax and include MIT and BSD licenses as FOSS, a company still cannot take your work and stop other people from using it.

      In the case of Duolingo, it’s pretty different because that volunteer labor output is gated in a proprietary walled garden.

      Whereas contributing a patch to chromium for example will never gate that contribution, even if it makes it into chrome and produces millions of dollars of profit for google. You can always and forever freely access and use a version of chromium with your patch as long as there’s still a copy left to access.

      • Blue_Morpho@lemmy.world
        link
        fedilink
        English
        arrow-up
        4
        arrow-down
        1
        ·
        edit-2
        8 months ago

        To be fair every FOSS license will prevent a company from having exclusive rights to use your work

        The trajectory for many Foss projects is to get the hardest part off the ground with mindshare and initial development. Then after all the hard work it becomes successful, the project is closed and all new features are added into the closed fork.

        Technically you still have the original work but within a few years the project is dead except for your personal work because the main fork has a large corporation behind it continuing the development.