I really don’t understand this angle. In fact, I am fairly positive that the training set for GPT-4 contains many thousands of conversations with AI agents not developed by OpenAI.
Do AI companies need to manually sift through the corpus and scrub webpages that contain competitor LLM output?
(“Yes” is an acceptable answer to this, but then it applies to OpenAI’s currently existing models just as much as to Bard)
OpenAI and Google both scour the web for human-generated content. What Google cares about here is the learnings from OpenAI's proprietary RLHF dataset, for which they had to contract a large sum of human labelers. Finding a roundabout way to extract the value of a direct competitor's purpose-built, costly data feels meaningfully different from scraping the web in general as an input to a transformative use.
OpenAI and Google both scour the web for content, period. That content could be human generated or AI generated or a mix of the two. Neither company is respecting copyright or terms of service of every individual bit of data collected. Neither company cares how much effort was put into creating the data, whether humans were paid to do it, or whatever else. So there really isn't that much difference between the two.
It's like the guy who never brings anything to the potluck, but after everyone finishes eating, he boxes up the leftovers, and starts selling them out of a food cart.
That particular example doesn't seem all that great, as it gives the impression of not letting food go to waste.
Though sure, the guy could just give the food away, but shrug.
Yes, this latest instance with OpenAI outputs is shady, but I think it's in the same spirit as scraping news organizations for content which journalists were paid to write, and then showing portions of it directly in response to queries so people don't go directly to the news organization's pages, and it's in the same spirit as showing answers to query-questions that are excerpts from scraped pages which another organization paid to produce.
There we go again, its, one law for the unwashed plebs and the other for us.
Why do you think that I, after spending my time and effort to write my blog, own my content to a lesser extent that OpenAI does their? Such hypocracy.
What now? Seriously?
I found this. Section D4.
"We need the legal right to do things like host Your Content, publish it, and share it. You grant us and our legal successors the right to store, archive, parse, and display Your Content, and make incidental copies, as necessary to provide the Service, including improving the Service over time. This license includes the right to do things like copy it to our database and make backups; show it to you and other users; parse it into a search index or otherwise analyze it on our servers; share it with other users; and perform it, in case Your Content is something like music or video."
"as necessary to provide the Service" seems critical.
> You retain ownership of and responsibility for Your Content.
and section D4 says:
> This license does not grant GitHub the right to sell Your Content. It also does not grant GitHub the right to otherwise distribute or use Your Content outside of our provision of the Service, except that as part of the right to archive Your Content, GitHub may permit our partners to store and archive Your Content in public repositories in connection with the GitHub Arctic Code Vault and GitHub Archive Program.
There is nothing in the terms that requires the GitHub user to relinquish all licensing rights.
https://docs.github.com/en/site-policy/github-terms/github-t...
Under definitions: The “Service” refers to the applications, software, products, and services provided by GitHub, including any Beta Previews.
The terms make clear that uploading code to GitHub gives GitHub the right to "store, archive, parse, and display Your Content, and make incidental copies, as necessary to provide the Service, including improving the Service over time" while the code is hosted on GitHub.
However, that's not the same thing as relinquishing (giving up) licensing rights to GitHub. The uploader still retains those rights, and there is nothing in the terms that says otherwise.
GitHub would argue that it is, and they'd likely argue that charging for access to copilot is akin to charging for access to private repositories.
Others would say that copilot is somehow separate from the services Github provides, so using their code for CoPilot wouldn't be covered by the ToS.
I'll repeat the definition of service: The “Service” refers to the applications, software, products, and services provided by GitHub, including any Beta Previews.
Fortunately HN commenters are not judges. And I would wager any bet that MS lawyers would not try to argue based on their ToS either, that would be a recipe for loosing any court case.
If you're posting anything you did not create yourself or do not own the rights to, you agree that you are responsible for any Content you post; that you will only submit Content that you have the right to post; and that you will fully comply with any third party licenses relating to Content you post.
I suppose this means if I upload your stuff to GitHub, and you sue GitHub, then GitHub would be able to somehow deflect liability onto me.
> You may convey verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice; keep intact all notices stating that this License and any non-permissive terms added in accord with section 7 apply to the code; keep intact all notices of the absence of any warranty; and give all recipients a copy of this License along with the Program.
https://www.gnu.org/licenses/gpl-3.0.en.html
If GitHub uses the source code in a way that violates the license, there is no provision in the GitHub terms of service that would allow GitHub to deflect legal liability to the GitHub user who uploaded the program. The uploader satisifed the requirements of GPLv3, and GitHub would be the only party in violation.
If you can't actually grant that separate license, you're misrepresenting your ownership and license to that code
> If you upload Content that already comes with a license granting GitHub the permissions we need to run our Service, no additional license is required.
https://docs.github.com/en/site-policy/github-terms/github-t...
and section D4 does not mention any permissions that GPLv3 does not already cover. GitHub automatically recognizes when a repo is GPLv3-licensed, so it cannot claim ignorance of what GPLv3 is.