‹ BackHN Continuity

Thread

Nobody pays for FOSS, we can force them to

196 points · 209 comments · Muhammad523

  1. mentalgear · · focus · HN ↗
    I feel like the main issue with projects switching between a permissive and less permissive license and back is that starting out as fully permissive in the first place was the main error.

    If everybody would just agree to start their open source code as something like source-available or OpenRAIL -requiring companies with more than $5M in annual revenue to pay for the work - we wouldn't be in this situation.

    <a href="https:&#x2F;&#x2F;fair.io&#x2F;" rel="nofollow">https:&#x2F;&#x2F;fair.io&#x2F;

    1. tracerbulletx · · focus · HN ↗
      Yeah its a bait and switch. People want the social credit, early adoption, and community embrace of being open source, but they also want a captive business model.
      1. amelius · · focus · HN ↗
        It&#x27;s not a bait and switch because the old version of the software that was released with the old license can still be used as such. If you call this bait and switch then I suppose this means that you somehow feel entitled to future versions of the software having the same license, forever.
        1. aaasssdddgirl · · focus · HN ↗
          That’s the thing with software, you can automate most future updates, with LLMs and whatnot.

          Also, the initial software probably didn’t have a lot of known cves when it was sold.

    2. rpdillon · · focus · HN ↗
      They won&#x27;t do this, because starting out as non-free doesn&#x27;t get the same traction. Now that I think about it, it&#x27;s basically a form of enshitification: draw people in with one deal, then after they&#x27;re onboard, change it to something less favorable.
      1. amelius · · focus · HN ↗
        Why is it enshittification if you only have to pay when you have &gt;$5M in revenue? Is your world so shit if you cross that threshold?
        1. johnnyanmac · · focus · HN ↗
          I think the issue is more on how you audit such things. Governments struggle (partially by design, but still) to get proper audits on who uses what and how much money they make.

          The theory is great, but I&#x27;m unsure how you execute this.

          1. amelius · · focus · HN ↗
            Well, that&#x27;s even more reason to not complain about it.
          2. _carbyau_ · · focus · HN ↗
            It isn&#x27;t about catching every last &gt;5m business out.

            It is about having a rule that can be enforced when it is obvious to do so.

            1. johnnyanmac · · focus · HN ↗
              Fair enough. I&#x27;m in support of it, but it seems like any company &gt;5m is also going to give a big legal fight if and when they are challenged on such aspects.

              But I&#x27;m all for a good attempt at taking our wealth back either way.

              1. _carbyau_ · · focus · HN ↗
                &gt; any company &gt;5m is also going to give a big legal fight

                I don&#x27;t know about any company doing that. I guess some would do so on principle. But I honestly suspect it&#x27;d be a cost&#x2F;risk based decision.

                Who knows. But there is seemingly no carrot to entice those with money to give some of it to support the project, so a stick it is.

                I like the Blender way of, contribute money = your features requests get some priority. But that only works if the company needs something.

          3. kelnos · · focus · HN ↗
            I think the maintainer is still better off if only 50% of companies that should be paying are actually paying. The alternative is to just get nothing.

            And if the maintainer wants to, they can always try to go after some of the more egregious offenders.

        2. rpdillon · · focus · HN ↗
          I&#x27;m just observing the incentives. There is a reason these licenses have not taken off, especially for nascent projects.
    3. [deleted] · · focus · HN ↗

      [deleted]

Open on Hacker News to reply ↗

Unofficial Hacker News client; not affiliated with Y Combinator.