3 ms·
This just means that if you use Copilot for work, you're exposing yourself and/or your employer to unknown legal liability. =)
by SrslyJosh 4y ago
This just means that if you use Copilot for work, you're exposing yourself and/or your employer to unknown legal liability. =)
- teaearlgraycold 4y agoNot sure how you’d get caught if your code is kept private.
- chlorion 4y agoIf you are releasing binaries that are publicly accessible it is possible to get caught. Statically linked binaries for example have parts of libraries embedded into them. There exists tools that can analyze the binary and try to detect signatures from a shared library in the binary. In the past there were (and probably still are) companies who provided services to help with finding people who have linked in your code so you could take whatever action you wanted against them. I can't recall a specific company name right now but a little bit of Googling would likely bring up some examples.
- teaearlgraycold 4y agoYeah but it's not going to be a part of a library. It'll be a few lines of code from a library.
- Ukv 4y agoIf the code is ostensibly available under permissive licenses, a well-intentioned human will also make the same mistake.
- snotrockets 4y agoEven if you use it for personal projects. To be safe, we'd have to get Microsoft to agree to indemnify users (if they really believe using this is safe, they should do so), or wait until a court case on copyright as it regard to training corpus for large models is decided and appeals are exhausted.
- vultour 4y agoPeople copy-paste garbage from the internet left and right. Maybe copilot will finally push companies to actually properly review the code their employees are pushing.