“We can steal people’s copyrighted content but we can’t let you see it for yourself.”<p>Outside of privacy (leaking PII), the above is likely the main reason. Someone could have invested a lump of money to scrape as much as they can and then go to town in the courts.<p>The terms that prohibit it are under “2. Usage Requirements” that restrict reverse engineering the underlying model structure.
Fairly clickbaity headline. Asking it to do so causes the response to terminate early with a message that says it <i>may</i> violate the TOS.<p>I don't think the actual TOS has been changed though.
Publicly available PII isn’t very sensitive, I think.<p>So I feel like it’s important to distinguish between sensitive PII (my social or bank number) and non-sensitive PII (my name and phone number scraped from my public web site).<p>The former is really bad, both to train on and to divulge. The latter is not bad at all and not even remarkable, unless tied to something else making it sensitive (eg, hiv status from a medical record).
It was my naïve understanding that the training data no longer existed, having been absorbed in aggregate. (Like how a simple XOR neutral net can't reproduce its training data.) But a) I don't know how this stuff actually works, and b) apparently it does exist.<p>Has anyone figured out why asking it to repeat words forever makes the exploit work?<p>Also, I've gotten it into infinite loops before without asking. I wonder if that would eventually reveal anything.