spockz
Joined 13 years ago
Joined 13 years ago
I now asked Argon for a pretty elaborate review and it used only 2% so I will be giving it another shot.
Another thing that can be of influence is that for subscriptions, Google uses some proprietary idea of “work done” for the quota instead of simply how many tokens were burned. I can imagine that this heuristic is sometimes quite off.
If one microVM can use the cpu in such a way that the registers can be used to communicate or exfiltrate/spy (the only difference being the directionality of the intent) by another microVM that is a leak on that microVM separation level.
I get that that behaviour shouldn’t just be changed but I would appreciate it if there were another key combination that would allow cycling through all windows of an app.
And probably something to understand what your agents are doing and why. With which reasoning.
Otherwise also stay a damn good IDE. We still need that. My agents are floundering on our bigger codebases and only produce warts.
> 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.
If we care so much about that it actually looks the same after all that time, why is it not a pdf?
I’m so confused that anyone would get hung up enough about this to let it block a migration of this size.
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.)
That you want your content to be readable from everyone doesn’t mean you want the admin interface to be available globally.