The problem there isn't copyright. It's whoever is demanding students use the latest version.
> Copyright rarely helps small authors who actually need it.
>
> It usually gets employed by conglomerates that own distribution and are already screwing authors as hard as they think they can get away with.
Do you think these small authors have the resources to try to enforce copyright?
* declarative mode, where your guest config is defined within your host config, or
* imperative mode, where your guest NixOS config is defined in a separate file. You can choose to reuse config between host and guest config files, of course.
It feels like a sleight of hand, either to not spook OpenAI employees (I.e. the audience of this post), or allow some later minor change in contract or interpretation or customer deployment posture to suddenly permit fully autonomous weapons.
> Fully autonomous weapons. The cloud deployment surface covered in our contract would not permit powering fully autonomous weapons, as this would require edge deployment.
Can anyone explain this constraint?
Why do fully autonomous weapons require edge deployment?
Does "fully autonomous" in this context mean "disconnected from the Internet"?
If so, can a drone with Internet connectivity use OpenAI?
Or maybe it's about on-premise requirements: the military doesn't want to depend on OpenAI's DCs for weaponry, and instead wants OpenAI in their own DCs for that?
I think the thesis of Pi is that there isn't much special about agents.
Model + prompt + function calls.
There are many such wrappers, and they differ largely on UI deployment/integration. Harness feels like a decent term, though "coding harness" feels a bit vague.
> Copyright rarely helps small authors who actually need it. > > It usually gets employed by conglomerates that own distribution and are already screwing authors as hard as they think they can get away with.
Do you think these small authors have the resources to try to enforce copyright?