| ← All issues | |
| The Diff No. 013 Friday, 16 October 2026 · AI dev news, only what is verified |
 |
Everyone shipped something fast. Check who built it first. Meta released the weights of a model it says runs on two Mac Studios. A launcher race between Epic and Steam turned on numbers nobody could pin down. The author of an old Meta source control server says Anthropic’s Scion borrowed heavily from it, and Anthropic has since added credit to its post. Today: Muse Spark Open, the Epic and Steam speed race, a follow-up on last issue’s Scion, and a long Goodfire essay on how readable neural networks may be. Fast is easy to claim. Credit and measurements take a second look. |
IN THIS ISSUE | 01 🍎 816 billion parameters, two Mac Studios Meta released the weights of Muse Spark Open and says it runs on a desk. | | 02 🏁 A launcher race, and no shared stopwatch Epic shipped a vibe-coded launcher. Steam patched back within a day. |  | 03 🪪 He says he built that server, and he wants credit A follow-up on last issue’s Scion, from the author of Meta’s Mononoke work. | | 04 🧠 "Neural networks are already clean" Goodfire researcher says polysemanticity was misread, and interpretability may be easier. |
|
🔥 VIRAL The loud ones on Hacker News. Numbers are a morning snapshot. | 01 HN: 663 points · Meta AI Research blog, Oct 15 🍎 816 billion parameters, two Mac StudiosMeta released the weights of Muse Spark Open and says it runs on a desk. SCENE Meta says it released the weights of Muse Spark Open on October 15: 816B total parameters, 42B active, a 1M-token context window, natively multimodal. The post says it is the first model in its class to run on a desktop, using two Apple M5 Ultra Mac Studios with MLX. On HN, one commenter was glad to see a major lab ship open weights. Another, popinman322, points at the license. THE THING Meta’s post says the weights ship under the Muse Model License with limited commercial terms that let many developers use it free. The commenter says it requires large inference providers to contact Meta for a license, and that this has tended to reduce price competition. We did not read the license text, so check it before you build on it. The post says Meta tested agent workflows fully on-device with its own Muse Code tool: iOS changes to the open-source Ice Cubes Mastodon client, including a build, and driving DaVinci Resolve to find and crop clips. It lists hosted providers (Baseten, Fireworks, Groq, Modal, Nebius, OpenRouter, Together) and runtimes from vLLM to llama.cpp. The benchmark section on the page had no readable numbers when we fetched it, so we cannot repeat any. Every claim here is Meta’s. We did not download or run it. ✂️ STEAL IT The sentence worth acting on is about hardware, not the model: the post says each M5 Ultra Mac Studio gives the GPU up to 512 GB of unified memory, so two hold the whole model. Work out what your own box can hold before you read any benchmark. Watch VERDICT Open weights from a major lab are real news. It fails the "just run it" test: it needs two top-end Macs or a GPU node, and the license has commercial limits you must read yourself. Meta AI Research post · Deploy docs · HN discussion |
02 HN: 295 points · secondhand article, Oct 15 🏁 A launcher race, and no shared stopwatchEpic shipped a vibe-coded launcher. Steam patched back within a day. SCENE Respawnfirst’s Sikandar Mahmood reports that on October 14 Epic launched a preview of a new game launcher, described as vibe-coded, and pitched it as faster than Steam. He says Valve pushed a small update within 24 hours that made Steam’s client faster. His article has a table: Epic about 5.47 seconds cold start and 0.36 seconds tray restore, Steam about 5.23 and 0.42. THE THING The article says the numbers came from "basic test systems" and does not say who ran them or how. On HN, a commenter named tancop says he tried both: Epic around 0.5 and 5 seconds, which matches the article, and Steam about 2 seconds to restore from the tray and 10 to 15 cold. That is one person’s test, but it does not match the article’s Steam figure. Another commenter argues the launch time barely matters for an app that stays open for hours. We did not read Epic’s own announcement or run either client. ✂️ STEAL IT Before you repeat a speed claim, find out who measured, on what machine, and whether cold or warm. Run your own timing, three times, and write down the version. Skip VERDICT Skip the headline. The numbers are unsourced and one reader got different ones. The useful part is the habit of timing it yourself, which takes five minutes. Respawnfirst article · HN discussion |
🔭 UNDER THE RADAR Quiet tools and field reports worth your time. |  03 HN: 232 points · author blog, Oct 15 · Sapling repo 7.1K stars, GPL-2.0 · card: GitHub 🪪 He says he built that server, and he wants creditA follow-up on last issue’s Scion, from the author of Meta’s Mononoke work. SCENE In No. 011 we covered Anthropic’s post about Scion, its in-house version control system. Two days later, a developer who writes as sunshowers posted that Scion closely resembles Mononoke, the source control server he says he helped build on Meta’s source control team. He cites his 2022 candidate materials for Oxide, which describe Mononoke’s derived data and Bonsai changesets. THE THING His follow-up says it goes beyond one concept: the data model and several structures around it match, down to the name, which he notes reverses the syllables of "Bonsai." He says he privately received confirmation that the resemblance was intentional and that staff overlapped. That is his claim, and he names no source. He also says Anthropic’s Nick G. replied on HN and that attribution was added to the post. We checked: the Anthropic post now says it was updated October 15 with more detail on the projects that pioneered its techniques, and a footnote names Sapling’s server component, Mononoke, and "the Bonsai data model." On HN, another reader says the new detail is that some Scion builders previously worked at Meta on this. Others dispute the framing. We cannot judge intent. ✂️ STEAL IT If you publish an engineering post about a system you built, say what it descends from. It costs one footnote, and it saves you a thread like this one. Watch VERDICT The attribution fix is checkable and has happened. The claim of intentional copying and shared staff is one person’s account. Treat the copying claim as his, and the credit fix as something we checked. Anthropic post, now updated · Original post · Follow-up · HN discussion |
04 HN: 542 points · Goodfire essay, about 65 minutes to read · only the summary read 🧠 "Neural networks are already clean"Goodfire researcher says polysemanticity was misread, and interpretability may be easier. SCENE Nick Cammarata of Goodfire has published a long essay he calls a working hypothesis. His argument: after months studying neurons and circuits in image and language models, he now thinks the evidence that convinced the field neurons pack unrelated concepts into one unit, called superposition, was misread. On HN a commenter says he was 16,000 words in and still could not tell what the essay meant by "clean." THE THING The essay’s summary says the cause of polysemanticity in early model organisms was not superposition but several ordinary, mostly fixable issues. For InceptionV1 it blames architecture that made later layers overflow, plus weak tools that made them look worse. It says architectural changes meant to help deep layers learn have made them more interpretable, that most neurons in models up to trillions of parameters can now be understood, and that interpretability may be far more tractable than feared. These are the author’s claims. We read the summary and about a page of the essay, not the whole 65 minutes, and did not check any result. Another HN commenter would not rush to call superposition wrong. ✂️ STEAL IT For practical work, the idea to try is the low-tech one: look at a network’s own neurons and circuits before you train a second model to decompose them. Watch VERDICT A serious, readable bet from a working interpretability team. It is a hypothesis, not a result the field has accepted, and we cannot vouch for the parts we did not read. Neural Networks Are Already Clean · HN discussion |
📊 THE ATTENTION GAP HN points at 06:30 IDT. Attention, not quality. | Muse Spark Open | | 663 HN | | Goodfire essay | | 542 HN | | Steam vs Epic | | 295 HN | | Scion follow-up | | 232 HN |
|
🗂️ THE BORING STUFF Oct 15 · Libreboot 26.10. The release notes say a new AGENTS.md in the lbmk build system sets a strongly anti-AI policy, and call it the most important change in the release. The same release adds full UEFI support through a MrChromebox EDK2 payload. Libreboot release post → Official page read this morning. Nothing installed or run. |
🧪 ONE THING TO TRY TONIGHT Time it three times. Pick a speed claim you read this week. Run the thing yourself three times, cold and warm, and write down the version and machine. Then compare it with the claim. |
What this issue could not see. HN, a vendor blog, a trade article, three personal and research blogs, a project release post and Anthropic’s updated post were read. Nothing was installed or run, and the Goodfire essay was only partly read. Deduped against every published issue; the Scion follow-up is flagged as such. Reddit returned rate-limit errors earlier in the week; X, Product Hunt and Bluesky returned nothing usable and LinkedIn was a login wall, so none of those are covered today. Video discovery found nothing current that passed review, so no video is recommended. |
| Images: credited in each report; source screenshots and announcement artwork, not our tests. |
|