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.)
> You must not attempt to extract protected reasoning through unauthorized access, reverse engineering, or circumvention of safeguards.
This is the only mention of reverse engineering on their ToS. It only applies to trying to reverse engineering their models not others.
Moreover, their ToS is all about protecting security and privacy, which is what I was using it for.
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.
Three regions that move as you scroll in x/y: current/next/clean.
The key is that when you scroll a column or a line, that column/line is written in all three regions.
The clean region is used both as a source for filling the dirty places where sprites have been written as well as the next current or next after a wrap.
VGA registers take care of the x, y start output.
a) needing to redraw a full screen when you reach the end of the buffer/region "ring"
or
b) relying on VGA 64k address wrapping (fiddly, doesn't work the same with all cards, doesn't allow you to use a split screen for a stationary lower status bar).
You need two regions for double buffering, giving you more paint time for all those sprites and one more for the wrapping trick. As you move around these three regions swap roles.
...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"
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.
> 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.
Because of such reasons many companies are indeed quite suspicious of using GCP, and for the same reasons prefer to use AWS or Microsoft Azure.