Live data from Hacker News

Nvidia sued for stealing trade secrets: blunder showed rival company's code

engadget.com

231–240 of 242 posts

Re: Nvidia sued for stealing trade secrets: blunder showed rival company's code

#231
post #158

Earlier quoted context omitted.

Companies of this size have routine code audits that would find copyright infringements of this sort. If the employee literally brought in source code files and not even change the name of the directory like it was highlighted here, it'd have been caught. The audit is also not conducted by the manager, but a third party. There is no possible way this would fly unless the individual intentionally stripped the source o…

Seems hard to catch at an audit. Surely he just used the stolen code as reference and didn't re-use entire files containing "Copyright by Valeo". If he would have been any smarter, he would have kept the stolen files on a private computer and he would have gotten away with it.

The article mentions the directory containing the files was still named as it was in Valeo. If he didn't bother renaming the path, I'm not sure he bothered removing the copyright.

Re: Nvidia sued for stealing trade secrets: blunder showed rival company's code

#232
post #206

Earlier quoted context omitted.

> If you use GitHub, you feed OpenAI with your code as training data already, with GitLab you do the same for Google. Do you have some evidence that github trained copilot on private repositories? They've been pretty clear about claiming they only used public repos. Also, gitlab is not owned by Google AFAICT but is instead a publicly traded company.

Some people complained that CoPilot outputted their rare code almost verbatim so I have no reason to trust whatever GitHub/Microsoft state.

If you your going to make these kinds of accusations (the kind that if proved true would lead to multi-million dollar lawsuits), you should at least try to provide sources.

Re: Nvidia sued for stealing trade secrets: blunder showed rival company's code

#234
post #176

Earlier quoted context omitted.

Patents really shouldn't be granted when any competent junior engineer could have designed and implemented the feature. This method is doesn't pass the "nonobvious" test.

Batteries used to have cardboard instead of metal shells. Because of this batteries used to leak prolifically. Then an inventor patented the modern metal shelled battery. His competitors all started infringing so he sued. They claimed that the invention was "obvious." The judge ruled that it clearly wasn't obvious, because if it had been they wouldn't have been making the obnoxiously stupid cardboard batteries for so…

I'd still argue that it was obvious. They just didn't do it because cardboard was cheaper.

Re: Nvidia sued for stealing trade secrets: blunder showed rival company's code

#235
post #232

Earlier quoted context omitted.

Some people complained that CoPilot outputted their rare code almost verbatim so I have no reason to trust whatever GitHub/Microsoft state.

If you your going to make these kinds of accusations (the kind that if proved true would lead to multi-million dollar lawsuits), you should at least try to provide sources.

Why don't you just look it up? It was on HN front page some time ago.

Re: Nvidia sued for stealing trade secrets: blunder showed rival company's code

#236
post #232

Earlier quoted context omitted.

Some people complained that CoPilot outputted their rare code almost verbatim so I have no reason to trust whatever GitHub/Microsoft state.

If you your going to make these kinds of accusations (the kind that if proved true would lead to multi-million dollar lawsuits), you should at least try to provide sources.

One example:

https://devclass.com/2022/10/17/github-copilot-under-fire-as...

Also there are multiple lawsuits already as you've probably noticed.

Re: Nvidia sued for stealing trade secrets: blunder showed rival company's code

#237
post #232

Earlier quoted context omitted.

If you your going to make these kinds of accusations (the kind that if proved true would lead to multi-million dollar lawsuits), you should at least try to provide sources.

One example: https://devclass.com/2022/10/17/github-copilot-under-fire-as... Also there are multiple lawsuits already as you've probably noticed.

That is an examples of GitHub allegedly violating the license of public repositories.

The claim that was made was that GitHub trained using private repositories and I have yet to see any evidence.

Re: Nvidia sued for stealing trade secrets: blunder showed rival company's code

#238
post #232

Earlier quoted context omitted.

If you your going to make these kinds of accusations (the kind that if proved true would lead to multi-million dollar lawsuits), you should at least try to provide sources.

Why don't you just look it up? It was on HN front page some time ago.

I tried, all I could find was one other HN comment asking about it. Admittedly I could have tried harder but it really isn't my assertion to defend.

I think there might be some confusion here between private repositories and public repositories with restrictive licenses. There is evidence of the latter but not the former.

Re: Nvidia sued for stealing trade secrets: blunder showed rival company's code

#239
post #237

Earlier quoted context omitted.

One example: https://devclass.com/2022/10/17/github-copilot-under-fire-as... Also there are multiple lawsuits already as you've probably noticed.

That is an examples of GitHub allegedly violating the license of public repositories. The claim that was made was that GitHub trained using private repositories and I have yet to see any evidence.

The caveat you missed in that case was that the person unchecked the checkbox that would allow GitHub to use files in his repository for training.

Re: Nvidia sued for stealing trade secrets: blunder showed rival company's code

#240
post #237

Earlier quoted context omitted.

That is an examples of GitHub allegedly violating the license of public repositories. The claim that was made was that GitHub trained using private repositories and I have yet to see any evidence.

The caveat you missed in that case was that the person unchecked the checkbox that would allow GitHub to use files in his repository for training.

That caveat is irrelevant as it has nothing to do with a private repository. When code is public, especially with a GPL license, it can end up in multiple repositories which may not all de-check the share check.
Post reply on HN