4 ms·
They're not claiming that it can never spit out code exactly, but that they will take liability for if: - It does - The user didn't turn off the filters that
by circuit10 3y ago
They're not claiming that it can never spit out code exactly, but that they will take liability for if:
- It does
- The user didn't turn off the filters that prevent this
- The user didn't intentionally make it do it
- This use is found to be illegal
There's a difference between code that needs to be kept private from bad actors (from their point of view at least) and code that is public but with restrictions on its use that anyone who gets it should be aware of. This is like saying "if you truly believe that license agreements are legally binding, then publish your user's passwords publically with a license saying no one can use them"
- klyrs 3y ago> This use is found to be illegal This being the real hurdle. With Microsoft money behind the defense, only megacorps can win.
- eru 3y agoMicrosoft has lost legal battles against non-megacorps in the past. I remember some guy representing himself and winning some dispute over shrink wrap licenses and student discounts.
- matheusmoreira 3y agoThat's badass. Where can I read about that court case?
- eru 3y agohttps://en.wikipedia.org/wiki/Microsoft_Corp._v._Zamos https://en.wikipedia.org/wiki/Microsoft_Corp._v._Zamos
- matheusmoreira 3y agoThat's seriously awesome.