Interesting. So what if the program presents the user a window saying "do you agree to be bound by <company X's EULA> which explicitly forbids third-party use o

Interesting. So what if the program presents the user a window saying "do you agree to be bound by <company X's EULA> which explicitly forbids third-party use of their API and thus agreeing to it will constitute breaking the law?" and pass that as a parameter. Or if you distribute it in source code only with the parameter settable via a configure param and asking the user to build a version that works? Or make a shim library that hooks to the API then distribute your product with a different shim library that passes false in this particular parameter, but leave notes on which bit to flip with a hex editor in the compiled binary to enable the functionality. This obviously gets less and less user-friendly the more we abstract it, but I'm wondering what its legal standing is.