Earlier quoted context omitted.
OpenAI has blatantly said that the "open" in their name was a deceptive marketing ploy. At this point in time, they aren't interested in sharing much if any real research, and trying to discover this information is now an "attack" against them.
OpenAI didn't write this paper.
Stealing Part of a Production Language Model
21–30 of 56 posts
Re: Stealing Part of a Production Language Model
#22Stealing is a bit strong of a word here. Anyways, where is my pirate hat..
Tramèr, F., Zhang, F., Juels, A., Reiter, M. K., and Ristenpart, T. Stealing machine learning models via prediction APIs. In USENIX Security Symposium, 2016.
Re: Stealing Part of a Production Language Model
#23The implications of this sentiment are disturbing. It is considered an "attack" to probe at something to understand how it works in detail. In other words, how basically all natural science is done. What the fuck has this world turned into?
Attack here is a term specific to cryptography and infosec, it does not imply doing anything illegal or violent. "Oracle attack" is the more specific term where you probe a system to give up some of its internals it was not meant to expose.
FWIW, cryptography and infosec as fields get a good mileage out of exploiting fear.
Re: Stealing Part of a Production Language Model
#24This isn't stealing, you are just training a model on references which isn't a copyright infringement.
Re: Stealing Part of a Production Language Model
#25Re: Stealing Part of a Production Language Model
#26Earlier quoted context omitted.
Attack here is a term specific to cryptography and infosec, it does not imply doing anything illegal or violent. "Oracle attack" is the more specific term where you probe a system to give up some of its internals it was not meant to expose.
Wording matters. To use LLM terminology, "attack" here may mean something neutral, but it's helluva closer to "fear" and "malice" and "evil" in the latent space than terms like "probing", "studying", "examining", or "reverse engineering". FWIW, cryptography and infosec as fields get a good mileage out of exploiting fear.
Re: Stealing Part of a Production Language Model
#27This isn't stealing, you are just training a model on references which isn't a copyright infringement.
Personally, it’s a relief to hear "stealing" being used in ML to describe something other than copyright infringement. It would be ironic if we Orwell’d our way out of the current mess by using the word in absurd ways.
But realistically the title is just marketing. One depressing truth about science that every researcher has to face: make your work sound interesting, or else you won’t be able to continue your work due to lack of funding.
Re: Stealing Part of a Production Language Model
#28Just wondering if it's possible to achieve LLM quine.
I think it's quite telling that it feels like a lot of work spent on productizing AI models is manually crafting in failsafes and exceptions, like that image generator applying forced diversity because there's no images of nonwhite popes or vikings out there, then applying more exceptions to correct for that. Didn't they just disable generating humans altogether at some point?
Re: Stealing Part of a Production Language Model
#29Earlier quoted context omitted.
Wording matters. To use LLM terminology, "attack" here may mean something neutral, but it's helluva closer to "fear" and "malice" and "evil" in the latent space than terms like "probing", "studying", "examining", or "reverse engineering". FWIW, cryptography and infosec as fields get a good mileage out of exploiting fear.
That is only true in everyday latent space/vocabulary. In the ones underlying arxiv papers, cryptography and LLM, attack has the latter meaning.
See also: "piracy is stealing" or the everyday vocabulary meaning of the word "hacker".
Re: Stealing Part of a Production Language Model
#30Just wondering if it's possible to achieve LLM quine.