Cloudflare freed up 100TB of RAM from its 1.1.1.1 DNS cache by optimizing how billions of entries are stored, while making the cache faster.

When people talk about AI image editing, the same names come up. Nano Banana, GPT Image or Maybe one or two others. And they're good, no argument there. But they all have something in common. You're on their servers, their terms & some generates watermark along with your image. What if I told you the open source community has been building real alternatives? Models you can actually run on your own hardware with no watermarks & no usage limits. Some of them are hitting benchmark scores that are really impressive. A few of them you can even build on top of, fine tune, or deploy in your own products. I went through what's out there and narrowed it down to six that are genuinely worth your time

Open almost any "best AI coding tools" list and you'll see the same names: Cursor, GitHub Copilot, Claude Code. They're good tools but they're also closed source and paid. What's changed over the past year isn't the quality of those products, it's how quickly the open-source alternatives have caught up. Some can orchestrate multiple agents, remember your projects across sessions, and automate complex development workflows. Many let you bring your own model, whether that's a local LLM, OpenRouter, OpenAI, GLM-5.2, Ornith, DeepSeek, or something else entirely. More importantly, you're in control. You decide where your code runs, which model powers it, and how your workflow evolves without being locked into a single company's ecosystem. If you've only looked at the paid options, these are the open-source AI coding tools worth knowing about.

WordPress has a problem it cannot fix from the inside. Not a performance problem. Not a features problem. A structural one. 96% of its security vulnerabilities come from plugins, and the reason is simple. Every plugin gets access to everything. The database, the filesystem, the entire execution context. That is how it was built in 2003 and that is how it still works today. Cloudflare looked at that and decided patching was the wrong answer. EmDash is their attempt to start over. Built in TypeScript, Its serverless & powered by Astro & MIT licensed. No PHP, legacy architecture or plugins that can silently access your entire database. I want to be straight about what this is right now. It is a v0.1.0 developer preview. You are not migrating your production site today. But the architecture decisions behind it are serious enough that if you build on WordPress, run a plugin business, or host WordPress sites for clients, you should understand what Cloudflare just shipped.

There's a version of this story where Anthropic was trying to protect itself from large-scale model theft. There's another where one of the AI industry's biggest privacy advocates quietly crossed a line its own users never expected. What makes this headline important isn't just that hidden tracking code existed. It's that the company behind it was Anthropic. Just months ago, Anthropic publicly refused to let the Trump administration use Claude to surveil American users. The company defended that position in court, arguing that AI companies shouldn't become tools for government surveillance. That stance became part of Anthropic's identity. Then came a very different decision. In March, Anthropic quietly added hidden tracking markers to Claude Code that flagged users' timezones, proxy connections, and potential ties to Chinese AI labs. The code remained unnoticed until security researcher Thereallo discovered it last week. After the discovery went public, an Anthropic engineer confirmed it on X, described it as an "experiment" intended to combat account abuse and model distillation, and said the company had already planned to remove it. The tracker was taken down shortly afterward. The bigger question isn't whether Anthropic had a reason. It's whether a company that built its reputation on privacy can afford to hide surveillance from the very developers it asks to trust its tools.

On Sunday, Shopify CEO Tobi Lütke did something most machine learning engineers spend months trying to achieve. He improved a core model's performance by 19% while he was asleep & didn't use a massive compute cluster or a team of researchers. He used a 630-line weekend project released by Andrej Karpathy called autoresearch. By the time he woke up, the agent had run 37 experiments, tested dozens of hyperparameter combinations, and handed him a 0.8B model that outperformed the 1.6B model it was meant to replace. Karpathy's response when he heard? "Who knew early singularity could be this fun." That's the story everyone is sharing. But the more interesting story is what autoresearch actually is, how it works, and what it quietly says about where AI research is heading.

When the news broke that OpenAI had built a custom chip, the instinct was to frame it as a NVIDIA story. Another lab trying to cut the cord, reduce dependence on H100s, claw back some margin from the company that's been printing money off the AI boom. That's not quite what's happening here. The chip is called Jalapeño, built with Broadcom, and it doesn't touch training at all. It's an inference chip, meaning it only runs models after they're already built, when a user sends a message and ChatGPT has to respond. The compute-heavy work of actually training those models still runs on NVIDIA hardware. OpenAI isn't replacing NVIDIA. It's going after a different part of the problem entirely, the part that happens millions of times a day, every time someone uses one of their products. That distinction matters because inference is where AI costs actually accumulate at scale. Training happens once per model. Inference never stops.