https://en.wikipedia.org/wiki/Goatse_Security#AT&T/iPad_emai...
https://www.praetorianprefect.com/2010/06/114000-ipad-owners...
Calling it illegal is utterly insane. It’s just a different user-agent and they’d prefer people use their official ones. OpenAI literally controls the keys so if they don’t want someone using an alternate mechanism, they can and will just ban the account.
If someone bypasses authentication I understand but if your api is open on the public internet on purpose, you don't get to randomly declare what's private and what isn't.
Whoo whoo, go easy on the straw man, man.
Bank of America used it to make people who simply changed the account number in their URL bar the criminals instead of them, who were completely incompetent at securing access to their customer's accounts. What previously would have been arguably criminal negligence.
It placed intent above competence - but only for those who can afford lawyers.
And here it is again, being abused the same way.
Hot take: It should be repealed completely.
Actually, the law says that the Terms of Service is a legally-binding contract unless you can prove any provision is legally considered unconscionable. However, if that happens, all provisions except that provision still bind. It is illegal to break a legally-binding contract, and you can be sued or taken to arbitration at a minimum in a civil court for "breach of contract." And that's before any Computer Fraud and Abuse Act or Digital Millennium Copyright Act violations.
Yes, corporations don't sue users for "breach of contract" almost... ever. It's expensive, risky, has low compensation for doing so, and is just bad PR. But they legally always can.
No, it doesn’t.
It says they can state the terms of a contract if all the requirements of contract formation have been met, which are more than just the absence of unconscionable terms.
But then of course... CFAA and DMCA. The DMCA in particular, for example, doesn't consider the strength of the lock in the criminality. DVDs can be cracked with 7 lines of Perl since 2001, but it's still a DMCA violation.
These aren’t reverse engineering the OpenAI API, they are reverse engineering the APIs of public services that in turn call the OpenAI API.
I’m not sure under what theory OpenAI would even sue.
> But then of course... CFAA and DMCA. The DMCA in particular, for example, doesn't consider the strength of the lock in the criminality.
The DMCA only applies to technology addressing copyrights, and CFAA seems inapplicable to consuming the backend APIs used by publicly accessible services because that’s just use of authorized access by a different manner, outside of CFAA scope under the Van Buren precedent.
(Somewhat tangential, the "networks as a 3D space you travel around in with locations you visit" analogy does more harm than good. It's not what's happening and it results in muddled thinking.)
[1] https://en.wikipedia.org/wiki/Computer_Fraud_and_Abuse_Act