Then I applied for daybreak blue and haven’t had any issues since.
It also a matter of phrasing. Say what you want to achieve not how if it is approaching defensive or cyber stuff.
Also state you are working on your own devices and software. (If that is the case of course.)
It's somewhat complex to understand; I didn't understand Claude's textual explanation at first. After asking for a html/js simulator showing things visually it clicked.
No pushback from Claude so far.
...for a niche of customers, from whom the revenue is probably entirely negligible to OpenAI.
Not saying it's right, ethical or anything like that, but it's not "stupid"
> Not saying it's right, ethical or anything like that, but it's not "stupid"
Quite many well-paying customers become very suspicious of whether integrating OpenAI into their workflows if they read about cases where OpenAI banned accounts willfully.
If OpenAI wants to become "infrastructure provider other companies should depend on (and thus pay)", OpenAI must behave like an infrastructure provider as for electricity or internet, i.e. must only ban accounts in exceptionally rare cases that 99.9 % of society will consider to be acceptable.
For corporate accounts they are apt to get a message to the admin account saying suspicious shit is occurring provide more verification.
>OpenAI must behave like an infrastructure provider as for electricity or internet
Oh, you mean like Google? Yea, how's that working out.
If your always-on agent hears to wrong thing, you could lose access to things you depend on. The same reason makes GCP very unattractive.