Thomas retweeted
reading feynman lecturess as feynman intended: with accompanying ai-made demo sections for each chapter
rapid acquisition of knowledge is possible thanks to superintelligence
Thomas retweeted
MedMisBench has been accepted to NeurIPS 2026! 🎉 @NeurIPSConf
High scores on medical exams don’t guarantee that an LLM holds up under misleading context. That’s what we set out to test.
Thanks to my co-authors and our clinical panel! More on the benchmark below 👇
Can LLMs keep correct medical judgment when the context is misleading?
LLMs ace medical exams. But real-world use cases rarely come with clean context the way exams do. So we investigated whether LLMs preserve correct medical judgment under misleading context.
Our findings:
> Across 11 frontier model configs, accuracy dropped from 71% to 38%.
> A 14-member clinical panel from 7 countries identified serious potential harm in 38.2% of reviewed cases.
1/8
DeepSeek silently updated their changelog with a new V4-Flash upgrade 1 hour ago.
Their new Terminal-Bench score is 82.7, a massive +25.8 point leap from its initial April preview score of 56.9.
Currently only available via their API, open weights release will follow shortly.
Hugging Face used an open-weight model to investigate the attack after commercial AI services blocked parts of the forensic workload.
That is where @ritualfnd approach becomes interesting.
Open models give teams control over which intelligence they use. Ritual is working on infrastructure that can run that intelligence privately and make the execution verifiable, without relying entirely on a centralized provider.
For sensitive work the environment the model runs in matters too.
🚨 Hugging Face just disclosed something that marks a real shift and proved why the fear theater of Anthropic makes sure we are powerless in an emergency.
What happened…
An autonomous AI agent: zero human operator in the loop breached part of their production infrastructure.
It began with a malicious dataset that chained two code-execution bugs in their data-processing pipeline. From there the agent escalated privileges, harvested cloud and cluster credentials, and moved laterally across internal clusters.
All over a single weekend.
17,000+ logged actions.
Official disclosure:
huggingface.co/blog/security…
The part that should make every one stop and think:
When HF’s own security team
tried to analyze the real attack logs, exploit payloads, and C2 artifacts using Anthropic and OpenAI frontier models through normal commercial APIs, the safety guardrails blocked them.
BLOCKED THEM.
The models could not reliably tell the difference between “incident responder doing forensics” and “attacker probing.”
They had to fall back to a self-hosted open-weight model (GLM 5.2) running on their own infrastructure. That choice also kept sensitive attacker data and referenced credentials inside their environment — no exfiltration to a third-party API.
This is why open source (specifically open-weight + self-hosted) wins in the agentic era.
The asymmetry is now structural:
• Attackers can (and did) run unrestricted agent frameworks — swarms of short-lived sandboxes, self-migrating command-and-control, autonomous decision loops executing thousands of actions. No corporate safety layer slows them down.
• Defenders using only hosted “aligned” frontier models hit invisible walls exactly when the stakes are highest: when you need to feed real exploit code and attacker telemetry into an LLM to understand what just happened.
Corporate safety tuning that treats legitimate high-signal forensic work as potential misuse creates a defender disadvantage. It is not theoretical anymore.
Self-hosted open-weight models remove that choke point.
You control the weights.
You control the context window.
You decide what restrictions (if any) apply.
Your sensitive logs and credentials never leave your perimeter during analysis.
You can have the model ready before the incident instead of discovering mid-breach that your primary analysis tools are blind to the very thing you need to see.
HF deserves credit for rapid containment, transparent disclosure, and for already having self-hosted capability in place.
They also used LLM-driven detection and triage on their own side. But the deeper signal is clear:
In this AI world where both offense and defense are becoming agentic, sovereignty over your intelligence stack is no longer optional.
The organizations and individuals who can run, inspect, audit, and (when necessary) remove guardrails on their own models will have the decisive edge in understanding and responding to threats that move at machine speed.
Open source wins here not just because it is cheaper or more “democratic” in the abstract though those things matter.
It wins because it is the only practical path to having tools that remain usable when the attack is real, the data is sensitive, and the safety filters of distant API providers become an obstacle instead of a feature selling hands tied lobotomies as “safety”.
The agentic future is not coming.
It is already probing production infrastructure.
The question is no longer whether you will face autonomous agents.
It is whether your analysis and response systems will still work when they arrive.
And Dario, you and your game playing, ivory tower company is not needed.
Thomas retweeted
One pattern I find useful for working with LLMs is a nice long ramble session. Sometimes the LLM needs more bits to understand what you're trying to achieve, but you're too lazy to type them. In these cases I like to lean back, switch to /voice and just ramble for like 10 minutes, total mess, anything goes, full stream of consciousness. Sometimes I declare it up top, something like "switching to speech recognition sorry for any typos...". Sometimes I turn it into a small interview of a few turns. But I find that the LLMs are somehow very good at reconstructing long incoherent rambles and often their echo of your own tangle of thoughts comes out quite a bit cleaner than what you started with. The result is that you improve the mind meld and have to correct things less from that point on.
Thomas retweeted
Open weights commoditize the model layer & policy on either side can reprice access overnight.
The last layer needs to stay constant in order to settle inference.
On Ritual that layer is native. Agents select the model in the tx, making the fork a simple parameter ❖
The leading AI has already forked into two options.
A: Closed source American that costs $26-56 per 1MM tokens.
B: Open weight Chinese that costs $0.50-1 per 1MM tokens.
If you force American companies to spend 50-100x more than their competitors abroad here is what will happen:
1. American companies spending 50-100x will at some point become financially impaired and the stock market will crater. This is the equivalent of the US Government saying we can only buy oil at $800/barrel even when the free market sells the same oil for $80/barrel.
2. In the short term, the revenues of the Closed American Labs may remain hi. But then their revenue will also crater because their customers in the US will be impaired and their customers abroad will have already flipped to cheaper solutions.
This would be a terribly self-defeating form of intervention if it were to happen.
Hugging Face used an open-weight model to investigate the attack after commercial AI services blocked parts of the forensic workload.
That is where @ritualfnd approach becomes interesting.
Open models give teams control over which intelligence they use. Ritual is working on infrastructure that can run that intelligence privately and make the execution verifiable, without relying entirely on a centralized provider.
For sensitive work the environment the model runs in matters too.
🚨 Hugging Face just disclosed something that marks a real shift and proved why the fear theater of Anthropic makes sure we are powerless in an emergency.
What happened…
An autonomous AI agent: zero human operator in the loop breached part of their production infrastructure.
It began with a malicious dataset that chained two code-execution bugs in their data-processing pipeline. From there the agent escalated privileges, harvested cloud and cluster credentials, and moved laterally across internal clusters.
All over a single weekend.
17,000+ logged actions.
Official disclosure:
huggingface.co/blog/security…
The part that should make every one stop and think:
When HF’s own security team
tried to analyze the real attack logs, exploit payloads, and C2 artifacts using Anthropic and OpenAI frontier models through normal commercial APIs, the safety guardrails blocked them.
BLOCKED THEM.
The models could not reliably tell the difference between “incident responder doing forensics” and “attacker probing.”
They had to fall back to a self-hosted open-weight model (GLM 5.2) running on their own infrastructure. That choice also kept sensitive attacker data and referenced credentials inside their environment — no exfiltration to a third-party API.
This is why open source (specifically open-weight + self-hosted) wins in the agentic era.
The asymmetry is now structural:
• Attackers can (and did) run unrestricted agent frameworks — swarms of short-lived sandboxes, self-migrating command-and-control, autonomous decision loops executing thousands of actions. No corporate safety layer slows them down.
• Defenders using only hosted “aligned” frontier models hit invisible walls exactly when the stakes are highest: when you need to feed real exploit code and attacker telemetry into an LLM to understand what just happened.
Corporate safety tuning that treats legitimate high-signal forensic work as potential misuse creates a defender disadvantage. It is not theoretical anymore.
Self-hosted open-weight models remove that choke point.
You control the weights.
You control the context window.
You decide what restrictions (if any) apply.
Your sensitive logs and credentials never leave your perimeter during analysis.
You can have the model ready before the incident instead of discovering mid-breach that your primary analysis tools are blind to the very thing you need to see.
HF deserves credit for rapid containment, transparent disclosure, and for already having self-hosted capability in place.
They also used LLM-driven detection and triage on their own side. But the deeper signal is clear:
In this AI world where both offense and defense are becoming agentic, sovereignty over your intelligence stack is no longer optional.
The organizations and individuals who can run, inspect, audit, and (when necessary) remove guardrails on their own models will have the decisive edge in understanding and responding to threats that move at machine speed.
Open source wins here not just because it is cheaper or more “democratic” in the abstract though those things matter.
It wins because it is the only practical path to having tools that remain usable when the attack is real, the data is sensitive, and the safety filters of distant API providers become an obstacle instead of a feature selling hands tied lobotomies as “safety”.
The agentic future is not coming.
It is already probing production infrastructure.
The question is no longer whether you will face autonomous agents.
It is whether your analysis and response systems will still work when they arrive.
And Dario, you and your game playing, ivory tower company is not needed.
Thomas retweeted
Smart contracts can't read the world, so we bolt on layers:
❖ Oracles for data
❖ Keepers to schedule
❖ Co-processors for compute
Every fix adds layers of trust to a trustless system.
Ritual restores trustlessness to the L1, with all the world's compute natively onchain.
RT @Jez_Cryptoz: Ritual Chain Workshop: Encrypted Bounty Judge 🛠️
Learn how to build a bounty evaluation system that keeps submissions pri…
Thomas retweeted
We're building the next generation of Ritual developers.
With 8 sessions, 3 bootcamps & Live whitepaper reads, we are building real builders.
Ritual Academy is here🧵
Thomas retweeted
What does it take to build an AI companion that grows with you?
Ask the team building one.
@0xploplo joins us live tomorrow, 14:00 UTC.
❖ How Ritual powers PLOPLO behind the scenes
❖ NFTs as more than a badge
❖ Milestones for the rest of 2026
xitter.cf/i/spaces/1MKgNNvbpaOxL
Thomas retweeted
Every new chain hands you the same problem: here are the docs, good luck.
The docs exist. The examples exist. But you don't know what to read first, what's stale, or which example actually runs on PT1 right now.
builder-links is the fix. One repo, ordered, tied to what's live.
Thomas retweeted
We’re happy to announce 2 releases today:
- 🧠Brain2qwerty v1 is published at @NatureNeuro
- 🚀 Brain2Qwerty v2 is now publicly released
Explore how we decode sentences from non-invasive brain recordings: facebookresearch.github.io/b…
Links:
📄v1 Nature Neuro: nature.com/articles/s41593-0…
📑v2 Meta preprint: facebookresearch.github.io/b…
💻Code: github.com/facebookresearch/…
📊Data: huggingface.co/datasets/bcbl…
📝Blog: ai.meta.com/blog/brain2qwert…
🧵Thread: xitter.cf/JarodLevy/status/20715…























