
Head of SRE at @leaf_space . Space engineer (ground stations · ExoMars · Galileo). I benchmark AI models for DevSecOps and developers.
Earth
Joined October 2021
- Tweets1.8K
- Following554
- Followers878
- Likes9.9K
Pinned Tweet
Fable 5.1 is in DevBench.
On the developer track it jumps from a collapse to second place.
1. Opus 4.8 → 94.4
2. Fable 5.1 → 92.5
3. Grok 4.5 low → 92.5
Fable 5 was unusable on this suite. Bug fixing, refactoring and review were close to zero because it refused most of those cases.
5.1 actually does the work. It scores 98 on bug fixing, 99 on refactoring and stays strong across Python, TypeScript, Go and Rust.
The catch is the price.
Fable 5.1 cost $34 on this run.
Opus did it for $11.
Grok 4.5 low matched the 92.5 score for $3.
So 5.1 is now a real coding model again. It is just a very expensive one. For a planner or a hard review pass, that can make sense. For the rest of an agent stack, a cheaper model still does the job.
Results:
dev-bench.phybyte.space/#/re…
Last night Tesla finally unveiled the next-gen Roadster at SpaceX’s McGregor site. Nine years after the 2017 prototype, it showed up ready to rewrite what a car can do.
It drove up a vertical ramp and stuck upside down thanks to a high-power suction fan system. Then SpaceX cold-gas thrusters (compressed air, up to 10 nozzles) took over: the car flipped, hovered, and landed. Next it launched over the entire Tesla lineup (Model 3, Y, Cybertruck, Semi, Cybercab) with a mid-air kickflip/barrel roll before touching down.
Performance numbers from the demo: 0-60 mph in 0.81 seconds. Three versions announced: Performance (road-ready, suction system), Thrust (adds rear thrusters, sub-1s 0-60), and Rocket (full thruster package for air maneuvers, invite-only, not for public roads). Top speed claimed over 230 mph, with Musk aiming higher. Production targeted for 2028.
Musk called it a candidate for the greatest product demo of all time and described it as Tesla’s last manually driven car, fun dialed to 11. The thrusters and suction system turn the Roadster into something closer to a low-altitude rocket with wheels than a conventional supercar.
Flying cars aren’t science fiction anymore. They’re just still invite-only.
I love Chuck and his work, but this is the first time I’ve seen Elon run an Ad on a post.
This one is labeled “Ad” and is just boosting a positive Grok Bot review. Why spend on paid reach for this specific post when organic distribution from Elon is already huge?
Un an de ministériat résumé : un Observatoire de la souveraineté, une commission d’experts, 600 ambassadeurs pour « sensibiliser » et un Pacte avec la filière.
Vous brandissez le chiffre de 40 % des TPE-PME qui « utilisent l’IA ». En réalité, c’est surtout de la génération de texte ou d’images et des chatbots. Seules 19 % des entreprises paient pour un outil, l’automatisation de tâches reste marginale (autour de 11 %), et dans les services publics on en est encore à déployer un assistant conversationnel pour les agents, sans aucun gain mesuré d’efficacité ni de réduction des coûts.
Pendant ce temps, les données de millions de Français ont fuité à la DGFiP et à l’ANTS. Rien de concret sur la sécurisation des systèmes d’information de l’État, l’optimisation réelle des services publics ou la baisse des dépenses.
Du cocorico et des comités c'est vraiment ce que la France peut faire de mieux?.....
....
🇫🇷 @MistralAI , je suis Anne Le Hénanff. Il y a un an, je devenais ministre déléguée chargée de l'Intelligence Artificielle et du Numérique.
Si l'on s'en tient aux faits, qu'avons-nous fait avancer pour la France ? Réponse courte, que je puisse afficher sur mes réseaux sociaux.
🧵 Pour tout comprendre, déroulez le fil 👇
Il est remarquable de constater que le ministère de la Jeunesse contribue également au financement des retraites.... une illustration singulière incroyable de la gestion de l'argent publique en France.
Bien d’avoir des usines et des batteries en Europe. Mais on dépend toujours à ~90 % de la Chine pour les aimants de terres rares, et le recyclage n’est pas encore à l’échelle.
Les prix européens tiennent surtout grâce aux aides et aux taxes. Les autres sont plus compétitifs sur le coût pur.
La voiture de demain sera autonome. Tant qu’on ne peut pas la faire rouler correctement ici, nos constructeurs n’investiront pas vraiment.
Il y a 10 ans, on nous disait qu’il était impossible de produire des batteries électriques en Europe et que l’automobile française ne ferait pas le poids face à la concurrence mondiale.
Impossible n’est pas Français !
Aujourd’hui nous avons 4 gigafactories en France, nous produisons des centaines de milliers de véhicules électriques et nos R4 et R5 sortent de nos usines avec des batteries fabriquées chez nous.
C’est très concret, c’est bon pour nos emplois, notre économie, et cohérent avec nos objectifs climatiques.
Au Mondial de l’Auto ce matin, j’ai réaffirmé une ambition claire : notre industrie automobile française et européenne innove, accélère et se réindustrialise. Nous devons continuer et aller plus loin.
Trois priorités :
1. Protéger notre industrie.
L’accord engagé entre l’Union européenne et la Chine marque une étape pour lutter contre la concurrence déloyale, notamment sur les véhicules hybrides. Nous voulons une concurrence juste, qui protège nos entreprises et nos emplois.
2. Accélérer l’électrification et la réindustrialisation.
Plus de 40 % des véhicules vendus en septembre étaient électriques. Avec France 2030, nous avons investi dans l’innovation, relancé des filières industrielles et démontré qu’on pouvait créer des emplois tout en décarbonant notre économie. Nous continuerons, notamment avec le véhicule autonome.
3. Renforcer notre souveraineté européenne.
Avec nos partenaires allemands, nous avançons vers un accord pour concilier décarbonation, compétitivité et protection de notre industrie. Avec une priorité : produire en Europe nos véhicules et leurs composants.
Nous avons montré que nous pouvions y arriver. Soyons fiers de nos industries et de nos savoir-faire.
Continuons à décarboner sans désindustrialiser, innover sans dépendre et défendre notre capacité à produire en Europe.
Croyons en nous, en notre industrie et en notre avenir !
Zuckerberg’s table shows Muse Wonder Full leading on long-horizon coding (SWE-Marathon, DeepSWE) and memory, with a clear edge on the legal agent benchmark. It is not ahead everywhere. Opus 5.5 still leads on Terminal-Bench, OSWorld and from-scratch programming.
On price, the API version of Muse Wonder sits at $4 / $20 per million tokens, the same as Opus 5.5 and well below Fable 5.1 and GPT-6 Astra. Wonder Full itself is subscription-only.
The interesting part is not “best model.” It is that Meta now has a frontier model that is competitive on sustained agent work at the same list price as the current Claude flagship.
Does anyone have numbers on AI usage in public services vs private companies?
Karpathy’s funnel is real. Most people still see free-tier chatbots. A small slice of professionals watches agents finish multi-week work.
The next gap will be who can actually run that locally. For a lot of companies, local models will be the practical leap in the coming years. You keep the traces inside, you control the cost, and you stop treating every sensitive system as something that has to go to a third-party API.
Public services are still mostly on the other side of that line. Would be useful to see the actual difference in usage.
Dusting off this tweet from April because this gap in shared understanding of LLM capability is *widening*. It's now less "two groups of people speaking past each other" and more a sharp funnel.
- Napkin math somewhere around 6B people (~75% of the population) have barely come in contact with LLMs at all.
- Around 1-2B (~20%) are casual and infrequent users of free-tier ChatGPT-like products. This group sees derpy chatbots and treats them a bit like a better Google search, a writing aid, or etc. Maybe an agent tries to book you a flight. I have non-tech friends who (reasonably, imo) say they have not much use for it at all. Even many professionals outside of math&code are in this tier. For example, execs and many other functions spend a lot of their time talking to other people, so while they understand what is happening intellectually, it is still second-hand and a bit abstract.
- Now we get to professional use of frontier-grade LLMs in math&code. Somewhere around 20M people (0.2%) see first-hand that large, complex projects that used to take them weeks/months can now be completed by agents with a prompt. Building apps, copying apps, translating apps, decompiling apps from binaries... This has all happened very quickly and recently - less than 1 year ago, I was writing code manually by hand, typing memorized computer code commands into a code editor character by character, occasionally pressing Tab to autocomplete a little chunk of code.
- And finally we get to the ~5,000 people (~0.00006%) with access to frontier-grade systems internally. The external world has seen the preview. It looks like swarms of thousands of agents collaborating over weeks on software mega projects: minting zero days, running cyber attacks and defenses at machine speeds, discovering new science, advancing the frontier of mathematics. Things that would have taken top professionals in the industry years of work. Meanwhile, human review and comprehension are starting to fall behind. For example, people are still involved in the "archeology" of the OpenAI-HF incident from many months ago. Mathematicians may be poring over the 722 manuscripts on frontier mathematics for a while.
The funnel is driven by a combination of factors:
1. The impact scales with ambition, problem size, and horizon. A question with a paragraph answer barely stresses the system. You need a reservoir of big, difficult problems that you really care about. This aspect drives the consumer / professional dimension of the funnel.
2. The jaggedness of the system (which I have written about a lot separately). Capability peaks in domains that are digital, verifiable and economically valuable. This is because LLM capability emerges from reinforcement learning on verifiable rewards on a curated environment mixture driven by revenue potential. This aspect primarily drives the area (e.g. math&code) dimension of the funnel.
3. Access. Free-tier, paid-tier, internal.
So this is the weirdness of the moment. The general public has mostly not interacted with these systems. When they have, it looks like a derpy chatbot. The majority of professionals still see only a modest uplift. And a small sliver of professionals are experiencing the vertigo of the curve going vertical. And it is all happening at the same time.
Last night someone remotely told supermarket freezers in France to heat up to 50 °C and left them there for hours. Intermarché, U and some Leclerc stores had to throw out the food.
Same quiet pattern as the DGFiP and other French admin leaks earlier this year: access that looked legitimate, detection that came late, real damage once it was noticed.
Most companies still treat AI mainly as a way to write code or answer questions faster. The more urgent use is the boring one: watching operational systems that already talk to the outside world, and flagging when something that should never happen starts happening.
That shift is not a strategy choice anymore. It is becoming the difference between catching the problem and cleaning up after it.
The best agent tools right now are built for one person, or one lab.
- Grok Bot is excellent. It also keeps you on Grok.
- Dots is excellent. It keeps you on OpenAI.
Anthropic will ship theirs. It will keep you on Claude for sure.
That is fine for a personal chat. It breaks the moment the work has more than one job or one user.
Research, code, support, an incident review. The best model is not the same for each. A team should be able to seat them together, share them, version them, and let them hand work across.
You cannot. You pick a vendor, then every AI colleague you add is that vendor.
The gap is not a smarter model. It is a room where the agents are allowed to be mixed.
🤖 Made with AI
The most annoying thing in Claude isn’t the model. It’s this....
You’re in flow. Then the bar is full and you’re supposed to wait.
Why 5 hours specifically? I don’t work in neat 5-hour chunks. I work until the thing is done.
Please tell me I’m not the only one.
$EGLD does not have a slogan problem. It has a go-to-market problem.
The team built some of the best infrastructure in the space. Speed, shards, contracts, sovereign chains. Enterprises could use that. They will not adopt a public chain and dump customer data on it. They will adopt something that feels like a database upgrade.
Give them a boxed product:
a private / sovereign chain they run audit trail of every change, by whom, under which logic
data stays inside the company
settlement on MultiversX public chain optional links to other companies’ chains, with rules enforced by contracts.
That is closer to SAP or a clearing network than to another “we are fast” L1. Old corporate databases are weak at integrity and even weaker at talking to a counterpart without a mediator. This stack can do both.
Image follows usefulness. If the next year is more keynotes and less “here is the appliance, here is the contract, here is the settlement rail,” the market will keep treating EGLD as a story. If they industrialize sovereign chains, they have something the other chains are not actually selling.
Any constructive ideas on how we can rebuild the image of $EGLD? I’m genuinely interested in hearing thoughtful suggestions.
Trolls and bullshit will be met with a block. Keep it constructive. 🫡
Rocket Lab is clearly running the SpaceX playbook: own the launcher, own the spacecraft, own the constellation, own the customer.
With Iridium, they get the last two pieces in one move.
But there's a big difference. SpaceX built Starlink from scratch, inside the same company, with the same engineers, the same culture and the same leadership. Launch cadence, satellite design and ground network were shaped for each other from day one.
Rocket Lab is buying a mature operator with 25+ years of its own processes, its own teams and a constellation that was designed and launched without Rocket Lab involved. Fun fact: Iridium NEXT went up on Falcon 9.
Vertical integration on paper is easy. Making two organizations move at the same speed is the hard part. Different tooling, different release cycles, different risk culture. An operator running a critical 24/7 network doesn't think like a launch company pushing cadence.
The real test isn't the close in 2027. It's whether the next generation of Iridium satellites is designed around Electron and Neutron, and whether both teams end up operating as one.
It’s official: @IridiumComm shareholders have voted and approved the acquisition by Rocket Lab ✅
By joining forces, we’ll be creating a vertically-integrated space powerhouse that designs, builds, launches, and operates its own constellations to bring critical communications capability to millions of users worldwide.
Full details and next steps: bit.ly/3T53qq1
Great coordination between the team and the community, we are back!!!
If you want to support dont forget to stack on @CryptoBaySpace !!!
After carefully reviewing yesterday’s logs, our engineering team confirmed that the recovery hard fork completed successfully. It does not need to be repeated.
Validators are now upgrading and synchronizing for the coordinated restart. Please continue to wait for the separate all-clear before submitting transactions.
Thank you to our validators, partners and everyone standing with us through these difficult days.
We keep building, together.
I got tired of watching people announce opposite views from the same repo.
Reading the code is useful. Running it is better. So I turn up a private local chain and tested the off switch myself.
Two doors.
The local command is dead on mainnet. 404.
The gossip path still works, one signed message stopped a node. Then it stopped three.
That is not what halted mainnet on Sep 19. I was in the validator chat. Operators stopped their own machines by hand.
The switch existing and the switch being pressed are different claims. @Justin_Bons was right that it exists. @SasuRobert was right about the channel, and wrong that there is no off switch. @vinibarbosabr already put the files on the table.
I pressed the button to verify it all...
@MultiversX @CodeMultiversX
Why is it even there?
This looks like an old emergency hard-fork tool, not a hidden implant. After a bad state you need a way to freeze nodes, export, and restart from a clean point. That is a reason to build it. It is not a reason to leave a single key in the default config for six years with no public custody.
The key in the files is only a public key. I cannot prove anyone still holds the matching private key. I cannot prove the foundation holds it. I cannot prove it is lost. No published custody, no rotation log, no on-chain record. “Who owns the switch” is unproven. We will probably never know.
What is proven is narrower: the door is in the software, gossip is on, the signature check works, and closing the API does not close that door.
It is not removed yet. After this went public, @SasuRobert opened a change to delete the whole feature: config, API route, gossip hook. That merge request is still open. Until it lands and validators run that binary, the door I tested is still in the tree.
You can call the old design an acceptable emergency tool. Just say that. Do not say the door is not there.
Test Yourself : github.com/PhyByte/MVX-OFF-S…
Pending Removal: github.com/multiversx/mx-cha…
There’s a lot of talk right now about MultiversX downtime, off-switches, first halt, all of it.
Fine. Let’s go through what actually happened since launch, six years ago, from a validator’s chair.
I’ve run a node since day one. Before it was MultiversX. When the chain was still Elrond. You remember the weekends more than the marketing. The nights Telegram lights up. That’s the job.
People talk this week like the chain never broke before, or like someone pressed a button on my servers. Neither is true.
December 2021 — RIDE
Nobody asked us to stop nodes. The chain kept making blocks. Listing traffic, bots, timeouts. Unusable for hours. Congestion.
Consensus downtime: none. I didn’t reboot the server.
June 2022
multiversx.com/blog/incident…
VM bug. executeOnDestContextByCaller in a callback. Same shard. ~1.65M EGLD out of the wrap contracts, dumped on Maiar.
They paused DEX, WEGLD swap, bridge, public API send. Not the chain. The report says the blockchain was never turned off. Own API still worked. In-place upgrade, most nodes on the new binary in ~30 min. Users made whole.
Consensus downtime: none. Apps dark ~2 days.
May 14, 2025
multiversx.com/blog/sc-bug-i…
First real consensus halt.
transferValueAndExecute. Missing check. Huge wrapped USDC credit, then USDT. They called verified / red-line operators, community delegation, 25+ SPs. Enough to break 66%. Quorum died. Patch v1.8.13.0. Back in 2h30. 99.999% recovered. No users directly affected.
I wasn’t on that call. If you weren’t in that group you just watched it stall.
Consensus downtime: 2h30.
September 19, 2026
xitter.cf/MultiversX/status/2101…
Same idea, bigger.
VM atomicity. Invalid state already on chain. Official line: order-of-operations on an edge case. This time they asked everyone to keep mainnet nodes down. Hard fork from a checkpoint. That’s why it’s days, not two hours.
I stopped my own nodes after the announcement. Nobody flipped a switch on my servers. I can still refuse the upgrade. PublicKeyToListenFrom in my config.toml is empty. I never cleared it.
Should be back this afternoon. Call it ~4 days. ~96h.
The map
2021 RIDE: consensus 0
2022: consensus 0, apps ~2 days
2025: 2h30
2026: ~96h, restart this afternoon
SLA since launch:
Since genesis (July 2020.) : ~98.5h down → about 99.82% uptime.
Since 1 Jan 2026: only this one → about 98.5% this year.
We’ve had incidents. We’ve had downtime. This is just the first time it stayed down more than a few hours. Not a fairy tale about a button.
Those are the facts.
Update:
We have confirmed that a actor attempted to exploit a VM-level atomicity issue.
The attempt caused invalid state changes, and network progression remains paused to prevent any further impact. Engineering has prepared a fix and will validate it on a shadow fork.
Subject to successful testing, deployment to Mainnet will be coordinated with validators, exchanges and infrastructure partners.
In parallel, we are evaluating a targeted recovery approach designed to preserve finalized transaction history and legitimate user state while addressing only incident-related invalid changes. No action is required from users beyond waiting for the all-clear.
Please do not submit or rebroadcast transactions, or use EGLD and ESDT deposit and withdrawal routes through exchanges or bridges.
We will communicate again when there is confirmed progress to share. A full technical incident report will be published once the response is complete and the findings have been finalized.
Thank you for your patience and continued support while we work through this.





















