feel the agi
Austin, TX
Joined October 2011
- Tweets14.9K
- Following5.5K
- Followers5.1K
- Likes248K
Hassan Hayat 🔥 retweeted
Introducing Echo-3. A state-of-the-art world model.
Echo-3 turns phone captures into photorealistic, metric-scale 3D worlds. From a single room to multi-floor buildings, outdoor and public spaces.
Available today.
Hassan Hayat 🔥 retweeted
Here's a direct link to OpenAI's PDF claiming a refutation of ETH. In particular, it's claimed that 3SAT on n variables is in about exp(n/(log n)^{1/2+o(1)}) time
github.com/openai/math/blob/…
What's the kalshi now on p = np?
The computer science collaboration will understand and explain a result concerning the Exponential Time Hypothesis (ETH), a longstanding conjecture about the computational complexity of Boolean formula satisfiability, a problem deeply related to the P vs. NP problem.
Surprisingly, our system has recently proved that the ETH is false, a result that was subsequently verified in Lean.
The refutation of the ETH reopens questions about how much faster these tasks could become, and may help guide the search for better algorithms. Finding such algorithms, and turning theoretical advances into practical improvements, will require significant further research.
Our system found its natural language disproof for the ETH we reached out to to @rrwilliams. Ryan will form a collaboration with Russell Impagliazzo and Ramamohan Paturi to verify and shepherd this result. Impagliazzo and Paturi, along with Francis Zane, are the original proposers of the Exponential Time Hypothesis, and Williams has refuted strong versions of the ETH, used ETH for hardness results, and connected algorithms and lower bounds.
This group asked us to make all raw data of the results public to facilitate independent verification by the community, which we have done by posting the natural language proof and Lean formalization to our GitHub repo. The group also invites the community to help organize an open examination of the ETH claim and to discuss the broader questions that AI-generated breakthroughs raise about verification, access, credit, and the future of research.
github.com/openai/math/blob/…
Hassan Hayat 🔥 retweeted
The computer science collaboration will understand and explain a result concerning the Exponential Time Hypothesis (ETH), a longstanding conjecture about the computational complexity of Boolean formula satisfiability, a problem deeply related to the P vs. NP problem.
Surprisingly, our system has recently proved that the ETH is false, a result that was subsequently verified in Lean.
The refutation of the ETH reopens questions about how much faster these tasks could become, and may help guide the search for better algorithms. Finding such algorithms, and turning theoretical advances into practical improvements, will require significant further research.
Our system found its natural language disproof for the ETH we reached out to to @rrwilliams. Ryan will form a collaboration with Russell Impagliazzo and Ramamohan Paturi to verify and shepherd this result. Impagliazzo and Paturi, along with Francis Zane, are the original proposers of the Exponential Time Hypothesis, and Williams has refuted strong versions of the ETH, used ETH for hardness results, and connected algorithms and lower bounds.
This group asked us to make all raw data of the results public to facilitate independent verification by the community, which we have done by posting the natural language proof and Lean formalization to our GitHub repo. The group also invites the community to help organize an open examination of the ETH claim and to discuss the broader questions that AI-generated breakthroughs raise about verification, access, credit, and the future of research.
github.com/openai/math/blob/…
Hassan Hayat 🔥 retweeted
Announcing three major scientific discoveries, one each in mathematics (harmonic analysis), computer science (complexity theory), and physics (quantum field theory).
AI starting to help us improve our understanding of the universe! openai.com/index/building-sc…
There are companies out there that make their money by doing ports. Like Mac ports or Switch ports. That line of work will soon be automated
Hassan Hayat 🔥 retweeted
1/7 🥥 New speculative decoding method!
Introducing DCOCO: Contextual Correction of Parallel Drafts.
Parallel drafters are fast, but lose context between predicted tokens.
DCOCO restores it without giving up parallelism.
Up to 6.6× faster than vanilla decoding. 🧵
Hassan Hayat 🔥 retweeted
I really like that coding agents are now good enough that you can just make your own ultra specialized tool for the one thing you're curious about, which in the past nobody would have taken the time for. Nice example:
Hassan Hayat 🔥 retweeted
Can a language model be based purely on self-conditioning? 🤔
Yes! Meet LAW 👋 (a.k.a. Loopholing All the Way!)
🧵1/8
Hassan Hayat 🔥 retweeted
I built bbtree, the foundation of databases and filesystems, and the fastest concurrent btree.
Code: github.com/XiangpengHao/bbtr…
Blog post & demo: bbtree.xiangpeng.systems/
Hassan Hayat 🔥 retweeted
Maybe we should delete the 99% of stuff that is just wasteful and friction-causing, the main purpose of which seems just to be to increase attack surface.
xitter.cf/unusual_whales/status/…
Hassan Hayat 🔥 retweeted
"Why is formal verification exploding NOW?"
1. Cost of proofs is going DOWN (as AI gets more capable)
2. Cost of exploits is going UP (as AI gets more dangerous)
3. Proofs exterminate exploits
4. Bonus: proof checking = perfect math/coding RL reward
The rest is economics
I’ve heard several OAI people say there are unfixable bugs in hardware that are exploitable by AI models directly speaking machine code so even if we could solve software that’s not enough. We need defense to move faster than offense if that’s even possible we may just have a new normal that requires adapting to insecure software (bank transfers require going into a branch and taking a dna test 🤣😬)
Hassan Hayat 🔥 retweeted
I can finally talk about Mass Effect Universe.
Since Bioware closed I can now reveal that I was part of the Mass Effect Council, saw what BioWare was building, and provided feedback during development.
• Set 600+ years after the Reaper War
• You play as a customizable N7 agent
• Instead of being a walking gun rack, you're a cross between John Wick and James Bond
• Shepard's legacy preserved, regardless of your ending
• A galaxy divided into three major factions
• Humanity, Krogan, Batarians, and more allied together
• Council races forming their own alliance
• The Geth emerging as a third superpower
• A galactic Cold War instead of another Reaper style invasion with a shadowy adversary
• Geth-built megastructures
• Connections between the Milky Way and Andromeda
• Experimental technology implanted in you as a unique point of difference
• Hacking and manipulating the environment
• See through walls, identify systems, remotely trigger hazards and more
• Handcrafted missions like ME1-3
• But with Hitman-style freedom in how you complete them
• Brutal close-range executions
• Squadmates who can clash with each other
• Romance wasn't being sanitised
• Liara returns - now an incredibly powerful Asari Matriarch
From what I saw, BioWare was making Mass Effect for us, the fans, not for people who don't exist.
It looked incredible.
And now we may never get to play it.
Find out more here: youtu.be/ZOWrTNazZxM
#SaveMassEffect
Hassan Hayat 🔥 retweeted
I always thought it was a shame that modest default stack setups made alloca() a generally-frowned-upon technique in C/C++. With 64 bit architectures, give every stack a virtual address space equal to the physical memory by default!
You can do a surprisingly good job of memory management with just the stack, and I contend that it has both correctness and performance advantages.
Allocations are a trivial pointer adjustment, and frees are literally free. Keeping everything linearly packed is friendlier for all layers of the cache hierarchy, and it makes keeping everything in huge / gigantic pages easy.
Leaving temporary intermediate blocks on the stack can seem wasteful, but unless you are dealing with algorithms that make > O(n) temporary allocations, it is usually not a big deal.
Static analysis can check if you store a stack pointer into a structure deeper in the stack, which is a use-after-free, and then memory management correctness is guaranteed.
The discipline of caller-allocates-return is awkward in some dynamic cases. It would take a change in low level calling conventions, but you could plausibly have functions that return with the stack extended from where it was when they were called. I’m not holding my breath for that.
It isn’t obvious if having AI coding agents makes discussions of software architecture more or less important!
URGENT - PHP Warns of Another Unpatched RCE Two Days After Emergency PHP2Shell Patches thehackernews.com/2026/10/ur…
Hassan Hayat 🔥 retweeted
The models aren't causing this. Decades of sloppy, inserious bs and corner cutting is causing this. Decades of "quick, let's outsource to the cheapest codemonkeys we can find" are causing this.
You can cry about it, or you can actually FIX THINGS. Either way, it's time for some reaping what was sewn. Burying your head in the sand doesn't fix anything. After a period of time, the vulnerabilities will be patched and things will stabilise again. Literally nothing has happened, except long standing problems have been identified that you were blissfully unaware of
