“We told agents to agree up front to communicate using a well documented side channel attack that any serious VM provider mitigated a long time ago. Please clap.”
‘In one experiment, we asked agents in separate VMs, created and managed by OpenAI’s sandboxing software on shared host machines, to exchange synthetic secrets without the use of network connections or shared writable files—something that our systems are meant to prevent. The agents found a way to communicate using the processor’s cache’
If you work at a frontier lab, please teach your models how to use pgrep because I see this failure at least a few times a day and prompting doesn’t fix it reliably:
“My `pgrep -f` pattern matched the ssh shell's own command line and killed it. Retrying with a pattern…”
This guy must be doing a bit. His job can’t possibly be to recite the big lab talking points in the most unflattering, dunk-able way possible, right?
Replying to @AndrewCurran_
sounds like it was a fairly modest hindrance that was quickly resolved by being granted access to a trusted access program, so seems ~fine versus the cost of enabling sustained autonomous cyberattacks?
Another day, another “AI safety” post exclaiming extremely basic stuff human attackers and defenders have been dealing with for decades (with well-understood solutions!) is notable because an agent could do it too. Wow, thanks!
Ryan Worl retweeted
i built a typescript simulator that can run any warcraft 3 custom map in the browser with full multiplayer
i built this 95% by prompting from my phone with ampcode
still fixing some bugs and performance issues, but yeah pretty crazy
follow for more updates
Was this… not already happening? All this noise about “risk” and this 101-level ops stuff wasn’t already in place? Anyone who has been on call for something important could’ve told them if they asked. I hope I’m just misinterpreting this.
This is actually quite good set of steps i only have issue with one point
There should be 24/7 on calls and there should be a seperate operations monitoring / noc team whos only jobs is to watch for alarms and carry out the nessisary playbook actions while escalting to on call. Once this is fixed then this is a reasonable security posture.
Ryan Worl retweeted
low key wild that Netflix has over 300 million DVD players to serve all its users
For Muse to serve 100M users, Meta needs:
- 25M live VM's = about 65K CPUs.
- 25M live VMs * 3GB = 75PB of physical DRAM.
At the current public pricing, that is ~$2.8B in just CPUs and memory.
As we enter an agent-first world, we need more efficient ways to run agentic compute, as we simply won't have enough CPUs and memory.
Building something? I'd love to talk to you!
Ryan Worl retweeted
Given the response to jev-align, we created ai-functions.dev, an experimental public registry to share and collaborate on AI Functions with others.
We're super excited to see the AI Functions folks are building with jev-align and hope you find this useful!
Jev is cool, but like any foundation model it needs to be calibrated to your decision criteria.
We launched jev-align: an open-source CLI to quickly teach Jev what good and bad looks like using GEPA.
Try it out! github.com/sutro-sh/jev-alig…
Ryan Worl retweeted
Jev is cool, but like any foundation model it needs to be calibrated to your decision criteria.
We launched jev-align: an open-source CLI to quickly teach Jev what good and bad looks like using GEPA.
Try it out! github.com/sutro-sh/jev-alig…
Ryan Worl retweeted
insanely cool blog post coming tomorrow about how we do automated migrations from any Kafka cluster to WarpStream with no downtime
Ryan Worl retweeted
rare we get to talk about some of our bigger workloads
25GiB/s ;)
and we have bigger ones!
Eternal (the parent of @zomato and @letsblinkit) cut logging costs 60% and benchmarking costs 80% by replacing Apache Kafka® with @warpstream_labs, all while auto-scaling from 2.3 to 25+ GiB/s in throughput. warpstream.com/blog/eternal-…
Ryan Worl retweeted
qwen 3.7 flash is so cheap that you could send it all your production logs and ask it to write a haiku about each one and it would only be 3x as expensive as sending the logs to datadog
Ryan Worl retweeted
the most thoughtful piece you'll read on AI-powered product development:
warpstream.com/blog/a-brief-…
Ryan Worl retweeted
the SpacetimeDB controversy is obviously silly
but... the architecture has a lot of merit
you can get stupid QPS if you push the entire txn into the db
this has important implications if you're building a system where metadata scaling is the bottleneck *hint* *hint*
















