Re:GitHub Private Repos Considered Private-Ish
by simonw on Sunday June 04, 2023 @11:16AM
(#36186276)
I genuinely don't see how "The information we learn only comes from aggregated data" relates to training LLMs, which need raw data, not aggregated data, as their input.
Maybe we have different definitions of the term "aggregated"?
This suggests to me that GitHub need to extend that text to explain what they mean by "aggregated".
Re:GitHub Private Repos Considered Private-Ish
by atq2119 on Sunday June 04, 2023 @12:16PM
(#36186809)
The LLM itself is a form of aggregated data.
Re:GitHub Private Repos Considered Private-Ish
by simonw on Sunday June 04, 2023 @12:23PM
(#36186885)
Sure, but the raw training data isn't.
I think GitHub need to clarify this themselves.
Re:GitHub Private Repos Considered Private-Ish
by atq2119 on Sunday June 04, 2023 @12:43PM
(#36187073)
Sure. All aggregated data is ultimately derived from raw, unaggregated data. One can make the argument that training an LLM is "just" an unusually complicated form of aggregation.
Whether that would hold up is another question. But yeah, I agree with the conclusion that they need to clarify this.
Re:GitHub Private Repos Considered Private-Ish
by hedora on Sunday June 04, 2023 @10:05PM
(#36191449)
Training the LLM is a form of “learning”, and putting all the data in an input training set is a form of aggregation.
The clause seems to mean “we can do whatever we want with your data as long as we violate many people’s privacy at scale at the same time”.
Re:GitHub Private Repos Considered Private-Ish
by mtlmtlmtlmtl on Sunday June 04, 2023 @12:43PM
(#36187075)
But then the training can be surreptitiously be called data aggregation. We don't look at the raw data, we aggregate it and then query the aggregation.
Definitely needs clarification, though somehow I suspect this is all by design.
Re:GitHub Private Repos Considered Private-Ish
by waynecochran on Sunday June 04, 2023 @07:52PM
(#36190687)
Enter lawyers.
It seems pretty clear to me that this means they're allowed to use private repos to train copilot, etc.
I wonder if any researchers have tried putting fingerprinted source code into a private repo, and then (after it is retrained) getting copilot to suggest stuff that could only have come from the injected supposedly-private source code.
That would make a nice paper. I hope someone does it.