| ▲ | ameliaquining an hour ago | ||||||||||||||||||||||||||||
You can keep airgapped software up to date, but you have to sneakernet all the updates to each machine. This isn't impossible if you operate your own data centers, but it's inconvenient, and also it sounds like they're largely using third-party clouds where you can't really do that. I do think airgapping would be good, since it seems more likely to me that current or near-future frontier models can break out of VMs and hide from traffic monitoring, than that they can establish a conspiracy when they can communicate only in one direction and only via the channel of the experiment output. | |||||||||||||||||||||||||||||
| ▲ | spacebanana7 an hour ago | parent [-] | ||||||||||||||||||||||||||||
But if GPT 7 eventually produces say npm packages when publicly released and knows that GPT 8 will be trained on JS, it can feed information to other agents even with sneakernet updates (even though it’d take months per mb). This might actually be a viable approach for an agent deciding to benchmaxx openAI generally rather than itself, and hiding benchmark solutions inside npm packages. | |||||||||||||||||||||||||||||
| |||||||||||||||||||||||||||||