2 ms·

Unless you're not using it to compete. Which would be most applications providing content directly to users.

• dragonwriter 6y ago
  > Unless you’re not using it to compete. Well, if you thoroughly explore the licensors current business so as to assure yourself that that’s not an issue, and are willing to accept the cost of ongoing monitoring in the future since your rights to continue to pull in future updates are affected by changes to the licensors business interests of which they are not required to provide you any notice (they only have to provide notice for things that they want to lock you out of even if they temporarily abandon a market).” No sane user with anything at stake is going to put any kind of reliance on something with those terms. And that’s just for a piece of software with a single upstring licensor with those terms. I don’t even want to begin to think about what a nightmare would be involved if you wanted to build a system that would rely on more than one piece of software, from different licensors, under this license.
  • cy_hauser 6y ago
    If I were writing an app that provided information as to what plants were native to a user's particular region, for example, I would have absolutely no fear of that license. That said, I can understand if one has a philosophical aversion to the license.