
@theoi
iAccount based inUnited States
About this account
- Account based in
- United States
- Connected via
- United States App Store
Account-level information from X, not a live location or the device used for a specific post.
Full time CEO @t3dotcodes & @t3dotchat. Part time YouTuber, investor, and developer
San Francisco, CA
Joined October 2016
- Tweets69.5K
- Following4.3K
- Followers41K
- Likes391K
Had the exact opposite of this today. I would never have survived the day without agents.
They caught so many problems. They triaged all the outages and security issues. They rolled dozens of api keys across various platforms.
Building with AI is pretty damn cool.
Theo - t3.gg retweeted
Kept going, typing in the composer now does ~75% less work, streaming replies no longer re-render the whole chat, and switching threads is ~30% lighter.
Duo launch is closing in, will we have to freeze or will we keep going?
It’s going to get a lot worse btw
October has been an absolute nightmare for software
> Railway - customer secrets exposure
> LiteLLM - malicious PyPI + Docker releases
> Zeabur - infrastructure breached
> OpenCode - AI API keys exposed
> OVHcloud CLI - official binaries backdoored
> Rank Math PRO - malware in official plugin
> TeamUpdraft - customer data compromised
> ConnectWise - cloud backup identities compromised
> Tensorlake - npm package infected
> SubQuery - backdoored npm package
> GhostAction - GitHub repos with malicious workflows
> PHP - critical RCE vulnerabilities
> Node.js - security vulnerabilities patched
> eMudhra - certificate authority keys compromised
> Tailscale - eMudhra incident
At this point, the biggest security risk might not be the code we write, but the code we trust...
"We’re a few model iterations away from every piece of software we rely on being compromised."
I really wish I wasn't right about this 🙃
Replying to @Linahuaa
Hi! Big Anthropic hater here. Fundamentally disagree.
Anthropic is spending way more than they are getting here. It’s causing a compute crisis for them that’s destroying their reputation in record time. The cost to train the thing is probably higher than the revenue will ever be, especially considering opportunity cost.
The security concerns are absolutely real here. Getting a 27-year old 0-day in OpenBSD by running a for loop is not a joke. We’re a free model iterations away from every piece of software we rely on being compromised.
I respect Anthropic for eating the cost here and giving the software world a few weeks to get ahead of the inevitable crisis looming overhead.
99.99% uptime = down for < 9 minutes a year
99.9% uptime = down for < 9 hours a year
A 9 hour outage caps you to 2 nines of reliability for the year.
Spent multiple hours now evaluating Railway alternatives to move my shit to. Conclusion is that Railway's product is uniquely good and nothing comes close to a drop in replacement 🙃
Minimum cost to replicate my setup today is 3x higher than I am paying them currently
My god they're putting grok bots bot everywhere, they're now in:
- the desktop app
- the mobile app
- grok dot com
- x dot com dms
- teslas
- cursor
In the future I would also like my bots to be accessible from:
- a really good apple watch app
- my washer/dryer combo unit
- my fridge
- my lumix s5iix camera
- a microchip in Theo's brain
- my subaru crosstrek
- my nintendo wii u and switch 2 (I don't want it on switch 1)
- my steam deck
- the youtube creator dashboard
I can't believe my favourite gui is built by a YouTuber and a Swedish guy named Julius
I talk about
- why t3code has been my daily driver
- if it makes sense why you should use it
At this point I'm tempted to see if I can recreate Railway faster than they can re-enable deploys 🙃
17 hours btw
It has been 16 hours since I was able to update my deployments on Railway 🙃
AAAaaaAAaAAaAaaaAaAAAAa
xitter.cf/i/broadcasts/1MKgNbBlY…
Everything is on fire and I want to die xitter.cf/i/broadcasts/1MKgNbBlY…
Lakebed, Postplan, and Shoo will be down indefinitely until Railway gets their shit fixed and I can actually redeploy them with rolled keys.
Incidents happen. I understand.
Blocking deploys so we can roll keys without downtime is unacceptable. I'm disappointed in Railway.












