I used to be indecisive, but now I'm not so sure.
San Francisco, CA
Joined February 2008
- Tweets17K
- Following2.3K
- Followers11.3K
- Likes2.3K
I don’t need the fancy new $300 @Apple TV with a Precision Finding remote. I already have that feature.
Every time I sit on my sofa, the TV turns on.
Roman Stanek retweeted
If you think that big corporations never listen to their customers, then how foo you explain Samsung?
If you still believe in free will, pay attention to what Codex suggests as the next step in the chat window.
Our thoughts are fully predictable before we even have them.
Surprised @Uber Eats doesn’t refund tips on undelivered orders, especially since tipping is done in advance.
Roman Stanek retweeted
Papers rejected by Nature:
1933 · Fermi’s theory of beta decay (“too remote from reality”)
1937 · Krebs’ citric acid cycle (Nobel Prize, 1953)
1973 · Lauterbur’s first MRI paper (Nobel Prize, 2003)
Roman Stanek retweeted
Thankful for all the coverage around our raise 🙏
Daytona is building a cloud for agents that's like giving every agent its own computer. It has attracted founders of Stripe, Perplextity, Datadog, Mercor and others as angels, it says.
spr.ly/6010BHbrem
Roman Stanek retweeted
Confused about U.S. foreign policy? I hope you will feel a bit less confused after you read my new essay on @realDonaldTrump's debt to Richard Nixon.
Roman Stanek retweeted
Holy moly... this new paper finds that 88% of VC-backed founders receive zero exit value 🤪🤪🤪
The clearest explanation I've heard of the eMudhra security incident:
Instead of generating a random 256-bit number, they generated a random number between 0 and 256.
Spam is just like fashion:
A year ago, my inbox was full of AI SDR pitches.
Six months ago, it was “We can connect you with investors and buyers.”
Now it is mostly “A few of our partners are looking to license operational data from companies in your space.”
Spam might be the best indicator of where the AI hype cycle is headed.
Roman Stanek retweeted
Some stats on #php2shell. In the 10 hours before it was publicly announced, across the @Cloudflare network we saw thousands of attempts to exploit it. That jumped to tens of thousands in the 45 minutes post announcement, hundreds of thousands within 2 hours, and millions now.
Roman Stanek retweeted
Many years back, I made a statement that “HTTPS is dangerous” due to significant, and obvious, problems in the design of the Certificate Authority system.
The core point I made: A small, simple mistake with a Root Certificate Authority has massive impacts throughout the system, making it highly likely that there were untold numbers of “fake” certificates which were “trusted”.
It is a “security based on trust” system, where we are asked to blindly trust dozens upon dozens of Root Certificate Authority organizations (from countries around the world) to never make a single mistake (or implement any backdoors for any government they are beholden to).
It is, quite simply, a design that appears specifically made to be abused and manipulated.
I was told that I did not understand how CA’s work.
I was mocked and ridiculed.
Well… as a wise man once said…
Who’s laughing now, Wayne?!
In April of 2025, eMudhra (an Indian Certificate Authority), published 8 intermediate CA keys which were so weak that a small child could guess the numbers in a few seconds.
One of the private keys was, literally, 4.
Just… 4.
This massive problem was not made public until October 17th of this year, when it was discovered by an anonymous guy on the Internet who goes only by “Wayne” (like “Cher”…. but… “Wayne”).
What this means in practical terms: It has been trivially simple, for the last year and a half, to create fake “secure” HTTPS certificates. (One person even created a fake HTTPS certificate for a Google.com subdomain.)
It took Mozilla 3 days, after learning about this (from “Wayne”), before they updated their certificate list (which many open source projects — including curl and Python — rely upon).
As of this moment, many systems are still vulnerable (including macOS).
