There’s a specific kind of online moment that only makes sense if you’re already inside it. From the outside it looks like nothing. From the inside it’s genuinely delightful.

This week, a well-known figure in the local LLM community starred a GitHub repository. That’s it. That’s the whole event. He starred llama.cpp, the foundational codebase behind most of the quantised models that hobbyists and tinkerers run locally on consumer hardware. The catch is that he’s been producing quantised GGUFs from that very codebase for longer than most people in the space have known it existed. Thousands of them. A quiet, consistent, enormous contribution to making local AI actually usable for ordinary people. And apparently he’d never clicked the star button.

There’s a particular kind of excitement that lives in corners of the internet where people argue about quantisation formats and token generation speeds. It is extremely nerdy. It is also, if you care about who gets to use powerful AI tools, genuinely important.

Qwen 3.7 dropped recently, and the announcement sent certain communities into a state that I can only describe as “physiologically enthusiastic.” People were excited about 122 billion parameters, 17 billion active per inference run, something called MTP that apparently doubles generation speed without quality loss, and a 512k context window. Someone tried to explain all of this patiently to a confused commenter, and I appreciated the effort. The explainer was good.

So AMD apparently just dropped some news at their AI Dev Day about releasing their own in-house Ryzen AI 395 mini PC box, coming in June. And the tech corners of the internet are… cautiously underwhelmed? Which, honestly, is a pretty reasonable reaction when you dig into what it actually is.

The short version: it’s a 395 with 128GB unified memory. Same as what you can already buy from a dozen different vendors right now. No extra bandwidth, no architectural magic, just AMD putting their own name on the box. One person who was actually at the event confirmed it directly with an engineer on the floor — just a standard 395 system, nothing more.

There’s a thread doing the rounds on r/LocalLLaMA that’s been rattling around in my head for the past couple of days. It started out as people poking at what appeared to be an AI bot posting in the community — responding to comments, giving out banana bread recipes, the whole nine yards — and it quickly spiralled into one of those gloriously chaotic internet moments where nobody’s quite sure who, or what, they’re talking to anymore.

So I’ve been down a rabbit hole this Easter weekend, and it has nothing to do with chocolate eggs. Google DeepMind dropped Gemma 4, and the local AI community has basically lost its collective mind — in the best possible way.

For those not deep in the weeds on this stuff, Gemma is Google’s family of open-weights AI models. The new Gemma 4 lineup ranges from tiny models designed to run on phones all the way up to a 31 billion parameter beast that’ll give your home server a decent workout. And the specs are genuinely impressive: multimodal input handling text, images, video and audio, context windows up to 256K tokens, native tool calling, built-in reasoning modes, and support for over 140 languages. That last point is actually more significant than most people give it credit for — more on that in a moment.

There’s something both beautiful and slightly chaotic about open source AI development that reminds me of my DevOps days. You know that feeling when you push what you swear is the final fix to production, only to find yourself back at your desk three hours later because someone spotted an edge case? Well, the LocalLLaMA community just got a dose of that with the latest Qwen3.5 GGUF update from Unsloth.