wilbeibi retweeted
I used to be the person companies called after they got hacked.
And I noticed something early on.
The hack almost never sank them. The cover-up did.
Every time, the team’s instinct was the same: wait until we know more, wait until we're sure, wait until we have the perfect statement, etc.
And some of the biggest companies in the world have learned what that waiting costs.
In 2016, Uber got hacked. Instead of telling anyone, it paid the hackers $100K to delete the data and stay quiet, and labeled it a bug bounty. The truth came out a year later. Uber paid $148M to settle with all 50 states, and its former security chief was criminally convicted.
That same year, Yahoo revealed that a 2014 breach had exposed 500M accounts. The news landed in the middle of Verizon buying the company. Verizon cut $350M off the price.
And in 2017, Equifax discovered a breach affecting over 140M Americans, then waited 40 days to tell the public. During that window, an executive who'd figured out what happened sold nearly $1M in stock. He went to prison for insider trading.
Meanwhile, hackers don't wait. They post your data. They email your customers directly. And when customers hear it from a stranger first, that trust is gone for good.
Telling customers early doesn't mean admitting fault. It can be as simple as: "We found suspicious activity. We're investigating. Here's what you should do right now. We'll update you as we learn more."
On Tuesday, I'm sharing the exact framework I'd use to write that email if I were in your shoes. Follow and turn on notifications so it's there when you need it.
Customers will forgive you for getting hacked. Most of them expect it by now.
What they won't forgive is finding out you knew and said nothing.
wilbeibi retweeted
Latest (and probably penultimate) Building Slack post is up: buildingslack.com/salesforce…
What it's like being eaten by the whale
Pretty cool!
We just raised a $60M Series B at a $1B valuation to build @daytonaio into the Agent Cloud.
@FirstMarkCap led the round, with all key existing investors and angels doubling down.
We're also thrilled to welcome the founders of some generational companies aboard, including @patrickc (Stripe), @tobi (Shopify), @AravSrinivas (Perplexity), @BrendanFoody (Mercor), @oliveur (Datadog), @adamdangelo (Quora) and @ericsyuan (Zoom)
We're a 35-person team. But that's about to change; we're hiring across the board, and we'd love for you to join us.
This is Pele, my new rendering library for diagrams and charts, compatible with the latest Mermaid syntax.
- 100-500× faster than mermaid.js
- 6× smaller bundle
- No dependencies
- Easy to theme
- Responsive to device width
In pursuit of making Obsidian insanely fast and cohesively designed, I always found the Mermaid library to be too big, too slow, and too hard to theme. Pele will be the new renderer in the next version of Obsidian, but you can start using it now.
Pele [ˈpɛlɛ] is named after the goddess of volcanoes and fire. It's open source under the MIT license. Try the playground!
wilbeibi retweeted
Today we're announcing Strands Box, our open source sandbox for developers building AI agents.
New blog post from me, on the Strands blog: strandsagents.com/blog/stran…
wilbeibi retweeted
Well, this is fast.
We tested @nvidia's new Vera CPU head-to-head against our most sought-after CPUs.
8x faster to spin up 1,000 @daytonaio sandboxes. 2,000 done in 27.4s, before Zen 5 finished 1,000.
Like a Rimac Nevera hitting 200 km/h before a Porsche 911 clears 100.
Full results soon 👀
wilbeibi retweeted
It's official! @daytonaio has a new address: daytona.com
Loved every min of it. Good engineers don't get attached to any specific language/framework.
youtube.com/watch?v=vDjW_dRy…
TL;DR: We just made Raft source-available.
We don't accept pull requests. We want prompt requests instead.
We are exploring what a new contribution model for open source could look like in the age of agents.





















