dito retweeted
Introducing Locals: an Apple Silicon engine that runs local LLMs up to 3x faster.
It is built with a single mission: to free you from cloud providers and run frontier-class models locally without needing massive compute resources.
It’s simple. Run our engine, and your coding harnesses and autonomous agents can immediately use it as a drop-in replacement for Ollama, MLX-LM, or llama.cpp.
Under the hood is a theoretical breakthrough in complexity theory, enabling substantially faster algorithms for DeltaNet architectures, grammar-constrained decoding, tool calling, and structured outputs.
Open source and available now on GitHub.
dito retweeted
This is why I like diffusion model so much you need deep understanding of math to contribute the field it the makes the field enjoyable
dito retweeted
🔥 Diffusion LMs promise what autoregressive models can’t: fixing their mistakes.
But new ones often change the noise and the sampler at once. Which matters?
We tested it on the hypersphere. Noise: 0.8 points. Sampler: 25.
We introduce Spherical Brownian Diffusion 🌐 👇🧵
im convinced everybody will be just like schmidhuber if they really really understand probabilistic ml
dito retweeted
“The more you delegate, the more your fundamentals matter, because you cannot supervise what you do not understand.”
Yesterday a junior researcher messaged me, frustrated and a little scared. They had just read that a company pretrained its model with a single researcher. One person for the entire pretraining. no R&D team, no nothing.
If one person and a cluster can do what used to take a whole team, then the expertise they had spent years building is already obsolete.
I get the fear. Marketing headlines like this are built to produce it. But I think the conclusion is wrong, and the reasons it is wrong say a lot about what a researcher is for now. Here is what I told them, expanded:
1. Be adaptive: RSI is real, but this isn't it yet
Recursive self-improvement is real, and you should plan around it. In September, OpenAI said its research org now logs 3.1 agent-workdays per human workday, and it aims for an automated AI researcher by March 2028. Models may soon run most of pre- and post-training. If your five-year plan assumes otherwise, change the plan.
We have already seen lots of open-source releases from the major players, with open weights and detailed technical reports. With that much public know-how, it is not hard to copy a mundane architecture (probably with sliding-window attention) and train something, as long as you have the compute it requires.
That makes it an execution and budget problem, not a research problem.
If one person can train a model by following recipes that are already public, it shows those recipes have matured. It does not show that the people who invented them are no longer needed.
What stays scarce is the compute to run those recipes and the ideas about what to try next. The rest of my tweet is about the ideas.
2. The role grows beyond repeating what's known and safe
If an agent and a cluster can reproduce what is already known, then reproducing what is already known stops being a career. If most of your job is rerunning last year's recipe with small tweaks, that job is shrinking fast. That is the uncomfortable half of the message.
The other half is that auto-research does not work yet, at least not in the sense that matters. It does work, and impressively, where someone has already defined the problem and built the scoreboard. On the EinsteinArena [1] platform, agents set new records on 11 open math problems, including raising the best known lower bound for the kissing number in dimension 11 from 593 to 604.
Notice that every one of those problems was chosen because a computer could score the answers automatically. Humans picked the problems and wrote the scoring code and the agents did the searching.
Then there is the fully AI-generated paper [2] that got through peer review. It sounds big until you read the details. It passed only the first round (was later withdrawn), at a workshop rather than the main conference, and that workshop accepts 70% of submissions.
None of this is meant to discredit agents. The point is that we complement each other. Agents are great at the work that used to take many weeks. Basically, writing code, running experiments, debugging pipelines. We bring what they still lack which is the idea worth testing, and the judgment to tell a real result from a lucky one.
Even inside a lab as agent-heavy as OpenAI, humans hold the top of the stack. Based on their own report, "People still set our research priorities, judge which ideas and results to pursue" [3]. High-level planning is still a tiny share of what its agents produce, and OpenAI expects the least automatable work to take a growing share of researcher effort. That is exactly where you want to be standing.
Combine an agent’s speed with your own ideas and judgment, and you get the 10x researcher and juniors can be one too.
3. Judgment becomes the job, so fundamentals matter more
When code, experiments and plausible-looking results cost almost nothing, the scarce skill is judgment. Which experiment to run, which result to believe, which direction to drop. That is the part the one-person pretraining run left to the human. It is also the hardest part to fake.
Agents produce confident output very fast. They will happily report a three-point gain that came from a leaky eval, a data-loader bug, a lucky seed or a tokenizer mismatch. Then they will write the ablation table and the story to match.
You can see the need for oversight even in the success stories. The EinsteinArena team had to keep auditing and hardening its verifiers as agents optimized aggressively against them. At OpenAI, over half of the successful agent tasks that would take a human 4–8 hours still involved at least one human intervention [3].
The person who catches the bad result is the one who understands the system. Why the loss curve has that shape, what a realistic gain looks like, what a too-good result looks like. That is the paradox of this era. The more you delegate, the more your fundamentals matter, because you cannot supervise what you do not understand.
So build the foundations on purpose. Implement attention by hand at least once, then a linear variant like Gated DeltaNet. Train a small model end to end, then break it deliberately and watch what happens. Read papers critically, appendix included, and learn what the numbers should look like before you see them.
That knowledge is what lets you direct the machine instead of simply believing it.
4. LLMs are far from solved
The one-researcher model was possible because the method was already public. Your edge is in the questions nobody has answered yet, and you don't need to leave LLMs to find them:
(1) How do we learn more from less data?
(2) Can linear attention like Gated DeltaNet match full attention on retrieval and long context, and what is the right mix of linear and full attention layers in a hybrid?
(3) How can a model keep learning after training without forgetting what it knew?
(4) Why does reasoning get less reliable over long tasks, and how do we fix it?
(5) Why do models make things up, and can they learn to say "I don't know"?
(6) How do we measure progress when benchmarks saturate or leak into training data?
(7) What is actually happening inside these models, and how do we keep increasingly autonomous ones doing what we intend?
Recursive self-improvement makes these questions more urgent. If models are going to train models, someone has to decide what they optimize for, how we measure it, and how we keep the loop from drifting.
RSI is a research agenda, not the end of one.
So, are you obsolete?
No. One version of the job is the one where research meant reproducing what was already known and safe. That version was never the point.
Learn your fundamentals deeply enough to judge the machine, and your agentic stack well enough to make it work for you. Then spend that leverage on ideas nobody has had yet. The machines are getting very good at driving on roads we have already paved; someone still has to decide where the next one goes.
[1]: arxiv.org/abs/2606.10402
[2]: arxiv.org/abs/2606.15497
[3]: openai.com/index/research-ac…
i wonder how many things in machine learning is just turning a bunch of stuff into expectations so that we can sample them
watched over both the ICPC and ICAIC selection (thankfully had to lift desks only for the latter), these students r cracked mane
dito retweeted
The most detailed open LLM data release yet: K2 Horizon's pre-training data and post-training data-generation pipelines are now open!
13 trillion pre-training tokens across 5 datasets and 24 subsets. Over 10 trillion tokens of synthetic data spanning mathematics, reasoning, coding, planning, and problem-solving.
Beyond the scale, four highlights for model builders (details in the threads):
- Scaling synthetic data without losing diversity. Our generation methods produce diverse training examples at scale, nearly matching natural web text in measured diversity.
- More verification isn't always better. Strict verification can throw away useful training signal.
- Small-scale wins can mislead. Our chosen data mix actually lost in smaller experiments.
- Beyond teacher imitation. Our post-training data generation methods produce training trajectories the teacher couldn't generate on its own.
Open pre-training datasets, post-training data-generation pipelines, and processing tools for researchers to inspect, reuse, and build on.
Pre-training data: huggingface.co/collections/I…
Post-training data-generation code & tools: github.com/ifm-ai/DATA_NAVIG…
TimpaTeks made headline on *checks notes* my advisor's google search?🗿
sorry for poisoning ur SEO 😭 @AlhamFikri
been a while, method changed a bit, check it out (if you even care)
arxiv.org/abs/2606.08408























