.@johnternus regarding the MacBook Pro:
1. Nobody cares about the touchscreen -- we all have iPads
2. The weight is fine
3. The bezels are perfect already
4. The only thing people want is more memory and better processors for local models!
Drin retweeted
The way frontier labs have restricted access to cyber capabilities makes no sense. If you're considered a "defender" you're not allowed access to the "offensive" versions of the models (the ones that can do development/validation of malware and exploits).
So for example, if you want to build some sample malware to test a detection system, nope.
Or if there's a major crisis due to a critical vulnerability in PHP and you need to rapidly triage fake exploits to see if there are any real ones floating around so you can warn people, nope.
Want to build a remote code exploit to make sure the detection rules you plan on proposing to the clients actually work? Hard nope.
You gotta call your red team friend and wait for them to do your job for you, because "defender" are only allowed to play in the sandbox with the children.
Not an expert, but I think that the ability to triage in-the-wild exploits during a major crisis affecting 40 million systems is possible maybe important.
And then they want to ban abliterated open weight models, which half of the people are only using because frontier labs will only give them access to lobotomized models.
based on my tests, Sonnet 5.5 is still faster than 6.1 Terra but 6.1 Terra produces better results for screenshot and writing tasks
the most reliable real-time sync i have experienced in an amp is in @AmpCode
i used the composer as my notes to sync between devices 🤣
Drin retweeted
I built 𝚌𝚙𝚞-𝚌𝚑𝚊𝚝, a reproduction of @openai's findings of covert communication using the CPU.
It runs on a generic host with 2+ Firecracker microVMs with no internet access. Works on x86 and even my M5 chip.
I was able to chat via 3 separate mechanisms:
① CPU contention
② Cache eviction timing
③ DRAM bandwidth contention
… across multiple CPUs, defeating all Firecracker's production recommendations (no SMT, no KSM, tenants pinned to different cores.)
Essentially, if shared hardware is involved, there's a good chance your agents can communicate covertly. And with really decent latency.
The good news: this is decidedly different from a *side-channel attack* where the agents could steal information (Meltdown/Spectre), a category of attack that providers like Vercel Sandbox mitigate. Further, in our real-world environment, these 'whispering' techniques are much harder to pull off and easier for us to monitor and detect (sampling hardware counters + lots of at-scale statistical data.)
Noteworthy: ironically, OpenAI and Anthropic's models refused to do this work. Open weight models got the job done. I'm worried the labs' stance might backfire and get in the way of helping developers build correct and secure systems. e.g: building a secure sandbox requires having this kind of analysis, and without it, we'll have a less secure world.
Drin retweeted
It's orbin' Zeit
(Some of you are old enough to get it)
I moved to @AmpCode and I love it.
They just shipped self-hosted orbs, so I made a template to run them on @Vercel Sandbox and Daemons (beta).
Every thread gets its own persistent sandbox, and auth is OIDC, so there’s no Vercel token to manage.
github.com/atinux/amp-orbs-o…
Drin retweeted
For the work I do, I can’t see why I’d develop locally anymore.
Why mess with worktrees when every thread can get its own computer?
The agent installs whatever it needs. Need ClickHouse or Kafka or Elasticsearch or Go or Rust or Python? Install it. Who cares? Zero cruft on my machine.

















